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

Element template generator feedback #1797

Open
11 tasks
chillleader opened this issue Jan 24, 2024 · 2 comments
Open
11 tasks

Element template generator feedback #1797

chillleader opened this issue Jan 24, 2024 · 2 comments
Assignees
Labels
kind:enhancement New feature or request

Comments

@chillleader
Copy link
Member

chillleader commented Jan 24, 2024

This issue is a place for general feedback from using one of our element template generators. If you have a small suggestion or a minor bug report, it's a good candidate to be added to this list.

If you have a suggestion, please add a comment below and we'll add it into the list.

Note that the suggestions here should have a limited scope (e.g. add a field to the annotation). All action items here don't have a high priority and will be picked up based on the available capacity. If you have a request with a bigger scope or a high priority, please open a separate issue. If the context is too complex to be expressed in 2 sentences, please open a separate issue as well.

Java annotation-based element template generator

  • Raise a warning/error if @TemplateProperty references a group that is not defined in @ElementTemplate.propertyGroups. Currently such properties are silently ignored.

  • Allow overriding dropdown choice labels by annotating the corresponding enum constants (to avoid a more verbose configuration via @TemplateProperty.dropdownChoices

  • Support language attribute on properties (for example: graphql) for enhanced language support of the code editor: chore(graphql): Use element template generator for GraphQL outbound c… #1903 (comment)

  • based on this support request:

    • it would be great if the files io.camunda.connector.api.outbound.OutboundConnectorFunction and io.camunda.connector.api.inbound.InboundConnectorExecutable under META-INF/services were also generated from the classes listed in connectorClasses. Depending on the connector type, the class name must be written in one of the two files.
    •  Documentation around template generators in our offical documentation page (What is it, when to use it , how to use it, where to find it, what is supported / What not? https://jira.camunda.com/browse/SUPPORT-20138
  • Allow configuring binding name prefix for nested properties

  • Connector generation cannot be started on Windows, probably because we exceed the maximum command line length which is 8191 characters on windows. (when setting the CLASSPATH variable) Probable solution: https://stackoverflow.com/a/52585324/4109477

  • Support the inputDataClass on the OutboundConnector annotation: https://github.com/camunda/team-connectors/issues/959

  • Support generation of constraints based on the input property type (comment below)

ConGen tool / CLI generators - OpenAPI, Postman

  • Support API key authentication for OpenAPI generator
@chillleader chillleader added the kind:enhancement New feature or request label Jan 24, 2024
@chillleader chillleader self-assigned this Jan 24, 2024
@jonathanlukas
Copy link
Contributor

Support generation of constraints based on the input property type.
Example: java.time.LocalDate requires input to match a date regex
Ref: https://camunda.slack.com/archives/C02JLRNQQ05/p1707831194793699

@mattli2024
Copy link

@chillleader - can you review if this is still relevant? thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind:enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants