Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move display_cimobjects from _common to separate module #720

Merged
merged 1 commit into from
Aug 11, 2020

Conversation

KSchopmeyer
Copy link
Contributor

Move all functions associated with display_cimobjects to separate module.

This is first part of adding t he code for issue #249, display classes
as tables. Because the new code is going to significantly increase the
size of the functions associated with displaying objects as tables, it
was logical to move this from _common.py to its own file.

Fixes alse one pylint issue by changing code

Fixes issue where pylint was reporting possible undefined variable in
pick_one_from_list() when the variable was part of a for statement by
not using that variable and creating a new variable to represent the
same information.te

In the process we noted that there was no test for the correct pick of
last item in the list and confirmation that if the next higher number
was picked it treated as invalid a so test was added.

NOTE: We also changed the names of a number of the methods that started with _print...
to _display... for consistency.

@KSchopmeyer KSchopmeyer added this to the 0.8.0 milestone Aug 10, 2020
@KSchopmeyer KSchopmeyer self-assigned this Aug 10, 2020
@coveralls
Copy link

coveralls commented Aug 10, 2020

Coverage Status

Coverage decreased (-0.09%) to 91.899% when pulling 37f3b8b on ks/#move_display_cimobject into 3bac9a8 on master.

module.

This is first part of adding the code for issue #249, display classes
as tables.  Because the new code is going to significantly increase the
size of the functions associated with displaying objects as tables, it
was logical to move this from _common.py to its own file.

Fixes alse  one pylint issue by changing code

Fixes issue where pylint was reporting possible undefined variable in
pick_one_from_list() when the variable was part of a for statement by
not using that variable and creating a new variable to represent the
same information.

In the process we noted that there was no test for the correct pick of
last item in the list and confirmation that if the next higher number
was picked it treated as invalid a so test was added.
@andy-maier andy-maier merged commit 8d123a4 into master Aug 11, 2020
@andy-maier andy-maier deleted the ks/#move_display_cimobject branch August 11, 2020 09:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants