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

Version 2 #40

Closed
4 of 12 tasks
drewjbartlett opened this issue Apr 5, 2018 · 12 comments
Closed
4 of 12 tasks

Version 2 #40

drewjbartlett opened this issue Apr 5, 2018 · 12 comments
Assignees

Comments

@drewjbartlett
Copy link
Collaborator

drewjbartlett commented Apr 5, 2018

Making a place to document the changes on V2

  • Rewrite entirely in TypeScript
  • Properly declare and import type definitions Properly declare and import type definitions #41
  • Fix all tests Fix tests for v2 #46
  • api renamed to http
  • swap qs for qs-stringify since we only use that method https://www.npmjs.com/package/qs-stringify
  • Allow for other promise-based http services to be used in place of axios with injection
  • Rewrite version 2 docs to reflect updates
  • Rewrite version 2 docs in nuxt (and maybe markdown)
  • Extract debugger to allow easier testing and optionally include based off ENV
  • Extract custom routes into package
  • Add plugin system to allow syntax like rapid.use(customRouter)
  • Fix nasty inheritance chain
@drewjbartlett
Copy link
Collaborator Author

@mgred I'm going to add a lot more features here but I figured for now we can use this to track progress and such. Feel no obligation to help me out, but if you want to it'd be much appreciated :D

@mgred
Copy link
Collaborator

mgred commented Apr 6, 2018

@drewjbartlett that sounds like a plan! I will get into your branch over the weekend and see if there is something to add here.

@drewjbartlett
Copy link
Collaborator Author

@mgred Awesome thanks! More than anything I need help getting proper ts declarations and compiling in place. Right now I am a bit lost on some of those things :D

@mgred
Copy link
Collaborator

mgred commented Apr 6, 2018

@drewjbartlett Alright, no problem! I think I can help there.

@yihou
Copy link

yihou commented Apr 7, 2018

Hi @drewjbartlett, I think I can help out, where can I start from?
Should we use rollup to compile instead?
rollup ts: https://github.com/rollup/rollup-plugin-typescript
rollup config: https://github.com/rollup/rollup-starter-lib/blob/master/rollup.config.js

@drewjbartlett
Copy link
Collaborator Author

@yihou Thank you! Right now I have no working build tool for v2. Give a look at https://github.com/rapidjs/rapid.js/tree/v2-refactor and you can see what I (sort of) have in place. Ultimately I want to have a working typescript compiler. I think the first step is to take it in its current rendition and remove all the errors from the ts compiler and properly get that working. Then I have some other plans to rewrite and simplify the API! Thanks a ton for offering your help :D

@ctsstc
Copy link

ctsstc commented Apr 18, 2018

I noticed the branch for v2 is 10 commits behind master, hopefully there's nothing too breaking to try and get caught up with. As mentioned in my PR into the v2 branch I would recommend looking at removing manually written d.ts files and let those be generated in the TS compile via some settings in the ts config, you may have to transition those d.ts files over to their own ts files for interfaces, etc. I've seen mixed answers about interface file naming conventions; I think if you're in C# you prepend them with and i, but in TS you don't iirc.

@mgred
Copy link
Collaborator

mgred commented Apr 19, 2018

@ctsstc

I would recommend looking at removing manually written d.ts files and let those be generated in the TS compile via some settings in the ts config

I think this is the way to go. Basically {declaration: true} in the tsconfig.json should do the trick.

I think if you're in C# you prepend them with and i, but in TS you don't iirc.

Yes

@mgred
Copy link
Collaborator

mgred commented May 22, 2018

Changed the description to also have a point regarding the tests

@mgred
Copy link
Collaborator

mgred commented May 22, 2018

@drewjbartlett i just had a look at githubs project boards
Just a quick thought... do you think it would make sense to organise all the refactoring work there to have a better overview of the tasks and duties?

@drewjbartlett
Copy link
Collaborator Author

@mgred I am definitely not opposed to this. Let me evaluate shortly what I want to change and I will list it out and we can plan the attack :D

@mgred
Copy link
Collaborator

mgred commented May 22, 2018

Nice thanks, @drewjbartlett

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants