You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current latest version of blueprint is v5.x and my company is building our application on v5. We're currently running up against a potential dependency issue with the blueprint datetime versus blueprint datetime2 module which may be resolved if blueprint versions are resolved.
Do you have any plans to upgrade to blueprint v5? Are there any blockers or special considerations to take into account? My company would be happy to support with this process as we feel the ove is a very useful tool.
From forking the library it looks like the main changes would be upgrading datetime to datetime2 as well as the keycombos module.
The text was updated successfully, but these errors were encountered:
Update: we are proceeding with using the vanilla js package of TeselaGen ove for now which is working nicely and decouples our build process and css pre-processing from the ove project.
@tnrich
The teselagen/ove vector editor package is currently using the following versions of blueprint:
The current latest version of blueprint is v5.x and my company is building our application on v5. We're currently running up against a potential dependency issue with the blueprint datetime versus blueprint datetime2 module which may be resolved if blueprint versions are resolved.
Do you have any plans to upgrade to blueprint v5? Are there any blockers or special considerations to take into account? My company would be happy to support with this process as we feel the ove is a very useful tool.
From forking the library it looks like the main changes would be upgrading datetime to datetime2 as well as the keycombos module.
The text was updated successfully, but these errors were encountered: