-
Notifications
You must be signed in to change notification settings - Fork 278
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
schema version? #104
Comments
@thomasdavis Is this already done and can this be closed? |
This is not yet in the schema. The actual schema is versioned, but the json for each resume does not reflect or store any version. So a field such as the proposed:
Is still needed |
dupe of #49 ? |
Yep. You can close this thread as duplicate. |
👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Howdy,
We should use Semantic Versioning, and have that defined in the JSON. That way, when the parser hits that, it knows what fields should be defined.
What do you think?
Thanks,
Jason Swindle
The text was updated successfully, but these errors were encountered: