Skip to content

Update deprecated elements in text #115

@braughtg

Description

@braughtg

When PreTeXt is updated to newest version (when #114 is merged) there are some deprecated elements that should be fixed. Some changes related to cardsort may already be in #65.

The following is in the output of the pretext build web output:

WARNING : * PTX:DEPRECATE: (2025-04-18) the "matches" element inside an "exercise" (or similar) to specify a drag-n-drop problem has been replaced by the "cardsort" element.  This is an entirely cosmetic change.  Until you make the change in your source, we will try to honor your intent. (16 times)
INFO    : *              located within: "ex-explore-the-issue-tracker-e" (xml:id)
INFO    : *              located within: "ex-github-repository-terminology" (xml:id)
INFO    : *              located within: "ex-workflow-step-definitions" (xml:id)
INFO    : *              located within: "ex-git-commands-summary-communities" (xml:id)
INFO    : *              located within: "ex-pull-request-b-ii" (xml:id)
INFO    : *              located within: "ex-pull-request-b-iii" (xml:id)
INFO    : *              located within: "ex-git-commands-summary-upstreaming" (xml:id)
INFO    : *              located within: "ex-git-commands-summary-upstreaming-2" (xml:id)
INFO    : *              located within: "ex-git-commands-summary-synching" (xml:id)
INFO    : *              located within: "ex-fixing-issue-process-a" (xml:id)
INFO    : *              located within: "ex-name-source-target-branches" (xml:id)
INFO    : *              located within: "ex-raw-merge-content" (xml:id)
INFO    : *              located within: "ex-raw-merge-dividers" (xml:id)
INFO    : *              located within: "ex-merge-tool-options" (xml:id)
INFO    : *              located within: "ex-git-commands-summary-merging-pt1" (xml:id)
INFO    : *              located within: "ex-git-commands-summary-merging-pt2" (xml:id)
INFO    : * --------------
WARNING : * PTX:DEPRECATE: (2025-04-23) an "@order" attribute on a "match" is deprecated and should instead be placed on the contained "premise" element(s).  If your cardsort problem is simply a 1-1 correspondence, then we will honor your intent.  If your problem is more complicated (multiple "premise" inside a "match") results may be variable and unpredictable. (2 times)

Metadata

Metadata

Assignees

Labels

CH4Issue related to Chapter 4 - Staying SynchronizedCh2Issue related to Chapter 2 - Communites and CollaborationCh3Issue related to Chapter 3 - Upstreaming ChangesCh5Issue related to Chapter 5 - Merge ConflictsbugSomething isn't workinghot fixIndicates a PR that can be merged any time.

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions