Merge pull request #1528 from GetStream/develop

v8.1.1

Author: arnautov-anton

.env.example

@@ -6,3 +6,4 @@ E2E_TEST_USER_2='test-user-2'
 E2E_TEST_USER_2_TOKEN='test-user-2-jwt'
 E2E_JUMP_TO_MESSAGE_CHANNEL='jump-to-message'
 E2E_ADD_MESSAGE_CHANNEL='add-message'
+E2E_ADDITIONAL_CHANNELS="mr-channel-1,mr-channel-2"

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,50 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: 'bug:'
+labels: bug
+assignees: ''
+
+---
+
+**Describe the bug**
+
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+
+If applicable, add screenshots to help explain your problem.
+
+**Package version**
+- stream-chat-react:
+- stream-chat-css:
+- stream-chat-js:
+
+**Desktop (please complete the following information):**
+
+- OS: [e.g. iOS]
+- Browser [e.g. chrome, safari]
+- Version [e.g. 22]
+
+**Smartphone (please complete the following information):**
+
+- Device: [e.g. iPhone6]
+- OS: [e.g. iOS8.1]
+- Browser [e.g. stock browser, safari]
+- Version [e.g. 22]
+
+**Additional context**
+
+Add any other context about the problem here.

.github/auto-merge.yml

@@ -0,0 +1,8 @@
+minApprovals:
+  NONE: 0
+requiredLabels:
+  - stream-dependencies
+updateBranch: true
+mergeMethod: rebase
+deleteBranchAfterMerge: true
+requiredTitleRegex: stream-chat-css

.github/dependabot.yml

@@ -0,0 +1,11 @@
+version: 2
+updates:
+  - package-ecosystem: 'npm'
+    directory: '/'
+    schedule:
+      interval: 'daily'
+    allow:
+      - dependency-name: '@stream-io/stream-chat-css'
+      - dependency-name: 'stream-chat'
+    labels:
+      - stream-dependencies

.github/workflows/ci.yml

@@ -25,16 +25,16 @@ jobs:
     runs-on: ubuntu-latest
     name: End-to-end tests
     steps:
-      - uses: actions/checkout@v2
+      - uses: actions/checkout@v3
 
       - name: 💾 Cache Dependencies
-        uses: actions/cache@v2
+        uses: actions/cache@v3
         with:
           path: ./node_modules
           key: ${{ runner.os }}-${{ matrix.node }}-modules-${{ hashFiles('**/yarn.lock') }}
 
       - name: 🔨 Install Dependencies & Build
-        run: yarn install --frozen-lockfile --ignore-engines
+        run: yarn install --frozen-lockfile --ignore-engines --ignore-scripts
 
       - name: ⚗️ End-to-end tests
         run: |
@@ -54,6 +54,7 @@ jobs:
           E2E_APP_SECRET: ${{ secrets.E2E_APP_SECRET }}
           E2E_TEST_USER_1_TOKEN: ${{ secrets.E2E_TEST_USER_1_TOKEN }}
           E2E_TEST_USER_2_TOKEN: ${{ secrets.E2E_TEST_USER_2_TOKEN }}
+          E2E_ADDITIONAL_CHANNELS: mr-channel-1, mr-channel-2
 
   test:
     runs-on: ubuntu-latest

.releaserc.json

@@ -8,7 +8,12 @@
         "changelogFile": "./CHANGELOG.md"
       }
     ],
-    "@semantic-release/github",
+    [
+      "@semantic-release/github",
+      {
+        "assets": ["./CHANGELOG.md"]
+      }
+    ],
     "@semantic-release/npm"
   ]
 }

CHANGELOG.md

@@ -1,5 +1,29 @@
 # Changelog
 
+## [8.1.0](https://github.com/GetStream/stream-chat-react/compare/v8.0.0...v8.1.0) (2022-04-08)
+
+
+### Bug Fixes
+
+* adjust links to stories used by add-message e2e tests ([c6dc53a](https://github.com/GetStream/stream-chat-react/commit/c6dc53ae18c0b03905a1f05452bcec6a610a6ca5))
+* autocomplete items clicking works on webkit ([#1494](https://github.com/GetStream/stream-chat-react/issues/1494)) ([4f73f14](https://github.com/GetStream/stream-chat-react/commit/4f73f145b877419a4d745c96f8b0096ac5a52ac3))
+* correct german calendar translation strings ([#1468](https://github.com/GetStream/stream-chat-react/issues/1468)) ([2471d4b](https://github.com/GetStream/stream-chat-react/commit/2471d4bcd227c7c7991d5791bd304409605349ac)), closes [#1467](https://github.com/GetStream/stream-chat-react/issues/1467)
+* fixed connection handling, updated configuration ([0face10](https://github.com/GetStream/stream-chat-react/commit/0face104ba81c3ca6495e63132af003a90228cc9))
+* improve portuguese translations ([5e67a86](https://github.com/GetStream/stream-chat-react/commit/5e67a865a8211956c3a86980cc2896f4e3f059ff))
+* improved German translations ([c4d71b6](https://github.com/GetStream/stream-chat-react/commit/c4d71b6f5b2e07ace0ee7644664ebabff2526138))
+* improved German translations ([a6fe4fb](https://github.com/GetStream/stream-chat-react/commit/a6fe4fbed906c102728bb18f97fee21f978f322a))
+* Slow mode role check and limitations ([a447ed5](https://github.com/GetStream/stream-chat-react/commit/a447ed5b2945e7f669d414ed820c2585bbdd04e9))
+* Update channel preview on connection recovery ([92f81d9](https://github.com/GetStream/stream-chat-react/commit/92f81d9831e6c84501550ee259939d872a2c66a5))
+* Update quoted message preview on message update ([#1503](https://github.com/GetStream/stream-chat-react/issues/1503)) ([f9a0081](https://github.com/GetStream/stream-chat-react/commit/f9a0081af3576f187883f649cf0a1f807b47ee44))
+* update unread counts for each ChannelPreview on WS connection recovery ([b267a65](https://github.com/GetStream/stream-chat-react/commit/b267a65c31ac97ee60d3a2681b26cfc610501a38))
+* Upload preview overflow in thread ([#1495](https://github.com/GetStream/stream-chat-react/issues/1495)) ([518d622](https://github.com/GetStream/stream-chat-react/commit/518d622f8b716a6c622a65816eae16f50e9545e5))
+
+
+### Features
+
+* support jump to message ([#1478](https://github.com/GetStream/stream-chat-react/issues/1478)) ([e297ffe](https://github.com/GetStream/stream-chat-react/commit/e297ffed906bd24ba68698cf704f9d08610d1314))
+
+
 ## [8.0.0](https://github.com/GetStream/stream-chat-react/releases/tag/v7.0.0) 2022-03-17
 
 ### Bug Fixes

CONTRIBUTING.md

@@ -0,0 +1,78 @@
+# Contributing to stream-chat-react
+
+As a contributor, here are the guidelines we would like you to follow:
+
+- [Asking questions](#asking-questions)
+- [Filing an issue](#filing-an-issue)
+- [Contribution Standards](#coding-standards)
+- [Submission Guidelines](#submission-guidelines)
+- [Signing the CLA](#contributor-licence-agreement)
+
+
+## <a name="asking-questions"></a>Are you looking for answers?
+There are many ways you can get your questions answered. It can be hard to decide, where to begin if you are just starting out. We suggest you take a look at the resources in the following order:
+
+### 1. Stream chat API documentation
+Package `stream-chat-react`  has a peer dependency [stream-chat-js](https://github.com/GetStream/stream-chat-js) - a client library for interacting with the Stream Chat API (see the [API docs](https://getstream.io/chat/docs/javascript/?language=javascript)).
+
+### 2. Documentation for stream-chat-react
+The [stream-chat-react](https://getstream.io/chat/docs/sdk/react/) documentation is held separately from the Stream Chat API docs. Besides documenting the component API, it provides examples of their use in various scenarios.
+
+### 3. Read the source code
+When you plan on contributing to the repository try to get acquainted with the existing code base. The best way to learn :)
+
+### 4. Take a look at our tutorials
+
+
+### Get help from our Customer Success team
+If what you are looking for is technical support embedding Stream in your application, we suggest emailing our Customer Success team at [email protected] with your application key and the SDK versions you're using. The Issue section of this GitHub repo is now reserved only for bug reports, feature improvements and suggestions.
+
+
+## <a name="filing-an-issue"></a>Filing an issue
+Spotting imperfections and not keeping them to yourself is the first step to make this library better. We are very grateful for reports concerning imperfections in the source code or the [documentation]((https://getstream.io/chat/docs/sdk/react/)). Before filing an issue, please, review the list of [open issues](https://github.com/GetStream/stream-chat-react/issues) first.
+
+### Reporting bugs
+You can report a source code bug by using the [Bug Report template](https://github.com/GetStream/stream-chat-react/issues/new/choose). Make sure you include "steps to reproduce" section. Bug that cannot be reproduced cannot be solved.
+
+Do not be afraid to report imperfections in our [documentation]((https://getstream.io/chat/docs/sdk/react/)) as well. In such case, please attach the `docs` tag to the issue.
+
+
+### Requesting a feature
+You can request a feature by submitting a [Feature request issue](https://github.com/GetStream/stream-chat-react/issues/new?assignees=&labels=feature&template=feature_request.md&title=) in our repository. If you would like to implement the proposal, please state it in the issue. It will allow us to discuss the proposal and better coordinate the efforts. You can even ping us - mention `@GetStream/stream-react-developers ` in the issue.
+
+## <a name="contribution-standards"></a> Contributing to the repo
+
+### Set up for success
+It is always good to get acquainted with the specifics of the package. For example the `stream-chat-react` package has its peer dependencies (`stream-chat-js`, `stream-chat-css`), which you may need to tweak at the same time, while developing the feature for `stream-chat-react`. To get more into those specifics, please read [development guide](./developers/DEVELOPMENT.md).
+
+### Good first issue
+
+###<a name="#coding-rules"></a> Coding rules
+Any contributions to the library should follow Stream's coding rules.
+
+#### 1. Code should be tested
+All the code submitted should be covered by unit tests. Mocking utilities are provided in `src/mock-builders`. Optimally a suite of E2E tests should be included as well.
+
+#### 2. API Changes should be documented
+Changes to components interface exposed to the library integrators should be documented. We keep the documentation `docusaurus/docs/React` folder.
+
+#### 3. Code should be DRY & correctly formatted
+If you find yourself copying source code from one place to another, please extract it into a separate component or function.
+
+#### 4. Keep an eye on performance
+Keep in mind that the chat application may need to work with thousands of messages.
+
+#### 5. Follow commit formatting rules
+We follow [Angular's Commit Message Format rules](https://github.com/angular/angular/blob/master/CONTRIBUTING.md#-commit-message-format) with [possible deviations](./developers/COMMIT.md). The same rules are used by our release automation tool. Therefore, every commit message should strictly comply with these rules.
+
+
+## <a name="submission-guidelines"></a> Submitting your work
+1. Make sure you have signed our Contributor License agreement
+2. [Fork](https://docs.github.com/en/github/getting-started-with-github/fork-a-repo) the repo and create a dedicated git branch locally
+3. Follow the [coding rules](#coding-rules)
+4. Create a descriptive PR ([see more on PR requirements](./developers/PR_REVIEW.md))
+
+
+## <a name="contributor-licence-agreement"></a> Contributor License Agreement
+Before we can merge your contribution into our repository, we would like to ask you to sign the [Contributor License Agreement](https://docs.google.com/forms/d/e/1FAIpQLScFKsKkAJI7mhCr7K9rEIOpqIDThrWxuvxnwUq2XkHyG154vQ/viewform).
+

commitlint.config.js

@@ -0,0 +1,3 @@
+module.exports = {
+  extends: ['@commitlint/config-conventional']
+};

developers/BRANCHES.md

@@ -0,0 +1,20 @@
+# Branches
+We have 2 protected (base) branches:
+
+- `develop`
+- `master`
+
+If you want to implement a solution, you are required to create branches from `develop` or its derivatives.
+
+The `develop` branch serves as a reservoir of bug fixes and new features waiting to be released.
+
+The `master` branch serves for release and should receive updates only from the `develop` branch.
+
+So the branch architecture in this repository is as follows:
+
+```shell
+NPM <--- master <--- develop <--- branch_solution_x
+                             <--- branch_solution_y
+                             <--- branch_solution_x
+                             ...
+```