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
I can see from the closed issues and the RFC errata history that the "'" character is allowed in literals now. However, I didn't realise that initially, and was quite confused as to why the second test case in spec-examples.json included what I thought to be an invalid literal. Obviously I've tracked that down, but would it be worth making this more obvious?
One way to do so might be to remove that test from the spec-examples.json file (it doesn't actually appear in the RFC itself) and creating a small new test case file (something like spec-errata-examples.json perhaps) which would include any cases which reflect changes to the spec? That would potentially make it clearer for example that the spec has changed, and also point people in the direction of checking errata during implementation (yes, I know I should anyway, but it's not always glaringly obvious).
The text was updated successfully, but these errors were encountered:
I can see from the closed issues and the RFC errata history that the
"'"
character is allowed in literals now. However, I didn't realise that initially, and was quite confused as to why the second test case inspec-examples.json
included what I thought to be an invalid literal. Obviously I've tracked that down, but would it be worth making this more obvious?One way to do so might be to remove that test from the
spec-examples.json
file (it doesn't actually appear in the RFC itself) and creating a small new test case file (something likespec-errata-examples.json
perhaps) which would include any cases which reflect changes to the spec? That would potentially make it clearer for example that the spec has changed, and also point people in the direction of checking errata during implementation (yes, I know I should anyway, but it's not always glaringly obvious).The text was updated successfully, but these errors were encountered: