fatedier 9cebfccb39 cmd: add verify command to verify if config file syntax is valid (#2389) il y a 3 ans
..
README.md 3621aad1c1 Reconstruct config (#2098) il y a 4 ans
client.go 9cebfccb39 cmd: add verify command to verify if config file syntax is valid (#2389) il y a 3 ans
client_test.go b5aee82ca9 update: support custom tls server name (#2278) il y a 4 ans
proxy.go 9cebfccb39 cmd: add verify command to verify if config file syntax is valid (#2389) il y a 3 ans
proxy_test.go 3621aad1c1 Reconstruct config (#2098) il y a 4 ans
server.go 0d84da91d4 change default value of dashboard_user and dashboard_pwd to empty string (#2383) il y a 3 ans
server_test.go 0d84da91d4 change default value of dashboard_user and dashboard_pwd to empty string (#2383) il y a 3 ans
types.go 3621aad1c1 Reconstruct config (#2098) il y a 4 ans
types_test.go 3fbdea0f6b rename models to pkg (#2005) il y a 4 ans
utils.go 3621aad1c1 Reconstruct config (#2098) il y a 4 ans
value.go 3621aad1c1 Reconstruct config (#2098) il y a 4 ans
visitor.go 1a11b28f8d config: inline is NOT SUPPORTED in encoding/json (#2304) il y a 4 ans
visitor_test.go 8fcd4f4a95 client: reconnect more quickly if it's a dial error (#2240) il y a 4 ans

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.