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

idAttribute of a resource can be a computed property #84

Closed
kenjiqq opened this issue Jun 28, 2014 · 1 comment
Closed

idAttribute of a resource can be a computed property #84

kenjiqq opened this issue Jun 28, 2014 · 1 comment
Assignees
Milestone

Comments

@kenjiqq
Copy link

kenjiqq commented Jun 28, 2014

I know there is an issue about computed properties already, and they way it's supported right now is with the methods field. But it would be sweet would the possibility to use a computed property as the idAttribute for a resource, or maybe a method.

Some APIs i work with do not return a unique id field, their "id" is the combination of two fields(folder + nr in that folder for instance). I guess this would be easier when real computed properties are added.

@jmdobry jmdobry self-assigned this Jun 29, 2014
@jmdobry
Copy link
Member

jmdobry commented Jun 29, 2014

This should be possible with how I'm thinking about doing computed properties.

This issue is dependent on #23.

I won't close it until #23 is closed, but keep it as a reminder to make sure the idAttribute of a resource can be a computed property.

@jmdobry jmdobry changed the title Computed property as resource id idAttribute of a resource can be a computed property Jun 29, 2014
@jmdobry jmdobry changed the title idAttribute of a resource can be a computed property idAttribute of a resource can be a computed property Jun 29, 2014
@jmdobry jmdobry mentioned this issue Jun 29, 2014
9 tasks
@jmdobry jmdobry added this to the 0.10.0 milestone Jun 29, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants