René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Improve Path.parse / Path.format combo","articleBody":"We have `Path.format` / `Path.parse` functions.\nThey can be chained which is very convenient.\n\n``` js\nimport Path from \"path\";\n\nlet path = \"/foo/bar/bazz.js\";\nlet pathP = Path.format(Path.parse(path));\n```\n\nCurrently `parse` converts string to an object with such structure\n\n``` js\n{ root: '/',\n  dir: '/Users/ivankleshnin/Projects/demo',\n  base: 'config.yml',\n  ext: '.yml',\n  name: 'config' }\n```\n\nThis object contains denormalized data between `base`, `name` and `ext` key values.\nNow let's try to replace file extension.\n\n``` js\nimport Path from \"path\";\nimport {assoc} from \"ramda\"\n\nlet path = \"/Users/ivankleshnin/Projects/demo/config.js\";\nlet pathP = assoc(\"ext\", \".json\", Path.parse(path));\n/* {...\n  base: 'config.js',  -- these two are \n  ext: '.json',       -- unsynced!\n...} */\nconsole.log(Path.format(pathP)); // extension weren't changed :(\n```\n\nThe simplest task is going to be not so simple?!\nNow if `format` took into consideration `ext` and `name` rather than `base` this could lead to an equal problem with changes to `base` key being ignored. \n\nCan we get rid of this `base` key?  It's always `parsed.name + parsed.ext` formula, not a big deal to make it manually. Example of hidden file parse: `{ base: '.gitignore', ext: '', name: '.gitignore' }` - same rule apply.\n\nWe can probably also implement it in a backward-compatibile way,\nkeeping `base` but using JS getter / setter for it's evaluation.\n","author":{"url":"https://github.com/ivan-kleshnin","@type":"Person","name":"ivan-kleshnin"},"datePublished":"2015-06-17T08:54:39Z","url":"https://github.com/nodejs/node/issues/1999"}