Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

[CHORE] why UpdateRouteTable add UnchangedTriggers #6286

Closed
bxjg1987 opened this issue Jan 12, 2025 · 0 comments
Closed

[CHORE] why UpdateRouteTable add UnchangedTriggers #6286

bxjg1987 opened this issue Jan 12, 2025 · 0 comments
Labels
maintenance This issue is about maintenance of the code base and related aspects

Comments

@bxjg1987
Copy link

UpdateRouteTable.HandleAsync(WorkflowTriggersIndexed notification, CancellationToken cancellationToken)
await routeTableUpdater.AddRoutesAsync(notification.IndexedWorkflowTriggers.UnchangedTriggers, cancellationToken);

but why add UnchangedTriggers?

@bxjg1987 bxjg1987 added the maintenance This issue is about maintenance of the code base and related aspects label Jan 12, 2025
@bxjg1987 bxjg1987 changed the title [CHORE] why UpdateRouteTable AddRoutesAsync(notification.IndexedWorkflowTriggers.UnchangedTriggers.. [CHORE] why UpdateRouteTable add UnchangedTriggers Jan 12, 2025
@elsa-workflows elsa-workflows locked and limited conversation to collaborators Jan 14, 2025
@sfmskywalker sfmskywalker converted this issue into discussion #6298 Jan 14, 2025

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
maintenance This issue is about maintenance of the code base and related aspects
Projects
None yet
Development

No branches or pull requests

1 participant