Skip to content

Conversation

@signekb
Copy link
Member

@signekb signekb commented Oct 1, 2025

Description

Closes #88

Needs an in-depth review.

Afterthought: Could we call "jsonpath" "field" instead to make it even simpler? Bc it's a JSON path to a specific field?

Checklist

  • Formatted Markdown
  • Ran just run-all

@signekb signekb moved this from Todo to In Review in Iteration planning Oct 1, 2025
@signekb signekb mentioned this pull request Oct 1, 2025
1 task
Copy link
Contributor

@martonvago martonvago left a comment

Choose a reason for hiding this comment

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

Nice, just very minor comments!

The 2 cons I can think of about calling it field:

  • Doesn't express clearly that it has to be in JSON path notation
  • One JSON path can correspond to multiple fields (e.g. you can target the name of all resources or all properties of a particular resource). Maybe this is not captured by just field?

express the location of the field or fields in [JSON
path](https://en.wikipedia.org/wiki/JSONPath) notation and define an
`Exclude` object with this `target`. For example, you can exclude all
`Exclude` object with the `jsonpath`. For example, you can exclude all
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
`Exclude` object with the `jsonpath`. For example, you can exclude all
`Exclude` object with this `jsonpath`. For example, you can exclude all

This sounds better to me, but 🤷

Copy link
Member Author

Choose a reason for hiding this comment

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

I've rewritten the sentence a bit now. Let me know what you think.

@github-project-automation github-project-automation bot moved this from In Review to In Progress in Iteration planning Oct 1, 2025
@signekb signekb requested a review from martonvago October 1, 2025 16:07
@signekb signekb moved this from In Progress to In Review in Iteration planning Oct 1, 2025
Copy link
Member

@lwjohnst86 lwjohnst86 left a comment

Choose a reason for hiding this comment

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

🎉 Nice! I'll update my PR after merging this 😁

@lwjohnst86 lwjohnst86 merged commit ee1f571 into main Oct 1, 2025
6 checks passed
@lwjohnst86 lwjohnst86 deleted the refactor/rename-target-and-location-to-jsonpath branch October 1, 2025 16:52
@github-project-automation github-project-automation bot moved this from In Review to Done in Iteration planning Oct 1, 2025
lwjohnst86 pushed a commit that referenced this pull request Oct 6, 2025
# Description

Based on a comment in #89 that this needs to be updated.

Needs a quick review.

## Checklist

- [X] Ran `just run-all`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

Refactor to call jsonpath, not target or location

4 participants