feat: generate standalone admin SDK - #6000
Conversation
|
There was a problem hiding this comment.
All reported issues were addressed across 252 files
Heads up: you’re close to your included review allowance. Set a flex budget so reviews don’t pause.
Note: This PR contains a large number of files. cubic selects up to 200 of the highest-priority eligible files for this review, so some files may not have been reviewed.
Tip: instead of fixing issues one by one fix them all with cubic
Re-trigger cubic
7503930 to
551224b
Compare
This comment has been minimized.
This comment has been minimized.
551224b to
5a9447a
Compare
5a9447a to
8e79147
Compare
8e79147 to
9756b22
Compare
This comment has been minimized.
This comment has been minimized.
9756b22 to
3047a44
Compare
There was a problem hiding this comment.
All reported issues were addressed across 82 files (changes from recent commits).
Reply with feedback, questions, or to request a fix.
Fix all with cubic | Re-trigger cubic
75edca9 to
9e82ae4
Compare
9e82ae4 to
999bbf1
Compare
Stack context
This PR is the second part of a four-PR stack that moves organization product-feature management from the legacy Dashboard Platform Admin surface into the standalone Admin application.
The preceding PR, #6036, establishes the shared backend contract, Goa operations, and isolated Dashboard/Admin OpenAPI inputs. This PR consumes that Admin-specific contract to generate a private TypeScript SDK and places it behind a constrained same-origin application boundary. The next PR uses this client to deliver feature-management parity in Admin, after which the final PR removes the duplicate Dashboard surface.
What this PR does