Rushabh Vora
Rushabh Vora
Oh wow.. seems like localisation is also needed in combination. 😐 So, the solution would to be also to guess the locale, like we are guessing the timezone?
So if I were to get the user locale via `navigator.language`, how would I use that when formatting the date? I can't see where to pass the locale for timezone...
As you can see in the above screenshot from Chrome's console, when I pass a locale to Intl.DateTimeFormat, it returns the desired abbreviation. I need to pass `en-IN` to get...
Should I leave this issue open since I hope this support can be added or is this not the right place for feature requests?
Aren't the locale names standardised? What I feel — If no locale name is passed, then there's no need to pass any locale to the Intl API/it would work as...
@ssokolow Understood. This bug doesn't happen often enough to be an annoyance, and when it does happen, I can just run `quicktile --daemonize` and get it working perfectly fine.
The errors don't show up for the tracked files either. They do show up in the shell when trying to commit, and it works perfectly at that time. Just not...
1.0.13-0 didn't change anything for me. The output from ESLint - ``` [Info - 11:23:24] ESLint server is starting [Info - 11:23:25] ESLint server running in node v14.16.0 [Info -...
On initial testing, it doesn't seem to be fixed. 😞 I'll test it out further sometime next week.
Still no change in behaviour for me 😓 Linting warnings/errors still don't show up in VS Code for changed lines, after the file has been saved.