Mark Story
Mark Story
If there is a need/desire for persistent configuration in bake, I would prefer we do just that vs. adding properties to arbitrary classes.
A standalone config file feels like a better long term solution to me. We could also use this file to allow customisations to other tasks or enabling specific cli flags...
> I'm not sure users would recognize the failure happened if we ignore it and successfully complete. Baking all could generate a lot of output. That is my concern as...
I think this makes sense to do in bake. Would we potentially run into phpcs errors because the doc string and typehint don't match?
How should bake find out the column type when the model has mapped the column to a custom type?
Updating the docs for custom types and having fixtures use it when creating schema sounds like a good solution. Custom types would still be included in fixture $fields and schema...
> Is there a way to define the data type? Not right now there isn't which is the source of this problem. Type mappers don't know and can't reasonably know...
You can overwrite files using the `--force` option as well.
> Hm, I still think bake should not ask to overwrite untouched files. At least I got used to overwrite all. I could go the other way around, how to...
> It seems to me that bake is designed to be used once then discarded – generally the approach for scaffolding. Yes, it is intended to make getting started quicker...