You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I'm seeing a weird behavior with v1.4.0 (not sure about how far back it goes though), that contracts attaching to a key is not evaluated, only contracts that attach after the value gets evaluated.
To Reproduce
Using the sample code from the documentation:
nickel eval sample.ncl --field=opt_level # evaluates to "A4", which is wrong
nickel eval sample.ncl --field=opt_level2 # contract broken by a value, which is expected
After a bit more experimentation, it seems only the --field argument is concerned (it was introduced in 1.3, IIRC). A fix is on the way, and this might mandate a 1.4.1 release - silently ignoring contracts is bad.
Describe the bug
I'm seeing a weird behavior with v1.4.0 (not sure about how far back it goes though), that contracts attaching to a key is not evaluated, only contracts that attach after the value gets evaluated.
To Reproduce
Using the sample code from the documentation:
Environment
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: