0xMiden / 0xMiden/examples

Issues/feedback related to v0.3

Open
#166 4 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
21
Forks
28
PR merge metrics
No merged PRs in 30d

Description

Issues and feedback related v0.3
```[tasklist]
### Tasks
- [x] Readability of "Help" section needs to be improved
- [x] Behaviour of the "Instructions" section is inapproriate - it simply toggles between appearing and disappearing when "instructions" is clicked. And also it replaces the output section which loses results of the last run.
- [ ] Implement links for each example, in a way they can be shared individually
- [x] Advice provider example runs into failures
- [x] Std library example runs into failures
- [x] Behaviour of "proving" toast component when tried to prove on a failing code needs to be fixed
- [ ] The button to download the ".masm" files is counterintuitive - it is hardly recognizable as a download button
- [ ] According to its behaviour the collapse button in the input panel is supposed to change from "+" to "-" rather than changing its colour from green to grey.
- [ ] https://github.com/0xPolygonMiden/examples/issues/174
- [ ] The debug view has few areas where it can be fixed/improved: the relevance of green numbers at the initial stage is very less, the "|<" and "<<" buttons does not appear to work when pressed first - shall be disabled in that case,
- [ ] It's hard to understand what is the VM's stack when going backwards; esp. if the state is changed to use a table.
- [x] Using the buttons ">>" and ">|" seem to print only the last state of the VM. That is not super useful for debugging one wants to see all intermediary values.
- [x] Verification of the matrix multiplication doesn't work
- [x] There is no output shown when "Prove" button is clicked
```

Contributor guide

Open the contributing guide

Research direction

This is a meta-issue tracking multiple frontend and UI bugs for version 0.3 of a tool. The tasks involve fixing UI components like toasts, buttons, and debug views, and improving behaviors like example linking and file downloads. Start by exploring the frontend codebase to locate the relevant UI components (Help section, Instructions panel, download button, debug view controls). Check the linked issue #174 for more context. 'Done' means each checked task in the list is addressed.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.