# autocomplete Published articles for autocomplete. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Build Hints That Fail Before the Build Server DevFeed: [Build Hints That Fail Before the Build Server]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-09-02T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [Compiler](), [Java](), [configuration]() Tags: [autocomplete](), [build](), [compilation](), [compiler](), [configuration](), [java]() ### AI overview Codename One moves 87 common build hints into Java annotations so the compiler can catch misspelled names, incorrect value types, and unsupported options before builds reach the server. The change preserves the existing key-and-string format used by older projects and the build service. ### Source excerpt Codename One now exposes 87 common build hints as Java annotations, giving the compiler enough information to reject misspelled names, wrong types, and unsupported values before a build reaches the server. ## Resilient Sync: Your IDE Keeps Helping even when your Build is Broken DevFeed: [Resilient Sync: Your IDE Keeps Helping even when your Build is Broken]() Original publisher: [Read original article]() Author: Laura Kassovic Published: 2026-08-13T04:00:00Z Content type: article Language: en Sources: [The Gradle Blog]() Topics: [Gradle](), [IntelliJ IDEA](), [ide](), [2026.2](), [configuration]() Tags: [2026-2](), [autocomplete](), [build](), [feature](), [gradle](), [ide](), [intellij-idea](), [kotlin](), [upgrade]() ### AI overview Gradle 9.7 and IntelliJ IDEA 2026.2 introduce resilient sync, allowing the IDE to remain useful when parts of a Gradle build fail to configure. Instead of aborting the entire sync, Gradle provides partial project models, editor data for resolvable Kotlin DSL scripts, and structured failure information. ### Source excerpt You upgrade Gradle, hit sync, and watch every build script turn red. The IDE that was finishing your sentences five minutes ago suddenly has nothing to say, and you're left fixing build logic in what is effectively a very expensive text editor. And the API you need to fix the error is the exact API the IDE can no longer tell you anything about. To get autocomplete back, fix the build. To fix the build, it would help to have autocomplete. Chicken, meet egg. Gradle 9.7, together with IntelliJ IDEA 2026.2, fixes this. The feature is called resilient sync, and it is one of those changes you only notice by its absence once you have it. What goes wrong today Nobody designed the old behavior to be cruel. It falls out of two entirely reasonable decisions that happen to collide. The IDE reasons that if it cannot get a model back from Gradle, it has nothing accurate to show you, so it shows almost nothing. Gradle reasons that if configuration throws, the whole operation failed, so it reports the failure and stops. Both are correct. Together they produce a tool that abandons you precisely when you need it most. The worst version is the multi-project build. You have a hundred subprojects, and one of them (or one shared convention plugin in an included build) has a broken script. In the old world, that single failure takes down the sync for all one hundred. Ninety-nine healthy projects lose their IDE support over one bad line somewhere else in the tree. Power users had a workaround, as charming as workarounds usually are: # The old "please just give me some completion" incantation. Don't rely on this. org.gradle.jvmargs=-Dorg.gradle.kotlin.dsl.provider.mode=classpath It coaxed some completion out of a broken build, frequently broke Gradle's internal state in other ways, and often needed an IDE restart to load new API. Reader, it was not a fix. It was a coping mechanism. What is resilient sync? Resilient sync replaces all-or-nothing with best-effort. When part of your build fails ## How Vinted Serves Personalised Search Autocomplete DevFeed: [How Vinted Serves Personalised Search Autocomplete]() Original publisher: [Read original article]() Author: Justina Bartulevičienė Published: 2026-04-22T00:00:00Z Content type: article Language: en Sources: [Vinted]() Topics: [recommendation systems](), [data](), [systems](), [Learning]() Tags: [autocomplete](), [model](), [offline](), [performance](), [personalisation](), [pipeline](), [search]() ### AI overview Vinted describes the architecture and operation of its personalized search autocomplete service. The system generates candidate queries from product metadata and search logs, indexes and matches them with typo tolerance, and ranks suggestions using personalization and a Learning-to-Rank model. The service supports 24 languages and more than 50 country-language combinations, with 125 million queries and reported throughput of 4,700 queries per second at 31 ms P99. ### Source excerpt At Vinted, more than 20% of all search sessions now start with a click on an autocomplete suggestion. A few years ago, that number was below 8%. Autocomplete not only saves typing effort - it helps people discover listings they didn't know existed, and guides them toward successful searches. Today, across 24 languages and 50+ country-language combinations, we have a pool of 125 million different queries ready to suggest to users. Our service, svc-suggestions, runs on Vespa and matches and ranks 4,700 queries per second at 31 ms P99. ## New Maestro Studio DevFeed: [New Maestro Studio]() Original publisher: [Read original article]() Author: Manu Armani Published: 2026-04-21T22:36:00Z Content type: release Language: en Sources: [mobile.dev - Medium]() Topics: [Mobile](), [Testing](), [Tool](), [selectors](), [Emulator]() Tags: [amazon](), [autocomplete](), [cli](), [developers](), [emulator](), [maestro](), [meta](), [testing](), [ui-testing]() ### AI overview Maestro announces a redesigned Maestro Studio desktop app for mobile UI testing. The release adds contextual autocomplete for commands, arguments, and selectors, emulator-assisted test creation, and more robust device connections, while existing tests continue to work without migration. ### Source excerpt Maestro Studio is the desktop app for mobile UI testing. Now completely redesigned, with contextual autocomplete. ## Tinybird adds Python-native definitions for datasources, pipes, and endpoints DevFeed: [Tinybird adds Python-native definitions for datasources, pipes, and endpoints]() Original publisher: [Read original article]() Author: Jorge Sancha Published: 2026-03-10T12:00:00Z Content type: release Language: en Sources: [Tinybird]() Topics: [Python](), [Code](), [ide](), [coding]() Tags: [autocomplete](), [code](), [coding](), [ide](), [product-updates](), [python]() ### AI overview Tinybird now supports defining datasources, pipes, and endpoints as Python code, with typed ingestion and IDE autocomplete. ### Source excerpt Define datasources, pipes, and endpoints as Python code. Get typed ingestion, IDE autocomplete, and a language your coding agent already understands. ## The AI Multiplier: Where Developers Actually Get Leverage DevFeed: [The AI Multiplier: Where Developers Actually Get Leverage]() Original publisher: [Read original article]() Author: Brian Jenney Published: 2026-03-07T21:57:25Z Content type: opinion Language: en Sources: [Brian Jenney]() Topics: [Artificial Intelligence](), [AI-assisted coding](), [coding assistant](), [coding](), [Software]() Tags: [ai](), [autocomplete](), [coding](), [coding-assistant](), [context](), [developers](), [refactor](), [tests]() ### AI overview This commentary describes how software developers can gain leverage from AI through progressively more advanced usage. It outlines coding-assistant tasks such as generating functions, refactoring code, writing tests, and explaining errors, then discusses using AI as a planning partner to analyze systems, identify risks, and propose plans before code is written. ### Source excerpt Last night I met up with Alex Lau, the author of Keep Calm, Code On, while he was in San Francisco. ## PHPStan custom rules DevFeed: [PHPStan custom rules]() Original publisher: [Read original article]() Author: Rob Published: 2026-03-03T11:00:00Z Content type: tutorial Language: en Sources: [Rob Allen]() Topics: [PHP](), [Exception](), [Code](), [phpstorm]() Tags: [autocomplete](), [class](), [code](), [container](), [exception](), [extension](), [php](), [phpstorm](), [runtime](), [settings]() ### AI overview This tutorial explains how a PHPStan custom rule can detect references to unavailable PHP classes. It also describes configuring PhpStorm to limit autocomplete to extensions used by the application. ### Source excerpt Recently I discovered that this code passed our PHPStan level 10 checks: use http\Exception\InvalidArgumentException; // ... throw new InvalidArgumentException; I was surprised as http\Exception\InvalidArgumentException is not a class in our system. While cooling, I discovered that there's an http PHP extension and it appears that PHPStan has a stub for this which means that it accepts it as existing even if it doesn't. What we think happened is that I wrote throw new InvalidArgumentException; and... continue reading. ## Tinybird, now in TypeScript DevFeed: [Tinybird, now in TypeScript]() Original publisher: [Read original article]() Author: Jorge Sancha Published: 2026-02-17T00:00:00Z Content type: release Language: en Sources: [Tinybird]() Topics: [TypeScript](), [SDK](), [Command-line interface](), [Development]() Tags: [autocomplete](), [cli](), [connectors](), [development](), [product-updates](), [sdk](), [typescript]() ### AI overview Tinybird introduces a TypeScript SDK for defining datasources, pipes, and connectors as TypeScript code, with type-safe ingestion, query autocomplete, and a CLI. ### Source excerpt Introducing Tinybird's TypeScript SDK. Define datasources, pipes, and connectors as TypeScript code. Get type-safe ingestion, autocomplete for queries, and a CLI that feels like modern app development. ## The Vibe Coding Stack for 2026 DevFeed: [The Vibe Coding Stack for 2026]() Original publisher: [Read original article]() Author: Daniel Moka Published: 2025-12-13T06:01:36Z Content type: article Language: en Sources: [Craft Better Software]() Topics: [Vibe coding](), [Claude Code](), [coding](), [VS Code Extension](), [Test-driven development]() Tags: [autocomplete](), [claude-code](), [code](), [developers](), [guide](), [tests](), [vibe-coding](), [workflows]() ### AI overview This article presents a 2026 "Vibe Coding Stack" centered on using AI coding agents, clear specifications, and modern models. It focuses on Claude Code and recommends practices such as using its VS Code extension, maintaining Claude.md project guidance, exploring and planning before coding, resetting drifting context, and creating reusable slash commands. ### Source excerpt How Top Developers Supervise AI to Craft Better Software ## AI Programming Paradigms: A Timeline DevFeed: [AI Programming Paradigms: A Timeline]() Original publisher: [Read original article]() Author: Kaushik Gopal Published: 2025-07-08T00:00:00Z Content type: opinion Language: en Sources: [Kaushik Gopal's Site]() Topics: [Artificial Intelligence](), [agentic-coding](), [AI-assisted coding](), [Programming](), [cursor](), [ide](), [GitHub Copilot](), [Large Language Model](), [GitHub]() Tags: [agentic](), [agentic-coding](), [agents](), [ai](), [ai-for-autocomplete](), [autocomplete](), [code](), [code-completion](), [coding](), [context](), [copilot](), [cursor](), [llm](), [programming](), [visual-studio]() ### AI overview The article outlines a progression of AI programming paradigms: super autocomplete, conversational coding, agentic coding, and possible multi-agent workflows. It describes how each approach changes the way developers interact with code and development tools. ### Source excerpt A developer podcast host recently said they only use AI for autocomplete. This shocked me. That's two generations behind today's state of the art. This is how the field is evolving: I spoke about this topic in episode #301 of Fragmented. It was recorded more recently so reflects my more current thoughts on the topic. Download directly AI Programming Paradigms at a Glance Super autocomplete: AI predicts code, not just keywords. Conversational Coding: Chat with your IDE, direct the AI, iterate together. Agentic Coding: AI acts independently - runs commands, checks work, iterates. Simul Agentic? : Multiple sub-agents, parallel workflows, working together. I. Super autocomplete # This used to be one of the biggest selling points of certain IDEs like JetBrains & Visual Studio.1 The first wave of AI changed this. IDEs now predict entire classes and logic blocks, not just keywords. They excel because they feed surrounding code context to the LLM for relevant suggestions. GitHub deserves credit for kicking off the revolution with their Copilot offering. Here's an early YouTube video of mine from June 20222 showing it in action. Autocomplete keeps advancing. Cursor (today's most popular AI IDE) has "Tab". JetBrains, the pre-AI autocomplete champion, is building Mellum (an LLM built for code completion). This paradigm is alive and well, but it's become table stakes. Most developers use it, but it's far from the frontier. II - Conversational Coding # When ChatGPT took the world by storm, a new paradigm emerged. Conversational coding, where you chat with the AI and pair program together. Unlike the autocomplete era, where you trust the AI's suggestions, here you direct the AI, give it context, and nudge it toward better solutions. This is arguably what most devs use today and envision when they hear "AI programming". It feels magical, productivity jumps are real, and it's hard to think of every going backwards. Cursor leads this charge: chat with your IDE and have it make code ## State of AI 2025: How Developers Are Adopting AI Coding Tools DevFeed: [State of AI 2025: How Developers Are Adopting AI Coding Tools]() Original publisher: [Read original article]() Author: Carlota Soto Published: 2025-04-23T18:48:42Z Content type: article Language: en Sources: [Blog -- Neon Docs]() Topics: [Artificial Intelligence](), [AI-assisted coding](), [cursor](), [coding](), [Repl.it](), [MCP]() Tags: [ai](), [ai-coding](), [ai-tools](), [app-development](), [autocomplete](), [coding](), [cursor](), [debugging](), [developers](), [mcp](), [product](), [workflows]() ### AI overview The article reports findings from the State of AI 2025 survey, which collected more than 4,000 developer responses about the use of AI tools in real workflows. It highlights growing adoption of AI-assisted coding, Cursor and v0 for prototyping, manual review of generated output, and continued attachment to established editors. ### Source excerpt The first-ever State of AI 2025 survey polled thousands of developers to see how AI tools fit into real workflows, from brainstorming features to debugging in production. The survey ran from Feb-March 2025 and collected over 4,000 responses from developers around the world. Organ... ## Meet Cursor Tab and Never Look Back: The Future of AI-Assisted Coding DevFeed: [Meet Cursor Tab and Never Look Back: The Future of AI-Assisted Coding]() Original publisher: [Read original article]() Author: Carlota Soto Published: 2025-04-04T00:13:42Z Content type: article Language: en Sources: [Blog -- Neon Docs]() Topics: [AI-assisted coding](), [cursor](), [Vibe coding](), [code-completion](), [Code]() Tags: [ai](), [ai-assisted-coding](), [autocomplete](), [code-completion](), [cursor](), [developer](), [learning](), [product](), [side-projects](), [vibe-coding](), [vs-code]() ### AI overview The article introduces Cursor Tab, an AI-assisted coding feature designed to keep developers in control while writing code. It contrasts "tab coding" with more autonomous vibe coding and describes predictive coding and zero-entropy edits, where Cursor anticipates larger code changes and handles predictable actions after the developer's intent is clear. ### Source excerpt It's crazy to think that "vibe coding" started just weeks ago, with this tweet from Andrej Karpathy: Now, you can get a job as a vibe coder, and Stanford professors are giving lectures on it. That escalated quickly. In its short life, vibe coding has come to mean all kinds of AI-... ## What's involved in getting a "modern" terminal setup? DevFeed: [What's involved in getting a "modern" terminal setup?]() Original publisher: [Read original article]() Author: Julia Evans Published: 2025-01-11T09:46:01Z Content type: opinion Language: en Sources: [Julia Evans]() Topics: [Terminal](), [Shell](), [Neovim](), [Vim](), [Git](), [Firefox]() Tags: [autocomplete](), [commands](), [config](), [firefox](), [git](), [history](), [ls](), [terminal](), [vim]() ### AI overview The article discusses what a modern terminal setup means to the author, including safe multiline paste, persistent shell history, useful prompts, 24-bit color, clipboard integration, command-specific autocomplete, shell colors, synchronized themes, automatic terminal recovery, keybindings, and scroll-wheel support. It emphasizes that achieving these conveniences requires coordinating the shell, terminal emulator, text editor, operating system, and applications. ### Source excerpt Hello! Recently I ran a terminal survey and I asked people what frustrated them. One person commented: There are so many pieces to having a modern terminal experience. I wish it all came out of the box. My immediate reaction was "oh, getting a modern terminal experience isn't that hard, you just need to....", but the more I thought about it, the longer the "you just need to..." list got, and I kept thinking about more and more caveats. So I thought I would write down some notes about what it means to me personally to have a "modern" terminal experience and what I think can make it hard for people to get there. what is a "modern terminal experience"? Here are a few things that are important to me, with which part of the system is responsible for them: multiline support for copy and paste: if you paste 3 commands in your shell, it should not immediately run them all! That's scary! (shell, terminal emulator) infinite shell history: if I run a command in my shell, it should be saved forever, not deleted after 500 history entries or whatever. Also I want commands to be saved to the history immediately when I run them, not only when I exit the shell session (shell) a useful prompt: I can't live without having my current directory and current git branch in my prompt (shell) 24-bit colour: this is important to me because I find it MUCH easier to theme neovim with 24-bit colour support than in a terminal with only 256 colours (terminal emulator) clipboard integration between vim and my operating system so that when I copy in Firefox, I can just press p in vim to paste (text editor, maybe the OS/terminal emulator too) good autocomplete: for example commands like git should have command-specific autocomplete (shell) having colours in ls (shell config) a terminal theme I like: I spend a lot of time in my terminal, I want it to look nice and I want its theme to match my terminal editor's theme. (terminal emulator, text editor) automatic terminal fixing: If a programs prints out some ## Why Coding Assistants Need Senior Developer Oversight DevFeed: [Why Coding Assistants Need Senior Developer Oversight]() Original publisher: [Read original article]() Author: Filipe Castro Published: 2024-09-11T11:00:00Z Content type: opinion Language: en Sources: [Avenue Code]() Topics: [coding assistant](), [GitHub Copilot](), [Artificial Intelligence](), [Programming](), [Deep learning]() Tags: [ai](), [artificial-inteligence](), [autocomplete](), [chatgpt](), [coding-assistant](), [copilot](), [data-and-machine-learning](), [deep-learning](), [devops](), [github-copilot](), [programming]() ### AI overview The article argues that coding assistants can accelerate development but may generate incorrect or inefficient code. Because beginners may accept flawed suggestions, it explains why experienced developers should evaluate assistant output and introduces the deep learning process behind these tools. ### Source excerpt Coding assistant tools are popping up everywhere nowadays (Copilot, JB Assistant, ChatGPT, etc.). They ensure fast and easy coding for developers and also provide a variety of ways to solve the same problem. Normally, the developer can choose preprocessed snippets for a line or lines of their code, along with some suggestions for autocomplete. ## How to Add an aiexclude File DevFeed: [How to Add an aiexclude File]() Original publisher: [Read original article]() Published: 2024-08-01T00:00:00Z Content type: tutorial Language: en Sources: [Donovan LaDuke - Developer]() Topics: [Android Studio](), [Large Language Model](), [AI-assisted coding]() Tags: [ai](), [android-studio](), [autocomplete](), [code](), [how-to](), [privacy]() ### AI overview A tutorial explaining how to use an .aiexclude file in an Android Studio project to prevent selected code files from being sent to Google's Gemini-powered code generation and autocomplete features. It highlights the trade-off between protecting private or proprietary code and retaining AI-assisted productivity features. ### Source excerpt Avoid Accidentally Sharing Code with AI for training by using an aiexclude file in Android Studio ## Zed2 Development Progress Report DevFeed: [Zed2 Development Progress Report]() Original publisher: [Read original article]() Author: Joseph Lyons Published: 2023-12-04T00:00:00Z Content type: article Language: en Sources: [Zed Industries - Blog]() Topics: [ide](), [ui](), [telemetry](), [Terminal](), [Vim](), [Open Source]() Tags: [autocomplete](), [bugs](), [collaboration](), [community](), [features](), [open-source](), [progress-report](), [telemetry](), [terminal](), [ui](), [vim]() ### AI overview This progress report describes the Zed team's three-phase transition from Zed1 to Zed2: making the editor runnable, adding productivity features, and completing larger flagship features. The team aimed to release a working Zed2 preview by the end of 2023 and planned to open source it after Zed2 superseded Zed1. ### Source excerpt Progress report on Zed2 ## Zed Weekly: #26 DevFeed: [Zed Weekly: #26]() Original publisher: [Read original article]() Author: Joseph Lyons Published: 2023-11-10T00:00:00Z Content type: article Language: en Sources: [Zed Industries - Blog]() Topics: [TypeScript](), [Code](), [npm](), [Framework]() Tags: [autocomplete](), [code](), [diagnostics](), [js](), [keyboard](), [npm](), [typescript](), [ui](), [update]() ### AI overview Zed Weekly #26 covers continued migration of the editor to GPUI 2, improvements to textual input and keyboard event handling, and restoration of JavaScript and TypeScript language support after a wrapper project removed deprecated command-line flags. ### Source excerpt Fixing the busted JS/TS language support, building the new theme system, and continuing to port Zed to GPUI-2. ## Zed Weekly #23: Autocomplete Documentation and Reduced UI Latency DevFeed: [Zed Weekly #23: Autocomplete Documentation and Reduced UI Latency]() Original publisher: [Read original article]() Author: Joseph Lyons Published: 2023-10-13T00:00:00Z Content type: article Language: en Sources: [Zed Industries - Blog]() Topics: [Documentation](), [Latency](), [ui](), [Concurrency]() Tags: [async](), [autocomplete](), [latency](), [performance](), [ui]() ### AI overview Zed Weekly #23 reports the addition of autocomplete documentation and a fix for completion filtering that previously blocked the UI thread. The revised synchronization allows filtering to race language-server re-requests, reducing typing hitching and latency when many completions are present. ### Source excerpt Vue, prettier, autocommpletion docs, and more! ## Zed Weekly: Channel Chat, Semantic Index Updates, Prettier Integration, and Autocomplete Docs DevFeed: [Zed Weekly: Channel Chat, Semantic Index Updates, Prettier Integration, and Autocomplete Docs]() Original publisher: [Read original article]() Author: Mikayla Maki Published: 2023-09-18T00:00:00Z Content type: article Language: en Sources: [Zed Industries - Blog]() Topics: [Development](), [Prettier](), [AI search](), [Artificial Intelligence](), [remote-development]() Tags: [autocomplete](), [chat](), [code](), [docs](), [formatting](), [integration](), [remote-development](), [search](), [testing](), [weekly]() ### AI overview This weekly development update covers progress on Zed's channel chat system, a moving and linking channels project, fixes for hint and LSP status bugs, and local Prettier integration. It also reports Semantic Index support for modified open buffers, an evaluation framework for the engine, planned integration with the inline code assistant, and continued autocomplete documentation work. ### Source excerpt Shipping channel chat, GPUI2 code samples, and autocomplete docs, and adding replace to our buffer search! ## Keeping IDE Sync Times at Bay: A Historical Perspective DevFeed: [Keeping IDE Sync Times at Bay: A Historical Perspective]() Original publisher: [Read original article]() Author: Roger Hu Published: 2023-05-04T07:00:00Z Content type: article Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [Android Studio](), [Gradle](), [ide](), [Development](), [IntelliJ IDEA](), [ci]() Tags: [android](), [android-studio](), [autocomplete](), [build-system](), [ci](), [context](), [continuous-integration](), [development](), [engineering](), [gradle](), [hints](), [ide](), [integration](), [intellij](), [intellij-platform](), [performance](), [sync]() ### AI overview A historical account of Android Studio's IDE synchronization, its integration with Gradle, and the performance challenges caused by large Android codebases. ### Source excerpt Commemorating 10 years since Android Studio's introduction ## One month with Github Copilot DevFeed: [One month with Github Copilot]() Original publisher: [Read original article]() Published: 2023-03-31T00:00:00Z Content type: article Language: en Sources: [Adam Bard]() Topics: [GitHub Copilot](), [Code](), [ide](), [Artificial Intelligence]() Tags: [autocomplete](), [code](), [copilot](), [developer](), [function](), [github-copilot](), [ide](), [if-statement](), [intellisense](), [patterns](), [usability]() ### AI overview The author reviews a month of using GitHub Copilot, describing it as an IDE-based coding assistant that generates fast suggestions from function names, docstrings, control-flow statements, and short cues. The article highlights its ability to complete larger code patterns, document functions, and generate example usage, while noting that its output may lack nuance and often needs touchups. ### Source excerpt I've been trialling Github Copilot for some weeks now, and so far I've been very impressed. It's clear to me that this and similar tools will become a permanent part of many programmers' toolkits (at least until the AI gets so clever that it obviates our jobs completely). ## Using TypeScript Intersections to Preserve Literal Autocomplete with Arbitrary Strings DevFeed: [Using TypeScript Intersections to Preserve Literal Autocomplete with Arbitrary Strings]() Original publisher: [Read original article]() Published: 2023-03-01T00:00:00Z Content type: tutorial Language: en Sources: [Artsy]() Topics: [TypeScript](), [Design system](), [React Native](), [CSS]() Tags: [autocomplete](), [css](), [design-system](), [palette](), [react-native](), [tools](), [types](), [typescript]() ### AI overview This tutorial explains a TypeScript type pattern that preserves autocomplete and typechecking for predefined design-system color values while still accepting arbitrary strings such as hexadecimal, RGB, HSL, and CSS color names. It uses an intersection-based type trick to keep specific string literals distinct from the general string type. ### Source excerpt At Artsy, we love TypeScript. We use it in most of our node/web/mobile repos. Today, I want to talk about a specific case we found while trying to make our types more strict on palette-mobile, which is our Design System for React Native. Check this out: const welp: "hello" | "world" | string // `welp` is of type `string`. Like the comment says, even though we have two specific strings, the fact that we do a union with string, makes welp have a type of just string. This is because both "hello" and "world" are strings, and the union tends to go to the type that includes the most. Think of set theory and bubbles. "hello" is a type by itself, and "world" is a type by itself. Unioning them together gives us a new type, which is a bubble that contains both "hello" and "world". In that "hello" | "world" union bubble, we see both "hello" and "world" types as subsets. The string bubble contains all strings, so it contains "hello" and "world" and "hello" | "world", so the union of them with string is string. That is usually ok, but for our case, it didn't work. Here is what we wanted to do. The problem In our Design System, we have certain color, named like black100, black80, blue100, red150 etc. We can have a type like type ColorDSValue = "black100" | "black80" | "blue100" | "red150" // | etc and that works great. We get to have autocomplete, typechecking, all the good stuff that TypeScript brings. But we also want to support any other string, like "#000000", "#000", "rgb(0,0,0)", "rgba(0,0,0,0.5)", "hsl(0,0%,0%)", "hsla(0,0%,0%,0.5)". Ok, you might say, just make more types like type ColorHexValue = `#${string}` type ColorRGBValue = `rgb(${number},${number},${number})` type ColorRGBAValue = `rgba(${number},${number},${number},${number})` type ColorHSLValue = `hsl(${number},${number}%,${number}%)` and so on. That's great. So far, so good. We also want to make sure CSS color names are accepted. So then we add something like type ColorCSSString = "red" | "blue" | "hotpink" // ## Autocomplete for Behaviors in PhpStorm with Mixins & Veneers DevFeed: [Autocomplete for Behaviors in PhpStorm with Mixins & Veneers]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2022-12-20T15:42:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [phpstorm](), [code-completion](), [Content Management System](), [Development]() Tags: [added](), [autocomplete](), [behaviors](), [cms](), [code](), [code-analysis](), [code-completion](), [completion](), [craft](), [insights](), [intellisense](), [learn](), [mixins](), [phpstorm](), [project](), [using](), [veneers]() ### AI overview A tutorial on restoring PhpStorm IntelliSense code completion for behaviors added to Craft CMS projects. It explains how to use mixins and veneer classes so PhpStorm can recognize dynamically added properties and methods through static code analysis. ### Source excerpt Learn how to get PhpStorm IntelliSense code completion for Behaviors added to your Craft CMS project using Mixins & Veneers ## Fluent Multi-Environment Config for Craft CMS 4 DevFeed: [Fluent Multi-Environment Config for Craft CMS 4]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2022-07-26T04:00:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Content Management System](), [data]() Tags: [allows](), [autocomplete](), [better](), [cms](), [config](), [craft](), [create](), [editor](), [environment](), [errors](), [fewer](), [files](), [fluent](), [insights](), [less](), [model](), [multi-environment](), [settings](), [using](), [work]() ### AI overview This tutorial explains how Craft CMS 4.2's optional fluent configuration interface improves multi-environment config files. It highlights autocomplete, inline documentation, and type-checking as ways to reduce lookup work and configuration errors. ### Source excerpt Using the new fluent model config settings in Craft CMS 4.2 allows you to create better config files, with less work and fewer errors [Next page]()