elsa-workflows / elsa-workflows/elsa-core

[Elsa V3] Mass Transit. Allow registering a different endpoint name formatter

Open
#4,396 0 comments 1 reaction 0 assignees View on GitHub
elsa 3 enhancement triaged
Dominant language
C#
Stars
7.9k
Forks
1.5k
Avg merge
15h 22m
Merged PRs (30d)
114

Description

Currently Elsa's Mass Transit feature registers the `KebabEndpointNameFormatter` by default without any way to configure this on the user's end. Some setups we have uses different endpoint naming conventions and adds prefixes to differentiate non production environments. It'd be great if we could also configure this on the user's end as Mass Transit only allows configuring this once.

Implementation Line here:

https://github.com/elsa-workflows/elsa-core/blob/6cd3bd2d618fbc9ab739071f4d976c0a5c5938f1/src/modules/Elsa.MassTransit/Features/MassTransitFeature.cs#L88C13-L88C53

Current workaround involves registering the `IEndpointNameFormatter` as a singleton service well in advance before calling `elsa.UseMassTransit` so it takes priority over the call on the integration side.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.