Skip to content

Provide a global CategoriesEnum #82

@kasey-mcfadden

Description

@kasey-mcfadden

Issue

CategoriesEnum definitions in the SDK are identical but scoped per-namespace:

src/api/resources/accounting/types/CategoriesEnum.ts
src/api/resources/ticketing/types/CategoriesEnum.ts
...etc.

This forces consumers to import a namespace-specific enum even when they just need the category value (e.g., for link-token requests, DB storage, or shared app logic).

Please consider exporting a single, global CategoriesEnum (or Category) that can be used across product namespaces.

Current behavior

import { Merge } from '@mergeapi/merge-node-client'

const categories = [Merge.ticketing.CategoriesEnum]
// or
const categories = [Merge.crm.CategoriesEnum]

Desired behavior

// Option A (top-level)
import { CategoriesEnum } from '@mergeapi/merge-node-client'
const categories = [CategoriesEnum]

// Option B (central types module)
import { CategoriesEnum } from '@mergeapi/merge-node-client/api/types'
const categories = [CategoriesEnum]

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions