Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2.1.12 Breaking Changes : TypeError: file.getFileEncodeBase64String is not a function #29

Open
petitchevalroux opened this issue Nov 13, 2023 · 10 comments

Comments

@petitchevalroux
Copy link

file.getFileEncodeBase64String() is not available in 2.1.12

From what I understand the function has been deleted because it should never have been there in the first place. The problem is that we use it.

More context : #3 (comment)

I think version 2.1.12 should therefore be a major release, as it introduces a breaking changes.

Solution : downgrade to 2.1.10

@rikschennink
Copy link
Collaborator

Should be fixed in 2.1.13

@akagamina
Copy link

still getting this error.

@vaclavgreif
Copy link

@rikschennink Also getting this error:

<FilePond
                    allowFileEncode={true}
                    instantUpload={false}
                    files={files}
                    onupdatefiles={files => {
                        setFiles(files);
                    }}

                    allowMultiple={true}
                    name="file"
                    onaddfile={(err, item) => {
                        console.log(item.getFileEncodeBase64String());
                    }}
                    labelIdle='Drag & Drop your files or <span class="filepond--label-action">Browse</span>'
                    onprocessfiles={(response) => {

                    }}
                />

@vaclavgreif
Copy link

Update: downgrade to 2.1.10 did indeed fix the issue

@rikschennink
Copy link
Collaborator

rikschennink commented Dec 12, 2023 via email

@rikschennink
Copy link
Collaborator

rikschennink commented Dec 12, 2023 via email

@vaclavgreif
Copy link

@rikschennink Yes, I did get the error in 2.1.13

@rikschennink
Copy link
Collaborator

rikschennink commented Dec 12, 2023 via email

@rikschennink
Copy link
Collaborator

Looks like 2.1.13 contained the erroneous 2.1.12 files 🫠

Just pushed 2.1.14 which contains the actual fixes for 2.1.13

@vaclavgreif
Copy link

Awesome, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants