Feature: add output events instead of inputs #1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I hope you can help us on this @AlexandrToorchyn |
|
@CharlesElGriego Thanks for the PR |
|
@CharlesElGriego Your improvements have been included in the latest release (v1.0.3) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
We are currently utilizing docuseal-angular in our solution and have encountered an unintended bug. It appears that the events which should be available to the parent component as @outputs() are currently implemented as @inputs().
For instance, we need to trigger a success message when the docuseal-save event returns a 200 status. Unfortunately, under the current setup, we are unable to do so.
Could you please assist us in resolving this issue? Your help would be greatly appreciated.
Best regards,
Charles