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

[EPIC] Release v6 #619

Closed
10 of 18 tasks
Romakita opened this issue Aug 20, 2019 · 8 comments
Closed
10 of 18 tasks

[EPIC] Release v6 #619

Romakita opened this issue Aug 20, 2019 · 8 comments

Comments

@Romakita
Copy link
Collaborator

Romakita commented Aug 20, 2019

Information

  • Version: 6.x
  • Type: EPIC

Stories

Optional stories for v6

@Romakita Romakita added this to the BACKLOG milestone Aug 20, 2019
@Romakita Romakita pinned this issue Aug 20, 2019
@chiqui3d
Copy link

chiqui3d commented Aug 22, 2019

Hello @Romakita
if you will deprecate @ServerSettings then as we will configure all parameters like mount and viewsDir

Thanks

@Romakita
Copy link
Collaborator Author

Hello @chiqui3d
ServerSettings will be replaced by an equivalent decorator with the same options and mechanism.

I want to introduce a new decorator which can be use over any class to store a part of the configuration like @configuration decorator. DI will resolve configuration when app is built by PlatformFactory.

Currently all stories aren’t described. I’ll doing that this week and see your feedback ;)

See you

@dlinx
Copy link

dlinx commented Sep 19, 2019

@Romakita
Will there be any support for 5.x after 6.x release?

@Romakita
Copy link
Collaborator Author

Romakita commented May 23, 2020

@dlinx
I'll produce a migration page to help developer. A large part of the existing code in v5 will be available on v6. Some v6 features are already available in v5.

The breaking change will be about existing deprecated features in v5:

  • Remove Filters features. Pipe is already out and must be used instead of.
  • Converter the signature of the ArrayConverter, etc... will be simplified. Most projects do not use this feature to change the json mapping behavior.
  • To use express a new package will be release: @tsed/plaftorm-express. Is the same thing for koa with @tsed/platform-koa. The server declaration will change but isn't a big change. Migration documention will explain the differences :)

v6 depreciation:

  • ConverterService will be deprecated in favor of the @tsed/json-mapper package.
  • Some JsonSchema decorators in v5 will be deprecated in favor of @tsed/schema package.

@Romakita
Copy link
Collaborator Author

https://v6.tsed.io (alpha)

@Romakita
Copy link
Collaborator Author

Koa integration is almost done. Some internal small changes are necessary to use Koa with the existing code but globally it works. I planed also to support Express v5 by releasing @tsed/platform-express5, just for fun. Then I want to develop a package to support fastisfy. I still have questions for HAPI. Maybe one of you will do it before me :)

@Romakita
Copy link
Collaborator Author

Alpha support koa now. The beta will be out soon.

This was referenced Oct 1, 2020
@Romakita Romakita modified the milestones: BACKLOG, V6 Oct 3, 2020
@Romakita
Copy link
Collaborator Author

V6 is released 🥳🥳

@Romakita Romakita unpinned this issue Oct 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants