I am using vega within a strictly secured network enclave. This
includes an appliance in the middle that rewrites all URLs
such that they go through a proxy. This even includes modification
of schema URLs that are embedded in application source code.
This change allows vega-schema-url-parser to work in these cases.
It simply removes the requirement that schema has to be immediately
prefixed by a '/'.
I am using vega within a strictly secured network enclave. This includes an appliance in the middle that rewrites all URLs such that they go through a proxy. This even includes modification of schema URLs that are embedded in application source code.
This change allows vega-schema-url-parser to work in these cases. It simply removes the requirement that schema has to be immediately prefixed by a '/'.