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
@casey thanks for the rapid response and clarifying this isn't yet expected to work at this time.
I do think there is an issue here as well with the incorrect error messages:
In the first case error: Expected identifier or string, but found '{' really shouldn't mention identifier, since, as you say, that's not currently supported.
In the second case error: Expected keyword xbut found identifiermydir`` is probably also wrong, since it doesn't seem that specifying x and hoping for shell expansion to work would lead to a good outcome.
Ah yeah, that is confusing. The reason you get: Expected identifier or string, but found '{' is because a shell-expanded string, x"foo" is accepted, and x is an identifier. x is accepted though, for shell-expanded string, so Expected keyword x but found idntifier is a correct error message.
The just parser is only dimly aware of keywords, and mostly treats them like identifiers, so it might be hard to improve the error message, which should ideally be something like Expected x keyword or string, but found '{'.
Consider the following justfile:
which, naively, I expected to work. But:
So, perhaps this is expected to work (i.e. following the error message and providing an identifier:
but:
So, I am not sure what the expected semantics of
[working-directory: ...]
are - the docs don't really tackle this.The text was updated successfully, but these errors were encountered: