Startup page
See original GitHub issueEven if I have a html page opened in the acive editor form an other folder, “Go Live” will serve the file with the same name from workspace root.
appModel.ts (114): let rootPath = WorkSpacePath ? WorkSpacePath : documentPath;
Will WorkSpacePath
ever be null?
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:6 (4 by maintainers)
Top Results From Across the Web
UCPS Secondary Startup Page
High School Student Startup Page. Schoolnet · Discovery Education · Albert · drive.google.com · O365 · MS Teams · Student Apps Locker ·...
Read more >Startpage - Private Search Engine. No Tracking. No Search ...
Search and browse the internet without being tracked or targeted. Startpage is the world's most private search engine. Use Startpage to protect your ......
Read more >Set your homepage and startup page - Google Chrome Help
On your computer, open Chrome. · At the top right, click More More and then Settings. · Under "On startup," select Open a...
Read more >Student Startup Page - Terrebonne Parish School District
Student Startup Page · Click the image to sign into Clever for access to TPSD Programs. · Clever · Click the image below...
Read more >Student Startup Page - Union County Public Schools
Kensington Elementary School · Student Startup Page · Original text.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Okay. I got your point. I’ll definitely try to add the settings 😃
Hello! Ok, I understand. But this is still a hard restriction: why should the workspace root be the web root as well? Mine is a subfolder of the workspace. It is confusing anyway: the file name is from the active editor, but the folder served is totaly different. What if there is no file with the same name in the workspace root? You will get a directory listing… quite useless. I think that you should let the user decide if he/she wants to serve the currently opened file or a specific file from the workspace - I am sure, the later will be the most used scenario. I suggest you add a setting (like the port), where the user can specify any html file relative to the workspace root. If the setting is missing then it should fall back to serving the currently edited file (indifferent if there is a workspace or not). If the setting is pointing to an inexistent file or file is not html, then the directory listing is adequate.