Mention some Laravel specific incompatibilities in the wiki

Open
#17 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Stale
Tech stack
laravel
Domain
documentation

Research direction

Start with the Package-Incompatibilities wiki page linked in the issue and review the existing incompatibility note. Add entries for form validation breaking routing, including the proposed workaround and issue #584, and for withoutMiddleware returning 404 in tests, linking #571 and noting that it cannot be fixed.

Written by the indexing model from the issue text.

Description

Originally posted over at dingo/api https://github.com/dingo/api/issues/655
I want to send a Pull Request, but I just want to make sure that it's fine

Hi,

I've been using dingo/api in many applications and I noticed that users of dingo/api might need to know about the following issues in the wiki (and maybe at least about their workarounds or a link to the github issue):

  • Form Validation breaks routing - I know this is mentioned in the docs for Exceptions, but the solution is not. This might be the solution (I tried it and it works)
  • withoutMiddleware in tests returns 404 - This is something that can't be fixed, but I think it's worth noting. #571

This is the only thing mentioned in the wiki page

The API will generally work with all other packages, however, some Laravel specific packages may conflict with the API as it integrates itself heavily with the Laravel router to provide the needed functionality.

Let me know what you think!

Dominant language
No language data
Stars
19
Forks
21
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dingo/api-docs

All issues in dingo/api-docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.