Request a patch for older UI version to include icon

[waijeeho]

Hey there! I'm working on Flex, which is on an older Paste version. We aren't able to upgrade our Paste version for Flex at the moment, but would like to use a handful of newly released icons from Paste.

Could we request a patch for our Paste version so that we do get access to new icons?

[TwilioPasteBot]

Disclaimer: This is a very experimental bot using OpenAI's GPT-4. The answers may not be correct, a human will review the answer and update it if necessary.

---

Sorry, I don't know how to help with that.

I did do a search though, and I managed to find these other Discussions that might be similar or related to your question. Give them a read to see if they answer your question. If they do, head back here and update this discussion and mark it as answered, pointing others to the related discussion:

• Twilio Flex 2.0 - Which versions of Paste and Paste Icons are usable (updated: 10/20/2023, similarity score: 88%)
• Streamline Icons (updated: 02/01/2023, similarity score: 87%)
• Use latest versions of Paste for Flex plugin development (updated: 11/07/2023, similarity score: 87%)

[TheSisb]

Hi @waijeeho,

I understand your desire to use the newly released icons from Paste, and I appreciate your willingness to explore options. However, I have to advise against requesting a patch for your existing Paste version to gain access to the new icons. When you overwrite an existing release, you can't guarantee that the new code will behave as expected, especially if it interacts with other dependencies. Releasing new semver versions is the recommended approach for maintaining a stable and predictable ecosystem. It allows developers to upgrade their dependencies in a controlled manner, without risking unexpected issues.

If you're having trouble upgrading your dependencies and are willing to make a trade-off for tech debt, you can manually copy the icons into your repository from ours.

[ChristopherLeeWilliams]

Hello, thanks for following up. I just wanted to make sure I understand the suggestion. Currently we are using paste/core version 15.3.1 and the version upgrade paths are all major version updates, no newer minor or patch versions. Newer major versions introduce some breaking changes we'd have to work through.

We were wondering if we would be able to get a new patch/minor version created with the icons, i.e. 15.3.2, or were you recommending against that? For the time being we have manually copied the svg. Thanks!

[TheSisb]

Hi @ChristopherLeeWilliams,

Ah, sorry I misunderstood. I thought the ask was to modify the existing version on NPM. In regards to shipping a patch on the v15 line, I'm afraid we aren't setup to do that in any reasonable way and are a little low on resources to prioritize that work.

In regards to breaking changes, v16 - which was released back in 2022 - should not break anything for your team. v17 onwards will require a small lift of effort, but nothing outrageous.

• v16 removed a hackfix for console, which I highly doubt was being used in Flex or the UI would have broken. That one is easy.
• v17 updates the Switch component API. This one will likely affect you, but you can explore a quick codemod (contributions are welcome) to make the conversion easy.
• v18 deprecates the light/dark named tokens, replacing them with strong/weak. Find and replace should do it, or another codemod.
• v19 asks your to add two dependencies we no longer bundle @types/react and @types/react-dom. This is so you can use the correct version of these packages for your version of React.
• v20 no changes. There should be nothing to this.

[ChristopherLeeWilliams]

Understood, no worries. Thanks for the callouts regarding the version upgrades!