You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Better type identification in the editor could help locate faster what you are looking for, especially when the rest of the backends are dimmed. Some subtle color differentiation could help
#4365
The first impression I have till now is that you are building something that seems groundbreaking. I can't remember the last time I had this feeling!
Here're some minor points that could be useful for now:
I could use a more clear connection between code (repository) and the app.
I would expect that selecting all text and typing would remove the original value.
Also, shift + tab to move back when the current field is empty could help, I wanted to do this more than 20 times.
Better type identification in the editor could help locate faster what you are looking for, especially when the rest of the backends are dimmed. Some subtle color differentiation could help.
It took me a while to realize the white dots are the requests and was confused as they seem to stop expanding after six requests. Scaling this could be interesting.
Some sample backends could help!
Being able to toggle an auto-arrange functionality per type could help to avoid having a mess with the service graph. Alternatively, snap-to-grid could help.
Since you've disabled zoom functionality, which I can see how this can be beneficial, some backends can go out of sight. Indicating there is more out of the viewport in a direction could help.
Sometimes DB backends are always highlighted even when I'm editing other backends.
I don't get why the functions live in their own plane but I'll get there.
The docs link moves around when you have added backends out of the viewport of the editor.
I could use a more clear connection between code (repository) and the app.
Coming from a UX and Frontend background, while I've worked a lot with backends like Java (Spring-Boot), it was slightly obscured at first for me to clearly differentiate what is hosted, built, or served from the dark platform. I particularly refer to the static assets which I had to upload using the CLI.
Reading through the documentation about dark and trace driven development in general this becomes more clear on the way.
Build your frontend or mobile app first and point your API endpoints at Dark.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
A user says:
Beta Was this translation helpful? Give feedback.
All reactions