uuayn

oh...the entire casdoor schema is stringly typed... 😬

hmm, yeah i'm finding tons of undocumented parameters in the beego docstring annotations, gonna try generating sea-orm code and just make sure that the code i write over that for interacting with the casdoor database is more or less doing the same thing as the casdoor api on an as-needed basis

i'll still submit a PR for adding responses where possible, i just don't have the attention span for addressing all the undocumented parameters (which i assume are necessary to generate proper api client code from the generated swagger)

hmm, does the casdoor http api return response codes other than 200 very often? it looks to me like even when there is a DB error of some kind it returns a http 200 with a json body containing a Status field set to "error"

i'm also wondering if the casdoor http API abstracts over transactions for any of the operations it performs...if not i might be better off just generating ORM code from the database itself and using that for non-OIDC interactions