Skip to content

Instantly share code, notes, and snippets.

@Afoucheaux
Last active May 5, 2021 15:43
Show Gist options
  • Save Afoucheaux/70e7673094ace12492741a89b6d00b0d to your computer and use it in GitHub Desktop.
Save Afoucheaux/70e7673094ace12492741a89b6d00b0d to your computer and use it in GitHub Desktop.
Mod 4 Pre-work paired notes

Aaron Foucheaux Where will you start in the codebase, and why did you decide to start there?

My Process: Started by logging onto the app and familiarizing what it was. (Gives me an idea of how components and functionality fit together.) Read documentation and Readme / setup guide. (General overview of the project and past development notes) Run tests Looked over file structure specifically components and package.json. (package.json, lets me note anything I may not be familiar with. Quick look at the component imports gives me an idea how the components are interacting.) Dig into the components (Start looking at the components that I will need to update in order to complete the issue.)

What is familiar to you about the codebase?

Most of the code base. Easier to say what I am not familiar with. Redux, GraphQL, Enzyme React fragment .

Are you making any assumptions? If so, what are they?

I am mostly making assumptions about existing functionality, Also that testing is correct and adequate since I have not used that specific testing yet.

How are you identifying what files are relevant to your issue?

My Process: Log onto the site, open dev tools and navigate to where my feature will be added. Utilize the component tool to see relevant starting components and paths. And compared to components in the text editor. In this specific case it was only showing routes so needed to find it based on the corresponding route in containers App.js. Once we have the starting components I can review the imports and exports to find all parts of the code that may be affected. Make a quick component diagram

What is the data flow in the application?

Starting- in the containers file App. (routing components and link to dom) Next- Routing to the appropriate container file starting on SignIn / Profile. Then- Into components that are needed for the corresponding pages. Then depending on user actions the corresponding containers/components will get passed the data needed.

What is unfamiliar? (different file structures, new packages or gems, etc.)

The React element being broken up into containers and components. (File structure) along with the above mentioned. ( Redux, GraphQL, Enzyme, React fragment )

Is there technology that you would need to research?

Include the link to documentation for that technology- Redux, GraphQL, Enzyme, React fragment.

Include at least one other source, such as an article/video you might use to gain an understanding of that technology (You do not need to read/watch). https://www.youtube.com/watch?v=-bmdf1oATQo

Include what search terms you used to find that source.

enzyme testing react

@Afoucheaux
Copy link
Author

CORS prework.

  • What does CORS stand for? Cross-Origin Resource Sharing.
  • Why is it necessary? It is used to mimic the same origin policy and allow the frontend to do HTTP request from a different origin then the backend.
  • Why is this important for the Capstone? I am assuming we with have different origins and it will be a good learning experience since its seams standard in the industry.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment