Status: Test has not been completed.
If config file is at root of project:
a. The test ... make a significantly annoying typescript project.
Summary:
The watch operator uses .subscribe function that creates a generator. That generator progresses forward by next() being called. This then gets evaluated to see if a re-render needs to occur and gets passed to useState.
useWatch():
useWatch.ts#L68
useWatch.ts#L184
Note: uses a syntax similar to a generator, when .next is called it executes a callback function that triggers updateValue from the useState.
Does anyone have a document they follow for having guidelines reviewing code within a team?
I read through this document today and it was helpful for this task:
https://github.com/mawrkus/pull-request-review-guide?tab=readme-ov-file
Different ways developers can review a pr
“A good plan violently executed now is better than a perfect plan next week.” -General George S. Patton, Jr.
When what is defined as a "good pattern" is setup And it is sufficiently complex. Be mindful that there are probably ways to automate and simplify.
But for the time being you need others to execute that pattern. Find the person who knows the pattern best and can accomplish the task most efficiently and accurately
Have a meeting with them and note how long the meeting took.
I need to fix all of my gists by moving them somewhere.
Each of my gists probably have a specific intended use.
I.e. book summaries - for helping people understand what I got out of a combination of books.
Current challenges: (what do I need?)
This document is
an effort to get people up to speed where they feel confident about react and javascript
I am putting together an organized list of what I grab for when solving various problems.
"what I know cold", and these are just the things that currently come to mind it can be updated later.
There are also "warm items", that I know to google and reach for when encountering a situation
an example of that would be an IIFE - immediately invoked function expression.
Cross-origin resource sharing (CORS) is a mechanism that allows restricted resources (e.g. fonts) on a web page to be requested from another domain outside the domain from which the first resource was served. This is set on the server-side and there is nothing you can do from the client-side to change that setting, that is up to the server/API. There are some ways to get around it tho.
Sources : MDN - HTTP Access Control | Wiki - CORS
CORS is set server-side by supplying each request with additional headers which allow requests to be requested outside of the own domain, for example to your localhost. This is primarily set by the header:
Access-Control-Allow-Origin
