-
Notifications
You must be signed in to change notification settings - Fork 404
Closed
Labels
area/configIssues related to the configIssues related to the configarea/syncIssues related to the real-time code synchronizationIssues related to the real-time code synchronizationarea/terminalIssues related to the terminal proxyIssues related to the terminal proxykind/featureNew feature or feature requestNew feature or feature request
Description
Is your feature request related to a problem?
No
Which solution do you suggest?
A configuration option to block opening the shell into the container until the sync process is initially caught up.
Which alternative solutions exist?
Additional context
My project can be rather large, especially if syncing all the dependencies.
I could exclude the dependencies from syncing, but overall it saves time to go ahead and let them sync.
However, if a developer gets into the project they can't really tell when everything is synced up without looking at the sync.log file. This might lead them to go ahead run the command to install all the dependencies themselves, or other commands that won't work correctly until everything is synced.
/kind feature
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area/configIssues related to the configIssues related to the configarea/syncIssues related to the real-time code synchronizationIssues related to the real-time code synchronizationarea/terminalIssues related to the terminal proxyIssues related to the terminal proxykind/featureNew feature or feature requestNew feature or feature request