premake / premake/premake-core
It would be nice to have better error identification.
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.6k
- Forks
- 654
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 13
Description
Right now when you get a simple error such as "String expected got table" you have to have either been retrying your script after each line edit to know where to look, or have a good feeling because you have been testing many things.
What would be nice is if the error told you the line of which the error occurred on. This could help more people figure out their own problems before having to seek help here.
Contributor guide
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 tracing how Premake reports errors such as "String expected got table" and identify where source location information is available or lost. Confirm the expected behavior for a script error, then verify that the reported line points to the line where the error occurred.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, lua
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100