Front end changes for the "New Database Connection" form

[seancolsen]

See these specs.

Case A	Case B	Case C

[seancolsen]

I have a small design question about this feature. Not sure of the best place to ask, so I'm starting here. @ghislaineguerin @pavish @kgodey @mathemancer I'm tagging you to see if you want to weigh in with your opinion.

After a user adds a new connection, what should happen next?

• (A) close the modal, showing the table of all connections.

  We follow this pattern when creating new schemas. It would be the easiest to implement.

  This is potentially annoying if there are already lots of connections though. It's not necessarily easy to find the one you just added.

• (B) same as (A), but also highlight the new connection.

  We don't think we follow this pattern anywhere.

  We could highlight the new one, but doing this well would be slightly complex (I can explain more if needed). This would be the hardest to implement of all the options.

• (C) navigate to the Database Page for the connection

  We follow this pattern when creating new tables because we navigate to the table.

  This is probably what most users would want, and it would be very easy to implement.

  I'm leaning towards this.

• (D) give the user a choice

  We don't follow this pattern anywhere, but for the Add Record page (yet to be implemented) it's important to me that we do establish a pattern like this.

  Here's an example of what this could look like for the New Connection modal:

  

  In the footer, we'd have this select input which would default to "Open", meaning that Mathesar would navigate to the Database Page for that connection. I like this pattern because I think it gives users a clearer expectation of the next step and it allows them to quickly add several connections in sequence.

  This would be relatively easy to implement.

[ghislaineguerin]

@seancolsen I'm also leaning towards option C. I think option D makes sense for the "Add Record Page" but not sure if needed for connections, since adding multiple seems unlikely.

[seancolsen]

Sounds good, @ghislaineguerin. I'll go with that unless anyone else wants to voice other opinions.

[pavish]

@seancolsen I also think C is the best option.

[kgodey]

+1 to option C.