Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nuxt-Link should not be considered a Block-Element #112

Closed
campino2k opened this issue Aug 5, 2020 · 1 comment
Closed

Nuxt-Link should not be considered a Block-Element #112

campino2k opened this issue Aug 5, 2020 · 1 comment

Comments

@campino2k
Copy link

Using a list of nuxt-links like

            ... 
            <template
              v-for="(location,idx) in locationsFirst"
            >
              <nuxt-link :key="location.slug" :to="{name:'locations-loc', params:{loc: location.slug}}" class="inline underline hover:no-underline hover:text-red-600 hover:bg-red-100 transition duration-500">
                {{ location.city }}</nuxt-link>{{ ++idx!==locationsFirst.length?', ':'' }}
            </template>
            und
            <nuxt-link
              v-if="locations.length"
              :to="{name:'locations-loc', params:{loc: locationsLast.slug}}"
              class="underline hover:no-underline hover:text-black hover:bg-blue-200 transition duration-1000"
            >{{ locationsLast.city }}
            </nuxt-link>

Where it should look like link1, link2, link3 and link4 will look like link1 , link2 , link3 and link4 where the commas get off by one char because linter is forcing line breaks inside nuxt-links.

@antfu
Copy link
Member

antfu commented Apr 18, 2024

Fixed in #391

@antfu antfu closed this as completed Apr 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants