-
Notifications
You must be signed in to change notification settings - Fork 829
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
Prevent reactive-watcher loop in Tabs / TabbedContent. #2305
Conversation
Labels are cheaper to use and the final visual result of the test won't depend on the directory it runs from.
Turns out I didn't need a descriptor. :(
if not active: | ||
raise ValueError("'active' tab must not be empty string.") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Originally I just let the setter set the attribute active
on the child Tabs
but the tests failed because they expected a ValueError
when setting the tab to an empty string, so I added it back in 6eb141c.
However, to me it doesn't make much sense that I can't set TabbedContent.active = ""
but I can set Tabs.active = ""
.
Am I "right"? If so, do we allow active = ""
everywhere or nowhere?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@willmcgugan pinging you because you already merged but this was left unresolved.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think an active tab of empty string doesn't anything useful, so it probably should be an error in both places.
This reverts commit 66a6448.
This will close #2229.
See this comment wherein for an explanation of the issue.
We use a descriptor to proxy the attribute
active
fromTabs
toTabbedContent
without having to keep it in sync in two different places.