Skip to content

Fix BKT params naming: use defaultBKTParams and experimentalBKTParams#109

Merged
mjyang00001 merged 1 commit intoCAHLR:content-stagingfrom
mjyang00001:content-staging
Apr 10, 2026
Merged

Fix BKT params naming: use defaultBKTParams and experimentalBKTParams#109
mjyang00001 merged 1 commit intoCAHLR:content-stagingfrom
mjyang00001:content-staging

Conversation

@mjyang00001
Copy link
Copy Markdown
Collaborator

Summary

  • Update deploy-content-staging.yml to generate defaultBKTParams.json and experimentalBKTParams.json instead of bktParams1.json/bktParams2.json
  • Update App.js imports to match the new filenames

Why

The incremental update workflow was generating files with the new names (defaultBKTParams/experimentalBKTParams) but content-staging's App.js was still importing the old names (bktParams1/bktParams2). This caused the build to silently fall back to stale BKT params, resulting in BKT parameter console errors and lessons not rendering correctly.

This fix was originally made on fix-bktparams-for-content-staging (commit 4d11d9d) but was never merged into content-staging.

Test plan

  • Trigger the incremental content update workflow after merge
  • Verify no "BKT Parameter does not exist" errors in browser console
  • Verify lessons render and problems can be answered

- Update workflow to create defaultBKTParams.json and experimentalBKTParams.json
- Update App.js imports to use new filenames
- Fixes module not found error for bktParams1.json
@mjyang00001 mjyang00001 merged commit a8d9c30 into CAHLR:content-staging Apr 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants