Can't open external links to projects in subgroups

[Terrance]

I confirm that I have searched the issue tracker

Before opening an issue, take a few minutes to search the issue tracker (both open and closed issues) for the problem you are facing. This will reduce the need for issue triage and save time.

• I confirm that I have searched the issue tracker

Describe the bug

LabNex URLs to projects in a subgroup (e.g. /<group>/<subgroup>/<project> or any further nesting) aren't recognised.

To Reproduce

1. Open labnex://gitlab.com/gitlab-org/gitlab (https://gitlab.com/gitlab-org/gitlab)
   • Successfully opens the project
2. Open labnex://gitlab.com/gitlab-org/auth/glgo (https://gitlab.com/gitlab-org/auth/glgo)
   • Opens the dashboard home screen

Expected behavior

Both projects can be opened via URL.

Versions (please complete the following information)**

• LabNex: 7.0.0
• Android: 13
• GitLab: Any

GitLab instance

• gitlab.com
• framagit.org
• Self-hosted instance
• Other service (Name/URL: )

Mode of installation

• Google Play Store
• F-droid
• APK
• Built from source
• OpenAPK
• Other stores (Name: )

Declaration

• I have carefully read and agree to follow the contribution guidelines.

[mmarif4u]

This is not a bug, it is by design. Checking through nested groups means calling multiple API calls, but in some cases we will not know if those are nested groups or other URL paths.

So I take this as an improvement but with settings to enable nested groups for deep linking, this is if some users dont want to wait or not interested in multiple calls can still use as normal single group path.

Now the decision which I am thinking is whether they should be enabled by default or disabled. I prefer them disabled though.

[Terrance]

Project sub-paths are (hopefully all) behind a dash e.g. https://gitlab.com/gitlab-org/auth/glgo/-/issues, so anything with a segment like that can just be split and identified in one step?

When there isn't a dash but there are two or more parts (i.e. the link is to a group, or repo front page), it probably makes sense to try parsing as a repo first, group second. If you're saying you have to do each path step individually, only the last part can be either a repo or a group, otherwise it's a 404 anyway?

[mmarif4u]

Personally I am not sure about GitLab complete URL structure, but if what you say is correct about the dash (-), then that would be great. Because this will make process of splitting easier.

Yes, priority will be repository, then group(s) and then nested groups.