diff --git a/pkg/analysis_server/doc/api.html b/pkg/analysis_server/doc/api.html index e8e7e184acf..59d6ae528d4 100644 --- a/pkg/analysis_server/doc/api.html +++ b/pkg/analysis_server/doc/api.html @@ -2534,6 +2534,7 @@ a:focus, a:hover { +
This section contains descriptions of the data types referenced @@ -2567,6 +2568,8 @@ a:focus, a:hover { + + @@ -3500,7 +3503,72 @@ a:focus, a:hover {
The names of the elements imported from the library.
-+ This object matches the format and documentation of the Entry object documented in the + Kythe Storage Model. +
+ ++ The ticket of the source node (must not be empty). +
++ An edge label (may be empty). The schema defines which labels are meaningful. +
++ The ticket of the target node (may be empty). +
++ A fact label (must not be empty). The schema defines which fact labels are meaningful. +
++ The String value of the fact (may be empty). +
++ This object matches the format and documentation of the Vector-Name object documented in the + Kythe Storage Model. +
+ ++ An opaque signature generated by the analyzer. +
++ The corpus of source code this KytheVName belongs to. Loosely, a corpus is a + collection of related files, such as the contents of a given source repository. +
++ A corpus-specific root label, typically a directory path or project identifier, denoting a + distinct subset of the corpus. This may also be used to designate virtual collections like generated files. +
++ A path-structured label describing the “location” of the named object relative to the corpus + and the root. +
++ The language this name belongs to. +
+A collection of positions that should be linked (edited simultaneously) for the purposes of updating code after a source change. For example, if a @@ -4679,7 +4747,7 @@ a:focus, a:hover { TODO: TBD