-
Notifications
You must be signed in to change notification settings - Fork 68
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
Add entitlements APIs and resources to TypeSpec #1537
Conversation
794381d
to
12ff45e
Compare
84e9c50
to
cedebfe
Compare
cedebfe
to
3d58c41
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A general comment on naming:
- EntitlementCreateInputs -> CreateEntitlementRequest (or NewEntitlement)
- EntitlementStatic -> StaticEntitlement
These names feel more natural to me.
While I realize these are breaking changes for OpenAPI, due to friendly name we can make these changes in TypeSpec. (Can be delayed, but please create a task somewhere)
It would be interesting to see if we can use TypeSpec for better server side code generation.
feat: write entitlement types and base endpoints feat: add management apis chore: address PR comments chore(api): entitlements nits
a3c8e6a
to
2180a84
Compare
Overview
Implements the entitlements related APIs in TypeSpec
Notes for reviewer
TypeSpec doesn't cover 100% of OAPI3 which results in some differences in the generated output.
allOf
types so thelastReset
prop ongetEntitlement
's return value isn't on top level anymore