feat: add optional outListingFile
config property that copies model listing JSON file as post-generate step
#493
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #492
This adds a new optional
outListingFile
property toUserConfig
(as used insde.config.js
), which simplifies the process of copying the model listing file to a specific location, like a source code directory.The one place where this was relevant was the new
house-game
example. I was able to simplify thesde.config.js
file for that project to use this new property instead of the old workaround, which was a custom plugin that copied the file.As part of this, I updated the
build
package tests to remove thesde-prep
directory between runs, and moved thebuild-dev
andbuild-prod
tests into separate directories, since before there was a chance that they would share the samesde-prep
directory, which could lead to race conditions.