-
Notifications
You must be signed in to change notification settings - Fork 38
[Improvement]: Allow filter definition's page limit to be int as well #245
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
[Improvement]: Allow filter definition's page limit to be int as well #245
Conversation
nice, do we need a migration there for existing data? |
No, existing decimal values will get converted to integers, meaning nothing really happens to the values. |
That's also what I meant with migration :-). At least we will need an upgrade note. But I'm not sure though, how a migration path could look like? Automatically overwriting the class definition is dangerous, because there might custom adaption to that class definition. Any ideas? |
Yeah, this situation is just like the one we faced when we migrated from Pimcore 6 to Pimcore X. Everything was broken because of return typehints because they were made mandatory. Back then we solved it by upgrading to Pimcore X and then manually go over our class definitions and update return typehints manually. The migration plan:
|
Hmm, we could do a two step process. And then with next major, we could switch to pure int. The change in |
Yeah, that's a good approach. I'll make the changes. |
2d4e4d5
to
a6bb199
Compare
|
Updated abstract class, allowing float and int values. |
thx very much |
Resolves #195