Recent searches
Search options
@greg0ire@phpc.social`doctrine/orm` 2.18.0 will have a flatter directory tree: https://github.com/doctrine/orm/pull/11148
`fzf` is going to be easier to use 
@hypolite Insert "I don't always make PRs, but when I do, I make sure to touch every file in the project" meme
@greg0ire wow, I thought Phpactor and Phpbench |were the only one that used `lib/` as the source directrory.
I did wonder where I got that idea from and when `src` was more appropriate. Need to migrate them to `src/` at some point 
@dantleech Yeah `lib` would make more sense as an alternative to `vendor` I think
@greg0ire I started using `lib`/ recently as an incubator for packages in addition to `src/`
@dantleech Ah yeah that makes sense... So the flow is you first extract from `src` to `lib`, then to a separate repo? I tend myself to put features as separate namespaces right under `src`, so that removing a feature is ideally just an `rm` command away, or as close to it as possible.
@greg0ire yeah it depends on the namespacing policy. I can resort to `lib/` when the root namespace of the project/package would be the "wrong" one..
e.g. for php-tui I had 3 packages in `lib/` and have now extracted 2 of them to repositories and the other one will probably stay there for ever.