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

@graphiy/actionman

v0.2.4

Published

Actions mananger

Downloads

3

Readme

.. image:: https://travis-ci.org/Graphiy/actionman.svg?branch=master :target: https://travis-ci.org/Graphiy/actionman |

Graphiy Actionman

Arbitrary implementation of Command design pattern <https://en.wikipedia.org/wiki/Command_pattern>_ for cross-modules communication with logging. This enables undo / redo and actions log functionality.

Functionality

  • action panel button click - fire action
  • enable / disable action
  • action panel toggle button
  • multiple components subscribe to action
  • some components subscribe / some not
  • granular update (providing component ids while firing an action)
  • action log
  • undo / redo
  • ADD TO DEMO: evalutate if the action can be executed

TODO

- multiple steps undo / redo
- queue of actions
- Sequences of Command objects can be assembled into composite (or macro) commands.

Consideration on implementation
  • Any action should have "id" differentiation? in terms of "check at a dinner" example: specifying id for the action is telling the Waiter, that Customer want a specific person to cook for him, while this person may or may not be available today or even be a Cook in this restoraunt.
    • first param of action.apply is always ids array
    • How to fire an action for all ids?
      • pass 'all'
      • do not specify any
  • Does actionman is required / able to keep track of all actions?
    • YES, Actionman is by it's name a manager of actions
  • How to undo / redo?
    • Should Undo / Redo be actions too?
      • No, because it is not specific to particular registrar
    • actionman.undo()
      • the way to trigger undo of the last action
    • concreteAction.undo()
      • actual way to undo
  • Should Actionman be a singleton
    • Pros
      • no need to pass the reference to actionman around to each consumer
    • Cons
      • there will be no ability to create multiple instances of application on the same page for them to track their actions independently
  • Should Action be a singleton?
    • Pros
      • same as for actionman
    • Cons
      • same as for actionman
      • if not a singleton, consumer needs to ask actionman for an action