Security News
Supply Chain Attack Detected in Solana's web3.js Library
A supply chain attack has been detected in versions 1.95.6 and 1.95.7 of the popular @solana/web3.js library.
@editorjs/image
Advanced tools
Image Block for the Editor.js.
Notes
This Tool requires server-side implementation for the file uploading. See backend response format for more details.
This Tool is also capable of uploading & displaying video files using the <video>
element. To enable this, specify video mime-types via the 'types' config param.
Get the package
yarn add @editorjs/image
Include module at your application
import ImageTool from '@editorjs/image';
Optionally, you can load this tool from JsDelivr CDN
Add a new Tool to the tools
property of the Editor.js initial config.
import ImageTool from '@editorjs/image';
// or if you inject ImageTool via standalone script
const ImageTool = window.ImageTool;
var editor = EditorJS({
...
tools: {
...
image: {
class: ImageTool,
config: {
endpoints: {
byFile: 'http://localhost:8008/uploadFile', // Your backend file uploader endpoint
byUrl: 'http://localhost:8008/fetchUrl', // Your endpoint that provides uploading by Url
}
}
}
}
...
});
Image Tool supports these configuration parameters:
Field | Type | Description |
---|---|---|
endpoints | {byFile: string, byUrl: string} | Endpoints for file uploading. Contains 2 fields: byFile - for file uploading byUrl - for uploading by URL |
field | string | (default: image ) Name of uploaded image field in POST request |
types | string | (default: image/* ) Mime-types of files that can be accepted with file selection. |
additionalRequestData | object | Object with any data you want to send with uploading requests |
additionalRequestHeaders | object | Object with any custom headers which will be added to request. See example |
captionPlaceholder | string | (default: Caption ) Placeholder for Caption input |
buttonContent | string | Allows to override HTML content of «Select file» button |
uploader | {{uploadByFile: function, uploadByUrl: function}} | Optional custom uploading methods. See details below. |
actions | array | Array with custom actions to show in the tool's settings menu. See details below. |
features | object | Allows you to enable/disable additional features such as border, background tunes and caption. See details below. |
Note that if you don't implement your custom uploader methods, the endpoints
param is required.
Add border
Stretch to full-width
Add background
Add caption
Add extra setting-buttons by adding them to the actions
-array in the configuration:
actions: [
{
name: 'new_button',
icon: '<svg>...</svg>',
title: 'New Button',
toggle: true,
action: (name) => {
alert(`${name} button clicked`);
}
}
]
NOTE: return value of action
callback for settings whether action button should be toggled or not is deprecated. Consider using toggle
option instead.
You can disable features such as border, background tunes and caption by defining features
in the configuration:
features: {
border: false,
caption: 'optional',
stretch: false
}
NOTE: set caption to optional
in order to configure caption as a tune.
This Tool returns data
with following format
Field | Type | Description |
---|---|---|
file | object | Uploaded file data. Any data got from backend uploader. Always contain the url property |
caption | string | image's caption |
withBorder | boolean | add border to image |
withBackground | boolean | need to add background |
stretched | boolean | stretch image to screen's width |
{
"type" : "image",
"data" : {
"file": {
"url" : "https://www.tesla.com/tesla_theme/assets/img/_vehicle_redesign/roadster_and_semi/roadster/hero.jpg"
},
"caption" : "Roadster // tesla.com",
"withBorder" : false,
"withBackground" : false,
"stretched" : true,
}
}
This Tool works by one of the following schemes:
Scenario:
config.endpoints.byFile
route)So, you can implement backend for file saving by your own way. It is a specific and trivial task depending on your environment and stack.
The tool executes the request as multipart/form-data
, with the key as the value of field
in configuration.
The response of your uploader should cover the following format:
{
"success" : 1,
"file": {
"url" : "https://www.tesla.com/tesla_theme/assets/img/_vehicle_redesign/roadster_and_semi/roadster/hero.jpg",
// ... and any additional fields you want to store, such as width, height, color, extension, etc
}
}
success - uploading status. 1 for successful, 0 for failed
file - uploaded file data. Must contain an url
field with full public path to the uploaded image.
Also, can contain any additional fields you want to store. For example, width, height, id etc.
All additional fields will be saved at the file
object of output data.
Scenario:
config.endpoints.byUrl
route) via 'url' in request bodyThe tool executes the request as application/json
with the following request body:
{
"url": "<pasted URL from the user>"
"additionalRequestData": "<additional request data from configuration>"
}
Response of your uploader should be at the same format as described at «Uploading files from device» section
Your backend will accept file as FormData object in field name, specified by config.field
(by default, «image
»).
You should save it and return the same response format as described above.
As mentioned at the Config Params section, you have an ability to provide own custom uploading methods.
It is a quite simple: implement uploadByFile
and uploadByUrl
methods and pass them via uploader
config param.
Both methods must return a Promise that resolves with response in a format that described at the backend response format section.
Method | Arguments | Return value | Description |
---|---|---|---|
uploadByFile | File | {Promise.<{success, file: {url}}>} | Upload file to the server and return an uploaded image data |
uploadByUrl | string | {Promise.<{success, file: {url}}>} | Send URL-string to the server, that should load image by this URL and return an uploaded image data |
Example:
import ImageTool from '@editorjs/image';
var editor = EditorJS({
...
tools: {
...
image: {
class: ImageTool,
config: {
/**
* Custom uploader
*/
uploader: {
/**
* Upload file to the server and return an uploaded image data
* @param {File} file - file selected from the device or pasted by drag-n-drop
* @return {Promise.<{success, file: {url}}>}
*/
uploadByFile(file){
// your own uploading logic here
return MyAjax.upload(file).then(() => {
return {
success: 1,
file: {
url: 'https://codex.so/upload/redactor_images/o_80beea670e49f04931ce9e3b2122ac70.jpg',
// any other image data you want to store, such as width, height, color, extension, etc
}
};
});
},
/**
* Send URL-string to the server. Backend should load image by this URL and return an uploaded image data
* @param {string} url - pasted image URL
* @return {Promise.<{success, file: {url}}>}
*/
uploadByUrl(url){
// your ajax request for uploading
return MyAjax.upload(file).then(() => {
return {
success: 1,
file: {
url: 'https://codex.so/upload/redactor_images/o_e48549d1855c7fc1807308dd14990126.jpg',,
// any other image data you want to store, such as width, height, color, extension, etc
}
}
})
}
}
}
}
}
...
});
FAQs
Image Tool for Editor.js
We found that @editorjs/image demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
A supply chain attack has been detected in versions 1.95.6 and 1.95.7 of the popular @solana/web3.js library.
Research
Security News
A malicious npm package targets Solana developers, rerouting funds in 2% of transactions to a hardcoded address.
Security News
Research
Socket researchers have discovered malicious npm packages targeting crypto developers, stealing credentials and wallet data using spyware delivered through typosquats of popular cryptographic libraries.