Runtime Type Information

Open
#701 1 comment 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
javascript, python
Domain
compilers

Research direction

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.

Written by the indexing model from the issue text.

Description

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.

Dominant language
Python
Stars
2.9k
Forks
218
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 TranscryptOrg/Transcrypt

All issues in TranscryptOrg/Transcrypt

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.