#603 Bring the interfaces in TOOLs in compliance with the coding style
Closed: Fixed None Opened 13 years ago by dpal.

Coding style http://www.freeipa.org/page/Coding_Style#Function_Parameters specifies order or the parameters.
Many functions in tools violate the coding style in this regard. The interfaces must be cleaned before 1.0 release.


Fields changed

rhbz: => 0

Fields changed

rhbz: => 0

Fields changed

rhbz: => 0

Fields changed

blockedby: =>
blocking: =>
coverity: =>
feature_milestone: =>
milestone: Tools Backlog => Tools 1.0
patch: => 0

Fields changed

blockedby: =>
blocking: =>
coverity: =>
feature_milestone: =>
milestone: Tools Backlog => Tools 1.0
patch: => 0

Fields changed

blockedby: =>
blocking: =>
coverity: =>
feature_milestone: =>
milestone: Tools Backlog => Tools 1.0
patch: => 0

I made sure that the new config API is consistent with the coding style.
Unfortunately the existing collection interface is not compliant but I know that it is already used outside of this project so changing interfaces at this point would not be nice.

design: =>
design_review: => 0
fedora_test_page: =>
resolution: => cantfix
selected: =>
status: new => closed

I made sure that the new config API is consistent with the coding style.
Unfortunately the existing collection interface is not compliant but I know that it is already used outside of this project so changing interfaces at this point would not be nice.

design: =>
design_review: => 0
fedora_test_page: =>
resolution: => cantfix
selected: =>
status: new => closed

I made sure that the new config API is consistent with the coding style.
Unfortunately the existing collection interface is not compliant but I know that it is already used outside of this project so changing interfaces at this point would not be nice.

design: =>
design_review: => 0
fedora_test_page: =>
resolution: => cantfix
selected: =>
status: new => closed

Metadata Update from @dpal:
- Issue assigned to dpal
- Issue set to the milestone: Tools 1.0

7 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/1645

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata