Skip to content

refactor(codegen)!: resolve misleading and clashing generated names - #132

Merged
emaarco merged 1 commit into
mainfrom
emaarco/check-issue-120-relevance
Sep 29, 2026
Merged

emaarco merged 1 commit into
mainfrom
emaarco/check-issue-120-relevance

Conversation

@emaarco

@emaarco emaarco commented Sep 29, 2026

Copy link
Copy Markdown
Member

Closes #120

What

  • Flow → FlowNodes (Kotlin, Java, C#), so it no longer clashes with kotlinx.coroutines.flow.Flow
  • Shared constants drop a leading prefix matching their holder: Messages.MESSAGE_FORM_SUBMITTED → Messages.FORM_SUBMITTED (kept when nothing valid remains)
  • Errors/escalations are named after their name only, without the code. The same name with different codes now fails shared-definition-collision, so constant names never depend on other models
  • Runtime BpmnError / BpmnEscalation → BpmnErrorDefinition / BpmnEscalationDefinition, avoiding clashes with the engines' BpmnError
  • ServiceTasks stays as is (see issue comment)

C# member names of shared definitions are now derived from the constant name instead of the raw name, so the prefix stripping applies there too.

Breaking

Yes — lands before 6.0.0 (#88). The v6 migration guide, generated-api docs and the migration skill are updated.

Rename Flow to FlowNodes, drop the kind prefix and the code suffix from
shared constants, and rename the runtime BpmnError/BpmnEscalation to
BpmnErrorDefinition/BpmnEscalationDefinition.

Refs #120
@emaarco
emaarco enabled auto-merge (squash) September 29, 2026 09:12
@emaarco emaarco self-assigned this Sep 29, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Test Coverage

Module Line Coverage
bpmn-to-code-core 98.0% (2891/2949 lines)
bpmn-to-code-gradle 24.8% (29/117 lines)
bpmn-to-code-maven 62.2% (28/45 lines)
bpmn-to-code-web 96.1% (222/231 lines)
bpmn-to-code-testing 97.2% (175/180 lines)
bpmn-to-code-runtime 99.3% (140/141 lines)

@emaarco
emaarco disabled auto-merge September 29, 2026 09:16
@emaarco
emaarco merged commit 658b98b into main Sep 29, 2026
5 checks passed
@emaarco
emaarco deleted the emaarco/check-issue-120-relevance branch September 29, 2026 09:16
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.

[Refactor]: Resolve misleading and clashing generated names

1 participant