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

Don't require a leading dot for JSON field paths #345

Merged
merged 1 commit into from
Apr 3, 2020

Conversation

negz
Copy link
Contributor

@negz negz commented Mar 28, 2020

@hongchaodeng
Copy link
Member

Ref #335

If this is a written k8s convention, we should follow and add a line in the spec. Also need to update examples and design doc.

@negz
Copy link
Contributor Author

negz commented Apr 3, 2020

Ping. Does this seem uncontroversial enough to merge?

Copy link
Contributor

@hasheddan hasheddan left a comment

Choose a reason for hiding this comment

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

@hongchaodeng I am happy to follow this with any clean-up that needs to happen in the docs 👍

@resouer
Copy link
Member

resouer commented Apr 3, 2020

/lgtm

This one is good enough to merge. Thorough fix could be done by follow up PRs.

@resouer resouer merged commit 92559e3 into oam-dev:1.0.0-alpha2 Apr 3, 2020
@hongchaodeng
Copy link
Member

@hasheddan
Note that this is NOT merged into master branch.
Just combine this commit in your follow up PRs.

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.

4 participants