lentil 0.1.4.1 → 0.1.5.0

raw patch · 8 files changed

+28/−7 lines, 8 files

Files

• changes.txt +9/−2
• doc/usr/page.rst +5/−1
• issues.txt +5/−0
• lentil.cabal +1/−1
• src/Lentil/Parse/Issue.hs +3/−1
• src/Main.hs +1/−1
• test/Lentil/Parse/IssueSpec.hs +3/−0
• test/test-files/lang-comm/pascal.pas +1/−1

@@ -1,14 +1,21 @@+0.1.5.0+-------++- Released Tue 29 Sep 2015 14:32:11 CEST+- Tags are now allowed at the beginning of the issue, before the description,+  too (request by qptain nemo).+ 0.1.4.1 -------  - Released Wed 26 Aug 2015 22:11:33 CEST-- Added ".cabal" ".chs" ".hsc" (request by Henning Thielemann)+- Added ".cabal" ".chs" ".hsc" (request by Henning Thielemann).  0.1.4.0 -------  - Released Wed 26 Aug 2015 19:42:05 CEST-- Added SQL-like string parsing (requested by qptain nemo)+- Added SQL-like string parsing (requested by qptain nemo).  0.1.3.1 -------

@@ -121,12 +121,16 @@   -- FIXME  -You can optionally put tags at the end of your issue, like this:+You can optionally put tags at the end or at the beginning of your issue,+like this:  ::    // FIXME: Mr. Burns should enter from the *right* side of the   //        nuclear station [script] [priority:1]++  -- todo: [rhyme] [magic] double trouble... I always forget the+  --       words :s [memory]  Tags are single words which are useful to catalogue and identify issues. Use them aplenty as they will make slicing and dicing your issue-base a breeze.

@@ -1,3 +1,8 @@+important: symlinks, windows, inceppa linux kernel, brogress bar, history+like sm suggests?, help as lentil PATH [PATH...], fast file programming,+extensible langparse,+henning newfiles+ bin/make-bins.hs     20  auto search (global? cpp?) version number? [dist]  

@@ -1,5 +1,5 @@ name:                lentil-version:             0.1.4.1+version:             0.1.5.0 synopsis:            frugal issue tracker description:         minumum effort, cohesive issue tracker based on                      ubiquitous @TODO@s and @FIXME@s conventions.

@@ -125,15 +125,17 @@ -- an issue is a flagword, followed by : , followed by some description and -- ended optionally by some tags (No t/f? End by whiteline or eof or -- another TODO).+-- tags can be placed *before* description, too issue :: ParIssue Issue issue = (mkIssue <$> incipit                  <*> fmap sourceName getPosition                  <*> (fmap sourceLine getPosition)+                 <*> option [] (try tags)                  <*> freeText                  <*> option [] (try tags))         <?> "issue"     where-          mkIssue fw fp ln ds tgs = Issue fp ln ds (addTag fw tgs)+          mkIssue fw fp ln tg1 ds tg2 = Issue fp ln ds (addTag fw (tg1++tg2))            addTag Todo tgs = tgs           addTag fw   tgs = (Tag $ fw2s fw) : tgs

@@ -28,7 +28,7 @@                                    short 'v'      <>                                    help "show version and copyright info" )     where-          versionCopy = "lentil - frugal issue tracker, version 0.1.4.1\n\+          versionCopy = "lentil - frugal issue tracker, version 0.1.5.0\n\                         \(C) 2015 Francesco Ariis - http://www.ariis.it\n\                         \released under the GNU General Public License v3\n" 

@@ -134,6 +134,9 @@     it "does parse an empty todo + tags" $       sp issue "\ntodo [alfa]\n"          `shouldBe` (Just $ Issue "<f>" 2 Nothing [Tag "alfa"])+    it "does parse tags before description" $+      sp issue "\ntodo [alfa] beta\n"+         `shouldBe` (Just $ Issue "<f>" 2 (Just "beta") [Tag "alfa"])    describe "issues" $ do     it "parses multiple issues" $

@@ -6,6 +6,6 @@ c := '"' // char  { TODO: block1 }-(*   todo block2 [tog] *)+(*   todo [tog] block2 *)  //  end