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

rename user property on github-release to author #138

Merged
merged 1 commit into from
Feb 12, 2018
Merged

Conversation

Dhaulagiri
Copy link
Collaborator

better matches what the api calls this

Fixes #113

better matches what the api calls this
user: belongsTo('github-user', { inverse: null }),
author: belongsTo('github-user', { inverse: null }),
user: computed(function() {
deprecate('The user property on the github-release model has been deprecated. Please use the author property.', false, { id: 'ember-data-github.release-author', until: '1.0.0' });
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@elwayman02 I had a thought that we could do something like this for renaming these properties in a backwards compatible way. If you like this I could go back and do this for those other props I renamed as well. Or we can just move forward knowing we have some minor breaking changes.

screen shot 2018-02-12 at 07 54 04

Copy link
Owner

Choose a reason for hiding this comment

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

Yea this seems like a fine way to being able to release these changes in advance. Then for v1.0 we can remove the backwards-compatible stuff.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Perfect, I'll make another PR this week to re-add the properties I removed and deprecate them

@Dhaulagiri Dhaulagiri merged commit f6c3f2a into master Feb 12, 2018
@Dhaulagiri Dhaulagiri deleted the br-release branch February 12, 2018 22:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants