You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I thought it was stable since the compose API was promoted on documentations but the I_KNOW_THE_APPSTREAM_COMPOSE_API_IS_SUBJECT_TO_CHANGE thing indicate the opposite.
If prioritizing the API over the cli tools is really preferred, why keeping this dealbreaker ?
Or they are stuff that needs to be worked on before ?
The text was updated successfully, but these errors were encountered:
I am still not happy with it, the API is leaking a few internals for appstream-generator to hook into that could probably be abstracted away better.
If you only use the AscCompose class (and not things like AscCanvas) you most likely won't experience much, or any, breakage though.
Ideally I would have more time to work on asgen and the compose library to declare it fully stable, but I currently don't have that time (or funding) sadly.
What do you want to use the API for / what concerns do you have?
I thought it was stable since the compose API was promoted on documentations but the
I_KNOW_THE_APPSTREAM_COMPOSE_API_IS_SUBJECT_TO_CHANGE
thing indicate the opposite.If prioritizing the API over the cli tools is really preferred, why keeping this dealbreaker ?
Or they are stuff that needs to be worked on before ?
The text was updated successfully, but these errors were encountered: