Skip to content

"input" and "output" blocks in NSO action definitions are incorrectly interpreted as duplicate schema nodes #213

Description

@Hubro

The "input" and "output" blocks of NSO action definitions probably shouldn't be interpreted as duplicate schema nodes:

image

This leads to huge amounts of diagnostic noise in large YANG files.

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