thomashoneyman/purescript-halogen-hooks

Issues

• Runtime exception when running two hooks components at the same time

  #73 opened 2 years ago by hrajchert
  1

• EventSource.emit docs are misleading for Hooks

  #48 opened 4 years ago by milesfrain
  4

• Runtime-Error "Uncaught TypeError: Cannot read property 'value0' of undefined"

  #68 opened 4 years ago by CarstenKoenig
  11

• performance improvements

  #70 opened 4 years ago by srghma
  1

• question - is there something holding up releasing latest version here?

  #67 opened 4 years ago by afcondon
  2

• Clarify `captures` documentation

  #65 opened 4 years ago by milesfrain
  1

• Make Puppeteer performance test code available in a separate package

  #58 opened 4 years ago by thomashoneyman
  1

• HookM code that modifies state can't be passed between components

  #37 opened 4 years ago by marcusbuffett
  13

• Consider absorbing `use*State` convenience functions from Hooks.Extra

  #50 opened 4 years ago by milesfrain
  2

• Link to cookbook's Halogen Examples ported recipes

  #51 opened 4 years ago by JordanMartinez
  1

• HalogenIO.dispose doesn't remove Hook-based components

  #41 opened 4 years ago by JordanMartinez
  4

• Push docs to Pursuit

  #45 opened 4 years ago by JordanMartinez
  4

• Halogen.Hooks should re-export the function memoComponent

  #42 opened 4 years ago by dederer
  1

• Fork in initializer fails to update state

  #40 opened 4 years ago by JordanMartinez
  1

• Enabling multi-Output via `Variant` and multi-Query via `VariantF`

  #38 opened 4 years ago by JordanMartinez
  4

• Sequential state updates don't cause hook re-execution.

  #5 opened 4 years ago by frabbit
  15

• Button and Container example not working outside of storybook

  #36 opened 4 years ago by milesfrain
  2

• Consider refactoring `modifyState` back to tokens, but use a different term to refer to the concept

  #30 opened 4 years ago by JordanMartinez
  12

• Is it possible to pass hooks around?

  #6 opened 4 years ago by prescientmoon
  4

• Optimization: only recheck `useTickEffect` memos when an effect modified state

  #26 opened 4 years ago by JordanMartinez
  1

• Make test code available to other packages

  #24 opened 4 years ago by JordanMartinez
  3

• useTickEffect finalizers don't get run when dependencies change

  #9 opened 4 years ago by JordanMartinez
  1

• Finalizers for useTickEffect and useLifecycleEffect run twice upon component removal

  #13 opened 4 years ago by JordanMartinez
  3

• Optimization: remove unnecessary `liftEffect`s throughout codebase

  #14 opened 4 years ago by JordanMartinez
  1

• Multiple uses of `useMemo` reevaluates values with unrelated dependencies

  #10 opened 4 years ago by JordanMartinez
  0

• Q: In useState example `Hooks.get stateToken` is not really necessary right?

  #4 opened 4 years ago by safareli
  2

• For readability in custom hooks, export type signatures of various functions via type aliases

  #1 opened 4 years ago by JordanMartinez
  4