Forcing explicit scope: kept, discarded, or with_discarded. Never all about discard

[jarednorman]

This is a great idea and would be really helpful for projects migrating from paranoia. I'd love if this could be provided as a separate gem that adds this functionality, as we want to keep discard's core as minimal as possible.

@j1mmie Can you publish a proof of concept that I can take a look at?

[gblair]

I think I like this design, for my 2 cents. @j1mmie, how did this end up panning out for you?

[jarednorman]

I am closing this issue because it's a feature request that I don't believe belongs in discard itself, but I may author a separate extension that does this unless someone provides a solution to accomplish it.

[j1mmie]

Thanks for your approval @jarednorman - Unfortunately I lost my progress on this extension. But maybe if there's more conversation + demand here someone would be willing to pick up the effort.

[jarednorman]

Too bad, but that's okay. We need some functionality like this for the Solidus project (which discard was originally written for) so I'm sure someone will pick up the helm.

[cedum]

👋 I started experimenting with showing a warning when the query condition is missing in this repo: https://github.com/cedum/explicit_query_condition

Actually, it doesn't support all cases: I couldn't find a way to check the join conditions easily to be able to show the warning when the explicit condition requirement on the joined table isn't present.

Let me know what you think and/or have any suggestions 🙏