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

[BEAM-12607] - Copy Code Snippet copies html tags #15611

Closed
wants to merge 11 commits into from
Closed

[BEAM-12607] - Copy Code Snippet copies html tags #15611

wants to merge 11 commits into from

Conversation

fernando-wizeline
Copy link
Contributor

Hitting the "copy to clipboard" button copies the snippet with all the html formatting.
By using the innerText instead of the innerHTML property, we were able to get the actual text without the HTML code.

@pabloem is this something you can help me to review?

Thanks!

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

  • [ x] Choose reviewer(s) and mention them in a comment (R: @username).
  • [ x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
  • Update CHANGES.md with noteworthy changes.
  • If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

ValidatesRunner compliance status (on master branch)

Lang ULR Dataflow Flink Samza Spark Twister2
Go --- Build Status Build Status Build Status Build Status ---
Java Build Status Build Status
Build Status
Build Status
Build Status
Build Status
Build Status
Build Status
Build Status
Build Status
Build Status
Build Status
Build Status
Build Status
Build Status
Build Status
Python --- Build Status
Build Status
Build Status
Build Status
Build Status
Build Status Build Status ---
XLang Build Status Build Status Build Status Build Status Build Status ---

Examples testing status on various runners

Lang ULR Dataflow Flink Samza Spark Twister2
Go --- --- --- --- --- --- ---
Java --- Build Status
Build Status
Build Status
--- --- --- --- ---
Python --- --- --- --- --- --- ---
XLang --- --- --- --- --- --- ---

Post-Commit SDK/Transform Integration Tests Status (on master branch)

Go Java Python
Build Status Build Status Build Status
Build Status
Build Status

Pre-Commit Tests Status (on master branch)

--- Java Python Go Website Whitespace Typescript
Non-portable Build Status
Build Status
Build Status
Build Status
Build Status
Build Status Build Status Build Status Build Status
Portable --- Build Status Build Status --- --- ---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.

GitHub Actions Tests Status (on master branch)

Build python source distribution and wheels
Python tests
Java tests

See CI.md for more information about GitHub Actions CI.

Copy link
Contributor

@aromanenko-dev aromanenko-dev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the fix, @fernando-wizeline ! I tested with staged version and it works for me on Mac.

In the same time, could you avoid merge commits and just rebase your feature branch with a fix commit on top of master branch? Thanks!

@pabloem
Copy link
Member

pabloem commented Sep 29, 2021 via email

@fernando-wizeline
Copy link
Contributor Author

Thanks for the fix, @fernando-wizeline ! I tested with staged version and it works for me on Mac.

In the same time, could you avoid merge commits and just rebase your feature branch with a fix commit on top of master branch? Thanks!

Hi @aromanenko-dev ! I'm trying to squash my commits, but the commits displayed here and the ones shown in my local branch differ by 5 "Merge branch 'apache:master' into master" commits. I see six here while in my local branch I see only one.
Any idea what might be occurring?
Thanks!

@aromanenko-dev
Copy link
Contributor

@fernando-wizeline Well, I guess it would be easier to re-create your feature branch (fernando-wizeline:BEAM-12607) from current master, commit your changes into this branch and push it again.

@fernando-wizeline
Copy link
Contributor Author

@fernando-wizeline Well, I guess it would be easier to re-create your feature branch (fernando-wizeline:BEAM-12607) from current master, commit your changes into this branch and push it again.

Great! Thanks for the suggestion @aromanenko-dev!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants