Comments (2)
Rojo 0.5.x currently doesn't respond to the project file changing itself. This is something that's fixed as part of the master branch, currently slated to be a 0.6.0 release in the future.
The VS Code plugin is what responds to the project file changing; it works by restarting the Rojo process. That forcibly kills any outstanding HTTP requests, giving you that error in the plugin!
If we fixed that error, there's another safeguard in place in the Rojo plugin that cancels the connection if a different Rojo server suddenly pops in. This fixes a couple other bugs, but makes restarting the process not quite correctly reload.
I'm going to move this over to the VS Code repository. It could be that this will remain unfixed until we do a release based on the current master codebase.
from vscode-rojo.
As LPG said, this is actually intentional. I think you would need to reload it manually to see your changes anyways, so it doesn't really make sense to me for this to not be the case.
from vscode-rojo.
Related Issues (20)
- Link in "Welcome to Rojo" page leads to 404
- Should the extension allow serving multiple project files concurrently, from the same workspace? HOT 1
- Should allow plugin management on unsupported systems if a custom path is specified.
- TypeError: Cannot read property 'globalState' of undefined
- Windows: "Manage it for me (Recommended)" button doesn't do anything HOT 7
- TypeError: Cannot read property 'find' of undefined HOT 1
- Falling back to installed version if Github goes down HOT 1
- Respect foreman configuration for Rojo version HOT 2
- command "Rojo: initialize" throw an error HOT 2
- Platform not supported warning under Arch linux HOT 3
- "Add support for optional paths" not supported in Project Schema HOT 1
- vs code plugin not working in version 2+ HOT 4
- Suggestion: Make it possible to hide the "Use aftman instead of foreman" popup HOT 3
- Suggestion: Add mouse free project building HOT 1
- Cannot Install Rojo in a Project HOT 1
- Serving project doesn't automatically forward port in remote VSCode
- Rojo server appears to not shut down properly on MacOS when turned off through VSCode UI. HOT 3
- Renaming a file duplicates it HOT 1
- can't get *.project.json file
- Extension not recognizing that Rojo is installed with Aftman
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from vscode-rojo.