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
It is possible to annotate an anonymous class with an attribute and not have a namespacedName property present. This same problem, presumably, exists with a class that isn't namespaced. This ticket should ensure that all class types can be properly gathered.
The text was updated successfully, but these errors were encountered:
After more research this is only a problem when attributing an anonymous class. A comprehensive strategy for how to deal with this needs to be designed. What is actually supposed to happen when this library finds an anonymous class with attributes is probably entirely contextual. Perhaps just ignoring it, perhaps keep track of what files/lines the anonymous class was found, or perhaps throw an exception. Depending on what you're trying to do with the Attribute either of these might be valid.
After giving this some more thought, if you're using Annotated Target it is because you want the code constructs before you're actually running the code. I couldn't think of a scenario where Annotated Target could provide its features on an attributed anonymous class. For now, we're gonna throw an exception until somebody can present a valid use case and solution for adding attributes to an anonymous class in the use cases Annotated Target is trying to support.
It is possible to annotate an anonymous class with an attribute and not have a namespacedName property present. This same problem, presumably, exists with a class that isn't namespaced. This ticket should ensure that all class types can be properly gathered.
The text was updated successfully, but these errors were encountered: