Challenge Overview
Our mission planner has so far been used to create standalone missions. Now we need to make some updates to make it more useful for the actual workflow where the consumer creates a service request and the provider creates the necessary mission. Here are the updates needed in this challenge:
1. When a provider accepts the service request and assigns a drone, a placeholder mission is created (this is already implemented, see PackageRequestService.assignDrone).
a) Set the mission name to "request from {consumer.name}, for {packageRequest.title}"
b) Copy over the zones attribute from PackageRequest to Mission object (zones attribute contains the regions to fly)
b) Copy over the zones attribute from PackageRequest to Mission object (zones attribute contains the regions to fly)
2. In the mission planner draw the regions to fly as an overlay on the map and add a toggle button to show/hide these regions. Make sure the overlay won't interfere with creating the waypoints (mouse click/drag events should pass through the overlay so the waypoints can be created/moved)
3. Show a readonly list of the regions to fly in a floating window in the map, pinned to the left. The style should be similar to the waypoints list shown on the right.
4. When the planner is opened, make sure it's centered and zoomed to the regions to fly.
5. If the planner is used to edit a standalone mission, there should be no changes to how it currently works, except that it should center and zoom on the mission path.
6. When creating a standalone mission, center and zoom on the current user location (already implemented), but location request should be loaded when loading any page on the site, not just the mission planner, and this location should be cached. Right now, the map centers on a default point first, then waits for the location request to complete (3-4 seconds) and then jumps to the right location.
Base code for this challenge is plannerUpdates branch in both frontend and backend repositories
Any changes to backend api require updating swagger, postman and test data.
3. Show a readonly list of the regions to fly in a floating window in the map, pinned to the left. The style should be similar to the waypoints list shown on the right.
4. When the planner is opened, make sure it's centered and zoomed to the regions to fly.
5. If the planner is used to edit a standalone mission, there should be no changes to how it currently works, except that it should center and zoom on the mission path.
6. When creating a standalone mission, center and zoom on the current user location (already implemented), but location request should be loaded when loading any page on the site, not just the mission planner, and this location should be cached. Right now, the map centers on a default point first, then waits for the location request to complete (3-4 seconds) and then jumps to the right location.
Base code for this challenge is plannerUpdates branch in both frontend and backend repositories
Any changes to backend api require updating swagger, postman and test data.
Final Submission Guidelines
Submit a git patch for your changes to the base codeSubmit a short video demonstrating the implemented features
Submit a short verification guide with screenshots (verification guide should be placed in the /verification-docs directory)