Skip to content

[native_assets_cli] BuildOutput API #25

Closed
Listed in
@dcharkes

Description

@dcharkes

It seems that this BuildOutput doesn't make a real API (such as output.addAsset(...)) instead it exposes it's constituent fields. Some of those fields like assets are mutable, others are not mutable.

It may be better to provide an API that one can use to add things to the output. The API can be hierarchical just like the config.

What should this API look like?
And should we separate API from implementation?

Related discussions:

Activity

added
P2A bug or feature request we're likely to work on
on Apr 28, 2023
dcharkes

dcharkes commented on Aug 1, 2023

@dcharkes
CollaboratorAuthor

One thing to do here is to make a clean API, rather than exposing the fields.

dcharkes

dcharkes commented on Oct 11, 2023

@dcharkes
CollaboratorAuthor

@mosuem as promised: This is the API that requires some iteration. 😃

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

    P2A bug or feature request we're likely to work onpackage:hooks

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      Participants

      @dcharkes

      Issue actions

        [native_assets_cli] `BuildOutput` API · Issue #25 · dart-lang/native