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

Control tool at opening #222

Merged
merged 3 commits into from
Nov 1, 2018
Merged

Control tool at opening #222

merged 3 commits into from
Nov 1, 2018

Conversation

pelord
Copy link
Member

@pelord pelord commented Oct 31, 2018

Please check if the PR fulfills these requirements

What is the current behavior? (You can also link to an open issue here)

What is the new behavior?
Adding a way to control which tool is open on page initialization. Creating keys and an array of allowed tool names.

Linked with PR infra-geo-ouverte/igo2#236

Does this PR introduce a breaking change? (check one with "x")

[ ] Yes
[X] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications:

Other information:

@pelord
Copy link
Member Author

pelord commented Oct 31, 2018

This pr solve issue #218

@cbourget
Copy link
Collaborator

cbourget commented Nov 1, 2018

This is a nice feature but I feel like it be in the app itself instead of the ToolService. I don't think a library component should have control over the router and be the one that decides what the "tool" param does.

@pelord
Copy link
Member Author

pelord commented Nov 1, 2018

Yes you are right.
This has been moved from tool.service to igo2 project (into portal)
Check PR infra-geo-ouverte/igo2#236

@cbourget
Copy link
Collaborator

cbourget commented Nov 1, 2018

Awesome! Thank you

@mbarbeau mbarbeau merged commit 9a2abf9 into master Nov 1, 2018
@mbarbeau mbarbeau deleted the controlToolAtOpening branch November 1, 2018 19:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants