Bug 387866 - KDevelop generates wrong project view tree when symbolic links are linked inside the project root.
Summary: KDevelop generates wrong project view tree when symbolic links are linked ins...
Status: RESOLVED WORKSFORME
Alias: None
Product: kdevelop
Classification: Applications
Component: UI: general (show other bugs)
Version: 5.2.1
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-13 08:36 UTC by Venca B Spam
Modified: 2022-12-10 05:17 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Video of JSON codemodel (692.32 KB, video/mp4)
2017-12-13 08:37 UTC, Venca B Spam
Details
CMake server codemodel (2.58 KB, application/json)
2017-12-13 08:38 UTC, Venca B Spam
Details
How to reproduce video (738.06 KB, video/mp4)
2017-12-13 08:38 UTC, Venca B Spam
Details
SimpleSymlinkScenario5 (1.49 KB, application/gzip)
2017-12-13 08:41 UTC, Venca B Spam
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Venca B Spam 2017-12-13 08:36:10 UTC
KDevelop generates wrong project view tree when symbolic links are linked inside the project root.

* How to reproduce: *
1. Open attached SampleSymlinkProject5/SampleSymlinkProject CMake project.
2. Let KDevelop parse it and then build it.
3. Browse the "project tool view"
4. Search for the location of the LibBar in the tree.

Actual result:
The "LibBar" is shown only as parrent of the "SomewhereInsideProjectRoot".

Expected behavior:
The LibBar should follow the buildsystem and should be shown as parent of the project root folder.
Opinion: Also the LibBar should match the filesystem, so it should be shown twice, first as parent "SomewhereInsideProjectRoot/LibBar", second as parent of the project root folder "LibBar".

Observation:

As I am reporter of another symbolic links related bug https://bugs.kde.org/show_bug.cgi?id=387391 I observed that if the symbolic link is pointing to resource outside the project root, it is displayed properly as the user expects.

Please see attached "How to reproduce video" for illustration.

Also please see attached "CMake server codemodel" as a reference of how the project is expected to be shown from the build system perspective. I attached video of the JSON displayed in Firefox for convenience - please see "Video of JSON codemodel".
Comment 1 Venca B Spam 2017-12-13 08:37:31 UTC
Created attachment 109352 [details]
Video of JSON codemodel
Comment 2 Venca B Spam 2017-12-13 08:38:18 UTC
Created attachment 109353 [details]
CMake server codemodel
Comment 3 Venca B Spam 2017-12-13 08:38:40 UTC
Created attachment 109354 [details]
How to reproduce video
Comment 4 Venca B Spam 2017-12-13 08:41:45 UTC
Created attachment 109355 [details]
SimpleSymlinkScenario5
Comment 5 Venca B Spam 2017-12-19 14:01:47 UTC
It looks that at least the whole KTextEditor component of KF5/KDE is behaving weird - seeing from the end user perspective. Although I can see the point from the developer perspective.

I looks like it always resolves symbolic links and exposes this to the user. I can understand that internally it is ok and maybe for many cases necessary.

From the user perspective it is however wrong approach. Why I thing this:

Imagine my mother when I explain her,:
Me: "Mom, here in your home folder e.g. /home/BestMomOnTheWorld/Documents there are all your Pie recipes."
Mom: "U r great son!"
..after a while, I am at the gate leaving for holiday..
Mom is calling: "I am lost, I lost my recipes, it says something about /mnt/dataserver/mirror/raid5/diskXYZ/users/online/uuid12729837192347/Documents/best recipe on the world.txt, I believe I lost it, how can I prepare for tomorrow's party?!??"

I did quick use case research and it looks that other frameworks do not propagate the resolved symlink path to the end users. Even QtCreator programmer tool properly assumes that the user wanted to not resolve the symlink in the interface.

Any ideas? or am I wrong about this?
Comment 6 Justin Zobel 2022-11-10 22:32:52 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 7 Bug Janitor Service 2022-11-25 05:20:33 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Bug Janitor Service 2022-12-10 05:17:15 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!