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

create nuget package for Visual Studio #21

Open
penCsharpener opened this issue Dec 27, 2017 · 8 comments
Open

create nuget package for Visual Studio #21

penCsharpener opened this issue Dec 27, 2017 · 8 comments

Comments

@penCsharpener
Copy link
Collaborator

probably not yet but once all endpoints are in place

@priyank-p
Copy link
Member

@zulipbot claim

@Janek91
Copy link

Janek91 commented Apr 2, 2020

Any plans regarding that? Code hasn't been touched for a long time. If you need help with that I'm willing to.

@penCsharpener
Copy link
Collaborator Author

sure, help is always welcome. I used to use Zulip at my last employer. Since I've changed I didn't have much time or use for it anymore. I haven't abondoned it but I also never had much feedback. I'm happy to pick it up again.
What are you ideas? What would you like to see implemented?

@Janek91
Copy link

Janek91 commented Apr 2, 2020

Basically - cover all missing endpoints and publish it as a NuGet package targeting .NET Standard 2.0, so that anyone can use it. Also we could split it into two parts - one for just building correct URLs and the other one - wrapping them in methods and calling via some REST library - like Flurl.Http (which is much better than RestSharp by the way). That would made it available for people which want to use REST library of their choice or its own implementation. Besides that unit tests should correlate with current Zulip API just like the Postman collection. In the and sample application could be upgraded do WPF one - which is much modern approach than the current WinForms one.

@penCsharpener
Copy link
Collaborator Author

sounds great. back then I only really worked with Winforms and even the API was new. RestSharp was a great help. With my newer NetDeepL project I used neither. .NET's HttpClient has come a long way.
As a test frontend for the sameple app I'd even go for Blazor as it would run also on unix systems.

@Janek91
Copy link

Janek91 commented Apr 2, 2020

Great I've forked the project and will create PRs as soon as something will be ready.
Blazor sounds fun - especially when server-side version will be production ready, but having desktop app too will make debugging, and testing easier. Anyway - it would be good to have that too.

@penCsharpener
Copy link
Collaborator Author

Service-side blazor is production ready since October 2019. WASM will be in May 2020 if they can keep their timeline. Knock yourself out ;-) I'm looking forward to your PRs! Thanks again.

@Janek91
Copy link

Janek91 commented Apr 2, 2020

Yes, I've meant WASM.

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

4 participants