Commit Graph

7 Commits (34286dbecdb339569d8e80c568dba31bfe9e3bc7)

Author SHA1 Message Date
Charlie Garrison e68b021379 Handle bare query for all startend triggers
Signed-off-by: Charlie Garrison <cngarrison@gmail.com>
2015-12-25 21:18:33 +11:00
Chris Wilson 2f11d6cc76 Update Binary IA to Uppercase. Fix All Test Cases for Uppercase Changes. 2015-01-09 19:46:54 +11:00
Matt Miller f63d3df4fd Passphrase: add structured answer. 2014-11-15 21:32:59 +02:00
Matt Miller 68fc7c8dec Set explicit caching everywhere.
This explicity sets the caching behavior for all goodies. Goodies which
did not have caching behavior set in their package have had it added.
Similarly for the tests.

This resulted in a number of changes for caching behavior, mostly
moving towards more frequent caching.

I identified three cases where goodies should not be cached. They are when
the result depends upon:

- some random element,
- the time of day or year (as with relative dates), or
- the location of the requesting user

In all other cases, I presumed that the goodies were sufficiently
deterministic in their output to warrant caching.
2014-09-27 10:35:17 -04:00
Matt Miller f345498b62 Passphrase: expand triggers.
Will now respond to queries like "5 word passphrase", "pass phrase 3
random words" and even "create random passphrase"

Tests updated to be more robust, cover the example queries and show
some new possibilities.

Also adds an abstract to reduce the scroll-spam on `dzil test`

Big thanks to @moollaza for both the suggestion and guidance.
2014-02-11 12:15:07 +08:00
Matt Miller 43aaef92cf Passphrase: bring up to current standards.
Intended to fix issue #313 and also fix #314.

- Add ability to use queries like "pass phrase 3 words"
- Add comments describing how it works.
- Add (arbitrarily chosen) limit of 10 words maximum.
- Constrain the query format more tightly
- Add more tests

This turned into more of a rewrite than I intended.

In the previous version, it was more forgiving about what trailed the
number of words requested... but it was assuredly requiring something.
I've decided to be explicit on wanting 'word(s)' at the end.

Previously it required a minimum of 1 word requested, but didn't have a
maximum.  I chose to make the max 10, as it keeps the output fairly
tidy and seems like a reasonable maximum someone might actually use
in practice.
2014-02-08 09:34:06 +08:00
Dylan Lloyd 3fdbe37cb1 rm'd old example files,new tests for those missing
also stripped carriage returns and trailing whitespace from share files
2013-02-07 20:26:39 -05:00