[ENH] Update JS client for auto ID generation when add

[spikechroma]

Description of changes

Summarize the changes made by this PR.

• Improvements & Bug fixes
  • ...
• New functionality
  • ...

Test plan

How are these changes tested?

• Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Documentation Changes

Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs repository?

[spikechroma]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• [ENH] Update documentation for generate ids changes #2775
• [ENH] Update JS client for auto ID generation when add #2757 👈
• [ENH] Generate IDs when not given in add  #2699 : 2 other dependent PRs (#2701 , #2719 )
• [CLN] Move validation logic to server #2709
• [CLN] Refactor code to extract out unpacking embeddings set from existing validation logic  #2686 : 1 other dependent PR (#2710 )
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @spikechroma and the rest of your teammates on Graphite

[github-actions]

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

• Can you think of any use case in which the code does not behave as intended? Have they been tested?
• Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
• If appropriate, are there adequate property based tests?
• If appropriate, are there adequate unit tests?
• Should any logging, debugging, tracing information be added or removed?
• Are error messages user-friendly?
• Have all documentation changes needed been made?
• Have all non-obvious changes been commented?

System Compatibility

• Are there any potential impacts on other parts of the system or backward compatibility?
• Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

• Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

[github-actions]

Please tag your PR title with one of: [ENH | BUG | DOC | TST | BLD | PERF | TYP | CLN | CHORE]. See https://docs.trychroma.com/contributing#contributing-code-and-ideas

[codetheweb]

lgtm

[codetheweb]

Suggested change

	const recordSet = arrayifyParams(reqParams);
	const { ids, embeddings, documents } = recordSet;
	if (!ids) {
	throw new Error("ids cannot be undefined");
	}
	validateIDs(ids);
	if (documents) {
	recordSet.embeddings = await computeEmbeddings(
	embeddingFunction,
	embeddings,
	documents,
	);
	}
	return recordSet as MultiRecordOperationParams;
	const recordSet: MultiRecordOperationParams = arrayifyParams(reqParams);
	const { ids, embeddings, documents } = recordSet;
	if (!ids) {
	throw new Error("ids cannot be undefined");
	}
	validateIDs(ids);
	if (documents) {
	recordSet.embeddings = await computeEmbeddings(
	embeddingFunction,
	embeddings,
	documents,
	);
	}
	return recordSet;

[spikechroma]

arrayifyParams actually gives MultiRecordOperationParamsWithIDsOptional type instead of MultiRecordOperationParams

[codetheweb]

should this be single backticks?

[spikechroma]

This is auto generated