nordea | gem compatible currency exchange rate implementation | Application Framework library

Because that server's response violates the HTTP specification, according to Fiddler:

[ProtocolViolation] Content-Length mismatch: Response Header indicated 12,803 bytes, but server sent 12,802 bytes.

The .NET Framework's HTTP stack is notorious for silently tolerating problems like this, while .NET Core features a completely rewritten stack that is much less forgiving. In this case it seems that Framework either isn't particularly trusting of the response's Content-Length or simply ignores it, while Core depends on its correctness (I'd guess for performance optimizations).

While some may argue that Core's behaviour is less convenient (especially since there's no way to opt out of it), the fact is that Framework's leniency is precisely the kind of thing that allows such broken behaviour to propagate and remain unfixed. Core is doing the right thing here, and I'm honestly baffled how the people running that server managed to screw up something as simple as Content-Length... and that they apparently never tested it's correct...

Your only options are to contact the server admin and get them to fix their brokenness, or use lower-level methods of reading that server's response in a way that bypasses the invalid Content-Length. An example of the following is given below (no guarantees regarding correctness or performance are provided; I tested this once):

Modified your script a bit to get title, description and href. Hopefully your questions are answered in-line.

I solve the problem since there always will be a match, but if the values isn't matched to anything, there will be a problem with integer(0)

Lombok's @Builder must have @AllArgsConstructor in order to work

Adding also @AllArgsConstructor should do

Under the hood it build all fields using constructor with all fields

applying @Builder to a class is as if you added @AllArgsConstructor(access = AccessLevel.PACKAGE) to the class and applied the @Builder annotation to this all-args-constructor. This only works if you haven't written any explicit constructors yourself.

I tried the data from the given URL. Not sure why but in the first json_decode(), the obtained value is the single JSON object with sub items. When that value is again called with json_decode() then value is obtained as an array. You may want to check in the source first how data is converted to JSON. There seems to be the problem.

Official Docs - Filtering and especially sorting are expensive operations.

The Angular team and many experienced Angular developers strongly recommend moving filtering and sorting logic into the component itself.

In general no need to use custom pipe for such case instead you can directly sort your data into your component class. But if you want to go with usage of pipe, refer below -

You need to set http.get() response type to text

Your numbers have a special pattern which can be used to hack the problem for you. If you notice, any space in this string which is followed by exactly three digits can be removed to unite the number forming actual number, which will make this string,

Try this