Exceptions not friendly to browser console

Open
#718 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript, python
Domain
compilers

Research direction

Start by reproducing the Exception and assert examples with --dassert, then inspect the generated JavaScript and the resulting Firefox console output. Trace how raised exceptions and failed assertions are translated, and consider the work complete when both examples show useful messages and a stack trace in the browser console.

Written by the indexing model from the issue text.

Description

Thank you so much for the code, Transcrypt is becoming awesome. Now to the issue:

raise Exception("Brouhaha!!!1")
assert False, "assert works in js"  # cannot debug this in JS console

Any one of the above exceptions appear in Firefox console as:
uncaught exception: unknown (can't convert to string)
...and there is no stacktrace.

(I compile with --dassert because I want assertions to run in JS.)

This is too unfriendly and impossible to debug, I am afraid.

If I am missing something, of course, please let me know.

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.