Stream not found by going for backslash

[AlexHofbeck (Alexander Hofbeck)]

Dear Specklers,

By hitting the \ instead of / one could create something like this by accident … this branch can also not be deleted in the frontend 1.0. I don’t know if this is an issue for frontend 2.0 as well.

In this is case it would be good to have a red message during the creation of the branches “you are not allowed to use the following symbols”, which prevents you from creating the branch.

BTW: As branches will be models in Frontend 2.0, how is the plan for grouping ? It would be really cool to have something similar

Best,
Alex

[jonathon]

@AlexHofbeck

By hitting the \ instead of / one could create something like this by accident

Good catch - this is a bug.

@AlexHofbeck

this branch can also not be deleted in the frontend 1.0. I don’t know if this is an issue for frontend 2.0

Can confirm it can be:

However the wrong UI component appears in list view:

You will be able to delete the branch via GraphQL and also with SDKs

---

@AlexHofbeck

As branches will be models in Frontend 2.0, how is the plan for grouping

Can you elaborate?

[AlexHofbeck (Alexander Hofbeck)]

@jonathon

Can you elaborate?

I mean with that a similar behavior like what frontend 1 had with the “/” … even if the branch is now called model? It is like folders for lots of models and helps keep overview …

MEP/ELECTRIC
MEP/HVAC
MEP/ProvisionForVoids
MEP/…

or to list up structural partial models

STR/STEEL (TEKLA)
STR/CONCRETE (REVIT)
STR/TIMBER (CADWORK)
STR/CONSTRUCTION PIT (REVIT)
STR/…

[jonathon]

Group and even better deeper sub-nesting

[AlexHofbeck (Alexander Hofbeck)]

the dream of every order fanatic . Love it @jonathon