utest | micro unit test framework for C99

Your a property is get-only, so in your ReadJson() method you need to populate the incoming List existingValue list (which will be the current property value) rather than creating a new list:

I'm seeing a huge fundamental issue here.

You really need a backend; look into NodeJS with Express if you like JavaScript.

There are so many things wrong with doing it like this.

1. User info is deleted upon reloading. Any user info created with this function is stored in the browser's RAM and is destroyed when the page is closed.

2. The existing user info (default info) can be accessed by anyone, even if they're not logged in.

3. Passwords are stored in plain text. This is so dangerous because if someone gets access to your database (which they can because it's front-end available) they will have your password. You NEED to hash it, and if you're not experienced with cybersecurity you should definitely use Firebase Google Authentication instead.

4. Input verification is done on the front-end. Of course, you don't have a back-end, but you want to do this on the back-end once you do some research into this. Otherwise, a user could directly fetch the backend from the console and bypass verification, thereby allowing SQL injection with zero effort.

5. Minor issue here. Your class names are not human-friendly to other developers or even future you. Please rename the input classes to something like "usernameBox," "passwordBox," and "loginErrorText."

There are a lot more I could list, but you really need to look into a tutorial on this because this is the most easily hackable code I've ever seen.

Document how to run or debug applications #2005 added official debugging documentation at Running and debugging your code which documents two approaches

1. via code lenses run | debug
2. via a launch.json configuration

Here is a hello world example how to debug a test using VSC and Metals via launch.json approach. We will use lihaoyi/utest library and set a breakpoint in a test.

1. Execute sbt new scala/scala-seed.g8 to create correct project structure

2. Open... sbt project with VSC or simply cd into project and execute code .

3. Replace ScalaTest with utest in build.sbt

I know that the size of union in C is the size of the largest member of the union.

If you know that, then I have some bad news for you :-) It's not necessarily true.

C implementations are allowed to insert padding in between members of structures, and after the final member of both structures and unions, in order to meet alignment requirements. The reason for the latter is to ensure, if you create an array of the union type, all elements of the array will be correctly aligned.

In this case (keeping in mind this is an example, as the sizes and alignment requirements may vary per platform), the most stringent requirement is probably that of uint32_t, in that it will prefer to be on a four-octet boundary.

That, combined with the fact that sTest is five octets in size, means that the structure size will be eight octets, not five.

normally if it is object it works fine without problem. But you may send string as type then try to parse it

This part:

Perhaps this example will be useful to find out how you can upload one or more files using Spring.

You have to specify that the string is unicode at the point of creation, not at the point of use:

I moved on and tried to start building my project with clang-cl and lld-link which provided a little more diagnostic output. I started getting warnings about linking different versions of the run time library. MSVC_RUNTIME_LIBRARY was correctly set and I had the /MTd flag in CMAKE_CXX_FLAGS and CMAKE_LINKER_FLAGS but by running ninja with the verbose setting I could see that my flags were being followed by /MDd which overwrote the previous runtime setting. Eventually I appended /MTd to CMAKE_CXX_FLAGS_DEBUG and CMAKE_CXX_FLAGS_RELEASE and now it's the last runtime flag in the compiler and link commands and I haven't had this problem since.