[GRASS-dev] [GRASS GIS] #2864: Add link to source code in the documentation pages.

[GRASS GIS]

#2864: Add link to source code in the documentation pages.
--------------------------+----------------------------------
  Reporter:  pmav99       |      Owner:  grass-dev@…
      Type:  enhancement  |     Status:  new
  Priority:  normal       |  Milestone:  7.0.4
 Component:  Docs         |    Version:  svn-releasebranch70
Resolution:               |   Keywords:  open science, access
       CPU:  Unspecified  |   Platform:  Unspecified
--------------------------+----------------------------------

Comment (by lucadelu):

 Replying to [comment:8 pmav99]:
 > Thank you all,
 > As far as I am concerned, the two lines seems cleaner to me. Now with
 regard to the link itself.
 >
 > 1. I am not sure if hard-coding the link to trunk is the best option.
 Since the documentation of multiple GRASS versions are online (i.e. 6.4,
 7.0, 7.1) I think that the link should point to the respective branch.

 It is hard-coded only because the idea is to have a url for each version.
 there is a variable and it is changed only once. Using the dictionary
 mapping it is more or less the same, when a new version will come it
 should be added to the dictionary.
 With only a variable there is less code and it should be a little bit
 faster.

 > 2. Since I guess that many users like myself don't have any particular
 knowledge of the GRASS code structure, in order to make this even more
 useful I think that the links themselves should directly point to the
 directory that contains the command in question.
 >

 If I understand correctly it is already like that

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/2864#comment:9>
GRASS GIS <https://grass.osgeo.org>