handling of OSF requests via OSF redirect service #126
Conversation
This file contains hidden or 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
adds some status codes for the OSF entry point concerning linking an OSF account to a DataPipe user account
stores the OSF environment (base is none, test., staging5., etc...) in NEXT_PUBLIC_OSF_ENV and OSF_ENV so we can switch between OSF environments! note that it has to have a period at the end since we are appending within a URL.
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.
this PR continues on the COS grant work, now adding support for users on the OSF website to access DataPipe via a custom pop-up window. this will handle both the linking of accounts (without a
nodeIri, justuserIri) and creating experiments that are automatically tied to a specific component, as opposed to the regular workflow of assigning a component via getting the id themselves.things to work on before merge: