Conversation
|
Will merge this with tests and docs! Docs are just the README. |
2596b67 to
bd73708
Compare
|
@triskweline Okay, finally got around to finishing this up! Ready for review. |
|
@botandrose Somehow I could not checkout your branch. Changes look good to me, thanks. I committed them myself in #28 to run CI and prepare the merge. That's a nice solution with the alias. In one of my projects I did this to achieve it: my_filter = lambda { |scope, string| ... }
filter :owner, &my_filter
filter :owner_id, &my_filter
filter :owned_by, &my_filterBut your solution is smarter than that. |
|
Released as 1.0.1 |
|
...and https://bardtracker.com is back on mainline minidusen! Thanks very much. |
|
You're welcome! |
TIL about BARD Tracker :) A year ago we migrated about a 100 Pivotal Tracker projects to Linear. |
|
@triskweline ha, yeah we did the exact same thing, and we missed Pivotal so much that we just decided to build our own clone. Opening it up to the public was a later decision. If you're feeling nostalgic, we support Pivotal .zip imports, and we're free for single users! $5/mo/collaborator after that. In any event, it was really nice not to have to implement search from scratch, so big thank you there 🙏 |
Hi folks, we've been using minidusen in production at https://bardtracker.com for a while now, and so far its been a great fit for our search functionality. I'm opening this PR to inquire if there's an appetite to upstream the following filter alias functionality that we use extensively:
This is equivalent to duplicating the block three times, once for each field.
What do you think? If you're open to merging something like this, I'll make another pass to add tests and documentation. If not, cheers, and we'll just keep it as a monkey-patch.