Project

General

Profile

Actions

Refactor #12091

closed

Should we disable MethodLength and ClassLength checking on dynflow actions in Katello

Added by David Davis over 8 years ago. Updated almost 4 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Category:
-
Target version:
Branch:
Difficulty:
Triaged:
Yes
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.

Actions #1

Updated by Eric Helms over 8 years ago

  • translation missing: en.field_release set to 114
Actions #2

Updated by The Foreman Bot about 8 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/Katello/katello/pull/5782 added
Actions #3

Updated by David Davis about 8 years ago

  • Status changed from Ready For Testing to Rejected
Actions #4

Updated by Jonathon Turel almost 4 years ago

  • Target version changed from Katello Backlog to Katello Recycle Bin
Actions

Also available in: Atom PDF