• Async actions, redux provides initial state from server
• Server app handles query params to compute initial state
• Route masking. Can be implemented, or mentee can switch to next.js for SSR
• Code splitting for optimized performance. Goes OOTB with next.js

Filtering and sorting is done as redux actions

Fully rendered application on Server side and Template render and data etching on client side

All data fetches moved to actions & received from store by components

On searchpage filter buttons work only once.

Should be tested.

Offline data storage & store restoration (coverage ~100%)

Create aliases for things like Assets or Components using:
https://webpack.js.org/configuration/resolve/

Actions and reducers covered with unit tests (~60%+, can be amended by mentor

• Testing Link components
• Testing route rendering
  --- to fix: ---
• checkPropTypes is not a function

I18n solution?

Task passing requirements:

• Markup is done with React Components
• Use ErrorBoundary component for catching and displaying errors
• Use smart/dumb components approach
• 100% decomposition ( evaluated by mentor )

Own tasks / notes:

• Use controlled input for smart request sending / validation / result suggestions

• 80% minimum coverage
• snapshot testing
• Functional testing with enzyme and jest
• write at least one e2e test

• self imposed >95% test coverage

Drop Redux in favor of own Store implementation for learning purposes.

Style components either using CSS modules or Styled Components

• Button
• Header
• Footer
• Input
• MovieSearch
• MovieGrid
• MovieGridItem

For enhancing testing environment.

Create better error handling service. Possibly extending withError component?

Implement this after core app logic is implemented to test Business requirements.

it("... executes passed click action", () => {
const mockFn = jest.fn();
const wrapper = shallow();

wrapper.simulate("click");

expect(mockFn).toHaveBeenCalled();

});

• Have 2+ pages which displays on different URLs
• Implement displaying 404 page for all invalid URL
• 404 page for all invalid URLs By default user lands on a new page with empty results state
• When user performs a search on the page, change URL and show search results
• When new user enters the site using direct link with search parameters - show search results