ProtectedconstructorOptionalauthority: stringOptionalpath: stringOptionalquery: stringOptionalfragment: stringOptional_strict: booleanReadonlyauthorityauthority is the 'www.msft.com' part of 'http://www.msft.com/some/path?query#fragment'. The part between the first double slashes and the next slash.
Readonlyfragmentfragment is the 'fragment' part of 'http://www.msft.com/some/path?query#fragment'.
ReadonlyfsReturns a string representing the corresponding file system path of this URI. Will handle UNC paths, normalizes windows drive letters to lower-case, and uses the platform specific path separator.
The difference to URI#path is the use of the platform specific separator and the handling
of UNC paths. See the below sample of a file-uri with an authority (UNC path).
const u = URI.parse('file://server/c$/folder/file.txt')
u.authority === 'server'
u.path === '/shares/c$/file.txt'
u.fsPath === '\\server\c$\folder\file.txt'
Using URI#path to read a file (using fs-apis) would not be enough because parts of the path,
namely the server name, would be missing. Therefore URI#fsPath exists - it's sugar to ease working
with URIs that represent files on disk (file scheme).
Readonlypathpath is the '/some/path' part of 'http://www.msft.com/some/path?query#fragment'.
Readonlyqueryquery is the 'query' part of 'http://www.msft.com/some/path?query#fragment'.
Readonlyschemescheme is the 'http' part of 'http://www.msft.com/some/path?query#fragment'. The part before the first colon.
There is quite some magic in to vscode URI class related to transferring via JSON.stringify(). Making the CodeURI instance makes sure we transfer this object as a vscode-uri URI.
Creates a string representation for this URI. It's guaranteed that calling
URI.parse with the result of this function creates an URI which is equal
to this URI.
OptionalskipEncoding: booleanDo not encode the result, default is false
Override to create the correct class.
StaticfileCreates a new URI from a file system path, e.g. c:\my\files,
/usr/home, or \\server\share\some\path.
The difference between URI#parse and URI#file is that the latter treats the argument
as path, not as stringified-uri. E.g. URI.file(path) is not the same as
URI.parse('file://' + path) because the path might contain characters that are
interpreted (# and ?). See the following sample:
const good = URI.file('/coding/c#/project1');
good.scheme === 'file';
good.path === '/coding/c#/project1';
good.fragment === '';
const bad = URI.parse('file://' + '/coding/c#/project1');
bad.scheme === 'file';
bad.path === '/coding/c'; // path is now broken
bad.fragment === '/project1';
A file system path (see URI#fsPath)
StaticfromStaticisStaticjoinCreate a new uri which path is the result of joining the path of the base uri with the provided path segments.
joinPath only affects the path component
and all other components (scheme, authority, query, and fragment) are
left as they are.The path segments are normalized in the following ways:
/ or \) are replaced with a single separatorfile-uris on windows, the backslash-character (``) is considered a path-separator..-segment denotes the parent segment, the . denotes the current segmentjoinPath(Uri.file('file:///c:/root'), '../../other').fsPath === 'c:/other'One more more path fragments
A new uri which path is joined with the given fragments
StaticparseCreates a new URI from a string, e.g. http://www.msft.com/some/path,
file:///usr/home, or scheme:with/path.
A string which represents an URI (see URI#toString).
Optional_strict: booleanStaticreviveOverride to create the correct class.
This is an implementation of #theia.Uri based on vscode-uri. This is supposed to fix https://github.com/eclipse-theia/theia/issues/8752 We cannot simply upgrade the dependency, because the current version 3.x is not compatible with our current codebase