-
Notifications
You must be signed in to change notification settings - Fork 0
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
Reference local field #30
Labels
Comments
MrSwitch
added a commit
that referenced
this issue
Aug 6, 2019
MrSwitch
added a commit
that referenced
this issue
Aug 6, 2019
MrSwitch
added a commit
that referenced
this issue
Aug 6, 2019
MrSwitch
added a commit
that referenced
this issue
Aug 6, 2019
MrSwitch
added a commit
that referenced
this issue
Aug 6, 2019
MrSwitch
added a commit
that referenced
this issue
Aug 6, 2019
MrSwitch
added a commit
that referenced
this issue
Aug 7, 2019
MrSwitch
added a commit
that referenced
this issue
Aug 7, 2019
MrSwitch
added a commit
that referenced
this issue
Aug 7, 2019
MrSwitch
added a commit
that referenced
this issue
Aug 7, 2019
MrSwitch
added a commit
that referenced
this issue
Aug 7, 2019
MrSwitch
added a commit
that referenced
this issue
Aug 7, 2019
MrSwitch
added a commit
that referenced
this issue
Aug 7, 2019
* feat(field_alias): Map field aliases to data in get request, #30 * feat(field_alias): Map field aliases to data in patch request, #30 * feat(field_alias): Map field aliases to data in 'del' request, #30 * feat(field_alias): Map field aliases to data in 'dare.post' request, #30 * spec(field_alias): update get spec, #30 * fix(field_alias): fix aliasing references, #30 * docs(field-alias): update field alias docs, #30 * refactor(field-alias): rename spec file, #30 * refactor(field-alias): standardize getting field attributes, #30 * fix(field-alias): ensure that join detection does not use the field alias, #30 * refactor(field-alias): tidy based on feedback, #30 * refactor(field-alias): tidy based on @cboyce183 feedback, #30
🎉 This issue has been resolved in version 0.32.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Map to another field, much like a table relationship without prefixing the table. i.e.
In this example requesting the "name" would map to the "displayName" field, aka...
Usecase: If a field has been renamed it's nice to still support the old name for a while. It's already possible to do this with Generated fields within a
dare.get
however that is rather cumbersome.The text was updated successfully, but these errors were encountered: