aboutsummaryrefslogtreecommitdiffstats
path: root/tests
Commit message (Collapse)AuthorAgeFilesLines
* refactor(providers,hooks): rewrite PrismThemeProvider & usePrismThemeArmand Philippot2023-11-111-13/+16
| | | | | | * reuse Theme provider logic * move DOM mutation from provider to hook * add a script to init theme before page load
* feat: replace next-themes with a custom ThemeProviderArmand Philippot2023-11-111-3/+6
| | | | | | | To be honest, next-themes was working fine. However since I use a theme provider for Prism code blocks, some code is duplicated between this app and the library. So I prefer to use a custom Provider without the options I don't need.
* refactor(hooks,provider): move reduce motion setterArmand Philippot2023-11-111-2/+8
| | | | | | | | | | Since the local storage key is not meant to change between the components, it should be set directly inside the app file. So both the local storage and the data attribute should be handle in a provider. I also added a custom document because we need a script to retrieve the stored value in local storage earlier to avoid flashing on hydration.
* refactor(hooks,providers): rewrite useAckee hook and AckeeProviderArmand Philippot2023-11-111-12/+24
|
* refactor(routes): replace hardcoded routes with constantsArmand Philippot2023-10-246-32/+52
| | | | | | | | 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.
* build: convert project to esmArmand Philippot2023-10-241-0/+2
|
* refactor(build): replace paths aliases with relative pathsArmand Philippot2023-09-192-2/+2
| | | | | | 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.
* test(e2e): add settings form testArmand Philippot2022-06-031-0/+177
|
* test(e2e): add other pages testArmand Philippot2022-06-034-0/+27
| | | | | 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.
* test(e2e): add contact page testArmand Philippot2022-06-031-0/+41
|
* test(e2e): add loading more button test for blog pageArmand Philippot2022-06-031-0/+44
|
* test(e2e): add back to top button visibility testArmand Philippot2022-06-021-0/+14
|
* test(e2e): add search feature testArmand Philippot2022-06-021-0/+41
|
* test(e2e): add Footer navigation testArmand Philippot2022-06-021-0/+12
|
* test(e2e): add main navigation testArmand Philippot2022-06-021-0/+62
|
* test: install and configure cypressArmand Philippot2022-06-027-0/+121
| | | | I also configure Jest to avoid conflicts between Cypress and Jest.
* build: configure jestArmand Philippot2022-03-242-2/+0
| | | | | | Since Next.js v12, Jest is already configured with the next/jest package. I also added a package to mock next/router.
* build: configure JestArmand Philippot2021-12-122-0/+2