Sebastien Dubois
Sebastien Dubois
Sorry for the confusion. You're right, it doesn't seem to be supported yet. I'll continue filtering on the client side for now: ``` import { ProjectSchema, Camelize, Gitlab } from...
I have introduced issues to request this for groups and projects: - https://gitlab.com/gitlab-org/gitlab/-/issues/429315 - https://gitlab.com/gitlab-org/gitlab/-/issues/429316
Hello Justin, For visibility, I thought it was supported, but you're right, it doesn't seem to be yet. Bummer :p
I have introduced an issue to request this: https://gitlab.com/gitlab-org/gitlab/-/issues/429314
For now I'll continue doing it on the client side: ``` import { GroupSchema, Camelize, Gitlab } from 'https://esm.sh/@gitbeaker/rest?dts'; export async function getInternalGroups(gitLabClient: InstanceType): Promise { // TODO refactor once...
I am trying to refresh user data by calling `auth.getUser()` and am facing the same error.
Related issue: https://github.com/solid/solid-spec/issues/150
I imagine that there could be different granularity levels for such a feature. A pod provider could be interested in how much traffic there is towards a specific pod, without...
Adding stable error keys to the returned JSON would be great (e.g., user.already.registered). That's clearer than abstract error codes ala Oracle. And the ideal would be using the structure proposed...