-
-
Notifications
You must be signed in to change notification settings - Fork 26
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
Upgrade Datetime library #320
Comments
I see two solutions:
I prefer the second solution ; do you think it's possible ? |
The first option involves some / lot of classes, since there are multiple types related to "dates" The second option I like it, but I am not sure how to do it. Should we expose a raw css/js file and then on the admin we capture it with encore and add it to the build? I add a third option.
|
I don't see how a
Cant we have webpack on this project to build css/js, and then we add the file here: |
We have to make sure we remain compatible with both v1 and v2 of this bundle, but yes I think it can be done that way. |
First part of the issue is solved (well we need to integrate it with AdminBundle). Now we need to merge to branch v2 and upgrade the library. |
Feature Request
We are somehow stuck with the DateTime form type, since it is coupled with the library we are using at the frontend to render it:
https://github.com/Eonasdan/bootstrap-datetimepicker/ -> version 3.1.3
Not only is outdated (there is a version 4, 5, 6 on that repository), but also it got a name change, at least one major rewrite, some options changed a lot, etc...
Also there is another problem here, the form type is defined here, but the library is added here: https://github.com/sonata-project/SonataAdminBundle/tree/4.x/assets/vendor
which is a problem because:
I think we should find a solution before release 2.0, wdyt @VincentLanglet ?
There are also some really old PRs and issues on CoreBundle (when everything was together):
sonata-project/SonataCoreBundle#138
sonata-project/SonataCoreBundle#149
The text was updated successfully, but these errors were encountered: