-
Notifications
You must be signed in to change notification settings - Fork 159
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
DXCDT-373: Address notation for keyword preservation #741
DXCDT-373: Address notation for keyword preservation #741
Conversation
Codecov ReportBase: 83.72% // Head: 83.75% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #741 +/- ##
==========================================
+ Coverage 83.72% 83.75% +0.03%
==========================================
Files 115 115
Lines 3403 3422 +19
Branches 634 640 +6
==========================================
+ Hits 2849 2866 +17
Misses 324 324
- Partials 230 232 +2
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
a76e9a6
to
2a23090
Compare
…ps://github.com/auth0/auth0-deploy-cli into DXCDT-373-keyword-preservation-address-notation
🔧 Changes
Building off of the previous few PRs for keyword preservation (#736, #738 , #740), this PR introduces the concept of an "address". An address is a proprietary notation for looking-up properties within an arbitrary data structure, similar to JSON dot notation. The primary difference is the ability to identify array items by a unique field instead of order. What this does is set us up to identify preservable fields in on asset tree and then look-up its value on another asset tree by the address.
Example:
Address for tenant
friendly_name
field:tenant.friendly_name
Address for action
name
field:actions.[name=action-1].name
📚 References
Related Issues:
#328
#688
🔬 Testing
Added and updated unit tests.
📝 Checklist