We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support NonEmptyArray (from fp-ts) as being a tuple with [0] defined as well as a traversable & indexable array
NonEmptyArray
nonempty arrays are treated like normal arrays
const a: NonEmptyArray<string> = ["abc", "def"] const x: string = pipe(a, get("a.[0]")) const y: Option<string> = pipe(a, get("a.[number]", 1))
Update Paths and Build (I think AtPath should work properly as-is)
Paths
Build
AtPath
Users of NonEmptyArray
try to support other implementations of NonEmptyArray as well (which would be safe, since we require typescript >v4.0).
The text was updated successfully, but these errors were encountered:
No branches or pull requests
🚀 Feature request
Support
NonEmptyArray
(from fp-ts) as being a tuple with [0] defined as well as a traversable & indexable arrayCurrent Behavior
nonempty arrays are treated like normal arrays
Desired Behavior
Suggested Solution
Update
Paths
andBuild
(I thinkAtPath
should work properly as-is)Who does this impact? Who is this for?
Users of
NonEmptyArray
Describe alternatives you've considered
try to support other implementations of NonEmptyArray as well (which would be safe, since we require typescript >v4.0).
Additional context
Your environment
The text was updated successfully, but these errors were encountered: