ManageIQ / ManageIQ/activerecord-virtual_attributes
Extract patching to a separate file from the modules themselves
Open
Nobody has claimed this yet.
good first issue
help wanted
refactoring
- Dominant language
- Ruby
- Stars
- 10
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
@kbrock as discussed. It's up to you how to do it, I just wanted a placeholder issue.
Contributor guide
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
The issue names no files or tests and leaves the implementation approach open. Start by locating the patching code in the modules, then determine the project’s existing test entry points; done means patching is separated into its own file without breaking the module behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100