npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

slate-bad-table

v0.1.3

Published

An ugly solution for nested table in Slate

Downloads

29

Readme

slate-bad-table

A slate plugin to handle table nested with block; this plugin is expected to be used with GitbookIO/slate-edit-table

Install

npm i --save slate-bad-table

Features

  1. Provides customized getFragmentAtRange and deleteAtRange for copy/paste
  2. Provides rules for customizing your own getFragmentAtRange and deleteAtRange

Simple Usage

import createBadTablePlugin from 'slate-bad-table';
const plugins = [createBadTablePlugin()]

Arguments

  • [typeBadTable: 'bad-table'] string for the table type
  • [typeBadRow: 'bad-table-row'] string for the row type
  • [typeBadCell: 'bad-table-cell'] string for the cell type
  • [typeParagraph: 'paragraph'] string for paragraph type

Utils

utils.getFragmentAtRange(node: Node, range: Range): Document

Customized method for copying. The method memics the default node.getFragmentAtRange, but tries to avoid bad-table* in the returned fragment;

utils.isSelectionInCell(value: Value): boolean

Return true if selection is inside a bad-table-cell

utils.isSelectionOutOfCell

Return true if selection starts and ends both outside any bad table. (Notice: it is NOT the opposite value of isSelectionInCell)

Changes

changes.deleteAtRange(change: Change, range: Range, {normalize: true}) : Change

Customized method for delete and paste at range. The method memics the default change.deleteAtRange, but tries to keep valid bad tables. Optional option normalize is for enable/disable normalization after deleteAtRange

changes.removeTable(value:Value, {snapshot: true}) => Change

remove bad-table if the focus is in the table

changes.removeRow(value:Value, {snapshot: true}) => Change

remove bad-table-row if the focus is in the row;

changes.removeRow(value:Value, {snapshot: true}) => Change

remove bad-table-row if the focus is in the row;

Rules

Rules for rules-combinator for customizing copy/paste logic with other plugins

rules.getFragmentAtRange: Array< ( getFragmentAtRange: (Node, Range) => Document, node: Node, range: Range, next: () => Document ): Document >
  • getFragmentAtRange for the root function entry, used for node or range change; You can see example of usage at lib/rules/getFragmentAtRange/ifStartInCell
  • node, range: node and range
  • next evaluate the following rules for binding rules, see example at lib/rules/getFragmentAtRange/index
rules.deleteAtRange: Array< ( deleteAtRange: (Change, Range) => Change, node: Node, range: Range, next: () => Change ): Change >
  • deleteAtRange for the root function entry, used for range change; You can see example of usage at lib/rules/deleteAtRange/ifStartInCell
  • change, range: change and range
  • next evaluate the following rules for binding rules, see example at lib/rules/deleteAtRange/index