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
The transformation currently keeps the order of strings the same as they appeared in the codebase. This makes literals that are close to each other (and possibly related to each other) close in the output.
For example in the sample in the readme, the result is ["property", "with", "a string literal", "other", "call", "is", "here"]. I think it would be better to sort them, for example put them in alphabetical order. That would make the example like: ["a string literal", "call", "here", "is", "other", "property", "with"].
This would make larger programs even harder to decypher, as a reader has no idea where to look for related literals.
The text was updated successfully, but these errors were encountered:
The transformation currently keeps the order of strings the same as they appeared in the codebase. This makes literals that are close to each other (and possibly related to each other) close in the output.
For example in the sample in the readme, the result is
["property", "with", "a string literal", "other", "call", "is", "here"]
. I think it would be better to sort them, for example put them in alphabetical order. That would make the example like:["a string literal", "call", "here", "is", "other", "property", "with"]
.This would make larger programs even harder to decypher, as a reader has no idea where to look for related literals.
The text was updated successfully, but these errors were encountered: