Skip to content

clarify that field names can be prefixed with properties or not#2

Merged
philvarner merged 2 commits into
mainfrom
pv/fields-names-semantics
Oct 12, 2022
Merged

clarify that field names can be prefixed with properties or not#2
philvarner merged 2 commits into
mainfrom
pv/fields-names-semantics

Conversation

@philvarner
Copy link
Copy Markdown
Contributor

Related Issue(s):

Proposed Changes:

  1. Clarify that implementers decide if field names need to be prefixed with properties or not

PR Checklist:

  • This PR has no breaking changes.
  • I have added my changes to the CHANGELOG or a CHANGELOG entry is not required.

@philvarner philvarner requested a review from m-mohr October 6, 2022 12:39
@m-mohr
Copy link
Copy Markdown
Contributor

m-mohr commented Oct 10, 2022

Should we say that a /queryables implementation would be helpful nevertheless? Otherwise, LGTM.

@philvarner
Copy link
Copy Markdown
Contributor Author

Should we say that a /queryables implementation would be helpful nevertheless? Otherwise, LGTM.

I was thinking we would define a /fieldable (includable? something like that) endpoint that is optional to implement, but not for rc.2. maybe for 1.1

@philvarner philvarner merged commit c9d6b27 into main Oct 12, 2022
@philvarner philvarner deleted the pv/fields-names-semantics branch October 12, 2022 00:28
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.

2 participants