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
{{ message }}
This repository has been archived by the owner on Jan 29, 2023. It is now read-only.
It would be great if a Hocon node could also yield its current path in the document.
It should merely be a additional field in the Hocon-enum, though I could be missing some complexity since I currently have no idea how this nom parser macros work and I assume you need the information from there.
The text was updated successfully, but these errors were encountered:
it should be possible with nom, but I'm using an old version (4.2) when current (6.1) changed a lot and is nicer to use
when trying to update, I encountered an issue (rust-bakery/nom#1021) that makes it harder to follow the Hocon spec... I should try again, that was quite some time ago
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It would be great if a Hocon node could also yield its current path in the document.
It should merely be a additional field in the Hocon-enum, though I could be missing some complexity since I currently have no idea how this nom parser macros work and I assume you need the information from there.
The text was updated successfully, but these errors were encountered: