URI.escape has been obsolete for some time -- but only recently started printing deprecation warnings.
I checked on what to do here, I thought there would be a proper way to escape, but it turns out that individual URI components should be escaped separately.
These particular methods only handle the scheme, host, base_url, base_path and path variables. Typically, all we really care about for escaping is the query params, which get handled separately, so this should be safe.
closes #12
URI.escapehas been obsolete for some time -- but only recently started printing deprecation warnings.I checked on what to do here, I thought there would be a proper way to escape, but it turns out that individual URI components should be escaped separately.
These particular methods only handle the
scheme,host,base_url,base_pathandpathvariables. Typically, all we really care about for escaping is the query params, which get handled separately, so this should be safe.TODO: