vaadin/crm-react

Getting Started with Create React App

This project was bootstrapped with Create React App.

Building a Docker image

1. build the app for production: yarn build

2. create a docker image: docker build -t crm-react-ui .

3. run the docker image: docker run -it --rm -p 8080:80 crm-react-ui

4. open the app in the browser http://localhost:8080.

   NOTE: In production mode the app is configured to access the backend at ./api (e.g. ./api/login). This can be changed e.g. by building the app for production with REACT_APP_BASE_API=http://localhost:8082 yarn build (in the step 1).

Available Scripts

In the project directory, you can run:

yarn start

Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.

The page will reload if you make edits.
You will also see any lint errors in the console.

yarn test

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

yarn build

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.
Your app is ready to be deployed!

See the section about deployment for more information.

yarn eject

Note: this is a one-way operation. Once you eject, you can’t go back!

If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.

You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.

Learn More

You can learn more in the Create React App documentation.

To learn React, check out the React documentation.

crm-react's Issues

Support arbitrary set of deal states

The set of deal states (their names and and whether or not they are 'active') should not be defined in the client-side. The UI should be able to handle any arbitrary set of deal states provided by the backend.

Currently the UI uses a hard-coded set of states:

crm-react/src/views/deals/DragDrop.tsx

Line 10 in 08cd128

const DealStatus = ['New', 'ProposalSent', 'ClosedWon', 'ClosedLost'];

navigation menu should be collapsed on narrow screens

The main content is hidden by the navigation menu when opening the app in a window that's less than 960px wide. At this screen size the app should start with the navigation menu closed by default.

The same should happen when navigating from page to page. On narrow screens the navigation menu should auto-close after a navigation.

Compare this version (on the left) with the Vaadin 14 version (on the right):

NOTE: this issue may be hard to fix with the current application structure:

I used a combination of 'temporary' and 'persistent' drawer of Material-UI.
In this case, it is hard to make such behavior.