Skip to content

Conversation

@abought
Copy link
Contributor

@abought abought commented May 10, 2016

Ticket

https://openscience.atlassian.net/browse/EOSF-3

Purpose

Start work on serializing data to send to server

Notes for Reviewers

  • Some "send to server" actions may be incomplete, but posting this for visibility and to avoid rework.
  • Feedback on tests is welcome; I think the extractAttributes test could be more elegant than it is
  • Worth giving a try in the browser to be sure that I got rid of all experiments

This PR had some trial and error; it's a good candidate for "merge and squash"

Routes Added/Updated

  • Add an "edit title" box to node detail page, to test writing to server
  • Add a placeholder action for later work on "create node" button

Blockers/ TODO

  • Remove unused uri templates packages
  • remove extraneous fields from payload and resolve 500 server errors

@abought abought changed the title [WIP] Serializer and adapter cleanup Serializer and adapter cleanup May 10, 2016
accessToken = config.OSF.accessToken;
} else {
// Acquire an OSF access token, then exchange it for a Jam token
// Acquire an OSF access token, then exchange it for a Jam token // TODO: Jam?
Copy link
Contributor

Choose a reason for hiding this comment

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

Shameless copy/paste. Will remove during merge.

@samchrisinger samchrisinger merged commit dc60e1f into CenterForOpenScience:develop May 11, 2016
ENV.OSF.apiUrl = 'https://staging2-api.osf.io';
ENV.OSF.authUrl = 'https://staging2-accounts.osf.io/oauth2/authorize';
}
if (BACKEND === 'prod') {
Copy link
Contributor

Choose a reason for hiding this comment

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

Probably shouldn't condone using prod as a backend for local development. If a dev needs a prod-like backend, they should use test.osf.io.

Copy link
Contributor

Choose a reason for hiding this comment

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

@sloria agreed, and I am trying to get the README to reflect this (we can be more explicit too), but the code should not assume that it's never being run in production.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Adding support for the test backend got lost in the shuffle, but I agree it should be added for use by third-party integrators. Thanks for the reminder!

Presumably, prod is kept for use in deployment.

Copy link
Contributor

Choose a reason for hiding this comment

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

@samchrisinger As discussed in our other thread, envvars should be used for production and any non-local deploys.

aaxelb added a commit that referenced this pull request Oct 23, 2017
* [Feature] Update for reviews (#2)

* Update models for reviews API
* ReviewLog adapter and serializer
* Fix log creator model

* [Feature] Include reviewable when creating review logs (#3)

* Include reviewable when creating review logs

* Add title/contributors fields to preprint model

* Clean up serializing relationships

* Add dateLastTransitioned to preprint model (#5)

* [Fix] Only fetch the logged in user once

* Allow reviews settings to be nullable

* Fix infinite authentication

* Add support for using query parameters in findRecord

* [Fix] Use `getRecords()` instead of `.record` (#8)

* Tweaks and updates for reviews

* Fix typo

* [Feature][MOD-73] Rename log to action (minimal branch) (#2)

* Rename `review-log` to `action`

* plac8 flake8

* Fix test errors

* [MOD-72][Feature] Add "My Reviews" for users with view_submissions permission

* Add actions property to user model

* Add `user` property to current-user instead

* Add DOI alias properties to preprint model

* Fix permissions check in navbar (#6)

* Only serialize actually dirty relationships

* Wait for currentUser.user to resolve (#8)

* [Feature][MOD-111] Add preprint" button direct to the current provider's add page (#11)

* Apply requested changes

* rename

* Apply requested changes

* Fix

* minor change

* Apply requested change

* Restore comment

* Update search link

* Use forked/fixed ember-data-has-many-query

* Update ember-data-has-many-query dependency

* Revert to non-forked ember-data-has-many-query

* Update CHANGELOG
aaxelb pushed a commit that referenced this pull request Oct 26, 2017
…r's add page (#11)

* Apply requested changes

* rename

* Apply requested changes

* Fix

* minor change

* Apply requested change

* Restore comment

* Update search link
fabmiz pushed a commit that referenced this pull request Jul 17, 2020
…1.0.12

chore(deps): [security] bump fstream from 1.0.11 to 1.0.12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants