feat: store raw stopwords and rewrite them at export #358
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
perierc
commented
Jan 19, 2024
There was a problem hiding this comment.
Note: this breaks the export for projects parsed before this PR.
alexgarel
approved these changes
Jan 22, 2024
Co-authored-by: Alex Garel <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
Currently, the parser reads the raw stopwords from the input taxonomy file, normalizes them and stores only these normalized stopwords in the Neo4J database.
This PR makes the parser store the raw stopwords also, to be able to rewrite them at export.
WARNING: This PR will make previously open projects impossible to export.
Part of
See issue #357