Skip to content
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

Inconsistencies between xlr-xld becoming problematic. #59

Open
istairbn opened this issue Jul 3, 2017 · 1 comment
Open

Inconsistencies between xlr-xld becoming problematic. #59

istairbn opened this issue Jul 3, 2017 · 1 comment

Comments

@istairbn
Copy link
Contributor

istairbn commented Jul 3, 2017

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.

@jdewinne
Copy link
Contributor

jdewinne commented Jul 6, 2017

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants