ESlint is configured with a basic code style, including React hooks dependency hints.
VSCode can display the ESlint errors and warnings thanks to the ESlint extension.
This extension includes a formatter to automatically reformat written code based on the code style.
DatAtlas needs a custom version of Kepler where a column can have multiple values. This is achieved by using a JSON value.
Having an array value represented as a JSON is specific to DatAtlas and may not be fitted for every projects. This is why the custom Kepler cannot be the subject of a GitHub PR, and should stay as a standalone until a consensus on what is an array value in CSV can be.
Next sections describe how to deal with this for developing and building DatAtlas.
DatAtlas Kepler custom package must be cloned next to the Front folder, in the system where the Front will be built.
Then for the Kepler side:
cd kepler.gl
yarn install
yarn run build
yarn link # may need sudo
And for the Front side:
cd ../front/src
yarn install
yarn link kepler.gl
yarn build # or yarn start
This implies pushing a different package.json than the one actually versioned and should be the result of a team decision.
Several solutions there :
"kepler.gl": "datatlas-erasme/kepler.gl",
see on NPM doc. Maybe the easiest to do but implies pushing the dist/ folder."kepler.gl": "../../kepler.gl",
see on NPM doc. Not great, every developers and build envs must have the same folder structure…