We need to add a @workflow TypeScript annotation that can be added to any TypeScript class. This annotation should require a fully qualified name (FQN) in the format {nameSpace}.{name}@{version}. The class should be registered in the workflow registry during system startup.
Acceptance Criteria:
The @workflow annotation can be added to any TypeScript class.
The annotation requires a FQN in the specified format.
The class is registered in the workflow registry during system startup.
Proper error handling is in place for incorrect FQN formats and failed registrations.
Sub-Tasks:
Research how to implement custom TypeScript annotations.
Implement the @workflow annotation in a feature branch.
Write unit and integration tests for the annotation.
Test the annotation and the registration process.
Review and merge the feature branch into the main branch.
Update internal and user-facing documentation to reflect the new annotation.
Suggested Solutions:
Use Decorators: TypeScript supports decorators, which can be used to create the @workflow annotation.
Use Reflection: You could use reflection to get the metadata of the class during system startup and register it in the workflow registry.
Use a Library: Consider using a library like reflect-metadata to simplify the implementation.
We need to add a
@workflowTypeScript annotation that can be added to any TypeScript class. This annotation should require a fully qualified name (FQN) in the format{nameSpace}.{name}@{version}. The class should be registered in the workflow registry during system startup.Acceptance Criteria:
@workflowannotation can be added to any TypeScript class.Sub-Tasks:
@workflowannotation in a feature branch.Suggested Solutions:
@workflowannotation.reflect-metadatato simplify the implementation.