fatedier 01a0d557ef fix legacy ini proxy conversion panic (#3667) 1 年間 前
..
README.md c95311d1a0 support yaml/json/toml configuration format, make ini deprecated (#3599) 1 年間 前
client.go 3ae1a4f45a update confugration examples and README (#3650) 1 年間 前
conversion.go 01a0d557ef fix legacy ini proxy conversion panic (#3667) 1 年間 前
parse.go c95311d1a0 support yaml/json/toml configuration format, make ini deprecated (#3599) 1 年間 前
proxy.go 5e70d5bee0 code optimization (#3625) 1 年間 前
server.go 5eb8f3db03 fix tlsVerify json tag (#3654) 1 年間 前
utils.go c95311d1a0 support yaml/json/toml configuration format, make ini deprecated (#3599) 1 年間 前
value.go c95311d1a0 support yaml/json/toml configuration format, make ini deprecated (#3599) 1 年間 前
visitor.go 5e70d5bee0 code optimization (#3625) 1 年間 前

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.