Cleanup handling of non-env configs
Reported by bahuvrihi | April 17th, 2008 @ 03:37 PM | in Tap 0.10.0
The load_config - configure cycle is confusing because of the yields to handle unknown configs. In one case a path is available and in the other there is not.
Direct all handling of non-env configs to a standard method and allow assignment of this method dynamically (a-la on_complete).
Comments and changes to this ticket
-
bahuvrihi April 17th, 2008 @ 04:17 PM
- State changed from “new” to “resolved”
- Assigned user set to “bahuvrihi”
Changed Env such that non_env_configs are passed to the load_config block, but ONLY for the config loaded directly from the config file. Similarly, non_env_configs are passed to the configure block but ONLY for the configs passed to configure.
Hence, non-env configs will automatically be overlooked in chain-loaded configurations.
-
bahuvrihi April 17th, 2008 @ 04:19 PM
- Milestone set to “Tap 0.10.0”
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
A framework for making configurable, file-based tasks and workflows.
bahuvrihi