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

@deep-foundation/object-to-links-async-converter

v0.0.1

Published

A deep package for converting object to links

Downloads

17

Readme

npm Gitpod Commitizen friendly

A deep package for converting object to links

Usage

  1. Install the package
  2. Give permissions to the package
  3. Insert Root link
  4. Update object value of Root link
  5. Insert ParseIt link from Root to Root
  6. See links created around Root link

FAQ

Must I use Root type

It is not required to use Root type but it is recommended to use it because this type is added to the tree
If you want to use your own type you should add it to tree of this package by creating TreeIncludeNode from tree of this package to your type

Must ParseIt.from and ParseIt.to be equal?

ParseIt.from must point to a link with object value, ParseIt.to can point to any link and new links will be created around ParseIt.to

How new links will look like?

Let us imagine we have this object and it is called MyLink:

{
  "myObject": {
    "myStringField": "myStringValue",
    "myNumberField": 123,
    "myBooleanField": true
  }
}

These links will be created:
Object around MyLink (from and to are pointing to your link)
Contain with value myObject from MyLink to Object
String with value myStringValue from Object to Object
Contain with value myStringField from Object to String
Number with value 123 from Object to Object
Contain with value myNumberField from Object to Number
Boolean from Object to true or false (from the @deep-foundation/boolean package)
Contain with value myBooleanField from Object to Boolean

How to programmatically wait until converting is done?

Use DeepClient.await method:

await deep.await(parseItLinkId);

Links are not created, nothing happened after inserting ParseIt

See PromiseResult for your ParseIt link

Using DeepCase

  • Press right mouse button on ParseIt link and select Traveller
  • Select Down
  • Select PromiseTree

You will see all the links down by promiseTree for "parent" ParseIt:

  • Then from YourLink to Promise
  • Promise
  • Rejected or Resolved from Promise to PromiseResult
  • PromiseResult

If you see Resolved link then handler was executed successfully, if you see Rejected link then handler was executed with error You can see the error in PromiseResult link value

Limitations

If you delete field in your object value and parse it again - link associated with that field will not be deleted. This feature will be implemented in the future!

Feedback

Feel free to open issues to write there about bugs, improvement requests, questions