-
Notifications
You must be signed in to change notification settings - Fork 202
Hide fileStatus when compileOnSave is false #546
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
Conversation
if (status.emitDiffers || status.modified) { | ||
this.fileStatus.text('Js emit is outdated'); | ||
this.fileStatus.addClass('icon-x text-error'); | ||
let project = getOrCreateProject(filePath); |
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.
getOrCreateProject
is something that shouldn't be called from the front end code. We have a seperate nodejs process running the background managing projects / language service etc. More docs : https://github.com/TypeStrong/atom-typescript/blob/master/CONTRIBUTING.md#architecture
Ok thanks, that's clearer to me now. Is calling parent.getProjectFileDetails the correct approach? |
Yes 👍 However I would prefer you track down usages of
Maybe add a function like |
Unfortunately, not all other usages of atom-typescript/lib/main/atomts.ts Line 126 in 2a7b563
(in this case I could move the updateFileStatus up into the then on line 111)
And here I would have to fetch
It seems to me to be a bit anti-DRY to have logic and code calling a Another idea would be to react to changes to the Let me know what you think. |
Hide fileStatus when compileOnSave is false
It will be in the next release 🌹 |
Thanks! |
Fixes issue #524
Hope it looks okay. I'm pulling the compileOnSave directly from the cache.