-
Notifications
You must be signed in to change notification settings - Fork 333
Cleanup internal endpoints #2086
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suspect this will conflict with #2059. Not sure what to do about it, though.
@@ -731,59 +729,64 @@ type FeatureAPI = | |||
:<|> FeatureConfigGet 'WithLockStatus 'TeamFeatureSelfDeletingMessages | |||
:<|> FeatureConfigGet 'WithLockStatus 'TeamFeatureGuestLinks | |||
|
|||
type FeatureStatusGet featureName = | |||
type FeatureStatusGet f = |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please, no one-letter names :(
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are you picking on this particular one? The codebase is full of one-letter names. Even for this very purpose (see e.g. Galley.API.Teams.Features
). I'm actually not sure what the problem is with one-letter names when they stand for very abstract things in a very limited scope (e.g. a single expression, like in this example). Also, the name that was there before isn't even correctly describing what the variable stands for (it's not a "feature name").
434ef39
to
3700c3f
Compare
3700c3f
to
f7bea4c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall this looks good.
I'm just curious: what is the motivation for removing internal endpoints from Swagger? Should we maybe put it into a different root/folder, but still have Swagger for internal endpoints?
Because the current swagger is supposed to present the API as visible from the outside (e.g. the |
This moves internal endpoints to the
Internal
module hierarchy inwire-api
, so that they are not included in the generated Swagger, and removes usages of servant-generic from Galley's internal API.Checklist
changelog.d
.