Warn user of unexported identifiers available in globals that are used in job code
Open
Nobody has claimed this yet.
DevX
enhancement
- Dominant language
- TypeScript
- Stars
- 21
- Forks
- 23
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 17
Description
Description
User might forget to export existing functions from the globals file.
eg.
const USER_DEFAULT = 'something'
And then go ahead to use this value in job code like below.
fn(state=> {
state.user = state.response.user || USER_DEFAULT;
return state;
})
This code will error since USER_DEFAULT was never exported.
With the info we have during compile-time. we can notify users whenever they make these mistakes.
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
No file, test, or entry point is named. Start by locating the compile-time handling of globals and job code, then determine how references to unexported global identifiers are represented. Done means users are notified when job code uses a global that exists but was not exported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100