Previous:
Defining Custom Block Nodes


Applying Custom Formatting

In the previous guide we learned how to create custom block types that render chunks of text inside different containers. But Slate allows for more than just "blocks".

In this guide, we'll show you how to add custom formatting options, like bold, italic, code or strikethrough.

So we start with our app from earlier:

class App extends React.Component {

  state = {
    state: initialState,
    schema: {
      nodes: {
        code: CodeNode
      }
    }
  }

  onChange = ({ state }) => {
    this.setState({ state })
  }

  onKeyDown = (event, data, change) => {
    if (event.which != 67 || !event.metaKey || !event.altKey) return
    event.preventDefault()
    const isCode = change.state.blocks.some(block => block.type == 'code')

    change.setBlock(isCode ? 'paragraph' : 'code')
    return true
  }

  render() {
    return (
      <Editor
        state={this.state.state}
        schema={this.state.schema}
        onChange={this.onChange}
        onKeyDown={this.onKeyDown}
      />
    )
  }

}

And now, we'll edit the onKeyDown handler to make it so that when you press ⌘-B, it will add a "bold" mark to the currently selected text:

class App extends React.Component {

  state = {
    state: initialState,
    schema: {
      nodes: {
        code: CodeNode
      }
    }
  }

  onChange = ({ state }) => {
    this.setState({ state })
  }

  onKeyDown = (event, data, change) => {
    if (!event.metaKey) return

    // Decide what to do based on the key code...
    switch (event.which) {
      // When "B" is pressed, add a "bold" mark to the text.
      case 66: {
        event.preventDefault()
        change.addMark('bold')
        return true
      }
      // When "`" is pressed, keep our existing code block logic.
      case 67: {
        if (!event.altKey) return
        const isCode = change.state.blocks.some(block => block.type == 'code')
        event.preventDefault()
        change.setBlock(isCode ? 'paragraph' : 'code')
        return true
      }
    }
  }

  render() {
    return (
      <Editor
        schema={this.state.schema}
        state={this.state.state}
        onChange={this.onChange}
        onKeyDown={this.onKeyDown}
      />
    )
  }

}

Okay, so we've got the hotkey handler setup... but! If you happen to now try selecting text and hitting ⌘-B, you'll get an error in your console. That's because we haven't told Slate how to render a "bold" mark.

For every mark type you want to add to your schema, you need to give Slate a "renderer" for that mark, just like nodes. So let's define our bold mark:

// Define a React component to render bold text with.
function BoldMark(props) {
  return <strong>{props.children}</strong>
}

Pretty simple, right?

And now, let's tell Slate about that mark. To do that, we'll add it to the schema object under a marks property. Also, let's allow our mark to be toggled by changing addMark to toggleMark.

function BoldMark(props) {
  return <strong>{props.children}</strong>
}

class App extends React.Component {

  state = {
    state: initialState,
    schema: {
      nodes: {
        code: CodeNode
      },
      // Add our "bold" mark to the schema...
      marks: {
        bold: BoldMark
      }
    }
  }

  onChange = ({ state }) => {
    this.setState({ state })
  }

  onKeyDown = (event, data, change) => {
    if (!event.metaKey) return

    switch (event.which) {
      case 66: {
        event.preventDefault()
        change.toggleMark('bold')
        return true
      }
      case 67: {
        if (!event.altKey) return
        const isCode = change.state.blocks.some(block => block.type == 'code')
        event.preventDefault()
        state.setBlock(isCode ? 'paragraph' : 'code')
        return true
      }
    }
  }

  render() {
    return (
      <Editor
        schema={this.state.schema}
        state={this.state.state}
        onChange={this.onChange}
        onKeyDown={this.onKeyDown}
      />
    )
  }

}

Now, if you try selecting a piece of text and hitting ⌘-B you should see it turn bold! Magic!


Next:
Using Plugins


results matching ""

    No results matching ""