Runtime Type Information

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

还没有人认领这个 Issue。

评估

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

调研方向

The issue does not name any files, tests, or compiler entry points. Start by tracing how Python typing annotations are handled during transpilation and how generated JavaScript represents classes and properties. Done would require an agreed design and a verified way for generated JavaScript to access the requested type metadata.

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

描述

STATE: under consideration

I don't see a way to embed type information in the transpiled JS code that can be accessed at runtime. Currently I have entities defined in Python and am converting those to JS so I can use them as view models on the front-end. Everything is working great, except that I define the entity field types using the Python typing module and this type information is lost after transpiling. Note, I'm not looking for runtime type enforcement like is currently supported with mypy... I'm looking to use reflection in the javascript to understand what types my entity properties are.

First, is this doable and I'm just missing it?

Secondly, if not, then has any thought been put into this? The type information for class properties could be stored in some type of metadata field on the class itself. And, maybe something similar could be done for module-level variables and function parameters?

Love this tool, btw, so thanks for the work you've put into it.

主要语言
Python
星标
2.9k
派生
218
30 天内没有已合并 PR

贡献指南

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

从这里开始

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

TranscryptOrg/Transcrypt 的其他 Issue

查看 TranscryptOrg/Transcrypt 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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