The Drupal status report page at /admin/reports/status may include warnings such as:
3 Unknown parsers
4 Up to date parsersVisit the Markdown Overview page for more details.
It isn't entirely obvious what is the appropriate action to take for unknown parsers.
Also, the number of unknown parsers includes those which are not enabled.
Should an unknown parser only trigger a warning if it is enabled?
1. change the logic that causes a warning so that it doesn't confuse people
2. provide guidance on what to do if there are unknown parsers
Active
3.0
Code
\Drupal\markdown\Annotation\ComposerPackage::getAvailableVersions is using a deprecated URL to check for known packages.
See https://github.com/thephpleague/commonmark/discussions/1082#discussionco... for more info.
This change doesn't explain what to do about unknown parsers, but it does:
1. fix the packagist API URL
2. only check enabled parsers
3. make the messaging a bit easier to read