typexjs/source/matrix/assets/scripts/js/parts/_dom_.js

Prism

const DOM_siblings__a = selector_s =>
{
  const node_e = document.querySelector( selector_s )
  return !node_e ?
    null :
    Array.prototype.filter
      .call( node_e.parentNode.children, sibling_e => sibling_e !== node_e )
}


const DOM_listReverse__v = selector_s =>
{
  const node_a = Array.prototype.slice.call(document.querySelectorAll( `${selector_s} li` ))
  node_a.forEach( node_e => node_e.parentNode.insertBefore( node_e, node_e.parentNode.firstChild ) )
}

The previous code shows an exception to the specifiers convention used by TypexJS: for DOM elements, it seems more appropriate to use the _e suffix for element, because the _N suffix is already used for a Null value than the _o suffix used for Object.

The example code shows another singularity: we can instantly differenciate JavaScript and browser specific functions or methods from our own code functions and methods. Our identifiers have a letter suffix where JS and browser identifiers have nothing. Therefore, we can safely use exactly the same names:

const myWindow = window
const window_o = window // smarter isn't it?

Hence, everytime we want to override some JavaScript or DOM function or any browser specific, third-party library function, etc. , we can safely do it while keeping a semantic coherency with the original function.