Repository navigation
docs(v2): add API reference pages for management and evaluation - #424
Conversation
Add v2 reference pages for auth, environments, branches, namespaces, flags, segments, and evaluation. Signed-off-by: Roman Dmytrenko <rdmytrenko@gmail.com>
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Verdict: comment
Clean, accurate addition of the v2 API reference pages (authentication, environments, branches, namespaces, flags, segments, evaluation, OpenFeature) plus a switch of the v1 reference examples and API playground server from https://try.flipt.io to http://localhost:8080. I verified the new v2 endpoints, HTTP methods, request bodies, and response schemas against the v2-branch OpenAPI specs (rpc/flipt, rpc/v2/environments, rpc/v2/evaluation) and they all match; all new pages are registered in docs.json and carry the required frontmatter. The localhost switch is actually a fix — try.flipt.io no longer resolves (DNS dead) — so it's not a regression. One low-stakes item to confirm before merge: the <ResponseExample> component renders.
docs/v2/reference/segments/create-segment.mdx
- minor (L26):
<ResponseExample>is used here and in 4 other new v2 pages (revoke-self, get-segment, list-segments, update-segment) but is not used anywhere else in the repo and I couldn't find a global component registration for it (the repo has no components dir / mint.json / global MDX import;<RequestExample>is used repo-wide and clearly resolves via some global mechanism, but I couldn't confirm the same for<ResponseExample>). Please confirm these five pages render correctly inmint devbefore merge — if<ResponseExample>isn't a globally-registered Mintlify component, those pages will fail MDX compilation. If it renders, ignore this.
🤖 Automated review by the Flipt PR review agent.
2 participants
Add v2 reference pages for auth, environments, branches, namespaces, flags,
segments, and evaluation.