Releases: PMA-2020/datalab
Releases · PMA-2020/datalab
1.4.0
1.3.0
Favicon added. Tooltip added. French translations for guided tour added. Some general updates, bugfixes, and developer updates, including automated tests.
New features
General updates
- Guided tour text updates (#70, #83)
- Break data down by: Default to "None" option (#80)
- Guided tour: French translations (#90)
- Change positioning/margins of "pre-footer text" (#87)
- Home page greeting text - remove border (#86)
- Text updates - home screen & pre-footer (#88)
Bugfixes
- Windows 10 IE: Country-round modal is empty (#82)
- Definitions disappear after charting (#78)
- Data labels occasionally mis-positioned (#69)
- French chart button text bleed (#94)
- Distribution indicators (pie chart / "method mix" indicators) not displaying due to "None" (#99)
- Over-time charts: legend and data labels do not display country name (#92)
- Chart title text: "by None" should not display (#91)
- Move position of some guided tour dialogue boxes so that they appear on screen (#71)
- Crazy legends showing up at top (#81)
- Footer text update - copyright year (#89)
Developer updates
1.2.0
New Features
- Guided tour: There is now a button at the bottom left of the UI. If the user clicks this, the background of the screen darkens, and a guided series of dialogue boxes appear, highlighting various parts of the UI and explaining their function.
- Dynamic URLs: It is now possible to know the rough state of the app and share that state with others via the URL. The URL now displays chart options that are selected.
- New tooltips: Added several tooltips, especially to UI items when they are in an inactive/disabled state (Chart button, certain disaggregation options, data download button, black & white button, over-time button).
General updates
- All values on a graph are now presented to one decimal point, even if it is ".0".
- Removed "contact" button as a result of the "guided tour" button now being placed there instead. As a follow-up, a prompt has been added to the guided tour to highlight the "contact us" link at the top-right of the screen.
- Replaced separate save/clear styles buttons with one "reset styles" button. Now, styles automatically are saved without having to click any special button. The styles are preserved between charts that are made in a single session, but not between separate sessions.
- Removed pie chart legend, as it was redundant and also decreased the size of the pie chart.
Bugfixes
- Stable browser support
- Edge
- Firefox
- IE
- Safari
- Smart phone / tablet (general)
- Citations at bottom now display correctly.
- Numbers now display correctly on graphs.
- Data download button works again.
- Styles tab now works again.
- Fixed an issue in which "black & white" button would was always active, regardless of how many colors were present in the chart. The number of colors allowed to be rendered in black & white / grayscale is now limited to 3.
- Country-round selection modal options were erroneously clearing after clicking "reset styles"
- Validation was effectively added by limiting the characters set which could be entered in a field (i.e. numbers rather than letters and numbers).
- Some fields are now pre-populated (i.e. title fields).
- Default values now appear as greyed out text in the background of the field.
- Fixed a bug in which axis label fields were controlling the opposite axis.
- Width of style fields now appears correctly at any width.
- Security - A vulnerable dependency was removed.
- Pie chart button now only appears when the indicator selected is possible to chart as a pie chart (i.e. numbers add up to 100%).
- Pie chart data labels were not rendering correctly.
- Widget tabs (Controls, Definitions, Styles) no longer have a graphical error at certain screen widths.
- Fixed a bug in which sometimes chart was rendered with too high a width.
- Fixed a bug in which the "over-time" button became automatically disabled after clicking "chart".
Notes
This release 1.2.0
is the first release to appear on GitHub. Prior updates were not compiled into releases, but for the purposes of ease of reference, 1.0.0
should refer to the initial minimum-viable-product first developed, and 1.1.0
should refer to the state of the application at the time the data model was replaced from a flat JSON file to a RESTful API.