-
Notifications
You must be signed in to change notification settings - Fork 6
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
feat(apikeys): implement the base paths for the api keys resource #22
Conversation
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.
You need to add the new api keys resource to the platform object in the file platform-client/src/resources/PlatformResources.ts
src/resources/ApiKeys/ApiKeys.ts
Outdated
return this.api.get<ApiKeyModel[]>(ApiKey.baseUrl); | ||
} | ||
|
||
toggle(apiKey: ApiKeyModel, options?: {}) { |
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
import Resource from '../Resource'; | ||
import {ApiKeyModel} from './ApiKeysInterfaces'; | ||
|
||
export default class ApiKey extends Resource { |
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
resourceId?: string; | ||
} | ||
|
||
export enum Provider { |
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
OTHER = 'OTHER', | ||
} | ||
|
||
export interface IdAndDisplayNameModel { |
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
displayName?: string; | ||
} | ||
|
||
export interface PrivilegeModel { |
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
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.
great job! you could squash and merge so that the git history remains clean 😄 I you do, you will still need to write a commit message that respects the commit message convention
🎉 This PR is included in version 2.3.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
No description provided.