| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
Previously, only the first 10 comments was loaded. So I update the
fetching method to retrieve all the comments on a post.
Also, I choose to order comments on client side because of a bug
with WPGraphQL.
Finally, I renamed the Comment type to SingleComment to avoid conflict
with existing types.
|
| |
|
|
|
|
|
| |
The api file in services was not really readable. So I move the types
and I also rewrite a little the fetch function.
I also rename most of the type to avoid conflict with preexisting
types (like Node) and to keep consistency.
|
| | |
|
| |
|
|
|
|
| |
By switching to custom hooks for revalidating articles and comments,
everything was working on development mode but articles failed to build
for production.
|
| | |
|
| | |
|
| |
|
|
|
| |
The Next config has also been updated: the experimental config
`outputStandalone` is no longer experimental.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bumps [terser](https://github.com/terser/terser) from 4.8.0 to 4.8.1.
- [Release notes](https://github.com/terser/terser/releases)
- [Changelog](https://github.com/terser/terser/blob/master/CHANGELOG.md)
- [Commits](https://github.com/terser/terser/commits)
---
updated-dependencies:
- dependency-name: terser
dependency-type: indirect
...
Signed-off-by: dependabot[bot] <support@github.com>
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
Everything was working fine with Firefox but it seems Chromium still
has issues with `em` unit in media queries. The toolbar modals (search,
settings and also main nav) was not displaying correctly on small
devices. Some styles was missing. By switching to pixels based media
queries, the bug seems fixed.
|
| |
|
|
|
|
| |
I changed the settings disposition to make tooltip positioning easier.
Jest complains about ref passed but everything seems to work as
expected so I'm not sure it is relevant. Maybe a bug with cloneElement.
|
| |
|
|
|
| |
The event was not captured so the tooltip remained open when the
settings was closed. It prevented to click on the toolbar buttons.
|
| | |
|
| |\
| |
| | |
Improve images, code blocks, cards and progress bar accessibility.
|
| | |
| |
| |
| |
| |
| | |
The progress element is a form element, so a label is required to be
accessible. Since I'm not using it without label, I transform the
optional info parameter to a mandatory label parameter.
|
| | |
| |
| |
| |
| | |
Prism is adding a tabindex to code blocks, so I think an aria label
can help screen reader users to identify the tabbed content.
|
| | | |
|
| | | |
|
| |/ |
|
| | |
|
| |\
| |
| |
| | |
In addition to Jest tests, I configure Cypress to test some pages and features.
I also fix some Jest errors due to images import.
|
| | |
| |
| |
| |
| | |
I mocked some SVG files and moves the branding photo to public
directory. It is more a workaround than a real fix but it works so...
|
| | | |
|
| | |
| |
| |
| |
| | |
Sometimes a build can be successful but the page is not working, so
these tests allows me to check if the page is correctly loaded.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |/
|
|
| |
I also configure Jest to avoid conflicts between Cypress and Jest.
|
| |\
| |
| |
| |
| | |
The settings modal had some accessibility issues:
* the SVG title was not used as radio button label,
* the state of the help button was only visual.
|
| | | |
|
| |/
|
|
|
| |
It seems I cannot use the SVG title as label. So I removed the title
and added a visually hidden span to set the radio buttons label.
|
| | |
|
| |\
| |
| | |
The previous switch buttons (using checkbox) was not a11y compliant. So I change my approach to use radio buttons and to clearly separate the two different states. I also convert the Ackee select setting to improve consistency between settings.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
Checkbox and radio buttons are working the same way so I decided to
group them in a same component.
|
| |/ |
|
| |
|
|
|
|
|
|
| |
Formatjs (ICU actually) uses single quotes as escape character so some
French translation had issues because of apostrophe. I replaced the
character used. I took the opportunity to use the correct characters
for some other typographic rules (non-breaking spaces, suspension
points…)
|
| |
|
|
|
| |
Some images failed to load and the staging build was randomly crashing
with exit code 137 (memory issue).
|
| |
|
|
|
| |
With French translation, words are a little longer so I reduce the
font size on small devices to avoid line breaking.
|