Skip to content

Self Document Available Objects #4

Description

@timtadh

The objects available to be passed to engines should be self documenting. Eg. you should be able to ask bin/fuzzbuzz what is available and it should tell you.

I am unsure if this should be exposed by the user interface but it certainly should be programmatically exposed. I am not sure of a good way to actually programmatically expose this since you can't say import this file (as it is not a .py file). Therefore I am leaning towards just making a command line flag.

Whichever way it is exposed the information provided should be the following:

  • Name of object
  • Description of what it is
  • Type of object (eg. dictionary, list, string, etc...)

@johngunderman any ideas?

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions