Feat/colorize actions

[stackdump]

Update ./static build to use different files for css, js, svg

Sync styles and behavior with ./public/model.svg - (single file)

Known issues - react build does not yet support new v1 features: colored tokens & Token / vector support in schema def

Summary by CodeRabbit

• Documentation

  • Updated user docs to include a new export option for Python and a dedicated test model section with a short URL for direct access.

• New Features

  • Launched an enhanced interactive model visualization with dynamic simulation controls, improved event handling, and a refined interface for model interaction.

• Style

  • Improved the code editor with updated placeholder text and scrollable content.
  • Introduced new visual styling for diagram elements with modern color themes and responsive design.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request updates documentation, application styling, and interaction modules. In the documentation, a Python export option and a short URL test model section have been added to the README, and the task lists in TODO have been expanded. In the application, CSS is updated to allow scrolling in the source area, while the code editor configuration in App.tsx is streamlined by removing syntax highlighting support. Additionally, the legacy editor HTML file is removed, and the main HTML file is overhauled with interactive SVG elements for Petri net visualization. New CSS and JavaScript files provide a framework for rendering and interacting with Petri nets.

Changes

File(s)	Change Summary
README.md	Added a new Python export option in the Goals section and introduced a "Test model with shortURL v1" section with a link to a test model.
TODO.md	Expanded task lists by adding new tasks under "WIP" and "BACKLOG", and updated tasks in the "DONE" section.
src/App.css	Added overflow: auto; to the #source selector for scrollable content.
src/App.tsx	Removed the rehypePrism import and the rehypePlugins prop; updated the editor height calculation, placeholder text (to "source v1"), and simplified font styling.
static/editor.html	Removed the entire file that provided a Petri net visualization interface.
static/index.html	Revamped HTML structure with a modern DOCTYPE, meta tags, new SVG elements replacing the iframe, a clickable title linking to "https://pflow.xyz", and enhanced JavaScript for handling model updates and event logging.
static/pflow.css & static/pflow.js	Introduced new files: pflow.css defines styles for Petri net elements (places, transitions, arcs, labels, tokens, etc.) and pflow.js implements functionality for visualizing and interacting with Petri nets using SVG, including functions for rendering, transition logic, token updates, and event handling.

Sequence Diagram(s)

sequenceDiagram
    participant U as User
    participant I as Index.html (SVG Canvas)
    participant PN as pflow.js (Petri Net Module)
    
    U->>I: Clicks on a transition element
    I->>PN: Sends fire transition request
    PN->>PN: Validates transition (canFire / isInhibited)
    alt Transition Valid
        PN->>PN: Updates tokens (updateTokens)
        PN->>I: Renders updated SVG state
    else Transition Invalid
        PN->>I: Sends error/warning message
    end

Loading

Poem

I'm a bunny on a code-filled spree,
Leaping through changes so sprightly and free.
Python exports and SVGs make my ears perk high,
Petri nets and tasks under a bright digital sky.
With every line hopped over, my heart does a little jig—
Hopping along in code, happy as a rabbit gig!

---

📜 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 94be448 and 7ed0504.

⛔ Files ignored due to path filters (2)

• public/model.svg is excluded by !**/*.svg
• static/model.svg is excluded by !**/*.svg

📒 Files selected for processing (8)

• README.md (2 hunks)
• TODO.md (1 hunks)
• src/App.css (1 hunks)
• src/App.tsx (3 hunks)
• static/editor.html (0 hunks)
• static/index.html (1 hunks)
• static/pflow.css (1 hunks)
• static/pflow.js (1 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

---

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.
  • 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 generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.