Code
How google/python-fire is laid out, and where to start for common changes.
There is no import map for this report yet.
Where to start reading
- Repository root
- Repository root
- Likely public API
- Likely public API
- Likely start-up file
- Suggested starting pointAI
- Suggested starting pointAI
- Suggested starting pointAI
Find files for a task
AIAdd support for a new Python object type (e.g., custom class)
- Update fire/inspectutils.py to add introspection logic for the new type
- Add parsing/routing rules in fire/core.py to handle the type in the routing chain
- Add type conversion logic in fire/value_types.py if needed for argument mapping
- Write integration tests in fire/core_test.py to verify routing behavior
Enhance help text and documentation generation
- Add docstring parsing rules in fire/docstrings.py for new docstring formats
- Update fire/helptext.py to format and display the new metadata
- Test with fire/helptext_test.py to verify output
Add a new command-line argument type or parsing behavior
- Define type recognition and conversion in fire/value_types.py
- Update fire/parser.py to recognize and handle the new syntax
- Add test cases in fire/parser_test.py to validate parsing
Customize behavior for specific functions or classes
- Use decorators from fire/decorators.py to annotate functions with Fire directives
- Add metadata extraction in fire/custom_descriptions.py to read decorator values
- Integrate with fire/core.py routing logic to apply customizations
Change the public API
Trace runtime behavior
Add or update tests
Change build or automation
RepoPilot lists up to 500 files, so a file missing here may still exist.
- Files marked “likely” are guessed from their names.