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.

Sign up for GitHub

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

Jump to bottom

fix: asset path should not be relative to page #402

Merged
merged 1 commit into from
Jul 13, 2022
Merged

fix: asset path should not be relative to page #402

merged 1 commit into from
Jul 13, 2022

Conversation

poyoho
Copy link
Contributor

@poyoho poyoho commented Jul 12, 2022

🔗 Linked issue

❓ Type of change

  • 📖 Documentation (updates to the documentation or readme)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • 👌 Enhancement (improving an existing functionality like performance)
  • ✨ New feature (a non-breaking change that adds functionality)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

if nuxt route had multi-level. such as http://a.b.c/page1/page2/page. nuxt-bridge will throw an error.

📝 Checklist

  • I have linked an issue or discussion.
  • I have updated the documentation accordingly.

danielroe
danielroe approved these changes Jul 13, 2022
View reviewed changes
Copy link
Member

@danielroe danielroe left a comment

Choose a reason for hiding this comment

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

Thanks! ❤️

@danielroe danielroe changed the title fix: multi level route path can not found file fix: asset path should not be relative to page Jul 13, 2022
@danielroe danielroe merged commit 3df21c7 into nuxt:main Jul 13, 2022
@poyoho poyoho deleted the public-base branch July 13, 2022 15:11
@danielroe danielroe mentioned this pull request Jun 20, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@danielroe danielroe danielroe approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@poyoho @danielroe