-
-
Notifications
You must be signed in to change notification settings - Fork 73
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
Graby: Return object instead of an array #316
Conversation
*/ | ||
final class Content | ||
{ | ||
private int $status; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe instead of HTTP properties, we could just store PSR-7 response object.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As far as I remember we've added the status
to be able to retrieve it in wallabag (same as for headers
).
So maybe we can ditch both and keep one response
or httpResponse
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, though I would want to return that with Graby\Extractor\HttpClient::fetch()
. And we would still need some mechanism to pass the effective URL. I guess we can decide on that later.
0c7087f
to
a5864a4
Compare
1384824
to
cbe698a
Compare
61c1b13
to
23e2cfa
Compare
string|false is annoying.
Use `array<string>` instead of `array<string|false>|null`.
This will allow static analysis tools to work better and make Graby more usable in IDEs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good job!
No description provided.