Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong layout in blame error message involving records #212

Closed
yannham opened this issue Nov 17, 2020 · 0 comments · Fixed by #213
Closed

Wrong layout in blame error message involving records #212

yannham opened this issue Nov 17, 2020 · 0 comments · Fixed by #213
Assignees

Comments

@yannham
Copy link
Member

yannham commented Nov 17, 2020

Describe the bug
When showing a blame error for a record contract, the underlining that points at the problematic field is off. Likely, #182 introduced a new simplified row syntax, but the code that determines the positioning of the underline and the accompanying label has not been updated accordingly.

To Reproduce

$nickel <<< 'deepSeq Assume({ a: { b: Num } }, {a = {b = "a"}}) 1'
error: Blame error: contract broken by a function.
  ┌─ :1:14
  │
1 │ {a: {b: Num}}
  │                expected field type
  │

Expected behavior
Have expected field type message rightly positioned with a line under Num:

error: Blame error: contract broken by a function.
  ┌─ :1:9
  │
1 │ {a: {b: Num}}
  │         --- expected field type
  │
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant