boolbase

WebJar for boolbase

License

License

ISC
GroupId

GroupId

org.webjars.npm
ArtifactId

ArtifactId

boolbase
Last Version

Last Version

1.0.0
Release Date

Release Date

Type

Type

jar
Description

Description

boolbase
WebJar for boolbase
Project URL

Project URL

http://webjars.org
Source Code Management

Source Code Management

https://github.com/fb55/boolbase

Download boolbase

How to add to project

<!-- https://jarcasting.com/artifacts/org.webjars.npm/boolbase/ -->
<dependency>
    <groupId>org.webjars.npm</groupId>
    <artifactId>boolbase</artifactId>
    <version>1.0.0</version>
</dependency>
// https://jarcasting.com/artifacts/org.webjars.npm/boolbase/
implementation 'org.webjars.npm:boolbase:1.0.0'
// https://jarcasting.com/artifacts/org.webjars.npm/boolbase/
implementation ("org.webjars.npm:boolbase:1.0.0")
'org.webjars.npm:boolbase:jar:1.0.0'
<dependency org="org.webjars.npm" name="boolbase" rev="1.0.0">
  <artifact name="boolbase" type="jar" />
</dependency>
@Grapes(
@Grab(group='org.webjars.npm', module='boolbase', version='1.0.0')
)
libraryDependencies += "org.webjars.npm" % "boolbase" % "1.0.0"
[org.webjars.npm/boolbase "1.0.0"]

Dependencies

There are no dependencies for this project. It is a standalone project that does not depend on any other jars.

Project Modules

There are no modules declared in this project.

boolbase

This very simple module provides two basic functions, one that always returns true (trueFunc) and one that always returns false (falseFunc).

WTF?

By having only a single instance of these functions around, it's possible to do some nice optimizations. Eg. css-select uses these functions to determine whether a selector won't match any elements If that's the case, the DOM doesn't even need to be touched.

And why is this a separate module?

I'm trying to modularize css-select and most modules depend on these functions. IMHO, having a separate module is the easiest solution to this problem.

Versions

Version
1.0.0