You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Users are sometimes caught by surprise when fs is set to remote but a file is read locally. We should show a warning the first time the app reads a local file from the override list, explaining the behavior and linking the full list of the overridden paths. Don't forget "Don't show again".
The text was updated successfully, but these errors were encountered:
Before we start this, we need some mechanism to pass messages from our hooks to the user. Something that would allow us communicate back from mirrord to the IDEs.
We could have a temporary file (maybe even in-memory only) that we write only important things to it, and the IDE reads those (tl;dr: our own stdout).
Before we start this, we need some mechanism to pass messages from our hooks to the user. Something that would allow us communicate back from mirrord to the IDEs.
We could have a temporary file (maybe even in-memory only) that we write only important things to it, and the IDE reads those (tl;dr: our own stdout).
We could expose logs via websockets and have the IDE open a new terminal tab for display (would require either merging mirrord-console to CLI or moving the logs to the new intproxy)
Users are sometimes caught by surprise when fs is set to remote but a file is read locally. We should show a warning the first time the app reads a local file from the override list, explaining the behavior and linking the full list of the overridden paths. Don't forget "Don't show again".
The text was updated successfully, but these errors were encountered: