Changing auth service from Typescript to Java with Spring boot #26
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
Update development branch
Update development branch to last stage of main
updating development branch with main branch
…e client to new auth api
…e client to new auth api
Victor-Palha
added
documentation
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.
This pull request includes several changes across multiple files in the
AshChatNativeproject, focusing on updating configurations, permissions, and improving code consistency. The most important changes include the change from NodeJS to Java with Spring Boot on the Auth Service and apply theses changes on the Client Mobile #12 .Other important part from this PR is the fact that it resolves the problem about the sharing from the Unique Device ID between auth service and chat service. Now every time the auth service updates the device token, the RabbitMQ sends a message to Chat service to update there too #22 resolving this issue.
Now the Auth Service are complete with unit and e2e tests to validate every step from the project and using Swagger to maintain the documentation.
The responses and requests to auth service still basic the same, but now every controller are follow the same pattern of response.
The dockers file was updated to use spring boot and the documentation are updated too.
😎👌🏻