Fix legend position (#192)
Changed traffic light colors (#189). Stronger red and green. Better suited for colors in graphs. This version of qmongjs: https://github.com/mong/qmongjs/commit/8a2de2df0
Alphabetic sorting of treatment units in menu (#188).
Added treatment unit selection menu (#186).
Filter out data with denominator < 5 (#185).
Included iframeResizer.js (#183).
Fix header and update medical fields (#182)
Almost all R code has been replaced by react.js.
Fix app so it will work with imongr >= 0.12 (#176). The functions get_indicator, get_registry and get_agg_data replaced by get_table function.
include = 1
Updated fagomr according to database update:
tarmkreft into tarmkreft_colon and tarmkreft_rectum.rygg to nkr_rygg (to be consistent with nkr_nakke).js in a bundle (#139). js code and development moved to https://github.com/mong/qmongjs
Number of indicators per medical field.
qmongrdata. At the moment, the tests in the current version of qmongr will fail with the latest (unreleased) version of qmongrdata.version_info. Previous version will fail for less than two packages (#128)Fix barchart button bug (#117)
Smoother transitions (#115)
Figure legend with interaction (#114)
Added interaction to the chart lagend and fixed the layout of the legend
Use internal data (#113)
Aggregating data from qmongrdata takes forever, and slows down the starting of the app (see issue #112). In this commit, the data aggr_data is created by running the function app_data() beforehand, and is used directly by the app.
Click on indicator in table will reveal barchart plot. A clickable button can change the plot to a line plot, showing a time series.
Added dependency: development version of shiny from rstudio/shiny on github. moduleServer, introduced in version 0.6.4, is not part of shiny on cran
testModule is no longer a part of shiny, so we had to use testServer to test our modules. callModule way of running modules and regular functions way of making modules can not be tested by testServer. Thus, we had to use moduleServer to make modules (and run the modules as regular functions). This is also the recommended way according to ?shiny::callModule:
Starting in Shiny 1.5.0, we recommend using moduleServer instead of callModule, because the syntax is a little easier to understand, and modules created with moduleServer can be tested with testServer().
In practice we replaced all
with
in the module part, and replaced all
shiny::callModule(mymodule, "myID", arg1 = "blablabla", arg2 = "blablabla2")with
mymodule("myID", arg1 = "blablabla", arg2 = "blablabla2")where we call modules.
docker_push) will be launched for all brancheshnskde/qmongr:test if $TRAVIS_BRANCH is master
hnskde/qmongr:latest if $TRAVIS_TAG is on the format vX.Y.Z.docker_hub is moved to https://github.com/mong/scripts for easy reuse. I use the same setup for tmongr and helseatlas and was tired of updating three places all the time.quality_overview into several modules (#97)qmongrdata version 0.2.3
stringr::str_sort(locale = "no") instead of sort(), e.g. to sort Arendal before Ålesund.qmongrdata version 0.1.0
