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

Do not require a leading dot for JSON field paths #347

Merged
merged 2 commits into from
Apr 24, 2020

Conversation

hasheddan
Copy link
Contributor

This cherry-picks 72eecb6 from the 1.0.0-alpha2 branch and updates all documentation and examples to reflect the removal of the leading dot from JSON field paths.

Ref: #345

negz and others added 2 commits April 5, 2020 14:21
… fieldPaths

This ensures that all examples and documentation
reflect the current status of the OAM spec
following the removal of the leading dot from
field paths in order to leverage existing
Kubernetes libraries.

Signed-off-by: hasheddan <[email protected]>
@msftclas
Copy link

msftclas commented Apr 5, 2020

CLA assistant check
All CLA requirements met.

Comment on lines +208 to +209
1. Embed a valid OAM workload kind under its `spec.workload` field.
2. Publish a set of parameters under its `spec.parameters` field. Parameters may
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Note: these updates are not strictly needed here, but I thought it would be a good idea to mirror the convention we are standardizing on for JSON field paths.

@hasheddan
Copy link
Contributor Author

@wonderflow can this be merged?

@resouer
Copy link
Member

resouer commented Apr 24, 2020

Yes, LGTM, sorry for missed this one!

We also need to check implementation side carefully for this change.

@resouer resouer merged commit 1d12986 into oam-dev:master Apr 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants