Add frontend skeleton with React app loader

[N3XT0R]

Summary

• scaffold frontend with Vite config and translation loader
• add dummy React SettingsPage with example REST and AJAX fetches
• introduce PHP scaffolding for settings page registration and React app loading

Testing

• composer test (fails: No code coverage driver with path coverage support available)

---

https://chatgpt.com/codex/tasks/task_e_689207eb9dcc8329977597a42f631892

Summary by CodeRabbit

• New Features

  • Introduced a modern React-based frontend with a settings page, supporting dynamic configuration and internationalization.
  • Added German, French, Italian, and Russian translations for improved localization.
  • Integrated Tailwind CSS for frontend styling.
  • Established a Vite-powered build system for efficient development and production builds.

• Chores

  • Updated project configuration files and .gitignore to support new frontend structure and dependencies.

• Documentation

  • Added initial HTML entry point and configuration files for frontend setup.

• Refactor

  • Introduced new backend PHP classes and interfaces to support React app integration and WordPress settings page registration.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This change introduces a new React-based frontend for a WordPress plugin, including initial app structure, internationalization support, Tailwind CSS styling, and project configuration. It also adds German, French, Italian, and Russian translation files. On the backend, new PHP classes and interfaces are scaffolded to support loading and registering the React app within the WordPress admin, though most methods are placeholders.

Changes

Cohort / File(s)	Change Summary
Frontend App Components frontend/App.jsx, frontend/components/SettingsPage.jsx, frontend/main.jsx	Adds a React App component that reads global config and renders SettingsPage. SettingsPage performs REST GET and AJAX POST requests using passed props. main.jsx bootstraps the React app on DOM load targeting a specific root element.
Frontend Project Configuration and Assets frontend/package.json, frontend/vite.config.js, frontend/index.html, frontend/index.css, .gitignore	Adds frontend project setup with Vite, React, Tailwind CSS, and WordPress i18n dependencies. Introduces Vite config with build and dev server settings. Adds HTML entry point with root div and script module. Adds Tailwind CSS base directives in CSS. Updates .gitignore to exclude build and node_modules directories.
Internationalization Support frontend/i18n-loader.js, frontend/translations/de_DE.json, frontend/translations/fr_FR.json, frontend/translations/it_IT.json, frontend/translations/ru_RU.json	Adds a dynamic i18n loader script that fetches locale JSON files and registers translations with WordPress i18n system. Adds locale JSON files for German, French, Italian, and Russian with localized UI strings and messages for the frontend.
WordPress React Integration Backend src/Infrastructure/WordPress/React/ReactAppLoader.php, src/Infrastructure/WordPress/React/Components/XPubSettingsAppLoader.php	Introduces PHP classes for loading React apps in WordPress. ReactAppLoader is a final class with a constructor and a load method stub for enqueuing scripts and injecting data. XPubSettingsAppLoader depends on ReactAppLoader and PluginContext and registers the React app with configuration data for nonce, URLs, and nonces.
WordPress Settings Page Registration src/Infrastructure/WordPress/Admin/SettingsPageRegistrar.php, src/Infrastructure/WordPress/Hook/HookRegistrableInterface.php	Adds a HookRegistrableInterface with a register() method. Adds a final class SettingsPageRegistrar implementing this interface, with stub methods for registering hooks, adding options page, rendering the page, and enqueueing assets. These are placeholders for WordPress admin settings page lifecycle management.

Sequence Diagram(s)

sequenceDiagram
    participant Browser
    participant index.html
    participant main.jsx
    participant App.jsx
    participant SettingsPage.jsx
    participant WordPress REST API

    Browser->>index.html: Loads page
    index.html->>main.jsx: Loads main.jsx as module
    main.jsx->>App.jsx: Renders <App />
    App.jsx->>SettingsPage.jsx: Passes config props
    SettingsPage.jsx->>WordPress REST API: GET /xpub/v1/example (with nonce)
    SettingsPage.jsx->>WordPress REST API: POST actionUrl (AJAX with nonce)

Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~15 minutes

Poem

🐇
In the garden of code, new shoots appear—
A React frontend, crisp and clear!
With translations that hop from DE to RU,
Tailwind breezes styling through.
PHP stubs await their spring,
As WordPress hooks begin to sing.
Oh, what a lovely patch to review!

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a098c24 and eb5e4ce.

📒 Files selected for processing (17)

• .gitignore (1 hunks)
• frontend/App.jsx (1 hunks)
• frontend/components/SettingsPage.jsx (1 hunks)
• frontend/i18n-loader.js (1 hunks)
• frontend/index.css (1 hunks)
• frontend/index.html (1 hunks)
• frontend/main.jsx (1 hunks)
• frontend/package.json (1 hunks)
• frontend/translations/de_DE.json (1 hunks)
• frontend/translations/fr_FR.json (1 hunks)
• frontend/translations/it_IT.json (1 hunks)
• frontend/translations/ru_RU.json (1 hunks)
• frontend/vite.config.js (1 hunks)
• src/Infrastructure/WordPress/Admin/SettingsPageRegistrar.php (1 hunks)
• src/Infrastructure/WordPress/Hook/HookRegistrableInterface.php (1 hunks)
• src/Infrastructure/WordPress/React/Components/XPubSettingsAppLoader.php (1 hunks)
• src/Infrastructure/WordPress/React/ReactAppLoader.php (1 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch codex/ubernehmen-von-frontend-skelett

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • Explain this complex logic.
  • 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 explain this code block.
• 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 explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this 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.