| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Both:
* move styles to Sass placeholders
Button:
* add `isPressed` prop to Button
* add `isLoading` prop to Button (to differentiate state from
disabled)
ButtonLink:
* replace `external` prop with `isExternal` prop
* replace `href` prop with `to` prop
|
| |
|
|
|
|
|
|
| |
It makes it easier to change a route if needed and it avoid typo
mistakes.
I also refactored a bit the concerned files to be complient with the
new ESlint config. However, I should rewrite the pages to reduce
the number of statements.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Next expect a default export for pages so only those components should
use default exports. Everything else should use named exports to
reduce the number of import statements.
|
| |
|
|
|
| |
* MDX type has changed so some components props had to be updated
* Since Storybook now supports TS, I renamed the main/preview files
|
| |
|
|
|
|
| |
Using paths aliases starting with "@" can be confusing and can lead to
conflict with existings modules. I prefer to use relative paths to
avoid extra configuration in tools because of these aliases.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
The previous way of handling content import was causing issue. So I use
dynamic import instead. However, the table of contents was not
displayed because the wrapper is first empty. I added a mutation
observer to refresh the table of contents when the body is updated.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Sometimes it is useful to display some preformatted data that are not
code.
|
| |
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
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...
|
| |
|
|
| |
I also configure Jest to avoid conflicts between Cypress and Jest.
|
| | |
|
| |
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
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…)
|
| |
|
|
|
| |
With French translation, words are a little longer so I reduce the
font size on small devices to avoid line breaking.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
I moved the website picture from useSettings to the layout
component since it is only used here. This reduce the number
of Jest errors. However, there's still some issues with some
images import...
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
By using useSWR I can fetch the changes from the backend.
By using fallback, I can access new articles without rebuilding the
entire app.
|
