Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OCPBUGS-23080: Add multiline support to template instantiation #14416

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

logonoff
Copy link
Member

Fixes:

https://issues.redhat.com/browse/OCPBUGS-23080
#13317

Analysis / Root cause:

<input type="text /> does not support multiline

Solution Description:

Add a button to toggle between multiline and single line

Screen shots / Gifs for design review:

Screencast.from.2024-10-18.11-14-55.mp4

Unit test coverage report:

n/a

Test setup:

Download the example template posted in the jira ticket comments and apply it using oc create -f ./template.yaml

Browser conformance:

  • Chrome
  • Firefox
  • Safari

@openshift-ci openshift-ci bot added the component/core Related to console core functionality label Oct 18, 2024
Copy link
Contributor

openshift-ci bot commented Oct 18, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: logonoff
Once this PR has been reviewed and has the lgtm label, please assign vikram-raj for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the kind/i18n Indicates issue or PR relates to internationalization or has content that needs to be translated label Oct 18, 2024
@logonoff logonoff force-pushed the OCPBUGS-23080-template-text-toggle branch from 09daeb8 to 9faa0d0 Compare October 18, 2024 16:59
@webknjaz
Copy link

webknjaz commented Oct 18, 2024

Analysis / Root cause:
<input type="text /> does not support multiline

@logonoff I think that's only a part of the cause. Have you checked if the result shows up as a secret? Your recording does not demonstrate looking up the saved value to verify that it's been saved the same.

IIRC, When I tried using DevTools to modify that input to a <textarea>, it was corrupting the input, making it single-line somewhere in the backend. Could you make sure that isn't happening?

@logonoff
Copy link
Member Author

Analysis / Root cause:
<input type="text /> does not support multiline

@logonoff I think that's only a part of the cause. Have you checked if the result shows up as a secret? Your recording does not demonstrate looking up the saved value to verify that it's been saved the same.

IIRC, When I tried using DevTools to modify that input to a <textarea>, it was corrupting the input, making it single-line somewhere in the backend. Could you make sure that isn't happening?

It seems to be working fine:

image

@logonoff logonoff changed the title OCPBUGS-23080; #13317: Add multiline support to template instantiation OCPBUGS-23080: Add multiline support to template instantiation Oct 18, 2024
@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. labels Oct 18, 2024
@openshift-ci-robot
Copy link
Contributor

@logonoff: This pull request references Jira Issue OCPBUGS-23080, which is invalid:

  • expected the bug to target the "4.18.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Fixes:

https://issues.redhat.com/browse/OCPBUGS-23080
#13317

Analysis / Root cause:

<input type="text /> does not support multiline

Solution Description:

Add a button to toggle between multiline and single line

Screen shots / Gifs for design review:

Screencast.from.2024-10-18.11-14-55.mp4

Unit test coverage report:

n/a

Test setup:

Download the example template posted in the jira ticket comments and apply it using oc create -f ./template.yaml

Browser conformance:

  • Chrome
  • Firefox
  • Safari

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Oct 18, 2024
@logonoff
Copy link
Member Author

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@logonoff: This pull request references Jira Issue OCPBUGS-23080, which is invalid:

  • expected the bug to target the "4.18.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@logonoff
Copy link
Member Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Oct 18, 2024
@openshift-ci-robot
Copy link
Contributor

@logonoff: This pull request references Jira Issue OCPBUGS-23080, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.18.0) matches configured target version for branch (4.18.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @yapei

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested a review from yapei October 18, 2024 17:23
@webknjaz
Copy link

It seems to be working fine:

image

Thanks for checking. I'll make sure to ask the instance admins to upgrade once this is released and report back in case of any issues.

@logonoff
Copy link
Member Author

/cc @vikram-raj for review

Copy link
Contributor

openshift-ci bot commented Oct 18, 2024

@logonoff: GitHub didn't allow me to request PR reviews from the following users: for, review.

Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

/cc @vikram-raj for review

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Copy link
Contributor

openshift-ci bot commented Oct 18, 2024

@logonoff: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/core Related to console core functionality jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. kind/i18n Indicates issue or PR relates to internationalization or has content that needs to be translated
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants