Antony Male
Antony Male
There's the fun around syncthing-inotify randomly delaying scans as well?
Ah, no, I guess the GUI gets events when the next scan is delayed, because a scan just happened... duh. Carry on.
OTOH, you care about how long you have to wait until the next scan. If you're given a timestamp, you're going to be doing that "wait time" calculation yourself in...
I don't want to be rude, but I said this was a breaking change in the issue you raised. If you feel differently the right thing to do is to...
Opening two dialogs at once breaks Bootstrap something terrible (after closing the second dialog, it thinks the first one has been closed too, so things like scrolling break).
@SpaceOgre The easiest way to suppress individual nullability warnings is to use the [null-forgiving operator `!`](https://docs.microsoft.com/en-us/dotnet/csharp/language-reference/operators/null-forgiving): ```cs var myClasses = list .Where(x => x.Prop != null) .Select(x => new MyClass(x.Prop!));...
@dependabot rebase
Adding fields is fine. Quasi-enums can be documented, and if you document them as potentially gaining new values in the future I can ensure that that won't break things.
There are various json schema specs as well. Maybe document responses using a schema, and test them against the schema? You can probably also gen docs from the schema.