The documentation around configuration mentions a way to override where to look for packs, but it seems like packs create doesn't honor this and only allows for creating packs in certain folders, not the one you override in the configuration.
I understand the configuration file syntax (regexp) doesn't make this easy to figure out where the source of the packs is located at. Could the configuration pack_paths, just always assume nested packs and change from regexp to strings instead?
The default configure file would then be:
packs_paths:
- gems
- components
- packs
and the configuration override example could be:
packs_path:
- packages
# or
- modules/systems
Which would be the same contents as PERMITTED_PACK_LOCATIONS today. Moving forward PERMITTED_PACK_LOCATIONS would likely move to a method that evals the config or uses the default if the config isn't present.
This would allow the create command to just work™️:
./bin/packs create modules/systems/disco-service
The documentation around configuration mentions a way to override where to look for packs, but it seems like
packs createdoesn't honor this and only allows for creating packs in certain folders, not the one you override in the configuration.I understand the configuration file syntax (regexp) doesn't make this easy to figure out where the source of the packs is located at. Could the configuration
pack_paths, just always assume nested packs and change fromregexpto strings instead?The default configure file would then be:
and the configuration override example could be:
Which would be the same contents as PERMITTED_PACK_LOCATIONS today. Moving forward
PERMITTED_PACK_LOCATIONSwould likely move to a method that evals the config or uses the default if the config isn't present.This would allow the create command to just work™️: