Skip to content

Class coverage in documentation #1534

@volsa

Description

@volsa

Since most of the docs only reference function blocks/functions and we mostly treat classes as second-class citizens right now (they aren't even mentioned in the POUs section of the book), I'd argue if we want to update our docs for classes, we should do the entire thing, not just the api guidelines. Out of scope?

Originally posted by @mhasel in #1533 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions