Discrepancy between Laravel package namespace and README.md instructions #325
Unanswered
Lexian-droid
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello, I am new to this whole library development, so I'm a little confused, but I'm hoping to ask about this little discreprency I found:
When you create a new package using configure.php, everything updates as expected, so I called mine, to follow the trend of some other packages,
lexiandev/laravel-fileforge
and the namespace isLexiandev\FileForge
and class name is instead justFileForge
like the namespace.However, for some reason, when I created my project, the readme.md says to run
to load migrations and other things, difficulty is, as you can see by my namespace, and class name, that doesn't exist, so I round up having to type
fileforge-migrations
leaving out the Laravel prefix, which runs the expected result.I don't really know if this is a bug or not, or if I'm missing something, but it seems like there might be a mismatch between the generated documentation and the actual naming conventions in the package. Could someone please clarify this for me? Thanks a lot for your attention and help!
Beta Was this translation helpful? Give feedback.
All reactions