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

[Bug?]: API route handlers not working if there is a default export #1237

Closed
2 tasks done
edivados opened this issue Jan 9, 2024 · 1 comment
Closed
2 tasks done

[Bug?]: API route handlers not working if there is a default export #1237

edivados opened this issue Jan 9, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@edivados
Copy link
Contributor

edivados commented Jan 9, 2024

Duplicates

  • I have searched the existing issues

Latest version

  • I have tested the latest version

Current behavior 😯

API route handlers not working if there is a default export.

0.3.x (works)
Open in StackBlitz

Beta 2 (doesn't work)
Open in StackBlitz

Expected behavior 🤔

API route handlers work even if there is a default export. With the exception of default and GET together.

Steps to reproduce 🕹

Steps:

Context 🔦

No response

Your environment 🌎

No response
@edivados edivados added the bug Something isn't working label Jan 9, 2024
@edivados
Copy link
Contributor Author

edivados commented Jan 9, 2024

From the docs:

API Routes do not export a default Solid component.

I take this as not supported anymore.

@edivados edivados closed this as completed Jan 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@edivados