Sorry, let me rephrase. Is this how it is supposed to work? Because right now it looks like a bug. The documentation is really terribly sparse on this topic.

apt-rdepends exists. This functionality should really reside in apt-cache itself.

if you put the reactive statement $: validate(inputValue); after the function updateInputValue declaration, it's working as expected:

can you remove the not a bug label considering that PaperTrail is creating this empty versions even when :updated_at is an ignored attribute?

Maybe it's also a bug because every warning should be ignorable? Not sure.

If that one somehow ends up being deemed an intended behavior rather than a bug, then it should definitely get explained in the docs too.

I'm not sure yet how much of this is a bug.

This isn't a bug. Svelte's reactivity is triggered by assignment, so it won't re-render on mutations like array pushing.

We want arr.push(foo); arr = arr; to work, and this is a bug.

(Note sure if this is a feature request or a bug...)

This isn't really a bug, because if you have an async function that returns a function, it doesn't really return a function - it returns a promise. I don't remember whether the Svelte internals currently check for the onMount callback's return being a function or whether they check for it being truthy. Maybe there's some adjustment to be made there.

Sometimes, the line between 'bug' and 'feature' is a hard one to draw. Generally, a feature is anything that adds new behavior, while a bug is anything that causes incorrect behavior. Sometimes, the core team will have to make a judgment call.

We iterate to deliver features, so we often don't have functionality that people expect. For this reason, 'people could reasonably expect this functionality' does not make it a bug.