Create basic app structure. Add deploy-dev pipeline

[AmsterGet]

TODO (will be a part of another PR):

• Add SCSS
• Add aliases for main dirs
• Create common page Layout component

[AmsterGet]

@Nikkov17 @skyRoma
Please check out the latest built version - https://aikray.github.io/menu-bot-front/
Don't forget to view on mobile screens :)

[Nikkov17]

we can combine html, root, body common styles

[Nikkov17]

is it needed?

[AmsterGet]

Actually no, until we will paste some page specific props to Footer.

[skyRoma]

So let's remove the dead code for now?

[skyRoma]

Please, change all file names to snake-case

[skyRoma]

As we agreed before or let's agree this CapitalCamelCase approach just for component file names. Both cases work for me, but they should be consistent across the whole project.

[skyRoma]

really minor, but could you please make the step names consistent with the 1st action

[skyRoma]

Is it really needed now? Since I don't remember that we used it on the previous project. Maybe the issue is in the token permissions or the token type? I think I used the classic token type

[skyRoma]

Width is 100% by default, sicne it's a <div>, so please remove this prop

[skyRoma]

it everytime will be null for the first visit, so use :string | null and remove as string below.
Or use localStorage.getItem(LOCAL_STORAGE_SAVED_CITY_KEY) || ''

[skyRoma]

Please, use classes for styles

[skyRoma]

As I can see it is even 100% by default

[skyRoma]

Should this also be an optional property? I suppose you wanted to make this component reusable even without list, just with input? But in general, I would suggest using composition in such cases (to have 2 separate components, search and list). But as for now we don't need just search (without list) let's make all properties required

[skyRoma]

And please group them together (first fields then methods). And for the future lets place the optional ones below the required ones

[skyRoma]

I suppose we won't have a city in the App if we don't have any restaurant for this city so you can remove || []

[skyRoma]

Sorry, but I didn't get why do we need this additional provider? why not just use only one StoreProvider? For me it looks unnecessary completed

like this for example

import { LOCAL_STORAGE_SAVED_CITY_KEY } from 'providers/store-provider/constants';
import { ReactElement, useCallback, useState } from 'react';

import {
  IStoreContext,
  StoreContext,
  StoreDispatchContext,
} from './storeContext';

interface IStoreProviderProps {
  children: ReactElement;
}

const extractCity = (): string =>
  localStorage.getItem(LOCAL_STORAGE_SAVED_CITY_KEY) || '';

const saveCityLocally = ({ selectedCity }: Partial<IStoreContext>) => {
  localStorage.setItem(LOCAL_STORAGE_SAVED_CITY_KEY, String(selectedCity));
};

const initialStore = {
  selectedCity: extractCity(),
};

export const StoreProvider = ({ children }: IStoreProviderProps) => {
  const [store, setStore] = useState(initialStore);

  const updateStoreProperties = useCallback(
    (storeProperties: Partial<IStoreContext>) => {
      setStore(prevStore => ({
        ...prevStore,
        ...storeProperties,
      }));
      saveCityLocally(storeProperties);
    },
    []
  );

  return (
    <StoreContext.Provider value={store}>
      <StoreDispatchContext.Provider value={updateStoreProperties}>
        {children}
      </StoreDispatchContext.Provider>
    </StoreContext.Provider>
  );
};

[skyRoma]

This is not used outside, please remove export.
The same for defaultStore below