{"action":"opened","issue":{"url":"https://api.github.com/repos/dsheets/codoc/issues/52","labels_url":"https://api.github.com/repos/dsheets/codoc/issues/52/labels{/name}","comments_url":"https://api.github.com/repos/dsheets/codoc/issues/52/comments","events_url":"https://api.github.com/repos/dsheets/codoc/issues/52/events","html_url":"https://github.com/dsheets/codoc/issues/52","id":56833689,"number":52,"title":"Don't linkify path components. ","user":{"login":"dbuenzli","id":485596,"avatar_url":"https://avatars.githubusercontent.com/u/485596?v=3","gravatar_id":"","url":"https://api.github.com/users/dbuenzli","html_url":"https://github.com/dbuenzli","followers_url":"https://api.github.com/users/dbuenzli/followers","following_url":"https://api.github.com/users/dbuenzli/following{/other_user}","gists_url":"https://api.github.com/users/dbuenzli/gists{/gist_id}","starred_url":"https://api.github.com/users/dbuenzli/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dbuenzli/subscriptions","organizations_url":"https://api.github.com/users/dbuenzli/orgs","repos_url":"https://api.github.com/users/dbuenzli/repos","events_url":"https://api.github.com/users/dbuenzli/events{/privacy}","received_events_url":"https://api.github.com/users/dbuenzli/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-02-06T16:30:03Z","updated_at":"2015-02-06T16:30:03Z","closed_at":null,"body":"I argue that most of the time you want to get to the definition of the last component of the path (i.e. final, type, value or module). However currently `codoc` linkifyes each component, because of Fitts's law it makes it hard to reach that target --- especially since our type names are often called `t`.\r\n\r\nWhen I have `M2.M1.t`, I really have to aim to click on that little `t` to get to what I want. This makes my browsing very slow and I hate that. I think you should link the whole path to the final component only (N.B. the behaviour I describe I actually `ocamldoc`'s one). \r\n\r\nGoing up in the hierarchy is quick enough if you need to: after you got to the def scroll up once to the top and then it's all about clicking on up/up once or twice (but again it's most of the time it's not what you are interseted in). \r\n\r\n\r\n\r\n"}}