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
Currently, our focus and priority in relation to setting the foundation for OpenAPI related work should be constrained only to ENSApi.
However, we should note how other apps beyond ENSApi in the ENSNode monorepo have APIs that we will want to apply all the same OpenAPI patterns to. This includes ENSIndexer and ENSRainbow. Potentially more future apps as well too, such as the new app that will soon be spun out of ENSApi specifically for ENS Referral Program related APIs. Etc.
Goals
Set the foundation for supporting multiple openapi.json files from multiple apps.
Stop making the assumption that we will only ever have a single openapi.json file in the monorepo.
Non-Goals
For the scope of this issue, we shouldn't actually introduce any new openapi.json files yet! Instead, we should only imagine and prepare for them to exist. We should stay focused on ENSApi for now.
Quick ideas
Maybe instead of building a single openapi.json file we instead build a distinct openapi.json file for each app with a filename such as {appname}-openapi.json. Advice appreciated.
The scope of this issue might be solved simply by renaming the openapi.json file that we're building and all the references to it.
Background
Goals
openapi.jsonfiles from multiple apps.openapi.jsonfile in the monorepo.Non-Goals
openapi.jsonfiles yet! Instead, we should only imagine and prepare for them to exist. We should stay focused on ENSApi for now.Quick ideas
openapi.jsonfile we instead build a distinctopenapi.jsonfile for each app with a filename such as{appname}-openapi.json. Advice appreciated.openapi.jsonfile that we're building and all the references to it.