API pings if data is ready from server, and then gives it to mobile app, desktop app or web app
Tools to check or debug api
in console, Network is where we can see which url is requested when we click Action button. So, as we can see in blue color, when we click ‘Forgot Pw’ button, that url is triggered as seen in RHS network tab.
and in LHS, we can see what to response with when {certain URL is called} aka {API endpoint}. So, LHS here is backend API docs built in Django by Backend-ers
.env folder lets you default-ize what path we want our tail URL to append with base path URL. That base path url is menioned in .env folder. .env may have more things than just base path urls.
Not only this, .env folder has other purposes too, as clarified from below
Also, we have to do git pull everytime after we do git checkout branchNewlyDevelopedFeature because I remember that one day, I couldnt deploy correctly because my to-go-and-deploy branchNewlyDevelopedFeature should have had .env updated.
.eslint.config.json - whatever stds we set for linting has to be followed as protocol in order to be valid. eg. if ‘feat’ is in eslint.config.json, then our git cmd should obey that language protocol like git commit -m “feat: feature of drop down menu fixed in this Pull Req” otherwise, compiler wont compile this git
.prettier.config.json - same context as .eslint but here it’s to standardize beauty aesthetics of code, that coder should follow - like how much spaces betn two codeblocks.
dyk that Fe developers that among breakpoints like that of tablet, mobile, computer screen, React’s minimum query only mentions css and flex specifics for <= minimum pixel width. Above pixel width has default css and flex design. this para deserves another post soon on Fe which I had been preparing
Its implementation in Elastic-Search I did;
