Open schlotterer opened 1 year ago
Use “wds” as the namespace permanently - this will simplify set up and make the bocks more portable within WDS builds
I love this! Does anyone know the reason we do the find and replace per-project?
Even though the dynamic package naming approach might seem appealing, it's crucial to keep coding standards in mind. These standards recommend that functions within a theme should have namespaces aligned with the theme's name. Disregarding this guideline could potentially trigger a PHP CodeSniffer (phpcs) error stating that Namespaces declared by a theme/plugin should start with the theme/plugin prefix.
As an alternative, you could think about creating a child theme. This way, you could ensure consistent namespaces for both wd_f
and wd_s
. However, it's important to note that using wd_f
and wd_s
as parent themes doesn't align with their intended usage – they're designed as starter themes rather than parent themes.
Use “wds” as the namespace permanently - this will simplify set up and make the bocks more portable within WDS builds
Specific things to add to the cli functionality to be prebuilt: