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
{{ message }}
This repository has been archived by the owner on Sep 4, 2021. It is now read-only.
If ApiCenter is used to manage relationships between services (#12), then it should also be able to work with artifacts that only consume APIs but do not offer one themselves (f.e. frontends).
One way to do this could be to re-define API to "interface" in general, so that "Frontend/Web GUI" is one possible type besides OpenAPI etc.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If ApiCenter is used to manage relationships between services (#12), then it should also be able to work with artifacts that only consume APIs but do not offer one themselves (f.e. frontends).
One way to do this could be to re-define API to "interface" in general, so that "Frontend/Web GUI" is one possible type besides OpenAPI etc.
The text was updated successfully, but these errors were encountered: