.
| venv/ | |
| __pycache__/ | |
| *.pyc | |
| # Audio files and transcription output | |
| *.m4a | |
| *.wav | |
| *.txt | |
| # Archives |
| export type TailwindBreakpointName = | |
| // Corresponds to Tailwind CSS default breakpoints | |
| | 'base' | |
| // Smallest breakpoint | |
| | 'sm' | |
| // Medium breakpoint | |
| | 'md' | |
| // Large breakpoint | |
| | 'lg' | |
| // Extra large breakpoint |
| import { cn } from '@/lib/utils'; | |
| /** | |
| * Represents a single definition term (dt) with zero or more definition details (dd) | |
| * | |
| * Describes what each probability category means in terms of historical distribution | |
| * | |
| * @example | |
| * ```tsx | |
| * // Single detail string |
In Design Systems use, either created ad-hoc, and managed from within a web application, when we want to support flexibiilty in color management, one recurring theme is the color variation to use as the background for a given color. Tailwind CSS helps managing some of the coplexity by allowing class names, but we still end up with the same problem. A Text color might be better with a very specific level of luminosity of the background color.
To avoid having too many Intl.NumberFormat and Intl.<...> adjacent spreaded around the code base and considering that not all browsers supports it for sure, and that there's the possibility that the code base making assumption that asking for using a locale (e.g. fr-CA) from the code base will be handled gracefully from a browser that doesn't have the language installed.
Let's have a way to have formatting created by a predictable way. Allow flexibility to have almost complete data configuration object we can get and hints about what's missing if we use them directly as they're returned.
| /** | |
| * Create an UTC date object based on an ISO yyyy-mm-dd string | |
| */ | |
| export const toUTC = (input) => { | |
| const date = new Date(`${input}T00:00:00Z`); | |
| if (Number.isNaN(date.getDate())) { | |
| throw new Error(date); | |
| } | |
| return date; |
| // fully-introspectable-component.mjs | |
| /** | |
| * A component that implements the full introspection API | |
| */ | |
| export class FullyIntrospectableComponent extends HTMLElement { | |
| /** | |
| * Attributes to observe for changes | |
| */ | |
| static get observedAttributes() { |
Typings are available on GitHub.com/obsidianmd/obsidian-api and as npm:obsidian
There's also a TypeScript types available on GitHub.com/ObsidianMD/obsidian-api as npm:obsidian