sandeepsingh11
commented
4 years ago Lastest commit fixes this. There is an added field for the choices (tails) that allows for an existing tail ID to be inputted. In shunin_handler.php, it looks up the ID and populates tail->fur with the found body text.
This way, duplicate choices will share tail IDs, leading to a shared anime answer.
FUTURE: there may be cases where I shouldn't share choices as anime answers can be a "bundle" (multiple answers / animes instead of a single ans / anime). This could lead to a drop in uniqueness and these bundles could be catering to a specific series of questions. I will see this as I continue populating the json anime file
Some questions are shared from different branches. For example:
In this case, the tail->fur property will contain the same body / text (steampunk scientific magic), but the current code will generate a different tail index for both of them. In that case, FMA will need to have 2 head values that point to each of the shared question's tail.
OR
There can be a "shared question" option in the Shunin form that, with JS, will grab the inputted tail index, populate the input field with the corresponding body text, and share that tail value, so that FMA will only contain 1 head val