-
Notifications
You must be signed in to change notification settings - Fork 325
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
change color when hovering over code-formatted text #2007
Merged
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
7da318e
make hovered code links change color
drammock 5508eed
fixup old test
drammock ef7837a
add basic test of colors
drammock 23b711b
add comment
drammock 8fccb62
cleaner error handling
drammock 81f25e5
refactor / DRY
drammock a277d97
fix docstring
drammock File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,19 @@ | ||
"""Test conf file.""" | ||
|
||
# -- Project information ----------------------------------------------------- | ||
|
||
project = "PyData Tests" | ||
copyright = "2020, Pydata community" | ||
author = "Pydata community" | ||
|
||
root_doc = "index" | ||
|
||
# -- General configuration --------------------------------------------------- | ||
|
||
# Add any Sphinx extension module names here, as strings. They can be | ||
# extensions coming with Sphinx (named 'sphinx.ext.*') or your custom | ||
# ones. | ||
extensions = [] | ||
html_theme = "pydata_sphinx_theme" | ||
html_copy_source = True | ||
html_sourcelink_suffix = "" |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,28 @@ | ||
Test of colors | ||
============== | ||
|
||
Some text with a `text link <https://pydata.org>`__. | ||
|
||
Heading 1 | ||
--------- | ||
|
||
Some text with a :ref:`cross reference link <a-cross-reference>` | ||
|
||
Heading 2 | ||
~~~~~~~~~ | ||
|
||
Some text with ``inline code``. | ||
|
||
|
||
.. _a-cross-reference: | ||
|
||
Heading 3 | ||
````````` | ||
|
||
Some text with a |code link|_. | ||
|
||
|
||
.. the below replacement is included to emulate what intersphinx / autodoc / numpydoc generate (links on text formatted as code), which (sadly) can't be done using nesting of standard rST markup. | ||
|
||
.. |code link| replace:: ``inline code link`` | ||
.. _code link: https://pydata.org |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
These seem to be the "light theme" colours; should we be testing for both light and dark?
My gut tells me yes WDYT @drammock @gabalafou ?
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 think that as long as we know that mode switching works, tests like this one (i.e. "did the CSS selector do what we intended" tests) only need to test one mode.
The exception would be any a11y test that checks for color contrast --- obv. we should run that test in both modes.
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.
We are running those a11y tests on both modes so then we should be covered