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

V1 lifecycle compatibility #196

Open
ghost opened this issue Apr 3, 2018 · 4 comments
Open

V1 lifecycle compatibility #196

ghost opened this issue Apr 3, 2018 · 4 comments

Comments

@ghost
Copy link

ghost commented Apr 3, 2018

@csuwildcat
Could we create a v2 test branch for a lifecycle extension, a lot of devs on v1 or devs thinking of choosing xtags would like to use v2 but want support for some of the older API.

A notable one is LotusJS

@ghost
Copy link
Author

ghost commented Apr 5, 2018

Just keeping thread updated:
Thinking of making a pull request under a lifecycle branch that way any work on this enhancement can be tracked better.

@csuwildcat
Copy link
Member

I'm not sure how compatible it will all be on the functionality side, but I'd have to know what was desired to know if it can be done.

@ghost
Copy link
Author

ghost commented Apr 8, 2018

I have been mulling it over and I don't think you are wrong.

I was thinking if any patch were to be made extending the definition to include a xtag.lifecycle might be a route to take.

@ghost
Copy link
Author

ghost commented Apr 8, 2018

This might be better off with #198 maybe..if you wanted to go a different route. Plus it may be better for me to drop this one.

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

1 participant