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

getBase64 returns string #624

Open
wants to merge 1 commit into
base: 1.11
Choose a base branch
from
Open

Conversation

divinity76
Copy link
Contributor

@divinity76 divinity76 commented May 14, 2024

... reading the code, it suggest the return can either be string or null, but with the isSuccessful() check, i think it can only ever return string?

not 100% sure if it should be string or ?string but we can narrow it down from mixed.

... reading the code, it suggest the return can either be string or null, but with the isSuccessful() check, i think it can only ever return string?
@enricodias
Copy link
Member

It should only be string but technically changing types to a more restrict one is still a breaking change :/
There are lot's of other cases like that in this lib. Changing them alone is not enough reason for a new major version, but we should fix them all in the first opportunity we have.

@divinity76
Copy link
Contributor Author

@enricodias got an idea! what if we make a develop branch where we queue up all the changes that should be part of the next release, and branch out from develop for making actual releases?

@enricodias
Copy link
Member

enricodias commented May 23, 2024

We already use the main branch as the current developing branch and make releases from it. Having another branch for a 2.x version would require us to keep syncing new features and fixes from 1.x to 2.x until the new version actually gets released. People also don't usually update major versions that often because they have breaking changes. We would end up having to support 2 versions for some time. When 1.0 was released, it took several months for the majority of users to migrate from 0.x to it. I think we need a better reason to justify a whole new major version, like a rework of some core features.

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

Successfully merging this pull request may close these issues.

2 participants