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

JSON Pointer syntax works for 'CompareProperty' but not 'UseCaseKeyProperty' #179

Open
linchrislin opened this issue Sep 27, 2023 · 2 comments

Comments

@linchrislin
Copy link

linchrislin commented Sep 27, 2023

Practiced 2 profiles with JSON pointer applied to CompareProperty of ConditionalRequirements in one profile and UseCaseKeyProperty of UseCases in another. Running the 2 profiles with same resource payload, the out log is as expectation for the Conditional implementation, but looks strange for the UseCase implementation.

Plz have profiles / payload / out-logs in JptrTests.zip

@mraineri
Copy link
Contributor

The spec actually doesn't call out the usage of JSON pointers for UseCaseKeyProperty today; normally when JSON pointers are allowed, we specify that directly in the definition of the property. For example, we have this defined for "CompareProperty":

If the value begins with a / character, the value shall represent an RFC6901-defined JSON Pointer, specifying an explicit path from the root level of the resource to a property within the resource.

But no such text for UseCaseKeyProperty...

@linchrislin
Copy link
Author

Understood it's not stated in the spec and is not supported in present.
It would be helpful when user try to create the use cases of:

  • EmbeddedMemory
  • AbsentDrive
    ..., etc.

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

No branches or pull requests

2 participants