-
Notifications
You must be signed in to change notification settings - Fork 13
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(projectSecrets): add CRUDL for project secrets #40
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Lukáš Janeček <[email protected]>
Signed-off-by: Lukáš Janeček <[email protected]>
Signed-off-by: Lukáš Janeček <[email protected]>
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 approach with the tool inputs 👍
import { createPaginatedResponse, getListCursor } from '@/utils/pagination.js'; | ||
import { getUpdatedValue } from '@/utils/update.js'; | ||
|
||
export function toDto(toolSecret: Loaded<ToolSecret, 'tool'>): ToolSecretDto { |
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.
toToolSecretDto
value: { | ||
type: 'string' | ||
}, |
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.
Are we sure about this? Should user (and the rest of the project) be able to read the value?
value: { | ||
type: 'string' | ||
}, | ||
tool: toolSchema |
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.
I don't think tool should be included in the tool secret response. If special endpoint for UI is needed, I'd rather go that way.
DO NOT MERGE