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

move AAPI from middleware #3

Open
cstockloew opened this issue Jun 10, 2017 · 3 comments
Open

move AAPI from middleware #3

cstockloew opened this issue Jun 10, 2017 · 3 comments

Comments

@cstockloew
Copy link
Member

Move AAPI from middleware to this repo; adapt bundle/package names.

@cstockloew
Copy link
Member Author

Just a quick vote: do we want to keep the AAPI?

There are some drawbacks with the approach, e.g. that not everything is possible yet (it's just not everything implemented to be available as annotation). Also, some levels of AAPI only work locally, but not distributed. And it's a completely different approach that may be problematic if a beginner starts with this one and then has to learn the 'traditional' way (twice the learning)..

@amedranogil
Copy link
Member

I would say keep it, we don't have the resource to fully integrate it, but I think in the future this feaute will be very useful for quick integration (when properly implemented).

@Alfiva
Copy link
Member

Alfiva commented Jun 27, 2017

I personally usually don't like annotations. Maybe we can keep it but not advertise it...

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

3 participants