Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add RFC for Notification Categories #72

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Add RFC for Notification Categories #72

wants to merge 1 commit into from

Conversation

ghost
Copy link

@ghost ghost commented Jul 11, 2017

10,000 foot view

Provide a useful mechanism for assigning notifications to taxonomies so they may be actioned upon differently under varying operating contexts.

Turning something like:

warning eslint > jshint > minimatch@0.4.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue

Into something like:

warn [infosec] vulnerability detected in minimatch ...

Impetus

We all yearn to reduce cognitive overhead during development. One such way of helping achieve that is to open a method by which packages may group like notifications into categories which may then be actioned upon in some way by the end-user via an API, be it CLI or configuration-based.

In turn taxonomies like [infosec] or [optim] enable parsable messages in buffered output for enhanced logging while adding value to end-users, if displayed.

Following a push notification model openens the ability to use OS-integrated notifiers to send important notifications to users via in-built tooling instead of only messaging on the CLI.

Please see files changed for the full RFC. View prettified.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants