[BUG] Unexpected token '<', "<!DOCTYPE "... is not valid JSON

[cdmathukiya]

Describe the bug
When I have define Route::resource in route file but not create all the methos in controller then it create this error.

To Reproduce
Steps to reproduce the behavior:

1. just define any route in route file.
2. do not create same method in controller
3. See error

Expected behavior
Output should show all the available/valid endpoints.

Versions (please complete the following information):

[kevincobain2000]

Thanks. Will check this.

[kevincobain2000]

Is the debug true in the config of LRD?

[cdmathukiya]

No, it is false

[kevincobain2000]

Thanks.
For the time being, you can try adding ->except(['show']) to the resource for the functions that are not implemented...

[alpemreelmas]

Thanks. For the time being, you can try adding ->except(['show']) to the resource for the functions that are not implemented...

I can confirm that this worked for me. I had forgetten just "show" method to call inside except method but I got this error. After adding ->except(["update","edit"]) it worked.

[kevincobain2000]

All good then? Let me know if I can close this issue.

[alpemreelmas]

All good then? Let me know if I can close this issue.

Yes, you can close this issue
Thanks

[AshirNob]

HEY,
see attached having same issue. even if i comment my all api routes, cleared cache this error doesn't go away.
also i removed my controller code still same.
what i am doing wrong here ?

[JanSuthacheeva]

I have the same error as soon as I publish the assets.

[kevincobain2000]

You don't need to publish assets on v2

[JanSuthacheeva]

Yes, but I want to add some stylings to the request page since the li and heading tags in the extra documentation are not visually different from the normal text. So I thought I publish it and track the changes in git too.

[kevincobain2000]

well...follow the traceback for hints. The error that you are seeing is when it is not able to connect to the API.

[JanSuthacheeva]

Will do it. Thanks!

[vincentdev15]

Today the bug is still there.