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

conflict check for plugins Proposal (with code) #121

Open
ldd opened this issue Aug 23, 2017 · 0 comments
Open

conflict check for plugins Proposal (with code) #121

ldd opened this issue Aug 23, 2017 · 0 comments

Comments

@ldd
Copy link

ldd commented Aug 23, 2017

I wrote a plugin that uses ES6's Proxies to observe many game objects and all managers.

You can find it here

My idea is to improve on it until it is able to show common conflicts and eventually suggest solutions. The best part about it is that plugin makers wouldn't be forced to implement any new code. Then again, eventually, a more structured and mature dependency tree could be suggested.
I know that this is not the priority of the engine right now, but I'd love to hear your thoughts on it.

Cons of my idea: At the time being, only modern browsers are supported and the shipped NW.js version of MV does not have support for ES6 Proxies. This could (eventually) be solved.

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