svg-icons | Easily access urls or inline SVG icons | Icon library

First, this error message is indeed expected on Jan. 11th, 2022.
See "Improving Git protocol security on GitHub".

January 11, 2022 Final brownout.

This is the full brownout period where we’ll temporarily stop accepting the deprecated key and signature types, ciphers, and MACs, and the unencrypted Git protocol.
This will help clients discover any lingering use of older keys or old URLs.

Second, check your package.json dependencies for any git:// URL, as in this example, fixed in this PR.

As noted by Jörg W Mittag:

There was a 4-month warning.
The entire Internet has been moving away from unauthenticated, unencrypted protocols for a decade, it's not like this is a huge surprise.

Personally, I consider it less an "issue" and more "detecting unmaintained dependencies".

Plus, this is still only the brownout period, so the protocol will only be disabled for a short period of time, allowing developers to discover the problem.

The permanent shutdown is not until March 15th.

As in actions/checkout issue 14, you can add as a first step:

First, if you want the user to be able to select up to 4 products, you should change handleAddToCart's if statement, change product to cart, and the length should be superior ou equal to 4. Then define a chooseOneProductForMeHandler, past it down to Cart, and use it, like so:

You are having a cascading issue. You are setting your theme colors on body, and trying to change it later trough App. You need to add the data-them on body itself or on html, witch comes before, not on something that comes after.

Adding this useEffect in App.js just before your return would work :

What is happening is that you are trying to access an item in the list using the index listOfSelectedQuestions[index] but the item doesn't exists.

What you can do is add an object to the index if it doesn't exists

The use of a pipe for this kind of operation may seem like a good idea initially, but when you rely on an impure pipe that will run on each change detection cycle, the performance of an app can be compromised.

There are more simple ways to filter an observable value based on another value, and my suggestion is to consider the values from the search input as a stream aswell.

If we instead of using [(ngModel)] use a FormControl to listen to the valueChanges observable of the input, we can combine the streams and filter the posts value based on the search value.

You would en up with something like this

There are 2 options for doing this:

1. Use a dynamic element similar to the pseudocode you shared. You can conditionally pick the element, you just need to use the name of the tag as a string like this (disclaimer: I don't know how conventional this is)

Note: the variable name for the component (in this example Component) needs to be capitalized or accessed with dot notation. or will work, but will not.

Looks like Vue 3 is not supported yet:

https://fontawesome.com/v6/docs/web/use-with/vue/troubleshoot#using-vue-3

You're not passing anything into your onSubmit function.

Rewrite it to something like this with your current setup:

I just solve this issue by correcting the RxJS version to 7.4.0. I hope this can solve others issue as well.