I also recommend reading through the tests in the GitHub repo because that documents the behavior of the module.
The demo code will also grab a stack of recent bugs and generate statuses for them. -- Emma On Tue, May 24, 2016 at 9:47 AM, Gijs Kruitbosch <gijskruitbo...@gmail.com> wrote: > On 24/05/2016 16:54, Ted Mielczarek wrote: > >> On Tue, May 24, 2016, at 11:45 AM, Emma Humphries wrote: >> >>> Last week the bugzilla.mozilla.org team had a work week in the San >>> Francisco office. They were finishing the work on the modal edit view in >>> Bugzilla, and joined them to land another new feature: Readable Statuses. >>> >>> Bugs in bugzilla.mozilla.org have a lot of metadata, and it's often not >>> immediately obvious what the state of a bug is. To help with that, I've >>> written an *opinionated* package for npm that looks at the bug's metadata >>> and returns a readable status message. >>> >> >> Hi Emma, >> >> This sounds interesting! I looked at the npm page and the github repo, >> but I didn't see any example output. I'm interested to know what the >> readable statuses look like. Do you have a pointer to examples? >> >> Thanks, >> -Ted >> > > You can see this in bmo if you have the new/modal/experimental UI enabled > ( > https://bugzillatips.wordpress.com/2015/08/07/new-modal-ui-for-show_bug-on-bmo/ > ) . Here's an example: > > "Status (ASSIGNED regression bug found in Firefox 47 with no priority > awaiting an answer on a request for information)" > > ~ Gijs > > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
