Skip to content

[BUG] Documenting a set() command with PARENT_SCOPE (or other flags) generates incorrect documentation #155

Description

@AutonomicPerfectionist

Describe the bug
Documenting the following command:

set(MyString "String" PARENT_SCOPE)

Documents the variable MyString as a List with the initial values String PARENT_SCOPE

Expected behavior
We should probably check for the PARENT_SCOPE flag, remove it from the type
and default value calculations, and flag it in the generated documentation.
I think adding a note that it sets in the parent scope should be sufficient.

I believe this affects other set() flags like CACHE

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions