{"action":"created","issue":{"url":"https://api.github.com/repos/npm/normalize-git-url/issues/3","labels_url":"https://api.github.com/repos/npm/normalize-git-url/issues/3/labels{/name}","comments_url":"https://api.github.com/repos/npm/normalize-git-url/issues/3/comments","events_url":"https://api.github.com/repos/npm/normalize-git-url/issues/3/events","html_url":"https://github.com/npm/normalize-git-url/pull/3","id":94907219,"number":3,"title":"Emulate old behavior for git+https:// urls and just warn about it","user":{"login":"zkat","id":17535,"avatar_url":"https://avatars.githubusercontent.com/u/17535?v=3","gravatar_id":"","url":"https://api.github.com/users/zkat","html_url":"https://github.com/zkat","followers_url":"https://api.github.com/users/zkat/followers","following_url":"https://api.github.com/users/zkat/following{/other_user}","gists_url":"https://api.github.com/users/zkat/gists{/gist_id}","starred_url":"https://api.github.com/users/zkat/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zkat/subscriptions","organizations_url":"https://api.github.com/users/zkat/orgs","repos_url":"https://api.github.com/users/zkat/repos","events_url":"https://api.github.com/users/zkat/events{/privacy}","received_events_url":"https://api.github.com/users/zkat/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-07-14T09:45:11Z","updated_at":"2015-07-14T21:55:45Z","closed_at":null,"pull_request":{"url":"https://api.github.com/repos/npm/normalize-git-url/pulls/3","html_url":"https://github.com/npm/normalize-git-url/pull/3","diff_url":"https://github.com/npm/normalize-git-url/pull/3.diff","patch_url":"https://github.com/npm/normalize-git-url/pull/3.patch"},"body":"Before my big `git` fix, we were accepting bad-format `git+https://` URLs and converting them to use absolute paths during normalization. This brings back only that specific old behavior, and warns about its deprecation.\r\n\r\nNote: idk what the _proper_ way to deprecate is, and I assume it's not a `console.warn`?"},"comment":{"url":"https://api.github.com/repos/npm/normalize-git-url/issues/comments/121403593","html_url":"https://github.com/npm/normalize-git-url/pull/3#issuecomment-121403593","issue_url":"https://api.github.com/repos/npm/normalize-git-url/issues/3","id":121403593,"user":{"login":"iarna","id":983798,"avatar_url":"https://avatars.githubusercontent.com/u/983798?v=3","gravatar_id":"","url":"https://api.github.com/users/iarna","html_url":"https://github.com/iarna","followers_url":"https://api.github.com/users/iarna/followers","following_url":"https://api.github.com/users/iarna/following{/other_user}","gists_url":"https://api.github.com/users/iarna/gists{/gist_id}","starred_url":"https://api.github.com/users/iarna/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/iarna/subscriptions","organizations_url":"https://api.github.com/users/iarna/orgs","repos_url":"https://api.github.com/users/iarna/repos","events_url":"https://api.github.com/users/iarna/events{/privacy}","received_events_url":"https://api.github.com/users/iarna/received_events","type":"User","site_admin":false},"created_at":"2015-07-14T21:55:45Z","updated_at":"2015-07-14T21:55:45Z","body":"Hoisting my comment out of amended comment limbo, in reply to adding a deprecation in npm directly, using depr check:\r\n\r\nI'm of mixed feelings– I'd love to see a better validation mechanic for the cli (`normalize-package-data` is annoying both due to the fact that it at its core is a data fixer AND because its oridinarily invoked via `read-package-json`)– but delaying a _bug fix_ for architecture ... doesn't pass my cost/benefit balance. And the alternative, adding a regex check directly in the caching code, feels like we're moving backwards here. Long term having the caching code emit deprecation warnings feels ... very poorly factored to me. What was the value in pulling this out in the first place if we then have to copy arbitrary bits of it back…"}}