You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: