Daniel Thoma

Next

1

fix https://github.com/clickbar/dot-diver/issues/3 fix https://github.com/clickbar/dot-diver/issues/4 fix https://github.com/clickbar/dot-diver/issues/5 Partially fixes https://github.com/clickbar/dot-diver/issues/2 Updates behavior for https://github.com/clickbar/dot-diver/issues/30 We use the currently given path (typed by the user) as an offset to only show the...

Index signature in object gets ignored

1

Example Type: ```ts export type ExampleType = { id: number } & Record ``` Here `test_data.foo` is not a valid path in `getByPath` and will throw a typescript error.

`setByPath()` uses the `Path` type, which does not differ between readonly and writeable properties. So the auto completion contains paths to properties, which are readonly. We should create an extra...

Let's consider the following cases: ```typescript type TestType = { a: number | { nested: string } } type value = PathValue // is string ``` Here, the type of...

Currently, if a type has many cyclic dependencies (see [readme-question](https://github.com/clickbar/dot-diver#-i-get-the-error-type-instantiation-is-excessively-deep-and-possibly-infinitets2589)), TypeScript fails due to the large number of possible paths. If circular constraints were better supported (see https://github.com/microsoft/TypeScript/issues/51011), an alternative...

See title. If we have a object inside a object with an index signature, all paths of the nested objects are getting truncated. Example: ```ts type TestType = { [index:...

Currently, we do not exposed the depth parameter, since interference of other generic Parameters (e.g. Path, PathValue) would stop. See this issue for further information: https://github.com/microsoft/TypeScript/issues/26242 This would kill the...