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
Currently we are testing our encoding against a fixed number number of scenarios. This means we may not be testing our encoding against every possible scenario. We know all known types and their structure, therefore it would be possible to build a tool that can generate a forc workspace that contains every possible test permutation.
The text was updated successfully, but these errors were encountered:
Given a lot of the new encoding work has been heavily battle tested I don't think there is much value in this in it's own right. In stead in should be superceded by #1795 where we can look at the new approach to encoding, and see how we want to test that more specifically.
Currently we are testing our encoding against a fixed number number of scenarios. This means we may not be testing our encoding against every possible scenario. We know all known types and their structure, therefore it would be possible to build a tool that can generate a
forc
workspace that contains every possible test permutation.The text was updated successfully, but these errors were encountered: