Plugin Support
-
Add support for Plugins to define and enable new Mod Queues! 🥇 The newly created mod queue can filter by tags, statuses, or comments containing a certain action (e.g. flagged, liked)
modQueues: { newQueueKey: { // Name name: 'My Queue Name', // Material Design icon icon: 'star', // Filter by tags tags: ['MY_TAG'], // Filter by statuses statuses: ['NONE', 'PREMOD', 'ACCEPTED', 'REJECTED'], // Filter by comment containing action_type action_type: 'FLAG', }, },
Example: Add a Featured Queue to the talk-plugin-featured-comments; simply add this to the plugin's index.js:
modQueues: {
featured: {
tags: ['FEATURED'],
icon: 'star',
name: 'Featured',
},
},- Allow passing of config to plugins (#839)
Features
- View More user history
- Auto updating and pagination to My Profile
- Emit events for
ui.AllCommentsPane.viewNewComments&ui.Comment.showMoreRepliesfor 3rd party event tracking
JWT/Cookie Support (ref: #831, #845)
-
Added more docs around JWT's
-
Fixes some bugs with the secrets loading
-
Created new configuration parameters:
TALK_JWT_DISABLE_AUDIENCE(optional) - whenTRUE, Talk will not verify or sign JWT's
with an audience (aud) claim, even if theTALK_JWT_AUDIENCEconfig is set. (DefaultFALSE)TALK_JWT_DISABLE_ISSUER(optional) - whenTRUE, Talk will not verify or sign JWT's
with an issuer (iss) claim, even if theTALK_JWT_ISSUERconfig is set. (DefaultFALSE)TALK_JWT_USER_ID_CLAIM(optional) - specify the claim using dot notation for where the
user id should be stored/read to/from. Exampleuser.idwould store it like:{user: {id}}
on the claims object. (Defaultsub)
-
Adds support for changing the cookie's name for any cookie we set related to the auth state by introducing the following new configuration parameters:
TALK_JWT_SIGNING_COOKIE_NAME(optional) - the default cookie name that is use to set a cookie containing a JWT that was issued by Talk. (Default process.env.TALK_JWT_COOKIE_NAME)
-TALK_JWT_COOKIE_NAMES(optional) - the different cookie names to check for a JWT token in, seperated by ,. By default, we always use theprocess.env.TALK_JWT_COOKIE_NAMEandprocess.env.TALK_JWT_SIGNING_COOKIE_NAMEfor this value. Any additional cookie names specified here will be appended to the list of cookie names to inspect.
-
When a request comes in, it will be verified against the following order:
- Custom cookies named from the list in
TALK_JWT_COOKIE_NAMES. - Default cookies named
TALK_JWT_COOKIE_NAMEthenTALK_JWT_SIGNING_COOKIE_NAME. - Query parameter
?access_token={TOKEN}. - Header:
Authorization: Bearer {TOKEN}.
- Custom cookies named from the list in
CLI
- Added Domain Whitelisting support to CLI setup
Styles
talk-stream-auth-sign-in-buttonandtalk-stream-comment-chevron- Admin style updates