Hover
Hover Type
If there is JSON Schema information, Tombi will display executable types as hover information as shown in the following table.
| JSON Schema | Hover Type |
|---|---|
type: boolean | Boolean |
type: integer | Integer |
type: number | Float |
type: string | String |
type: string, format: date-time | OffsetDateTime |
type: string, format: date-time-local | LocalDateTime |
type: string, format: date | LocalDate |
type: string, format: time-local | LocalTime |
type: array | Array |
type: object | Table |
Also, the following abbreviations are used for Composition Type and Null described in JSON Schema.
| JSON Schema | Hover Type |
|---|---|
oneOf | String ^ Boolean |
anyOf | String | Boolean |
allOf | String & Boolean |
null | String? |
To shorten the display character on the hover, the name of the definitions in the JSON Schema
is not used, and the type is displayed as the TOML Basic Type like String, Boolean, and Array, etc.
Therefore, the & that indicates the relationship of allOf does not appear on hover
if you are using the correct JSON Schema.
For dependency entries, Tombi can also enrich hover content with package metadata such as the resolved package name and description.
Examples:
- in
Cargo.toml, hover can show metadata from workspace crates, path dependencies, or crates.io - in
pyproject.toml, hover can show metadata from workspace packages, local path sources, or PyPI
In offline mode, remote registry lookups are skipped and only local workspace or path metadata is used.
See also: