-
Notifications
You must be signed in to change notification settings - Fork 26
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
feat(geo): adding initial button component files #957
Conversation
Il manque les traductions associées au bouton dans les fichiers en.geo.json et fr.geo.json. Je me demande si on devrait pas le renommer... Initial-button me dit pas grand chose. |
Ma première idée était initial-extent. ça pourrait être map-extent |
Mais étant donné que de le bouton peut servir autant à un extent qu'à un centre avec niveau de zoom, seulement extent n'est peut-être pas adéquat ? Au final, il sert vraiment à bouger ou à recentrer ta carte active à un endroit prédéfinie. |
recenter-map ? |
packages/geo/src/lib/map/initial-button/initial-button.component.html
Outdated
Show resolved
Hide resolved
packages/geo/src/lib/map/initial-button/initial-button.component.ts
Outdated
Show resolved
Hide resolved
@PhilippeLafreniere18 @mneige Any reviews? |
C'était bon pour moi ! Il manquait seulement la doc (assemblage) |
* adding initial button component files * correcting initialbutton * corrections to initial button * correction to initial button * Button name changed to home-extent-button * adding package.json as required * minors fix * fix package * refactor(home-extent-button): update with config * fix event parameter * feat(home-extent): allow to provide homeExtent properties from context Co-authored-by: Philippe Lafreniere <philippe.lafreniere@msp.gouv.qc.ca> Co-authored-by: Pierre-Etienne Lord
Please check if the PR fulfills these requirements
What is the current behavior? (You can also link to an open issue here)
Missing button to return to initial extent of the map
What is the new behavior?
Added button to return to initial extent of the map
Does this PR introduce a breaking change? (check one with "x")
If this PR contains a breaking change, please describe the impact and migration path for existing applications:
Other information: