Skip to content
This repository was archived by the owner on Mar 4, 2020. It is now read-only.
This repository was archived by the owner on Mar 4, 2020. It is now read-only.

Proper marking of depreciated components / properties in DocSite #1756

@hughreeling

Description

@hughreeling

Feature Request

Problem description

Should be very clear to the user when components / behaviours are depreciated and will not be supported going forward. Currently it's in text, that's not particularly visible.

Proposed solution

Depreciated components should be:
Greyed out or similarly distinguishable in component list
Clear marked as depreciated on component and examples pages
Depreciated props should be:
Greyed out or similarly distinguishable in list

Metadata

Metadata

Assignees

No one assigned

    Labels

    vstsPaired with ticket in vsts

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions