Runtime: give the VM a name
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 21
- Forks
- 23
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 17
Description
When we get an error in the runtime, anything in the jobcode is said to belong to vm:module(0)
I'm sure that when we create the VM context, we can actually pass a name for the environment.
It would be ideal to use the step name (converted to a kebab-cased slug and maybe truncated to 10 or so characters) here.
This will also help the global functions
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the runtime code that creates the VM context and inspect how the current vm:module(0) name is assigned. Trace the available step name and determine how it is passed into the context; done means runtime errors and global functions use the resulting kebab-cased, suitably shortened VM name.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100