Resolve `view_to_iframe` limitations

Open
#268 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
Domain
backend, web-dev

Research direction

Start by reading the implementation and usage of view_to_iframe. Investigate how iframe-to-parent events could be exposed and how args and kwargs are serialized into the URL, then determine which limitation has an actionable scope. Done means an agreed implementation direction, with documentation where needed.

Written by the indexing model from the issue text.

Description

complexity: 2 (medium) priority: 3 (low)
Current Situation and Proposed Actions

There are currently a few resolvable limitations of view_to_iframe.

  • No built-in method of signalling events back to the parent component.
  • All provided args and kwargs must be serializable values, since they are encoded into the URL.
    • Maybe we can wrap each individual view with another view that automatically pulls serialized arguments from the database?
    • Is resolving this actually worth it? I don't believe it's possible for standard Django views to accept objects are arguments, so is there any reason why converted views should behave differently?
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

  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-django

All issues in reactive-python/reactpy-django

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.