-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
March Iteration Plan #3555
Comments
For the item, "HTML Preview run from a WebView and support executing JS", is there any plans to add support for jade templates also? Like jade to html on the fly and render? |
@codyrigney92 There is an extension to convert jade to html, you could use this in combination with HTML preview to achieve this? |
@tht13 Thanks, I'll have to give that a try. |
I'm sad #78 is not on the roadmap :( |
@luisrudge this is just the finish list for the build conference end of March. We will update the roadmap soon. |
Is there also a way for debug adapters to get the locale of the user? I name my "threads" |
@felixfbecker the localisation story is in the works. The locale is passed via the environment. node-debug is an example. |
@tht13 I tried your suggestion but there are 2 problems
I'll wait for the release and see what's possible then. Thanks! |
@codyrigney92 If you add a feature request to the html preview repo I'll remember to add that compatibility. |
@codyrigney92 Jade preview compatibility has been added and v0.0.3 will be released later this evening 😄 |
@tht13 Thanks! |
Add comment about insiders release ready for testing. |
So I'm confused; The ability to disable intellisense in comments - was that fixed, or not? I've tried out the insider build and don't see the functionality implemented. |
Update to 1.0 Release of VS Code
We have now completed engineering work for our “1.0” release of VS Code. However, with all of the excitement around //Build, we've decided to take this opportunity to hold back our "1.0" release for just a couple of weeks, to get some more community testing on the product. Our “Insiders” release has been updated to match what we plan to ship in mid April. We encourage you to download it today (release notes), use it, and let us know if you find any critical ship stopping issues. In the meantime we're going to finish up work on the 1.0 documentation, clean up debt, unwind a bit, and start planning the future of Visual Studio Code.
March is our end game for the Build 2016 milestone. During the endgame the focus is on problems, performance, publish. This doesn't mean that we do stop listening to feedback, but we will slow down on adding new features.
Endgame Schedule
Monday, Mar 14
Tuesday
Wednesday
Thursday
Friday
Monday, Mar 21
insider
channelTuesday-Friday
For more information about our development process please refer to the development process page.
Finish
taken.
installing extensions
javascript.validate.enable
Revive javascript.validate.enable setting #3909 @dbaeumerjsconfig.json
file @jriekensupport to pass a 'More Information' url from the debug adapter to the frontend #3448 @weinand
Problems.Performance
Polish
Adoptions
ElectronRelease
The text was updated successfully, but these errors were encountered: