-
Notifications
You must be signed in to change notification settings - Fork 7
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
Remove DocBlocks from final output or build #43
Comments
Hmm.. the first comment (usually the DocBlock) should be stripped from the package when built. |
Thx for your reply! If I understand correctly, is correct that the DocBlock stay if the package is installed via repoman. |
Correct: installing via Repoman does not strip out DocBlocks. Repoman installs are intended more for dev scenarios, and Repoman uses the info in the DocBlocks, so it doesn't strip them. |
Thx for the explication, maybe will be useful to add a notice in the wiki/DocBlocks about this behaviour. what do you think? something like:
|
hi @fireproofsocks in fact the DocBlocks aren't striped out. |
can you help me to fix thix issues? I'm searching on where this pre-process should be do... |
It'd be somewhere in the parser sub classes... |
Hi @fireproofsocks thx for your reply.
$string = preg_replace('#(' . preg_quote($this->dox_start) . ')(.*)(' . preg_quote($this->dox_end) . ')#Uis', '', $string, 1);
That is not the problem. |
Yeah, there should be a unit test for that case. This might be trickier to pinpoint. |
hi,
there is a way to remove/filter DocBlock from the output?
Example, in case of a template, i wouldn't that the name of the template is available in the source code of each page that use it.
The text was updated successfully, but these errors were encountered: