Need a way to catch typos in type names #24

New Issue

glen · 2022-07-24T20:02:40Z

glen commented

2022-07-24 20:02:40 +00:00

With the merge of #23, adding a signature like numbre: () => n => foo(n) where numbre is a typo for number will just be silently ignored, forever waiting for the possibility that type numbre will someday be added. There should be some mechanism for catching such typos that still allows the pre-installation of implementations for types that have not yet been installed.

With the merge of #23, adding a signature like `numbre: () => n => foo(n)` where `numbre` is a typo for `number` will just be silently ignored, forever waiting for the possibility that type `numbre` will someday be added. There should be some mechanism for catching such typos that still allows the pre-installation of implementations for types that have not yet been installed.

glen referenced a pull request that will close this issue

2022-07-30 02:45:36 +00:00

test: Check for undefined types, as a means to detect typos in type names #35

glen closed this issue

2022-07-30 02:45:44 +00:00

Sign in to join this conversation.