Issue #62: Chat message send icon was not refreshed #7847
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…, remove hack which existed for node 0.10.xx
…ting' into assistify-knowledge-connector
…solved in helpers
Assistify knowledge connector
…cy to canotto:swalforms
Assistify help request
No migration on DB implemented, has to be done manually
* some deletion of obsolete code
…k-results-refactoring
Redlink results refactoring
Not beautified yet and not yet visible in the lefthandside navbar.
Some minor beautification
* Allow lowercase topic names * Error handling Smarti not available : Do not create `undefined` script tags * Help-request actions button shall disappear once the help-request has been closed (#38) * Make requests for expertises respect case as well (#36) * Remove subscription of owner who created a request on closing a help request (fixes #38) * #47 - Closing a help request does not store the conversation correctly - Added some debugging output - Some formatting * Do not lowercase experts channel * Satisfy linter and remove console dependency
Fixes a small / not related lint Issue
Search config
add configuration parameter for Assistify Widgets posting behaviour
Conflicts: Expertise and request room types to be considered in files which have been converted from .coffee to .js: - packages/rocketchat-ui/client/views/app/room.js - packages/rocketchat-ui-admin/client/rooms/adminRooms.js package.js merged
Conflicts: Expertise and request room types to be considered in files which have been converted from .coffee to .js: - packages/rocketchat-ui/client/views/app/room.js - packages/rocketchat-ui-admin/client/rooms/adminRooms.js package.js merged
…x` has done to the file previously... Note to myself: report error in `stylelint --fix`
…idation #77 smarti widget invalidation
The actual correction would be to provide a real authorization object, but that lead to exceptions which could not be corrected so far. Thus, this commit provides a short-term-low-risk-workaround.
|
github@beimir.net, Oliver Jägle seem not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
|
Pls Ignore this pull request |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.