This PR introduces a "copy full path" feature for the httpendpoint activity in Elsa #133 , utilizing the MudExtension component to enable start and end adornments. This feature has been integrated into the SingleLineComponent, allowing it to be toggled on or off through a flag in elsa-core. Currently, the Blazor text field has a limitation where both start and end adornments cannot be added to the same component, an issue acknowledged in the MudBlazor repository (Issue #8945).
Key Points of this PR:
Leverages MudExtension to support both start and end adornments.
Adds a copy icon as an end adornment, with the flexibility to support more adornments in the future.
Integrates the feature into the SingleLineComponent with a toggle flag in elsa-core.
Please note a side effect: the placeholder text appears at the top of the textbox rather than centered, due to both adornment slots being added by default.
I believe this enhancement adds valuable functionality, but I would appreciate your feedback on whether this approach aligns with the project’s goals and standards. As this is my first PR for this library, look forward to future contributions. I welcome any suggestions or modifications to improve this implementation.
This PR introduces a "copy full path" feature for the
httpendpoint
activity in Elsa #133 , utilizing theMudExtension
component to enable start and end adornments. This feature has been integrated into theSingleLineComponent
, allowing it to be toggled on or off through a flag in elsa-core. Currently, the Blazor text field has a limitation where both start and end adornments cannot be added to the same component, an issue acknowledged in the MudBlazor repository (Issue #8945).Key Points of this PR:
MudExtension
to support both start and end adornments.SingleLineComponent
with a toggle flag in elsa-core.Please note a side effect: the placeholder text appears at the top of the textbox rather than centered, due to both adornment slots being added by default.
I believe this enhancement adds valuable functionality, but I would appreciate your feedback on whether this approach aligns with the project’s goals and standards. As this is my first PR for this library, look forward to future contributions. I welcome any suggestions or modifications to improve this implementation.
Note: After Elsa-core PR - https://github.com/elsa-workflows/elsa-core/pull/6037 merges the api-client lib version need to be updated in elsa-studio