-
Notifications
You must be signed in to change notification settings - Fork 273
N°4789 - Parse datamodel module.xxx.php files instead of interpreting them #746
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The roles of the three classes MouleFileParser, ModuleFileReader and PhpParser should be furthermore clarified -at least explained.
| $sExpr; | ||
| PHP; | ||
| try{ | ||
| $aNodes = ModuleFileParser::GetInstance()->ParsePhpCode($sPhpContent); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought this class is consumed by ModuleFileParser... not the other way around!
… them - refactoring all in a dedicated service first
…dle ModuleInstallerAPI methods calls during setup
…p redondant evaluators
…ove ModuleFileParser internal logic into ModuleFileReader
cf28d40 to
9436a02
Compare
… them (#746) - namespacing ModuleFileReader classes
This PR relies on a fork from nikic/PHP-Parser
nikic/PHP-Parser#1107
The idea is to enhance how module configuration are read. It would have been nice to propose another format as well (ie json). but this is another story...