Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.14.34
->1.5.4
Release Notes
Yoctol/bottender
v1.5.4
Compare Source
line
[deprecated] add deprecated warning to the following methods:
context.useAccessToken
context.replyButtonTemplate
context.push
context.pushText
context.pushImage
context.pushVideo
context.pushAudio
context.pushLocation
context.pushSticker
context.pushImagemap
context.pushFlex
context.pushTemplate
context.pushButtonTemplate
context.pushButtonsTemplate
context.pushConfirmTemplate
context.pushCarouselTemplate
context.pushImageCarouselTemplate
context.send
context.sendImage
context.sendVideo
context.sendAudio
context.sendLocation
context.sendSticker
context.sendImagemap
context.sendFlex
context.sendTemplate
context.sendButtonTemplate
context.sendButtonsTemplate
context.sendConfirmTemplate
context.sendCarouselTemplate
context.sendImageCarouselTemplate
v1.5.3
Compare Source
prompt-confirm
.v1.5.2
Compare Source
v1.5.1
Compare Source
messaging-apis
(#806):onRequest
option (#773):id
toRequestContext
(#774)connector.preprocess
(#771)messaging-apis
to v1.0.0messenger
line
getConfig
(#770):emojis
on LINE text message event (#793):LineContext.getMembersCount
method (#824):telegram
TelegramEvent.isPollAnswer
andTelegramEvent.pollAnswer
(#745):pollAnswer
to telegram routes:TelegramContext.answerCallbackQuery
(#750):slack
*
(#758):context.views.open
in slack home tab (#809)dialogflow
@google-cloud/dialogflow
v4create-bottender-app
bottender-facebook
FacebookConnector
to experiment using same connector for Messenger and Facebook.v1.4.10
Compare Source
slack.event
(#842)v1.4.9
Compare Source
useUnifiedTopology
to avoid warning (#831)v1.4.8
Compare Source
v1.4.7
Compare Source
v1.4.6
Compare Source
messenger
home_url
).v1.4.5
Compare Source
v1.4.4
Compare Source
slack
v1.4.3
Compare Source
v1.4.2
Compare Source
getClient
function (#744)v1.4.1
Compare Source
create-bottender-app
v1.4.0
Compare Source
namespace.any
for better readability (#719):messenger
Support
event.isReaction
&event.react
:Support detect events in routers:
context.sendOneTimeNotifReqTemplate
(#722):line
LineNotify
(#721):language
toUser
(messaging-apis#563)sticon
toTextMessage
(messaging-apis#564)bottender-dialogflow
create-bottender-app
lib
es2018-es2020 by default.App
action accept Action as return value (#734)v1.3.5
Compare Source
router.d.ts
into package files whitelistv1.3.4
Compare Source
bottender/router
import statement in TypeScript (#715)v1.3.3
Compare Source
line
messaging-api-line
for domain name change for certain endpoints.v1.3.2
Compare Source
line
messaging-api-line
.create-bottender-app
eslint-plugin-import
for--typescript
.dist
to.gitignore
for TypeScript (#697).v1.3.0
Compare Source
whatsapp
whatsapp
built on top of Twilio API for WhatsApp (#664):slack
line
messaging-api-line
to support narrowcast.create-bottender-app
bottender dev
(#654).cli
bottender dev --inspect=HOST:PORT
(#656).v1.2.3
Compare Source
slack
v1.2.2
Compare Source
create-bottender-app
v1.2.1
Compare Source
v1.2.0
Compare Source
[new] Added four NLU packages:
[new] Added
context.setIntent()
for intent tracking purpose (#617):context.setAsHandled()
andcontext.setAsNotHandled()
for tracking handling status (#624):getSessionStore
helper function to get the session store that configured bybottender.config.js
(#633):getClient
helper function to access underlying messaging client configured bybottender.config.js
(#634):slack
includeBotMessages
option for interacting withbot_message
(#635):Then you can use
context.event.isBotMessage
to determine if the event is a bot message event:v1.1.3
Compare Source
v1.1.2
Compare Source
super.prepare()
inprepare
method to avoid overwriting parent methodv1.1.1
Compare Source
v1.1.0
Compare Source
Instead of:
messenger
line
slack
e.g.
context.postMessage
andcontext.postEphemeral
is now deprecated, usecontext.chat.postMessage
andcontext.chat.postEphemeral
instead.e.g.
For views, we keep
channelId
inprivateMetadata
to get session key for upcoming view events. (ref)telegram
viber
v1.0.8
Compare Source
v1.0.7
Compare Source
super.prepare()
inprepare
method to avoid overwriting parent methodv1.0.6
Compare Source
v1.0.5
Compare Source
v1.0.4
Compare Source
v1.0.3
Compare Source
v1.0.2
Compare Source
prepare
support for production mode.v1.0.1
Compare Source
messenger
fields
support tocontext.getUserProfile()
:bottender.config.js
inmessenger-typing
exampleline
shouldBatch
tofalse
afterhandlerDidEnd
has been called. This may be the best way to handle errors in LINE:telegram
context.editMessageMedia()
:v1.0.0
Compare Source
create-bottender-app
. You can use following command to create your new bot:bottender start
cli. It findsindex.js
entry andbottender.config.js
config file then executes accordingly:To enable console mode:
bottender dev
cli:The bot server will be restarted after changing the files.
Action:
Pass Props to Action:
Router:
Chain:
_error.js
entry support for error handling:middleware
and Handlers has been moved to@bottender/handlers
package. You can install it from registry:And import them like this:
Messenger -
Slack -
Telegram -
Viber -
[breaking] rename
skipProfile
toskipLegacyProfile
, and set to true by default[breaking] unify requestContext (#541)
[deps] update
messaging-apis
to v1[examples] Rewrite all examples for Bottender v1
[docs] A brand-new website with new docs - https://bottender.js.org?new
messenger
pageId
config to automatically add subscribe app inbottender messenger webhook set
.get-started
,greeting
,persistent-menu
,whitelisted-domains
cli subcommands has been removed. Useprofile
instead:bottender messenger profile get bottender messenger profile set bottender messenger profile delete
context.sendAirlineFlightUpdateTemplate()
.line
context.getMessageContent()
. You can use it to get received media content:sendMethod
toreply
andshouldBatch
totrue
by default.menu
cli subcommand has been removed.slack
token
in payload when received a JSON string payload.telegram
context.sendAnimation()
:context.sendPoll()
v0.15.18
Compare Source
line
messaging-api-line
to 0.7.18 to support LINE domain changes.v0.15.17
Compare Source
line
v0.15.16
Compare Source
v0.15.15
Compare Source
messenger
page.id
to Messenger sessions:line
skipProfile
toLinekBot
andLinekConnector
.destination
toLineEvent
.slack
skipProfile
toSlackBot
andSlackConnector
.telegram
-w
for--webhook
.v0.15.14
Compare Source
messenger
v0.15.13
Compare Source
context.usePersona
:v0.15.12
Compare Source
messenger
skipProfile
option toMessengerBot
andMessengerConnector
to skip auto updating user profile:v0.15.11
Compare Source
messenger
skipAppSecretProof
option toMessengerBot
andMessengerConnector
:v0.15.10
Compare Source
origin
option for testing purpose:messenger
v0.15.9
Compare Source
messenger
List all personas:
Create a new persona with name and profile picture url:
Get persona by persona ID:
Delete persona by persona ID:
v0.15.8
Compare Source
sessionStore.all()
to fetch all of sessions from the store:messaging-apis
(which support messenger persona api)v0.15.7
Compare Source
messaging-apis
, so now we can useDEBUG
env variable to enable request debugger:ConsoleBot
recognize symbol as_methodMissing
(#333)v0.15.6
Compare Source
line
telegram
isReplyToMessage
,replyToMessage
(#330):v0.15.5
Compare Source
slack
v0.15.4
Compare Source
print:
Useful when debugging synchronized connectors.
console
context.platform
consistent withcontext.session.platform
v0.15.3
Compare Source
console
mockPlatform
option:v0.15.2
Compare Source
messenger
context.isThreadOwner()
:v0.15.1
Compare Source
line
v0.15.0
Compare Source
v0.15
is the second major version after we open sourced Bottender. In this version, we introduce a lot of helpful, community requested features based on Messaging APIs v0.7.context.requestContext
:Express, Micro, Restify:
Koa:
DEBUG
env:DEBUG=bottender:* DEBUG=bottender:request DEBUG=bottender:session:read DEBUG=bottender:session:write
MemoryCacheStore
(#235)messenger
MessengerContext
method -sendQuickReplies
appsecret_proof
by default.context.getThreadOwner
pageId
,gamePlay
,brandedCamera
,isRequestThreadControlFromPageInbox
getters toMessengerEvent
It will enable message batching functionality via messaging-api-messenger under the hood.
sendAirlineFlightUpdateTemplate
has been renamed tosendAirlineUpdateTemplate
.line
replyFlex
,pushFlex
,sendFlex
:issueLinkToken
toLineContext
(#245):linkAccount
events support (#243):shouldBatch
option:When batching is enabled,
Those 5 messages will be sent in one API call, just like the below one.
sendMethod
option:telegram
ok
isfalse
in Telegram:custom connector
It's useful in custom connectors.
Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.