New Case Study:See how Anthropic automated 95% of dependency reviews with Socket.Learn More
Socket
Sign inDemoInstall
Socket

vitessce-api

Package Overview
Dependencies
Maintainers
1
Versions
5
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

vitessce-api

**Work-in-progress!** Based on [create-openapi-repo](https://github.com/Redocly/create-openapi-repo), this describes an API [Vitessce](https://github.com/hms-dbmi/vitessce) could consume, and HuBMAP could provide.

  • 0.0.4
  • latest
  • npm
  • Socket score

Version published
Weekly downloads
2
decreased by-85.71%
Maintainers
1
Weekly downloads
 
Created
Source

vitessce-api OpenAPI Specification

Work-in-progress! Based on create-openapi-repo, this describes an API Vitessce could consume, and HuBMAP could provide.

Why?

When running on localhost, this provides much the same editing interface as Swagger. Contrasted with SwaggerHub, this approach provides:

  • The GitHub ecosystem we're familiar with.
  • We edit the spec as small files, and a build process assembles the monolithic OAS JSON.
  • Intermediate versions can be "published" to S3 for public review, without creating a new version number.
  • Final version is published to NPM where it can be referenced like any other dependency.

Out of the box, create-openapi-repo does provide a nice integration with Travis and GitHub Pages, but it doesn't match our needs right now:

  • Only the latest version is visible: Older versions could be regenerated, but they aren't accessible at a URL.
  • Waiting for Travis before merging is important, but it shouldn't be necessary to just show a work in progress.

There are things about this approach which do seem weird to me, and if there are other tools which better match our needs, please suggest them!

Develop

  1. Install Node JS.
  2. Clone repo and run npm install in the repo root.
  3. npm start launches the development server.

Running on localhost, you can make edits in the web interface and they will be saved to the local filesystem.

Publish

The publish scripts need jq: Install with homebrew/apt-get/etc..

Work should be done in a feature branch, rather than committing directly to master. When you have work you'd like others to see, run ./push-s3.sh: That will update the list at the bottom of this README.

When there's consensus on a new version of the API, make a release branch, bump the version number, and run ./push-npm.sh.

Use

On another project that wants to use the API spec, run npm install vitessce-api, and then in the code:

import { api } from 'vitessce-api';

console.log('Here is your API:', api);

Releases and Demos

Releases

See NPM.

Demos

datebranchversiongit hashas htmlas json
2019-07-11mccalluc/as-table0.0.4-rc4f446c6htmljson
2019-07-11mccalluc/fill-out-end-points0.0.4-rc1797738htmljson
0.0.4-rc
2019-07-11mccalluc/fill-out-end-points0.0.4e20910dhtmljson

FAQs

Package last updated on 12 Jul 2019

Did you know?

Socket

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.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc