Add compat attribute flags to control parsing #254
Labels
AsciiDoc specification
issues for supporting syntax from the current AsciiDoc specification
enhancement
Milestone
Comments
This was referenced May 21, 2022
|
The basics of the flag have been added to the codebase, with enabling it as an attribute flag slated for 10.3 after an initial announcement as part of 10.2. |
MasterOdin
added
enhancement
AsciiDoc specification
netbsd-srcmastr
pushed a commit
to NetBSD/pkgsrc
that referenced
this issue
May 29, 2022
Version 10.2.0 (2022-05-22) --------------------------- .Future feature As part of the intended 10.3.0 release, the following document attribute flags will be reserved for modifying asciidoc-py runtime behavior: - `future-compat` - `legacy-compat` - `compat-mode` Please see asciidoc-py/asciidoc-py#254 issue #254] for more information. .Bug fixes - Fix verbose output not working when using a2x or asciidoc entry points .Miscellaneous - Automate publishing asciidoc-py website as part of release process Version 10.1.4 (2022-03-01) --------------------------- .Bug fixes - Add missing test py files to dist archives - Fix DeprecationWarnings in a2x regexes
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now, the asciidoc-py parser does not fully follow the parsing rules of asciidoctor, differing in some cases. As part of the roadmap (#173), the plan is to slowly fix these instances where parsing rules differ, and bring asciidoc-py into compliance with the spec such as it currently exists. The 11.0 release would hopefully be fully spec compliant in this regard. However, to ease the developer time on working on this new parsing while still supporting 10.x releases until 11.0 is released, the new parsing stuff will be added to the 10.x releases over time and hidden behind a
future-compatattribute flag. If that flag is enabled, then users would use the new parsing rules, and so give people the ability to see what they might need to change about their document to make it ready for 11.0. The flag should not be advertised until most of the stuff from 11.0 has been added so as to make the breaking changes to documents (if any) fixable in one shot, as opposed to risk breaking things on users under a point release.The text was updated successfully, but these errors were encountered: