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

@partially-applied/material-dropdown

v0.0.2

Published

material dropdown

Downloads

6

Readme

DropDown

Model

(component wont work if options and default is not passed)

Model =
 options: # What options the dropdown shows
  "Afghanistan"
  "Bahamas"
  "Cambodia"
  "India"
  "Pakistan"
  "USA"
  "UK"
  "Canada"
  "Ukraine"
 default:2 # Since options is an array - provide default value 
 onchange:[] # attach either an array of functions or just a single function on onchange to get 
 # notification  when the user interacts with the dropdown. the event handler returns the Model 
 # Object with Model.value updated.

Params


### Params

defaultParams = 
  scroll:
    style:
      padding-left:"1em"
      padding-right:"1em"
    maxHeight:"10em"
  valuebox:
    style:
      padding-bottom:"0.1em"

How to use


createDropDown = require "./dropdown" # Returns vNode constructor function.
VNode = createDropDown Model,Params # returns the VNode, accepts 2 objects - models and params. 

Notes

In situations where the model is changed exterally or via another componenet we could have exposed a VNode.data.redraw() function, however this requires that other components which updates model values to know the dependency graph / information about each Model value.

Its much simpler to let onchange keep track of dependencies and update them.

How does it work ?

Observe

console.log Model.onchange # => []
VNode = createDropDown Model,Params 
console.log Model.onchange # => [fn]

The component constructor pushes the update function onto the Model.onchange array.

What this means is all long as any other componenet that makes changes on Model calls all the functions attached to onchange all the component level redraws gets called, and each component does not need to keep track of other components effected by changing the model.

Using the './utils' helpers functions in this component.

# ./fooComponent

{eventReact,Events} = require './utils'

create = (Model,Params2 = {}) -> # Model is same as above
  #....
  #....
  #....

  Ctrl = {}

  Ctrl.Model = Model 

  signalFn = Events update Ctrl # Ctrl.Model is passed onto update function
  
  #....
  #....
  #....


update = (Ctrl,signalOb) -> 
  
  
  #....
  #....
  #....

  {Model} = Ctrl # Extract Model

  switch signalOb.eventName

  #....
  #....
  #....

  | "makeModelChanges" => # some signal that notifes that some change needs to be made to the Model

    Model.value = 6 # make some change to model

    eventReact Model # Update other components that depend on Model

  #....
  #....
  #....

How you structure fooComponent is based on what you think is best - but the important thing is to call all functions attached to onchange.