You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
馃帀 StrictDoc's New Year 2027 Deprecations Removal Party 馃Ч
#3224
We plan to remove all currently deprecated features from StrictDoc by the end of 2026. If you still use any of these features, migrate by December 31, 2026.
Why
StrictDoc keeps many old code paths for backward compatibility. These code paths no longer match the development strategy of StrictDoc and add maintenance overhead to our development. After the removal, the team can spend the saved time on new features and fixes.
A less obvious reason is AI-assisted development. The old code and documentation confuse AI agents, which keep suggesting deprecated patterns. We want the StrictDoc code and documentation to show only the current patterns, so that AI agents follow them in future work.
How
We will remove all deprecations in one dedicated release. The work will go in as a series of small, focused pull requests. If you have questions or need help migrating, reply to this thread or contact us at strictdoc.project@gmail.com.
Planned time window: 20 to 31 December 2026.
Deprecations to be removed
Please check your projects against the list below. Migrate each affected project before the removal. For most items, StrictDoc prints a DEPRECATION warning when it runs.
1. The strictdoc.toml configuration file will be removed
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
What
We plan to remove all currently deprecated features from StrictDoc by the end of 2026. If you still use any of these features, migrate by December 31, 2026.
Why
StrictDoc keeps many old code paths for backward compatibility. These code paths no longer match the development strategy of StrictDoc and add maintenance overhead to our development. After the removal, the team can spend the saved time on new features and fixes.
A less obvious reason is AI-assisted development. The old code and documentation confuse AI agents, which keep suggesting deprecated patterns. We want the StrictDoc code and documentation to show only the current patterns, so that AI agents follow them in future work.
How
We will remove all deprecations in one dedicated release. The work will go in as a series of small, focused pull requests. If you have questions or need help migrating, reply to this thread or contact us at strictdoc.project@gmail.com.
Planned time window: 20 to 31 December 2026.
Deprecations to be removed
Please check your projects against the list below. Migrate each affected project before the removal. For most items, StrictDoc prints a
DEPRECATIONwarning when it runs.1. The
strictdoc.tomlconfiguration file will be removedReplace it with
strictdoc_config.py.Migration guide: https://strictdoc.readthedocs.io/en/stable/?a=SECTION-UG-MIGRATE-CONFIG-2025-Q4
2.
MATHJAXandMERMAIDinproject_featuresare no longer neededMathJax and Mermaid are now on by default. Delete both entries from
project_featuresinstrictdoc_config.py.3.
REQUIREMENT_STYLEin[DOCUMENT]options is renamed toVIEW_STYLERename it to
VIEW_STYLE. The values stay the same.4.
REQUIREMENT_IN_TOCin[DOCUMENT]options is renamed toNODE_IN_TOCRename it to
NODE_IN_TOC. The values stay the same.5. Old Python import paths
This item affects users of the Python API or custom generators.
strictdoc.core.actions.export_actionstrictdoc.features.export.export_actionstrictdoc.core.statistics.metricstrictdoc.features.project_statistics.metricstrictdoc.export.html.generators.project_statisticsstrictdoc.features.project_statistics.generatorstrictdoc.export.html.generators.view_objects.project_statistics_view_objectstrictdoc.features.project_statistics.view_objectstrictdoc.export.html.generators.view_objects.project_tree_statsstrictdoc.features.project_statistics.models.project_tree_stats6.
SOURCE_FILE_LANGUAGE_PARSERSinproject_featuresThis feature is now on by default, and the flag does nothing. Delete it from
project_featuresinstrictdoc_config.py.7. Old fields in
Filerelations:VALUE,FUNCTIONandCLASSUse
PATHinstead ofVALUE. UseELEMENTandIDinstead ofFUNCTIONandCLASS.Before:
After:
For a class, use
ELEMENT: class.Note
StrictDoc does not print a warning for these fields yet.
Deprecations that were already removed
[SECTION]: use[[SECTION]]instead. See the migration guide.REQ_PREFIX: usePREFIXinstead.REFS: useRELATIONSinstead.passthroughcommand: usestrictdoc export --formats=sdocinstead.All reactions