Files
tasks/chasm/workflow.go
Yichao YangandGitHub bd90fe6f8d CHASM: Store component and task type ID instead of name (#8588)
## What changed?
- Introduce typeID for registered CHASM components and tasks
- In longer term the relationship between component/task name and ID
should be persisted (similar to namespace)

## Why?
- Store less data
- Decouple user visible name from internal implementation, making it
possible in the future to rename components/tasks
- Required for separate ID space work, where archetype information needs
to be stored in all history tasks as well.

## How did you test it?
- [x] built
- [ ] run locally and tested manually
- [x] covered by existing tests
- [ ] added new unit test(s)
- [ ] added new functional test(s)
2025-11-18 21:59:55 -08:00

12 lines
273 B
Go

package chasm
const (
WorkflowLibraryName = "workflow"
WorkflowComponentName = "workflow"
)
var (
WorkflowArchetype = Archetype(fullyQualifiedName(WorkflowLibraryName, WorkflowComponentName))
WorkflowArchetypeID = ArchetypeID(generateTypeID(WorkflowArchetype))
)