Without this workaround when using the Pattern Lab Twig Namespaces plugin using a path / directory other than the one PL would normally assign (ex. one single @mylibrary alias for any pattern to be included by) the original Lineage fix stops working entirely and you get dozens and dozens and dozens of warnings saying you're PL includes / embeds / extends aren't referencing a real pattern.
CC @bmuenzenmeyer since these are the sorts of things we'll need to work through in trying to unify the PHP and Node Pattern Lab cores (perhaps bumping this sort of thing to code handling the Twig Engine / adapter)
Addresses original issue opened here: https://github.com/EvanLovely/plugin-twig-namespaces/issues/4
Without this workaround when using the Pattern Lab Twig Namespaces plugin using a path / directory other than the one PL would normally assign (ex. one single
@mylibrary
alias for any pattern to be included by) the original Lineage fix stops working entirely and you get dozens and dozens and dozens of warnings saying you're PL includes / embeds / extends aren't referencing areal
pattern.CC @evanmwillhite @jesconstantine @bradfrost