8 Matching Annotations
- Jan 2023
-
github.com github.com
-
Do you plan to continue merging MR and releaseing new versions for this Gem? I don't think there is any similar gem like this, so it would be sad to see it fade away.
-
- May 2022
-
-
Is IT Maintenance the same as IT Management? For some it may be a semantic discussion while others consider these words synonymous.
IT Maintenance and IT Management are not the same
Is IT Maintenance the same as IT Management? For some it may be a semantic discussion while others consider these words synonymous.
-
- Mar 2021
-
trailblazer.to trailblazer.to
-
With all this “monetization” happening around Trailblazer, we will also make sure that all free and paid parts of the project grow adult and maintan an LTS - or long-term support - status. Those are good news to all you users out there having been scared to use gems of this project, not knowing whether or not they’re being maintained, breaking code in the future or making your developers addicted to and then cutting off the supply chain. Trailblazer 2.1 onwards is LTS, and the last 1 ½ years of collaboration have proven that.
-
- Feb 2021
-
-
I apologize for the slow development of Reform after the "explosion" when I released it initially. The reason for this is I changed jobs and didn't use Reform (yet).
-
- Nov 2020
-
www.youtube.com www.youtube.com
-
If everyone did this, the repair shops would be out of business.
-
- 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
- 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)
- forking to add a desired missing feature/change
- run-time dynamicness/generics vs. having to explicitly list/hard-code all options ahead of time
- workarounds
- Svelte: how to affect child component styles
- trying to prevent one bad thing leading to people doing/choosing an even worse option
- maintenance burden
- maintenance burden to explicitly define/enumerate/hard-code possible options (explicit interface)
- component/library author can't consider/know ahead of time all of the ways users may want to use it
- being explicit
- burden
- ugly/kludgey
- explicit interfaces
Annotators
URL
-
-
github.com github.com
-
You can help ensure your RFC is reviewed in a timely manner by putting in the time to think through the various details discussed in the template. It doesn't scale to push the thinking onto a small number of core contributors.
-