Ken frontend

[ken-zlai]

Summary

This PR contains two major updates to the project:

1. Frontend is built and served with Node.js
   This let's us use SSR for faster load times if we choose to use it.
2. Wireframe of the app
   I've created a basic wireframe of our app with left nav, api calls/configs, etc. We will expand this as Eugene ramps up on exactly what it looks like

Checklist

• Added Unit Tests
• Covered by existing CI
• Integration tested
• Documentation update

Summary by CodeRabbit

• New Features

  • Introduced a multi-stage build process for Docker, enhancing the deployment of the application.
  • Added new services in Docker Compose for improved application structure.
  • Implemented Tailwind CSS for styling and theming in the frontend.

• Documentation

  • Updated README files for better clarity on setup and usage instructions.
  • Added a new configuration file for frontend components.

• Bug Fixes

  • Corrected indentation and configuration issues in Docker Compose.

• Tests

  • Expanded testing capabilities with new scripts for integration and unit tests.

• Style

  • Enhanced CSS styling with Tailwind and custom variables for light/dark themes.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The changes introduce enhancements across various project files, including updates to the .gitignore to exclude additional build artifacts and temporary files. The build.sbt file is updated with new dependency versions, while the Docker setup is refined with a multi-stage build process and improved service configurations in docker-init/compose.yaml. The frontend is restructured with new configuration files and updated scripts for testing and building, reflecting a comprehensive update to the project's build and deployment processes.

Changes

File(s)	Change Summary
.gitignore	Added entries to ignore various build artifacts, temporary files, and environment configurations for Java, Python, Spark, frontend assets, and test results.
build.sbt	Updated dependency versions for Scala, Spark, Flink, Jackson, and Avro; modified frontend build command and updated task dependencies in the hub project.
docker-init/Dockerfile	Introduced a multi-stage build process; updated Python dependencies; modified paths for scripts and requirements; set up application directory structure.
docker-init/README.md	Updated instructions for initializing demo data with Docker; clarified access to web server and data table locations.
docker-init/compose.yaml	Added new services and modified existing configurations, including health checks and environment variables for app and frontend services.
docker-init/frontend/Dockerfile	Implemented a multi-stage build for the frontend application, specifying build commands and exposing the correct port.
docker-init/start.sh	Changed execution flow to run ./hub/bin/hub directly, removing error handling for the previous Python script.
frontend/README.md	Restructured content to focus on the Chronon frontend, added installation and development instructions, and clarified testing and best practices.
frontend/components.json	Introduced a new configuration file for frontend components with Tailwind CSS setup and TypeScript support.
frontend/eslint.config.js	Added a new ESLint rule for Svelte files to handle unused variables more effectively.
frontend/package.json	Added new scripts for Docker builds and modified existing test scripts; introduced new dependencies to enhance functionality.
frontend/playwright.config.ts	Updated testDir property to reflect new directory structure for integration tests.
frontend/postcss.config.js	Added a new configuration file for PostCSS with Tailwind CSS and Autoprefixer plugins.
frontend/src/app.css	Created a new CSS file using Tailwind CSS for theming with custom properties for light and dark modes.
frontend/src/app.html	Modified HTML structure (details not fully provided).

Possibly related PRs

• Docker init #20: This PR also involves modifications to the .gitignore file, specifically adding a new entry to ignore *.db files, which is related to the general enhancements made to the .gitignore in the main PR.
• Wire up Play frontend + server in docker setup #24: This PR includes updates to the docker-init/Dockerfile, which also involves the handling of build artifacts and the execution of scripts, similar to the changes made in the main PR regarding the .gitignore file and the overall project structure.

Suggested reviewers

• piyush-zlai
• chewy-zlai

Poem

In the burrow where code does grow,
Changes hop with a joyful glow.
New scripts and builds, a dance of delight,
With Docker and Svelte, everything's bright!
So let’s cheer for the code we refine,
A project reborn, oh how divine! 🐇✨

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.