This gist was built by the community of the researchers and was scribed by Kir and Igor from the QIWI/Vulners. We are grateful for the help of all those who sent us the data, links and information. Together we can make this world a better place!
| /** | |
| * Deep copy function for TypeScript. | |
| * @param T Generic type of target/copied value. | |
| * @param target Target value to be copied. | |
| * @see Source project, ts-deepcopy https://github.com/ykdr2017/ts-deepcopy | |
| * @see Code pen https://codepen.io/erikvullings/pen/ejyBYg | |
| */ | |
| export const deepCopy = <T>(target: T): T => { | |
| if (target === null) { | |
| return target; |
| " Specify a directory for plugins | |
| call plug#begin('~/.vim/plugged') | |
| Plug 'neoclide/coc.nvim', {'branch': 'release'} | |
| Plug 'scrooloose/nerdtree' | |
| "Plug 'tsony-tsonev/nerdtree-git-plugin' | |
| Plug 'Xuyuanp/nerdtree-git-plugin' | |
| Plug 'tiagofumo/vim-nerdtree-syntax-highlight' | |
| Plug 'ryanoasis/vim-devicons' | |
| Plug 'airblade/vim-gitgutter' |
| { | |
| "suggest.noselect": false, | |
| "coc.preferences.formatOnSaveFiletypes": [ | |
| "javascript", | |
| "typescript", | |
| "typescriptreact", | |
| "json", | |
| "javascriptreact", | |
| "typescript.tsx", | |
| "graphql" |
by Richard Bullington-McGuire richard@obscure.org @obscurerichard on GitHub and Bluesky
Use these as comments in pull requests in order to charm the project owner into taking action on the pull request.
lonely pull request
the completist in me pines
for its prompt closure
| /* | |
| Copy this into the console of any web page that is interactive and doesn't | |
| do hard reloads. You will hear your DOM changes as different pitches of | |
| audio. | |
| I have found this interesting for debugging, but also fun to hear web pages | |
| render like UIs do in movies. | |
| */ | |
| const audioCtx = new (window.AudioContext || window.webkitAudioContext)() |
JavaScript warnings are these messages being displayed in yellow or red in your JavaScript console or terminal. They make no sense at all in general but they are a good indication of the health of your app. The points below will give you a general idea of how many warnings you should expect in your app:
-
0 warnings: the app is not working at all
-
5 warnings: app is probably starting but crashing soon after - try to find why it crashes. You'd think you could read the warnings to learn why it doesn't work, but that's not what warnings are for.
-
50 warnings: That's the soft spot - most likely everything's running smoothly