Skip to content
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

Move page parsers into a namespace #385

Closed
caendesilva opened this issue May 17, 2022 · 0 comments · Fixed by #394
Closed

Move page parsers into a namespace #385

caendesilva opened this issue May 17, 2022 · 0 comments · Fixed by #394
Assignees

Comments

@caendesilva
Copy link
Member

They don't need to be in the root namespace and can be moved to for example models/parsers

@caendesilva caendesilva self-assigned this May 18, 2022
@caendesilva caendesilva linked a pull request May 18, 2022 that will close this issue
caendesilva added a commit that referenced this issue May 18, 2022
…espace

Fix #385: Move page parsers into models/parsers namespace
caendesilva pushed a commit that referenced this issue Aug 8, 2022
…ot-seem-to-work-for-customized-nested-docs-output-paths

Fix bug where DocumentationPage::home() did not work when the documentation page output directory is customized hydephp/develop@027b7af
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant