feat: implement Phoenix LiveView UI and PostgreSQL persistence#12
Merged
Conversation
nachodall
force-pushed
the
web-interfacec
branch
from
573bb28 to
acbef04
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR completes requirement 2 of the Forth Interpreter project by transforming the standalone evaluator into a web application. The core logic has been integrated into a Phoenix LiveView environment, providing a reactive interface and persistent storage for execution history.
Key changes:
Architecture Refactor: Compile the proyect with Phoenix and moved the core logic to lib/forth_interpreter_elixir/forth.ex and integrated it into the Phoenix application tree.
Persistence Layer: Implemented the Interpreters.Execution schema and Ecto migrations to store program inputs and stack results in PostgreSQL.
UI: Created a ForthLive module that handles real-time code evaluation and dynamic updates to the history table without page reloads.
Boilerplate and assets: Added necessary Phoenix boilerplate, including Tailwind CSS (via DaisyUI) and core UI components for a polished look.
Closes #11