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

Clarify FloatInput value/value_thottled behavior in docs #5249

Merged
merged 2 commits into from
Jul 18, 2023

Conversation

owenlamont
Copy link
Contributor

Thought I'd tweak this documentation that read a little funny to me when I was raising issue 5205. I think the word spinner threw me which I interpreted as busy spinner but maybe that meant spinbox.

I did some testing and found the value and value_throttled behaved seemingly identically in terms of updates. Also couldn't get the mouse wheel to change the value at all as the documentation implies it should.

Happy to have this PR rejected if I'm being too verbose or am writing too inconsistently with the other docs - I'm trying to slowly wrap my head around the preferred writing style and constraints.

Took the liberty of tweaking the .gitignore too as I was using PyCharm at the time and saw its config wasn't ignored while VS Code's was.

@codecov
Copy link

codecov bot commented Jul 13, 2023

Codecov Report

Merging #5249 (31522c0) into main (af242fa) will increase coverage by 1.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #5249      +/-   ##
==========================================
+ Coverage   82.53%   83.56%   +1.02%     
==========================================
  Files         266      274       +8     
  Lines       39409    39606     +197     
==========================================
+ Hits        32528    33098     +570     
+ Misses       6881     6508     -373     
Flag Coverage Δ
ui-tests 39.30% <ø> (-0.01%) ⬇️
unitexamples-tests 73.78% <ø> (+1.28%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

see 42 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@owenlamont
Copy link
Contributor Author

Damn, I don't see how my docs update could've broken any of these tests... Do these intermittently fail often or is something wrong on the main branch?

@hoxbro
Copy link
Member

hoxbro commented Jul 14, 2023

Don't worry, it is not related to your changes.

The macos-latest unit tests also fail on main and the UI tests are flaky.

Copy link
Member

@philippjfr philippjfr left a comment

Choose a reason for hiding this comment

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

Thanks!

@philippjfr philippjfr merged commit 9545115 into holoviz:main Jul 18, 2023
10 of 15 checks passed
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.

None yet

3 participants