This fixes issue #139, in which it was reported that deletions appear in the top row of the heatmap, normally reserved for substitutions by Ala.
In addition:
Some refactoring, TypeScript migration, and JSDoc creation has also been done.
The heatmap's y-axis tick mark labels have been made more readable.
@PlushZ provided a useful example in score set tmp:540c9d47-9e0c-4c56-839c-3b1249a957df. To test the bug fix using this example, you may change the ownership of that score set in a development instance of MaveDB.
The heatmap for this score set should now look like this:
The heatmap for score set urn:mavedb:00000001-a-1 is a good check against regressions, and it should look like this:
This fixes issue #139, in which it was reported that deletions appear in the top row of the heatmap, normally reserved for substitutions by Ala.
In addition:
@PlushZ provided a useful example in score set tmp:540c9d47-9e0c-4c56-839c-3b1249a957df. To test the bug fix using this example, you may change the ownership of that score set in a development instance of MaveDB.
The heatmap for this score set should now look like this:
The heatmap for score set urn:mavedb:00000001-a-1 is a good check against regressions, and it should look like this: