jvanderbiest / directline-jabber Goto Github PK

When specifying the attachment option in Chatdown, the image gets embedded if it's a local URL. This embedded image will fail when sending to DirectLine because of a 300K character limit. We should be able to somehow host it and send it with the request.

Support for custom events to send out prior to the conversation

Instead of running it from node by specifying the app.js file, make an executable that can be run directly.

Try to have an emulator channelId that is used with the emulator too. It might have different results with bots.

Include conversationupdate and update watermark accordingly

Get some code coverage and refactor on the way.

Release as npm repository package and add a badge to the readme.md

Currently only GET is supported, for BotFramework samples default is POST.

Just use transcript files from emulator. Will also fix bug for vsts release pipeline.

Currently we only support one Chatdown file by specifying the filepath in the commandline. Let's give the option to specify multiple files.

Instead of supporting only files, let the user have the option to specify a folder that contains all the Chatdown files.

Support cards and assert based on card type.

https://docs.microsoft.com/en-us/azure/bot-service/rest-api/bot-framework-rest-connector-api-reference?view=azure-bot-service-4.0#attachment-object

The DirectLine secret in development is exposed in the VSCode launchsettings file. Would be good if we could add it in a configuration file that is excluded from github.

assert attachments

When sending out activities to the bot, we might want to replace the userid in the transcript by a fixed userId or prefix the existing userId with a value.

We don't expect users to have access to the DirectLine secret directly. As a best practice the DirectLine secret should never be exposed but instead an access token is generated by an API call and send back to the user.

It should not be required to have Chatdown conversations to start the application. Chatdown coversations get translated to transcripts anyways so we should be able to also load plain transcripts that might come from the emulator directly.

Turns out it's a problem with the Azure Devops Pipeline (jvanderbiest/directline-jabber-az-pipeline#2)

If no preprocessor file gets resolved, we'll throw an error