Hi sri,
here are my three wishes:
1. in a Mojolicious app, it would be nice to be able to run selected tests
from the "t" directory more easily, like so:
myapp test -v test3 test5
Currently I have to do
myapp test -v ~/experiments/mojo/myapp/t/test3
~/experiments/mojo/myapp/t/test5
Maybe Mojolicious::Command::test could first check for each argument if a
file with that name exists in the t directory?
2. it would be nice if a Mojolicious app could display descriptions and
usage on the command line for all Command packages in the app.
Currently it picks up only those that have their own files. My command
packages are often so short that it's more handy to have them in the app
file itself.
3. I work a lot with Mojo::Collections and find myself often writing code
like "push @{$self->item->fields}, $something". I would suggest to add
methods push, pop, unshift, shift and list to the module (which would
operate on the collection and not create a new one). This way one could
avoid the unwieldy array dereference and even chain the methods like this:
$self->item->fields->push($something)->each(sub {...}).
The pop and shift methods would be useful when the collection contains
objects with methods.
The list method should just return the dereferenced collection (like
@$collection).
I know a similar proposal has been declined before, but I think it would
make code more readable and more conform to the Mojo feel :-)
Love it!
Martin
--
You received this message because you are subscribed to the Google Groups
"Mojolicious" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/mojolicious.
For more options, visit https://groups.google.com/d/optout.
