[JBoss JIRA] (JBIDE-21911) Icons for Service and Route are not whole
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21911?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21911.
---------------------------------
Verified on nightly build of JBT with OpenShift plugin build B258.
> Icons for Service and Route are not whole
> -----------------------------------------
>
> Key: JBIDE-21911
> URL: https://issues.jboss.org/browse/JBIDE-21911
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Fred Bricon
> Labels: openshift_v3
> Fix For: 4.3.1.CR1
>
> Attachments: icons.png, pficon-route-black.png, pficon-service-black.png
>
>
> Icons for OpenShift 3 services and routing are cut off. The upper arrow on an icon is not whole, the sharp part is missing. See on the screenshot:
> !icons.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ERT-66) Create Identifier Completion Engine
by Ian Stewart-Binks (JIRA)
[ https://issues.jboss.org/browse/ERT-66?page=com.atlassian.jira.plugin.sys... ]
Ian Stewart-Binks edited comment on ERT-66 at 3/31/16 10:38 AM:
----------------------------------------------------------------
- Identifiers completion should also support CamelCase, i.e. if the identifier CamelCase exists and the user types in CC, CamelCase should be proposed.
- Identifiers that begin with an underscore should have a lower relevance than those that do not.
- Function completion should check if `(` already exists. If it does, do not insert `(`, if it does not, insert it.
was (Author: istewart):
- Identifiers completion should also support CamelCase, i.e. if the identifier CamelCase exists and the user types in CC, CamelCase should be proposed.
- Identifiers that begin with an underscore should have a lower relevance than those that do not.
> Create Identifier Completion Engine
> -----------------------------------
>
> Key: ERT-66
> URL: https://issues.jboss.org/browse/ERT-66
> Project: Eclipse Release Train
> Issue Type: Sub-task
> Components: JSDT
> Reporter: Ian Stewart-Binks
> Assignee: Ian Stewart-Binks
>
> When a user invokes code completion, a set of useful identifier should be suggested to them. These identifiers should only be identifiers that are visible within the current scope from the current file. This should first support identifiers using ES5 keywords, and be extensible enough for ES6 keywords to fit in later on. Function identifiers from the current file and scope should be included as well.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21846) Deploy image name validation fails to catch long name before submitting resource
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21846?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21846.
---------------------------------
Verified on nightly build of JBT with OpenShift plugin build B258.
> Deploy image name validation fails to catch long name before submitting resource
> --------------------------------------------------------------------------------
>
> Key: JBIDE-21846
> URL: https://issues.jboss.org/browse/JBIDE-21846
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Priority: Minor
> Fix For: 4.3.1.CR1
>
>
> The generated name for the image "saturnism/spring-boot-helloworld-ui" produced "spring-boot-helloworld-ui" which violates the max length for resource names. This is only an issue when the name is set by change the image but not editing the name directly in the UI. The validation was not being triggered.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month