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

Fix a confusing Regex in the Compose webpage #4852

Merged
merged 1 commit into from May 21, 2022
Merged

Conversation

cortinico
Copy link
Member

The default was not accurate + the suggested regex was more complicated than needed. I'm fixing it.

@codecov
Copy link

codecov bot commented May 21, 2022

Codecov Report

Merging #4852 (a00fb57) into main (ee2e9a0) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main    #4852   +/-   ##
=========================================
  Coverage     84.75%   84.75%           
  Complexity     3431     3431           
=========================================
  Files           491      491           
  Lines         11280    11280           
  Branches       2078     2078           
=========================================
  Hits           9560     9560           
  Misses          673      673           
  Partials       1047     1047           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ee2e9a0...a00fb57. Read the comment docs.

@schalkms schalkms added this to the 1.21.0 milestone May 21, 2022
@schalkms schalkms merged commit 486c894 into main May 21, 2022
@schalkms schalkms deleted the nc/fix-compose-regex branch May 21, 2022 21:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants