declarations under manifest cache
Reported by bahuvrihi | September 10th, 2008 @ 09:49 AM | in Tap-0.11.0
When manifest cache has been implemented, you could have another task declarator:
module Sample
module Nest
include Tap::Support::Declarations
# ::desc short description
# This is the long description of A
tasc :a
# ::desc short description
# This is the long description of B
tasc :b => :a
end
end
'desc' very much like Rake. In this case desc signifies that the file should be loaded and manifest information pulled from it. That way, the tasks will be naturally named in their proper subclasses and no long namespaces need to be specified in the documentation.
Comments and changes to this ticket
-
bahuvrihi September 10th, 2008 @ 09:58 AM
- Milestone set to Tap-0.11.0
-
bahuvrihi October 11th, 2008 @ 09:08 AM
- Assigned user set to bahuvrihi
- State changed from new to resolved
- Tag changed from feature, tap to feature, tap
Implemented without manifest cache.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
A framework for making configurable, file-based tasks and workflows.