-
Notifications
You must be signed in to change notification settings - Fork 8
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(API): Implement figma attachments endpoints #415
Conversation
Varpuspaavi
commented
Sep 27, 2023
•
edited
Loading
edited
- https://phrase.atlassian.net/browse/TSE-613
- https://github.com/phrase/phrase/pull/11856
Reminder to self: I will bump GO before Bumping the CLI |
--- | ||
summary: Attach the Figma attachment to a key | ||
description: Attach the Figma attachment to a key | ||
operationId: figma_attachment_key/create |
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.
wouldn't it be more logical to add these operations to figma_attachments
(or perhaps keys
) instead?
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.
Adjusted, not exactly sure if this is what you meant
CR
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.
yeah, but they'd also have to live on paths/figma_attachments
IMO
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.
but I guess the API PR has already been merged in phrase?
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.
Yes the API PR is merged. Can we have two create.yaml
/destroy.yaml
in the same folder? I could adjust this. On the API PR we agreed to not use custom named methods and instead went with second controller to have option for second create/destroy paths