Mock orcid login in dev environment #1375
Open
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
…e seed entries to upsert instead of error if they already exist
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.
Fix: #1374
It is currently impossible to login in the dev environment, meaning that we can't interactively try and replicate bugs in prod that require a login like paper submission. In general it's great to be able to test things in a dev environment instead of needing to test in prod!
This PR just mocks the OmniAuth provider using instructions from their docs to automatically log us in as the Lord Fake user.
I updated the seed.db entries to match that (added uid and provider fields) and also updated those to upsert instead of error if they already exist.
It was also impossible to create a paper without a subject existing, so i added one.