404labfr / 404labfr/nova-signature
Losing the signature when updating resource
- Dominant language
- Vue
- Stars
- 14
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
If I update resource without clicking in the "attach" button I will lose the previous data(lost signature).
Also the "saveOnChanges()" won't help unless you sign again.
I notice when updating the resource the (textarea for the signature) will give you a default value, that is a transparent background. example below. And that is the data that get saved in the DB.
What I'm looking for here is just when saving the resource keep the same signature with out clinking in the attach button.
data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAYwAAACUCAYAAACAyx4IAAAA+klEQVR4nO3BMQEAAADCoPVPbQdvoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAeA2UgQABdXK3UQAAAABJRU5ErkJggg==
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue is about a Vue component in a Laravel Nova field. Look at the signature field's frontend code, likely in a Vue file, where the textarea with the signature data is handled. The bug is that on update, the signature data is replaced with a default transparent image unless the 'attach' button is clicked. Examine the saveOnChanges method and the update flow to see where the previous signature value is lost. Check how the component's state is managed during resource updates.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100