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

overlapr

v1.0.2

Published

A range overlap detection tool for graphical representation

Downloads

11

Readme

Overlapr

Overlapr is a conflict detection tool that will help you represent them graphically on your UI, regardless of the application.

Installation

Yarn

yarn add overlapr

NPM

npm install overlapr

Usage

import overlapr from 'overlapr'

const data = overlapr.processData(rawData)
const {start, end, width, height, offset} = data['some-id']

Demo

https://codesandbox.io/p/github/ntocampos/overlapr-demo/main

API

Input

The main function expects an array of objects to be analyzed as its first parameter. Each of those objects should have at least the following properties:

type InputObject = {
  id?: string,
  start?: number,
  end?: number,
}[]

It's ok to have more properties tho, they will just be ignored by Overlapr.

As we can see, all attributes are optional because your objects might not have this specific format and it might be too expensive to transform them before passing in Overlapr. That's where the config parameter comes in. There, you can define custom getters for each one of those attributes, like so:

type Config = {
  getId?: (InputObject) => string,
  getStart?: (InputObject) => number,
  getEnd?: (InputObject) => number,
}

With this configuration object, you can have your input property values in any way you want, as long as getter functions return the correct data.

Notice that either one of those (be it the attribute or the attribute getter in the config) is necessary in order to get Overlapr working property. This means that you can have the id and end properties defined, but use the getStart function to get the start values.

Output

After running Overlapr on your entity collection, you'll get a hash object as the output, having your input IDs as the keys and OverlapItems as the values. The OverlapItem object contains information about the conflicts and how to render them on your UI. It follows the following format:

type OverlapItem = {
  _original: InputObject
  id: string
  start: number
  end: number
  depth: number
  conflicts: string[]
  context: number
  offset: number
  width: number
  height: number
}

type Output = {
  _ordered: OverlapItem[],
  [id: string]: OverlapItem,
}

Here's an explanation of each one of those attributes. For detailed information with examples, please refer to the specs.

  • _original: the original object from your input. It's here just for convenience, in case you need to easily access it when using the output data.
  • id: your entry's ID.
  • start: the start of the range. The same you provided via start attribute or getStart getter.
  • end: the end of the range. The same you provided via end attribute or getEnd getter.
  • depth: the depth where this element is positioned. It is used internally when calculating the context, width, and offset. It's made available just in case you need it for some reason, but you shouldn't need it.
  • conflicts: an array containing the IDs of the elements that this entry overlaps.
  • context: this represents the number of columns in the cluster in which this entry is inserted. It's used internally when calculating the width and offset for the entries.
  • offset: this is the entry's offset relative to the cross-axis. Where it should start.
  • width: the length of this entry relative to the cross-axis.
  • height: the length of this entry relative to the main axis. This is calculated simply as end - start.

Contributing

Pull requests are welcome, but please open an issue first to discuss what you would like to change before opening the pull request.

Please make sure to update tests as appropriate.

License

MIT