Greenstand / Greenstand/treetracker-web-map-core
Map object support changing the initial status
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 4
- Forks
- 33
- PR merge metrics
- No merged PRs in 30d
Description
Currently, we init the Map object by bounds or filters, like: userid=1
Now we should be able to make the Map object being able to switch between these states, like change from `userid=1` to `treeid=xxx`, vice verse
---
Some hints:
- Please read our [readme](https://github.com/Greenstand/treetracker-web-map-core#treetracker-web-map-core) for more information/guide/tutorial.
- Here is [an engineering book](https://greenstand.gitbook.io/engineering/) in Greenstand.
- To know more about our organization, visit our [website](https://greenstand.org).
- If you want to join the slack community (some resources need the community member's permission), please leave your email address.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the repository README and trace how the Map object is initialized from bounds or filters. Identify the existing entry point for its initial state and determine how switching between userid and treeid should be represented. Done means the Map object can change between those filter states without reinitialization.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100