You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure how hard it would be, but I have a use case to use this package as a tool for rewriting TOML files without affecting style and whitespaces. So, the first idea that I had would be to write a function which can take the toml eslint AST and generate the TOML source.
I'm not so sure how far away an idea like this is, but I feel like it's a small change to at the least maintain newlines and comments.
I'm not entirely sure, but I thought I'd throw this idea in here.
Cheers
– Cole
The text was updated successfully, but these errors were encountered:
For now, whitespaces information is not stored on the node as it is intended for use with the ESLint plugin.
However, all comment information is stored in the root node.
I don't know how your tool works, but could you open the PR if you have the information you need? Or could you write the details of the information you need here and wait for someone to work on it?
If that doesn't break the ESLint plugin, I'll probably accept the change.
I'm not sure how hard it would be, but I have a use case to use this package as a tool for rewriting TOML files without affecting style and whitespaces. So, the first idea that I had would be to write a function which can take the toml eslint AST and generate the TOML source.
I'm not so sure how far away an idea like this is, but I feel like it's a small change to at the least maintain newlines and comments.
I'm not entirely sure, but I thought I'd throw this idea in here.
Cheers
– Cole
The text was updated successfully, but these errors were encountered: