If the flow plugin runs before the class properties one (or if the class properties plugin isn't used), we remove uninitialize class fields:

class Foo { x: string }

currently becomes

class Foo {}

while it should be

class Foo { x }

If someone still wants the old behavior, they can either use flow comments (as [offically recommended](https://github.c

For users that have made a purchase, add a link to Managing purchases, renewals, and cancelations the suggested InlineHelp links on the following pages:

• plans
• my plan
• settings
• support
• customer home
• any purchase-related screens

ref: pbOQVh-mX-p2#support

This would be a nice little feature to have, Excel users are using this a lot.

Note: for support questions, please use stackoverflow. This repository's issues are reserved for feature requests and bug reports.

• I'm submitting a ...

  • bug report
  • feature request
  • support request => Please do not submit support request here, see note at the top of this template.

• Do you want to request a feature or report a bug?

Minor bug

The summary report in stdout has fields provided by summaryTrendStats, but in JSON format report ignores that definition

Environment

K6 version: k6 v0.27.1 (2020-07-30T10:20:27+0000/v0.27.1-0-g4ee1ca96, go1.14.6, linux/amd64)
OS version: 18.04.2 LTS (Bionic Beaver)

Expected Behavior

The fields defined in summaryTrendStats are represented in the JSON summary report

Actual