Option to update existing signature box (instead of always creating a new one) #89
Conversation
This file contains 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
ridgey-dev
changed the title
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.
Currently, the package automatically creates a new signature box with a random name for every signature action. This behavior leads to PDFs that contain both the newly created (signed) signature box and the original (unsigned) placeholder, which is not ideal for workflows where maintaining the integrity of pre-existing placeholders is critical.
To address this, I have created this pull request to enable the functionality of updating existing signature boxes instead of creating new ones. This enhancement ensures that the package can effectively handle documents with predefined signature placeholders without introducing redundancies.