Most developers use Mapped Types. Few realize they can use them to 'filter' keys on the fly. Imagine you have a type with 50 properties. You need a new type that only includes keys matching a specific pattern, like those containing the word 'Id'. Not keys you manually list. Not keys you hardcode. But keys that match a rule. This is where selective remapping in mapped types shines. We know we can use the 'as' keyword to rename keys. But the real 'pro move' is knowing what happens when you remap a key to 'never.' In TypeScript, if a key is remapped to 'never', it is removed from the resulting type entirely. And that's an important point to keep in mind because this is what we can use to do a selective remapping in mapped types. By iterating over every key and applying a conditional check: 1. If the key matches your rule - Keep it. 2. If it doesn’t - Remap to 'never.' This pattern is extremely useful in real-world scenarios where you need only specific prefixed keys or you’re building reusable utility types. When you're building utility types, API response handlers, or form schemas, you often need specific subsets of properties. This pattern lets you extract them programmatically instead of maintaining duplicate type definitions. Once you realize you can conditionally 'filter' keys during transformation, you stop fighting the type system and start making it work for you. #TypeScript #JavaScript #Programming #Coding #WebDevelopment
Selective Remapping in Mapped Types for TypeScript
More Relevant Posts
-
Most developers use == without fully understanding what it actually does. And that’s where bugs are born. 👀 👉 0 == false → true 👉 "" == 0 → true 👉 "5" == 5 → true Shocking? That’s because == does type coercion (automatic type conversion). It tries to “adjust” values before comparing them. On the other hand 👇 ✅ === compares value + type ❌ No conversion ✅ No unexpected surprises Example: 0 === false → false "5" === 5 → false 💡 Developer Rule: Always prefer === in real projects and interviews. Clean code = Predictable behavior. If this helped you, follow for more simple JavaScript concepts explained clearly 🚀 #JavaScript #WebDevelopment #Coding #Frontend #Programming #100DaysOfCode
To view or add a comment, sign in
-
-
JavaScript Variables: Your Code's Memory Boxes! 🗃️✨ Think of variables as sticky notes 📝 where you jot down info your code needs— like numbers 🔢, text 📄, or lists 📋. JS offers 3 main types, each with super simple rules: var (The Vintage Choice) 🕰️ • Works across whole functions ⚙️ • Jumps to the top (hoisted!) 🚀 • Easy to change or reuse 🔄 • Skip it for new projects ❌ let (The Flexible Friend) 🧡 • Stays inside blocks {} 🧱 • Needs to be declared first ⏳ • Change the value anytime ➕➖ • Great for counters or loops 🔁 const (The Rock-Solid One) 🪨 • Locked to blocks {} 🔒 • Declare first, no changes allowed 🚫 • Can't redeclare it ❌ • Ideal for constants like API keys 🔑 Pro Tip: 💡 Start with const everywhere. Switch to let only if you need to update. Ditch var for cleaner code! 🧹 Which one trips you up most? Drop a comment! 👇💬 #JavaScript #WebDevelopment #FrontendDev #LearnToCode #CodingTips #JSBasics #Programming #Developers #TechTips #CodeNewbie #JavaScriptTips #Frontend #CodingLife #WebDev #100DaysOfCode
To view or add a comment, sign in
-
-
𝐐𝐮𝐢𝐜𝐤 𝐉𝐚𝐯𝐚𝐒𝐜𝐫𝐢𝐩𝐭 𝐂𝐡𝐚𝐥𝐥𝐞𝐧𝐠𝐞 – 𝐂𝐚𝐧 𝐘𝐨𝐮 𝐆𝐮𝐞𝐬𝐬 𝐭𝐡𝐞 𝐎𝐮𝐭𝐩𝐮𝐭? Sometimes it’s not about complex algorithms… It’s about understanding how small string methods work together. 👀 Here’s the snippet 👇 const result = ["genetech", "solutions"] .map(word => word.charAt(0).toUpperCase() + word.slice(1)) .join(" "); console.log(result); What will be the output? 🤔 A) genetech solutions B) GENETECH SOLUTIONS C) Genetech Solutions D) ["Genetech", "Solutions"] This one tests your understanding of: - map() - charAt() - toUpperCase() - slice() - join() Small fundamentals. Big difference. 💡 Drop your answer in the comments 👇 Let’s see who reads code carefully 😄 #JavaScript #WebDevelopment #FrontendDeveloper #CodingChallenge #LearnToCode #Programming #Developers #TechCommunity #JS #CodeDaily
To view or add a comment, sign in
-
-
🚀 JavaScript Tip: Say Goodbye to “Try-Catch Hell” in 2026! If your code still feels like a pyramid of nested try-catch blocks just to handle a simple API call, you’re doing things the old-school way. The Safe Assignment Operator (?=) is changing how JavaScript handles errors by treating them as data instead of exceptions that interrupt your flow. Instead of wrapping everything in try-catch, you can now assign results in a cleaner, more linear way — while still capturing errors in a predictable format. Why developers are switching: ✅ No more deep nesting ✅ No more declaring variables outside blocks just to use them later ✅ Code stays top-to-bottom and easier to follow ✅ Feels similar to Go and Rust’s “error as value” approach So what about you — are you still using traditional try-catch for most cases, or have you started moving to safe assignments? 👇 #JavaScript #WebDev #Coding #SoftwareEngineering #CleanCode #Programming #ReactJS #TechTrends
To view or add a comment, sign in
-
-
⚡ Ever wondered why your JavaScript code runs in a specific order? The answer lies in something called the Call Stack. Every time a function runs, JavaScript adds it to the stack. When the function finishes, it gets removed. Simple rule it follows: 📦 LIFO — Last In, First Out That means the last function added is the first one removed. 🚨 And yes… That scary error — “Maximum call stack size exceeded” It happens when functions keep getting added to the stack without stopping. Eventually, memory fills up… and the program crashes. 🎯 Why understanding the Call Stack matters: ✔ Helps you understand execution order ✔ Makes debugging easier ✔ Builds strong recursion fundamentals ✔ Makes you interview-ready Mastering the Call Stack is one of the first real steps toward truly understanding JavaScript. #JavaScript #WebDevelopment #FrontendDeveloper #Programming #LearnToCode #Developers #Tech
To view or add a comment, sign in
-
-
𝗝𝗮𝘃𝗮𝗦𝗰𝗿𝗶𝗽𝘁 𝗖𝗹𝗼𝘀𝘂𝗿𝗲𝘀 𝗘𝘅𝗽𝗹𝗮𝗶𝗻𝗲𝗱 — 𝗖𝗼𝗺𝗽𝗹𝗲𝘁𝗲 𝗡𝗼𝘁𝗲𝘀 𝗳𝗼𝗿 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿𝘀 Closures are one of the most powerful and important concepts in JavaScript. They allow a function to access variables from its outer scope even after the outer function has finished executing. Understanding closures helps you master data privacy, function factories, callbacks, and advanced patterns used in modern frameworks like React. These notes break down closures in a simple and practical way with clear explanations and real-world use cases to strengthen your core JavaScript knowledge. #JavaScript #Closures #JSConcepts #WebDevelopment #FrontendDevelopment #LearnJavaScript #Programming #DeveloperNotes #Coding #SoftwareEngineering
To view or add a comment, sign in
-
JavaScript Prototype Explained Simply (Must Know Concept) Why Prototype Matters? ✔ Code Reusability ✔ Memory Efficient ✔ Enables Inheritance ✔ Foundation of JavaScript Classes Array.prototype → Object.prototype → null Methods like: • push() • pop() • map() • filter() Come from Array.prototype const arr = [10, 20, 30]; console.log(arr.__proto__ ===Array.prototype); // true If you're learning JavaScript, mastering Prototype is a game changer 💪 #JavaScript #WebDevelopment #Frontend #Programming #Developers #CodingJourney
To view or add a comment, sign in
-
-
JavaScript isn’t evolving through hype anymore. It’s evolving through small, practical upgrades that quietly make your code cleaner, safer, and easier to reason about. From Object.hasOwn() and private class fields to toSorted() and Object.groupBy() to Promise.withResolvers() and Iterator Helpers… Modern JS is pushing toward: • Less mutation • Clearer intent • Safer async handling • More functional data processing And honestly? That’s the kind of evolution that makes senior engineers dangerous. Before you search for a solution, you first need to know it exists. Which of the modern features are you already using in production? #JavaScript #WebDevelopment #Frontend #NodeJS #ECMAScript #SoftwareEngineering #CleanCode #Programming #FullStack #DevCommunity
To view or add a comment, sign in
-
-
🔄 The JavaScript Event Loop — most devs use it daily but can't explain it in an interview. Here's the simple truth: ➡️ JS is single-threaded — one task at a time. ➡️ The Call Stack runs your code synchronously. ➡️ Web APIs handle async tasks (setTimeout, fetch). ➡️ The Callback/Task Queue holds results waiting to run. ➡️ The Event Loop checks: "Is the stack empty? Push the next task." Example: console.log("1"); setTimeout(() => console.log("2"), 0); console.log("3"); // Output: 1, 3, 2 ← setTimeout goes to Web API, then queue Microtasks (Promises) run BEFORE the next macro task — that's why .then() beats setTimeout. Understanding this = writing faster, non-blocking code. 🚀 #JavaScript #WebDev #FullStack #Programming #SoftwareEngineering
To view or add a comment, sign in
-
Explore content categories
- Career
- Productivity
- Finance
- Soft Skills & Emotional Intelligence
- Project Management
- Education
- Technology
- Leadership
- Ecommerce
- User Experience
- Recruitment & HR
- Customer Experience
- Real Estate
- Marketing
- Sales
- Retail & Merchandising
- Science
- Supply Chain Management
- Future Of Work
- Consulting
- Writing
- Economics
- Artificial Intelligence
- Employee Experience
- Workplace Trends
- Fundraising
- Networking
- Corporate Social Responsibility
- Negotiation
- Communication
- Engineering
- Hospitality & Tourism
- Business Strategy
- Change Management
- Organizational Culture
- Design
- Innovation
- Event Planning
- Training & Development