@ljmotta hi, thank you, I would like to ask about the command name:

• will it be somehow clear it is a command that belongs to KIE VSCode extension? I mean some prefix maybe? 'KIE: ....' ?
• is there a reason the command name dos not contain keywords like 'jbpm', 'bpmn', 'workflow', is that because it may be used for generating forms of 'anything'

I do not have a strong opinion about the points I bring. I am probably fine if we do not change the name. However, sharing the fact, that me, I would try to search in list of VSCode commands by keywords mention in first or second point.

@jomarko I understand what you mean. I was relying on a prefix to give the context of the command, as you're right, the form code generation is exclusively for workflow projects. I just checked, and all our KIE VS Code extensions doesn't use a prefix, which is a common approach across other community extensions (e.g. Prettier, Go, TypeScript, ESLint, etc...). For this case, I'll add the prefix to the BPMN VS Code using its extension name (KIE BPMN Editor), and we should create a separated issue to tackle this on other extensions.

Now, with the prefix in place, the current command name would be: KIE BPMN Editor: Generate form code for human interactions, and I guess you're right too to include de jbpm as we need to use the compiled JSON Schemas. Maybe KIE BPMN Editor: Generate form code for human interactions from jBPM project. WDYT?

@ljmotta thank you, the last proposal KIE BPMN Editor: Generate form code for human interactions from jBPM project sounds to me quite long. I mean, would it fit the menu [1]? However, I am not an expert in other extension commands, maybe it is totally common to use also long command name. I like the proposal to contain a lot of information, what the command actually does and if it fits the menu [1], then I am fine with it.

For example, Devbox: Generate a Dockerfile from devbox.json is 46 characters long while KIE BPMN Editor: Generate form code for human interactions from jBPM project is 76 characters long.

[1]

Hi @ljmotta

Sorry if this is not the best place to expose this. I was wondering if the scope of this issue might reach DMN too in some way.

I've seen many DMN developers using VS Code, most of them not very skilled from a technical point of view (poor knowledge on Java, Maven, OpenAPI...) and there's something they've been missing: user-friendly forms to test both DMN models and individual decision nodes.

Do you think that this initiative could also be applied to DMN?

Best regards,

Jaime

@jomarko The extension name is Apache KIE™ BPMN Editor. The command with the extension name as prefix was trimmed down as we can see in the image below:

Shortening it to BPMN Editor fits well:

As Apache KIE™ BPMN Editor can be too long for a command prefix, I think it's harmless to left as BPMN Editor.

@jaimeizuz Hi! Sorry for the late response.

Could you please create a separate issue for DMN? We would need to make this feature from scratch. The BPMN form code generation already existed as a CLI tool which is being moved to the BPMN VS Code extension.

@ljmotta thank you for the screenshot, I agree with your shortening.