The ui shows internal command when it maybe shouldn't

[demetris-manikas]

What happened?
When I visit the commands page of the ui i can see and execute internal commands

What did you expect to happen instead?
I would expect internal commands to not appear at all or at least to not be executable

How can we reproduce the bug? (as minimally and precisely as possible)
Define an internal command and check the commands page
My devspace.yaml:

version: v2beta1
...

Local Environment:

• DevSpace Version: 6.3.14
• Operating System: windows | linux | mac
• ARCH of the OS: AMD64 | ARM64 | i386
  Kubernetes Cluster:
• Cloud Provider: google | aws | azure | other
• Kubernetes Version:
  Client Version: v1.31.0
  Kustomize Version: v5.4.2
  Server Version: v1.30.6+k3s1

Anything else we need to know?

[deniseschannon]

What is your concern of showing the internal commands? The UI doesn't have any special permissions and it's hosted locally, so this is really scoped to the individual user.

[demetris-manikas]

Hi.
The devspace list commands does not list internal commands although one can execute them.
I would expect the ui to do something similar.
In my case I have 4 "public commands" and another 12 "internal"
A developer should only be presented with the useful 4 command and not with 16.
I am not suggesting to completely remove them from the ui but some kind of grouping in the UI would be nice.
Thanks for your time.

[zerbitx]

This would be a feature request, so we've updated that and will look back shortly. In the meantime a PR would be welcome. Thanks!

[demetris-manikas]

I would give it a go at creating a PR.

How should the internal commands be treated?
To just hide them is a change in one line of code.

devspace/ui/src/pages/commands/commands.tsx

Line 103 in a633a2b

commandsList={this.props.devSpaceConfig.config.commands}

.filter(...)
For any other solution I would need you to guide me in how you want the UI to look.

[demetris-manikas]

I am having some trouble seeing my changes locally.
I followed all the steps in the contributing section to build devspace.
After making some code changes I run npm run build and all is fine.
But here I am missing a step.
What am I supposed to do to make ./devspace ui use the newly built files?
Thanks.

[demetris-manikas]

Hi.
Can anybody help here?
I am stuck.
Should I give up?
Thanks

[zerbitx]

For ui development, try uncommenting this and opening it up on port 3000.

[demetris-manikas]

@zerbitx Thanks for your help.
So...
How should this be implemented?
The simplest would be to add a checkbox for toggling show/hide of internal commands.
The somewhat more complicated would be to generalize this a bit by adding a command.group property (instead of using just the internal flag) and show the commands grouped accordingly.
Anyway, I will implement any solution you propose so I will be waiting for your decisions.