🚀 Feature: For functions, provide the type.

Open
#133 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
node.js, typescript
Domain
api, backend-api-design

Research direction

Start by reading the linked Appwrite #8329 issue, then inspect the Node.js SDK entry points for cloud-function context handling and its existing TypeScript declarations. The work is done when context type information is exposed uniformly through the SDK, with the resulting annotations covering the cloud-function context use case described here.

Written by the indexing model from the issue text.

Description

🔖 Feature description

This issue is the same as
Appwrite #8329 Issue

Simply put, this involves adding type information to the context of cloud functions. Although this can be implemented locally, I prefer to implement it uniformly within the SDK.

🎤 Pitch

Using TypeScript but the context is still untyped doesn't make sense. And providing a better, simpler type annotation is all that's needed.

👀 Have you spent some time to check if this issue has been raised before?
  • I checked and didn't find similar issue
🏢 Have you read the Code of Conduct?
Dominant language
TypeScript
Stars
257
Forks
45
Avg merge
11h 59m
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 appwrite/sdk-for-node

All issues in appwrite/sdk-for-node

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.