app

This is obsolete now that the collection navigation is configured through the data model settings page

Since we also expose the Skia-bindings for a Canvas-like API I think it might be a good idea to start refactoring the API to utilise more named arguments e.g. ~x=..., ~y=....

What do you others think?

Version: v0.10.0
To reproduce, go to settings and add more than categories at the same time below any category.
When you assign the name for one of the new, the other get the same name.
If you go to the second and try to change the name, the first one gets the second name.
I hope this helps.
Thanks.

[aw-qt_2021-03-26T00-09-49.log](https://github.com/ActivityWatch/activitywatch/files/621747

/area API
/kind good-first-issue

Describe the feature

For flagged fields like kubernetes.podspec-fieldref the validation should include the name of the feature flag to toggle in the error message it surfaces. The validation logic is roughly here: https://github.com/knative/serving/blob/644798277d9fe6715e4f638281141356df46d7e1/pkg/apis/serving/k8s_validation.go#L246