Skip to content

Feature grouping of Streams API #368

@kosamari

Description

@kosamari

I have a question about how Streams API would be represented within web-features.

Would "Streams" be a bigger feature, and separate APIs like "WritableStream" or "ReadableStream" be a sub feature? or is it going to be just "Streams"?

context : we are discussing how to communicate WritableStream being Baseline in our documentation, and run into this question of "what is the unit of a feature" since when we discuss stream use case multiple stream API are involved in a demo.

Metadata

Metadata

Assignees

No one assigned

    Labels

    feature definitionCreating or defining new features or groups of features.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions