always use single dot fieldpath notation #261
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This patch completes earlier work that was done in the
pkg/fieldpathpackage that only uses a single dot notation to refer to a field with
type list or map within a field path.
We previously were using a double dot in field paths in
generator.yamlconfig files to refer to fields of type list or map. This was erroneous,
since referring to the field (not the value of the field) only
requires a single dot in order for the fieldpath to "locate" a field
within a path.
In this PR, we simplify and DRY up the inference code in
pkg/model/model.go's processing of "nested fields" so that the fieldpath added for all Field objects uses this single-dot notation only.
Signed-off-by: Jay Pipes jaypipes@gmail.com
By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache 2.0 license.