Closed (outdated)
Project:
Config Enforce Devel
Version:
1.0.x-dev
Component:
Code
Priority:
Minor
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
21 Apr 2023 at 04:46 UTC
Updated:
27 Nov 2025 at 15:32 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #3
sidharth_soman commentedI've fixed all the issues except for those relating to filling out/correcting documentation (which should ideally be done by the maintainers). Please review the above MR.
Comment #4
avpadernoThe usual comment is Install, uninstall, and update hooks for the [module name] module.
That should be Hook implementations for the [module name] module.
As per coding standards, that should go all in one line.
@seedoes not need a final period.The description must start with a capitalized word.
Also, the parameter type is given after
@param, not in the short description.What follows
@todoshould be an imperative sentence.No, the issue on the existing documentation comment for that class property is not that it uses spaces where they should not be.
Documentation comments must not be empty.
That not how parameters are documented.
The
@vartag is missing.It is sufficient to say The file system service.
Comment #5
ambient.impactI appreciate all the work that's going into this. We're currently focused on building up the test suite for both modules and then will heavily rewrite most of the internals, along with much better documentation and more consistent coding style. You can find a high level overview in #3305516: Config Enforce roadmap and #3306273: Config Enforce Devel roadmap.
Comment #6
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 #7
ashutosh ahirwal commentedI Have updated the issue summary.
Comment #8
avpadernoComment #11
avpadernoComment #12
a.aaronjake commentedHi @bharath_kondeti,
Applied latest changes on MR !9, it seems to have problem, might be the reason it threw multiple errors. Please see below:
Kindly check and advise.
Thanks,
Jake
Comment #14
kalash-j commentedi have fixed the remaining phpcs issues
Comment #15
a.aaronjake commentedHi @kalash-j,
MR!19 was applied not-so successfully and it also threw multiple errors
Kindly check
Thanks,
Jake
Comment #17
avpadernoMR !19 did not fix all the PHP_CodeSniffer errors/warnings.
Comment #18
avpadernoComment #20
star-szrThank you for the efforts here folks. No further work is planned for the 1.0.x series other than security fixes and some deprecations and such.
2.0.x is under active development and we plan to fix the phpcs issues there, but this will be taken on by the module maintainers so that it can be done efficiently without a lot of rework needed, and without disrupting the work that the module maintainers are doing across many fronts.