Thread strategyName from the typogenerator library through to results…#23
Merged
Thread strategyName from the typogenerator library through to results…#23
Conversation
….json and the frontend UI, replacing the client-side heuristic that attempted to infer variant class from Levenshtein edit distance. Added a candidate struct to carry the strategy name through the worker pipeline and a Strategy field on the Output struct. On the frontend, removed classifyVariant(), levenshtein(), and a duplicate shannonEntropy() definition. The variant filter dropdown is now dynamically populated from actual strategy names in the data. Also fixed a runtime bug where parseList() was called but never defined (replaced with splitAny).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue #4 resolved and unnecessary code from the frontend removed.