81ef403230
* update import/export for attachments and new file paths * add unit test * update templates test * temp checking * cleanup * cleanup * more cleanup * lint fixes * cleanup some functions * cleanup * fix build breaks * fix tests for changes * move function to different file * more cleanup, code movement * unit test fixes * add unit tests * fix tests * more unit test fixes * test fix * revert package-lock.json * fixes from code review * fix export image * more fixes to remove attachmentId * change from removed api * update test * lint fixes * update for review comments * fix tests * test fix * lint fix * remove sprintf from logging, use mlog * more lint fixes * Update server/boards/app/files.go Co-authored-by: Doug Lauder <wiggin77@warpmail.net> * remove code --------- Co-authored-by: Mattermost Build <build@mattermost.com> Co-authored-by: Doug Lauder <wiggin77@warpmail.net>
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 boards) 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=boards
# Build multiple packages
npm run build --workspace=packages/client --workspace=packages/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.
Useful Links
- Developer setup, now included with the Mattermost server developer setup
- Web app developer documentation