You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To import specific files in io-ts, you need to import with /lib/ or /es6/ prefixes, like import { Encoder } from "io-ts/lib/Encoder"
Desired Behavior
Don't require that prefix, like import { Encoder } from "io-ts/Encoder"
Suggested Solution
Do what fp-ts is now doing with gcanti/fp-ts#1241 to simplify imports
Who does this impact? Who is this for?
All users who use sub-package imports
Describe alternatives you've considered
handling doing the correct import manually leads to a lot of extra boilerplate in setting up linters to avoid the wrong imports, getting confusing errors when you use the wrong one.
Additional context
fp-ts already shows a proof of concept so would be nice to apply it here.
Your environment
Software
Version(s)
io-ts
2.2.9
fp-ts
2.8.1
TypeScript
3.9.6
The text was updated successfully, but these errors were encountered:
🚀 Feature request
Current Behavior
To import specific files in
io-ts
, you need to import with/lib/
or/es6/
prefixes, likeimport { Encoder } from "io-ts/lib/Encoder"
Desired Behavior
Don't require that prefix, like
import { Encoder } from "io-ts/Encoder"
Suggested Solution
Do what
fp-ts
is now doing with gcanti/fp-ts#1241 to simplify importsWho does this impact? Who is this for?
All users who use sub-package imports
Describe alternatives you've considered
handling doing the correct import manually leads to a lot of extra boilerplate in setting up linters to avoid the wrong imports, getting confusing errors when you use the wrong one.
Additional context
fp-ts
already shows a proof of concept so would be nice to apply it here.Your environment
The text was updated successfully, but these errors were encountered: