Files
mostlymatter/webapp
Harrison Healey d25326764f MM-62710 Ensure CommentedOn message is never missing due to unloaded data (#30572)
* MM-62710 Ensure CommentedOn message is never missing due to unloaded data

There's more information in the Jira ticket on how this occurs, but the
short version is that there's a way for either the root post and/or the
root post's author to be missing which previously caused the "Commented
On" line not to be rendered for a comment with CRT disabled. That caused
the post to appear as if it was part of the wrong thread.

Now, the CommentedOn component is always mounted when for the first
non-consecutive reply to a thread, and it knows how to load that missing
data itself.

I also took the opportunity to implement basic `useUser` and `usePost`
hooks which will fetch the user/post if needed. They're both implemented
using a shared `makeUseEntity` which should be usable for other entities
(objects stored in Redux state and fetched using a Redux action). These
also both use actions that use `DelayedDataLoader` to batch and debounce
requests for that data as well!

Assuming this works well, I'm hoping we can start using this pattern
elsewhere in the app.

* Update tests and remove unneeded mapStateToProps

* Address feedback

* Fix playwright tests

* revert Fix playwright tests

---------

Co-authored-by: yasserfaraazkhan <attitude3cena.yf@gmail.com>
2025-04-02 11:45:00 -04:00
..
2023-03-22 17:22:27 -04:00

Mattermost Web App

This folder contains the client code for the Mattermost web app. It's broken up into multiple packages each of which either contains an area of the app (such as playbooks) or shared logic used across other packages (such as the packages located in the platform directory). For anyone who's used to working in the mattermost/mattermost-webapp repo, most of that is now located in channels.

npm Workspaces

To interact with a workspace using npm, such as to add a dependency or run a script, use the --workspace (or --workspaces) flag. This can be done when using built-in npm commands such as npm add or when running scripts. Those commands should be run from this directory.

# Add a dependency to a single package
npm add react --workspace=playbooks

# Build multiple packages
npm run build --workspace=platform/client --workspace=platform/components

# Test all workspaces
npm test --workspaces

# Clean all workspaces that have a clean script defined
npm run clean --workspaces --if-present

To install dependencies for a workspace, simply run npm install from this folder as you would do normally. Most packages' dependencies will be included in the root node_modules, and all packages' dependencies will appear in the package-lock.json. A node_modules will only be created inside a package if one of its dependencies conflicts with that of another package.