Skip to content
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

Merged
merged 2 commits into from
Oct 13, 2023
Merged

Conversation

Varpuspaavi
Copy link
Contributor

@Varpuspaavi Varpuspaavi commented Sep 27, 2023

@Varpuspaavi Varpuspaavi changed the title feat: Implement figma attachments endpoints feat(API): Implement figma attachments endpoints Sep 27, 2023
@Varpuspaavi Varpuspaavi marked this pull request as ready for review October 10, 2023 13:11
@Varpuspaavi
Copy link
Contributor Author

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
Copy link
Collaborator

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?

Copy link
Contributor Author

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

Copy link
Collaborator

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

Copy link
Collaborator

@jablan jablan Oct 11, 2023

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?

Copy link
Contributor Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants