#267 | 2851394-267.patch | 208.51 KB | quietone |
|
#267 | diff-260-267.txt | 1.22 KB | quietone |
#260 | interdiff-258-260.txt | 6.32 KB | jungle |
#260 | 2851394-260.patch | 208.52 KB | jungle |
|
#258 | 2851394-258.patch | 214.84 KB | jungle |
|
#258 | interdiff-257-258.txt | 904 bytes | jungle |
#257 | interdiff-255-257.txt | 11.18 KB | jungle |
#257 | 2851394-257.patch | 214.81 KB | jungle |
|
#255 | 2851394-255.patch | 208.34 KB | anmolgoyal74 |
|
#247 | diff_reroll_2851394_238-247.txt | 49.69 KB | ankithashetty |
#247 | 2851394-247.patch | 207.46 KB | ankithashetty |
|
#238 | interdiff-2851394-236-238.txt | 1.28 KB | shaktik |
#238 | 2851394-238.patch | 209.23 KB | shaktik |
|
#237 | interdiff-2851394-234-236.txt | 4.76 KB | markdorison |
#236 | 2851394-236.patch | 208.19 KB | shaktik |
|
#234 | 225-234-interdiff.txt | 4.57 KB | mmatsoo |
#234 | 2851394-234.patch | 210.59 KB | mmatsoo |
|
#233 | 2851394-233.patch | 199.34 KB | Swapnil_Kotwal |
|
#229 | interdiff_225-229.txt | 30.14 KB | nitesh624 |
#229 | 2851394-229.patch | 195.54 KB | nitesh624 |
|
#225 | interdiff_223-225.txt | 4.57 KB | mmatsoo |
#225 | 2851394-225.patch | 215.79 KB | mmatsoo |
|
#224 | interdiff_223-224.txt | 4.57 KB | mmatsoo |
#224 | 2851394-224.patch | 230.93 KB | mmatsoo |
|
#223 | 2851394-223.patch | 210.59 KB | mrinalini9 |
|
#220 | interdiff_217-220.txt | 397 bytes | nitvirus |
#220 | 2851394-220.patch | 210.35 KB | nitvirus |
|
#217 | interdiff_214-217.txt | 711 bytes | ravi.shankar |
#217 | 2851394-217.patch | 210.96 KB | ravi.shankar |
|
#214 | interdiff_210-214.txt | 9.21 KB | ridhimaabrol24 |
#214 | 2851394-214.patch | 210.09 KB | ridhimaabrol24 |
|
#210 | 2851394-210.patch | 207.77 KB | ridhimaabrol24 |
|
#209 | interdiff_200-209.txt | 4.08 KB | ridhimaabrol24 |
#209 | 2851394-209.patch | 222.11 KB | ridhimaabrol24 |
|
#200 | interdiff-191-200.txt | 810 bytes | jungle |
#200 | 2851394-200.patch | 222.11 KB | jungle |
|
#191 | 2851394-191.patch | 222.9 KB | jungle |
|
#187 | Screenshot at 2019-11-15 11-16-10.png | 191.72 KB | shimpy |
#186 | grammar-indefinite-articles-2851394-186.patch | 224.48 KB | shashikant_chauhan |
|
#185 | Screenshot at 2019-11-14 15-34-35.png | 147.03 KB | shimpy |
#183 | grammar-indefinite-articles-2851394-183.patch | 224.94 KB | shashikant_chauhan |
|
#182 | Failure Message.png | 216.56 KB | shubham.prakash |
#176 | interdiff-163_176.txt | 2.4 KB | wolffereast |
#176 | grammar-indefinite-articles-2851394-176.patch | 229.4 KB | wolffereast |
|
#174 | interdiff.txt | 1.14 KB | amit.drupal |
#174 | grammar-indefinite-articles-2851394-174.patch | 233.26 KB | amit.drupal |
|
#173 | grammar-indefinite-articles-2851394-173.patch | 235.73 KB | wolffereast |
|
#172 | grammar-indefinite-articles-2851394-172.patch | 235.74 KB | wolffereast |
|
#171 | interdiff_163-171.txt | 2.4 KB | wolffereast |
#171 | grammar-indefinite-articles-2851394-171.patch | 235.75 KB | wolffereast |
|
#163 | grammar-indefinite-articles-2851394-163.patch | 227.03 KB | wolffereast |
|
#157 | interdiff_147-157.txt | 1.96 KB | kostyashupenko |
#157 | grammar-indefinite-articles-2851394-157.patch | 204.85 KB | kostyashupenko |
|
#147 | interdiff-144-147.txt | 1.92 KB | oknate |
#147 | grammar-indefinite-articles-2851394-147.patch | 206.43 KB | oknate |
|
#144 | grammar-indefinite-articles-2851394-144.patch | 206.65 KB | oknate |
|
#144 | interdiff-143-144.txt | 2.39 KB | oknate |
#143 | interdiff-133-143.txt | 3.29 KB | oknate |
#143 | grammar-indefinite-articles-2851394-143.patch | 205.57 KB | oknate |
|
#133 | grammar-indefinite-articles-2851394-133.patch | 202.28 KB | oknate |
|
#132 | interdiff-131-132.txt | 12.55 KB | oknate |
#132 | grammar-indefinite-articles-2851394-132.patch | 201.88 KB | oknate |
|
#131 | grammar-indefinite-articles-2851394-131.patch | 189.94 KB | oknate |
|
#127 | fix_grammar-2851394-127.patch | 298.73 KB | savkaviktor16@gmail.com |
|
#120 | interdiff_119-120.txt | 5.42 KB | tanc |
#120 | fix_grammar-2851394-120.patch | 191.6 KB | tanc |
|
#119 | interdiff_113-119.txt | 9.78 KB | tanc |
#119 | fix_grammar-2851394-119.patch | 191.6 KB | tanc |
|
#118 | Error.png | 77.33 KB | Dinesh18 |
#113 | fix_grammar-2851394-113.patch | 190.67 KB | martin_q |
|
#113 | interdiff_110-113.txt | 91.34 KB | martin_q |
#110 | fix_grammar-2851394-110.patch | 263.66 KB | dimaro |
|
#110 | interdiff_107-110.txt | 976 bytes | dimaro |
#109 | image.png | 34.54 KB | mahtab_alam |
#107 | 2851394-107.patch | 264.11 KB | MerryHamster |
|
#104 | 2851394-104.patch | 276.74 KB | MerryHamster |
|
#100 | interdiff_97-100.txt | 6.8 KB | leolandotan |
#100 | 2851394-100.patch | 289.03 KB | leolandotan |
|
#97 | interdiff-88-97.txt | 4.07 KB | swarad07 |
#97 | 2851394-97.patch | 296.51 KB | swarad07 |
|
#95 | 2851394-94.patch | 298.15 KB | swarad07 |
|
#95 | interdiff-88-94.txt | 5.55 KB | swarad07 |
#89 | patch_result_core.png | 26.79 KB | Venkatesh Rajan.J |
#88 | 2851394-88.patch | 294.9 KB | jofitz |
|
#88 | interdiff-86-88.txt | 1.21 KB | jofitz |
#86 | 2851394-86.patch | 296.11 KB | jofitz |
|
#84 | patch_error_2.png | 113.5 KB | Venkatesh Rajan.J |
#84 | patch_error_1.png | 64.3 KB | Venkatesh Rajan.J |
#79 | fix_grammar_a_to_an-2851394-79.patch | 357.97 KB | hgunicamp |
|
#79 | interdiff-2851394-79.txt | 1.19 KB | hgunicamp |
#78 | interdiff-75-78.txt | 1.09 KB | gaurav.kapoor |
#78 | fix_grammar_a_to_an-2851394-78.patch | 359.47 KB | gaurav.kapoor |
|
#75 | fix_grammar_a_to_an-2851394-75.patch | 358.52 KB | hgunicamp |
|
#75 | interdiff-2851394-75.txt | 175.61 KB | hgunicamp |
#73 | fix_grammar_a_to_an-2851394-73.patch | 280.08 KB | hgunicamp |
|
#73 | interdiff-2851394-73.txt | 55.69 KB | hgunicamp |
#70 | fix_grammar_a_to_an-2851394-70.patch | 216.99 KB | hgunicamp |
|
#70 | interdiff-2851394-70.txt | 3.12 KB | hgunicamp |
#69 | fix_grammar_a_to_an-2851394-66.patch | 216.99 KB | hgunicamp |
|
#69 | interdiff-2851394-66.txt | 3.12 KB | hgunicamp |
#69 | fix_grammar_a_to_an-2851394-66.patch | 216.99 KB | hgunicamp |
|
#69 | interdiff-2851394-66.txt | 3.12 KB | hgunicamp |
#63 | fix_grammar_a_to_an-2851394-63.patch | 129.03 KB | akashkrishnan01 |
|
#58 | error.png | 21.65 KB | lomasr |
#56 | 2851394-reroll.patch | 131.77 KB | tameeshb |
|
#54 | intediff.txt | 1.46 KB | tameeshb |
#54 | 2851394-reroll.patch | 131.77 KB | tameeshb |
|
#53 | 2851394-reroll.patch | 131.02 KB | tameeshb |
|
#53 | intediff.txt | 922 bytes | tameeshb |
#51 | after.png | 53.2 KB | lomasr |
#50 | fix_grammar_a_to_an-2851394-50.patch | 132.3 KB | dimaro |
|
#43 | fix_grammar_a_to_an-2851394-43.patch | 132.3 KB | jofitz |
|
#40 | interdiff-36-39.txt | 814 bytes | boaloysius |
#40 | fix_grammar_a_to_an-2851394-39.patch | 132.2 KB | boaloysius |
|
#38 | interdiff.txt | 814 bytes | Munavijayalakshmi |
#38 | fix_grammar_a_to_an-2851394-38.patch | 132.2 KB | Munavijayalakshmi |
|
#36 | fix_grammar_a_to_an-2851394-36.patch | 146.03 KB | GoZ |
|
#34 | fix_grammar_a_to_an-2851394-34.patch | 146.3 KB | GoZ |
|
#27 | fix_grammar_a_to_an-2851394-27.patch | 145.92 KB | GoZ |
|
#25 | interdiff-2851394-22-25.txt | 44.52 KB | GoZ |
#25 | fix_grammar_a_to_an-2851394-25.patch | 145.92 KB | GoZ |
|
#23 | interdiff-17-22.txt | 576 bytes | tameeshb |
#22 | 2851394-22.patch | 89.29 KB | tameeshb |
|
#17 | fix_grammar_a_to_an-2851394-17.patch | 98.19 KB | GoZ |
|
#17 | interdiff-2851394-15-17.txt | 2.01 KB | GoZ |
#16 | fix_grammar_a_to_an-2851394-15.patch | 96.33 KB | GoZ |
|
#16 | interdiff-2851394-2-15.txt | 38.43 KB | GoZ |
#2 | fix_grammar_a_to_an-2851394-2.patch | 54.24 KB | GoZ |
|
Comments
Comment #2
GoZ CreditAttribution: GoZ at Centarro commentedComment #3
gmaltoni CreditAttribution: gmaltoni at CI&T commentedComment #4
gmaltoni CreditAttribution: gmaltoni at CI&T commentedI applied the patch and it worked cleanly.
Comment #5
GoZ CreditAttribution: GoZ at Centarro commentedThanks @gmaltoni.
What's about the grammar fixes ? I'm not a english native so if someone could review i don't make mistakes that will be great.
Thanks
Comment #6
cilefen CreditAttribution: cilefen commentedComment #7
GoZ CreditAttribution: GoZ at Centarro commented@cilefen what do you mean by "needs work" ?
If it's related to #2574981: Fix grammar ("an URL" should be "a URL") and consistent use of URL (not "url" / "Url") in documentation only, part 1, i don't touch to 'Url' to let this issue which has anteriority continue discussion and patch them.
Comment #8
cilefen CreditAttribution: cilefen commentedI set it to needs work because of your #5 comment.
Comment #9
cilefen CreditAttribution: cilefen commentedAlso, how can a reviewer know that all of them are fixed in a given patch? If you have a repeatable way you used to find them it will help to mention that in the issue summary.
Comment #10
GoZ CreditAttribution: GoZ at Centarro commentedThe only way i find was to search with regex in comments: " [aA] [aeiou]" and for each, define if a or an should be used.
I keep 'a' for sentences designing a name like 'a EntityType object'.
I move it to review unless someone see a missing sentence or a wrong one.
Comment #11
cilefen CreditAttribution: cilefen commentedOh sorry for #6 - I meant "needs review". 'a EntityType object' should be 'an'.
Comment #12
cilefen CreditAttribution: cilefen commentedGoZ: please share the regex you used, so reviewers can evaluate that all files and all possible cases were hit.
Comment #13
GoZ CreditAttribution: GoZ at Centarro commentedI use regex from #10 in IDE like PhpStorm and look at comments results.
I'll add to patch every sentences corresponding to 'a EntityType object'.
Comment #14
GoZ CreditAttribution: GoZ at Centarro commentedRemove u from regex, and use regex as non case sensitive: " [a] [aeio]"
Comment #15
cilefen CreditAttribution: cilefen commentedSee my comment on #2574981-79: Fix grammar ("an URL" should be "a URL") and consistent use of URL (not "url" / "Url") in documentation only, part 1
Are you catching multiline instances like?:
Comment #16
GoZ CreditAttribution: GoZ at Centarro commentedI have been quick in previous comment. Regex is better like " a [aeio]".
Here is patch with #13 changes + missings
Comment #17
GoZ CreditAttribution: GoZ at Centarro commentedYou are right, here is regex to check new lines : " a *\n[ \*/]*[aeio]"
+ 1 missing line.
Comment #18
cilefen CreditAttribution: cilefen commentedPlus this issue should also do the opposite: 'an' to 'a'.
Edited: patch/issue
Comment #20
bleen CreditAttribution: bleen at NBCUniversal commentedThis change makes the comment longer than 80 chars ... you should break the last work to a new line
Other than that, this is RTBC from me
Comment #21
bleen CreditAttribution: bleen at NBCUniversal commentedComment #22
tameeshb CreditAttribution: tameeshb at Google Summer of Code commentedApplying correction from #20
Comment #23
tameeshb CreditAttribution: tameeshb at Google Summer of Code commentedInterdiff attached
Comment #24
GoZ CreditAttribution: GoZ at Centarro commentedThanks @tameeshb
Still have to work on #18
Comment #25
GoZ CreditAttribution: GoZ at Centarro commentedMake a new pass with regex " a[^a-z]+[aeio]" for a to an so i can find words preceded by a non alphabetical character like 'a $element'.
Replace every 'an' to 'a' found with regex " an[^a-z]+[b-df-gj-np-qz]".
For acronyms, i take care of the pronunciation of the first letter.
If in doubt, i take a look at ngrams tool : https://books.google.com/ngrams/graph?content=a+html%2Can+html&year_star...
Comment #27
GoZ CreditAttribution: GoZ at Centarro commentedreroll
Comment #28
swarad07Looks good. Reviewed it manually.
Comment #29
xjmGood sleuthing and thanks for documenting how you created and reviewed the patch. #25 is especially helpful.
I thought about whether we could create a coder rule to detect this (in order to meet https://www.drupal.org/core/scope#coding-standards) but since it depends on the pronunciation and on whether the following word is an acronym, any rule would have false positives.
Since this is a grammar fix that can disrupt a lot of other patches, it's the sort of change we make during our release candidate phases. So, I'm postponing it for now and marking it as an RC target. The RC phase begins after March 1.
Comment #30
xjmOkay, we can look at this again during RC. I'll send a retest. The patch will probably need to be recreated.
Comment #32
xjmYep. Let's recreate a new patch using the instructions in #25, rather than trying to reroll the current one. Thanks!
Comment #33
prash_98 CreditAttribution: prash_98 commentedShould we make the changes in #25 or do the whole thing again i.e each and every change.
Comment #34
GoZ CreditAttribution: GoZ at Centarro commentedComment #36
GoZ CreditAttribution: GoZ at Centarro commentedSorry for that
Comment #37
Munavijayalakshmi CreditAttribution: Munavijayalakshmi at Valuebound commentedLine exceeding 80 characters.
Comment #38
Munavijayalakshmi CreditAttribution: Munavijayalakshmi at Valuebound commentedComment #40
boaloysius CreditAttribution: boaloysius as a volunteer commentedas #38 failed
Comment #41
boaloysius CreditAttribution: boaloysius as a volunteer commentedComment #43
jofitz CreditAttribution: jofitz at ComputerMinds commentedRe-rolled.
Comment #45
boaloysius CreditAttribution: boaloysius as a volunteer commentedComment #46
jofitz CreditAttribution: jofitz at ComputerMinds commented@boaloysius I'm afraid you can't set to RTBC because you have contributed a patch to this issue.
Comment #47
darius.restivan CreditAttribution: darius.restivan commentedChecked, everything seems ok.
Comment #48
darius.restivan CreditAttribution: darius.restivan commentedComment #50
dimaro CreditAttribution: dimaro at La Drupalera by Emergya commentedRerolled #43
Simple rebase fixed it.
Comment #51
lomasr CreditAttribution: lomasr at gai Technologies Pvt Ltd for gai Technologies Pvt Ltd commentedApplied the patch in #50. Worked fine for 8.3.x
For 8.4.x I got this error
Comment #52
boaloysius CreditAttribution: boaloysius as a volunteer and at Google Summer of Code commentedComment #53
tameeshb CreditAttribution: tameeshb at Google Summer of Code commentedRerolled from changes in 8.4, should work on 8.4 now.
Comment #54
tameeshb CreditAttribution: tameeshb at Google Summer of Code commentedReroll Patch redone, previous one had one thing missing also, this must be tested against 8.4.x but it's option isn't here to test with.
Might fail with 8.3.x
Comment #55
tameeshb CreditAttribution: tameeshb at Google Summer of Code commentedComment #56
tameeshb CreditAttribution: tameeshb at Google Summer of Code commentedTest against 8.4.x
Comment #58
lomasr CreditAttribution: lomasr at gai Technologies Pvt Ltd for gai Technologies Pvt Ltd commentedTested on 8.4.x, got an error please see the screen.
Comment #59
dimaro CreditAttribution: dimaro at La Drupalera by Emergya commented@lomasr I tried to replicate the error, however using "git apply" all looks good for me and I can not reproduce that.
Comment #60
akashkrishnan01 CreditAttribution: akashkrishnan01 commentedPatch #56 works fine for me too.
Comment #61
akashkrishnan01 CreditAttribution: akashkrishnan01 at Google Summer of Code commentedComment #63
akashkrishnan01 CreditAttribution: akashkrishnan01 at Google Summer of Code commentedSince the previous patch was changing a few file which is not included in a basic Drupal core site, so removed them and re-rolled with a new patch.
Comment #64
akashkrishnan01 CreditAttribution: akashkrishnan01 at Google Summer of Code commentedWorks fine for me. Let the bot give it a try now.
Comment #65
hgunicamp CreditAttribution: hgunicamp at CI&T commentedTo make sure that I would be able to get all 'a [aeiou]' occurrences in comments I used the following command:
find . -type f \( -name '*.inc' -or -name '*.module' -or -name '*.php' \) -exec grep -e '\(\*\|\/\/\).*\b\(A\|a\) \$\?\([AEIOU]\|[aeiou]\)' {} \+ | wc -l
It show me that before applying the 'fix_grammar_a_to_an-2851394-63.patch' patch there were 1298 occurrences.
After applying the patch, it was reduced to 1162.
To help us find where these mistakes are we could use the following command.
find . -type f \( -name '*.inc' -or -name '*.module' -or -name '*.php' \) -exec grep --color=auto -e '\(\*\|\/\/\).*\b\(A\|a\) \$\?\([AEIOU]\|[aeiou]\)' {} \+
Comment #66
akashkrishnan01 CreditAttribution: akashkrishnan01 at Google Summer of Code commentedhgunicamp, keeping things you shared, I have corrected those wrong statements. Thanks for your review. I have created a new patch with new changes as well.
Comment #67
akashkrishnan01 CreditAttribution: akashkrishnan01 at Google Summer of Code commentedComment #69
hgunicamp CreditAttribution: hgunicamp at CI&T commentedI tried to solve this problem as "dropping down dominoes pieces" using the 'sed' command, but I was able to reduce to 963 occurrences. The chain reaction was not so explosive as I thought.
The command I used was:
sed -i 's/\(\*\|\/\/\)\(.*\) \(A\|\a\) \([AEIOU]\|[aeiou]\)/\1\2 \3n \4/g' $(find . -type f \( -name '*.inc' -or -name '*.module' -or -name '*.php' \) -exec grep -e '\(\*\|\/\/\).*\b\(A\|a\) \$\?\([AEIOU]\|[aeiou]\)' {} \+ | cut -f1 -d':' | uniq )
This command bring back things like 'an url' or 'module An and B' that I fixed by hand.
Work is still need.
Comment #70
hgunicamp CreditAttribution: hgunicamp at CI&T commentedI'm sorry @akashkrishnan. I had not updated my page and used the same name you used for a patch (fix_grammar_a_to_an-2851394-66.patch). Let's upload again.
I'm using 'fix_grammar_a_to_an-2851394-70.patch'.
Comment #73
hgunicamp CreditAttribution: hgunicamp at CI&T commentedFollowing the "dropping down dominoes" strategy, I used a command to replace "an " for "a ". The command also avoids replacing expressions like "an (html|http|xml|xss)".
sed -i 's/\(\*\|\/\/\)\(.*\) \(A\|a\)n \([B-DF-HJ-NP-TV-Z]\|[b-df-hj-np-tv-z]\)/\1\2 \3 \4/;s/ \(A\|a\) \([Hh][Tt][Mm][Ll]\|[Xx][Mm][Ll]\|[Hh][Tt][Tt][Pp]\|[Xx][Ss][Ss]\)/ \1n \2/g' $(find . -type f \( -name '*.inc' -or -name '*.module' -or -name '*.php' \) -exec grep -e '\(\*\|\/\/\).* \(A\|a\)n \([B-DF-HJ-NP-TV-Z]\|[b-df-hj-np-tv-z]\)' {} \+ | cut -f1 -d':' | uniq)
The command
find . -type f \( -name '*.inc' -or -name '*.module' -or -name '*.php' \) -exec grep -e '\(\*\|//\).* \(A\|a\) \([AEIOU]\|[aeiou]\)' {} \+ | grep -v -e '\(A\|a\) [Uu][Rr][Ll]' | wc -l
Shown me the there are 646 "a " remaining occurrences.
Comment #74
nicrodgersI've just done a very quick skim review of the first couple of changes in the patch in #73, and it includes a lot of unnecessary changes that actually change the sentence from correct to incorrect. For example:
"A user" is correct.
"A one-dimensional" is correct.
"A UNIX timestamp" is correct
Comment #75
hgunicamp CreditAttribution: hgunicamp at CI&T commentedThanks @nicrodgers.
I found and corrected the mistakes you pointed.
I made another search excluding expressions like "a user, a url, a one, a unix, an html, an xml, an http, an xss".
Let me know if there are any more collateral damages from my approach.
Comment #77
gaurav.kapoor CreditAttribution: gaurav.kapoor at OpenSense Labs commentedComment #78
gaurav.kapoor CreditAttribution: gaurav.kapoor at OpenSense Labs commentedComment #79
hgunicamp CreditAttribution: hgunicamp at CI&T commentedThanks @gaurav.kapoor for trying to fix my mess.
Actually the mistakes are in the commentaries of functions 'module_a_post_update_a' and 'module_a_post_update_b', where my patch replaced 'Module A update' for 'Module An update'.
Sending a patch to fix this collateral damage.
Comment #80
vegantriathleteI'll queue this up for this weekend's Drupalcamp Colorado and see about having somebody look at it on Sunday.
Comment #81
nicrodgers@vegantriathlete great! I think this would really benefit from a manual review and manual fix - the automated/bulk solutions seem to be creating more bugs than they are fixing.
Comment #83
Venkatesh Rajan.J CreditAttribution: Venkatesh Rajan.J as a volunteer and at DrupalPartners commentedComment #84
Venkatesh Rajan.J CreditAttribution: Venkatesh Rajan.J as a volunteer and at DrupalPartners commentedCould not apply patch #79 on Drupal 8.5.x, throws some errors while applying the patch.
Comment #85
cilefen CreditAttribution: cilefen at Institute for Advanced Study commentedHello Venkatesh Rajan.J:
Thank you for helping. In order that your support can be even more useful let me suggest the following. When a patch does not apply it is not necessary to post evidence (code screenshots are seldom needed). Instead add the tag "Needs reroll". It is even more helpful to reroll it, if you are comfortable doing so.
Thank you!
Comment #86
jofitz CreditAttribution: jofitz at ComputerMinds commentedRe-rolled. Including correcting from "an user", "an unique" and "an UID".
Comment #88
jofitz CreditAttribution: jofitz at ComputerMinds commentedFixed a couple of coding standards errors.
EDIT:
Unable to replicate the test failure locally(appears to have been a testbot fault).Comment #89
Venkatesh Rajan.J CreditAttribution: Venkatesh Rajan.J as a volunteer and at DrupalPartners commented@Jo Fitzgerald,
Thanks for the patch. It works well. PFA for the same.
Comment #91
dimaro CreditAttribution: dimaro commented@Venkatesh Rajan.J I think that we have to check again these occurrences.
The last patch before @cilefen categorized this issue as "Needs reroll" is from May 4.
Comment #92
Ivan Berezhnov CreditAttribution: Ivan Berezhnov as a volunteer and at Drupal Ukraine Community for Levi9 commentedComment #93
vegantriathleteComment #95
swarad07Attempting a patch reroll against 8.6.x...
Comment #97
swarad07Seems I left some code during conflict resolution in ConfirmDeleteMultiple.php. That was the only file with conflicts during rebase.
Comment #98
thatdamnqa CreditAttribution: thatdamnqa as a volunteer commentedThanks for this. Upon reviewing, I found a few items that need some more work eg the ones below. If you could fix these it would be much appreciated.
"A URI" is correct
Presuming it's pronounced "ex-or", then "an XOR" is correct
"A URI" is correct. This change has been made 8 times in this file, all are incorrect.
"A usability problem" is correct.
"A unified" is correct
"A Utility class" is correct
Comment #99
thatdamnqa CreditAttribution: thatdamnqa as a volunteer commentedComment #100
leolandotan CreditAttribution: leolandotan as a volunteer and at Promet Source commentedHi! I applied the fix mentioned in #98. Upon applying the patch to the latest 8.6.x code, `git apply` didn't work so I used `patch -p1` and had two rejects which are for core/lib/Drupal/Component/Gettext/PoStreamReader.php and core/modules/simpletest/src/AssertContentTrait.php. For core/lib/Drupal/Component/Gettext/PoStreamReader.php, I just manually added the changes from the patch while core/modules/simpletest/src/AssertContentTrait.php didn't need to be changed because a recent commit removed all the code inside this file as stated in it's docblock.
Hope everything is in order.
Comment #101
amietpatial CreditAttribution: amietpatial as a volunteer and at gai Technologies Pvt Ltd for gai Technologies Pvt Ltd commented@ leolando.tan I also faced same issue of apply patch but after applying it's working fine
Comment #102
bleen CreditAttribution: bleen at NBCUniversal commentedNOTE: This comment should in no way derail, bikeshed, delay, conflate, blow up, distract from this effort...
Once this is committed I wonder if there a way to add a build check to D.O. so that future patches are checked using similar REGEXes as were used here to warn (break build?) people about making the same mistake. It would be a shame to do this work so thoroughly only to have a future patch introduce the same mistakes a week later.
... If not, then isn't possible we are being overly thorough here? Why not just commit what we have and move on?
Just thinkin' about a possible followup
Comment #103
sayali_pd CreditAttribution: sayali_pd commentedThere wasn't any change required here. "An onerror" is the right usage. Please change it back
This should be "a HTTP request". Please make the required changes.
"a UTF-8 BOM" is the right usage. Please change this back.
This should be "a unicode" character. Please change this back
This should be changed to "The root URL, which has a URI scheme,host and an optional port"
"a UTF-8 string" is the right usage. Please change it back.
Please change this back to "a UTF-8 string"
Please change this to "a UTF-8 string" back. This would be the right usage.
This should be "A URI". Please change it back.
Please change this back to "a UTF-8 string".
Please change this back to "truncates a UTF-8-encoded" string
Please change this back to "An onerror attribute"
Please change this to "a URI"
Please change this back to "a UUID"
Please change this back to "a UUID"
This should be changed back to "a AccessManager instance"
"a UTF-8 string" would be the right usage. Please change it back.
Comment #104
MerryHamster CreditAttribution: MerryHamster at Skilld commentedFixed all items from #103
8.6 has many changes since the last patch so I have not added the interdiff file.
Comment #105
MerryHamster CreditAttribution: MerryHamster at Skilld commentedComment #107
MerryHamster CreditAttribution: MerryHamster at Skilld commented8.6 has many changes since the #100 patch, so #104 patch had fallen.
I recreated patch for current 8.6 and added all notes from #103
Comment #108
MerryHamster CreditAttribution: MerryHamster at Skilld commentedComment #109
mahtab_alam CreditAttribution: mahtab_alam at Valuebound commentedPatch #107 failed
Comment #110
dimaro CreditAttribution: dimaro at Ymbra commentedOne more time the patch no longer applies.
Rerolled #107
Comment #111
martin_qThere is a recurring problem with the correct usage of 'a/an' before 'http' because the pronunciation of the letter 'H' is disputed. Although many people do consider it to be pronounced /heɪtʃ/ (which would necessitate the article 'a'), the standard and far more widespread pronunciation is /eɪtʃ/ (requiring the article 'an'). Source: https://en.wikipedia.org/wiki/H#Name_in_English
Thus there are problems with this patch (as well as various other false positives), and with the list in #103. I'll reroll it...
Comment #113
martin_qRerolled 110, which reverts several things related to false positive 'a'/'an' issues, a few other wording problems and some comment line length issues (but only those line length issues that I spotted easily, possibly not a complete list).
(For the record, I'm a mother tongue (British) English speaker.)
Comment #114
martin_qComment #115
jpoesen CreditAttribution: jpoesen at Code Enigma commentedThanks @martin_q!
1.
--> should be constructs, no?
2.
--> I believe this should have been corrected to 'has been updated *and* there are no warnings'.
3.
--> while not exactly within the scope of this round of corrections, the error reads 'MySQL server has gone away', not 'had'.
4.
--> Should this not have been corrected to 'at least *one* item'?
5.
--> again strictly out of scope, but: incorrect word order, and pronoun issue.
--> suggestion: 'First create a user, then assign them a langcode'.
6.
--> As you indicated in comment #111, use 'an' before 'HTTP', so the above correction should be undone.
7.
--> Missing period at the end.
8.
--> should either be ', and ensure [...]' or ', ensuring [...]'
--> 'Do not limit *a* validation' sounds strange but might be correct if we are talking about individual, discrete validations, rather than 'all/any validation' to be skipped.
Comment #116
jpoesen CreditAttribution: jpoesen at Code Enigma commentedComment #117
Dinesh18 CreditAttribution: Dinesh18 as a volunteer commentedComment #118
Dinesh18 CreditAttribution: Dinesh18 as a volunteer commentedI tried applying the patch mentioned in #113. It throws an error.
We need reroll. Added the needs reroll tag.
Here is the error msg screenshot attached.
Comment #119
tancHere is a re-roll of #113, not including the changes suggested by @jpoesen.
There were a few changed file paths:
core/modules/editor/src/Tests/EditorAdminTest.php -> core/modules/editor/tests/src/Functional/EditorAdminTest.php
core/modules/editor/src/Tests/EditorLoadingTest.php -> core/modules/editor/tests/src/Functional/EditorLoadingTest.php
core/modules/system/src/Tests/System/HtaccessTest.php -> core/modules/system/tests/src/Functional/System/HtaccessTest.php
core/modules/system/src/Tests/System/ThemeTest.php -> core/modules/system/tests/src/Functional/System/ThemeTest.php
The text changes in core/tests/Drupal/Tests/BrowserTestBase.php did not apply and no longer exist (so not included in this patch).
The rest of the changes were line numbers.
Comment #120
tancIncludes suggested changes from @jpoesen in #115
Comment #121
tancComment #122
martin_qThanks, all. I agree with all of @jpoesen's points - these were all either due to me being too cautious about changing meaning of things I don't know about, or me reading the texts too quickly. And in the case of that "a HTML" I must just have been confused. Definitely 'an HTML"! :)
Comment #124
quietone CreditAttribution: quietone as a volunteer commentedRetesting the patch in #120 in 8.7.x
Comment #125
mayaslatinek6@gmail.com CreditAttribution: mayaslatinek6@gmail.com at Agiledrop - Your Trusted Drupal Teammates commentedCouldn't apply the patch provided in #120
Comment #126
quietone CreditAttribution: quietone as a volunteer commentedSince the patch no longer applies, tagging for reroll
Comment #127
savkaviktor16@gmail.com CreditAttribution: savkaviktor16@gmail.com at Skilld commentedRe-rolled
Comment #128
oknateThe drupal bot tester says the patch adds nine additional coding standard messages
Comment #129
quietone CreditAttribution: quietone as a volunteer commented@oknate is correct, there are coding standard errors that need to be fixed. Setting to NW.
Comment #130
oknateIt also looks like there's some unintentional changes/reversions in core/modules/tour/js/tour.es6.js and core/modules/quickedit/js/models/EntityModel.es6.js in #127.
Comment #131
oknateReroll with two small fixes (comments longer than 80 characters).
Comment #132
oknateAdding some more indefinite article fixes.
Comment #133
oknateComment #134
quietone CreditAttribution: quietone as a volunteer commentedLatest patch has all coding standards fixed, Thanks oknate.
Comment #135
volkswagenchickTagging for upcoming contribution days.
Comment #136
johnpicozziPatch applies cleanly and changes look good.
RTBC +1
Comment #137
pawandubey CreditAttribution: pawandubey as a volunteer and at TATA Consultancy Services commentedI have tested this patch#133 and working fine along with the coding standards.
Comment #138
samiullah CreditAttribution: samiullah at Srijan | A Material+ Company commentedComment #139
samiullah CreditAttribution: samiullah at Srijan | A Material+ Company commentedPatch Looks good
Comment #140
samiullah CreditAttribution: samiullah at Srijan | A Material+ Company commentedComment #142
alexpottFor me - at least according to the rules this conversion is wrong. When saying this out loud I would say "at-group annotation" so following the general rule from https://english.blogoverflow.com/2011/11/articles-a-vs-an/ - @group starts with a vowel sound and so should be an @group annotation. This why it is an HTML because saying H you say "aitch" which is starts with a vowel sound.
Note in core we have stuff like
And
So we're not consistent and this patch doesn't adjust any of this to be consistent.
Comment #143
oknateUpdated, I searched the codebase for "a @" and found a few that I think should be changed, based on Alex Pott's comment.
Comment #144
oknateAdding a few more changes. Not sure why I missed these in the last patch.
Comment #145
oknateComment #146
alexpottLooks like something crept in by mistake.
Comment #147
oknateFixing the "butterfingers" typo in #146, also making a change
- an (array of) SelectInterface(s)
+ a SelectInterface or an array of SelectInterfaces
I think the second way is clearer.
Comment #148
jcloys CreditAttribution: jcloys commentedComment #149
jcloys CreditAttribution: jcloys at Princeton University commentedReview and can confirm that the patch applies. One patch adds an where appropriate and the diff can show this appropriately.
Comment #150
pawandubey CreditAttribution: pawandubey as a volunteer and at TATA Consultancy Services commentedPatch looks good.
RTBC +1
Comment #151
jcloys CreditAttribution: jcloys at Princeton University commentedComment #153
alexpottRandom testbot fail.
Comment #155
pawandubey CreditAttribution: pawandubey as a volunteer and at TATA Consultancy Services commentedComment #156
quietone CreditAttribution: quietone as a volunteer commentedPatch in #147 no longer applies, needs a reroll.
Comment #157
kostyashupenkoComment #158
baikhoReviewing patch in #157 and everything seemed fine but looking at:
I think "Test acquiring a releasing lock with a long key (over 255 chars)." would be correct grammar? (I am not an english native speaker)
Comment #159
volkswagenchickComment #160
pawandubey CreditAttribution: pawandubey as a volunteer and at TATA Consultancy Services commentedPatch in #157 no longer applies, needs a reroll along with the suggestion in #158.
Comment #162
wolffereast CreditAttribution: wolffereast commentedI'm working on the reroll and change mentioned in 158
Comment #163
wolffereast CreditAttribution: wolffereast commentedI added some specificity to the original regex posted in #25.
For the a regex: updated to match only instances in comment lines and not match items followed by the word one (the word one came up as a false positive many times, this significantly culled the results).
(?:\*|//)[^\r\n]*\sa[^a-z.:]+(?!one)[aeio]
Similar update to the an regex, finding only items in comments and adding digits to the matched items as those occasionally need updates.
(?:\*|//)[^\r\n]*\san[^a-z.:]+[b-df-gj-np-qz0-9]
TestDiscoveryTest had more issues than just an a/an flip. I have updated the grammar to be more appropriate, but this might do better split out into a separate ticket.
Additional items that are likely outside the scope of this ticket:
an should precede consonants that sound as thought they start with a vowel. For example: an X-Files episode
This is a much more difficult thing the grep, so should probably be handled on a case by case basis in separate tickets as instances are discovered.
I didn't update anything outside of a comment or docblock with the exception of a test in TestDiscoveryTest. That text matches the doc block string that follows, so I updated both.
There is an issue with the comment in editor.admin.es6.js:670 that includes an a/an item but it needs more work. I will open a separate ticket for that one.
Comment #164
artis CreditAttribution: artis at Texas Creative commentedManually reviewed the patch as a native (american) english speak. Did not find any clear issues with the grammar or spelling on the relevant lines of code.
There is one situation with some gray area.
If the @ symbol is read as 'at' in front of @Translation then the update to 'an' in this patch is correct. However if the @ symbol should be ignored when read then it should go back to being preceded by 'a'. Don't have a strong inclination either way. Marking as RTBC. If someone strongly disagrees then the patch would need to be re-rolled with that one change.
Comment #165
oknateThis has grown to be a giant patch. +1 RTBC. Can we get this one in, and then going forward doing smaller patches for individual issues?
Comment #166
bleen CreditAttribution: bleen at NBCUniversal commentedgoing forward we should look to include the regex used here in the checks on all new patches... I'm not sure how to get that done (or how to even indicate that to the d.o. team) but if new patches had a failing "test" based on this then it would prevent similar issues in the future
Comment #167
oknatethat would be awesome, there are checks for php standards, maybe it could be added there, in /vendor/drupal/coder/coder_sniffer/Drupal/Sniffs/Commenting
Comment #168
artis CreditAttribution: artis commented+1 for that suggestion
Comment #169
pawandubey CreditAttribution: pawandubey as a volunteer and at TATA Consultancy Services commentedCompletely agree with @artis on the review part and the suggestion given by @oknate.
RTBC+1
Comment #170
wolffereast CreditAttribution: wolffereast commentedI agree that a test would be great but I think designing it will be quite a task because of the sheer volume of edge cases in the English language. Even with the updated regex I still had to comb through the returned list to ensure I didn't update anything incorrectly. I also see some holes in the existing version that would sneak through a test based on the current regex. For example it doesnt pick up any word following an 'a' that starts with a u. That incorrectly ignores words like 'unknown' which should use an instead of a, but doesn't incorrectly flag things like 'a unique'.
Well shoot, now that I looked for it I found an instance of the u edge case. I hate to do this, but I rerolled the patch and updated the a regex to catch the new item.
In addition to the addition of the un capture group I forced either a space or a line break after the captured a. That removed a bunch of false positives that were catching a followed by odd punctuation.
(?:\*|//)[^\r\n]*\sa[\s\r\n][^a-z.:]*(?:(?!one)[aeio]|un[b-df-hj-np-tv-z])
While I thought about it we also weren't catching the numbers 8, 11, 18, or anything in the 80s.
(?:\*|\/\/)[^\r\n]*\sa[\s\r\n][^a-z0-9.:]*(?:(11|18)[^0-9]|8[0-9]+|(?!onc?e)[aeio]|un[b-df-hj-np-tv-z])
And at this point I feel pretty confident that this is getting to the point where it is no longer maintainable.
Other items that would need to be caught:
I'm sure I'm missing more cases. Those cover most of the ~30 false positives I am seeing when I run the above on core.
Comment #171
wolffereast CreditAttribution: wolffereast commentedWoops, forgot the patch!
Comment #172
wolffereast CreditAttribution: wolffereast commentedOne of the files was moved in another update. Updated the patch to include the change. The interdiff is still essentially the same so I didn't regenerate that as well.
Comment #173
wolffereast CreditAttribution: wolffereast commentedAnother moved file breaking the patch. Hopefully this also fixes the CI issue. the 163-171 interdiff is still essentially correct.
Comment #174
amit.drupal CreditAttribution: amit.drupal as a volunteer and at Valuebound for Valuebound commentedAfter Review found some unused code.
Update #173
Comment #176
wolffereast CreditAttribution: wolffereast commented@amit.drupal good catch! That was my rookie mistake, some testing for a different ticket snuck its way into this patch. I went all the way back to the patch in 163 and used the updated regex to apply the additional changes. Attaching a new patch and an interdiff. I believe those additions were the reason for the CI issue
Comment #177
wolffereast CreditAttribution: wolffereast commentedGot a pass after removing my mistakes. moving to needs review
Comment #179
andyrandom CreditAttribution: andyrandom commentedLooks good to me, excellent attention to detail. This obviously took a lot of work.
I found two minor typos that persisted in lines that were updated. They're not specific to this issue (spelling mistakes rather than a/an discrepancies), but as long as we're diving this deep into the documentation it makes sense to add them.
This should say "and check"
Spelling "response" properly will re-break these lines.
Comment #180
Dinesh18 CreditAttribution: Dinesh18 as a volunteer commentedI tried to apply patch #176 but the patch is not applying properly and It is failing.
Comment #181
shubham.prakash CreditAttribution: shubham.prakash at OpenSense Labs commentedThe patch no longer applies and needs reroll.
Comment #182
shubham.prakash CreditAttribution: shubham.prakash at OpenSense Labs commentedComment #183
shashikant_chauhan CreditAttribution: shashikant_chauhan as a volunteer commentedRerolled the patch and added the changes mentioned in #179.
Comment #184
shashikant_chauhan CreditAttribution: shashikant_chauhan as a volunteer commentedComment #185
shimpyI tried applying #183. But failed to apply. Attaching screenshot as well.
Comment #186
shashikant_chauhan CreditAttribution: shashikant_chauhan as a volunteer commentedRemoved the extra space in a new patch which was added while rerolling the patch.
Comment #187
shimpyI tried applying patch #186 but failed to apply.
Comment #188
shashikant_chauhan CreditAttribution: shashikant_chauhan as a volunteer commented@shimpy, Don't be in a hurry.
Before applying any patch you should first check if you have the latest code on branch 8.9.x.
use command
git pull origin 8.9.x
then try applying the same patch again. I checked the patch is getting applied successfully.
Comment #189
shimpy@shashikant_chauhan
Thanks for reminding me to pull the latest 8.9 code. Patch got applied.
Comment #190
jungle#186 is broken
Comment #191
jungleRerolled from #186 and get .js files generated by run npm run build:js, not touched directly. (Updatd to IS) no css/.pcss.css file changes.
But run
npm run build:css
got one file change. I think this should be done by a separate issue.Comment #192
jungleComment #193
jungleComment #194
jungleUpdate IS: .post.css -> pcss.css
Comment #195
thallesThis issue already have three years and don't look me that been next to resolve, because involve several files, and this issue has no critical, so, maybe, can be best, to send small patches, that involve few files
Comment #197
jungle1 fail in #191 just because of
core/tests/Drupal/KernelTests/Core/Theme/ConfirmClassyCopiesTest.php
changed, and hash does not match. simply changing the file hash (md5) in the test does not fix it. The other tests will break. So options areI'd set back to needs review
Comment #198
jungleLet's postpone it or split it into small ones.
Comment #199
jungleComment #200
jungleAs Classy was removed in 9.x, and I have no idea how to fix the hash tests easily, so just reverted the change to core/themes/classy/templates/dataset/item-list--search-results.html.twig to get the tests passed and sizing the current window. we can fix it in a separate issue if necessary
Comment #202
jungleJust tested that the failed test passed on my local. It seems a random tests failure. Queued and check back later.
Comment #203
jungleComment #204
clayfreemanThis was quite an exhausting review, so let me know if I've missed anything or missed discussion on how some things should be handled.
This sentence is a bit clunky; is the content being opened in a dialog or an off-canvas dialog (or a dialog in an off-canvas dialog)?
following*
This line now breaks the 80 character wrap guide. Consider adjustment?
This really depends on how one pronounces
#
; "hashtag," "pound sign," or "octothorpe?"I believe "hashtag" or "pound sign" are most common; so this is probably fine.
This comment doesn't make complete sense in this context, as visibility isn't being verified.
Aside from that, it's much easier to read "If the field has at least one item, ..." rather than how it's currently written.
The grammar is a bit rough here; maybe "Ensure that a module which does not provide a module overview page is handled correctly."
If we expect "@" to be pronounced, this is fine, but if we just pronounce the annotation object, this needs to be fixed.
This is confusing at first. Might consider rewriting.
I'd rewrite to say:
Returns an ID that is guaranteed to be unique.
This can probably go either way, but I read this as "Constructs an Entity object" in my head (without the namespace).
Consider moving the parenthetical after the article-adjoining word: "In case an error (e.g. fatal) occurs ..."
Comment #205
dipakmdhrm CreditAttribution: dipakmdhrm as a volunteer and at QED42 commentedComment #206
dipakmdhrm CreditAttribution: dipakmdhrm as a volunteer and at QED42 commentedComment #207
shimpyComment #209
ridhimaabrol24 CreditAttribution: ridhimaabrol24 at Srijan | A Material+ Company for Drupal India Association commentedFixed suggestion given on #204
Comment #210
ridhimaabrol24 CreditAttribution: ridhimaabrol24 at Srijan | A Material+ Company for Drupal India Association commentedPatch uploaded for Drupal 9.1
Comment #211
jungleThanks @ridhimaabrol24!
Over 80 chars
Comment #212
ridhimaabrol24 CreditAttribution: ridhimaabrol24 at Srijan | A Material+ Company for Drupal India Association commentedThanks for the review @jungle. Will submit a patch after fixing these.
Comment #213
thallesLooks me that #210 needs reroll
Comment #214
ridhimaabrol24 CreditAttribution: ridhimaabrol24 at Srijan | A Material+ Company for Drupal India Association commentedFixed lines exceeding 80 chars as suggested in #211 and also re-rolled the patch. Please review.
Comment #215
thallesThanks @ridhimaabrol24!
Comment #216
quietone CreditAttribution: quietone as a volunteer commentedThis caught my eye. Searching the issue I found #115.8 suggesting a improvement.
Comment #217
ravi.shankar CreditAttribution: ravi.shankar at OpenSense Labs commentedThis patch might address comment #216.
Comment #218
mmatsoo CreditAttribution: mmatsoo commentedI was reviewing https://www.drupal.org/files/issues/2020-05-29/2851394-217.patch and noticed that the lines below are mistakenly changing "a" (correct) to "an" incorrect.
```
@@ -642,7 +642,7 @@ public function testDatelistWidget() {
$field_name = $this->fieldStorage->getName();
$field_label = $this->field->label();
- // Ensure field is set to a date only field.
+ // Ensure field is set to an date only field.
```
The original "// Ensure field is set to a date only field." is grammatically correct.
Comment #219
nitvirus CreditAttribution: nitvirus at Srijan | A Material+ Company commentedAsssigning this to myself
Comment #220
nitvirus CreditAttribution: nitvirus at Srijan | A Material+ Company commentedRemoving this code as per last comment
Comment #221
nitvirus CreditAttribution: nitvirus at Srijan | A Material+ Company commentedUnassigned this and changing the status to needs review.
Comment #222
jungleThanks, @nitvirus! But it's totally wrong based on the
interdiff
in #220Just need to revert the change below as #218 pointed. not REMOVE it from the patch file!
Comment #223
mrinalini9 CreditAttribution: mrinalini9 at Srijan | A Material+ Company for Drupal India Association commentedI have rerolled patch #217 as it's no longer applicable and also reverted changes as mentioned in #222, please review.
Comment #224
mmatsoo CreditAttribution: mmatsoo at Chromatic commentedI reviewed the patch from #223 and found some grammatical errors that I fixed in the patch I have added. Hopefully the interdiff tells that tale.
Otherwise I made it through the entire patch to confirm that the changes from "a" to "an" and vice versa now look good.
Comment #225
mmatsoo CreditAttribution: mmatsoo at Chromatic commentedOops, my last patch had junk in it that was not necessary. Re-rolled and added again, along with the same, but renamed interdiff.
Comment #226
mmatsoo CreditAttribution: mmatsoo at Chromatic commentedComment #227
quietone CreditAttribution: quietone as a volunteer commented@mmatsoo, thanks for updating the patch.
I have only looked at the interdiff and found that, sadly, all of the changes are out of scope, that is they are doing things other than change 'a' to 'an'. Looking back I see that in #224 that grammatical errors were fixed. While they may be correct they need to done in a separate issue so that so the change can be made throughout core. There will be policy about that on d.o but I can't find it right now.
Sorry, this looks out of scope.
This word change is made in several places.
This too looks out of scrope
Not sure why this was changed. The line was 80 characters long. Am I not seeing something?
Comment #228
nitesh624Assigning to myself and i will work on this today
Comment #229
nitesh624Removed the out of scrope changes in #225
Comment #230
nitesh624Comment #231
nitesh624Comment #232
mmatsoo CreditAttribution: mmatsoo at Chromatic commented@quietone Thanks for the explanation about things being out-of-scope. I guess I got all caught up fixing other things I noticed along the way.
Regarding your question about line length, I corrected the spelling of "response". (It originally was "resonse" and I wondered if it was intentionally misspelled to keep the line length at 80 characters.) That pushed the line even longer, so I moved "InsertCommand" to a new line.
Comment #233
Swapnil_Kotwal CreditAttribution: Swapnil_Kotwal at Asentech LLC commentedComment #234
mmatsoo CreditAttribution: mmatsoo at Chromatic commented@nitesh624 The interdiff for your patch has a lot of stuff not involved with reversing the changes I made in #225
I have re-rolled my patch to reverse the out-of-scope changes I introduced in #225
It should now be back to the state of where @mrinalini9 had it in #223
The interdiff shows the difference from 225 to 234. It adds back grammatical errors, but they are considered out-of-scope for this issue so back in they go.
Comment #235
shaktikThe patch is no longer to apply, so I am working on it.
Comment #236
shaktikrerolled patch #234, Kindly check.
Comment #237
markdorisonI created an interdiff between #234 and #236. Of the new changes that were added, a number of which are not valid.
I have updated the ticket description to note that the selection of a/an is not based on the succeeding letter, but the phonetics of the following word. For example, "an HTML page" is correct, despite "HTML" beginning with an "H" since we pronounce it "aitch tee em el" not "haitch tee em el."
Comment #238
shaktikHi @markdorison,
Thanks for the review.
I think you have created reverse direction interdiff patch because already updated on "an HTML page" and
in 234 and 236 patch. I have fixed new thing. Kindly check.
Comment #239
shaktikComment #240
sanjayk CreditAttribution: sanjayk as a volunteer and at Srijan | A Material+ Company for Drupal India Association commentedComment #241
sanjayk CreditAttribution: sanjayk as a volunteer and at Srijan | A Material+ Company for Drupal India Association commentedPatch applied successfully and also pass test cases.
Comment #242
asishsajeev CreditAttribution: asishsajeev at Zyxware Technologies commentedComment #243
asishsajeev CreditAttribution: asishsajeev at Zyxware Technologies commentedThe Patch applied successfully. Thanks for the patch.
Comment #244
asishsajeev CreditAttribution: asishsajeev at Zyxware Technologies commentedComment #245
jungleNeeds reroll.
Comment #246
ankithashettyComment #247
ankithashettyRe-rolled the patch in #238... Kindly review.
Thank you!
Comment #248
sarvjeetsingh CreditAttribution: sarvjeetsingh as a volunteer and at QED42 for Drupal India Association commentedPatch applied cleanly to the latest pull of 9.1. There were no errors found related to the use of 'a' and 'and' in the submitted patch. Moving it to RTBC.
Comment #249
catchThis touches a lot of files which is likely to be disruptive for other patches, so let's aim to schedule commit towards the end of the 8.1.x beta.
Comment #251
Pasqualle8.1.0 beta?
Comment #252
PasqualleComment #253
xjmComment #254
longwaveWe are in the beta window now, so it would be a good time to get this rerolled again and then reviewed if we are to get this done for 9.1.0.
Comment #255
anmolgoyal74 CreditAttribution: anmolgoyal74 at OpenSense Labs for DrupalFit commentedRe-rolled
Comment #256
longwaveThis is looking really good, lots of little fixes here. I read through the whole patch and noted a handful of minor problems:
Maybe out of scope but there is a typo here - $bath_url should be $base_url.
Not sure this needs "a" or "an", it doesn't read well either way.
This should be "Ensure that a module which..."
I think this one should actually be "..in an iframe".
I think "a" is correct here? We could perhaps also drop the @FieldType bit and just say "...assign to a map field".
I think this could just say "In case a fatal error occurs...", the "e.g." part is out of place and I'm not sure what other type of error might happen to cause this - it doesn't give any hints.
Comment #257
jungleAddressing #256
be wrapped in an @Translation()
, omitted an or a in 3 occurrences -- Could it be be wrapped in the @Translation(), the is omittable?#256.4
More occurrences replaced.
Comment #258
jungleWrapped too early, addressing
Comment #259
longwave#257.1 - "be wrapped in @Translation()" is correct, there is no need for "the" here.
However, I didn't realise there were other instances of "frame" instead of "iframe", changing all of those here might be out of scope, especially in user-facing messages?
Comment #260
jungle#259, good point, thanks! Let me revert it, and let's do it in a separate issue, as it is UI-related. Filing the followup next.
Comment #261
jungleOpened #3182122: Change "in a frame" involving "oEmbed" to "in an iframe"
Comment #262
longwaveThanks, this looks good now - let's try to get this in the beta window.
Comment #264
jungleLooks like a random fail, re-queued.
Comment #265
gaurav.kapoor CreditAttribution: gaurav.kapoor at Axelerant for Drupal India Association commentedComment #266
catchRemoving 'needs scheduling' since we're in beta right now. Needs a re-roll though.
Comment #267
quietone CreditAttribution: quietone as a volunteer commentedSimple reroll. Patch failed to apply to ConfigExportImportUITest.php.
Comment #268
quietone CreditAttribution: quietone as a volunteer commentedComment #269
longwaveBeat me to it, I arrived at the same patch.
Something about this issue makes d.o super slow for me, maybe just the sheer number of comments though.
Comment #271
catchCommitted/pushed to 9.2.x and cherry-picked to 9.1.x, thanks!