[jira] [Updated] (CAUSEWAY-3963) WONT DO - [Debug] For every Type introspected, keep track of what triggered the Introspection

["Andi Huber (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CAUSEWAY-3963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andi Huber updated CAUSEWAY-3963:
---------------------------------
    Fix Version/s: 4.0.0-M2
                       (was: 4.0.0)

> WONT DO - [Debug] For every Type introspected, keep track of what triggered the Introspection
> ---------------------------------------------------------------------------------------------
>
>                 Key: CAUSEWAY-3963
>                 URL: https://issues.apache.org/jira/browse/CAUSEWAY-3963
>             Project: Causeway
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Andi Huber
>            Assignee: Andi Huber
>            Priority: Major
>             Fix For: 4.0.0-M2
>
>
> Some times types end up in the meta-model, which we perhaps don't want. At this stage it is hard to find the cause for why a specific type got introspected.
> With this change, we'd like to introduce e.g. a new field within ObjectSpecification, that keeps some record on what triggered the introspection.
> Could be because discovered by Spring as a Bean candidate, which is the trivial case, but then we have cascading triggering via going into type hierarchies and also members and action parameters. 
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)