Skip to content

docs: Describe why certain implementations (e.g. ion-loading) are described as recommended #3669

Open
@Alextremeee

Description

@Alextremeee

Describe Problem

For example the documentation of ion-loading describes both an inline and controller implementation, but describes the inline one as recommended without explaining why.

It would be useful to know why this is recommended at this point in the documentation as it may inform your decision about how to implement something. For example, a controller-based implementation of ion-loading may seem preferable to my use case, but if I don't know why an inline implementation is recommended it's harder to make a good choice.

Is this recommendation simply for code clarity, or does it provide a benefit to the end user?

Describe Preferred Solution

I believe there are a few components that have the same description so this could just be a link to a page describing why inline implementations are preferable.

Describe Alternatives

No response

Additional Information

https://ionicframework.com/docs/api/loading#inline-recommended

Metadata

Metadata

Assignees

No one assigned

    Labels

    contentIssues related to the contents of the documentation website

    Type

    No type

    Projects

    Status

    Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions