Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

import/focus on one project from a url #14550

Closed
maxandersen opened this issue Sep 13, 2019 · 8 comments
Closed

import/focus on one project from a url #14550

maxandersen opened this issue Sep 13, 2019 · 8 comments
Labels
kind/enhancement A feature request - must adhere to the feature request template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P2 Has a minor but important impact to the usage or development of the system.

Comments

@maxandersen
Copy link

Quickstarts repos like https://github.com/quarkusio/quarkus-quickstarts have multiple sub projects and would be awesome to either:

A) have one devfile.yaml in root to define a shared workspace setup, but then be able to tell che to just import lets say https://github.com/quarkusio/quarkus-quickstarts/tree/master/getting-started folder - without having to use absolute folder names/urls.

B) allow referring to folder like che.openshift.io/f?url=https://github.com/maxandersen/quarkus-quickstarts/tree/che/getting-started and have it locate nearest devfile.yaml rather than listen to /devfile.yaml in root directly.

Ultimately having the project explorer or similar "focused" on getting-started to avoid polluting the UI.

@maxandersen maxandersen added the kind/enhancement A feature request - must adhere to the feature request template. label Sep 13, 2019
@ibuziuk ibuziuk added severity/P2 Has a minor but important impact to the usage or development of the system. area/devfile labels Sep 16, 2019
@skabashnyuk
Copy link
Contributor

related to #13671

@skabashnyuk skabashnyuk added this to the 7.x milestone Sep 19, 2019
@maxandersen
Copy link
Author

#13671 seem to be about sparse checkout which is useful but separate feature IMO.

In this I'm talking about being able to checkout a github repo but then only import part of it and be able to focus on that.

Limiting import is more about saving resources in a limited cloud environment but also to avoid polluting the UI with potentially hundreds of other projects. When I use emacs, eclipse, vscode, intellij or any other desktop IDE I can think of I highly rely on being able to focus on a specific area.

That is useful not only when doing quickstart like projects for newbies, but also for normal development work of just focusing on one area - while still being able to navigate to other parts of the larger project.

@skabashnyuk
Copy link
Contributor

In this I'm talking about being able to checkout a github repo but then only import part of it and be able to focus on that.

Am I understand you correctly. You want to check out all soure code, but Theia should open only one subfolder?

@maxandersen
Copy link
Author

Yes, or at least be able to "focus" on it.
Two different usecases with slightly different wanted behaviors:

  1. A quickstart repo like https://github.com/quarkusio/quarkus-quickstarts/ you would be ok just doing a spare checkout and focus on lets say getting-started folder. Since there is no shared parent pom all is good.

  2. in quickstart repo like https://github.com/jboss-developer/jboss-eap-quickstarts you would like a full checkout as each quickstart refer to the parent pom and possibly other modules next to it - but be able to "focus" us just importing i.e. hello-world + parent project.

  3. with more "traditional" multi-module project like https://github.com/quarkusio/quarkus you want to checkout everything but at least have a way to limit how much of the project gets imported to avoid using all available memory and/or at least be able to "focus' the selected projects.

For now using che for mainly smaller projects and quickstarts #1 and #2 would be a great help.

@skabashnyuk
Copy link
Contributor

@l0rd @slemeur @sunix @tsmaeder can you comment? look like it will require some changes on IDE side.

@sunix
Copy link
Contributor

sunix commented Sep 19, 2019

I commented here
I would like to explore theia workspace multi root to solve that problem.

@che-bot
Copy link
Contributor

che-bot commented Mar 18, 2020

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 18, 2020
@sunix
Copy link
Contributor

sunix commented Mar 20, 2020

another clean solution: #15540

@che-bot che-bot closed this as completed Apr 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement A feature request - must adhere to the feature request template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P2 Has a minor but important impact to the usage or development of the system.
Projects
None yet
Development

No branches or pull requests

5 participants