Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add support for TOML #16

Open
ESultanik opened this issue May 28, 2020 · 1 comment
Open

Add support for TOML #16

ESultanik opened this issue May 28, 2020 · 1 comment
Labels
enhancement New feature or request

Comments

@ESultanik
Copy link
Collaborator

No description provided.

@ESultanik ESultanik added the enhancement New feature or request label May 28, 2020
ESultanik added a commit that referenced this issue Jun 9, 2020
@ESultanik
TOML diffing support, but no formatter yet (#16)
40ff708
ESultanik added a commit that referenced this issue Jun 9, 2020
@ESultanik
Rudimentary TOML formatting (#16)
e0edd9c
ESultanik added a commit that referenced this issue Jun 10, 2020
@ESultanik
Added a formatting test for TOML (#16)
761a09e
@ri0t
Copy link

ri0t commented Feb 27, 2021

Soo. lemme see if i got this right: Once this issue is solved, i can use graphtage to automatically update old toml-configuration file versions to up to date ones by supplying a small ruleset (i.e. patch) on whats changed? That would be lovely!

I've just implemented a crude upgrader for that purpose - but i feel, that it lacks in power/flexibility. E.g. it renames field names by search/replace... duuuhhh..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ri0t @ESultanik