-
-
Notifications
You must be signed in to change notification settings - Fork 21
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.
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
feat(parser,frontend,backend): conserve comments order and sort properties at export #364
Conversation
62ca3f7
to
22f9afc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few questions and nits but it seems mostly great!
NB: did you do a few checks on various taxonomy files? I'd bet that there are some very weird edges cases that we have not thought of
You can also add comment tests for the parser |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks !
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good
What
Currently, all comments are parsed together for an entry node, and rewritten at the beginning of the node at export. This PR modifies the parser to keep the order of the comments during parsing to be able to rewrite them in the same order at export.
For that, we create a comments field for each commented property/language in each entry node in Neo4J.
A backend controller (
update_node
) has also been updated to take these comments into account.This PR also disables the display of comments on the frontend, to simplify the app for now.
This PR also sorts the properties of an entry node at export to have a deterministic output.
Part of
Resolves #363
Resolves #365