Fiddle: add fields to KibaException

[krishan711]

Description

[Copilot]

Pull Request Overview

This PR enhances error handling by extending KibaException with additional context fields and ensuring those fields are populated in the Requester.

• Extend the KibaException class to include exceptionType and fields properties.
• Update Requester to extract and pass exceptionType and fields from the error response when throwing exceptions.
• Document the change in the CHANGELOG.md.

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
src/requester/requester.ts	Pass exceptionType and fields from errorContent to KibaException
src/model/kibaException.ts	Added exceptionType and fields properties and updated constructor
CHANGELOG.md	Added entry for new KibaException properties

Comments suppressed due to low confidence (4)

src/model/kibaException.ts:2

• Add JSDoc comments to the KibaException class and its new exceptionType and fields properties to explain their purpose and usage.

export class KibaException extends Error {

src/model/kibaException.ts:7

• [nitpick] Consider refactoring this constructor to accept a single options object for optional parameters (exceptionType and fields) to improve readability and ease future extensions.

  public constructor(message: string, statusCode?: number, exceptionType?: string, fields?: Record<string, string>) {

src/requester/requester.ts:97

• Add unit tests to verify that exceptionType and fields from the error response are correctly propagated through KibaException when an error occurs.

        throw new KibaException(errorContent.message, response.status, exceptionType, fields);

src/requester/requester.ts:95

• Add a type check to ensure errorContent.fields is an object mapping strings to strings before assigning, preventing potential runtime errors if the response shape is unexpected.

        const fields = errorContent.fields || {};