Resolve `view_to_iframe` limitations

未关闭
#268 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
停滞
技术栈
django, python, react
领域
backend, web-dev

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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?
主要语言
Python
星标
357
派生
22
平均合并
10 小时 31 分钟
30 天内合并 PR
2

贡献指南

这个仓库没有索引到贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

reactive-python/reactpy-django 的其他 Issue

查看 reactive-python/reactpy-django 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。