Release datapipe-client - #276
Merged
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
datapipe-client@0.2.0
Minor Changes
4479720: Accept
experiment_id, the name the jsPsych extension and plugin use for the experiment ID, so the same option is spelled the same way everywhere.experimentIDstill works and there are no plans to remove it. Give one or the other. If both are given and differ,saveData,saveBase64DataandgetConditionthrow, and a session starts inert with a console warning. Nothing changes on the wire.132affd: Pass the session to
saveDatawithsessioninstead of flushing and readingsessionIdyourself.saveDatawaits for the session to start and sends its id.Adds
session.ready(), which resolves once the session has started (or failed to). It waits only for startup, not for staged writes, so a final submission from a background tab is no longer held up by a throttled flush.sessionIdstill works.