List view
- Due by August 12, 2022•1/1 issues closed
- Due by April 30, 2022•3/3 issues closed
- Due by April 14, 2022•6/6 issues closed
- Due by March 29, 2022•13/13 issues closed
- Due by March 8, 2022•3/3 issues closed
- Due by February 21, 2022•4/4 issues closed
- Due by February 7, 2022•8/8 issues closed
- Due by January 24, 2022•4/4 issues closed
- Due by December 23, 2021•5/5 issues closed
Stream-chat-css release workflow: https://github.com/GetStream/stream-chat-css/issues/13
Due by December 3, 2021•5/5 issues closed- Due by November 22, 2021•5/5 issues closed
- Due by November 15, 2021•2/2 issues closed
- Due by November 8, 2021•11/11 issues closed
- Due by October 29, 2021•9/9 issues closed
- Due by October 25, 2021•9/9 issues closed
- Due by October 18, 2021•4/4 issues closed
- Due by October 11, 2021•5/5 issues closed
Progress with message list implementation. - message grouping by user - ensure the scroll behavior is consistent (spec - https://www.notion.so/stream-chat-fe-sdk/Chat-Message-List-Scrolling-Behavior-5f205217b8f3462984334bdc73b84124) - reactions - use translation keys for displaying UI texts Show and tell - the above.
Due by October 4, 2021•4/4 issues closedThe goal would be to create a functioning Message List component. For the purposes, we can use the dummy, prototype composer we have from the sample app. - basic behavior (should already be there) - scrolling to the bottom, keeping up with new messages. - the equivalent of `MessageSimple`. - the avatar - the message "bubble" - the delivery date and status - the actions UI skeleton popup (not the actual actions) - reactions (reacting, unreacting, seeing the reaction counts) - render image attachment (not the gallery) - custom message item template Write documentation for the message list and the message item customization options. Show and tell: - the sample app now uses the Message component, which looks like the one in React. - and (maybe live coding or separate example) - we can customize the message list with an item template :)
Due by September 27, 2021•5/5 issues closedWhat do we want to announce to the company in one week as progress? Angular's first sprint created a foundation for our project. - we have a sample app - we are sharing stylesheets with React - we have a repo with our setup - library code is extracted from the sample app - GH automation - no publishing to NPM just yet - What do we want to show and to who? - internal stakeholders - Team leads (React, Petyo) - PMs (FYI) - How are we going to show it? - either Loom - or a written memo with links
Due by September 20, 2021•7/7 issues closed