-
-
Notifications
You must be signed in to change notification settings - Fork 4k
feat(builders): multipart form data output support #11248
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
base: main
Are you sure you want to change the base?
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 2 Skipped Deployments
|
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #11248 +/- ##
==========================================
+ Coverage 44.39% 44.77% +0.38%
==========================================
Files 315 317 +2
Lines 18136 18252 +116
Branches 1805 1863 +58
==========================================
+ Hits 8051 8172 +121
+ Misses 10073 10068 -5
Partials 12 12
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
| */ | ||
| export class MessageBuilder implements JSONEncodable<RESTPostAPIChannelMessageJSONBody> { | ||
| export class MessageBuilder | ||
| implements JSONEncodable<RESTPostAPIChannelMessageJSONBody>, FileBodyEncodeable<RESTPostAPIChannelMessageJSONBody> |
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.
| implements JSONEncodable<RESTPostAPIChannelMessageJSONBody>, FileBodyEncodeable<RESTPostAPIChannelMessageJSONBody> | |
| implements FileBodyEncodeable<RESTPostAPIChannelMessageJSONBody> |
This is redundant considering FileBodyEncodeable extends JSONEncodable
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'm aware, but I'm honestly for leaving it in just for extra readability without knowing what a FileBodyEncodeable is (arguably beneficial for docs too?). Thoughts @vladfrangu
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.
For docs it would (should) show the toJSON() on the extended interface already, so not sure of the benefit
No description provided.