-
Notifications
You must be signed in to change notification settings - Fork 30
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.
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
Cannot expand relation #237
Comments
Since I cut a release overnight, and that seems to be a POData issue,@CalamarMihai, can you try setting your POData dependency to 0.3.7 on your testbed to see if that solves your second issue? |
@CyberiaResurrection Can I propose an audit and we suspend anything AUTH related because a number of people have issues with it and the flag does not appear to work properly. |
@CalamarMihai, after seeing if explicitly including POData 0.3.7 on your testbed solves your issue or not (since I expect you're using dev-master on POData indirectly), you'll need to give me more information so I can reproduce your second issue, solve it (and, ultimately, add it as a regression test).
|
@CalamarMihai, all packaged tests are currently passing on a clean install of POData-Laravel itself as at current master HEAD ( 7727b6e ). This is just trying to constrain where the problem lurks. @c-harris , given the timing of the report, it looks like something fired up the hyperdrive and departed to east hyperspace among PRs 226 and/or 229 on POData. Given how big and gnarly 229 ended up, I'm suspecting that in lieu of further feedback. In light of that, what do you propose to audit and what do you propose to look for? |
First, I apologize for the delay.
The first issue is ok now, after reinstall, i had no issue with the authentication error. I tried the common types of relationships supported by Eloquent (belongsTo, hasOne, hasMany, etc..) Regardless of the value of parameter $expand, even if the relationship exists or not, I receive the same error. If you think it helps, I can make a copy of the project and database and put it on file sharing. Sorry for my bad english and thanks for your help. |
Thanks for your patience, your help and the extra information, @CalamarMihai . I've updated the issue title and will try to investigate in the next few days, as I'm a little busy at the moment (unless @c-harris wants to take a swing). |
I'll take a look shortly and see if we can spin up a regression test for this specific case. |
Any news about this issue? |
@CyberiaResurrection, i try on a new clean instance of laravel and now it has passed this issue, but i have another 2 new issues.
$controllerMethod = '\AlgoWeb\PODataLaravel\Controllers\ODataController@index';
Route::get('odata2.svc/$metadata', ['uses' => $controllerMethod]);
Route::any('odata2.svc/{section}', ['uses' => $controllerMethod])->where(['section' => '.*']);
Route::any('odata2.svc', ['uses' => $controllerMethod]);
Now it's working
Symfony\Component\Debug\Exception\FatalThrowableError
Argument 2 passed to POData\Providers\Metadata\ResourceAssociationSet::keyNameFromTypeAndProperty() must be an instance of POData\Providers\Metadata\ResourceProperty, null given, called in /var/www/testing/vendor/algo-web/podata/src/POData/UriProcessor/QueryProcessor/ExpandProjectionParser/ExpandProjectionParser.php on line 193
Thank you very much and I really appreciate the effort.
Originally posted by @CalamarMihai in #236 (comment)
The text was updated successfully, but these errors were encountered: