Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Modernize code (use typescript, use class syntax instead of prototype) #68

Open
TysonAndre opened this issue Apr 8, 2021 · 6 comments
Labels
bounty:$50 Bounty applies for fixing this issue (Parse Bounty Program) type:feature

Comments

@TysonAndre
Copy link

TysonAndre commented Apr 8, 2021

A switch to typescript may make sense in a major version

index.d.ts may get out of sync with the implementation. It may be easier to write everything in typescript and add a publish hook to convert code to typescript
(https://github.com/aws/aws-sdk-js-v3/blob/main/clients/client-dynamodb/package.json https://www.typescriptlang.org/docs/handbook/declaration-files/publishing.html#including-declarations-in-your-npm-package https://github.com/aws/aws-sdk-js-v3/blob/main/clients/client-dynamodb/tsconfig.json)

(the publish hook would trigger a typescript build to dist/ or a subdirectory)

Alternately, with --checkJs, jsdoc can be type checked in CI


Also, class syntax can be used in node 6+ - the upstream code was supporting node 4+ and declared function Client instead of class Client https://github.com/parse-community/node-apn/blob/master/lib/client.js


What are the maintainer's thoughts on those ideas? Would you accept PRs?

@davimacedo
Copy link
Member

Yes. I think that it makes sense and I'd be glad to review a PR.

@mtrezza mtrezza changed the title Idea: Modernize code (use typescript, use class syntax instead of prototype) Modernize code (use typescript, use class syntax instead of prototype) Mar 27, 2022
@parse-github-assistant
Copy link

Thanks for opening this issue!

  • ❌ Please edit your post and use the provided template when creating a new issue. This helps everyone to understand your post better and asks for essential information to quicker review the issue.

@mtrezza mtrezza added the bounty:$100 Bounty applies for fixing this issue (Parse Bounty Program) label Jul 16, 2023
@mtrezza
Copy link
Member

mtrezza commented Jul 16, 2023

Added a bounty so hopefully someone will pick this up.

@mrevanzak
Copy link

is this still valid?

@mtrezza mtrezza added bounty:$50 Bounty applies for fixing this issue (Parse Bounty Program) and removed bounty:$100 Bounty applies for fixing this issue (Parse Bounty Program) labels Dec 30, 2024
@mtrezza
Copy link
Member

mtrezza commented Dec 30, 2024

@mrevanzak yes, the issue is still up for grabs

@mrevanzak
Copy link

I would give it a try if it still $100

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bounty:$50 Bounty applies for fixing this issue (Parse Bounty Program) type:feature
Projects
None yet
Development

No branches or pull requests

4 participants