majkelcc

I'm guessing that previously there was no `hide_default_column_types` configuration option, hence the fallback to the default value. Would distinguishing between this option missing (being nil`) and being set to empty...

Just a though - support for updating multiple containers sounds like a bigger change and personally. What if we could try to make chaining multiple update actions easier? This could...

After discovering that attempting to clone `FormData` object can result in error in some cases, I changed the fix so that it doesn't use new methods and only allows `xdomain`...

> I'm open if you think you can make it work fitting that info into the table. This indeed turned out to be a problem very early. I'll see what...

I recently migrated to Vite and faces the same issue, but my solution was different - not to rely on `autoBuild` at any point, which imho is better to be...

In https://github.com/ruby-json-schema/json-schema/blob/master/lib/json-schema/errors/validation_error.rb I see some very useful information coming with each error. To be as flexible as possible validation could return an array of instances of mentioned `ValidationError`. Additionally to...

If you want to protect your source code you need to use a tool for obfuscating ruby code before using Traveling Ruby, which simply copies your source code unmodified to...

I also noticed a very odd behaviour: - when I pass an invalid path via `SOLID_QUEUE_RECURRING_SCHEDULE` then SolidQueue defaults to the default `config/recurring.yml` configuration file - when I pass an...

I thought I'm just tired, but I can still replicate this behaviour - I'm testing it by adding a new task to `config/recurrring.yml` - it gets added every time when...

Used commands: - `SOLID_QUEUE_RECURRING_SCHEDULE=non_existing_path.yml bin/jobs` - `bin/jobs --recurring_schedule_file=non_existing_path.yml` Now I made a syntax error in the default `config/recurring.yml` and discovered that when using the env variable, SolidQueue is always reading...