It was my mistake. Now when we start to type some local symbol name lazily relying to IDE autocompletion, then one of that short locale data modules may appear at the first place in autocompletion list if its name exactly match with first letters your did type. Here are examples:
const a = ne // you mean `next`, but see `ne` locale import first
const b = ce // you mean `cert` or `cent...`, but see `ce` locale import
const c = af // you mean `after`, but see `af` locale import first
const d = be // you mean `before...`, but see `be` locale import first
be // you mean `beforeAll(`, but see `be` locale import first
Since there are lots of locales existing and declared, we may hit same
annoying autocompletion mess very often.
Some screenshots to demonstrate the problem:
And how it should/would be after applying this fix:
In my previous PR #13 I did introduce TS declarations including all locale data as modules. Every locale module was declared as following:
It was my mistake. Now when we start to type some local symbol name lazily relying to IDE autocompletion, then one of that short locale data modules may appear at the first place in autocompletion list if its name exactly match with first letters your did type. Here are examples:
Since there are lots of locales existing and declared, we may hit same annoying autocompletion mess very often.
Some screenshots to demonstrate the problem:
And how it should/would be after applying this fix: