| Summary: | When the opened folder is the project in the Electron app, .tern-project problems cannot be fixed | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Michael Rennie <Michael_Rennie> | ||||
| Component: | JS Tools | Assignee: | Michael Rennie <Michael_Rennie> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | major | ||||||
| Priority: | P2 | CC: | mamacdon, Olivier_Thomann, steve_northover | ||||
| Version: | 13.0 | Flags: | Olivier_Thomann:
review+
|
||||
| Target Milestone: | 14.0 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Michael Rennie
Another part of this problem: since we can't find the right context to modify / create the file, we also do not read the file if it is there. Created attachment 265956 [details]
Proposed fix
when the project is the root opened file, the project becomes "/file/" in electron.
The patch adds support to the javascriptProject to account for this.
+1 Michael, is this fixed and the patch good? (In reply to Steve Northover from comment #4) > Michael, is this fixed and the patch good? There are some edge cases the patch does not handle, that I am currently working on. I pushed in support for your project being the root folder: http://git.eclipse.org/c/orion/org.eclipse.orion.client.git/commit/?id=e25c0a27ca05bf5620d5ae825db3f7748a638bf5 To support walking back up the tree to find a project context will require an implementation in the server - I tried a client-side-only fix and the performance was terrible. Ok, so do these cases work:
1) The "project" case:
GitRepoWithGoodStuff1
2) The "root" case:
Root
GitRepoWithGoodStuff1
GitRepoWithGoodStuff2
3) The "toolchain" case:
Root
ToolChainName
GitRepoWithGoodStuff1
GitRepoWithGoodStuff2
I am guessing that 3) doesn't work (and it also doesn't have to at the moment).
(In reply to Steve Northover from comment #7) > Ok, so do these cases work: > > 1) The "project" case: > > GitRepoWithGoodStuff1 > > 2) The "root" case: > > Root > GitRepoWithGoodStuff1 > GitRepoWithGoodStuff2 > > 3) The "toolchain" case: > > Root > ToolChainName > GitRepoWithGoodStuff1 > GitRepoWithGoodStuff2 > > I am guessing that 3) doesn't work (and it also doesn't have to at the > moment). Yes, 1 and 2 work, 3 does not 1) and 2) are the current case? 3) is something that we discussed supporting but did not settle on. *** Bug 509356 has been marked as a duplicate of this bug. *** (In reply to Steve Northover from comment #9) > 1) and 2) are the current case? 3) is something that we discussed > supporting but did not settle on. Yes, that is the current state. If we can settle on a good (performs and scales well) fix for bug 511326, we can also support 3. Fixed a bug found with "files in root of workspace": http://git.eclipse.org/c/orion/org.eclipse.orion.client.git/commit/?id=fccf9b8b3b003086f0348dc103f3259d2be3d027 (In reply to Michael Rennie from comment #12) > Fixed a bug found with "files in root of workspace": > > http://git.eclipse.org/c/orion/org.eclipse.orion.client.git/commit/ > ?id=fccf9b8b3b003086f0348dc103f3259d2be3d027 Fixed another regression found: http://git.eclipse.org/c/orion/org.eclipse.orion.client.git/commit/?id=e709d1a81905515d6ed43731bdd18450dddb8493 Closing fixed. I opened bug 511590 to track the work of supporting asking the server for project context. |