stringparser | use pattern matching and information extraction

With the help of a freelancer on Fiverr I solved it in the following way:

https://stackoverflow.com/a/69871902/1972372

Basically parsed the tags manually and kept track of the content types and order in an array, while keeping formatted Texts in another array. Then I could take that content and plant it into a ViewBuilder body function.

Unfortunately, SwiftUI doesn't let you change a Text's background color yet, without turning it into some View. So I had to make do with other, similar formattings for now.

You can use a mapping type to create a proper type for your handlers param:

i think you need several solutions. I think a little different regex are necessary. Here is a RegEx which will be helpful in further development.

(\d+).*?(\b\d+\b).*?(\b\d+)

Demo: https://regex101.com/r/iIlLLN/1

The difference between the Person displayed and the type you expected is pretty much just cosmetic. The compiler has a set of heuristic rules it follows when evaluating and displaying types. These rules have changed over time and are occasionally tweaked, such as the "smarter type alias preservation" support introduced in TypeScript 4.2.

One way to see that the types are more or less equivalent is to create both of them:

It is a known issue in TypeScript that the false branch of a conditional type does not get its types narrowed. So in T extends U ? F : G does not take G and replace it with something like G>. As far as the compiler is concerned, the T in G might still be assignable to U, even though it's obvious to us that it won't be. See microsoft/TypeScript#29188. It looks like there was some work done to address this at microsoft/TypeScript#24821, but it was not merged. It's not clear to me if or when this issue will be resolved.

Until then, it's easy enough (if annoying) to do such narrowing yourself when necessary:

Orion restricts the usage of some characters due to security reasons (script injections attack in some circumstances), see this piece of documentation. In particular, the = you have in the password attribute value.

You can avoid this, for instance, by encoding the password in base 64, or using URL encoding before storing it in Orion.

Another alternative using TextUnrestricted in attribute type. This special attribute type does not check if the attribute value contains a forbidden character. However, it could have security implications, use it at your own risk!

I got this working. The solution was a bit brute force — overloading the createRoute function. Here's what I have:

The array temp exist only in the scope of function stringParser(). The pointer t points to the array temp or in other words t holds the address of where temp is stored. When you return from the function stringParser(), the array temp does no longer exist and accessing it causes undefined behavior (UB). You return the pointer t that points to temp and give it to printf(). printf() dereferences the pointer, means it wants to access the array to which t points to, but the array temp does no long exist and therefore you have UB.

There are multiple ways to avoid UB:

• Make the array temp static. But that does not work well with multi threading programs and should be avoided in libraries.
• Use dynamic memory allocation, reserve the storage for the temp-array with malloc() or calloc(), but then you have to free() the memory again after you no longer need it.
• Declare the array inside main() and pass a pointer to it to stringParser(), but keep the size in check and make sure you never get a buffer overflow.

Off-Topic: size_t is a better type for array indexing, since it is guaranteed to be large enough to hold every possible index and size_t is unsigned. Your program is prone to buffer overflows by future changes. Since you do not document that the string given to stringParser() has to be shorter than 100 chars. You need to document that better, check if the string is not too long or create the array dynamically to be big enough for the given string.

Yep, don't include one cpp file in another. Use header files.

CardBase.cpp