Question babel-plugin-flow-runtime: overwrite assert: false

According to the documentation assert: true should be turned off during production builds.

For an UMD library with an public API it would be beneficial if assertions could be scoped to specific public methods. That would allow getting the the benefits of run time type checking for the library consumer without getting the overall performance penalty.

Here’s an example, where I’d like to get assertions for the public filter method (taken from a tcomb babel-plugin-transform-flow-strip-types implementation).

...
const FilterLogic = enums.of(['or', 'and'], 'FilterLogic')

type FilterExpression = {
  field: string,
  operator: string,
  value: any
}

type FilterGroup = {
  logic: FilterLogic,
  filters: Array<FilterExpression | FilterGroup>
}

export default class Collections {
...

// Would it be possible to turn on assertion for .filter?
// maybe by using a decorator like @guarded?
  filter (options?: FilterGroup) {
    if (!options) {
      return toJS(this.$filter)
    }
    this.$filter = options
    this.data = []

    return this.read()
  }
...
}

[phpnode]

Added pragma like // @flow-runtime assert, decorate and suppression types / comments in v0.0.7, docs here - https://codemix.github.io/flow-runtime/#/docs/pragmas

[RainerAtSpirit]

This looks excellent. Thanks for adding.