Skip to content

Falco Rules Doc Comments #150

Description

@leogr

Motivation

The issues I found with comments are due to practical reasons. In particular:

  • There should be no empty lines between the comments and the referred item
    • This will avoid ambiguities.
    • I guess I mostly fixed that with this PR.
  • There's no standard item's comment structure
    • I would love to define a simple Rule Doc convention (i.e., something similar to Go Doc Comments, but simpler)
  • There's no clear way to distinguish sections from item's comment

Feature

Implement a simple Rules Doc Comments guideline and add it to the rules style guide.

Alternatives

Just rely on an existing convention, if any, or do nothing. However they don't look like compelling alternatives.

Additional context

See #149 (comment)

Activity

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

Metadata

Metadata

Assignees

Labels

help wantedExtra attention is neededkind/featureNew feature or request

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions