Improvement for the declaration of the props, new configuration property "instanceof"

[UpperCod]

In addressing this, I noticed a bug in Atomico current validation, which I've fixed in Atomico@1.45.0, which fix introduced instanceof validation by default, you can learn more about this in the release /~https://github.com/atomicojs/atomico/releases/tag/1.45.0

The goal of this feature is to improve the way of declaring types in Atomico, allowing input values not only to depend on the type, but also on the type of the instance, example:

Now Atomico is strict when defining types

component.props = { el: { type: Element } };

const Component = c(component);

const componentInstance = new Component;

componentInstance.el = document.createElement("div"); // Error!

but with this new property we can check not by strict type but by instance of the constructor

component.props = { el: { type: Element, instanceof: true } };

const Component = c(component);

const componentInstance = new Component;

componentInstance.el = document.createElement("div"); // Success!

This will allow your web component to work internally with custom Constructors.

class MyObject{}

component.props = { el: { type: MyObject, instanceof: true } };

const Component = c(component);

const componentInstance = new Component;

componentInstance .el = new MyObject// Success!

componentInstance .el = {}// Error!

[UpperCod]

I have analysed, I think it is more feasible for this to be automatic without the need to use instanceof, limiting simple types to typeof and unknown types to instanceof ...

Atomico validation is really simple /~https://github.com/atomicojs/atomico/blob/master/src/element/set-prototype.js#L146-L153.

const filterValue = (type, value) =>
    type == Any
        ? { value }
        : type != String && value === ""
        ? { value: null }
        : {}.toString.call(value) == `[object ${type.name}]`
        ? { value, error: type == Number && Number.isNaN(value) }
        : { value, error: true };