-
Notifications
You must be signed in to change notification settings - Fork 662
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
Add new file_input
block kit element soon to be introduced.
#1689
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.
🚀
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.
LGTM but should we include the parameter for file extensions?
FYI let's hold off on this until 11/13 at least? Context: delayed our GA by a couple of days: https://slack-pde.slack.com/archives/C0539UD5E6M/p1699467241515679?thread_ts=1699461506.812299&cid=C0539UD5E6M |
@WilliamBergamin what do you mean by the following?
|
@filmaj there is a parameter that allows the developer to restrict the file type being sent from the user I think it is The JSON looks like this {
title: "Enter a file",
name: "image-123",
type: Schema.types.array,
maxItems: 1,
description: "",
items: {
type: Schema.slack.types.file_id,
allowed_filetypes_group: "ALL"
},
} @henrymingwu was this feature intended for developers |
@WilliamBergamin I believe the code snippet you shared is for OpenForm fields in the automation platform. However, the interface is a bit different for the File Input block element; see the reference doc for it here: https://api.slack.com/reference/block-kit/block-elements#file_input |
Ohh completely missed |
Summary
In preparation for next week's launch of the new Block Kit File Input element.