Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Support for PHP source directory

Open
#175 7 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
php
Domain
tooling

Research direction

No files or tests are named in the issue. Start by reviewing the Composer autoload configuration and current PHP package/test layout, then determine whether PSR-4 or PSR-0 fits; done means PHP source is separated from tests and deployment can distinguish package code without affecting Composer users.

Written by the indexing model from the issue text.

Description

Carsten,

This is a great package. Been using it for a while on my PHPFUI site which easily documents any PHP code.

I was wondering if you would be up for a Pull Request to put the PHP source in it's own directory. This is pretty standard practice for PHP libraries. I would be willing to submit one, I just don't want to do the work if you have a reason to keep it the way it is. I would go with either PSR-4 or PSR-0 autoloading depending on if you have a preference.

This should not affect any user of the package if they are using composer to install it. The reason I am interested in a dedicated source directly is my PHPFUI site does not use composer for deployment, but has everything checked in. I have a script that copies over files, but it can't easily distinguish between test code and package code. It is also a good logical separation in general.

Anyway, let me know if you think this would be a good idea. Happy to contribute to this excellent project.

Bruce

Dominant language
HTML
Stars
1k
Forks
137
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cebe/markdown

All issues in cebe/markdown

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.