Plugins are ways of adding new languages or formatting rules to Prettier. Prettier’s own implementations of all languages are expressed using the plugin API.

If I follow the new examples and implement them in my code (e.g. Passkeys), how will I know if a security issue is found in the examples in the future? Currently, libraries get updated and I pull in the new version. Unless I remember to check back occasionally, I'll never know if the example code is updated or fixed.

this is a serious problem because all they need to do is automate AI research 00:41:53 build super intelligence and any lead that the US had would vanish the power dynamics would shift immediately

ZenHub’s Issue dependencies not only help teams visualize relationships between pieces of work, but they save team members a lot of time that would otherwise be lost just hunting down information.

When relying on just a list of GitHub issues and comment references to other Issues, there’s a strong possibility that visibility into how these changes impact other tasks get lost or forgotten.

def prevent_delivery_to_guests if @user && @user.guest? mail.perform_deliveries = false end end

Yes, using custom tags. Example in Python, making the !join tag join strings in an array:

I find Alt + right-click + drag to be the most convenient way to do this.

For pluggability, an endpoint is split into a Protocol and an Adapter part. This separates generic logic from environment-dependent code.

Note how a handful of default steps lead into six standardized termini, allowing to plug protocols into different adapters. Imagine replacing your self-written API adapter with a canonical JSON-API adapter, for example.

Better yet, send them a link to this page to help them understand why and how to make an example app:

Configurable syntax! You can add new rules and even replace existing ones.

Community-written plugins and other packages on npm.

That’s pretty gnarly. While the name of the constant LOOSE_APP_ASSETS gives me some idea of what it does, it still takes a second to wrap your mind around. If you were trying to figure out what assets are being precompiled and you did a puts config.assets.precompile that lambda object would be utterly baffling.

Save time with AutomationsAutomate the repetitive work in seconds so you can avoid human error and focus on what matters

In addition, PPAs are awful for software discovery. Average users have no idea what a PPA is, nor how to configure or install software from it. Part of the point of snap is to make software discovery easier. We can put new software in the “Editor’s Picks” in Ubuntu Software then people will discover and install it. Having software in a random PPA somewhere online is only usable by experts. Normal users have no visibility to it.

With the new plugin based architectue, the library has really small core. Everything else is built around as a plugin.

To be clear, I have a reasonable workaround. I'd only like it to be less difficult to discover. At a minimum, this issue should help others find it...

Everyone has an idea about how to make it easier to find needles in the haystack, but no-one bothers to ask what all this hay is doing here in the first place.

Or, to echo @jeremy in #24417 (comment 215479841): Yay for hotkeys, but I had no idea until ... Let's make this useful feature more discoverable!

"2 years ago": Note that you can already automatically quote part of a previous comment by selecting it and pressing the r key. Me: Wait, what, you mean this feature — which I have often wished for, and people keep asking for (#217171, opened 2 months ago) — has already existed in GitLab for over 2 years and I just didn't realize it?! In fact, I was just coming to suggest this feature when I found these existing open issues. :)

Yes I agree. No one brother to find this feature except system admin and no one know a R shortcut.

I just learned (from #24417 and #21316) that this feature actually exists already — it's just only available via a hot key (select some text and press r to quote some text for reply) so it's not easily discoverable.

On a side note, I just learned that you can do this now by highlighting text in an issue and pressing r. Yay for hotkeys, but I had no idea until I read about it in https://gitlab.com/gitlab-org/gitlab-ce/issues/43716

"Splitters can be lumped more easily than lumpers can be split"

For example, if error messages in two narrowly defined classes behave in the same way, the classes can be easily combined. But if some messages in a broad class behave differently, every object in the class must be examined before the class can be split. This illustrates the principle that "splits can be lumped more easily than lumps can be split".