implementing frontend | restructuring data backend #9
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Screencast.from.29-12-23.02.24.11.PM.IST.webm
issues #2 #5
the above video shows how the frontend would look like
I choose using typescript react shadcn tailwind for the frontend
I choose react because in previous version plain html/css javascript was being used. it was hard to add new features and using react solves that
Also we can easily manage the states in react when the extension gets out of focus which is issue that is mension in #6
further I changed the json data structure in which backend and frontend were talking with each other
from
to
{"one_word": [{"question":"question1""answer":"answer1"},{"question":"question2":"answer":"answer2"}]}
this is more structured and allows to scale the extension for more types of questions in the future
if any suggestions and improvement, please inform.