saade / filament-autograph Goto Github PK

What happened?

I would like to return the signature data drawn. However, afterStateUpdated is not working. Is there some way that I can make this?

How to reproduce the bug

Method afterStateUpdated is not working.

Package Version

^3.0

PHP Version

8.2.0

Laravel Version

10.0.0

Which operating systems does with happen with?

Windows

Notes

No response

What happened?

When using the autograph field inside a table repeater, the lines you draw, get an offset to the right (so the line you draw, is not exactly where you draw it)

How to reproduce the bug

In this video, I have 2 autograph fields. 1 in a normal form, below that, inside a repeater. You can spot the differences here.

Package Version

3.0

PHP Version

8.2

Laravel Version

10.0

Which operating systems does with happen with?

macOS, Windows, Linux

Notes

No response

What happened?

Is their any way to save the signature in to database

How to reproduce the bug

I'm trying every possible way i know to save the signature

Package Version

2.0.0

PHP Version

8.2.0

Laravel Version

10.0.0

Which operating systems does with happen with?

Linux

Notes

No response

What happened?

When i draw something and save as file directly, everything works ok, but when you save it in the database and open the record again, it shows correctly, but when you save it as file there is no line anymore. In my case i used it for a signature, but the signature is not visible anymore

How to reproduce the bug

• Add the signatur to a filament form
• load the form on your website and sign
• save the form
• open the form again
• save as jpg / png / svg
• open the saved file
• you see a empty image

Package Version

3.0.0

PHP Version

8.2.8

Laravel Version

10.19.0

Which operating systems does with happen with?

Windows

Notes

No response

What happened?

Maybe I'm missing something, but is the intention that the signature will persist in the database? Not seeing this behavior. If I draw a signature and save the form, nothing is written and the signature is lost if I refresh the page...

How to reproduce the bug

Install filament-autograph, add SignaturePad::make('signature') to resource form, draw signature & save resource.

Package Version

3.0

PHP Version

8.2

Laravel Version

10.0

Which operating systems does with happen with?

No response

Notes

No response

What happened?

I'm trying to load an image from the database and update $this->data, but nothing is happening.

How to reproduce the bug

The field is mounted with some image with $this->form->fill()
Then a button trigger a method to load different values in the fields, updating $this->data. It works fine for all the fields (Toggle) except SignaturePad.

Package Version

3.0.2

PHP Version

8.2

Laravel Version

10.43.0

Which operating systems does with happen with?

macOS

Notes

public function selectExistingSignature($autographId)
    {
        $autograph = Autograph::find($autographId);

        if ($autograph) {
            $this->data['autograph'] = $autograph->image;
        }
    }

What happened?

If I save a signature in dark mode and then change to light mode, the signature is barely visible because it is displayed with the color used in dark mode.

How to reproduce the bug

Save signature in dark mode and change to ligt mode to edit or show.

Package Version

3.0.0

PHP Version

8.2.11

Laravel Version

10.26.2

Which operating systems does with happen with?

Windows, Linux

Notes

No response

What happened?

Hello,

The composer require saade/filament-autograph command fails with Laravel 11:

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires saade/filament-autograph ^3.0 -> satisfiable by saade/filament-autograph[v3.0.0, v3.0.1, v3.0.2].
    - saade/filament-autograph[v3.0.0, ..., v3.0.2] require illuminate/contracts ^10.0 -> found illuminate/contracts[v10.0.0, ..., v10.48.4] but these were not loaded, likely because it conflicts with another require.


Installation failed, reverting ./composer.json and ./composer.lock to their original content.

As far I as I can tell, this is because the package requires only the version 10 for illuminate/contracts.

In the composer.json file, I suppose the illuminate/contracts ^10.0 (line 26) sould be changed to illuminate/contracts ^10.0|^11.0.

I would love to make a PR to propose this change but I am not enough experienced with Git/GitHub to do it...

@saade, could you please have a look?

How to reproduce the bug

Try to install on a fresh Laravel 11 / Filament 3 project.

Package Version

3.0

PHP Version

8.3

Laravel Version

11.1

Which operating systems does with happen with?

macOS

Notes

No response

What happened?

Added a table action which opens a form in a modal containing signature pad component

How to reproduce the bug

Tables\Actions\Action::make('sign') ->form([ SignaturePad::make('signature'), ]) ->action(function (array $data, User $record): void { dd($data, $record); $record->save(); }),

Package Version

3.0.0

PHP Version

8.2.0

Laravel Version

10

Which operating systems does with happen with?

Linux

Notes

Only tried on linux but i guess should happen other systems too.

What happened?

It doesn't work in a relationship manager form.

How to reproduce the bug

create a relation manager and add SignaturePad to form

Package Version

3.0.0

PHP Version

8.2.11

Laravel Version

10.26.2

Which operating systems does with happen with?

Windows, Linux

Notes

No response