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

Create a CLI #6

Open
kerrizor opened this issue Mar 11, 2014 · 1 comment
Open

Create a CLI #6

kerrizor opened this issue Mar 11, 2014 · 1 comment

Comments

@kerrizor
Copy link
Owner

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?
@bf4
Copy link

bf4 commented Mar 12, 2014

This issue seems to mostly be about desired functionality that isn't really dependent on a command-line.

For the CLI, I like GLI?

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.

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

No branches or pull requests

2 participants