You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
frp/pkg/config
fatedier 900454e58b
more e2e test cases (#2450)
3 years ago
..
README.md Reconstruct config (#2098) 4 years ago
client.go Typo: josn => json (#2429) 4 years ago
client_test.go frpc: support 'includes' in common section to include proxy configs in other files(#2421) 4 years ago
parse.go frpc: consider include configs for verify and reload command (#2424) 4 years ago
proxy.go frpc: consider include configs for verify and reload command (#2424) 4 years ago
proxy_test.go Reconstruct config (#2098) 4 years ago
server.go more e2e test cases (#2450) 3 years ago
server_test.go change default value of dashboard_user and dashboard_pwd to empty string (#2383) 4 years ago
types.go Reconstruct config (#2098) 4 years ago
types_test.go rename models to pkg (#2005) 4 years ago
utils.go Reconstruct config (#2098) 4 years ago
value.go Reconstruct config (#2098) 4 years ago
visitor.go config: inline is NOT SUPPORTED in encoding/json (#2304) 4 years ago
visitor_test.go client: reconnect more quickly if it's a dial error (#2240) 4 years ago

README.md

So far, there is no mature Go project that does well in parsing *.ini files.

By comparison, we have selected an open source project: https://github.com/go-ini/ini.

This library helped us solve most of the key-value matching, but there are still some problems, such as not supporting parsing map.

We add our own logic on the basis of this library. In the current situationwhich, we need to complete the entire Unmarshal in two steps:

  • Step#1, use go-ini to complete the basic parameter matching;
  • Step#2, parse our custom parameters to realize parsing special structure, like map, array.

Some of the keywords in tag(like inline, extends, etc.) may be different from standard libraries such as json and protobuf in Go. For details, please refer to the library documentation: https://ini.unknwon.io/docs/intro.