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

fix($theme-default): Fix slots syntax #1964

Closed
wants to merge 1 commit into from
Closed

fix($theme-default): Fix slots syntax #1964

wants to merge 1 commit into from

Conversation

kefranabg
Copy link
Collaborator

Summary

Fix #1963

What kind of change does this PR introduce? (check at least one)

  • Bugfix
  • Feature
  • Code style update
  • Refactor
  • Docs
  • Build-related changes
  • Other, please describe:

If changing the UI of default theme, please provide the before/after screenshot:

Does this PR introduce a breaking change? (check one)

  • Yes
  • No

If yes, please describe the impact and migration path for existing applications:

The PR fulfills these requirements:

  • When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)

You have tested in the following browsers: (Providing a detailed version will be better.)

  • Chrome
  • Firefox
  • Safari
  • Edge
  • IE

If adding a new feature, the PR's description includes:

  • A convincing reason for adding this feature
  • Related documents have been updated
  • Related tests have been updated

To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it.

Other information:

Copy link
Contributor

@haoranpb haoranpb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi,

I think we should fix it with the new syntax. What do you think?

This is my first review ever, sorry if I'm doing anything wrong.

Best Regards.

before: info => `<template #${info}>`,
before: info => `<template slot="${info}">`,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is still working fine since this is a <template>

Comment on lines 22 to 25
<slot
name="sidebar-top"
#top
slot="top"
/>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The new v-slot syntax can only be added to a <template>, so the code below should fix it

<template #top>
  <slot name="sidebar-top"/>
</template>

Comment on lines -3 to +4
<CarbonAds #sidebar-top/>
<BuySellAds #page-bottom/>
<CarbonAds slot="sidebar-top"/>
<BuySellAds slot="page-bottom"/>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can only use the new v-slot on the component when name is default

<template #sidebar-top>
  <CarbonAds/>
</template>

@kefranabg
Copy link
Collaborator Author

Hi @ludanxer, thanks for doing a review 🙏
Actually, I'm wondering if the new slot syntax is really more readable in this specific case 🤔

@haoranpb
Copy link
Contributor

Well, I can't stop thinking it's a template with an id top...

But the old one won't be supported anymore in vue3.0.

I tied to extend Sidebar.vue and Page.vue directly, and got lots of errors.

@haoranpb
Copy link
Contributor

Hi @kefranabg ,

I just noticed that PR #1951 already tried to fix this with the new syntax.

@ulivz
Copy link
Member

ulivz commented Oct 21, 2019

Just closed this in favor of #1951 .

@ulivz ulivz closed this Oct 21, 2019
@kefranabg kefranabg deleted the fix/slots branch October 23, 2019 08:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Carbon ads are not displayed anymore
3 participants