Resolve `view_to_component` limitations
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by tracing the view_to_component entry point named in the issue. The issue lists HTTP-method handling, ReactPy event attachment, and same-domain hyperlink interception as separate limitations, but names no files or tests; done would require defining and implementing the intended iframe-like behavior for these cases.
Written by the indexing model from the issue text.
Description
Current Situation and Proposed Actions
There are currently several limitations of using view_to_component.
- Requires manual intervention to change HTTP methods to anything other than
GET.- The initial HTTP request will probably always have to be
GET, but it might be reasonable to automatically handle other kinds of HTTP methods depending on what the user clicked on. - Realistically, the end goal is to make
view_to_componentbehave as similarly to an iframe as technologically possible.
- The initial HTTP request will probably always have to be
- ReactPy events cannot conveniently be attached to converted view HTML.
- It might make sense to give the user some kind of interface to "query select" certain rendered items, and attach ReactPy event functions to them.
- Has no option to automatically intercept click events from hyperlinks (such as
<a href='example/'></a>).- All hyperlinks that point to the current domain should probably be intercepted by ReactPy and rendered via
view_to_component. - Realistically, the end goal is to make
view_to_componentbehave as similarly to an iframe as technologically possible.
- All hyperlinks that point to the current domain should probably be intercepted by ReactPy and rendered via
- Dominant language
- Python
- Stars
- 357
- Forks
- 22
- Avg merge
- 10h 31m
- Merged PRs (30d)
- 2
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from reactive-python/reactpy-django
-
Add coverage tests Opencomplexity: 3 (low) priority: 3 (low) type: ci
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
complexity: 1 (high) priority: 1 (high)
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
complexity: 2 (medium) priority: 3 (low)
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
complexity: 1 (high) priority: 2 (moderate)
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
complexity: 2 (medium) priority: 2 (moderate) type: investigation
Difficulty 5/5 Over a week Newbie friendliness 20/100
All issues in reactive-python/reactpy-django
Similar issues
-
area/auth bug comp/agent P3 platform/discord type/security
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
NousResearch/hermes-agent#117848 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100