You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When debugging hook-related issues in Kedro-Viz because the console output does not make it clear whether hooks are being used or not. Users may not know to try the --include-hooks option, leading to confusion when functionality is missing.
Context
This change is important because it will improve clarity when running Kedro-Viz. Some users use custom hooks and are unaware that hooks are not being loaded, making it difficult to diagnose problems. Adding a simple message in the console output would save users time when this problem arises.
Example implementation:
INFO: Running kedro-viz without hooks, if you spot missing functionality try 'kedro viz run --include-hooks'
or
INFO: Running kedro-viz with hooks: mlflow, custom
Possible Alternatives
Could we make --include-hooks by default?
Checklist
Include labels so that we can categorise your feature request
The text was updated successfully, but these errors were encountered:
We purposely made --include--hooks not there by default because ideally kedro-viz doesn't need to run hooks unless you are using dynamic pipeline. Something that I heard is not encouraged. can you confirm @astrojuanlu ?
Also include--hook made Kedro-viz slower if you had pyspark setup, or mlflow.
This is great idea! I also wanted to ask if there's anyway to detect a user is using dynamic pipelines or requires to run hooks to access variables, and if kedro-viz fails; we could say that's because hooks didn't run ? I guess that sort of error handling would be in framework ?
Description
This is a follow-up issue to: #2142
When debugging hook-related issues in Kedro-Viz because the console output does not make it clear whether hooks are being used or not. Users may not know to try the
--include-hooks
option, leading to confusion when functionality is missing.Context
This change is important because it will improve clarity when running Kedro-Viz. Some users use custom hooks and are unaware that hooks are not being loaded, making it difficult to diagnose problems. Adding a simple message in the console output would save users time when this problem arises.
Example implementation:
INFO: Running kedro-viz without hooks, if you spot missing functionality try 'kedro viz run --include-hooks'
or
INFO: Running kedro-viz with hooks: mlflow, custom
Possible Alternatives
Could we make --include-hooks by default?
Checklist
The text was updated successfully, but these errors were encountered: