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

Standardize the mechanisms for copy annotations to component/implementation class #112

Open
realityforge opened this issue May 21, 2020 · 0 comments

Comments

@realityforge
Copy link
Member

A few attempts have been made to build on Arez functionality in other downstream projects. One challenge is how to copy annotations to generated subclasses to trigger other annotation processors. See arez/arez-persist#4 for a description of such an issue.

It would be useful to define a mechanism by which Arez derived frameworks could cooperate and allow mixing frameworks. An annotation on an annotation style approach should do the trick. This would make all sidecar solutions a lot easier to implement.

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

No branches or pull requests

1 participant