- Feb 2021
-
alistapart.com alistapart.com
-
Since CSS doesn’t (yet) offer a way to style grid cells, areas, or tracks directly, we have to stretch elements over the parts we want to style independently from the elements that contain content.
-
They likely won’t have any content, making them a sort of structural filler to spackle over the gaps in Grid’s capabilities.
-
- Jan 2021
-
www.emailonacid.com www.emailonacid.com
-
-
The Gmail Android app that comes pre-installed with most new Android phones contains a feature to access non-Google accounts using POP and IMAP. Unfortunately, emails accessed through this setup lack the embedded style (<style>) support as well as the support for background images.
-
-
stackoverflow.com stackoverflow.com
-
Great, I can use vw to scale text so it doesn't look puny on a desktop! Perfect... Oh. Huh, now the text is too small to read when viewed on a phone. Okay, well I can just use "max(x,y)" to make sure it doesn't get shrunk beyond a minimum size. Perfect... Oh. Hmm. Looks like "max" isn't supported properly by Chrome. Okay, well guess I'll just use "px" again.
-
-
-
Interesting . That feature (<slot slot="..."/>) was only recently added in #4295. It wasn't primarily intended to be used that way, but I guess it's a good workaround for this issue. I'm yet to find caveats to slotting components that way, other than it's inconvenient, as opposed to <Component slot="..."/>.
-
-
github.com github.com
-
Related to #1824, can do <svelte:component this={Bar}> <slot></slot> <slot name="header" slot="header"></slot> </svelte:component> <script> import Bar from './Bar.svelte'; </script> as a forwarding workaround
-
-
github.com github.com
-
In 3.29.0 you can now use <slot slot='...'> to forward slots into a child component, without adding DOM elements.
-
-
svelte.dev svelte.dev
-
https://github.com/sveltejs/svelte/issues/1037#issuecomment-737872461
Explanation (from https://github.com/sveltejs/svelte/issues/1037#issuecomment-739458005):
@AlexGalays register is an action created and passed in from the parent node (Wrapper) which allows the child to register with it. Not builtin to svelte.
That's very clever @PatrickG. Nice one. I was a bit confused when first looking at it to understand what was going on, but I think that will be a handy tool in the toolbox.
But why do we need this? If we remove all use:register, it still toggles just fine. Seems the only benefit is that this allows cleanup.
-
-
github.com github.com
-
A Svelte component that monitors an element enters or leaves the viewport/parent element. Performant and efficient thanks to using Intersection Observer under the hood. Can be used in multiple projects including lazy loading images, infinite scrolling, playing/pausing the video when in the viewport, tracking user behaviour firing link pre-fetching and animations and many many more.
-
-
atomiks.github.io atomiks.github.io
-
It's a generic abstraction for the logic and styling of elements that pop out from the flow of the document and float next to a reference element, overlaid on top of the UI.
-
-
ux.stackexchange.com ux.stackexchange.com
-
Material Design guidelines don't specify popovers, but the specification of material properties provide a clear set of properties that can be used to create popups.
-
-
fontawesome.com fontawesome.com
-
A hosted Kit is the easiest way to add Font Awesome to your website. It's a collection of icons, styles, and settings that allows you to make changes and update versions without pushing code.
Tags
Annotators
URL
-
- Dec 2020
-
www.gimpusers.com www.gimpusers.com
-
It works very well, especially since the current Gimp roadmap relegates CMYK support to a version Gimp 3.2 However to be fairquoteShould a new developer join the team to specifically work on CMYK-related features, we will do our best to help him/her to complete this project and get it to our users as soon as possible.unquoteNot holding my breath.
-
-
github.com github.com
-
I guess it's about "preloading" and not "navigation", if it's the case, then I guess there is still no way to attach to navigation events, and this issue should be kept open.
-
No JS event is fired, so there currently isn't any clean way to do this that I can see.
-
-
sozi.baierouge.fr sozi.baierouge.fr
-
Press these buttons to move to the previous/next frame
-
-
www.npmjs.com www.npmjs.com
-
No more waiting around for pull requests to be merged and published. No more forking repos just to fix that one tiny thing preventing your app from working.
This could be both good and bad.
potential downside: If people only fix things locally, then they may be less inclined/likely to actually/also submit a merge request, and therefore it may be less likely that this actually (ever) gets fixed upstream. Which is kind of ironic, considering the stated goal "No more waiting around for pull requests to be merged and published." But if this obviates the need to create a pull request (does it), then this could backfire / work against that goal.
Requiring someone to fork a repo and push up a fix commit -- although a little extra work compared to just fixing locally -- is actually a good thing overall, for the community/ecosystem.
Ah, good, I see they touched on some of these points in the sections:
- Benefits of patching over forking
- When to fork instead
-
Yarn only runs the postinstall hook after yarn and yarn add, but not after yarn remove. The postinstall-postinstall package is used to make sure your postinstall hook gets executed even after a yarn remove.
Tags
- irony
- missing feature leading to less-than-ideal workarounds
- forking to add a desired missing feature/change
- pull request stalled
- unfortunate workarounds
- limitations leading to workarounds
- maintaining a fork while waiting for upstream to merge
- making it easy to do the wrong thing
Annotators
URL
-
-
-
It seems being able to bind:this={slotEl} directly on a slot element is a popular request. I'll add my +1 as adding div wrappers just to get dom references gets old really fast.
-
-
developer.mozilla.org developer.mozilla.org
-
This creates an options object with a getter function for the passive property; the getter sets a flag, passiveSupported, to true if it gets called. That means that if the browser checks the value of the passive property on the options object, passiveSupported will be set to true; otherwise, it will remain false. We then call addEventListener() to set up a fake event handler, specifying those options, so that the options will be checked if the browser recognizes an object as the third parameter.
-
-
gamefaqs.gamespot.com gamefaqs.gamespot.com
-
I also would like to see any hidden blocks or dev shortcuts.
-
I'm more bothered by the fact that you can't practice other people's levels, just certain parts of the level, before actually going back and trying to beat it completely.
-
- Nov 2020
-
github.com github.com
-
You can also see this repo: default-passive-events.
-
-
github.com github.com
-
Not being cancelable makes validating dialog content impossible - eg a login dialog or anything that takes user input. Of course, it's easy enough to get around - but I think this should be a requirement of a dialog.
-
-
github.com github.com
-
It is impossible to rebuild the base from the Dockerfile as the 3rd party dependencies have changed significantly since 8 months ago when the base was last built. The tags for my base image have been overwritten and I can only restore them from a descendant image. With Docker 1.8 I simply pulled the descendant image, tagged the base layer and I was done. With Docker 1.10+ I'd need to save, then manually construct the base image descriptor and reload it. Doable but sad that it's far more complex.
-
Allowing parent layer metadata to be saved for a layer, regardless if the parent layer is in the save command, would be a huge win for those of us working on CI/remote systems. Reusing parent layers used to be ridiculously easy. It would be good if we could get some comparably easy way to do it now.
-
It used to be great that I was able to select a layer from any image and use it as a starting point. Currently, I am given an image that has 4 layers to be stripped off to get to the original base image. The original image is not reconstructable in any other way.
-
-
github.com github.com
-
Supersedes (and first sighting at): https://github.com/wycats/javascript-decorators
-
-
stackoverflow.com stackoverflow.com
-
# Run once, hold otherwise if [ -f "already_ran" ]; then echo "Already ran the Entrypoint once. Holding indefinitely for debugging." cat fi touch already_ran
-
Edit this file (corresponding to your stopped container): vi /var/lib/docker/containers/923...4f6/config.json Change the "Path" parameter to point at your new command, e.g. /bin/bash. You may also set the "Args" parameter to pass arguments to the command. Restart the docker service (note this will stop all running containers):
-
-
github.com github.com
Tags
Annotators
URL
-
-
stackoverflow.com stackoverflow.com
-
I came over from Vue as well, the out-in is one thing I miss with Svelte. Rich Harris even acknowledged it prior to Svelte 3 but never really implemented a fix as far as I'm aware.
-
-
imfeld.dev imfeld.dev
-
Directives like ng-if="info.report.revenue" sort of work in Angular if info.report is undefined, in that the ng-if becomes false. But the Svelte equivalent {#if info.report.revenue} throws an error. For now we're using lodash get in places where we need to and looking forward to Svelte support for optional chaining.
-
-
github.com github.com
-
This is not an MDC Web component. It is an addition that SMUI provides.
-
-
-
sveltematerialui.com sveltematerialui.com
-
That file is mandatory, but it can contain nothing, if you want the default theme.
Optional but still kind of mandatory. Odd.
Tags
Annotators
URL
-
-
-
In Angular CLI 6 this command has been removed, and it will not come back. Instead there is a new concept called Builders.With the new Angular CLI you can customize the build process by defining your own builders as well as using one of the builders provided by the community.
Why did they remove it if it was useful? They wanted people to be stuck in Angular CLI world? Couldn't they still provide that escape route / migration path for those that really do need/want to eject?
-
-
news.ycombinator.com news.ycombinator.com
-
Since you've been using Svelte for a few months after using React, haven't you been hit by the lack of composability in Svelte?Passing around components as variables is such a common pattern in React, and there's no good replacement in Svelte. The lack of dynamism in components and styles makes theming and crafting reusable components (outside of simple widgets) very tedious [1][2]. I'm genuinely curious how someone can come from React and not be bothered by it.
Tags
Annotators
URL
-
-
-
If this is getting implemented, I think I'll love to see both implemented. I can see a lot of use cases where I would like to encapsulate the component with additional wrappers and in another scenarios I would like to just use the component. Now i work around this using empty div but then at times it breaks the structure because of the div element and I'll have to add more class utilities to make it work. This will be a great addition for Svelte.
-
Another possible syntax is {#slot bar}<Foo/>{/slot}, which would also allow a bunch of DOM nodes and components inside the slot, without them needing to be from a single component
I like it
-
-
-
I also tried to use <!-- svelte-ignore unused-export-let --> before the script tag but still no chance.
-
-
github.com github.com
-
You can only adopt a workaround, which can be one of
-
-
github.com github.com
-
Just coming here to voice my agreement that these warnings are annoying and exist in other libraries as well. For me this happened with svelma. I didn't write the library code, so I don't have complete control over it even though I agree there is an argument to be had around whether I should be notified anyway. In either case, these warnings should be easily disabled since libraries don't always get updated over night.
-
- Oct 2020
-
stackoverflow.com stackoverflow.com
-
I use a mutator and use it's changeValue function to 'change' the value of the relevant field (I supply the same value). This in turn notifies all relevant parties of the change to the form's state, and a validation is triggered.
Nearly duplicate annotation here: https://hyp.is/I2t56hjLEeuPXIsZG-jYog/xtzmf.csb.app/
-
-
xtzmf.csb.app xtzmf.csb.app
-
Use the same value that was submitted, which ensures that a 'change' is triggered even though the value itself doesn't change. Therefore, the same value gets validated again.
Calling it "change" even though it didn't change is kind of cheating/abuse ... but I guess it's okay...??
mutateValue([name], state, { changeValue }) { // change the value to the same value, thus // triggering a revalidation of the same value changeValue(state, name, value => value); }
-
-
-
But it sounds like the library could use some way to setTouched()
-
-
-
I have a feature spec to test the Javascript behavior of the blur event, sadly Capybara's native DSL doesn't seem to support it yet.
-
-
final-form.org final-form.org
-
Wondering how to get field state from multiple fields at once? People coming from Redux-Form might be wondering where the equivalent of Redux Form's Fields component is, as a way to get state from several fields at once. The answer is that it's not included in the library because it's so easy to write one recursively composing Field components together.
-
-
github.com github.com
-
Perhaps we should detect URLSearchParams objects differently (using duck typing detection instead of instanceof window.URLSearchParams, for example) but the solution isn't adding a specific polyfill to Axios (as it'd increase the bundle size and still won't work with other polyfills).
-
-
ponyfoo.com ponyfoo.comPony Foo1
-
Sometimes we can’t implement a solution that’s fully spec-compliant, and in those cases using a polyfill might be the wrong answer. A polyfill would translate into telling the rest of the codebase that it’s okay to use the feature, that it’ll work just like in modern browsers, but it might not in edge cases.
-
-
masteringjs.io masteringjs.io
-
The intuition behind POJOs is that a POJO is an object that only contains data, as opposed to methods or internal state. Most JavaScript codebases consider objects created using curly braces {} to be POJOs. However, more strict codebases sometimes create POJOs by calling Object.create(null) to avoid inheriting from the built-in Object class.
-
-
humanwhocodes.com humanwhocodes.com
-
This isn’t to say that multiplying code is good or bad – it’s a characteristic of all code regardless of quality.
-
What makes it good or bad is the quality of the code being multiplied.
-
-
-
Supporting JSX out of the box is the engineering equivalent of Mozilla supporting DRM out of the box in FireFox.
-
-
github.com github.com
-
However, in function components there really isn't much need for this pattern since you can just use JS default arguments
-
-
github.com github.com
-
We aim to support all svelte features. In some cases this is not possible. For those cases we provided feasible workarounds.
-
-
facebook.github.io facebook.github.io
-
Balanced named tags is a critical syntactic feature of the XML-style notation.
-
-
-
A program somewhat controlling it's own flow. That's the key feature that makes a programming language Turing complete.
-
A programming language is Turing complete if you can implement any possible algorithm with it.
-
-
medium.com medium.com
-
Moreover, React team even removed the “highlight updates” feature from dev tools because people used to obsessively haunt wasted renders with no reasoning behind it
-
-
github.com github.com
-
I discovered that a solution can be hacked using an {#if}, but a proper one would be nice:
-
-
-
-
Here's a proxy store I wrote to derive the value of a store nested within other stores, it plays nice with typescript and can go infinitely deep
-
(Note sure if this is a feature request or a bug...)
-
-
-
But of course this could be overused.
-
<p>{(x *= 4)} {(x *= x)} {(x *= x)}</p>
Tags
Annotators
URL
-
-
github.com github.com
-
This reactive statement is just used to have the store automatically subscribed and unsubscribed.
-
I'm suggesting there should be a way to write lifecycle related code that also responds to changing props, like how useEffect works. I think how React handles this could be a good source of inspiration.
-
One thing I considered was abusing a custom store for this kind of thing.
Tags
- use as inspiration
- missing feature leading to less-than-ideal workarounds
- copying/doing the same as how another project/library did it
- feature proposal
- Svelte: store: custom
- inspiration
- learning from others
- Dylan Vann
- copying ideas from another project
- abuse of feature
- Svelte: store
- excellent writing
- can we do even better?
- learning by studying/emulating/copying others who do it well
Annotators
URL
-
-
dylanvann.com dylanvann.com
-
the code is a bit verbose/convoluted
-
-
dylanvann.com dylanvann.com
-
Using another reactive statement with $effect we have Svelte automatically handle subscribing and unsubscribing to the store
-
-
bookbook.pubpub.org bookbook.pubpub.org
-
Art by O’Hare and Bell highlight - both visually and conceptually - the dialogic quality of annotation expressing power.
While I'm reading this, I can't help but wishing that Hypothes.is would add a redaction functionality to their product. They could potentially effect it by using the highlighter functionality, but changing the CSS to have the color shown be the same as that of the (body) text instead of being yellow.
-
-
-
Solid’s State primitive is arguably its most powerful and distinctive one. Through the use of proxies and explicit setters it gives the control of an immutable interface and the performance of a mutable one
-
-
-
Solid supports most React features like Fragments, Portals, Context, Suspense, Error Boundaries, Lazy Components, Async Rendering, Implicit Event Delegation, SSR
-
-
www.youtube.com www.youtube.com
-
Building an Online Community for Behavioural Science COVID-19 Response – Prof. Ulrike Hahn. (2020, August 8). https://www.youtube.com/watch?v=noWjiDQSD14
-
- Sep 2020
-
-
I guess we could always add a bunch of adapter code to watch the flag and trigger a callback when it becomes true or false...
-
but would it be reasonable to expect svelte-select to handle that so that consumers of this lib don't have to do all that?
-
-
svelte.dev svelte.dev
-
-
Most simple example: <script> import ChildComponent from './Child.svelte'; </script> <style> .class-to-add { background-color: tomato; } </style> <ChildComponent class="class-to-add" /> ...compiles to CSS without the class-to-add declaration, as svelte currently does not recognize the class name as being used. I'd expect class-to-add is bundled with all nested style declarations class-to-add is passed to ChildComponent as class-to-add svelte-HASH This looks like a bug / missing feature to me.
-
Vue does this in a way that just makes sense.
-
TBH It is a bit disheartening to see this issue closed when all proposed solutions do not sufficiently solve the issue at hand, I really like svelte but if this is how feature requests are handled I am probably not going to use it in the future.
Tags
- missing feature that competitors have
- frustrating when maintainers stubbornly stick to opinions/principles/decisions and won't change despite popular user support
- not adding features that users really want/often request
- surprising behavior
- user can always abandon/quit/leave your site/app
- Svelte: how to affect child component styles
- feature request
- key point
- missing feature
- +0.9
- unfortunate
Annotators
URL
-
-
github.com github.com
-
It would be tiresome - and bloated - to include a class pass-through for every component or assigning custom properties (from the RFC linked) for all potential properties on every component, just in case it's gonna be used in layouts that requires it. Wrapping them in a wrapper div is certainly an option, but potentially creates 100s or 1000s (long lists, several lists etc.) of new elements in the DOM slowing down low-end devices.
-
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.
-
For my point of view, and I've been annoyingly consistent in this for as long as people have been asking for this feature or something like it, style encapsulation is one of the core principles of Svelte's component model and this feature fundamentally breaks that. It would be too easy for people to use this feature and it would definitely get abused removing the style safety that Svelte previously provided.
Tags
- forking to add a desired missing feature/change
- why this feature is needed
- run-time dynamicness/generics vs. having to explicitly list/hard-code all options ahead of time
- safety (programming)
- Svelte: how to affect child component styles
- trying to prevent one bad thing leading to people doing/choosing an even worse option
- core principles
- maintenance burden to explicitly define/enumerate/hard-code possible options (explicit interface)
- ugly/kludgey
- bloat
- 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)
- workarounds
- design goals
- verbose / noisy / too much boilerplate
- abuse of feature
- scalability
- component/library author can't consider/know ahead of time all of the ways users may want to use it
- core values
- consistency
- Svelte: CSS encapsulation
Annotators
URL
-
-
github.com github.com
-
There's no way to change style incapsulation method without patching the compiler, and this means maintaing a fork, which is not desirable.
-
Allow creating custom components with the same abilities as native dom. By all means keep the same level of encapsulation, don't push class on components, but allow a component to mark the class property or another as a CSS Class property, in which case you could pass it through the same transformation that native elements go through
-
-
github.com github.com
-
This has already forced me to forgo Svelte Material because I would like to add some actions to their components but I cannot and it does not make sense for them to cater to my specific use-case by baking random stuff into the library used by everyone.
-
-
github.com github.com
-
Your tooltip component will have to wrap your image with a span tag or something, it can’t just add events to its children. And if you are adding multiple actions to it you will have to wrap it multiple times.
<Concern1> <Concern2></Concern2> </Concern1>
vs.
<img use:concern1 use:concern2>
-
Lets not extend the framework with yet another syntax
-
and one which you don’t need to use and won’t add any code to your app if you choose not to use
Tags
- why this feature is needed
- you aren't going to need it
- keep things simple
- avoid complexity
- feature not needed; better to use a different approach/feature instead
- scalability
- programming: multiple ways to do the same thing
- verbose
- no cost if feature not used (only included in bundle if used)
- Svelte: action (use:)
Annotators
URL
-
-
github.com github.com
-
And of course, if you don't use them you don't pay for them
-
Why not just do something like this?
-
I'm still confused about the need for this, so at the expense of continuing to be that obnoxious kid at the playground, I'm going to stick my neck out again.
-
Devil's advocate: I'm not convinced the functionalities you list can't already be done within the JS of the component. Example: autofocus can simply be done w/ a method or oncreate.
-
You can imagine the ensuing combinatorial explosion if we needed to add borders or box shadows or filters or what-have-you.
-
I'm just pushing on the "is this really a good idea" front
-
If this was tied into Svelte's flow with hooks this would not be necessary since it would know when it was being removed from the DOM.
-
You must: reference each element you are extending using refs or an id add code in your oncreate and ondestroy for each element you are extending, which could become quite a lot if you have a lot of elements needing extension (anchors, form inputs, etc.)
-
This is where hooks/behaviors are a good idea. They clean up your component code a lot. Also, it helps a ton since you don't get create/destroy events for elements that are inside {{#if}} and {{#each}}. That could become very burdensome to try and add/remove functionality with elements as they are added/removed within a component.
-
Drag and drop might be done better with hooks than components.
-
This can and should be done with other components, IMHO.
-
The other possible route would depend on #640 (dynamic components), plus the ability to pass around element names as strings in place of components, plus #195 (spread).
-
I'm a lot softer on this feature now - I'm starting to believe that every single use case that you would use a hook for, you could/should use a component for.
-
Tags
- difficult/hard
- computing: history
- why this feature is needed
- you aren't going to need it
- feature/issue/bug dependencies
- use cases
- no cost if feature not used (only included in bundle if used)
- framework taking care of responsibility so users can leverage it and not have to worry about that responsibility themselves
- combinatorial explosion
- too hard/difficult/much work to expect end-developers to write from scratch (need library to do it for them)
- from different perspective/point of view
- just use/do...
- design goals
- library/framework could make this easier
- feature not needed; better to use a different approach/feature instead
- scalability
- feature proposal
- naming
- svelte
- Svelte
- could be easier / more difficult than it needs to be
- Svelte: action (use:)
Annotators
URL
-
-
github.com github.com
-
Ideally, you should be able to write pure css in style tags in components, just like you can other frameworks(React or vue)
-
-
github.com github.com
-
CSS encapsulation is a critical feature of single file components in Svelte; it allows you to think only about the styles that live together in a given component. Managing CSS has long been one of the more challenging aspects of building for the web; we have no desire to bring those problems back via official APIs that encourage the de-scoping of CSS. We do not wish to revisit the age of namespaced CSS selectors and required preprocessors.
-
-
I understand what you're getting at, but we shouldn't miss out on useful features just because a few developers will abuse it...
-
-
github.com github.com
-
And normally, accepting a class prop is documented in the component's props, so passing a class prop to a component that doesn't utilize it, and see no effect is not surprising at all, in the sense that passing any undocumented prop normally mean that it will have no effect.
-
The nice thing with this implementation is that it doesn't have any overhead or modified behavior for code that doesn't use the feature. If you don't like, no harm done, you can just ignore it.
Tags
Annotators
URL
-
-
-
Syntax-wise, I would like to be able to pass id, style and class DOM attributes as well as (ideally) svelte props to whatever the slot was replaced with, so prefixing everything with attr in the slot that should be passed sounds like a good idea. Examples: <slot attr:class=“test” attr:class:active={true} /> or <slot attr:style=“color: red” attr:id=“henlo” />
-
-
svelte.dev svelte.dev
-
If your reaction to the video was 'fine, but if we use TypeScript and write plugins for each editor then we can get all the autocomplete and syntax highlighting stuff' — in other words, if you believe that in order to achieve parity with CSS it makes sense to build, document, promote and maintain a fleet of ancillary projects — then, well, you and I may never see eye to eye!
-
-
cep.lse.ac.uk cep.lse.ac.uk
-
Carozzi, F., Provenzano, S., Roth, S. (2020). Urban Density and Covid-19. Retrieved from http://cep.lse.ac.uk/pubs/download/dp1711.pdf
-
-
github.com github.com
-
Secure-by-default is a great approach, but this is not that. It's not even, we know what's best. It's clean up your act or you're out. You really should provide an opt-in to running with scissors. Maybe like config.opt_in_to_dynamic_routes_you_dumbass = true. 1 Pick your reaction
-
I too would like to know more about the security concerns that are the motivation to remove these useful dynamic routing components. The only thing I can think off is someone who accidentally exposes a private method public, is there more? The dynamic routes are a great way to keep the routing.rb DRY and avoid unneeded dependencies between the routing and the controller files, it has been quintessential Rails magic since version 1.0, surely there must be more serious security concerns to give up such important benefits? What are they? Do we really need to completely remove this from the code base, when removing it from the default routes.rb already would get you most of the security benefit?
-
I'm sure the security overlords have our best interest in mind and I'd be happy to change my opinion if someone can explain this tradeoff better. I know I can recreate the functionality for myself but I also like to keep in mind what's best for Rails. Just a hand wavy "we've had this for almost 10 years, but it might become an issue in the future so let's preventively eliminate it" does not seem a good enough reason to cut a feature that can make code much more DRY and elegant.
-
-
ccforum.biomedcentral.com ccforum.biomedcentral.com
-
Hupf, J., Mustroph, J., Hanses, F., Evert, K., Maier, L. S., & Jungbauer, C. G. (2020). RNA-expression of adrenomedullin is increased in patients with severe COVID-19. Critical Care, 24(1), 527. https://doi.org/10.1186/s13054-020-03246-1
-
-
stackoverflow.com stackoverflow.com
-
being able to compose multiple components' functionality via decoration (not creating new "combo" components or something) is more elegant, and something I wish React had.
-
Sounds like Mixins are on their way out
-
- Aug 2020
-
-
-
As a result, I end up quoting multiple people, sometimes quoting several people back-to-back, before even writing my reply. In those instances it feels like I'm not properly citing those individuals. I feel like it might seem I'm not providing new readers appropriate context for a given quote. It might also be implied that separate quotes are from the same person, leading to mis-attribution.
-
-
covid-19.iza.org covid-19.iza.org
-
Urban Density and COVID-19. COVID-19 and the Labor Market. (n.d.). IZA – Institute of Labor Economics. Retrieved July 30, 2020, from https://covid-19.iza.org/publications/dp13440/
-
-
steamcommunity.com steamcommunity.com
-
What is Search, Anyway?Steam Search does more than just looking up games; it's a powerful tool that drives many of our discoverability features, including Top Sellers and Specials pages. Today's features are available anywhere the Search tool is used across the store.
-
- Jul 2020
-
bugs.ruby-lang.org bugs.ruby-lang.org
-
bugs.ruby-lang.org bugs.ruby-lang.org
-
bugs.ruby-lang.org bugs.ruby-lang.org
-
Old patch: https://github.com/ruby/ruby/pull/128/files
-
If you're having to look at GitHub, it seems like you didn't find a situation yourself where the requested feature would make you happier. I would advice you not to attempt to find use cases beforehand, just let them find you.
-
-
gitlab.com gitlab.com
-
bugs.ruby-lang.org bugs.ruby-lang.org
-
Besides, this will just end up being reported as a security bug to the security list if left as is, cause docker will eat up all your disk space due to a single call site flooding STDERR forcing logs to grow forever.
-
-
-
www.ruby-lang.org www.ruby-lang.org
-
A beginless range is experimentally introduced. It might not be as useful as an endless range, but would be good for DSL purposes.
-
-
-
Added `Array#union` and `Array#difference` instance method.
It appears that this PR built on (was based on) https://github.com/ruby/ruby/pull/1747/files.
That seems perfectly reasonably to me in this case. Better than creating 2 completely independent PRs that both modified some of the same lines (requiring/forcing a conflict).
The only downside is that it arbitrarily chooses one PR to be the parent of the other, when they should more intuitively be thought of as siblings/co-equals.
I like how both PRs both say that they "This solves partially https://bugs.ruby-lang.org/issues/14097"
-
-
bugs.ruby-lang.org bugs.ruby-lang.org
-
Matz, alas, I cannot offer one. You see, Ruby--coding generally--is just a hobby for me. I spend a fair bit of time answering Ruby questions on SO and would have reached for this method on many occasions had it been available. Perhaps readers with development experience (everybody but me?) could reflect on whether this method would have been useful in projects they've worked on.
-
-
stackoverflow.com stackoverflow.com
-
Creating and calling a default proc is a waste of time, and Cramming everything into one line using tortured constructs doesn't make the code more efficient--it just makes the code harder to understand.
The nature of this "answer" is a comment in response to another answer. But because of the limitations SO puts on comments (very short length, no multi-line code snippets), comment feature could not actually be used, so this user resorted to "abusing" answer feature to post their comment instead.
See
-
-
www.algolia.com www.algolia.com
Tags
Annotators
URL
-
- Jun 2020
-
stackoverflow.com stackoverflow.com
-
What would be nice is if JavaScript had a built-in way to do what I can do in Ruby with:
> I18n.interpolate('Hi, %{name}', name: 'Fred') => "Hi, Fred"
But to be fair, I18n comes from i18n library, so JS could just as easily (and I'm sure does) have a library that does the same thing.
Update: Actually, you can do this in plain Ruby (so why do we even need
I18n.interpolate
?):main > "Hi, %{name}" % {name: 'Fred'} => "Hi, Fred"
main > ? String#% From: string.c (C Method): Owner: String Visibility: public Signature: %(arg1) Number of lines: 9 Format---Uses str as a format specification, and returns the result of applying it to arg. If the format specification contains more than one substitution, then arg must be an Array or Hash containing the values to be substituted. See Kernel::sprintf for details of the format string. "%05d" % 123 #=> "00123" "%-5s: %016x" % [ "ID", self.object_id ] #=> "ID : 00002b054ec93168" "foo = %{foo}" % { :foo => 'bar' } #=> "foo = bar"
I guess that built-in version is fine for simple cases. You only need to use
I18n.translate
if you need its more advanced features likeI18n.config.missing_interpolation_argument_handler
.
-
-
edgeguides.rubyonrails.org edgeguides.rubyonrails.org
-
Sometimes, the line between 'bug' and 'feature' is a hard one to draw. Generally, a feature is anything that adds new behavior, while a bug is anything that causes incorrect behavior. Sometimes, the core team will have to make a judgment call.
-
Please don't put "feature request" items into GitHub Issues. If there's a new feature that you want to see added to Ruby on Rails, you'll need to write the code yourself - or convince someone else to partner with you to write the code. Later in this guide, you'll find detailed instructions for proposing a patch to Ruby on Rails. If you enter a wish list item in GitHub Issues with no code, you can expect it to be marked "invalid" as soon as it's reviewed.
-
-
rails.lighthouseapp.com rails.lighthouseapp.com
-
Seems a little unfortunate that there is no obvious way to edit or remove my previous reply.
-
-
-
With inline diff tags you can display {+ additions +} or [- deletions -].
Can also use/abuse for general highlighting (background color) purposes. Too bad there's no first-class support for that, and that you can only highlight with green or red and not yellow, etc.
-
-
securitytoday.com securitytoday.com
-
The breach was caused by Facebook’s “View As” feature, which allows users to view their own account as if they were a stranger visiting it.
-
-
Local file Local file
-
inhibiting both full-length AR andAR splice variants lacking LBD.
inhibit both FL and ARv7
-
- May 2020
-
docs.gitlab.com docs.gitlab.com
-
Enable the sub-chart The way we’ve chosen to implement compartmentalized sub-charts includes the ability to disable the components that you may not want in a given deployment. For this reason, the first setting you should decide on is enabled.
-
-
gitlab.com gitlab.com
-
The Inherited Environment Variables feature is under development and not ready for production use. It is deployed behind a feature flag that is disabled by default.
Tags
Annotators
URL
-
-
developer.apple.com developer.apple.com
-
about.gitlab.com about.gitlab.com
-
We iterate to deliver features, so we often don't have functionality that people expect. For this reason, 'people could reasonably expect this functionality' does not make it a bug.
-
If people care about a missing feature, then ideally the issue should be marked as ~"Accepting merge requests"
-
-
www.addictivetips.com www.addictivetips.com
-
The context menu will have three options; Normal Reload, Hard Reload, and Empty Cache and Hard Reload. The third option is what you’re looking for. Click ‘Empty Cache and Hard Reload’ to clear the cache for a particular website.
-
-
superuser.com superuser.com
-
After opening up the developer tools (usually by pressing F12) Click + Hold on the "Reload Page" button. From the popup list, choose "Empty Cache and Hard Reload".
-
-
-
-
I want my Page Translator extension to be made irrelevant by Firefox having built-in language translation, like Google Chrome and Microsoft Edge. It is a critical feature used by millions of people daily. It bridged a feature gap. Mozilla killing this add-on without replacing it hurts users.
-
-
github.com github.com
-
I would love for Mozilla to make this extension irrelevant by providing the functionality natively. Language translation is a standard and yet highly differentiating feature in Chrome and Edge.
-
I wish Mozilla would recognize the importance of built-in translation that Google Chrome and Microsoft Edge have.
-
- Apr 2020
-
code.luasoftware.com code.luasoftware.com
-
Some variety of markdown support the following syntax, but not supported in Hugo/BlackFriday. [Lua Software](http://www.luasoftware.com){:target="_blank"}
-
-
stackoverflow.com stackoverflow.com
-
[link](url){:target="_blank"} Works for jekyll or more specifically kramdown, which is a superset of markdown, as part of Jekyll's (default) configuration. But not for plain markdown. ^_^
-
-
stackoverflow.com stackoverflow.com
-
For ghost markdown use: [Google](https://google.com" target="_blank) Found it here: https://cmatskas.com/open-external-links-in-a-new-window-ghost/
-
-
-
As serious leaks become more common, surely we can expect tougher laws. But these laws are also making it difficult for those of us who wish to improve security by studying actual data. For years we have fought increasingly restrictive laws but the government’s argument has always been that it would only affect criminals.
-
-
www.troyhunt.com www.troyhunt.com
-
A middle ground would be to recommend the user create a new password without necessarily enforcing this action. The obvious risk is that the user clicks through the warning and proceeds with using a compromised password, but at least you've given them the opportunity to improve their security profile.
-
-
www.driftingruby.com www.driftingruby.com
-
This gives your users the option to increase the level of security to their account and help prevent unauthorized access.
-
-
www.troyhunt.com www.troyhunt.com
-
Another approach I toyed with (very transiently) was blocking entire countries from accessing the API. I was always really hesitant to do this, but when 90% of the API traffic was suddenly coming from a country in West Africa, for example, that was a pretty quick win.
-
-
www.cnet.com www.cnet.com
-
Well, as a home user, I also belong to an investment club with 10 members. I also have a medium size family who I like to send photo's to, and my son is on a soccer team. all those have greater than 5 people on the list. sooooooooo..... once again, the people with valid use of the internet have to 'deal' with those that abuse it.
-
-
www.w3.org www.w3.org
-
In the early 1990s, the creators of Netscape apparently built a function that enabled each web page to be annotated by those visiting it, as a way for viewers to discuss the page’s content. But according to a [1] produced in 2013 by a nonprofit called [Hypothesis][2], the feature was turned off.
-
- Mar 2020
-
rubyworks.github.io rubyworks.github.io
-
A NackClass is the same as NilClass except for any method it does not recognize, it return the instance of itself. nack.nack.nack.nack #=> nack Note I used to call this NullClass, but "nack" seems a little more fitting a term.
-
-
-
bugs.ruby-lang.org bugs.ruby-lang.org
-
www.argotrans.com www.argotrans.com
-
Google Translate Widget
-
Another “decision” to make GoogleYoutube crappier and crappier with every passing day. The corporation seems stridently dedicated to deprecating its own products and abusing its customers.Search is now suckier than DuckDuckGo. Fuzzy and/or cherry-picked results.YouTube flooded with reposts/stolen vids and the “recommended” videos have literally nothing to do with your viewing behavior.Politicization and one-way censorship.Translator used to be nearly limitless (no text limit, websites translatable, etc) — now it’s basically a severely nerfed mini-tool to translate short phrases.
-
-
crowdin.com crowdin.com
-
Cool idea how they show which ideas they are considering, planning, and have already launched.
-
-
-
Request features
Tags
Annotators
URL
-
-
searchengineland.com searchengineland.com
-
Instant previews saw very low usage by our users, and we’ve decided to focus on streamlining the page to benefit more users.
-
-
searchengineland.com searchengineland.com
-
the feature was dropped to “lack of use.”
I don't find the reason "lack of use" sufficient in its own right. (I personally didn't use this feature.) People might not use it because they don't know about. And those that do use may find it extremely useful; it's not their fault if others don't know about it or use. It seems to discriminate a bit against the minority who may use a useful feature. They would rather be in the majority, safe from having one of their favorite features removed.
But I do understand and appreciate the good explanation given below.
-
Yes, it’s been deprecated. Why? Because too few people were using it to make it worth the time, money, and energy to maintain. In truth, although I sometimes disagree with the operator changes, I happen to agree with this one. Maintaining ALL of the synonyms takes real time and costs us real money. Supporting this operator also increases the complexity of the code base. By dropping support for it we can free up a bunch of resources that can be used for other, more globally powerful changes.
-
- Jan 2020
-
bugs.ruby-lang.org bugs.ruby-lang.org
-
I've often wished for some standard variable to use for blocks and such. Like some people here, I had considered
it
. Usually I use_
but I know that means "unused" to many/most programmers. I like the%
option that Clojure has.
-
- Dec 2019
-
github.com github.com
-
An ssh public key in a ~/.ssh/authorized_keys file can have a command="" option which forces a particular command to be executed when the key is used to authenticate an ssh connection. This is a security control that mitigates against private key compromise. This is great when you only need to execute a single command. But if you need to perform multiple tasks, you would normally need to create and install a separate key pair for each command, or just not bother making use of forced commands and allow the key to be used to execute any command.
-
-
babeljs.io babeljs.io
-
Moving forward with v7, we've decided it's best to stop publishing the Stage presets in Babel (e.g. @babel/preset-stage-0). We didn't make this decision lightly and wanted to show the context behind the interplay between TC39, Babel, and the community.
-
- Nov 2019
-
github.com github.com
-
this is not intended to become a big, public thing. You're welcome to use anything and steal any code. Please do not count on us adressing feature requests or issues though.
-
-
bugs.ruby-lang.org bugs.ruby-lang.org
-
Try doing the equivalent of #indexes without it. Not that it's especially hard, but you have to stop and work out a solutuon. When you need it, that's when you wish there were already a method for it.
-
You haven't shown any real use case yet. I don't deny that the functionality alone would be a good shortcut itself just like any other proposal we see every day.
-
-
github.com github.com
-
Feature requests are great, but they usually end up lying around the issue tracker indefinitely. Sending a pull request is a much better way of getting a particular feature into Capybara.
-
-
github.com github.com
-
I often wish for this. I don't understand why this hasn't been added.
Ugly workaround for now:
# Note, even though we don't need or use arguments passed to this selector, you *must* pass in an # argument to prevent it from matching the :id selector and giving a "Unable to find id :parent (Capybara::ElementNotFound)" error. # Example: el.first(:parent, 1) # You may also need match: first if el matches multiple elements to avoid Capybara::Ambiguous Capybara.add_selector(:parent) do xpath { ".//.." } end
-
-
github.com github.com