Network mapped paths resolve differently in Atom 1.12

Prerequisites

For more information on how to write a good bug report or enhancement request, see the CONTRIBUTING guide.

Description

Since Atom 1.12 beta the paths of files on network mapped drives are resolved with the full server name instead of the path of the network mapped drive. This caused problems with restoring the session of projects on network mapped drives when upgrading to Atom 1.12.

Example: \\server\path\to\folder is mapped to Y:\. Atom restores the session with the Y:\ path but all new files open with the \\server\path\to\folder path. So you have to close and reopen all files you previously had opened to not have duplicate files open. This also can cause the UNC path error when running the linter on beta.

I did discover that the tree-view still has the old path if you copy the full path of some file and the title bar of Atom also displays the network mapped drive label. So currently we display both of the paths in different parts of Atom.

Atom 1.12.0-beta5 paths

path stuff

Atom 1.11.2 paths

path stuff 1 11

Upgrading from 1.11 to 1.12

path stuff upgrade

Steps to Reproduce

  1. Install Atom 1.11.2
  2. Map a network drive on Windows
  3. Open a folder on the network mapped drive
  4. Open some files for example: Y:\file.txt
  5. Install Atom 1.12-beta5
  6. Paths from previous session restore as Y:\file.txt
  7. Open Y:\file.txt from the tree-view a duplicate tab opens as \\server\path\to\folder\file.txt

Expected behavior: Paths to be consistent across Atom. Upgrade to be smooth so users don’t have to close every file after upgrading to avoid opening duplicate files.

Actual behavior: Paths are inconsistent. Upgrade from 1.11 to 1.12 not smooth.

Versions

atom --version

Atom    : 1.12.0-beta5
Electron: 1.3.6
Chrome  : 52.0.2743.82
Node    : 6.3.0
apm --version

apm  1.12.5
npm  3.10.5
node 4.4.5
python 2.7.11
git 2.10.1.windows.1
visual studio 2015

1 possible answer(s) on “Network mapped paths resolve differently in Atom 1.12