Bug 2046498 - "All Projects" and "all applications" use different casing on topology page
Summary: "All Projects" and "all applications" use different casing on topology page
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.10
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.11.0
Assignee: Abhinandan Das
QA Contact: spathak@redhat.com
Depends On:
TreeView+ depends on / blocked
Reported: 2022-01-26 20:00 UTC by Samuel Padgett
Modified: 2022-08-10 10:44 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Version: 4.10.0-0.nightly-2022-01-17-091922 Cluster ID: 0991574b-4684-468f-8506-9e6dd3d8ac15 Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.137 Safari/537.36
Last Closed: 2022-08-10 10:44:09 UTC
Target Upstream Version:

Attachments (Terms of Use)
Screenshot (67.54 KB, image/png)
2022-01-26 20:00 UTC, Samuel Padgett
no flags Details
application-add-page.png (171.10 KB, image/png)
2022-02-01 16:14 UTC, Christoph Jerolimov
no flags Details
application-topology.png (34.66 KB, image/png)
2022-02-01 16:14 UTC, Christoph Jerolimov
no flags Details
topology-shortcuts.png (61.09 KB, image/png)
2022-02-01 16:15 UTC, Christoph Jerolimov
no flags Details
add1.png (34.13 KB, image/png)
2022-02-01 16:15 UTC, Christoph Jerolimov
no flags Details
app2.png (30.00 KB, image/png)
2022-02-01 16:15 UTC, Christoph Jerolimov
no flags Details

System ID Private Priority Status Summary Last Updated
Github openshift console pull 10999 0 None Closed [BUG] podman containers are not starting post reboot 2022-06-15 10:18:17 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 10:44:28 UTC

Description Samuel Padgett 2022-01-26 20:00:44 UTC
Created attachment 1855621 [details]

We should be consistent in the case we use for the "All Projects" and "all applications" dropdown items, particularly because they appear side by side. One uses headline case, the other is all lowercase. (See screenshot.)

Comment 1 Christoph Jerolimov 2022-02-01 15:06:08 UTC
- "All Projects" should be "All projects"
- "all applications" should be "All applications"

Comment 2 Christoph Jerolimov 2022-02-01 16:14:49 UTC
Created attachment 1858390 [details]

Comment 3 Christoph Jerolimov 2022-02-01 16:14:57 UTC
Created attachment 1858391 [details]

Comment 4 Christoph Jerolimov 2022-02-01 16:15:09 UTC
Created attachment 1858392 [details]

Comment 5 Christoph Jerolimov 2022-02-01 16:15:17 UTC
Created attachment 1858393 [details]

Comment 6 Christoph Jerolimov 2022-02-01 16:15:26 UTC
Created attachment 1858394 [details]

Comment 7 Christoph Jerolimov 2022-02-01 22:37:38 UTC
Asked Abigael Donahue about our convention. Thanks for this answer:

It seems like "application" and "projects" are treated as common nouns (not capitalized) in documentation and in examples I found in the terms list, so I'd follow that convention, even though there is a project resource and not an application resource. So this is what I'd recommend for the examples you shared:

- Create application
- No applications
- Create project
- No projects

We should fix and correct this it on the shown pages/screenshots, and search for more inconsistencies.

Comment 8 Samuel Padgett 2022-02-04 12:40:25 UTC
We have different conventions in console itself for k8s kinds. Currently, we always use PascalCase for Kubernetes types. Since Project is a type, I'd expect it to be capitalized. If we change Project, we have to consider changing all kinds, which is an enormous change :/

Comment 9 Samuel Padgett 2022-02-04 12:54:07 UTC
To give some more background:

The reason we do this is that we have to handle custom types that can have any name. We only get the PascalCase kind from the API. We used to try to humanize these names in descriptions, but there is no good rule for doing it correctly. For instance, `OAuthClient` should be humanized to `OAuth client` and not `o auth client`. You can't know that programmatically unless you special case every exception, which is impossible because users can add their own custom resources. To avoid these problems, we decided to always use the k8s kind when referring to resources in the console even though this is not what the docs use.

We could revisit this, but it would be a large effort and potentially require a big chunk of the UI to be translated again due to string changes if we're not careful.

Comment 12 Vikram Raj 2022-02-17 13:59:50 UTC
Verified it on 4.11.0-0.nightly-2022-02-16-131355. Now we have the `All applications` option in Application dropdown.

Comment 14 errata-xmlrpc 2022-08-10 10:44:09 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.