Console UX feedback: persistence, Functions config bugs & load time - v2.x

I've collected a few issues and improvement suggestions, mostly in Databases and Functions. I'll post each one as a separate message below with screenshots.

Issue #1 - [Databases] Persist view and sort preferences

Where: Console → Databases (list page) and Console → Databases → [Database] → Tables sidebar

1. Databases view mode doesn't persist
Switching the Databases page to list view only lasts for the current visit. After a page refresh, or navigating away and back, it resets to grid view, so I have to switch it again every time.

2. Tables sort order doesn't persist
Inside a database, the tables sidebar has a sort option (e.g. Name (A → Z)). Once set, it resets to the default (Created, oldest first) whenever I open another table, switch databases, or refresh the page.

Expected: Both settings should be remembered once chosen.

Suggestion: Save them locally (localStorage) or, better, in user/project preferences so they persist across sessions and devices. Scoping the sort order per database or globally would both work.

Issue #2 - [Databases] Restore "Create more" toggle in Create Column modal

Where: Console → Databases → [Database] → [Table] → Columns → Create Column

Issue: The previous Console version had a "Create more" toggle in the Create Column modal that kept it open after saving, so you could add several columns in a row. It's gone in the current version. The modal now closes after every save, so I have to click + Create column again for each new column. This adds an extra step per column and slows down table setup.

Expected: A way to create multiple columns without reopening the modal each time.

Suggestion: Bring back the "Create more" toggle next to the Create Column button. When checked, the form resets after saving and stays open for the next column.

Issue #3 [Functions] "Select" root directory adds leading ./ that breaks builds

Where: Console → Functions → [Function] → Settings → Version control (Git) → Branch Settings → Root directory

Issue: When I use the Select button to pick the function's root directory, it fills the path with a leading ./ (e.g. ./functions/brevo). Deployments with this path fail to build. I have to edit the field manually to remove the ./ (e.g. functions/brevo) before builds succeed.

Reproducibility: Consistent. Tested on ~6 functions across Dart and TypeScript runtimes.

Steps to reproduce:

1. Connect a function to a Git repo
2. Click Select next to Root directory and choose a subfolder
3. Click Update and trigger a deployment → build fails
4. Remove the leading ./ manually, redeploy → build succeeds

Expected: The path returned by Select should work as-is.

Suggestion: Either return the path without ./, or normalize the root directory (strip leading ./ and /) on save or in the build pipeline.

Issue #4 - [Functions] "Add event" builder generates incorrect TablesDB event string

Where: Console → Functions → [Function] → Settings → Executions → Events → + Add event

Issue: When I use the + Add event builder to trigger a function on row creation in a TablesDB table, it generates an incorrect event string that never fires.

The generated event has two problems:

1. Uses the legacy databases. prefix instead of tablesdb.
2. Omits the rows.* segment, so it targets table creation instead of row creation

Steps to reproduce:

1. Open a function's Settings → Executions → Events
2. Click + Add event and select TablesDB → [Database] → [Table] → Rows → Create
3. Save and create a row in that table → function doesn't execute

Expected: The builder should output the correct TablesDB event path (tablesdb.[db].tables.[table].rows.*.create).

Issue #5 - [Console] Slow initial load (10–15s) on first visit

Where: Console, first load (Cloud)

Issue: When I open the Console after a while away (cold load, not a refresh), it takes 10–15 seconds before it becomes usable. Later navigation within the same session is fine. I didn't have this problem on v1.9.x.

Note: I'm not sure if this is specific to my setup but I don't have this issue with all the sites deployed to my project, else I'd have blamed it on region, so I'd appreciate knowing if others see the same thing. Happy to share any further information

That's everything from me 🙏🏽
I'd appreciate if these get a look.
Thank you, Appwrite

cc @user