As a way of reducing the friction for new users running lakeFS locally it would be good to provide a default value for the storage namespace. Storage namespace is not something that a new user will necessarily be familiar with so we need to make it as easy to enter.
At the moment the form field has a placeholder but this disappears as soon as the user starts typing something which requires them to have memorized the syntax that the placeholder gave them
Some suggestions:
If we're running locally then maybe we can simply default the actual contents of the field to local://example-bucket - does the user actually need to configure this unless they want to?
If not running locally then default the value to the storage namespace prefix?
or maybe default the contents to the storage namespace prefix so all the user has to do is enter some path name?
or add a hint underneath the form box
We should also delay the validation on what's entered until they at least take focus from the box - as can be seen from the screencap above the user gets a scary red message telling them they're doing something wrong even if they're entering as-yet-still-valid text
@rmoff, a solution can be to add the default_storage_namespace (don't remember the exact name) configuration to the bundle of default local settings. This way, this field will get filled automatically
As a way of reducing the friction for new users running lakeFS locally it would be good to provide a default value for the storage namespace.
Storage namespace
is not something that a new user will necessarily be familiar with so we need to make it as easy to enter.At the moment the form field has a placeholder but this disappears as soon as the user starts typing something which requires them to have memorized the syntax that the placeholder gave them
Some suggestions:
local://example-bucket
- does the user actually need to configure this unless they want to?We should also delay the validation on what's entered until they at least take focus from the box - as can be seen from the screencap above the user gets a scary red message telling them they're doing something wrong even if they're entering as-yet-still-valid text