Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define a tempalte for Rest API #71

Open
ghassanmas opened this issue Jan 24, 2022 · 0 comments
Open

Define a tempalte for Rest API #71

ghassanmas opened this issue Jan 24, 2022 · 0 comments

Comments

@ghassanmas
Copy link
Member

We want to come up with a template that we or/and the owners/maintainers of an MFEs would use as a reference for documenting the usage of the Rest API.

What should the template have or indicate:

  • Indicating if the API is a (backend for frontend) or is general-purpose API:
    • If it's a general-purpose API, does the doc for it exist? e.g. swagger/API if yes link to them...
  • All possible usage scenarios:
    • What are the different ways or combinations to use the API
    • How does the MFE respond to each scenario
    • Indicating all metadata of each request: [method, status code, URL headers]
      • Indicating as well if any of the metadata is optional or required.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant