-
Notifications
You must be signed in to change notification settings - Fork 9
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
Add chat to game-event page #96
Conversation
9bb672d
to
00d57db
Compare
Keep up the good work, is there screenshots that we can see in the meantime ? |
b587743
to
e2fc76c
Compare
did it |
fadccbe
to
e14b15a
Compare
Great job, the chat looks awesome! I really like it. |
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.
looks good just a small comment
btw if you have time to implement and not part of this PR
you can improve the chat a bit having a 5 sec loop to request the messages (no need to implement a full web socket chat) that will ask the server for messages and reload just the chat box with new messages so you don't need to refresh the page everytime
e14b15a
to
087ee3f
Compare
Thank you, I open issue for it #103 |
Great job! |
087ee3f
to
96ae0e8
Compare
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 understand it, this PR includes quite a lot of refactoring that are not directly related to the functionality being introduced. Unless the refactoring is tightly coupled with the code being introduced, it's better to split them into different PRs. It makes it less likely that you'd have uncaught regressions and it also makes it easier to review which makes it less likely to introduce new bugs.
7e7e32a
to
8c0686e
Compare
I would like to know if you talked about just the changes of the fixtures I made or other things you think it needs to be in another PR? I think the other changes related to the chat features. |
I don't recall anymore. I'll let you be the judge. |
f8c04c1
to
56d83ec
Compare
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.
Whenever we have an opportunity to test a unit (usually a function) on its own, we should prefer that over testing it inside something else.
We should also have that something-else tested, but then we should focus on its functionality rather than the functionality provided by the unit it utilize.
71059b2
to
193ba76
Compare
193ba76
to
4ce5af3
Compare
4ce5af3
to
a815a17
Compare
3ca6ef1
to
ac09499
Compare
ac09499
to
eb2090e
Compare
modify game-event html for adding the chat html adding tests for the chat adding new view function that handle the chat adding urls for the new view function
eb2090e
to
7a5c51a
Compare
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.
lgtm. Good job!
Desired Outcome
Players will be able to chat with each other in the specific event. Only the players
who joined the event, will be able to enter the chat.
Implemented Changes
Connected Issue/Story
Resolves #95
Dependencies
Test coverage
changes
Documentation