-
Notifications
You must be signed in to change notification settings - Fork 393
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
release: 0.8.x #315
release: 0.8.x #315
Conversation
Params fixes and features
Before merge we should update it with latest class-validator and class-transformer releases |
any news on releasing this version? |
@NoNameProvided |
another +1 for releasing this ASAP. Not having class-validator due to the version issues is ruining everything. @NoNameProvided please release to NPM |
Looking to get this version too please :) |
Just a bump on this, is there anything we can do to help get it released? |
Is this package still maintained? |
It would be great to release this version, I am still expecting this :) |
🎉 |
Just out of curiosity when is it going to be pushed to NPM? Thanks :) |
Hopefully soon. I've already requested @NoNameProvided here and also @pleerock through email. Regarding fixes for class-transformer and class-validator, yes it does - check the release notes here |
@jotamorais thanks for your work on this project. Just a question: how much attention you want to give this project? I'm considering to use it for commercial product. Is it safe? |
I'm supporting it because I also use it commercially (the company I work for). So, I can assure it's a strong reason to stick around. |
@jotamorais I hope I can help you to maintain this project. At least with PR. Let's give it a try |
Version 0.8.0 is now published in NPM. Thank you all for your contributions. |
Great job 👍 |
@MichalLytek why deleted? |
@rustamwin Because it's merged :) |
@MichalLytek I mean, the next branch should keep as pre-release branch. |
Thank you very much for this release. Really nice to see this project moving again 🎉 |
I'm starting to document a "contribution guide" and in there we will have more details of the branching and releasing model moving. For now, we first need to do a proper triage of open issues and open PRs and from there prioritize to allow clear visibility and communication of the project's current state. |
So exciting :) Hopefully the other projects will be picked up too
…On Fri, Oct 4, 2019 at 5:22 AM Jonathas Morais ***@***.***> wrote:
@MichalLytek <https://github.com/MichalLytek> I mean, the next branch
should keep as pre-release branch.
I'm starting to document a "contribution guide" and in there we will have
more details of the branching and releasing model moving. For now, we first
need to do a proper triage of open issues and open PRs and from there
prioritize to allow clear visibility and communication of the project's
current state.
I'm planning to use the project board
<https://github.com/typestack/routing-controllers/projects/3> for that.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#315?email_source=notifications&email_token=AABUPVXC3A3JJOC425WPR3TQMYL45A5CNFSM4EAGBDVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAIYFNQ#issuecomment-538018486>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABUPVWOHKTLJNM6HIAXTQLQMYL45ANCNFSM4EAGBDVA>
.
|
This PR combines #289 with reverted
@PathParams
decorator name change and changed error name toInvalidParamError
.Additionally, it extract generic
@Session()
decorator into@SessionParam()
and@Session()
decorators to provide better consistency in param injection decorators naming.