-
Hi All! |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 4 replies
-
Yes, no issues at all. You just need to rename all the imports that reference the Link component as well (VScode automatically does it). If you are thinking about making the change on the main template, I still prefer the |
Beta Was this translation helpful? Give feedback.
-
I agree with your explanation, this one is more logical. Thank you!
Get Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: Timothy ***@***.***>
Sent: Sunday, January 9, 2022 9:52:19 AM
To: timlrx/tailwind-nextjs-starter-blog ***@***.***>
Cc: Sipakov, Rostyslav [missionIZ] ***@***.***>; Author ***@***.***>
Subject: Re: [timlrx/tailwind-nextjs-starter-blog] const CustomLink (Discussion #329)
Yes, no issues at all. You just need to rename all the imports that reference the Link component as well (VScode automatically does it).
If you are thinking about making the change on the main template, I still prefer the Link.js rather than CustomLink.js. The main idea is that you should have one link component and there's no need to use next/link directly. I find it easier to customise the link / a tag logic this way.
—
Reply to this email directly, view it on GitHub<#329 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AIFDQMUPL2QPLDXEV55WRXTUVGOKHANCNFSM5LRNB2OA>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
Yes, no issues at all. You just need to rename all the imports that reference the Link component as well (VScode automatically does it).
If you are thinking about making the change on the main template, I still prefer the
Link.js
rather thanCustomLink.js
. The main idea is that you should have one link component and there's no need to usenext/link
directly. I find it easier to customise the link / a tag logic this way.