[danieljbruce]

Description

This pull request preserves nanosecond precision when timestamp microseconds equal zero.

Impact

Queries with BigQueryTimestamp parameters no longer lose sub-microsecond nanosecond precision.

Changes

• Update BigQueryTimestamp constructor in handwritten/bigquery/src/bigquery.ts to check pd.getMicroseconds() > 0 || pd.getNanoseconds() > 0 before serializing with pd.toISOString().

Testing

• Add a unit test in handwritten/bigquery/test/bigquery.ts verifying that bq.timestamp() preserves nanosecond precision when microseconds are 0 for both PreciseDate and ISO string inputs.

Alternatives

• Not merging this pull request would leave BigQueryTimestamp dropping nanosecond precision whenever the microsecond component happens to be zero (000), while merging carries negligible risk because timestamps without microseconds or nanoseconds continue using Date#toJSON().

[gemini-code-assist]

Code Review

This pull request updates the BigQueryTimestamp class to preserve nanosecond precision when converting to an ISO string, even if the microsecond precision is zero. A corresponding unit test has been added to verify this behavior. There are no review comments, so no additional feedback is provided.

[danieljbruce]

/gemini review

[gemini-code-assist]

Code Review

This pull request updates the BigQueryTimestamp class to preserve nanosecond precision when microseconds are zero. It also refines the JSDoc and TypeScript type definitions for the timestamp methods to explicitly return BigQueryTimestamp, and adds comprehensive unit tests to verify the preservation of nanoseconds under various conditions. There are no review comments to address.