xataio / vscode-extension Goto Github PK

In order to align the user experience in VS Code extension with the Web UI, it would be preferable to use the same names for column types.

Description of the problem

I have a mono-repo with more than one .xatarc, the vscode extension only use the root level .xatarc

Proposed solution

We could read the mono-repository manifest to load the different .xatarc available and behave as vscode multiple workspace mode

Table was created via Xata UI (on the website).
Column "test" via VSCode extension.
As you can see, columns created by the first method doesn't show in extension.
Maybe I don't know something or it is really problem.

Why do we list columns here:

Instead of just showing them in the right pane in the table view? I think it could be valuable–if we show columns in the sidebar–to toggle them to make the right pane table view more concise. That could be pretty cool.

Thoughts?

I click this and I want to insert a row:

But instead I add a column. Can we switch and make inserting with this plus icon and add a column with right click context menu? Adding a column is done much less often than inserting rows.

We want a panel that show the current database used by the current project

Add:

• Get Started
• Global mode vs Focus mode
• Complete list of features
• Add support to README
• Contributing

add /branches to the url

Why is this red?

Tasks

• Run the tests
• Deploy to VSCode stores on new version

Add a command to open the shell on the specific database/branch

Context

So far we can just adding one record per one record and we have a very basic auto-completion on link

Solutions

• Add a data key that take an array of records
• Use bulk endpoint
• Improve generated JSON schema to autocomplete the link ids

This should also create a git branch

Following of #17

Let's redirect to vscode directly instead of spawing a web server.

This will improve a bit the UX, since the user will be focus on the vscode instance directly after defining an API key.

Challenges

• uri flow on vscode
• uri flow on vscode.dev (need to deal with crypto in a webworker env)

Instead of F1 -> Insert Records, what if we had the following flow when inserting a record:

• Save inserts a new record, then
• if we change the JSONC document and save again, it updates it

Can we do that?

When a database is empty (no table) we have the setup project showing. This should be a create table call to action or "no table"

When clicking the Login button on the Xata: Explorer I am always directed to the page "New API key for Xata VSCode extension". Once I log out I have no option in the UI to log back in with an existing key. It would be great to provide an option "Login with existing API key".

Also, for this purpose, when creating an API key for the extension it would be great to expose it to the user so they can keep it to log back in. This way the user won't need to sign in to their Xata app account on a browser session every time they would like to login to the Xata VS Code extension.

After the last update for multi-region support the extension is creating and incomplete and invalid URL for the database.

Once clicked on the Get Started to link to a database on the Project panel, the following dialog pops-up:

And the generated .xatarc has the following value:

{
  "databaseURL": "/db/my-db-name"
}

instead of the following pattern:

https://{{workspace name}}.{{ region }}.xata.sh/db/{{ db name }}

Once properly generated and added, the Extension also throws an error saying the URL is invalid.

The Login button opens the system's default browser.

As an end user, I may prefer to log in to app.xata.io using a browser or session that isn't my default browser.

In order to do that, I would have to go to the default browser session that was started by the vscode extension, and copy the create API key URL from there, then paste it to the browser session of my preference. A "Copy login url" option, or simply making the existing Login button right-clickable to allow copying its url content, would help address this.

We need a nice logo (and tweak the description, categories…) for the vscode marketplace.

Let's bundle the extension so we can use it directly in https://vscode.dev/

https://code.visualstudio.com/api/working-with-extensions/bundling-extension

From feedback from user: the bool and float icons used by the VS Code Extension differ to those used by the UI.

Could we align them?

Bool:
UI:
Extension:

Float:
UI
Extension:

I have 3 columns, but in the table view I see only 2. I expect to also see email in the table view.

cosmicconfig can read all

So I've added the API_KEY to my env-file and the project view works fine, but when I refresh the explorer view I get the following error:

In here:

I want a button to see my records after inserting, and another button to "Open in Xata"

https://github.com/xataio/vscode-extension/pull/33/files#r924908893

• LICENSE.md is changed
• package.json is changed

The flow of creating xata branch need to be adjust when the current workspace is not a git repo

Problem

Right now, adding coucou.test in the schema is show like this:

Also, we don't have any way to add this coucou.test right now inside the VS Code extension.

Proposed solution

• Add "object" type
• Add a special flow to create object properties
• Add a hierachy level in the view tree for object