Chris Swithinbank
Chris Swithinbank
Oh, just noticed this was patched by #59, but I guess is not yet in the version 0.4.4 distributed over npm.
Thanks @adngdb — linking [your comments on Gitter](https://gitter.im/boardgame-io/General?at=5f55d76adfaaed4ef536f4ee) too for future reference. boardgame.io lacks a `playerView`/`stripSecrets` equivalent for plugins at the moment, which would probably be a prerequisite for this....
Just updating here to say that https://github.com/boardgameio/boardgame.io/issues/671 has been resolved and plugins can now send different state to each player, so adding some player-targeting logic should now be possible.
Remembered the problem with this: Linear supports a different set of statuses _per team_ and if you use one that doesn’t exist in the team, it’ll be ignored which is...
Progress in https://github.com/delucis/github-to-linear/tree/dx-184/default-statuses but I’m not very happy with the code — `options.js` probably needs a full refactor if we really think this is helpful.
I’m not sure Linear supports this if I’m understanding what you mean correctly. Linear issues can be automated by linking GitHub PRs (not GH issues) — https://linear.app/docs/github#link-prs — but all...
This could be do-able, but would require a relatively high-privilege GitHub access token to modify the pull request — currently the extension requests a Linear access token, but isn’t authorized...
> Is this format alright? I might make the colours tuples of `[hex, name]`? ```js { Blues: [["#54b9ff", "Sky Blue"], ["#2b7eca", "Cerulean Blue"]], // ... } ``` Or just make...
I think this PR can be closed? Sorry if I’m mistaken @alexanderniebuhr!
Oh, sorry! Feel free to reopen then — I’m just cleaning up and updating PRs after migrating deploys to Netlify. (Might be a good idea to update the PR description...