Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
INI file format vs. others (JSON, YAML, XML...) #914
From time to time, we consider whether we should continue using INI as our DB-mirroring file format. I'm creating this issue to document the issues, possible alternatives and our thinking in general.
The goal of our format is to be as friendly as possible to diffing and merging. This drives everything. The power users will work with the format in diff tools and even in our current UI, users can go to the Details panel (#49) and with the full diff.
The format needs to be simple and preferably without indentation. This all lead to the decision to use an INI format as soon as issue #1.
What we don't like about INI
First and foremost,
Then, a smaller thing, INI format just isn't "cool" in a sense that we have this old, archaic thing in an otherwise greatly progressive project. But that's obviously just a very minor thing.
In regards to the parse_ini_string(), you can replace that with zendframework/zend-config. Docs at https://github.com/zendframework/zend-config/tree/master/doc/book
Although zend-config ini uses parse_ini_string() function, the zend team did all the heavy lifting.