GitLab CI reports PHP_CodeSniffer warnings/errors which should be fixed.
| Comment | File | Size | Author |
|---|---|---|---|
| #12 | cs-issues-3292463-12.patch | 19.39 KB | sidharth_soman |
| #9 | coding-standard-3292463-9.patch | 19.35 KB | urvashi_vora |
| #5 | fixing-coding-standard-3292463-5.patch | 18.99 KB | nitin_lama |
| #2 | phpcs-drupal-coding-standard-3292463-2.patch | 20.77 KB | Harsh panchal |
Issue fork sharpspring_crm-3292463
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
Harsh panchal commentedI have fixed this issue and providing a patch.
Comment #3
shamir.vs commentedI applied patch #2. one file failed to apply the patch. Can you please check
patching file sharpspring_crm.module
patching file src/Form/SharpSpringCrmConfigForm.php
patching file src/Plugin/WebformHandler/SharpSpringCrmLeadHandler.php
Hunk #5 FAILED at 75.
1 out of 8 hunks FAILED -- saving rejects to file src/Plugin/WebformHandler/SharpSpringCrmLeadHandler.php.rej
patching file src/Plugin/WebformHandler/SharpSpringCrmListHandler.php
patching file src/SharpSpringCrm.php
Comment #4
urvashi_vora commentedHi,
Because of inactivity for more than a week, assigning this to myself and I am working on this currently.
Comment #5
nitin_lamaNo activity since last 2 days. Here's the updated patch.
Comment #6
nitin_lamaComment #7
urvashi_vora commentedHi,
Your patch applied, but still, some errors are there. I am working on them.
Comment #8
gisleHi, I am a site moderator at Drupal.org, resposible for sorting out spam.
Today, an extraordinary number of spam flags was raised about comments posted about this, and other, issues. Viz.:
#3292463: Fix the issues reported by phpcs, #3222510: Drupal Coding Standard Fixes., #3290851: Coding Standard Issue, #3169485: Fix Drupal Coding Standard Errors, #3291030: Fix the issues reported by phpcs, #2876993: Fix the issue reported by phpcs, #2886164: Coding Standard issues.
Please note that spam is defined as "unsolicited advertising". The spam flag should not be used for other purposes, such as flagging that you dislike a post or you disagree with someone's behaviour. Please do not do this. It is just wasting the site moderators' time. If you need help to sort out some dispute, report it to the CWG. A possible conflict between community members is out of scope for site moderators.
Looking at the flagged comments, it looks like the root of the matter is some sort of disagreement between individuals from two different agencies about the handling of coding standards patches. I hope this has stopped now, but I shall conclude by adding this standard text created by the Drupal Community Health Team for use in situations like this:
Escalating emotions
This discussion appears to include escalating emotions, creating the opportunity for miscommunication. The invested parties are encouraged to take a break from this discussion to help gain perspective. It is important to the community that all members are shown the appropriate amount of respect and openness when working together. Additionally, there are resources offered by the Drupal community to aid conflict resolution should those be needed.
For more information, please refer to Drupal’s Values and Principles of seeking first to understand, then to be understood. Assume best intentions of other contributors and suspend judgment until you have invested time to understand decisions, ask questions, and listen. Before expressing a disagreement, make a serious attempt to understand the reasons behind the decision.
This comment is provided as a service (currently being tested) of the Drupal Community Health Team as part of a project to encourage all participants to engage in positive discourse. For more information, please visit https://www.drupal.org/project/drupal_cwg/issues/3129687
Comment #9
urvashi_vora commentedHi,
Please review this patch.
Thanks
Comment #10
drupalmatts commentedThanks I will review these asap and get a new release ready. I would also like to get this certified for a 1.0 release.
Comment #11
sidharth_soman commentedHi @urvashi_vora,
Your patch applied cleanly. It has solved most of the coding standard issues. However, there are a few of them remaining shown below.
I'll work on this.
Comment #12
sidharth_soman commentedHere is the updated patch. Please review.
Comment #13
hardikpandya commentedThe last applied patch is not applying.
I will work on fixing this.
Comment #15
hardikpandya commentedCreated MR that fixes all phpcs issues reported.
Comment #16
avpadernoThe issue summary should always describe what the issue is trying to fix and, in the case, of coding standards issues, show which command has been used, which arguments have been used, and which report that command shown.
Comment #17
hardikpandya commentedComment #18
hardikpandya commentedComment #19
avpadernoComment #20
mahima_mathur23 commentedComment #21
cleavinjosh commentedHi @hardikpandya,
I tried to apply MR!1 but I encountered some errors.
Please check and advise.
Thank you.
Comment #23
avpadernoComment #24
cleavinjosh commentedHi,
Please review MR!3. Thank you.