Conversation
1d6c4f3 to
d184926
Compare
|
Hi @veloce, could I've some feedback if I am on track or not? Following, I'll list what is currently missing in this PR:
|
There was a problem hiding this comment.
Thanks for tackling this!
You're definitely on the right track. UI looks neat! (only feedback is that the status code is not aligned with the url).
Haven't looked in detail to the code, but I'm not sure why you want to improve the throttling logic to get the logs? Seems not really necessary but I may miss sth.
In the log screen, I'd add a confirm dialog when tapping the delete button.
|
Hi @veloce. Regarding the throttling logic, my previous implementation was buggy but now seems to be fixed. I also added a confirmation dialog to delete the logs, then are missing only batching and internationalisation. |
2e3f4fb to
8b62bdb
Compare
Thanks! will review asap. Batching could be done in another PR I suppose (if we ever need it). |
veloce
left a comment
There was a problem hiding this comment.
Nice work!
Internationalisation is not needed yet for this feature. We can leave the hardcoded English strings.
A widget test that test the whole log screen would be nice. Nothing fancy, but perhaps something like a test that loads the whole app (you can find example in app_test.dart), then navigates to the log screen and see the startup requests. That would test the whole logging logic at once and having a test that shows the number of requests made during app startup is not bad as well.
No need to test pagination or deletion.
| }, conflictAlgorithm: ConflictAlgorithm.replace); | ||
| } | ||
|
|
||
| Future<void> update( |
There was a problem hiding this comment.
I don't think we need this, do we?
There was a problem hiding this comment.
At the moment http logs are saved when a request is made and then updated with the status code when the response is received.
There was a problem hiding this comment.
If you would like to use the save method in an upsert manner I have to understand how to manage primary key column that is used as a cursor for the pagination logic
There was a problem hiding this comment.
No I just thought the log would never need to be updated.
There was a problem hiding this comment.
Yeah maybe was better to save the log directly when receiving the response...only difference is that we cannot save unanswered http requests.
|
Sure I'll add some tests 👌🏻 |
| _createCorrespondenceGameTableV1(batch); | ||
| _createChatReadMessagesTableV1(batch); | ||
| _createGameTableV2(batch); | ||
| _createHttpLogTableV1(batch); |
There was a problem hiding this comment.
It should be _createHttpLogTableV4 imo (as in created in version 4).
| Client call() { | ||
| const HttpClientFactory({this.onCreate}); | ||
|
|
||
| final Client Function(Client client)? onCreate; |
There was a problem hiding this comment.
Would be better named wrapClient or wrapper.
7bb35aa to
156faf9
Compare
|
@vincendep do you wish to continue working on this PR? there are a couple of renaming, and a test missing still. |
|
Hi @veloce, I would like to continue but at the moment I don't know when I will be able to do it. |
|
Since it's almost done, if you prefer, I can take it over. I can add the test and merge this. |
|
No problem at all, as you wish. |
Specs:
Implemetation:
This PR closes #699