-
Notifications
You must be signed in to change notification settings - Fork 39
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
[ENG-4460] Toggle assertions based on preprint-provider flag #756
[ENG-4460] Toggle assertions based on preprint-provider flag #756
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A real fix would be to make two separate test cases for the PreprintProver.assertionsEnabled
flag turned on and off, but I can't seem to get the changes in my preprint-provider factory in eosf to show up here :/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this still true that you can't get the changes to show?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not getting the changes to show, but I can just hack it with something like ctrl.set('selectedProvider', { assertionsEnabled: true });
so I'm adding a couple tests that do that.
@@ -26,7 +26,7 @@ | |||
"coveralls": "cat ./coverage/lcov.info | coveralls" | |||
}, | |||
"devDependencies": { | |||
"@centerforopenscience/ember-osf": "https://github.com/CenterForOpenScience/ember-osf.git#v0.36.0", | |||
"@centerforopenscience/ember-osf": "https://github.com/CenterForOpenScience/ember-osf.git#feature\/custom-preprint-citation", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note to self: make sure this is updated on release
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved except for the pointing to a feature branch of ember-osf and mayyybe updating the test if you've figured out your problems there.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this still true that you can't get the changes to show?
2d8fe52
into
CenterForOpenScience:feature/provider-defaults
* Toggle assertions based on preprint-provider flag * Update test * Point package.json to eosf feature branch temporarily * Add tests for assertionsEnabled
* [ENG-4460] Toggle assertions based on preprint-provider flag (#756) * Toggle assertions based on preprint-provider flag * Update test * Point package.json to eosf feature branch temporarily * Add tests for assertionsEnabled * Update yarn.lock (#757) * [ENG-4585] Remove Chronos (#759) * remove chronos * remove styles and translations --------- Co-authored-by: Yuhuai Liu <yuhuai@cos.io>
Purpose
assertions_enabled
)Summary of Changes/Side Effects
assertionsEnabled
flag tosubmit
page controllerTesting Notes
assertions_enabled
flag on the preprint_provider page in the admin appassertions_enabled
does not control whether we show/hide COI and/or Author Assertions on the preprint-detail page (e.g. osf.io/preprints//), so if a preprint is submitted with COI or Author Assertions, it will show up on the detail page regardless of theassertions_enabled
flag on the providerTicket
https://openscience.atlassian.net/browse/ENG-4460
Notes for Reviewer
assertionsEnabled
flag to the preprint-provider modelReviewer Checklist
CHANGELOG.md