Skip to content

feat: update resource_request schema to require only one of resourceType and resourceName#75

Open
akryukov378 wants to merge 1 commit into
mainfrom
feature/resource-request-schema-update
Open

feat: update resource_request schema to require only one of resourceType and resourceName#75
akryukov378 wants to merge 1 commit into
mainfrom
feature/resource-request-schema-update

Conversation

@akryukov378

Copy link
Copy Markdown
Collaborator
  • Es wurde eine oneOf-Einschränkung hinzugefügt, um sicherzustellen, dass genau eines der Felder resourceType oder resourceName vorhanden ist.
  • Das Beispiel wurde aktualisiert, um beide gültigen Muster zu veranschaulichen.
  • resourceRequestId bleibt für alle Ressourcenanfragen obligatorisch.

…ype or resourceName

- Changed required fields from both resourceType and resourceName to just resourceRequestId
- Added oneOf constraint to ensure exactly one of resourceType or resourceName is present
- Updated example to demonstrate both valid patterns
- resourceRequestId remains mandatory for all resource requests
"oneOf": [
{
"required": ["resourceType"],
"not": {

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

@mjoerg78 ist "not required" nicht überflüssig? Das bedeutet optional, was ohnehin default ist.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Auf der anderen Seite habe ich mir kurz überlegt - anscheinend ist es gar nicht möglich die "genau eines"-Semantik zu erzwingen. Ich versuche noch zu experimentieren.

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