[TS] Support new field declaration for instances

Open
#288 0 comments 0 reactions 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
Feature
Clarity
Mostly clear
Activity status
Stale
Domain
devtools

Research direction

Start by tracing how instance field reads create fake objects and how input values resolution restores registered fields. Add support for declarations such as x["newField"] = 15 so the field is registered and restored during input resolution; the issue names no files or tests, so identify the relevant implementation and regression-test entry points first.

Written by the indexing model from the issue text.

Description

There should be an option to add fields x["newField"] = 15. Right now, reading of such field returns a fake object, but it isn't registered anywhere. Therefore, we won't restore it during input values resolution

Dominant language
Kotlin
Stars
33
Forks
27
Avg merge
4d 3h
Merged PRs (30d)
15

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 UnitTestBot/usvm

All issues in UnitTestBot/usvm

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.