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 latest suite of changes have seen all the XL Deploy tasks renamed so that everythinbg comes under XL Deploy (rather than split between XL Deploy and xldeploy)
This is good... except that now it looks incredibly inconsistent. Some fields take Applications/ and some don't. Some have auto-complete. Some are duplicate functions entirely.
Technically the best thing would be to have 1 plugin. If we can't, we should try and be consistent so that inputs from one task type can seamlessly work with another.
The text was updated successfully, but these errors were encountered:
The idea is indeed to move more functionality to the official supported plugin and also reuse as much as possible from that plugin. That is also the purpose of the v3.x versions. However, first step will now be to make v3.x backwards compatible.
After that we'll look into getting rid of duplicate task types and making it more consistent.
The latest suite of changes have seen all the XL Deploy tasks renamed so that everythinbg comes under XL Deploy (rather than split between XL Deploy and xldeploy)
This is good... except that now it looks incredibly inconsistent. Some fields take Applications/ and some don't. Some have auto-complete. Some are duplicate functions entirely.
Technically the best thing would be to have 1 plugin. If we can't, we should try and be consistent so that inputs from one task type can seamlessly work with another.
The text was updated successfully, but these errors were encountered: