-
Notifications
You must be signed in to change notification settings - Fork 7
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
Add a parameters map to p:uuid? #587
Comments
I thought that "the mechanism" refers to some type of configuration, or an extension attribute. |
ndw
added a commit
to ndw/steps
that referenced
this issue
Jul 31, 2024
ndw
added a commit
to ndw/steps
that referenced
this issue
Jul 31, 2024
ndw
added a commit
to ndw/steps
that referenced
this issue
Jul 31, 2024
ndw
added a commit
to ndw/steps
that referenced
this issue
Aug 1, 2024
ndw
added a commit
to ndw/steps
that referenced
this issue
Aug 1, 2024
ndw
added a commit
to ndw/steps
that referenced
this issue
Aug 1, 2024
ndw
added a commit
to ndw/steps
that referenced
this issue
Aug 1, 2024
ndw
added a commit
to ndw/steps
that referenced
this issue
Aug 2, 2024
ndw
added a commit
to ndw/steps
that referenced
this issue
Aug 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It strikes me as slightly weird that the
p:uuid
step says:Wouldn't it make sense to add a
parameters
map option so that there's a place to provide the necessary inputs? Implementors could use extension attributes or something, I suppose, but it seems like there's plenty of precedent for having aparameters
map for this purpose...The text was updated successfully, but these errors were encountered: