The command "gulp create-package" supports the --view flag, but not the --ve flag, so that it builds a customization package that does not contain the institution code (or maybe I call it wrong). However, when I run with gulp run --view DAN1 --ve, the institution code is supported.
Please upgrade the "gulp create-package" command to support taking both a source view code and target view code and packaging it with an alternate top directory.
Best practice would be to keep in Git only "official view codes", but to build for testing and demo a customization package named for a developer or feature. Our institution code is 01NLM_INST, so an example would be building from primo-explore/custom/01NLM_INST for a target customization package with a top-level directory 01NLM_INST-DAN1.
I have an Apache ant build file that does this, but I am not familiar enough with gulp tooling to want to develop a gulp/node way of doing the same.
The command "gulp create-package" supports the --view flag, but not the --ve flag, so that it builds a customization package that does not contain the institution code (or maybe I call it wrong). However, when I run with gulp run --view DAN1 --ve, the institution code is supported.
Please upgrade the "gulp create-package" command to support taking both a source view code and target view code and packaging it with an alternate top directory.
Best practice would be to keep in Git only "official view codes", but to build for testing and demo a customization package named for a developer or feature. Our institution code is 01NLM_INST, so an example would be building from
primo-explore/custom/01NLM_INSTfor a target customization package with a top-level directory01NLM_INST-DAN1.I have an Apache ant build file that does this, but I am not familiar enough with gulp tooling to want to develop a gulp/node way of doing the same.