esp-idf/tools/idf_py_actions
Aleksei Apaseev ba51b09cb2 coredump: added the chip_rev field into the coredump header 2023-07-26 10:53:28 +08:00
..
README.md
__init__.py
constants.py esp32p4: introduce the target 2023-06-13 15:16:11 +08:00
core_ext.py fix(tools): Tool curses import check 2023-07-12 13:23:06 +00:00
create_ext.py feat: fix: create-project & create_component with proper file permission 2023-07-17 19:32:30 +08:00
debug_ext.py coredump: added the chip_rev field into the coredump header 2023-07-26 10:53:28 +08:00
dfu_ext.py
errors.py
global_options.py
hints.yml feat(system): add an error log and a hint on failed interrupt alloc 2023-07-19 16:47:41 +02:00
roms.json tools: update esp-rom-elf to version 20230320 2023-03-20 19:20:34 +08:00
roms_schema.json tools: fixed elf symbols load if gdbinit specified 2022-09-21 22:39:03 +04:00
serial_ext.py fix: fix idf passing wrong chip revision to idf_monitor 2023-07-05 17:30:12 +08:00
tools.py fix(tools/hints): add guide to fix error with unsupported asyncio 2023-07-03 10:26:26 +02:00
uf2_ext.py

README.md

idf.py extensions

Python modules (subdirectories and files) in this directory named [your_extension]_ext will be loaded as idf.py extensions. If you want to provide extra extensions just provide ; separated list of directories with extensions in IDF_EXTRA_ACTIONS_PATH. Extensions will be loaded in alphanumeric order. Command line arguments parsing and extension mechanism is implemented on top of Click (versions >=5.0 are supported).

They should define a function action_extensions(base_actions, project_path) where:

  • base_actions - dictionary with actions that are already available for idf.py
  • project_path - working dir, may be defaulted to os.getcwd()

This function have to return a dict with 3 possible keys:

{
    # Additional options that will be available from id
    "global_options": [{
        "names": ["--option-name"],
        "help": "Help for option --option-name.",
    }],
    # List of functions that will have access to full app context, and can mangle with arguments
    "global_action_callbacks": [global_callback],
    # Additional subcommands for idf.py
    "actions": {
        "subcommand_name": {
            "callback": subcommand_callback,
            "help": "Help for subcommand.",
        },
    },
}

Where function global_callback(ctx, global_args, tasks) accepts 3 arguments:

  • ctx - Click context
  • global_args - dictionary of all available global arguments
  • tasks - list of Task objects

And subcommand_callback(subcommand_name, ctx, args) accepts 3 arguments:

  • subcommand_name - name of subcommand
  • ctx - Click context
  • args - list of command's arguments