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
Next step is to do the same with the server. But because, dmn-scala has no _213 package - that won't work. There is some compatibility between 3 and 2.13 - but it is a pain anyway. So migrating dmn-scala to Scala 3 would be the prefered solution.
Describe the solution you'd like
Migrate dmn-scala to Scala 3
Are there any plans?
If not, would a pull request be considered?
The text was updated successfully, but these errors were encountered:
I don't have a concrete plan yet to migrate to Scala 3. So, it is not a priority at the moment but it's on my wishlist for this year. 😅
If not, would a pull request be considered?
Not in this case. I really want to do this by myself to get more familiar with Scala 3 and discover new opportunities. ✨
Before migrating the DMN engine to Scala 3, I want to migrate the FEEL engine to Scala 3 as well. A precondition for the migration is coordinating with Camunda Platform 7 and 8 to ensure compatibility.
Is your feature request related to a problem?
I migrated the UI of the DMN Tester to Scala 3.
Next step is to do the same with the server. But because, dmn-scala has no _213 package - that won't work. There is some compatibility between 3 and 2.13 - but it is a pain anyway. So migrating dmn-scala to Scala 3 would be the prefered solution.
Describe the solution you'd like
Migrate dmn-scala to Scala 3
Are there any plans?
If not, would a pull request be considered?
The text was updated successfully, but these errors were encountered: