types are extremely poor without coverage.

Open
#33 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
typescript
Domain
api

Research direction

Start by locating the EngineParameters declaration shown in the issue and review how engine names and parameters are exposed in the TypeScript API. Determine the intended coverage and source of truth for generated or maintained types, then verify that supported engines and their parameters are represented without the current broad Record<string, any> type.

Written by the indexing model from the issue text.

Description

Engine parameters is:
export type EngineParameters = Record<string, any>;

This is basically the same as not having ts support. There isn't even an enum or something for engine names. Auto generating types from code with gpt would result in more robust typing. Should matter since you want money for using your tools

Dominant language
TypeScript
Stars
95
Forks
33
Avg merge
8d 12h
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from serpapi/serpapi-javascript

All issues in serpapi/serpapi-javascript

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.