spacecloud-io / mission-control Goto Github PK

on pressing ctrl + s from the keyboard
it should trigger the save button of mission control

The create project UI has been updated but isn't binding with space-cloud yet. Needs to be done

Right now the Mission Control doesn't send the Authorization header while fetching DB connection status from Space Cloud. This results in an error when Space Cloud is run in PROD mode.

Let's send the Authorization header in each and every request.

Right now the user is provided a single field for editing connection string. The problem with this is that the user has to learn the format of connection string.

We should perhaps provide a connection string builder like this:

This can make it easier for users to play around with the connection string

We need a notification to show whether the config has been updated successfully

When space-cloud/pull/508 is merged, UI-support for configuring the logging should be added.

https://docs.spaceuptech.com/auth/authorization/database/
following is the link header

on click it doesn't forward to the content directly

There are eventing functions in dbAction.js file
Remove eventing functions from dbAction.js and put in the appropriate place mostly in utils.js file

Right now the Mission Control allows an user to make two projects with same name (resulting in same project IDs), which shouldn't be allowed. We should prevent this while the user is creating a project, informing him that such project already exists.

when i add a rule for a collection that doesnt exist, that rule name gets added to the list of tables in the overview page
and when i try to delete it, i get an error saying such table doesnt exist

Right now the user has to manually type the entire rule to edit a rule. It could be great, if the rules editor provided auto complete for keywords in rules (eg: op, f1, f2).

The links do not redirect to any pages

https://docs.spaceuptech.com/storage/database/mutations/

While creating a new collection/table, the schema textbox has a default schema value which is derived from the table name. However, after changing the schema, if we change the table name in the form, the value of schema gets overwritten by the default schema

We need an option to delete a project in mission control. This is already implemented in space cloud.

When creating a collection and updating the collection name, the entire scheme-description is reset.
I guess this is due to the automatically generated skeletal structure of the type that also includes the name of the collection.

There are still links to the plans page which have been removed. Remove all such linkages.

There are many places where we do not provide a link to the relevant docs. Here's a list:

• Add / Edit table model
• Connection string (whats the format for each database)

the event trigger which are alread created, but when clicked on edit button the name of existing event is not shown in the modal

The Make First DB Query button seems to be taking more space than expected on the overview page

Right now the user has to remember the possible field types and directives (eg: @unique, @relation, etc.) while writing schema. It would be great, if this could be autocompleted.

In mission control, while previewing mutations, this is what is shown to us

I believe that the right hand side should also be delete_table.

I also think that this is due to this code in utils.js/generateQueries :

queries.delete.res = removeRegex(`{ 
      "data":{ 
        "insert_${colName}":{ 
          "status": 200
        }
       }
      }`, 1)

Let's not do that. The user has to type the schema all over again because of that.