Refactor #12091
Should we disable MethodLength and ClassLength checking on dynflow actions in Katello
Pull request:
Fixed in Releases:
Found in Releases:
Description
The dynflow actions feel more like procedural or imperative programming than OO programming so I am wondering if it makes sense to disable length checking as it's an issue we keep hitting.
History
#1
Updated by Eric Helms over 6 years ago
- Legacy Backlogs Release (now unused) set to 114
#2
Updated by The Foreman Bot over 6 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/Katello/katello/pull/5782 added
#3
Updated by David Davis over 6 years ago
- Status changed from Ready For Testing to Rejected
#4
Updated by Jonathon Turel almost 2 years ago
- Target version changed from Katello Backlog to Katello Recycle Bin