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

seneca-vote

v1.0.1

Published

A voting plugin for Seneca.js

Downloads

4

Readme

seneca-vote

A voting plugin for Seneca.js

Contents:

Requirements

The following Seneca plugins must be plugged in before this plugin can be used:

  • seneca-entity
  • seneca-promisify

Normally, your code would look like this:

const Seneca = require('seneca')
const Entities = require('seneca-entity')
const SenecaPromisify = require('seneca-promisify')
const VotePlugin = require('seneca-vote')

Seneca()
  .use(Entities)
  .use(SenecaPromisify)
  .use(VotePlugin)

Actions

Action Descriptions

Upvote Action

Pattern

sys:vote,vote:up

Params

  • fields.poll_id_ : ID! : The ID of the poll to upvote on.
  • fields.voter_id_ : ID! : The ID of the voter.
  • fields.voter_type_ : "sys/user"! : The type of the voter. Currently only "sys/user" is supported.

Description

Creates an upvote for a poll. If the voter has already downvoted on the poll,
the downvote will be replaced by an upvote. On success, the number of upvotes
and downvotes are counted and included in the response.

Responses

Upon successful upvote:

{ ok: true, data: { num_upvotes: Int!, num_downvotes: Int! } }

Upon failed validation of the request params:

{
  ok: false,
  why: String,
  details?: { path: Array<Any>?, why_exactly: String? }
}

When the poll does not exist:

{ ok: false, why: String, details?: { what: String? } }

Downvote Action

Pattern

sys:vote,vote:down

Params

  • fields.poll_id_ : ID! : The ID of the poll to upvote on.
  • fields.voter_id_ : ID! : The ID of the voter.
  • fields.voter_type_ : "sys/user"! : The type of the voter. Currently only "sys/user" is supported.

Description

Creates an downvote for a poll. If the voter has already upvoted on the poll,
the upvote will be replaced by a downvote. On success, the number of upvotes
and downvotes are counted and included in the response.

Responses

Upon successful downvote:

{ status: "success", data: { num_upvotes: Int!, num_downvotes: Int! } }

Upon failed validation of the request params:

{
  ok: false,
  why: String,
  details?: { path: Array<Any>?, why_exactly: String? }
}

When the poll does not exist:

{ ok: false, why: String, details?: { what: String? } }

Open Poll Action

Pattern

sys:vote,open:poll

Params

  • fields.title_ : string! : The title of the poll.

Description

Creates a new poll with the given title. If a poll with the given title already exists,
then action will nontheless succeed, but a new poll will not be created. On success,
the poll data is returned.

Responses

Upon success:

{
  status: "success",
  
  data: {
    poll: {
      id: ID!,
      title: String!,
      created_at: Date!,
      updated_at: Date?
    }
  }
}

Upon failed validation of the request params:

{
  ok: false,
  why: String,
  details?: { path: Array<Any>?, why_exactly: String? }
}

Get Poll Action

Pattern

sys:vote,get:poll

Params

  • poll_id_ : ID! : The ID of the poll to get.

Description

Upon success, returns the poll data. Returns an error message if the poll with
the given ID does not exist.

Responses

Upon success:

{
  status: "success",
  
  data: {
    poll: {
      id: ID!,
      title: String!,
      created_at: Date!,
      updated_at: Date?
    }
  }
}

Upon failed validation of the request params:

{
  ok: false,
  why: String,
  details?: { path: Array<Any>?, why_exactly: String? }
}

When the poll does not exist:

{ ok: false, why: String, details?: { what: String? } }

Plugin Options

locks_disabled : Boolean? By default, this option is set to true, i.e. locks are disabled by default. If set to false, re-enabled locks which help prevent potential race conditions in actions.

During implementation work on seneca-vote, in order to meet certain MVP requirements, such as that there can only ever be a single poll record with the same title, - locks were implemented as part of seneca-vote to prevent race conditions, that may otherwise occur under high loads.

It was ultimately decided to disable the locks by default in order to comply with the rest of the Seneca eco-system. Entity upserts are planned to be added to Seneca entities in the future. They will work as upserts normally do:
https://docs.mongodb.com/drivers/node/fundamentals/crud/write-operations/upsert/
https://www.postgresqltutorial.com/postgresql-upsert/

Further work on the data model of seneca-vote is expected in order to both prevent race conditions and remain compliant with the rest of the Seneca eco-system.

Dev Scripts

$ npm test
Runs the automated tests.

$ npm run check-coverage
Generates a test coverage report.

$ npm run reset Sometimes when the project starts acting weird, the first go-to solution may be to go ahead and refresh (i.e. reinstall) the packages used in the project. This command does just that.

$ npm run clean Normally this command is not meant to be invoked explicitly, and is generally meant for consumption by other scripts in the project.