I'm getting started with OpenAPI generator and would like to learn the best practices and see a list of companies that are actually using SDK generated by this tool (the reason is I feel like the tooling is a little bit behind for OpenAPI v3 so I'd like to see if anyone has a build an end-to-end pipeline).
So far I've found DataDog and their custom tooling and OneSignal's SDK.
Related
I have been working in the Django rest framework since three years on wards. Recently reading about FAST API frame work. FAST API looking like a very good framework for the current REST API service development. Seems like few things are missing from FAST API which are there in django.
Pagination
class based views.
mock testing
class based views.
struggled allot to provide the lookup for encrypted data in the django rest framework.
Could any one help me that how can we achieve above features with FAST API.
Currently in Jan 2020. FastAPI has a much smaller and different featureset to Django Rest Framework (DRF).
DRF is built on Django you have all the features Django available to you as well as convenient tools for building REST API's.
With FastAPI the framework way is more minimal it provides a simple, quick way to create and test a set of OpenAPI compatible endpoints. With a focus on speed and asynchronous style request-response handling.
However does not include ORM or migrations, admin, accounts etc and all the other 'batteries included' stuff you get with Django.
To achieve the functionality you have listed you'd right now you'd have to roll-your-own or use some pre-existing async python packages and adapt for your needs.
I have to create app as following.
1- App should work with Android and iOS.
2- Resolution should support to Mobile and Tabs
3- Data storage is on cloud. So, Restful API call will be there for
data transactions
4- There might be local storage for configuration settings
5- There might be native code for some functionalities like implement UrbanAirship Notification, Facebook etc
When I create project for Xamarin.Forms, I get 2 options to create application:
1- Shared, 2- .Net Standard.
I have tried with both. One point is that I haven't found library that contains name like .Shared or .Portable that I have found in one of my old project.
Here is comparision. Please suggest me which type of project I should create for my next project.
Thank you.
At the end it boils down to a matter of taste. The main difference is
shared projects are included in your platform projects as if the source code files were part of the projects themselves
.NET Standard projects are compiled to their own assembly
.NET Standard superseded the portable class libraries. The latter are deprecated and should not be used anymore. There would be no reason for anyway, since .NET Standard is way more convinient and supports a greater subset of .NET (effectively - depending on the PCL profile, but that one compatible with Xamarin was quite limited, e.g. there was very little support for the classes from System.IO).
There are pros and cons both for .NET Standard and shared projects. In shared projects you can use classes directly in your platform projects (anyway, this might be not advisable if you are trying to develop SOLID code), but you'll have to to use #ifdefs to use code that is compatible with only one of the platforms. With .NET Standard you may need to write classes containg platform dependent code twice and load them via DependencyService or - even better - a fully fledged IoC container, but therefor they are much cleaner and concerns are seperated much better.
In the times of PCL there were good reasons to go a hybrid way, e.g. to use System.IO.File from a class that was directly compiled in your platform projects, since both support it, but the PCL Xamarin Profile did not, but with .NET Standard this ain't necessary anymore.
I would always go for .NET Standard libs for the reasons mentioned.
.NET Standard is the future and all plugins and libraries will need to follow and supported it sooner or later.
As in the new prerelease of Xamarin forms 3.0:
We’re now building with .NET Standard 2.0, using the magic of
multi-targeting, while still supporting the PCL profiles and other
.NET Standard versions you may need. Notice how much faster your
projects load when you use .NET Standard project types!
Update To Xamarin.Forms 3.0 prerelease
.NET Standard will provide many features out of the box. Developers are now upgrading their solutions and plugins to support that standard.
.Net Standard. is a new PCL. Use it as if it were a PCL.
Has there ever been a more confusing/difficult time to be a web developer using the Microsoft stack? That's not really my question... I know that the answer is a categorical no. :)
The single page app template that comes with VS 2013 is deplorable.
I've been working on building up a similar project template that uses Angular JS on the client, but I'm starting to spin my wheels a bit porting over the external (openId/oauth) login features.
I believe this is because of the lack of good, single-point-of-truth, and current documentation for Katana's auth/security bits and also because of how unreadable the client side code is in the S.P.A. template in visual studio 2013.
I know that I can get through it, but while I'm struggling with it, I'm wondering:
Are there any good community provided project templates or example code bases in existence that use .NET 4.5 (MVC5/Web Api 2), Angular JS, the new ASP.NET Identity stuff, and the Katana packages?
There's HotTowel.Angular, but it takes no stance on security. Besides, it's a Nuget package, which can't or shouldn't dictate as much as a proper project template can.
I agree with your observations. I have found the following setup that seems to meet your requirements and I think works very well (I don't have a template), I would suggest the following:
Create an empty WebApi2 project and adopt authentication/authorization depicted here
Use a regular index.html in the base directory as a launching point for your angular application. You can either maintain your client packages with nuget, npm, or bower.
Use whatever technique you like for organization of client code.
Personally, I would create 3 projects, One for client code, (mydomain.com) One for your api (api.mydomain.com) and one for your Model/Repository/Data Access layer.
update
Here is an open-source project that might be what you're looking for!
I am evaluating Meteor as an alternative to developing real-time capabilities using socket.io and it looks like awesome framework for single page real-time apps. It is great time saver that enables developer focusing on the business logic of the app, rather than writing boilerplate code. However, I find it still pre-mature for a medium size app with multiple pages/routings and REST api. Plus, number of features like i18n are still not available which requires some time investment to develop by myself.
I think that it would be great if I could combine Meteor and Express and use Meteor in use cases where it really shines.
Is it possible to develop an app using standard Express/Mongo stack and use Meteor for only specific part of the app where I need real time collaboration?
For example, can I share a session between Express/Connect and Meteor?
Thanks!
This does not directly answer your question, but I thought I'd throw it out there:
You should check out the community packages on atmosphere. Specifically, I'd recommend having a look at iron-router and i18n (I'll note I have not used the latter).
I've built a large production app that uses iron-router and it's running smoothly. You may also be able to use its server-side-routing capabilities to implement your REST api.
Now before I dive too far into this this question, I am aware of nDjango and MonoRail; however, those project seem to be lacking.
What I'm wondering is if there is a solution out in the .Net world that has the following features out of a single box like Rails has in Ruby or Django has for Python. I know tools that do pieces but am curious if there's 1 unified solution out there.
Database Versioning/Migrations
ORM or similar code gen
MVC-based
Pre-generated administrative screens
View generation
Theming / styling
(I'm sure I'm forgetting another cornerstone feature)
There's lots of options that cover one or more of these aspects but is there something in .Net that covers all of them?
Thanks
I have not yet found a solution as you have described, but as you know there are bits and pieces that could be used together to provide a stack that is close:
Database Versioning/Migrations - DotNetMigrations
ORM or similar code gen - Nhibernate, Entity Framework
MVC-based - native to ASP.NET MVC
Pre-generated administrative screens - PLINQO
view generation - available in Entity Framework or CodeSmith templates, PLINQO
Theming / styling - native to ASP.NET
This would provide a stack that is .NET and not another ecosystem sitting on top of a .NET substrate.
You can actually run Rails under the .NET DLR. This allows you to not only access the feature set Rails provides, but also everything else which is available in the .NET ecosystem.
I haven't found a one click installer which gives me everything on your list, but, as you say, I have found excellent solutions for each point on your list which integrate well.
I'm honestly not sure how close this gets you, but S#arp Architecture seems to be trying to cover a lot of this ground in a single package.
There is a django for .net, the name is django!
In the web there is a lot of post about django running with ironpython (a implementation of python for the "virtual machine" of C#, CLR, i think)
there is also ndjango - the django templating language written in f# for .net. you can use it with bistro or asp.net mvc (or whatever else that you plug it into)