4 Matching Annotations
- Apr 2022
-
sde.ok.gov sde.ok.gov
-
assistive technology
We should place the definition of Assistive Technology here: Assistive Technology is technology used by individuals with disabilities in order to perform functions that might otherwise be difficult or impossible.
-
- Apr 2021
-
rampages.us rampages.us
-
theodicy
theodicy: vindication of God, explains why God would allow evil
-
- Sep 2020
-
github.com github.com
-
Svelte will not offer a generic way to support style customizing via contextual class overrides (as we'd do it in plain HTML). Instead we'll invent something new that is entirely different. If a child component is provided and does not anticipate some contextual usage scenario (style wise) you'd need to copy it or hack around that via :global hacks.
-
Explicit interfaces are preferable, even if it places greater demand on library authors to design both their components and their style interfaces with these things in mind.
Tags
- run-time dynamicness/generics vs. having to explicitly list/hard-code all options ahead of time
- maintenance burden
- component/library author can't consider/know ahead of time all of the ways users may want to use it
- trying to prevent one bad thing leading to people doing/choosing an even worse option
- Svelte: how to affect child component styles
- workarounds
- forced to fork/copy and paste library code because it didn't provide enough customizability/extensibility / didn't foresee some specific prop/behavior that needed to be overridable/configurable (explicit interface)
- explicit interfaces
- maintenance burden to explicitly define/enumerate/hard-code possible options (explicit interface)
- ugly/kludgey
- burden
- forking to add a desired missing feature/change
- being explicit
Annotators
URL
-