Include child relationship names on sobject export

[paustint]

Fetch all related sobject metadata to obtain the child relationship name for any lookup fields when the user chooses the option to include this.

There are no other SOQL based ways to obtain this data, so we end up needing to take the performance hit of fetching metadata for all related sobjects

resolves #1102

[socket-security]

Report too large to display inline

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Possible typosquat attack	npm/object.assign@4.1.2	Did you mean: object~~.~~**-**assign	apps/docs/yarn.lock	⚠︎
Critical CVE	npm/vm2@3.9.13	CVE: GHSA-7jxr-cg7f-gpgv vm2 vulnerable to sandbox escape (CRITICAL) Affected versions: < 3.9.15 Patched version: 3.9.15	yarn.lock	⚠︎
Critical CVE	npm/vm2@3.9.13	CVE: GHSA-g644-9gfx-q4q4 vm2 Sandbox Escape vulnerability (CRITICAL) Affected versions: <= 3.9.19 Patched version: No patched versions	yarn.lock	⚠︎
Critical CVE	npm/vm2@3.9.13	CVE: GHSA-cchq-frgv-rjh5 vm2 Sandbox Escape vulnerability (CRITICAL) Affected versions: <= 3.9.19 Patched version: No patched versions	yarn.lock	⚠︎
Critical CVE	npm/vm2@3.9.13	CVE: GHSA-whpj-8f3w-67p5 vm2 Sandbox Escape vulnerability (CRITICAL) Affected versions: < 3.9.18 Patched version: 3.9.18	yarn.lock	⚠︎
Critical CVE	npm/vm2@3.9.13	CVE: GHSA-xj72-wvfv-8985 vm2 Sandbox Escape vulnerability (CRITICAL) Affected versions: < 3.9.16 Patched version: 3.9.16	yarn.lock	⚠︎
Critical CVE	npm/vm2@3.9.13	CVE: GHSA-ch3r-j5x3-6q2m vm2 Sandbox Escape vulnerability (CRITICAL) Affected versions: < 3.9.17 Patched version: 3.9.17	yarn.lock	⚠︎

View full report↗︎

Next steps

What is a typosquat?

Package name is similar to other popular packages and may not be the package you want.

Use care when consuming similarly named packages and ensure that you did not intend to consume a different package. Malicious packages often publish using similar names as existing popular packages.

What is a critical CVE?

Contains a Critical Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/object.assign@4.1.2
• @SocketSecurity ignore npm/vm2@3.9.13

Copilot reviewed 4 out of 4 changed files in this pull request and generated no suggestions.

Comments skipped due to low confidence (3)

libs/features/sobject-export/src/sobject-export-utils.ts:112

• The getterFn function should handle null or undefined values to avoid unexpected results. Suggestion: obj[_label] = getterFn(value ?? '');

obj[_label] = getterFn(value);

libs/features/sobject-export/src/sobject-export-utils.ts:248

• Ensure that field.name is unique within the context of the related SObject to avoid potential issues.

const childRelationship = sobjectsWithChildRelationships[relatedSObject]?.[field.name]?.relationshipName;

libs/features/sobject-export/src/SObjectExport.tsx:261

• The type cast to ListItem[] is unnecessary if FIELD_ATTRIBUTES is already of type ListItem[]. Consider removing the cast.

items={FIELD_ATTRIBUTES as ListItem[]}