a87d29fce7
* remove redundant button styles and use proper button classes * remove import for contact_us css * fix view plans button to be xs * tweak to disabled state on save button in floating bar * change contact us to tertiary button like before * updated btn-full on free edition right panel * update contact button to be primary when shown in the trial card * fix issue with hover state on save changes panel error state * fix style lint issues * update snapshots * fixed a few license page buttons * fix lint issue * Update index.test.tsx.snap * add empty end lines * fixed scope of css so it doesn't affect product switcher * upate button font size for xs, update bg color for button in announce bar * fix lint error * update missed cancel buttons to use proper classes * fixed text spec to find the right button * updated snapshots * fix issue with test on cancel button * update snapshots
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.
Useful Links
- Developer setup, now included with the Mattermost server developer setup
- Web app developer documentation