NEW FireBAT: Map -> Print Advisory
- Dominant language
- Python
- Stars
- 65
- Forks
- 11
- Avg merge
- 21h 25m
- Merged PRs (30d)
- 70
Description
**As a** *FBAN/FBS* **I want** *to save the FBA as a PDF* **So That** *the RWCO can review and sign it and it can be distributed to dispatchers, Ops, Plans, IMT colleagues, and stakeholders (sometimes industry/contractors in the field) as appropriate.*
**Additional Context**
- see [Figma](https://www.figma.com/file/AUhBnTB50dnY7ysoxBSqPN/FireBAT-2021?node-id=207%3A2) - needs heavy design collaboration
- There is an area for capturing text relating to the FBA - this may imply we are dealing with two screens - screen 1) capture information and screen 2) display advisory preview / print.
- There may be future requirements around who has rights to view and edit the FBA.
- There are concerns around the rendered FBA changing on the fly - which would cause it to differ from the final PDF.
- Think in terms of 3 separate screens. Screen 1: Edit, Screen 2: Read only, Screen 3: System dialog print preview
- Screen 2 and Screen 3 are really the same page, but in print mode, the styles are slightly different. Screen 2 is rendered with CSS making it a normal web page. Screen 3 is rendered with CSS that renders it appropriately for printing.
**Acceptance Criteria**
- [ ] Given I am on the "Preview FBA" screen, When I look at the screen, What I see is as close as possible to what is going to end up being printed to PDF.
- [ ] Given I have clicked on the "Print / save as PDF" button, I can use the system dialog to print/save the page as show in the system dialog preview.
- [ ] Given I have printed/saved the output, it is formatted correctly for Portrait.
**Definition of Done**
- [ ] Ready to Demo in Sprint Review
- [ ] Does what I have made have appropriate test coverage?
- [ ] Documentation and/or scientific documentation exists and can be found
- [ ] Peer Reviewed by 2 people on the team
- [ ] Manual testing of all PRs in Dev and Prod
- [ ] Merged
Contributor guide
Research direction
Start with the linked Figma design and clarify the proposed edit, read-only preview, and print-preview screens with the team. No files, tests, or entry points are named in the issue, so first locate the existing FBA/map interface and its frontend tests. Done means the preview matches the PDF closely and portrait printing or saving works through the system dialog.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- figma, react
- Domain
- design, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100