Re: [platform-dev] Marking nested projects as derived, what are the risk

[Mickael Istria <mistria@xxxxxxxxxx>]

Thanks Andrey. I actually tried that first to validate SCM integration isn't really an issue

1. Create or import a project

2. Pick a folder (that will be turned into a project later, so it's good if it's a project), mark is a derived

3. Try to edit a File

   => Got a pop-up "this file is derived, do you want to edit it?", which is actually a good thingz

   => Got EGit staging the file anyway (EGit prefers trusting the .gitignore) and mark the file and folder as modified

4. Open the folder as project

5. Edit another file

   => Everything file

   => EGit stages the change and marks the file and folder as modified

So to me, this workflow looks totally desirable for cases of nested projects: it warns users when editing the "non-leaf" duplicate resource, it still makes EGit works well, it hides duplicated resources in many views...