Accepting means allowing specific files to be dropped into an instance.
This accept-3
file type is only intended to be used on
.Accept
files.
There was a concept called buckets that was too unusual thus too complex, so we are
phasing them out in favor of sections. Sections are simply files in other
files to allow grouping their children, for example if you have a 2-columns app.
The older type accept-2
supported accepting files in specific buckets,
accept-3
is not aware of buckets any more. The .Accept file needs to be
defined on the section files instead.
An accept-3
file can be configured via the string attribute accept
.
The attribute values must be a space separated lists of app methods. There are 2 special values:
.Image
- currently only the built-in image-1
app implements it, and.None
- which can not be implemented.Built-in methods you will likely want to use:
.Inline
,.Request
,.Page
.You can also use user-space methods, like .foo
. User-space methods start
with a dot followed by a lower-case letter. This allows you to create
applications that only allow one to drop specific file types - those that
implement that interface.
Open it in your browser to validate it.
{
"title": "",
"link": "",
"type": "accept-3",
"statusCode": 0,
"attr": {
"accept string": ""
}
}
Do not create the .Accept
file or use:
{
"title": "",
"link": "",
"type": "accept-3",
"statusCode": 0,
"attr": {
"accept string": ".None"
}
}
{
"title": "",
"link": "",
"type": "accept-3",
"statusCode": 0,
"attr": {
"accept string": ".Page"
}
}
{
"title": "",
"link": "",
"type": "accept-3",
"statusCode": 0,
"attr": {
"accept string": ".Image"
}
}
{
"title": "",
"link": "",
"type": "accept-3",
"statusCode": 0,
"attr": {
"accept string": ".Inline"
}
}
{
"title": "",
"link": "",
"type": "accept-3",
"statusCode": 0,
"attr": {
"accept string": ".Inline .Request"
}
}
.Request