You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: