Users typed endpoint

[kennethnrk]

Migrated users and user_topics to typed endpoint.

I have not used Pydantic's URL type for payload_url because URL doesn't flag incomplete URLs like http://127.0..:6000.

I have also created check_int_param_in which is similar to check_int_in but check_int_param_in raises a ValueError not ValidationError.

Similarly check_param_url, which is similar to check_url.

[timabbott]

Is there a better way to do this AfterValidator pattern that woudln't require the lambda x wrapper?

[kennethnrk]

For validation functions that accept only 1 positional argument we could pass the function directly to AfterValidator. But for functions like check_int_in which take a second parameter we would need tot use lambda or a similar wrapper function. Both lambda and wrapper functions have been used in the docs, the do the same thing esssentially.

[timabbott]

Any ideas on a better way to do this role parameter without so much nesting? I suppose an option would be to just declare a RoleParameterType and use that here? I think we have some other views that use a lot of enumerated integer parameters, so it'd be good to have a clean pattern for these.

[timabbott]

https://docs.pydantic.dev/2.0/usage/types/number_types/ might offer some inspiration.

[kennethnrk]

Creating RoleParameterType is an option, I didn't create it initially because role isn't being used in any endpoint in any other file, but its being used twice here so it might be better to create a type.

We could use Enums or Literal but that would sacrifice the ability to pass a list. Both those would require us to hardcode specific values and do not take lists. Literal does take tuples but passing tuples throws linting errors.

[timabbott]

Yeah I think making a type for use in this file is worth it; if nothing else it'd be a good example pattern to try.