Add conditional check for sqlite3_production_warning before setting to false in railtie.rb #106
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As mentioned in #105, the new Rails main (7.2.0-alpha) removes
config.active_record.sqlite3_production_warning
and so the litestack railtie attempt to set it to false fails. This is an attempt to fix that.This is also a better solution (IMHO) than #98, as there are still people utilizing older versions that might need this check. This only fixes it if it's needed.