From b39e04ca314883e4e0502b57b356cfa4e7fadf1d Mon Sep 17 00:00:00 2001 From: Timothy Armes Date: Fri, 7 Jul 2023 09:32:37 +0200 Subject: [PATCH 1/3] Fix warning on VSCode --- .vscode/settings.json | 4 ++- .vscode/tailwindcss.json | 55 ++++++++++++++++++++++++++++++++++++++++ 2 files changed, 58 insertions(+), 1 deletion(-) create mode 100644 .vscode/tailwindcss.json diff --git a/.vscode/settings.json b/.vscode/settings.json index 94198d8..7a49787 100644 --- a/.vscode/settings.json +++ b/.vscode/settings.json @@ -25,5 +25,7 @@ "tournois", "unspiderfied", "unspiderfy" - ] + ], + + "css.customData": [".vscode/tailwindcss.json"], } diff --git a/.vscode/tailwindcss.json b/.vscode/tailwindcss.json new file mode 100644 index 0000000..96a1f57 --- /dev/null +++ b/.vscode/tailwindcss.json @@ -0,0 +1,55 @@ +{ + "version": 1.1, + "atDirectives": [ + { + "name": "@tailwind", + "description": "Use the `@tailwind` directive to insert Tailwind's `base`, `components`, `utilities` and `screens` styles into your CSS.", + "references": [ + { + "name": "Tailwind Documentation", + "url": "https://tailwindcss.com/docs/functions-and-directives#tailwind" + } + ] + }, + { + "name": "@apply", + "description": "Use the `@apply` directive to inline any existing utility classes into your own custom CSS. This is useful when you find a common utility pattern in your HTML that you’d like to extract to a new component.", + "references": [ + { + "name": "Tailwind Documentation", + "url": "https://tailwindcss.com/docs/functions-and-directives#apply" + } + ] + }, + { + "name": "@responsive", + "description": "You can generate responsive variants of your own classes by wrapping their definitions in the `@responsive` directive:\n```css\n@responsive {\n .alert {\n background-color: #E53E3E;\n }\n}\n```\n", + "references": [ + { + "name": "Tailwind Documentation", + "url": "https://tailwindcss.com/docs/functions-and-directives#responsive" + } + ] + }, + { + "name": "@screen", + "description": "The `@screen` directive allows you to create media queries that reference your breakpoints by **name** instead of duplicating their values in your own CSS:\n```css\n@screen sm {\n /* ... */\n}\n```\n…gets transformed into this:\n```css\n@media (min-width: 640px) {\n /* ... */\n}\n```\n", + "references": [ + { + "name": "Tailwind Documentation", + "url": "https://tailwindcss.com/docs/functions-and-directives#screen" + } + ] + }, + { + "name": "@variants", + "description": "Generate `hover`, `focus`, `active` and other **variants** of your own utilities by wrapping their definitions in the `@variants` directive:\n```css\n@variants hover, focus {\n .btn-brand {\n background-color: #3182CE;\n }\n}\n```\n", + "references": [ + { + "name": "Tailwind Documentation", + "url": "https://tailwindcss.com/docs/functions-and-directives#variants" + } + ] + } + ] +} From 88e75511d77d7ee9439ad03d2ce8049199716d78 Mon Sep 17 00:00:00 2001 From: Timothy Armes Date: Fri, 7 Jul 2023 09:34:05 +0200 Subject: [PATCH 2/3] Code tidy --- app/[lang]/components/Navbar.tsx | 40 ++++++++++-------------- app/[lang]/components/TestableLayout.tsx | 3 +- app/[lang]/layout.tsx | 3 +- {app => css}/globals.css | 0 4 files changed, 20 insertions(+), 26 deletions(-) rename {app => css}/globals.css (100%) diff --git a/app/[lang]/components/Navbar.tsx b/app/[lang]/components/Navbar.tsx index 810e10f..fb28091 100644 --- a/app/[lang]/components/Navbar.tsx +++ b/app/[lang]/components/Navbar.tsx @@ -6,6 +6,12 @@ import Hamburger from "./Hamburger"; export default function Navbar() { const t = useTranslations("Nav"); + const links = [ + { title: t("tournaments"), route: "/tournois" }, + { title: t("about"), route: "/qui-sommes-nous" }, + { title: t("contact"), route: "/contactez-nous" }, + ]; + return (