ignorant | ignorant allows you to check if a phone number | Plugin library

I'm working on scripting the setup of our dev machines via chocolately, etc. and I've gotten it to install VS Code, but my attempts to script adding extensions end in failure.

So I have a custom programming language, and in it I am doing some math formalization/modeling. In this instance I am doing basically this (a pseudo-javascript representation):

I have the following curl command that, when run from command line, works perfectly:

Can I get some help implementing a function that counts the number of cases?

First of all, I'm sorry to ask you the same question over and over again.

I've been trying to implement the function for more than a week, but I don't get the hang of it.

This is the code I wrote now.

How to host React app in a way, that it uses the domain of the husk HTML instead of having it configured in some config.js as suggested in another answer ( Dynamic configuration variables in Javascript / React )?

The react JS is hosted under same domain as the application API. It is assumed root is always used per application, not subdirectory, so just https://some.domain can be baseUrl. Dev setup for React is not of interest for PROD, and can be set up separately.

For example, there can be many domains, which the same JavaScript code should serve.

Why it is so simple with the normal js code, which can be ignorant of domain, and a problem with React?

Backend is not Node.js, but even backend gets it's domain from HTTP headers, so having to configure React seems very odd.

Is there any way better than having some configuration transponder on the backend?

The idea is that React code is stored without any lists of possible domains as is suggested everywhere. At the moment it needs to be specially build for each domain separately, which is not convenient, and in described scenario of same domain it should be avoided. What can be put into src/config/index.js to make it sense the domain dynamically?

The React works with API only.

I'm new to Python as well as using the Spyder IDE. When I was writing example codes and learning about for loops, I had noticed that I had forgotten to put the colon after for loop and Spyder corrected it for me automatically when I pressed enter to go to the next line. I want to turn off this behavior. However, I do not want to turn off auto-predict. I want to turn it off since I want to learn the syntax properly and not be ignorant of the correct way of writing code.

Dialogflow, and Google Cloud Console, refuses to publish my fulfillment code that I made on the Inline Editor.

Here is a code snippet from my index.js file:

How can I put data into object values in an array in javaScript? I am taking data from the backend using axios and useEffect hook! taking data I need to push that data into an object which is inside of the array! code I wrote doesn't work and ignorant! there is a JS question!

First of all, let me start by saying that I am using Angular 10 with the Nebular UI Library for the front-end, Node.js for the back-end API, and JWT with the email/password strategy for authentication. I have noticed that for every time the user sings-in and signs back out without refreshing the application, a new duplicate sign-out request is made to the server (multiple http requests are being sent out). If you refresh the application after you sign back out though, the problem goes away. I'm not sure if I'm skipping something or I'm simply ignorant on the right way to log out and sign back in using JWTs, but I've been trying to find a solution to this problem for days now with no success so I'm eager for some help.

Current behavior:

If the user were to sign in and logs back out again more than once, the sign-out request made to the server is duplicated. This issue persists REGARDLESS of if you use an http interceptor (NbAuthJWTInterceptor or otherwise).

Expected behavior:

If the user were to sign in and log back out again, there should be NO redundant sign-out requests made to the server regardless of how many times the user repeats these steps without refreshing the app.

Steps to reproduce:

1. The first time the user signs in everything works fine and there are no duplicate requests made to the server when you log out.
2. After you sign back in for the 2nd time and sign out for the 2nd time without refreshing the application, the 2nd sign out request you make to the server will send out a duplicate sign-out request (2 identical sign-out requests are sent to the server).
3. If the user signs in again for a 3rd time and signs back out for a 3rd time, then 3 sign-out requests will be sent to the server (a total of 3 identical requests sent out).
4. If the user were to sign in and log back out again, the sign-out request would sent be duplicated one more time and a total of 4 identical sign-out requests would be sent out. This continues indefinitely.

Here is a screenshot from my dev-tools network tab for these 4 steps (after signing-in and signing back out 4 times):

Related code: On the client side I have the header.component.ts file from which the sign out process is initiated: