Feat: User Login API issue#47

[mtreacy002]

Description

Added Login User API

Fixes #47

Type of Change:

• Code

Code/Quality Assurance Only

• New feature (non-breaking change which adds functionality pre-approved by mentors)

How Has This Been Tested?

Try to login a user
Gif file: https://media.giphy.com/media/L329CK5dENhpM68PVN/giphy.gif

Checklist:

• My PR follows the style guidelines of this project
• I have performed a self-review of my own code or materials

Code/Quality Assurance Only

• My changes generate no new warnings
• My PR currently breaks something (fix or feature that would cause existing functionality to not work as expected)
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been published in downstream modules

[mtreacy002]

Update @anitab-org/bridgeintech-maintainers . I've just created Login API. Can you please review this PR. @ramitsawhney27 , do you want the test cases to be done on a separate PR or just in this one? I'm thinking of waiting for the Register API test cases PR to be approved and add Login API on top of that code base, so will do a separate PR from this one. What do you think?

[mtreacy002]

Update @anitab-org/bridgeintech-maintainers . I've just pushed latest code change to fix message display connection error response.

[isabelcosta]

@mtreacy002 I added comments according to our 1:1 today, where we discussed you can remove the Refresh API related code, as this is not a priority for MVP.

[mtreacy002]

Update @anitab-org/bridgeintech-maintainers. I have pull rebased the changes made per mentor feedback on PR #59 (Register API tests) onto this PR as well so the changes made here already in sync with changes done on PR #59.

[ramitsawhney27]

Won't this change now? should be indexed using the named tuple?

[mtreacy002]

Yes, It is now (on PR #65), already using namedtuple. This Login PR #60 was made before that namedtuple PR. I don't think I need to change in this PR since it'll be overwritten by PR #65 changes if that one also got approved after this.

screenshot from namedtuple ms_api_utils.py

The commit history showing sequence of changes

[mtreacy002]

@anitab-org/bridgeintech-maintainers . Any progress on this PR review? If there's no other changes required, can you please approve this PR?
Note: This PR is the first in line to be merged out of all the current open PRs. Thanks.

[foongminwong]

Tested User Login API here with no errors

[mtreacy002]

@ramitsawhney27 as you have reviewed tthis PR and verbally approves it in BIT weekly meeting last week, can you please give the formal approval so it can be merged? Thanks