These are chat archives for ractivejs/ractive

12th
Sep 2018
Cerem Cem ASLAN
@ceremcem
Sep 12 2018 08:00
hmm. your components' names are not determined in the beginning (page load)?
kouts
@kouts
Sep 12 2018 12:34
starting view is not standard
Cerem Cem ASLAN
@ceremcem
Sep 12 2018 14:43
I think I got your point
kouts
@kouts
Sep 12 2018 14:45
backend instructs UI which View to load at start
it can be made static though
Cerem Cem ASLAN
@ceremcem
Sep 12 2018 14:46
so you have to instruct your router to handle this case too, right?
kouts
@kouts
Sep 12 2018 14:48
I'm not using a router right now but yes
it's still work in progress
Cerem Cem ASLAN
@ceremcem
Sep 12 2018 15:04

off topic (not that off but, kind of): What is a "bug" anyway? I think if:

  1. the part that isn't working at the moment was working in the past and there is no deprecation in the meanwhile
  2. documentation says something but sw (or system) doesn't/can't do it
  3. there are poor error messages that doesn't help much to find the root cause (I learnt this from Jose Valim, he was saying "Poor error messages are considered as bug")
  4. a behavior is inconsistent with the rest of the application or in general practice (this might be a bit fuzzy but I'll try to explain: if your app handles mouse over as a "focus" command for an <input /> and some inputs that doesn't behave like that on purpose (for safety reasons, maybe) that is clearly a bug. If the inputs that accepts "focus command via mouseover" and those that doesn't are separated visually (for example, safe inputs are green) that isn't a bug, but a feature)
    then these behaviors should be considered as bug.

what do you think?

kouts
@kouts
Sep 12 2018 15:10
:bug:
Cerem Cem ASLAN
@ceremcem
Sep 12 2018 15:11
:DDDD
kouts
@kouts
Sep 12 2018 15:12
I think all 4 apply
Chris Reeves
@evs-chris
Sep 12 2018 15:13
1, 2, and 3 definitely, and 4 yes, but it's a bit more context sensitive
in my experience, 2 is often a docs bug
Cerem Cem ASLAN
@ceremcem
Sep 12 2018 15:18
I'm also marking the issues as bug in my projects if a feature is definitely "expected" (as if the project has been reached to 1.0) but is missing at that moment
Joseph
@fskreuz
Sep 12 2018 17:09
To me, a bug is "something that doesn't work as described" :grin:
And this description could be a requirements document, a spec sheet, or anything that caused that functionality to exist in the first place.
And this is why I push everyone to have very detailed conditions of satisfaction/steps to reproduce because they're effectively historical records for determining bug vs feature vs out-of-scope. :grin: