Skip to content
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

fix(commit, MetadataEditor): fix meta editing and the flow after you commit #394

Merged
merged 2 commits into from
Jan 17, 2020

Conversation

ramfox
Copy link
Member

@ramfox ramfox commented Jan 15, 2020

Adjust the saveWorkingDatasetAndFetch and Commit components, along with the mutations reducer and actions to fix the flow after you commit.

We need to wait for both the commit to be successful and for the history list to update, inorder to show the user a clean commit experience. To do that, we've added a saveComplete/SAVE_COMPLETE action to the mutations reducer that gets called when save & history fetching is complete

Also adjusts the MetadataEditor to fix a content jumping problem

Also, also fixes a bug when navigating to a dataset using the dataset list.

After this pr, e2e tests are passing locally, but not on ci

closes #396

@ramfox ramfox added the fix label Jan 15, 2020
@ramfox ramfox self-assigned this Jan 15, 2020
@ramfox ramfox force-pushed the commit-flow-fix branch 4 times, most recently from 60707ae to 0e3878c Compare January 17, 2020 17:53
…commit

Adjust the `saveWorkingDatasetAndFetch` and `Commit` components, along with the `mutations` reducer and actions to fix the flow after you commit.

We need to wait for both the commit to be successful and for the history list to update, inorder to show the user a clean commit experience. To do that, we've added a `saveComplete`/`SAVE_COMPLETE` action to the `mutations` reducer that gets called when save & history fetching is complete

Also adjusts the MetadataEditor to fix a content jumping problem
…aset is called

Also adds an e2e test to confirm behavior
Copy link
Member

@b5 b5 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! Apparently we need to fix some stuff with FSI integrations before CI will be happy, so LGTM, but let's fix that shit

Comment on lines +458 to +462
dispatch(setSaveComplete())
dispatch(openToast('success', 'commit', 'commit success!'))
dispatch(setSelectedListItem('commit', path))
dispatch(setActiveTab('history'))
dispatch(setSelectedListItem('commitComponent', DEFAULT_SELECTED_COMPONENT))
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hmmm... these are all firing in parallel? Let's examine this in a future PR!

@@ -206,32 +206,59 @@ describe('Qri End to End tests', function spec () {
await checkStatus('structure', 'added')
})

it ('navigate to collection and back to dataset', async () => {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🙌

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

bug(Dataset History): if 'history' is selected when opening the app, spinner is always spinning
2 participants