"schema" property when registering renderers about jsonary HOT 1 CLOSED

Ooh, ooh! How about the "filter" property is an object?

{
    schema: [...],
    readOnly: true,
    type: [...],
    filter: function (data, schemas, uiState) {...}
}

If a function is supplied, then it's wrapped up in one of these objects (as the "filter" property).

Could then assign each renderer a registration order, and have:

• universal list (not schema-specific) for each basic type (includes any with regex/string)
• for each basic type, have map from absolute schema URLs to list of renderers.

Have two copies of the above - read-only and read-write. Then when selecting a renderer, simply look up the URLs of all the schemas in the map for the appropriate writeability/type, and concatenate them all (along with the appropriate "universal list"). Sort the list, and pop them off until one matches.

That should scale better.

from jsonary.