| /* | |
| Element to slide gets the following CSS: | |
| max-height: 0; | |
| opacity: 0; | |
| overflow: hidden; | |
| transition: max-height 0.4s ease 0s; | |
| */ | |
| /** | |
| * Like jQuery's slideDown function - uses CSS3 transitions |
| # --------------------------------------------------------------------------- | |
| # | |
| # Description: This file holds all my BASH configurations and aliases | |
| # | |
| # Sections: | |
| # 1. Environment Configuration | |
| # 2. Make Terminal Better (remapping defaults and adding functionality) | |
| # 3. File and Folder Management | |
| # 4. Searching | |
| # 5. Process Management |
| <html> | |
| <head><title>Fuzzy Search</title> | |
| <script id="algorithm"> | |
| //This algorithm is an original work by Andrew Matte in Toronto, andrew.matte@gmail.com | |
| //You are completely free to do whatever you want with this algorithm but, | |
| //please credit me if the project is open source. Also there is no warranty that is it perfectly suited to your use case. | |
| //Written originally in Visual Basic to replace VLOOKUP's fuzzy lookup in Microsoft Excel | |
| //in 2014, implemented in MS-SQL, Python, and JS. | |
| //Apologies for any similarities to an algorithm you personally might have written independently. | |
| var proximity = (wordA, wordB) => { |
FWIW: I (@rondy) am not the creator of the content shared here, which is an excerpt from Edmond Lau's book. I simply copied and pasted it from another location and saved it as a personal note, before it gained popularity on news.ycombinator.com. Unfortunately, I cannot recall the exact origin of the original source, nor was I able to find the author's name, so I am can't provide the appropriate credits.
I am moving this gist to a github repo so more people can contribute to it. Also, it makes it easier for me to version control.
Please go to - https://github.com/praveenpuglia/shadow-dom-in-depth for latest version of this document. Also, if you find the document useful, please shower your love, go ⭐️ it. :)
Heads Up! It's all about the V1 Spec.
In a nutshell, Shadow DOM enables local scoping for HTML & CSS.
| import {Action, ActionCreator, Dispatch} from 'redux'; | |
| import {ThunkAction} from 'redux-thunk'; | |
| // Redux action | |
| const reduxAction: ActionCreator<Action> = (text: string) => { | |
| return { | |
| type: SET_TEXT, | |
| text | |
| }; | |
| }; |
Thanks to React hooks you have now happily turned all your classes into functional components.
Wait, all your components? Not quite. There is one thing that can still only be implemented using classes: Error boundaries.
There is just no functional equivalent for componentDidCatch and deriveStateFromError yet.
| import { captureException, flush } from '@sentry/nextjs'; | |
| import NextErrorComponent from 'next/error'; | |
| import type { ErrorProps } from 'next/error'; | |
| import type { NextPage } from 'next'; | |
| interface AppErrorProps extends ErrorProps { | |
| err?: Error; | |
| hasGetInitialPropsRun?: boolean; | |
| } |
This post was adapted from an earlier Twitter thread.
It's incredible how many collective developer hours have been wasted on pushing through the turd that is ES Modules (often mistakenly called "ES6 Modules"). Causing a big ecosystem divide and massive tooling support issues, for... well, no reason, really. There are no actual advantages to it. At all.
It looks shiny and new and some libraries use it in their documentation without any explanation, so people assume that it's the new thing that must be used. And then I end up having to explain to them why, unlike CommonJS, it doesn't actually work everywhere yet, and may never do so. For example, you can't import ESM modules from a CommonJS file! (Update: I've released a module that works around this issue.)
And then there's Rollup, which apparently requires ESM to be u
| import React from 'react'; | |
| import Jumbotron from 'react-bootstrap/Jumbotron'; | |
| import Alert from 'react-bootstrap/Alert'; | |
| import Button from 'react-bootstrap/Button'; | |
| import { FallbackProps } from 'react-error-boundary'; | |
| interface AEFProps extends FallbackProps { |