-
Notifications
You must be signed in to change notification settings - Fork 7
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
Highlight box bug #38
Conversation
Pull Request Test Coverage Report for Build 9370168024Details
💛 - Coveralls |
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.
@yoonieaj good job. You fixed the immediate bug, but should look for all places where drawText
is called, and make sure it's called after the corresponding drawRect
calls. Otherwise this issue might come up again later.
CHANGELOG.md
Outdated
@@ -24,6 +24,7 @@ and adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). | |||
- Added data type and manual layout tests for the `draw` function. | |||
- Updated file paths for example files under docs to import the correct file. | |||
- Added style and automatic layout tests for the `draw` function. | |||
- Fixed highlight bug and changed implementation of `hide` style option. |
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.
This change a bug fix, so should go under the "Bug fixes" section. You should describe in more detail what the bug is, but don't need to mention specific implementation details. I.e., focus on the what, not the how.
Proposed Changes
Fixed a bug where the fill colour of boxes covered and hid the text in the box. This was done by changing the order in which elements are drawn.
Also changed the implementation of the hide style option. Now, this option sets text opacity to zero (before, it covered the text with a white box), so that the hide style option still works after the above bug fix.
...
Type of Change
(Write an
X
or a brief description next to the type or types that best describe your changes.)Checklist
(Complete each of the following items for your pull request. Indicate that you have completed an item by changing the
[ ]
into a[x]
in the raw text, or by clicking on the checkbox in the rendered description on GitHub.)Before opening your pull request:
After opening your pull request:
Questions and Comments
I went over the snapshots and it seems like they were failing because of the changed order in which elements were drawn, so I decided to update the snapshots and have included the updated versions in this PR.