Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue 51432: LKSM: special character in sample names is not working well on various pages #1658

Merged
merged 10 commits into from
Dec 9, 2024
Merged
Show file tree
Hide file tree
Changes from 8 commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions packages/components/package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion packages/components/package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@labkey/components",
"version": "6.4.0",
"version": "6.4.1-fb-issue51432.1",
"description": "Components, models, actions, and utility functions for LabKey applications and pages",
"sideEffects": false,
"files": [
Expand Down
6 changes: 6 additions & 0 deletions packages/components/releaseNotes/components.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,12 @@
# @labkey/components
Components, models, actions, and utility functions for LabKey applications and pages

### version 6.X
*Released*: X 2024
- Issue 51432: LKSM: special character not working well on various pages
- Warn user about missing quotes when pasting data into editable grid that containing comma
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Warn user about missing quotes when pasting data into editable grid that containing comma
- Warn user about missing quotes when pasting data into editable grid that contains a comma

- Replace `&` with a similar unicode character for lineage graph labels display as vis-network doesn't work well with `&`

### version 6.4.0
*Released*: 4 December 2024
- Remove assays.scss
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -789,7 +789,7 @@ describe('parsePastedLookup', () => {
valueDescriptors: List([{ display: 'abc', raw: 'abc' }]),
});
expect(parsePastedLookup(stringLookupCol, stringLookupValues, 'abc, valueD')).toStrictEqual({
message: { message: 'Could not find "abc", "valueD"' },
message: { message: 'Could not find "abc", "valueD". Please make sure values that contains comma(,) are properly quoted.' },
valueDescriptors: List([
{ display: 'abc', raw: 'abc' },
{ display: 'valueD', raw: 'valueD' },
Expand Down Expand Up @@ -820,7 +820,7 @@ describe('parsePastedLookup', () => {
valueDescriptors: List([{ display: 'abc', raw: 'abc' }]),
});
expect(parsePastedLookup(intLookupCol, intLookupValues, 'abc, valueD')).toStrictEqual({
message: { message: 'Could not find "abc", "valueD"' },
message: { message: 'Could not find "abc", "valueD". Please make sure values that contains comma(,) are properly quoted.' },
valueDescriptors: List([
{ display: 'abc', raw: 'abc' },
{ display: 'valueD', raw: 'valueD' },
Expand Down
23 changes: 13 additions & 10 deletions packages/components/src/internal/components/editable/actions.ts
Original file line number Diff line number Diff line change
Expand Up @@ -291,8 +291,12 @@ async function getLookupValueDescriptors(
return descriptorMap;
}

function lookupValidationError(value: string | number | boolean): CellMessage {
return { message: `Could not find ${value}` };
function lookupValidationError(value: string | number | boolean, fromPaste?: boolean): CellMessage {
let suffix = '';
if (fromPaste && typeof value === 'string' && value.toString().indexOf(',') > -1) {
suffix = '. Please make sure values that contains comma(,) are properly quoted.';
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
suffix = '. Please make sure values that contains comma(,) are properly quoted.';
suffix = '. Please make sure values that contain commas are properly quoted.';

}
return { message: `Could not find ${value}${suffix}` };
}

async function getLookupDisplayValue(column: QueryColumn, value: any, containerPath: string): Promise<MessageAndValue> {
Expand Down Expand Up @@ -455,16 +459,15 @@ export function addColumns(
if (insertFieldKey && leftColIndex < editorModel.orderedColumns.size - 1) {
let readOnlyEnded = false;
editorModel.orderedColumns.forEach((fieldKey, ind) => {
if (ind <= leftColIndex || readOnlyEnded)
return;
if (!editorModel.columnMap.get(fieldKey).readOnly)
readOnlyEnded = true;
else
altInsertFieldKey = fieldKey;
if (ind <= leftColIndex || readOnlyEnded) return;
if (!editorModel.columnMap.get(fieldKey).readOnly) readOnlyEnded = true;
else altInsertFieldKey = fieldKey;
});

if (altInsertFieldKey)
leftColIndex = editorModel.orderedColumns.findIndex(column => Utils.caseInsensitiveEquals(column, altInsertFieldKey));
leftColIndex = editorModel.orderedColumns.findIndex(column =>
Utils.caseInsensitiveEquals(column, altInsertFieldKey)
);
}

const editorModelIndex = leftColIndex + 1;
Expand Down Expand Up @@ -940,7 +943,7 @@ export function parsePastedLookup(
.slice(0, 4)
.map(u => '"' + u + '"')
.join(', ');
message = lookupValidationError(valueStr);
message = lookupValidationError(valueStr, true);
}

return {
Expand Down
33 changes: 33 additions & 0 deletions packages/components/src/internal/components/lineage/models.test.ts
Original file line number Diff line number Diff line change
Expand Up @@ -225,5 +225,38 @@ describe('lineage model', () => {
expect(nodes[childThreeNode.lsid].level).toEqual(-1);
expect(nodes[childFourNode.lsid].level).toEqual(0);
});

it('Issue 51432: special character in sample names result in: SyntaxError: unterminated character class', () => {
const childLsid = 'child-lsid';
const parentLsid = 'parent-lsid';

const childNode = LineageNode.create(childLsid, {
parents: [{ lsid: parentLsid, name: '&4[0' }],
name: '&4[0_1001'
});

const parentNode = LineageNode.create(parentLsid, {
children: [{ lsid: childLsid, name: '&4[0_1001' }],
name: '&4[0'
});

const result = LineageResult.create({
nodes: {
[parentNode.lsid]: parentNode,
[childNode.lsid]: childNode,
},
seed: childNode.lsid,
});

const { edges, nodes } = generateNodesAndEdges(result);

expect(Object.keys(edges).length).toEqual(1);
expect(Object.keys(nodes).length).toEqual(2);

expect(nodes[parentNode.lsid].level).toEqual(-1);
expect(nodes[parentNode.lsid].label).toEqual('&4[0');
expect(nodes[childNode.lsid].level).toEqual(0);
expect(nodes[childNode.lsid].label).toEqual('&4[0_1001');
});
});
});
20 changes: 19 additions & 1 deletion packages/components/src/internal/components/lineage/models.ts
Original file line number Diff line number Diff line change
Expand Up @@ -781,6 +781,7 @@ function addEdges(
}
}

const FULLWIDTH_AMPERSAND = '&'; // U+FF06, use as alt display for & so vis-network won't error out
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So odd that this is even a thing.

function createVisNode(
node: LineageNode,
id: string,
Expand All @@ -791,11 +792,28 @@ function createVisNode(
// show the alternate icon image color if this node is the seed or has been selected
const { image, imageBackup, imageSelected, imageShape } = node.iconProps;

let nodeLabel = node.name;
// Issue 51432: LKSM: special character in sample names result in client side exception: SyntaxError: unterminated character class
// vis-network does special processing for labels that evaluates to true for `/&/.test()`
if (nodeLabel?.indexOf('&') > -1) {
// for labels that starts with '&', the entire label is replaced with '&lt;' by vis
if (nodeLabel.startsWith('&')) {
nodeLabel = nodeLabel.replace('&', FULLWIDTH_AMPERSAND);
}

try {
new RegExp(nodeLabel);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably not a huge deal, but since regular expressions and exception throwing are relatively expensive, perhaps it would be more efficient to always do the replaceAll. Or are there cases where this substitution isn't a good thing?

Copy link
Contributor Author

@XingY XingY Dec 7, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was hoping to preserve the original labels as much as possible. The hope is that there aren't many that contains & to trigger this code.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably true that there aren't many &-names, or we would have heard more about this problem, and maybe the world of JavaScript is different in this regard than Java, but I still think it's more efficient (and targeted) to do the replacement without regex construction, especially since it seems like this RegExp construction could throw an error for other reasons than the &.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure that makes sense. Since user can't copy label from the vis canvas, it's no harm to do the replacement more aggressively. Updated to use replaceAll instead.

} catch (error) {
// vis-network is not able to tolerate the presence of '&' in certain strings due to Uncaught SyntaxError from `new RegExp()`. Encoding does not help.
nodeLabel = nodeLabel.replaceAll('&', FULLWIDTH_AMPERSAND);
}
}

return {
kind: 'node',
id,
lineageNode: node,
label: node.name,
label: nodeLabel,
level: level(depth, dir, false),
title: getLineageNodeTitle(node, true),
image: {
Expand Down