Skip to content
This repository was archived by the owner on Sep 21, 2023. It is now read-only.
This repository was archived by the owner on Sep 21, 2023. It is now read-only.

Introduce formatting warnings #322

Description

@TimJentzsch

The formatting issues should be split into "errors" and "warnings".
Errors should indicate issues that are always wrong and block the done.
Warnings indicate potential issues that require the user to double-check.

For example, the check for hashtags being headings should be a warning instead of an error.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions