@yelworc
Yeah, you are absolutely right, actually ideally this would be oneOf instead of anyOf:
https://github.com/axa-ch/json-logic-js/blob/d56799465c6ce011c23f09d45267bba55ae55ec7/schemas/common/any.json#L8

and maybe it works if object is removed from all-types here:
https://github.com/axa-ch/json-logic-js/blob/d56799465c6ce011c23f09d45267bba55ae55ec7/schemas/common/all-types.json#L7

ACTUALLY IF I CHECK THE ORIGINALL CODE, IT SEEMS WOULD BE OKAY TO REMOVE object:

Lines 209 to 219 in a15f528

    
           jsonLogic.apply = function(logic, data) { 
        
             // Does this array contain logic? Only one way to find out. 
        
             if(Array.isArray(logic)) { 
        
               return logic.map(function(l) { 
        
                 return jsonLogic.apply(l, data); 
        
               }); 
        
             } 
        
             // You've recursed to a primitive, stop! 
        
             if( ! jsonLogic.is_logic(logic) ) { 
        
               return logic; 
        
             }

Indeed jsonLogic.apply and all it's operands are very forgiving, so I decided to start with a forgiving schema.
The first arg could also just be a boolean, as documented here:
https://github.com/jwadhams/json-logic-js#always-and-never

But I agree with you it's rather paradox and makes these schemas kinda pointless.
Though you can still replace all-types and any with your own.

Also it is possibly to nest any operator within each other, but semantically this is pointless too.
An ideal schema would also test, that a given operator makes sense.

I would also really like to get the inventors feedback @jwadhams
What do you think?

Edit:
Tracked here axa-ch#15

	jsonLogic.apply = function(logic, data) {
	// Does this array contain logic? Only one way to find out.
	if(Array.isArray(logic)) {
	return logic.map(function(l) {
	return jsonLogic.apply(l, data);
	});
	}
	// You've recursed to a primitive, stop!
	if( ! jsonLogic.is_logic(logic) ) {
	return logic;
	}

JSON Schema #55

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions