This repository has been archived by the owner on Apr 9, 2022. It is now read-only.
Flexible Parse Excel #301
Draft
Flexible Parse Excel #301
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Resolves #292
Test out Excel parsing to make sure this plan works
Get keys from Excel sheet and ask user for input on whether they want it as a candidate field and for name
Ask on the front end for name inputs? Because you can't interact with it after you deploy
Use a json file to keep a map of the candidate fields- the ones that are specified in the schema, and specify part of the map for custom fields
Store map somewhere (in Utils probably) To be able to display in front end
Test out having
strict: falsefor CandidatesChange frontend to be able to display fields not specified in schema