| /** | |
| 电信 | |
| 中国电信手机号码开头数字 | |
| 2G/3G号段（CDMA2000网络）133、153、180、181、189 | |
| 4G号段 177 | |
| 联通 | |
| 中国联通手机号码开头数字 |
| # It might work in 4, but I'm not testing there. Lower you'll have to tweak code | |
| #requires -Version 5.0 | |
| param( | |
| # Your Live ID for MSDN login | |
| [Parameter(Mandatory)] | |
| [PSCredential] | |
| [System.Management.Automation.CredentialAttribute()] | |
| $Credential, | |
| # Pick a browser to use. Defaults to Firefox (which doesn't seem to require an external Driver file) |
| import HighlightJS from 'highlight.js' | |
| createHighlightedCodeBlock (content, language) { | |
| let lineNumber = 0 | |
| const highlightedContent = HighlightJS.highlightAuto(content, [language]).value | |
| /* Highlight.js wraps comment blocks inside <span class="hljs-comment"></span>. | |
| However, when the multi-line comment block is broken down into diffirent | |
| table rows, only the first row, which is appended by the <span> tag, is | |
| highlighted. The following code fixes it by appending <span> to each line |
Sometimes, when rebasing interactively with git, we need to squash a sequence of commits in a branch.
For example, we need to transform this:
pick 0253dc894f bumped
pick 5a1e86933c remove dependency
pick bffoffb395 memberships rpc resource
pick 222fabf5e0 rpc membership service
pick 726a2f9a10 remove crypto logic
| import {forwardRef, useImperativeHandle, ForwardRefExoticComponent, RefAttributes, Ref} from "react"; | |
| export type Handle<T> = T extends ForwardRefExoticComponent<RefAttributes<infer T2>> ? T2 : never; | |
| export const Parent = (props: {})=> { | |
| let childHandle: Handle<typeof Child>; | |
| return ( | |
| <div onClick={()=>childHandle.SayHi()}> | |
| <Child name="Bob" ref={c=>childHandle = c}/> | |
| </div> |
The [React docs][condoc] give some example use cases for context:
Context is designed to share data that can be considered “global” for a tree of React components, such as the current authenticated user, theme, or preferred language.
The common property of these use cases is that data like the current theme doesn't change often and needs to be shared deep down the component tree, which would be cumbersome with "[prop drilling][drill]". Something else that needs to be shared everywhere is the application state when using a "single source of truth" pattern, so it would follow that the context API would help with that as well, but there's a catch: components that use context will rerender every time that the provided value changes, so sharing the whole application state through context would cause excessive render lifecycles.
| 'use client' | |
| import * as React from 'react' | |
| import { EyeIcon, EyeOffIcon } from 'lucide-react' | |
| import { Button } from '@/components/ui/button' | |
| import { Input, type InputProps } from '@/components/ui/input' | |
| import { cn } from '@/lib/utils' | |
| const PasswordInput = React.forwardRef<HTMLInputElement, InputProps>(({ className, ...props }, ref) => { |
