Conversation
|
I'm not entirely sure if the extensions should be in |
|
The reason I hadn't had the generation commands in I also couldn't find a good way to pass those options into the |
|
Re: the extensions, I'm not sure either...the Composer docs seem to imply that you can put extensions in |
|
Also just wanted to say -- I really appreciate all your recent contributions. This library takes a good bit of work to keep rolling, and a major motivation of the v6 overhaul was to make it easier for people to contribute, so it's cool to see that that's paying off. Thanks for your time and help! |
This adds a `build` and `clean` commands to `composer.json` to enable easier discovery of the build process for new developers. Due to the `clean` deleting the raw directory. I've moved the gitignore into the top level `.gitignore`. The available commands are added to the README.md Add single schema generation commands to README We need to explain about the need for `--` in composer commands
067084b to
136bd29
Compare
|
I've added more information to the README.md. Unfortunately you can't run The composer documentation does mention being able to avoid the |
|
@dpash I kinda dropped the ball here, but are you still interested in looking into getting the command line args to work? I think I was waiting to see where you went with that, which is why I never merged this. If you'd like to leave it as is, I'm happy to merge this, but a) raw schemas are no longer gitignored and b) there's now a separate |
This adds a
buildandcleancommands tocomposer.jsonto enable easier discovery of the build process for new developers.Due to the
cleandeleting the raw directory. I've moved the gitignore into the top level.gitignore.The available commands are added to the README.md