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
Often latent objects are scattered across multiple classes; I would argue that cross-class occurrences might be the strongest indicator of latent classes hiding in the code (and usually the most obvious)
Some brainstorm on what /could/ be in such a tool:
run from the command line
scan an application for models
just pick through app/models and lib/ ?
walk through object space ?
be passed an array of objects or files ?
output
to STDOUT a nicely formatted report
an HTML report, perhaps with line numbers, code highlighting, etc?
The text was updated successfully, but these errors were encountered:
Perhaps related, are you thinking of static or dynamic analysis? I imagine meta-programming might hide some latent object, and am not sure how comparatively easy it would be to pull that from an AST, versus evaluated code.
Often latent objects are scattered across multiple classes; I would argue that cross-class occurrences might be the strongest indicator of latent classes hiding in the code (and usually the most obvious)
Some brainstorm on what /could/ be in such a tool:
app/models
andlib/
?The text was updated successfully, but these errors were encountered: