-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Any plans for WorkItems? #7
Comments
I would definitely accept pull requests. Work items are definitely very useful, but I've been slammed with the VS and TFS 2015 releases lately. If you had some bandwidth and wanted to work on work items, that would be great! |
I was about 2 hours into implementing Work item support when I posted this, so that's great to hear. I plan to use this for a Plastic SCM issue tracking extension for VSO / TFS, and so Work Items are pretty critical to that. ;) How would you go about handling the "Fields" returned with the work items? They're completely configurable, so we can't bind them directly to properties. My best idea so far is to bind the fields to a Key/Value dictionary, and then provide properties for the common ones (such as title and work item type). Do you have any opinions on the matter? Also, would you be opposed to me cleaning things up a bit elsewhere as I go? locally I've moved all of the Model classes into subfolders based on logical groupings (Git, Projects, etc) and I've changed how the your AddOptionalParameter function works slightly. |
@Quantumplation not sure how far you got into this, let me know if I can help. |
Oh gosh, this was so long ago haha. IIRC I got really far into it, but I have no idea which of my harddrives that code would be on these days. I'll poke around if I get some free time. |
This library looks really high quality, but the last commit was in January. Do you have plans to implement Work Item querying? Without that, it's of rather limited usefulness. Would you accept Pull Requests for it?
Regards,
Pi Lanningham
The text was updated successfully, but these errors were encountered: