Skip to content

Limit the exposed API to necessary methods and types #451

@merlinnot

Description

@merlinnot

Since we're working on a v3 release, it might be wise to revise the API of the library. Multiple types are exposed that seem not necessary, which might result in issues when internal structure of the library is modified (e.g. LegacyEvent).

It's also easier for developers when autocomplete suggests only usable types and it's not bloated with internals.

We should verify that all exported types actually belong to the API layer. This can be done by modifying the following:

export * from './config';
export * from './cloud-functions';
export * from './function-builder';

in the following way:

export { Only, Necessary, Types } from './config';
export { No, Internals } from './cloud-functions';
export { Nice, And, Small } from './function-builder';

Metadata

Metadata

Assignees

No one assigned

    Labels

    tracked internallyIssues that are tracked internally, even though the issue is closedtype: cleanup

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions