Changes between Version 46 and Version 47 of CodeTagsPlugin


Ignore:
Timestamp:
Apr 12, 2017, 10:00:54 PM (7 years ago)
Author:
figaro
Comment:

Typo

Legend:

Unmodified
Added
Removed
Modified

  • CodeTagsPlugin

    v46 v47  
    11[[PageOutline(2-5,Contents,pullout)]]
    22
    3 = A plugin for displaying code tags (`XXX`, `FIXME`, `TODO`, etc.)
     3= Add code tags (`XXX`, `FIXME`, `TODO`) to source code
    44
    55== Description
    … …  
    1010 * `XXX` is for things that require more thought and that are arguably broken.
    1111
    12 See [http://c2.com/cgi/wiki?FixmeComment FixmeComment].
     12See [http://c2.com/cgi/wiki?FixmeComment FixmeComment] for a background to this plugin.
    1313
    14 You need a subdirectory named `cache` that is writeable by your Trac to make this work. This takes some time the first it is used. Also don't forget to grant the `CODETAGS_VIEW` permission to your users.
     14You need a subdirectory named `cache` that is writeable by your Trac to make this work. This takes some time when it is first used. Also don't forget to grant the `CODETAGS_VIEW` permission to your users.
    1515
    1616== Bugs
    … …  
    2525
    2626Plugin does not handle multiple repositories well:
    27  * if no default set, `get_repository(None)` will return `None`
    28  * Even if a default is set, it will only parse this repository
    29  * Fixed by patch [attachment:basic_multirepo_support.patch]
     27 * If no default is set, then `get_repository(None)` will return `None`.
     28 * Even if a default is set, it will only parse this repository.
     29 * Fixed by patch [attachment:basic_multirepo_support.patch].
    3030
    3131== Feature Requests
    3232
    3333Since the tracker has no !CodeTags component I will put that here:
    34  * feature "upgrade CodeTag to issue". Click on one of the CodeTags to be brought to a "New Ticket" page, with fields already completed (will require some parsing). Bonus points if the CodeTag (and surrounding comments, which might be numerous) can optionally be removed from the SVN and a commit log entry automatically generated.
     34 * Feature "upgrade CodeTag to issue". Click on one of the CodeTags to be brought to a "New Ticket" page, with fields already completed (will require some parsing). Bonus points if the CodeTag (and surrounding comments, which might be numerous) can optionally be removed from the SVN and a commit log entry automatically generated.
    3535 * Having a huge code base makes the table with the tags so huge that even modern browsers can hardly display it. Maybe:
    3636  * Split it up into multiple pages