-
-
Notifications
You must be signed in to change notification settings - Fork 73
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
Implement Image API #10
Comments
Image fields currently get serialized as a mapping of I would propose the following serialization format instead: {
"@id": "http://nohost/plone/my-image",
"@type": "Image",
"title": "My Image",
"...": "...",
"image": {
"filename": "image.png",
"content-type": "image/png",
"size": 1185,
"download": "http://nohost/plone/my-image/@@images/image",
"scales": {
"icon": "http://nohost/plone/my-image/@@images/image/icon",
"large": "http://nohost/plone/my-image/@@images/image/large",
"listing": "http://nohost/plone/my-image/@@images/image/listing",
"mini": "http://nohost/plone/my-image/@@images/image/mini",
"original": "http://nohost/plone/my-image/@@images/image",
"preview": "http://nohost/plone/my-image/@@images/image/preview",
"thumb": "http://nohost/plone/my-image/@@images/image/thumb",
"tile": "http://nohost/plone/my-image/@@images/image/tile"
}
}
} This doesn't include the dimensions for each scale as in your initial suggestion, but including those would make the response really rather bulky. I don't feel strongly about this, but I probably wouldn't include those until we have framing in place and a client can request to have them omitted. |
Closed by #115 |
The text was updated successfully, but these errors were encountered: