22 Matching Annotations
  1. Last 7 days
    1. Is there a good way to do this given the compiler won't know at build time what events are needed? Should I make a wrapper that does addEventListener myself with a bind:this? Would be nice if Svelte could handle dynamic events though.
  2. Sep 2020
    1. The primary motivation for this change is to have the same behavior between dom elements and wrapper components. Class directives are extremely convenient but that convenience is lost when a section of code needs to be converted to a component.
    2. This is especially useful for components that are a simple wrapper around a dom element.
  3. Jul 2020
  4. Jun 2020
  5. May 2020
  6. Apr 2020
  7. Feb 2020
  8. Jan 2020
  9. Nov 2019
  10. Sep 2019
    1. This version of Field is a thin wrapper over the official Field component, and the only Field API that this library uses/overrides is the field-level validate prop, so even if you are using this library's Field component, you will still get improvements as features are added to the React Final Form library in the future.
  11. Aug 2019
  12. May 2015
    1. if the client is incapable of working with HTTP headers

      OK... So in fact the wrapper I am implementing for recs ecommerce API is overkill - it is redundant with http. I'll keep it though, since I like to define my own error codes.