Skip to content

Conversation

@JessicaSachs
Copy link
Contributor

Description of Problem

There were some type errors in the <TeamPage> when mounting the team list. Turns out there was a typo and some type mismatches.

I was investigating vuejs/theme#36 and noticed it.

@netlify
Copy link

netlify bot commented Feb 13, 2022

✔️ Deploy Preview for vuejs ready!

🔨 Explore the source changes: 70c5e9e

🔍 Inspect the deploy log: https://app.netlify.com/sites/vuejs/deploys/6208d87dfcf02c00072871a3

😎 Browse the preview: https://deploy-preview-1529--vuejs.netlify.app

website?: Link
socials: Socials
sponsor?: string
sponsor?: boolean | string
Copy link
Contributor

Choose a reason for hiding this comment

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

From a quick search, it looks like this field is only used in one place, which uses it for a v-if. I think the handful of entries with string values are leftover from an incomplete migration and should just be switched to true instead.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Isn't there a button for sponsors? image

Copy link
Contributor

Choose a reason for hiding this comment

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

Yeah, sorry, that's what I meant. That button in TeamMember.vue seems to be the only place that uses the sponsor property and it just treats it as a boolean. There are 5 people in members-core.json that have a string value for sponsor, but I believe they should all just be switched to true, and then sponsor doesn't need to support the string type.

@JessicaSachs
Copy link
Contributor Author

JessicaSachs commented Feb 14, 2022 via email

@skirtles-code skirtles-code merged commit 38d8292 into vuejs:main Feb 14, 2022
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.

2 participants