-
Notifications
You must be signed in to change notification settings - Fork 41
Rename objects #427
Comments
Thoughts @kadel @pradeepto |
Good catch. We should be consistent with our object naming. This is definitely an UX issue. |
There is a difference between
|
@kadel Problem is that most people won't be looking at the code-names, but rather the documentation names. Could we refer to it as a routeSpecObject instead within the documentation? Are you good with the other parts being renamed (containerObject, serviceObject, etc..) |
We should distinguish between what is referring to our |
Hmm. so in the docs, let's go with routeSpecObject? @kadel |
You are talking about what will be in the sidebar in Objects section, right? I would actually go with just 'route' and 'ingress' |
PR here: #429 |
Within file-reference.md we have different names for different objects.
For example: http://kedgeproject.org/file-reference/#containerspec
We have containerSpec, service and then.... routeObject.
Names should be consistent.
Either:
containerSpec, serviceSpec, routeSpec
or
containerObject, serviceObject, routeObject
👍 for Object.
The text was updated successfully, but these errors were encountered: