Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(map): resolve marker latency, issue 360 #416

Merged
merged 1 commit into from
Apr 25, 2022
Merged

fix(map): resolve marker latency, issue 360 #416

merged 1 commit into from
Apr 25, 2022

Conversation

maximenathan
Copy link
Contributor

Resolve issue #360

Replace MUI Box component to div

@maximenathan maximenathan added the Type: Bug Something isn't working as expected label Apr 24, 2022
@maximenathan maximenathan linked an issue Apr 24, 2022 that may be closed by this pull request
@@ -65,10 +65,10 @@ const Property = ({
{loading ? (
<Skeleton variant="text" width="100%" />
) : (
<Box display="flex" flexDirection="column">
<div style={{ display: 'flex', flexDirection: 'column' }}>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

On pourrait rajouter un commentaire pour expliquer pourquoi on passe un div peut-être ? J'imagine que la Box répétée des milliers de fois étaient trop lourde.

J'imagine que la modif venait de moi, je prends note du problème de performance que ça peut induire, désolé.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Il doit y avoir un bug avec le composant "Box" car normalement cela ne devrait pas provoquer de ralentissement... Oui, mettre un commentaire pour expliquer la raison du div ici serait bien :)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

J'ai trouvé ce commentaire à propos des performances de Box : mui/material-ui#21657 (comment)

A partir de la v5 de MUI (on est toujours en v4 sur Grottocenter), ils l'ont optimisé et elle s'affiche 5 fois plus vite.

@bsoufflet
Copy link
Contributor

@Clm-Roig : Je viens d'ajouter le comment. J'ai créé ce ticket aussi : #417

@github-actions
Copy link

Azure Static Web Apps: Your stage site is ready! Visit it here: https://orange-rock-0d4f87503-416.westeurope.azurestaticapps.net

@maximenathan
Copy link
Contributor Author

J'ai supprimé sans faire expres le commit de @bsoufflet
Il y avait une petite erreur sur la prop preferCanvas

@Clm-Roig

@GrottoCenter GrottoCenter deleted a comment from github-actions bot Apr 25, 2022
@GrottoCenter GrottoCenter deleted a comment from github-actions bot Apr 25, 2022
@github-actions
Copy link

Azure Static Web Apps: Your stage site is ready! Visit it here: https://orange-rock-0d4f87503-416.westeurope.azurestaticapps.net

fix #360
- add a comment on map issue
- update default map location of map
- add preferCanvas prop
- prevent zooming too much out (for better performance)
@github-actions
Copy link

Azure Static Web Apps: Your stage site is ready! Visit it here: https://orange-rock-0d4f87503-416.westeurope.azurestaticapps.net

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Something isn't working as expected
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[MAP] Performance issue
3 participants