• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

bluealba / rules-js
99%
master: 97%

Build:
Build:
LAST BUILD BRANCH: 0.2.0
DEFAULT BRANCH: master
Repo Added 15 Sep 2017 09:49PM UTC
Files 22
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

LAST BUILD ON BRANCH feature/rename-named-closures-to-provided-closures
branch: feature/rename-named-closures-to-provided-closures
CHANGE BRANCH
x
Reset
  • feature/rename-named-closures-to-provided-closures
  • 0.2.0
  • builtin-transformers
  • closure-library
  • closure-parameters-accept-literal
  • date-range-builtin-closure
  • daterange-empowered
  • feature/conditional-reducers
  • feature/date-range-rules
  • feature/make-synchronic
  • feature/named-closures
  • feature/refactor-all-closures-can-be-bounded
  • feature/reference-named-closures-by-name
  • master
  • v0.0.11
  • v0.0.2-alpha
  • v0.0.3
  • v0.0.5
  • v0.0.6
  • v0.0.7
  • v0.0.8
  • v0.1.0

pending completion
9

push

travis-ci

aitrusgit
rename named closures to provided closures

since any closure can be actually named (rules and rule flows are
almost always named for trace sake). Actually, we are moving towards
allowing any named closure (even rules and flows) to be refenced
through its name. This will allow to reuse complex rule flows in,
by example, different rules execution branches.

31 of 31 branches covered (100.0%)

Branch coverage included in aggregate %.

130 of 131 relevant lines covered (99.24%)

143.47 hits per line

Relevant lines Covered
Build:
Build:
131 RELEVANT LINES 130 COVERED LINES
143.47 HITS PER LINE
Source Files on feature/rename-named-closures-to-provided-closures
  • List 0
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
9 feature/rename-named-closures-to-provided-closures rename named closures to provided closures since any closure can be actually named (rules and rule flows are almost always named for trace sake). Actually, we are moving towards allowing any named closure (even rules and flows) to be refenced thr... push 16 Sep 2017 05:47PM UTC aitrusgit travis-ci pending completion  
See All Builds (54)
  • Repo on GitHub
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2025 Coveralls, Inc