decklist | code behind decklist.org , which generates DCI Registration | Generator Utils library

Use below code it's working for me

https://codesandbox.io/s/weathered-water-jm1ydv?file=/src/App.js

If you think about this in real world terms, you have a Deck that has instances of Card in it. The types of attributes or physical properties of the cards in the deck are all the same, they all have a Suit and a Number and in your business case they all have a Value as well. From a structural point of view they are identical, all that changes are the values for each of the properties.

If every Card has the same attributes, and the same behaviours, then there is no reason to create further sub-classes or even interfaces of these Cards.

In software design, we use inheritance and composition (Interfaces) to add attributes and behaviours to the base implementation; or to change existing behaviours. It is an anti-pattern to inherit from a Card just to change the values of the attributes and doing so can elad to confusion down the track. You really need to separate the concept of structure vs content. If the structure and beahviour

On top of this you have defined a list of suits and have declared that they have specific integer values, in C# we can encapsulate such fixed lists using an enum.

You can remove the code from onCreate, onUpgrade, onOpen and that will give you the results you are looking for.

The result from GetDeckList would be only one record: android_metadata, a table by default.

If you need to create tables in the future, then add the code back to onCreate, in that case, you could have some constants in your DBHandler for your new tables.

Finally, I recommend you have a Singleton to have only one instance of DBHandler to avoid memory leaks or memory allocations. Another piece of advice would be If you can use the abstraction library Room from the Android Jetpack, much better, this library will save you from important issues from using SQLite directly. If you want to check Room out, please check Room Setup

Right after I posted this question, I found this comment on the Prettier GitHub repo which indicates that it's by design that prettier prioritizes the rule of keeping import statements on a single line:

This is actually intended. We have a special case for import and require with single elements where we keep them in a single line. You don't get much more information when they are in two lines and they look worse with a series of imports. This was done due to common request from people using prettier.

First of all, I recommend you improve your style when naming variables as they make reading easier, for example that the class name are nouns and not a verb.

Getting to the bottom of the problem, never use (or try to use) global variables as they cause silent bugs if there is a better option and you don't understand how it works. In the case that you want a window where you ask the user to provide information on how to select an option that will then be used in the main window then it is advisable to use a QDialog. In the following example, this is done and the "Choose" button is linked to the accept slot so that it closes the window, and that information can be used to know that the "x" button of the window was not closed. Also I have created a property that has the selected text.

Edit to add after feedback:

I am not sure what you mean by "console log" but since the question is tagged with C# i will assume you mean the standard console. Perhaps something like this then:

You should add a key: Key(index) to your FlashcardCreateTile items to make them unique.

Flutter engine needs that to properly build your list

You wrote this