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

@moodlenet/system-entities

v0.8.1

Published

Access control Maintainance of all Moodlenet Entities

Downloads

24

Readme

MoodleNet Key value store

This package manages system's all installed authentication strategies

Glyphs : definezione !!! arango, collezioni, 2 tipi di collezioni, nodi , e edge, e.> dge crea relazioni tra nodi (definite tipo json), glyphs = struttura dei dati che può essere nodo o edge

node -> contengono le entità (oggetti di bussines) edge -> rappresentano un collegamento tra due nodi e possono avere altri dati come metadati a quella relazione esempio utente likes ---> altre entità

ho 3 collezioni utente nodo, likes è un edge ,

API

getMyUserNode node : read, create, edit ensureGlyphs

ensureGlyphs fullGlyphName = getCollectionName(pkgId, pkgGlyphName) Defs[collectionName]['kind'], Defs[collectionName]['type']

const opts: CollectionDefOpt = {
  kind: glyphOpts.kind,
  opts: glyphOpts.opts,
}

return { descriptor, opts, pkgGlyphName, fullGlyphName }

CollectionDefOptMap : lista delle collezioni dei packages, i package di norma inseriscono le collezioni in un unico db system-entities e possibile che un package si crea un db / collezione suo db

access control crea db , e permette di creare collezione

il db mette in relazione tutte le collezione, (attenzione alle collezioni di graph, dove i package mettono le entità condivise tra i package)

export type GlyphDefsMap<Defs extends Record<string, GlyphDef> = Record<string, GlyphDef>> = Defs

collectionsDefOptMap = { ..._coll_def_opt_map, [glyphName]: opts }  {} as CollectionDefOptMap,
 await arangoPkg.api('ensureCollections')({ defs: collectionsDefOptMap })

lib:

 createNode
 editNode
 createEdge
 readNode