make sure magic calls on entity find the correct table name #50
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I had two tables called `pages` and `page_contents`. Beforehand when calling for example `$page->hasPageContents()` on a Page Entity then the library looks for the database wrong table `pageContents` because `__call` doesn't translate the method name from camelCase to snake_case. This commit fixes this that the snake-case table names such as `page_contents` get found. Beforehand when calling for example $page->hasPageContents() on a an entity then looks for the database wroing table `page_contents`. This commit fixes this that the snake-case table name `page_contents` gets found.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I had two tables called
pagesandpage_contents.Beforehand when calling for example
$page->hasPageContents()on a Page Entity then the library looks for the database wrong tablepageContentsbecause__calldoesn't translate the method name from camelCase to snake_case.This commit fixes this that the snake-case table names such as
page_contentsget found.