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

Collapse namespace pipeline #136

Open
noklam opened this issue Oct 3, 2024 · 5 comments
Open

Collapse namespace pipeline #136

noklam opened this issue Oct 3, 2024 · 5 comments
Assignees
Labels

Comments

@noklam
Copy link
Contributor

noklam commented Oct 3, 2024

Description

image

Context

The only way to collapse a pipeline is using the side panel, this is not available in the extension which means we can only expand, but not collapse the pipeline.

@stephkaiser

@noklam noklam added the design label Oct 3, 2024
@stephkaiser
Copy link

I can explore how to collapse without using the side panel 👍 there is also the expand/collapse button in the action bar but this expands and collapses everything in the pipeline.

Screenshot 2024-10-03 at 12 49 44

@noklam
Copy link
Contributor Author

noklam commented Oct 3, 2024

Thanks! @stephkaiser , we don't show this the action bar so we only have the flowchart view. We need to consider this together with #123, I would say this is the minimal change we need to make the flowchart usable in VSCode.

Feel free to playaround with it, it should be quite easy to setup by just using the demo project in viz and install the extension from VSCode. If you need help on this please let me know!

@stephkaiser
Copy link

sounds good, thanks Nok!

it would be good to understand the priority for this work so we can plan it accordingly, is it a blocker for users at the moment?

cc @astrojuanlu

@astrojuanlu
Copy link
Member

it would be good to understand the priority for this work so we can plan it accordingly

+1

@noklam
Copy link
Contributor Author

noklam commented Oct 3, 2024

For me, the priority are #58, we are planning to put this into a proper sprint so I will make sure discuss those ticket during grooming. (maybe in the Kedro framework one but I can invite you in that case).

I would say kedro-org/kedro#123 is the blocking one, which has been flagged by multiple users during demo (pre-release).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: No status
Status: In Progress
Development

No branches or pull requests

3 participants