LazyTool: round-4 _MATERIALIZE_OK additions

Eight more execution-path attrs surfaced by API tests:

- ``execute`` — the tool execute method itself.
- ``expand_incoming`` — parameter expansion for multi-run / map-over.
- ``params_to_strings`` — parameter serialisation.
- ``tool_action`` — execution action dispatch.
- ``tool_dir`` — on-disk directory accessor (read by some callers).
- ``completed_jobs`` — job-search-by-tool API.
- ``get_default_history_by_trans`` — default-history lookup during execute.
- ``regenerate_imported_metadata_if_needed`` — import/export job path.

All execution-path; correct to materialise on first read.
This commit is contained in:
mvdbeek
2026-07-28 17:27:19 +02:00
parent 09f32c2a15
commit 39c5552f2b
+8
View File
@@ -139,6 +139,14 @@ class LazyTool:
"tool_source", # raw ToolSource; some callers walk it directly
"dynamic_tool", # dynamic-tool linkage on execution
"produces_entry_points", # interactive tool entry points
"execute", # actual tool execute method
"expand_incoming", # parameter expansion for multi-run/map
"params_to_strings", # parameter serialisation
"tool_action", # execution action dispatch
"tool_dir", # on-disk tool directory accessor
"completed_jobs", # job-search via tool
"get_default_history_by_trans", # default-history lookup on execute
"regenerate_imported_metadata_if_needed", # import/export path
# Job runner reads this on the tool to decide environment setup.
"requires_galaxy_python_environment",
}