Adam Stankiewicz
Adam Stankiewicz
I'd just suggest instead of documenting it, to make it a positional argument so it's easy to deploy single component or run custom function of some component, so: - `sls...
(--component flag works) Also maybe a good a default, when only one component is defined, is to run custom method of that component.
This makes sense. You could include this fix in your PR as well if you can manage to do it :) btw. I've updated many things in 1.5.3, so please...
If they won’t change it we could catch and ignore this error maybe On Tue, 27 Mar 2018 at 01:31, Chad McElligott wrote: > knex-migrate pretty much just calls out...
The knexfile is supposed to be exactly at `/path/to/your/project/knexfile.js`. Sorry if code suggests otherwise, but the message is correct.
Yes, I understand it now. This needs to be fixed
Yes, do you want to write this section?
When I implemented this library this seemed to be the most offending difference, but this is just how https://github.com/sequelize/umzug works. Personally I think this is better choice because each migration...
Could you prepare PR to fix this?
Thank you for this PR, but you'd need to send similar PR to knex itself first