-
Notifications
You must be signed in to change notification settings - Fork 3
resolve name inconsistency #168
resolve name inconsistency #168
Conversation
|
||
@gcp_endpoint.route("/gcp", methods=["GET"]) | ||
@swag_from("../schema/gcp.yml") | ||
@google_endpoint.route("/google", methods=["GET"]) |
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.
@FKolwa does it make sense to rename our endpoint too? Wasn't sure about this
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.
Hm. I'm a bit torn on this one too. I'd like to stay as consistent as possible but gcp would probably make more sense as an endpoint. I'd say we probably should stick to gcp.
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.
We decided to keep it to google, because otherwise we would have a lot of exceptions and inconsistency again.
b521656
to
dce8ac6
Compare
Signed-off-by: Janine Olear <pninak@web.de>
dce8ac6
to
d8901f4
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.
LGTM!
Such consistency. 👏🏻 |
closes #117