16 Matching Annotations
  1. Apr 2021
  2. Jan 2021
    1. The extra div soup is two fold:
    2. (this issue)
    3. A component reserving a slot but needing to perform manipulation on its content dom reference will need to add an extra element wrapper on the receiving site (some people mention it here: #2106).
    4. A big app will have lots of components compared to regular html elements and these need to be wrapped before being fed to a slot, every single time on the call site
    5. I think this is very important feature to implement. Because for now we need to wrap target components by useless wrapper nodes.
  3. Oct 2020
    1. Looks like the problem is that debounce defaults to waiting for 0 ms ... which is completely useless!

      It would be (and is) way to easy to omit the 2nd parameter to https://lodash.com/docs/4.17.15#debounce.

      Why is that an optional param with a default value?? It should be required!

      There must be some application where a delay of 0 is useless. https://www.geeksforgeeks.org/lodash-_-debounce-method/ alludes to / implies there may be a use:

      When the wait time is 0 and the leading option is false, then the func call is deferred until to the next tick.

      But I don't know what that use case is. For the use case / application of debouncing user input (where each character of input is delayed by at least 10 ms -- probably > 100 ms -- a delay of 0 seems utterly useless.

    1. emphasized the disutility of 1:1 maps and other overly detailed models: "A model which took account of all the variation of reality would be of no more use than a map at the scale of one to one."
  4. Sep 2020
  5. Feb 2017