Closed lylest closed 6 months ago
Thanks for raising this, but I don't think documenting this is something that this package should be responsible for to be honest. As you can see when you look at the example, saving the image (and generally any interaction with the signature data) is something that is completely offloaded to the underlying signature pad instance. This package is merely a simple React wrapper around the original signature pad package.
So I'd suggest perhaps raising an issue at the signature pad repository if you feel that documentation around the saving of signature data to an image file is unclear or insufficient.
This issue raise the need to provide more documentation and real world use case of saving the Generated signature into SVG or PNG, The current document documentation is very insufficient and does not well explain how to use this in real world solution, it is just a pieces of cropped code which does not do a good job in explaining the actual usage, Please someone have a look at this