This commit is contained in:
@@ -9,10 +9,24 @@
|
|||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## ROUGH SCHEDULE TO GET TO BETA
|
## ROUGH SCHEDULE TO GET TO BETA
|
||||||
|
|
||||||
|
Report designer improvements
|
||||||
|
add group by method to standard functions and document
|
||||||
|
ayGroupBy
|
||||||
|
settle on a standard for naming for preparedata parameter, update docs to match
|
||||||
|
it should reflect that it's a combination or package of different things one of them being the report data
|
||||||
|
remove default sample helper, css from new reports template
|
||||||
|
change new reports template to be simplified and stardardized
|
||||||
|
Clean up docs to properly explain what comes into preparedata and which keys are which
|
||||||
|
in docs it says see below or something but that's not ideal, put it directly into both sections if necessary in a code markdown block
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
security jwt tokens and expiration, can a user just keep working if they are set to inactive because their token hasn't expired?
|
security jwt tokens and expiration, can a user just keep working if they are set to inactive because their token hasn't expired?
|
||||||
should tokens refresh periodically and have a super short life?
|
should tokens refresh periodically and have a super short life?
|
||||||
|
|||||||
Reference in New Issue
Block a user