Add source-backed Blood Hunts enrichment map#136
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
MonoBehaviour/BloodHuntsDataAuthoring.json.npm run refresh:db-assets, coverage reporting, and generated-data validation.HideLevelconversion, required joins, and excluding Unity/UI asset fields.Verification
npx tsx scripts/blood-hunts.test.ts$env:VRISING_ASSET_DUMP_DIR='C:\Users\mitch\Local\Assets'; npm run refresh:db-assetsnpm run generate:dbnpm run validate:datanpx tsc --noEmitnpm run verifynpm testNote:
refresh:db-assetsusedVRISING_ASSET_DUMP_DIR=C:\Users\mitch\Local\Assetsbecause currentorigin/mainstill defaults to the old OneDrive asset dump paths.