[
https://issues.jboss.org/browse/JBIDE-20004?page=com.atlassian.jira.plugi...
]
Jeff Cantrill commented on JBIDE-20004:
---------------------------------------
[~adietish] [~mlabuda] Where do we see this now? Is it the category folders in the
explorer view? I don't know how the web console handles it or if they have a standing
convention. I presume its spelled out as desired on each web page. We could add info to
our enum to handle this case as there really is no sane way to know where to split an
capitalize.
OpenShift v3 resources names should be camelcasized or splitted by
space character
----------------------------------------------------------------------------------
Key: JBIDE-20004
URL:
https://issues.jboss.org/browse/JBIDE-20004
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.3.0.Beta1
Reporter: Marián Labuda
Assignee: Jeff Cantrill
Priority: Minor
Fix For: 4.3.0.Beta2
Currently OpenShift v3 resources are as one long name and without camel case practice or
spaces or spaces with capitalized first letters. It would be better to have more
appropriate format.
Affected resources:
* Buildconfigs should be "Build configs" or "BuildConfigs" or
"Build Configs"
* Deploymentsconfigs should be "Deployment configs" or
"DeploymentConfigs" or "Deployment Configs"
* Imagestream should be "Image streams" or "ImageStreams" or
"Image Streams"
* Replicationcontrollers should be "Replication controllers" or
"ReplicationControllers" or "Replication Controllers"
I would suggest to use capitalized separated wording but I leave it up to decision of
developer.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)