Unless someone goes out of their way to categorize their Features, this date_migrate_example Feature often ends up listed with client-specific code in the Features UI. I think it would be ok to move it into "Migrate Examples" since that appears to be its purpose. Thanks!

CommentFileSizeAuthor
#1 1719290-1-migratepackage.patch611 bytesrupl

Comments

rupl’s picture

rupl
he/him
Primary language English
commented
Status: Active » Needs review
StatusFileSize
new 1719290-1-migratepackage.patch611 bytes

Here's the patch.

rupl’s picture

rupl
he/him
Primary language English
commented

Can I offer a review on another issue in exchange for this cosmetic patch being committed?

rupl’s picture

rupl
he/him
Primary language English
commented
Component: Code » User interface

So sad that I can't even offer a review to get this committed :(

Doesn't anyone want to avoid seeing this random unrelated Feature listed with all their other client-specific code? End users are confused by it. I have confirmed that already with multiple clients.

simon georges’s picture

simon georges commented
Status: Needs review » Reviewed & tested by the community

I'm totally in favor of that too, either "Migrate examples" or "Example modules" (same as Variable or Examples modules).

Patch applies cleanly.

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented
Status: Reviewed & tested by the community » Needs work

It would be all by itself in "Migrate Examples" (for what it's worth, migrate_example itself is in the Migration group). "Date/Time", of course, is a reasonable option to keep it with the other date modules, but I think Simon's got the best idea - "Example modules", which has some traction.