Deprecations
Anything listed here still works. A removal only ever happens in a major release, and only after the member has been marked deprecated in a minor one. Each entry names what to use instead.
How you are told:
@deprecatedin the source. It shows in your editor, intscand lint rules, and in the custom-elements manifest. It only reaches you if you use TypeScript or typed JSX.- A console warning, for the few members where a host can act on it. It is printed once per element and names the replacement. Marked below.
- The release notes and the host migration notes for every change that touches the Public API (in Storybook).
Removed in the next major release
| Deprecated | Use instead | Console warning |
|---|---|---|
test-navigation.qtiContext | qtiTest.qtiContext: the same value, same behaviour | yes, on write |
qti-test-context-updated event | qti-state-changed, and qtiTest.state to restore | no |
SessionContext.navItemLoading and navTestLoading | nothing: the library never set them | no |
test-navigation.qtiContext is an alias today: it reads and writes the enclosing qti-test’s
value, so setting the shuffle seed there keeps working. See Persist & restore.
Planned, not yet marked in the source
These are decided but not deprecated in code yet, so nothing warns about them.
| Planned | Replacement |
|---|---|
sessionContext.view | view in the config, mirrored until the old one goes |
Dispatching on-test-switch-view and test-show-candidate-correction | a view property and a showCandidateCorrection method |
Deprecated, no removal date
| Deprecated | Use instead | Console warning |
|---|---|---|
Assigning or reading qtiTest.testContext to persist a session | qtiTest.state. testContext is still the internal provider | no |
item.responses | item.variables | no |
ConfigContext.disableAfterIfMaxChoicesReached | disableAfterMaxReached | yes |
qti-choice-interaction orientation | the qti-orientation-horizontal / -vertical classes | no |
IInteraction | RegisteredInteraction | no |
DragDropInteractionMixin, TouchDragAndDrop and the other legacy drag-drop mixins | DragDropSlottedMixin (and DragDropSlottedSortableMixin) | no |
test-paging-buttons-stamp, test-section-buttons-stamp | the <template>-driven pattern used by test-scoring-buttons | no |
test-show-correct-response | the <template>-driven pattern used by test-view-toggle | no |
filterArgsForSpread | the spreadArgs directive | no |
“No removal date” means it is marked deprecated and will be removed in a later major release, not the next one. It moves to the first table when a date is set.