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
From a discussion in #230, it would be helpful to have test vectors for all of these keys. One possible solution would be a column next to description that either contains the test vectors directly, or points to an external document where they can be found.
The text was updated successfully, but these errors were encountered:
I can't find the issue right now, but one of them in here talks about converting the primary entry-point to be a JSON doc, which would be much easier to extend with fields like "fixtures" rather than just adding more ordered columns. I think there was some agreement about making it compile-to-CSV so table.csv remains intact as is but the table.json is what we edit to add new entries.
From a discussion in #230, it would be helpful to have test vectors for all of these keys. One possible solution would be a column next to description that either contains the test vectors directly, or points to an external document where they can be found.
The text was updated successfully, but these errors were encountered: