New Research: Supply Chain Attack on Axios Pulls Malicious Dependency from npm.Details →
Socket
Book a DemoSign in
Socket

router3

Package Overview
Dependencies
Maintainers
1
Versions
5
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

router3

A simple router tag called router3

latest
Source
npmnpm
Version
0.0.7
Version published
Weekly downloads
6
20%
Maintainers
1
Weekly downloads
 
Created
Source

router3

The second try for writting a normal and simple router tag

How to?

Wanna see it in action? Check the demos

Is it working? Check the tests

TODO

Still I've to develop some things...

  • Add a relative tag. The idea is located at test/case2 (is it necessary?)
  • Make possible to define nested views inside the src=url file
  • Dispatch show/hide events for default routers

Demo

Check the demos' source code. They can give you a big picture about what I want to develop.

Usage

If you can express your idea in HTML then you can express it in JS

A router is an HTML tag that defines a region that browser shows when window.location.hash matches the router's hash attribute.

Check this simple example:

<router3 hash="page1">
  Some HTML content
</router3>
<a href="#page1">Show page1</a>

If click over the anchor then the router becomes visible. Otherwise it's hidden.

The full set of attributes that are present in the router3 tag are:

  • hash [string] or "regexp"
  • src [string] points to an absolute URL
  • class-hide [string] the class that will appear instead of hidden
  • class-show [string] the class that will appear when not hidden

A second example that allows to fetch HTML code from outside

<router3 hash="page1" src="/page1.hml">
  Some default html code
  <router3-src></router3-src>
  More html code
</router3>
<a href="#page1">Show page1</a>

In this second example you should care about the /absolute URL path. The tag <router3-src> holds everything that comes from /page1.html. If this tag is not indicated, by default it will be appended via appendChild as indicated here.

Events

If src is defined for a router them it can accept the load event, e.g.

<router3 hash="page1" src="/page1.html"></router3>
<script>
  document
    .querySelector('router3[hash="page1"]')
    .addEventListener('load', e => {
    // this event will be executed after
    // the browser loads the url /page1.html
  });
</script>

When a router matches a window.location.hash then the show / hide events are dispatched, e.g.

<router3 hash="page1">
  some content
</router3>
<script>
  document
    .querySelector('router3[hash="page1"]')
    .addEventListener('show', e => {
    // this event will be executed after
    // the browser changes its hash to #page1
  });
  document
    .querySelector('router3[hash="page1"]')
    .addEventListener('hide', e => {
    // this event will be executed after
    // the browser changes its hash to something
    // different than #page1
  });
</script>

Default router

The default router can be achieved if set hash="". E.g.

<router3 hash="page1" src="/page1.html"></router3>
<router3 hash="">A default view</router3>

So, if window.location.hash === 'page1' then router[hash="page1"] is visible.

But, if window.location.hash === '' then router[hash=""] is visible and the other is hidden.

Keywords

routing

FAQs

Package last updated on 22 Aug 2016

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts