<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>PrimeNG on redzimski.dev</title>
    <link>https://redzimski.dev/tags/primeng/</link>
    <description>Recent content in PrimeNG on redzimski.dev</description>
    <generator>Hugo -- 0.129.0</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 07 Oct 2025 12:00:00 +0000</lastBuildDate>
    <atom:link href="https://redzimski.dev/tags/primeng/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Building a confirmable MultiSelect with Angular&#39;s ControlValueAccessor</title>
      <link>https://redzimski.dev/posts/building-a-confirmable-multiselect-in-angular/</link>
      <pubDate>Tue, 07 Oct 2025 12:00:00 +0000</pubDate>
      <guid>https://redzimski.dev/posts/building-a-confirmable-multiselect-in-angular/</guid>
      <description>There&amp;rsquo;s a specific kind of late-project design request that every developer recognises. It sounds like nothing: &amp;ldquo;Could we just add a confirm step to the multiselect? So it only applies when you press Confirm?&amp;rdquo; That&amp;rsquo;s the request. A button. Turns out there is no such thing as just a button.
In one of the projects I worked on, we had exactly this requirement. A dropdown multiselect needed to support a draft state: users could select options, deselect them, and click around as much as they wanted, but nothing would be committed to the form until they hit &amp;ldquo;Confirm&amp;rdquo;.</description>
    </item>
  </channel>
</rss>
