pareeohnos

Apologies @kevinongko I had left the `type` of the prop out because it was always giving warnings/errors in the actual code, but I've just had another look and it seems...

@kevinongko just ran into the issue and the reason why I left it failing on the linter. If I leave in the `type: [String, Number]` attribute of the value prop,...

I had originally tried that approach but Vue still spits out a warning (though it's just a warning so wouldn't cause any real issues). I assume vue's type check is...

Unsure really, I can't see why it would break anything. The only thing is it wouldn't give any warnings or errors if the `value` prop was not provided by the...

I'm happy to make any change needed but can't personally get it merged released. Hopefully soon

@egeersoz I can't do anything about getting it merged unfortunately. @kevinongko any updates, would be good to be able to use this without needing to use my fork in our...

@egeersoz have you added `:empty-value="null"` to the template? Otherwise it defaults to the normal behaviour

@egeersoz hmm fair enough. I had originally removed this but it failed the linter specs and a PR won't be accepted with this, so not sure what to do here...

Seems true of the `skip_load_resource` as well, but even for 1.6.9 and 1.6.8. I've got ``` load_and_authorize_resource :user load_and_authorize_resource :location, through: :user, shallow: true skip_load_resource only: :create ``` And `load_resource`...

It may well be a JDBC specific issue, as the JDBC drivers override various methods that AR normally handles but I couldn't say for sure. I'm not sure if any...