clues - npm Package Compare versions

Comparing version 2.2.1 to 2.5.0-beta1

bower.json

 {
   "name": "clues",
-  "version": "2.2.1",
+  "version": "2.5.0",
   "main": "clues.js",
@@ -5,0 +5,0 @@ "scripts": [

clues.js

@@ -35,5 +35,5 @@ // clues.js (c) 2009-2014 [e-mail] @license MIT
 
-  clues.version = "2.2.1";
+  clues.version = "2.5.0";
 
-  clues.prototype.solve = function(fn,local,caller) {
+  clues.prototype.solve = function(fn,local,caller,fullref) {
     var self = this, ref, args;
@@ -48,2 +48,20 @@ local = local || {};
 
+      // If the reference contains dots we solve recursively
+      if (ref.indexOf('.') > -1) {
+        var keys = ref.split('.'),
+            key = keys.shift();
+        fullref = fullref ? fullref+'.'+key : key;
+        return self.solve(key,local,caller,fullref)
+          .then(function(d) {
+            while (key = keys.shift()) {
+              fullref += '.'+key;
+              d = d[key];
+              if (d && d.solve)
+                return self.facts[ref] = d.solve(keys.join('.'),local,caller,fullref);
+              if (!d) return self.Promise.rejected({ref: key, fullref : fullref, caller: caller, message: ref+' not defined', name: 'Undefined'});
+            }
+            return d;
+          });
+      }
+
       // If we can't find any logic, we check self and local before returning an error
@@ -56,3 +74,3 @@ if (self.logic[ref] === undefined) {
         if (typeof(self.options.fallback) === 'function') return self.facts[ref] = self.options.fallback.call(this,ref,local,caller);
-        return self.Promise.rejected({ref: ref, caller: caller, message: ref+' not defined', name: 'Undefined'});
+        return self.Promise.rejected({ref: ref, fullref: fullref || ref, caller: caller, message: ref+' not defined', name: 'Undefined'});
       }
@@ -98,2 +116,3 @@
         e.ref = e.ref || ref;
+        e.fullref = e.fullref || fullref;
         e.caller = e.caller || caller || '';
@@ -100,0 +119,0 @@ throw e;

package.json

 {
   "name": "clues",
-  "version": "2.2.1",
+  "version": "2.5.0-beta1",
   "description": "Lightweight logic tree solver using promises.",
@@ -5,0 +5,0 @@ "keywords": [

README.md

@@ -33,2 +33,5 @@ #### Breaking changes in version 2.0:
 
+##### Nesting
+Logic trees can contain clues objects that provide a separate fact/logic space for any sub-components.  This allows for example person1 and person2 to have identical logic trees without sharing the same facts.   Trees can be traversed using dot notation, either when solving by string or using the minification definition above.   See `recursive-test.js` in the test directory for examples.  (todo: more docs)
+
 ## API Reference
@@ -35,0 +38,0 @@

New alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Major refactor

Supply chain risk

Package has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.

Found 1 instance in 1 package

No v1

Quality

Package is not semver >=1. This means it is not stable and does not support ^ ranges.

Found 1 instance in 1 package

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Network access

Supply chain risk

This module accesses the network.

Found 1 instance in 1 package

Uses eval

Supply chain risk

Package uses dynamic code execution (e.g., eval()), which is a dangerous practice. This can prevent the code from running in certain environments and increases the risk that the code may contain exploits or malicious behavior.

Found 2 instances in 1 package

Dynamic require

Supply chain risk

Dynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.

Found 1 instance in 1 package

Environment variable access

Supply chain risk

Package accesses environment variables, which may be a sign of credential stuffing or data theft.

Found 3 instances in 1 package

Long strings

Supply chain risk

Contains long string literals, which may be a sign of obfuscated or packed code.

Found 1 instance in 1 package

Improved metrics

Number of lines in readme file

162

increased by1.89%

Number of low supply chain risk alerts

0

decreased by-100%

Number of medium supply chain risk alerts

1

decreased by-90%

Worsened metrics

Total package byte prevSize

37018

decreased by-84.77%

Number of package files

19

decreased by-36.67%

Lines of code

646

decreased by-89.63%

Number of low quality alerts

2

increased by100%

No dependency changes