4 Matching Annotations
  1. Nov 2022
  2. github.com github.com
    Many routers with warning `<Component> was created with unknown prop` · Issue #4652 · sveltejs/svelte
    1
    1. TylerRick 22 Nov 2022
      The console needs to be readable in development and to provide the best DX I have to design my libraries in ways that prevent these warnings. This results in design decisions that are detrimental to functionality and/or code readability/simplicity.
      errors/warnings: ignoring/filtering out errors that don't apply / are unhelpful / you can't do anything about errors/warnings: too noisy
    Visit annotations in context

    Tags

    Annotators

    URL

    github.com/sveltejs/svelte/issues/4652
  3. Apr 2021
  4. github.com github.com
    WayneD/rsync
    1
    1. TylerRick 13 Apr 2021

      Mentioned here:

      but I can't find it on my system

      errors/warnings: ignoring/filtering out errors that don't apply / are unhelpful / you can't do anything about workaround treating/address the symptom rather than the underlying problem rsync
    Visit annotations in context

    Tags

    Annotators

    URL

    github.com/WayneD/rsync/blob/master/support/rsync-no-vanished
  5. Sep 2020
  6. github.com github.com
    Uncaught (in promise) TypeError: Cannot read property 'removeChild' of null · Issue #2086 · sveltejs/svelte
    1
    1. TylerRick 30 Sep 2020
      Since this issue seems to pop up periodically, it would be useful to turn this into a warning. It may not be elegant, but it prevents surprise blank screens due to a navigation error.

      Not an actual fix.

      errors/warnings that you can't do anything about errors are helpful for development (better than silently failing) user-friendly workarounds
    Visit annotations in context

    Tags

    Annotators

    URL

    github.com/sveltejs/svelte/issues/2086
  7. stackoverflow.com stackoverflow.com
    Uncaught (in promise)
    1
    1. TylerRick 30 Sep 2020
      It is showed as an error, but it is a warning as it doesn't break anything. I hate having warning/error in my console not coming from me. It is not justified as it's not bad practice imho
      warnings errors/warnings that you can't do anything about
    Visit annotations in context

    Tags

    Annotators

    URL

    stackoverflow.com/questions/44678505/uncaught-in-promise