NAntCollections Work Item Rss Feed

Created Issue: Fix the "static-ness" of the dictionaries / lists for sessions

JeffyW — Wed, 23 Jul 2008 16:31:03 GMT

If a nant task calls the <nant> target calling a script which subsequently loads dictionaries, those dictionaries collide and overwrite each-other. These should be isolated.

CREATED ISSUE: Clean up errors in documentation

JeffyW — Thu, 01 Nov 2007 20:15:21 GMT

This ticket will be used to track as many errors in documentation that should be cleaned up for the next release:

dict::contains-key
<echo message="MyFirstKey found: ${dict::contains-key('MyDict','MyFirstKey)}"/>
<echo message="MyThirdKey found: ${dict::contains-key('MyDict','MyThirdKey)}"/>
- Should read -
<echo message="MyFirstKey found: ${dict::contains-key('MyDict','MyFirstKey')}"/>
<echo message="MyThirdKey found: ${dict::contains-key('MyDict','MyThirdKey')}"/>

list-create
<list-create dictionary="MyList">
- Should read -
<list-create list="MyList">

COMMENTED ISSUE: New function "list::top"

jkohlhepp — Thu, 01 Nov 2007 01:32:57 GMT

I'd like to see a function that will return the value of the last item added (the "top") much like the "pop" function without removing that item. This will allow me to add an item and then reference it like:

<list-add list="xyz" value="item"/>
<property name="action.${list::top('xyz')" value="something"/>

Currently I
<property name="a" value="item"/>
<list-add list="xyz" value="${a}"/>
<property name="action.${a}" value="something"/>
Comments: ** Comment from web user: jkohlhepp **

Could you just do a ${list::get-item(list::count-1))}? Not sure if "get-item" is the name of the function but you get the idea...

CREATED ISSUE: New function "list::top"

JeffyW — Tue, 30 Oct 2007 19:15:23 GMT

CREATED FEATURE: Initialize collection from external file

jkohlhepp — Thu, 18 Oct 2007 11:32:21 GMT

It is desirable to have the initial values of a dictionary or list loaded from an external file. Not sure what the format of the external file should be, but it might be easiest if we kept the same NAnt syntax and hijacked the NAnt parser to read it. So the NAnt task would look like this:

<list-create sourceFile="c:\blah.xml"/>

and the external file would look like this:

<list-item value="1"/>
<list-item value="2"/>
<list-item value="3"/>

(Not sure if that syntax matches NAntCollections exactly; been awhile since I looked at the code.)

CLOSED FEATURE: list-unshift, list::shift

JeffyW — Tue, 10 Jul 2007 01:41:44 GMT

Add items to make it easier to use list as a stack (fifo).

REOPENED FEATURE: list-unshift, list::shift

JeffyW — Tue, 10 Jul 2007 01:41:25 GMT

Add items to make it easier to use list as a stack (fifo).
Comments: ** Comment from web user: JeffyW **

Add to release 0.2

CLOSED FEATURE: list-unshift, list::shift

JeffyW — Sun, 08 Jul 2007 23:46:11 GMT

Add items to make it easier to use list as a stack (fifo).

COMMENTED FEATURE: list-unshift, list::shift

JeffyW — Sun, 08 Jul 2007 23:46:03 GMT

Add items to make it easier to use list as a stack (fifo).
Comments: ** Comment from web user: JeffyW **

Finished and checked in.

CREATED ISSUE: packaging - SLN contains SCC binding

jkohlhepp — Sun, 08 Jul 2007 20:05:56 GMT

There is an issue with packaging the source for release. The SLN gets included with the src zip file, but this SLN has the TFS SCC binding in it for Codeplex. As a consequence, anyone who opens the SLN will be prompted for the username/pass for codeplex and will have to click through several warnings and dialogs before they can get into the source.

CLOSED TASK: Examples in XML documentation

jkohlhepp — Sat, 07 Jul 2007 23:06:36 GMT

The XML documentation for functions and tasks does not contain examples. Examples make the generated documentation easier to use. See the NAnt source for how to format examples in the XML comments.
Comments: Examples now present on all tasks and functions.

CLOSED FEATURE: list-push, list::pop

JeffyW — Sat, 07 Jul 2007 17:14:34 GMT

These would allow for lists to be more easily used as a stack.

COMMENTED FEATURE: list/dict -push, ::pop

JeffyW — Sat, 07 Jul 2007 17:14:31 GMT

These would allow for lists/dictiontaries to be more easily used as a stack.
Comments: ** Comment from web user: JeffyW **

As discussed with Justin, no need for this functionality with dictionaries.

COMMENTED FEATURE: list/dict -unshift, ::shift

JeffyW — Sat, 07 Jul 2007 17:13:45 GMT

Add items to make it easier to use list / dict as a stack (fifo).
Comments: ** Comment from web user: JeffyW **

As discussed with Justin, no need for this functionality in dictionaries.

CREATED FEATURE: list/dict -unshift, ::shift

JeffyW — Sat, 07 Jul 2007 17:00:51 GMT

Add items to make it easier to use list / dict as a stack (fifo).

CLOSED FEATURE: list-create, dictionary-create

jkohlhepp — Sat, 07 Jul 2007 16:52:30 GMT

It would be nice if we could have a syntax like this:

Instead of this:

The top syntax has the list name once, while the bottom requires it for each item. A similar syntax could be done for dictionaries.
Comments: Added.

CLOSED FEATURE: list::is-empty and dict::is-empty

JeffyW — Sat, 07 Jul 2007 15:47:43 GMT

Both should return true if the collection does not exist. Calling them should not *create* the collection.

CLOSED TASK: Build scripts

JeffyW — Sat, 07 Jul 2007 15:08:42 GMT

We need some NAnt scripts to build a release version of the library. These scripts should build the project for release, run the UTs, build the NDoc docs, possibly update the assembly versions, etc.

CLOSED ISSUE: NAntCollections.Tests should be friend assembly of NAntCollections

jkohlhepp — Sat, 07 Jul 2007 03:01:33 GMT

In order to make the UTs execute NAnt in-process, the test scripts needed to reset the ListManager and DictionaryManager before each test. This required making those manager classes public when they should really be internal. If the NAntCollections.Tests assembly were a friend assembly then this wouldn't be necessary.
Comments: Done.

CREATED ISSUE: NAntCollections.Tests should be friend assembly of NAntCollections

jkohlhepp — Sat, 07 Jul 2007 01:11:40 GMT