Backport `reactpy_django` features to `reactpy`

Open
#1,258 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
django, python, react

Research direction

Start by reviewing the completed work in #110 and #1278, then read #578 and the proposed offline HTML fallback and hook work. No files or tests are named; done would require deciding which ReactPy-Django features can be supported in ReactPy and defining the scope and acceptance criteria for each backport.

Written by the indexing model from the issue text.

Description

priority-2-moderate
Current Situation

Currently, ReactPy-Django is significantly ahead of ReactPy in terms of feature set.

While some of ReactPy-Django's features can't exist on ReactPy (mostly due to the lack of a built-in database), a few of them can.

Proposed Actions

The following feature can be backported:

  • #110
  • #1278
  • Convert vdom_to_html to reactpy_to_html
  • #578
  • Support offline HTML fallback within template tags
  • use_query and use_mutation hooks (NOTE: This should probably become an external package)
Dominant language
Python
Stars
8.1k
Forks
332
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from reactive-python/reactpy

All issues in reactive-python/reactpy

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.