Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix processing & linking of alias types #6

Merged
merged 2 commits into from
Jan 12, 2021
Merged

Fix processing & linking of alias types #6

merged 2 commits into from
Jan 12, 2021

Commits on Jan 7, 2021

  1. Fix processing & linking of alias types

    Prior to this change, alias types would be added to the `processor.Types`
    map twice, in the case where an API defines both the alias type, and
    another struct which uses either a pointer to, or an array / slice of,
    an alias type. Depending on which element is processed first, the alias
    type would be added to the map as an AliasKind, or a
    SliceKind/ArrayKind/PointerKind. This means that where templates attempt
    to render an underlying type of an Alias using `IsAlias`, the alias may
    be registered as a non-alias type.
    
    In addition, alias types were treated as Basic in the renderer if their
    underlying types were basic. This means in the above case, links are not
    generated to the alias type in the generated documentation, despite them
    being a valid type as part of the API.
    coro committed Jan 7, 2021
    Configuration menu
    Copy the full SHA
    7cb5f85 View commit details
    Browse the repository at this point in the history

Commits on Jan 11, 2021

  1. Configuration menu
    Copy the full SHA
    594a01a View commit details
    Browse the repository at this point in the history