All right, so now the time to put our data gracefully into our application, so for that purpose,
the first thing that will do is of this correct answers.
If we just take a look at our finished application, you might see that in the guidance, as we have
done, says we have answered correctly upon the total number of questions that we have admitted, right?
So let's head back into our application and inside this.
But having to do is that I remove this hardcoded value three and we're going to put up.
Correct.
So this defines the correct answers.
Times the index, so this is going to have container index, so let's just put up an index in here.
Now hit save.
Now, apart from this, the next refactoring is to be done in H2 Element.
So this H2 tag is going to be dangerously said in a statement.
So basically, this is the question of our application, so we'll get rid of this because it is going
to be a self-loathing tag.
No, inside this, they're going to put up dangerously.
Set in a steamer and that there's going to be equal to two sets of elevators inside it.
Now underscore underscore, Admiral.
And this is going to contain a question.
All right, so we have set it up a question as of now inside this debate, which we left empty back
at the time.
We are going to map our data and the data that we're making mapping is done, says data.
So answers.
That map now this map is going to take up a single answer every time.
And every time it takes up an answer as well as an index.
And this is going to Muppet.
Now, every time we want to return.
And said this done, we're going to put a button element, so let's just put up a button.
Now we are supposed to play this on to the inside elevator, so let's play the plays live inside curly
braces.
All right.
No, it's fine.
Now inside this written statement, we're going to have a button element, so let's put up a button
element.
Now, this button element is going to hold up a key as well as a class name, and the key is going to
be indexed, so let's just give it the index and give it a class name that is going to be equal to answer.
But.
All right, so we have a button or the gear class named after the class name, we'll be giving it an
unclaimed property so unclaimed.
No, this is going to be another function again, and we are going to call out every time to check answers,
so check.
And so now this is going to compare.
Correct answer.
The data was done so that we are given.
All right, so here we are checking a button element now, right after on click will be dangerously
setting down HDMI that is going to be equal to the answer that we're given.
So again, dangerously set in HDMI, that is going to have a double that of curly braces, then the
underscore underscore etched HTML.
And that is going to be cold with the answer.
All right, so now let's put our ability to work.
And seems like it isn't working.
So I'll manually just return it.
So our key?
And next on our list is a class name.
And on property.
All right.
So now is the time to close up and right, so let's close the button with a self-closing tag.
So Halliburton has been closed now, so it should be on to.
All right, so we are our final.
Now hit save.
So we have poured almost all the data that we needed in this no function or this Abdul GSX is complete
now let's run this application, but before we do that, I'd like to set up our models.
And I see that we have still one property that is left, and that is the next question.
Properties are, let's assign it.
And this is going to be assigned to a button that is at the end.
So give it up and click property.
Which is going to be equal to an next question that we're getting from a context judge, it's now time
to open up our model.
So let's open up our model now.