-
Notifications
You must be signed in to change notification settings - Fork 120
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
Rename annotations #239
Comments
@falko: Ping - it now exists on master and released as alpha1: https://github.com/camunda-community-hub/spring-zeebe/releases/tag/8.1.0-alpha1 |
maybe a nice to have here would be a new field in |
We discussed this in the past - and so far we decided against it - as I don't see a good reason why the Java variable name has to be different than the process variable name. Actually, it might even easily add confusion. Technically, there would not be a big show stopper though - but as this is an easy addition with a sensible default, we can still ad this whenever we want (whereas we wanted to have the renaming part of the 8.1 release) |
The annotations used in
spring-zeebe
will be renamed, according to our experiences using the library so far. We take the 8.1 release as a good moment in time to make that change.All existing annotations will be deprecated, but keep working for now (and will be removed in a future release).
@ZeebeCustomHeaders
-->@CustomHeaders
@ZeebeDeployment
-->@Deployment
, already deprecated fieldclassPathResources
will be removed in the new annotation@ZeebeVariable
-->@Variable
@ZeebeVariableAsType
-->@VariableAsType
@ZeebeWorker
-->@JobWorker
,autoComplete
default value will be switched from false to true (as we see auto completion as the default to be used in most cases).forceFetchAllVariables
got renamed tofetchAllVariables
.See also #229 for some discussion on this issue
The text was updated successfully, but these errors were encountered: