Gusto / Gusto/explicit_activerecord
Enumeration of some improvements
Open
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 7
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Creating this small ticket to track some ideas for improvements to this gem and its dependencies:
DeprecationHelper improvements
- Log with stack trace: this will help people build allow lists
ExplicitActiveRecord improvements
- Allow allow list per class for incremental work
- ExplicitActiveRecord::Reading
- Start with solid test cases, e.g. WhereChainExtension, pluck, find, direct execution on DB, calling find, a join against the table, calling against a relation (e.g. foo.bars), meta-programatically defined find (Foo.find_by_my_special_column) try different approaches
- Try to see if the sql subscriber can show what tables are being affected, and how
- ExplicitActiveRecord::Persistence
- Add other ways to implicitly persist, such as update_all, etc., or at least test case that fails/skips
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file paths or tests are named. Start by locating DeprecationHelper and the ExplicitActiveRecord::Reading and Persistence components, then review existing tests around the listed ActiveRecord cases. The issue is done only after the separate improvements have defined scope and corresponding behavior or test coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rails, ruby
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100