Repository navigation
fix(types): resolve TypeScript errors in FooterLayout and Showcase components - #2524
Conversation
|
@bobby404-K is attempting to deploy a commit to the recode Team on Vercel. A member of the Team first needs to authorize it. |
|
Thank you for submitting your pull request! 🙌 We'll review it asap. The estimated time for response is 5–8 hrs. In the meantime, please provide all necessary screenshots and make sure you run - npm build run , command and provide a screenshot, if it's a Video -LEGEND, which helps speed up the review. If you have questions, reach out to LinkedIn. You can see in our Leaderboard in 20 min from now!😊 Note: I maintain the repo issue every day twice at 8:00 AM IST and 9:00 PM IST. If your PR goes stale for more than one day, you can tag and comment on this same issue by tagging @sanjay-kv. We are here to help you on this journey of open source. Consistent 20 contributions are eligible for sponsorship 💰 🎁 check our list of amazing people we sponsored so far: GitHub Sponsorship. ✨ 📚Your perks for contribution to this community 👇🏻
Thanks again for your contribution! 😊 |
|
✅ Synchronized metadata from Issue #2520:
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Description
Fixes #2520
Type of Change
Changes Made
src/theme/Footer/index.tsxto import the swizzled localFooterLayoutfrom./Layoutinstead of@theme/Footer/Layout, resolvingTS2739missing properties error.export const prepareUserState = (): any => undefined;insrc/pages/showcase/index.tsx, fixingTS2614missing export errors inShowcaseFilterToggleandShowcaseTagSelect.npx tsc --noEmit) passes with zero errors.Dependencies
Checklist
npm run buildand attached screenshot(s) in this PR.