-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
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
update README.md and fix bug in fallback config lookup #52
Conversation
"description": "If `true`, Alloglot will log more output." | ||
"description": "If `true`, Alloglot will log more output.", | ||
"default": null |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The issue preventing the fallback from being used is that VS Code defaults boolean config options to false
if the package.json doesn't specify a different default.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My config-loading logic saw that user-level config "existed" (incorrectly) and so ignored the fallback.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
:argh:
A PR to release these changes has been created, bumping the version from 3.0.1 to 3.0.2. |
} | ||
|
||
function timestamp(): string { | ||
return new Date().toJSON().split('T')[1].replace(/\.\d*Z/, ' UTC') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Dates in vanilla JS, oh what fun.
No description provided.