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

Proposed change to get_values behavior #1535

Closed
wants to merge 1 commit into from

Conversation

kfreezen
Copy link
Contributor

get_values() did not load existing sections before checking the _sections property.

NOTE: Haven't written a test to check for this yet.

@kfreezen
Copy link
Contributor Author

Proposed fix for #1534

@kfreezen
Copy link
Contributor Author

Looking at test here; I suppose we can leave it raising a KeyError. The main fix was force-loading the _sections attribute before checking the list.

I'll re-commit using KeyError.

Copy link
Member

@Byron Byron left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks a lot, much appreciated!

I think the commit should link back to the issue it resolve to create a more declarative history.
Finally it should be possible to devise a test that would fail without this change to cement it. Otherwise it might be removed in future because it's unclear why eager loading of sections is necessary.

@Codym48
Copy link
Contributor

Codym48 commented Feb 16, 2023

@kfreezen, consider accepting kfreezen#1 to add test coverage for this change? I verified it fails on main:

image

@Byron
Copy link
Member

Byron commented Feb 16, 2023

Closing as it's superseded by #1555

@Byron Byron closed this Feb 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants