Håvard Wormdal Høiby
Håvard Wormdal Høiby
Hi. :wave: By running in react [`strict-mode`](https://reactjs.org/docs/strict-mode.html), I noticed that that `react-vis` relies on the now deprecated [`componentWillReciveProps`](https://reactjs.org/docs/react-component.html#unsafe_componentwillreceiveprops). With a quick search in the repo I found the following usages...
1. Add the flag `--wm` to `create-workflow-home` with the full package name like `workflow-wm-i3`. This will force the `create-workflow-home` to add this wm as a dependency and to wire it...
## Steps to reproduce - install `window-build-tools` as described in the manual. - install workflow `npm i -g workflow` in PowerShell (The actual steps included running `npm i -g create-workflow-home`...
Add the command `workflow create-flow /path/to/flow.js [--template ]` to `workflow-cmd`. Should create a new flow file which will run on the installed version of `workflow`. Should default to a [ReactExample.js](https://github.com/havardh/workflow/blob/master/packages/create-workflow-home/files/static/flows/ReactExample.js)....
`workflow-server` is the next big planned change to workflow. This issue will serve as a tracking issue for the implementation with a high-level description. ## Description The first approach to...
The `workflow-parser-arguments` does not parse positional arguments correctly. The first argument passed along is the name of the flow file which is being resolved. This argument should not be included....
## How to reproduce Add a split with two instances of the same application. ``` import React from 'react'; import render, { Workspace, requireComponent } from 'workflow-react'; const { SplitH...
## Expected The following code should trigger automatically playback on linux ``` ``` ## Actual Playback must be triggered manually. ## Detail The `uri` spec for autoplaying a track seems...