You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is a protocol that allows servers to recieve request from different domains to bypass a browser security feature that restricts cross-origin HTTP requests that are initiated from scripts running in the browser
(Same origin policy)
Why is it necessary?
Allows a server to relax the same-origin policy.
Why is this important for the Capstone?
To make cross-domain requests possible in cases where it is legitimate to do so like working on a full-stack app for Capstone.
To make sure we can make safe requests form the browser so developers can get the needed data.
Issue: #65 Add error messaging to FE Profile container when phone number is not the right format
Approach:
Where will you start in tech codebase, and why did you decide to start there?
First get some familiarity with the README see if anything pops out to set the stage for what I should be looking for, also a good way to get a first look at DB schema
Take a look at gem file to see what we are working with
Take a look at schema and models to see the relationships
Now in context of the issue, we are dealing with messaging/phone numbers so I am going to go look for where that functionality is and is tested. In this case, I see that the phone number is part of the SMS API service being consumed by the BE.
I see that an error is occuring in the SMS service on the BE if the phone number is not a good format.
However, the issue references the error messaging on the FE Profile Container, so I am going to navigate to the FE codebase to find this Profile Container (Javascript). I am