let timer; // Timer identifier const waitTime = 500; // Wait time in milliseconds // Search function const search = (text) => { // TODO: Make HTTP Request HERE }; // Listen for `keyup` event const input = document.querySelector('#input-text'); input.addEventListener('keyup', (e) => { const text = e.currentTarget.value; // Clear timer clearTimeout(timer); // Wait for X ms and then process the request timer = setTimeout(() => { search(text); }, waitTime); });

// Get the input box let input = document.getElementById('my-input'); // Init a timeout variable to be used below let timeout = null; // Listen for keystroke events input.addEventListener('keyup', function (e) { // Clear the timeout if it has already been set. // This will prevent the previous task from executing // if it has been less than <MILLISECONDS> clearTimeout(timeout); // Make a new timeout set to go off in 1000ms (1 second) timeout = setTimeout(function () { console.log('Input Value:', textInput.value); }, 1000); });

In order to execute an event listener (or any function for that matter) after the user stops typing, we need to know about the two built-in JavaScript methods setTimeout(callback, milliseconds) and clearTimeout(timeout): setTimeout is a JavaScript method that executes a provided function after a specified amount of time (in milliseconds). clearTimeout is a related method that can be used to cancel a timeout that has been queued.

Research shows that people who are asked to write on complex topics,instead of being allowed to talk and gesture about them, end up reasoning lessastutely and drawing fewer inferences.

Different independent studies indicate that writing byhand facilitates understanding. In a small but fascinating study, twopsychologists tried to find out if it made a difference if students in alecture took notes by hand or by typing them into their laptops(Mueller and Oppenheimer 2014). They were not able to find anydifference in terms of the number of facts the students were able toremember. But in terms of understanding the content of the lecture,the students who took their notes by hand came out much, muchbetter. After a week, this difference in understanding was still clearlymeasurable.

"The main lesson is that even though they were all good at recognizing letters, the writing training was the best at every other measure. And they required less time to get there," lead author Professor Robert Wiley, from the University of North Carolina, Greensboro, said in a statement. "With writing, you're getting a stronger representation in your mind that lets you scaffold toward these other types of tasks that don't in any way involve handwriting." Every participant in the study was an adult but the scientists are confident that the same for children. The key, they argue, is that handwriting reinforces what is being learned about the letter, such as the sound, beyond their shape. "The question out there for parents and educators is why should our kids spend any time doing handwriting," explained senior author professor Brenda Rapp, from Johns Hopkins University. "Obviously, you're going to be a better hand-writer if you practice it. But since people are handwriting less then maybe who cares? The real question is: Are there other benefits to handwriting that have to do with reading and spelling and understanding? We find there most definitely are."

In mutations, when errors happen, the other fields may return nil. So, if those other fields have null: false, but they return nil, the GraphQL will panic and remove the whole mutation from the response, including the errors!

In order to have the rich error data, even when other fields are nil, those fields must have null: true so that the type system can be obeyed when errors happen.

dlbink is a good example, since thestructure of the input query directly controls the stucture of thereturn type. The sever has no way to deal with that when the query isparsed and planned, so you have to help it out.

Explicit types for function return values and arguments makes it clear to any calling code what is the module boundary's input and output.

result["result.policy.default"].success?

Perhaps we should detect URLSearchParams objects differently (using duck typing detection instead of instanceof window.URLSearchParams, for example) but the solution isn't adding a specific polyfill to Axios (as it'd increase the bundle size and still won't work with other polyfills).

To check whether a data type is iterable look at the method Symbol.iterator.

the promise specification explicitly does not make a distinction

All valid JavaScript code is also TypeScript code. You might get type-checking errors, but that won't stop you from running the resulting JavaScript.