Skip to Main Content

MongoByte MongoDB Logo

Welcome to the new MongoDB Feedback Portal!

{Improvement: "Your idea"}
We’ve upgraded our system to better capture and act on your feedback.
Your feedback is meaningful and helps us build better products.

Status Submitted
Categories IDEs
Created by Guest
Created on May 12, 2021

Improvements to Terminal Shell (split)

It would be nice that When the VSC extension is added, it creates an entry in the integrated terminal settings (terminal.integrated.automated.windows/mac) like: - "MongoDB": { "path": "mongo", "args": ["$Env:MDB_CONNECTION_STRING"] } Which I can't currently get to work. So that when I split a currently connected MongoDB intergrated terminal session, it spawns another mongo session with the same connection parameters at the same level. Also at the moment $Env:MDB_CONNECTION_STRING only seems to be set when the MongoDB:Launch MongoDB Shell is run, not when a connection is made to the a MongoDB server (connections). At the moment, if the user uses MongoDB:Launch MongoDB Shell, it creates a new integrated terminal view and doesn't seem to allow for a split view. See screen shot. PS - please sort out this text entry box, so it's resizeable, its not the 90's :)
  • Guest
    May 13, 2021
    EDIT: So comment should be read after my earlier comment. Actually, what would be even better, is being able to add to the connections panel, a context option of "Create Terminal Session", or whatever is appropiate, maybe with a split option (See screen shot in link above) This would create a terminal session on the connection, without having to change the connected session, against which the playground runs. Across the bottom of VSC the user could have easy access to multiple mongodb servers, based upon the connections that had already been setup. My only concern, would be tracking them. So if possible, then connection name is present in the terminal session. So at the moment, I would create a powershell, and it's tab would say powershell, however if it said, if created by the extension, M001Atlas or whatever the name of the connection was called. This would allow the user to track where they are connected to.
  • Guest
    May 12, 2021
    If that's not possible, then add option to the connections, along delete/refresh etc, so a right click on the connect with an option "SET ENV VARIABLE". So that I could take the connection string, go to a terminal session and do Mongo $ENV:MDB_CONNECTIONS_STRING Which allows a quick connection to any server in the list, from the terminal. It would allow easy way of having multiple terminal sessions to multiple servers at the same time. Super :)
  • Guest
    May 12, 2021
    It would be nice that When the VSC extension is added, it creates an entry in the integrated terminal settings (terminal.integrated.automated.windows/mac) like: - "MongoDB": { "path": "mongo", "args": ["$Env:MDB_CONNECTION_STRING"] } Which I can't currently get to work. So that when I split a currently connected MongoDB intergrated terminal session, it spawns another mongo session with the same connection parameters at the same level. Also at the moment $Env:MDB_CONNECTION_STRING only seems to be set when the MongoDB:Launch MongoDB Shell is run, not when a connection is made to the a MongoDB server (connections). At the moment, if the user uses MongoDB:Launch MongoDB Shell, it creates a new integrated terminal view and doesn't seem to allow for a split view. See screen shot. PS - please sort out this text entry box, so it's resizeable, its not the 90's :) PPS - When I tried to submit an entry, with a JPG, the entry form came back with a "Sorry, we couldn't submit your request. So here is a link to the forum post about this request. https://developer.mongodb.com/community/forums/t/vsc-extension-mongodb-integration-into-the-terminal-options/106552/3?u=neilm