nocode
Swashbuckle.AspNetCore
nocode | Swashbuckle.AspNetCore | |
---|---|---|
108 | 16 | |
59,407 | 5,103 | |
- | - | |
0.0 | 8.9 | |
23 days ago | 5 days ago | |
Dockerfile | C# | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nocode
-
I'm Excited about Darklang
> "no cruft: no build systems, no null, no exception handling, no ORMs, no OOP, no inheritence hierarchies, no async/await, no compilation, no dev environments, no dependency hell, no packaging, no git, no github, no devops: no yaml, no config files, no docker, no containers, no kubernetes, no ci/cd pipelines, no terraform, no orchestrating, no infrastructure: no sql, no nosql, no connection poolers, no sharding, no indexes, no servers, no serverless, no networking, no load balancers, no 200 cloud services, no kafka, no memcached, no unix, no OSes"
I'll be honest, I did the same and at first thought Darklang was a troll project along the lines of https://github.com/kelseyhightower/nocode.
Either this is one hell of a project that is taking on all problems (and will consequently fail), or this pitch is misguided. The majority of what is listed there have nothing to do with languages.
-
Thinking Inside The Box: Relational Style Joins in SurrealDB
I hope this clears some of the fears of missing out (FOMO) that you might have about SurrealDB not having traditional SQL joins. You can still do the things you need to do such as with the subqueries. When it comes to the traditional joins though, we think about it more in terms of the joy of missing out (JOMO) because the best way to reduce errors in your code is by writing less code, as seen in our record links example.
-
Vanilla Design: The Best React UI Library Ever
Vanilla Design is a super lightweight, ultra high-performance React UI library. Vanilla Design Team places a great emphasis on code size and performance, drawing inspiration from the nocode philosophy, which has significantly boosted the security and maintainability of Vanilla Design. It's like they've added an extra layer of bulletproofing and polish to their creation!
- efficiencyHack
-
Ask HN: How Airtable / Notion's Database is implemented?
There are some open source competitors to Airtable and Notion that can provide good insight. Check out https://github.com/kelseyhightower/nocode
-
Does Debian always have this many "release critical" bugs at release?
Well 100 is a number. And here is the relation: https://sources.debian.org/stats/ and here is how to get 0 bugs: https://github.com/kelseyhightower/nocode
-
Looking for partner to start hosting service
This is my background and i years of experience hosting this..
-
Sunt masterele online worth it?
Asta kelseyhightower/nocode: The best way to write secure and reliable applications. Write nothing; deploy nowhere. (github.com) are mii de forkuri si zeci de mii de stelute, activitate masiva la 'issues' - mii, sute de 'pull requests', clar ca rezolva o problema reala, nu?
-
My manager wants me to code a bug free application
Well, you can write a bug-free application..
-
Show HN: Gut – An easy-to-use CLI for Git
First off, congratulations on entering the Computer Science!
Second, I am not sure what is a bigger joke here, the project itself and the OP's innocuous and cute self-promotion or the fact that this post landed the HN's front page.
0. Terms and definitions.
"You" refers not to the author of the tool but to the dear reader who happens to stumble upon this comment in the stream of random screen scrolling.
1. Comment body.
Couple of things about CS classes and specifically about programming classes. They will teach you everything but the most important engineering principles. And you'll have to adjust your learnings once you leave the campus gate behind and enter the wilderness of real tasks and challenges.
The first biggest lesson I learnt as a CS graduate was that the most beautiful, efficient and valuable software program is the one that does not exist, literally no code[0]
The second biggest lesson I learnt as a CS graduate was YAGNI[0]. You never ever write a single line of code, even touch the keyboard until you are absolutely sure you have exhausted all possible options to solve your problem without getting your hands dirty with programming.
The third biggest lesson I learnt as a CS graduate was RTFM[2]. It is so exciting to go to conferences and see people present fancy slides and watch youtube videos with lollipop coloured pictures explaining some complex topics in a eli5 style. Or read blog posts on a gazillion of websites posted by unknown unknowns but yet coming so convincing as if they were written by John Carmack or ChatGPT 5. But then none of them tell you the whole truth and show you the full picture. It is only official documentation, manuals and boring reference specifications that can help you find what you are looking for. And you will need to learn the skill of grinding hunderds of pages of badly styled refdocs to find that really nitty gritty quirky feature that consumed your whole day in finding out why your code does not work as expected. That's where you will start proceeding to the official docs and source code (if needed) before anything else (even Stackoverflow!).
There have been so many git wrappers around, you can probably try them all (tig, jj, gh-cli, gitui, lazygit, gix, you google it). But then, no matter how much effort their authors invest in those tools, there will always be inconsistency between git and its wrapper and you find yourself resorting to git to do what was supposed to be covered by the bespoke tool. And then you learn to respect git, understand its concepts as they were designed, learn some bash and git aliases[3], ditch all those tools (or the majority of them) and proceed with your personal tailored toolbox where if you find something odd you adjust it for your needs within 10 minutes and chill out.
[0] - https://github.com/kelseyhightower/nocode
[1] - https://en.wikipedia.org/wiki/You_aren%27t_gonna_need_it
[2] - https://en.wikipedia.org/wiki/RTFM
[3] - https://git-scm.com/book/en/v2/Git-Basics-Git-Aliases
Swashbuckle.AspNetCore
- TypeSpec: A New Language for API-Centric Development
-
Advantages and disadvantages of FastEndpoints
It isn't where it needs to be. Notably, it cannot out-of-the-box handle open generic data types. There's also plenty of issues logged for this library. - Personally, that makes me think the approach is overly complicated and doesn't do its job as well as it should.
-
Web API Swagger to File Error Net 6
I have been checking all the sites about web api swagger to file but it seems theres some issue exporting swagger file on net 6.. any one can help us on this issue? https://github.com/domaindrivendev/Swashbuckle.AspNetCore/issues/2585
-
App Service Memory jump. This app service barely gets used. It's running on a B3 plan with some other small app services that also have a graph like this but at different times. These are all .Net, C#, and running on Linux. Any ideas on what might do this or how I'd track it down?
Also, there are multiple open bugs regarding memory utilization issues with Swagger, such as this one.
-
Update Swashbuckle.AspNetCore Version from version"4.0.1" to "6.2.3"
Hi there. I had an interesting task: to update the Swashbuckle.AspNetCore version from "4.0.1" to "6.2.3". It looked very simple but it was not what it looked like. The main problem was breaking changes which happened when passing from version 4 to version 5. Swashbuckle.AspNetCore began to use Swagger/OpenAPI version v3 instead of OpenAPI v2. The project makes use of NSwag to generate httpClient for getting data from another microservice. Any attempt to regenerate auto generated code changed it after updating Swashbuckle.AspNetCore version. These caused a lot of build errors. I should have decreased differencies between the new code and old one. Main difference which cause incompatibility in the project were:
-
Authenticate Next.js SPA with ASP.NET 6 Identity and Duende Identity Server Part 1
Swashbuckle Github repo
-
OpenAPI extensions and Swashbuckle
Swashbuckle.AspNetCore
-
dotnet swagger tofile : FileNotFoundException dotnet-swagger.xml
Trying to generate swagger from the compiled dll using this command with the swagger CLI:
-
A Developer's Guide to CQRS Using .NET Core and MediatR
Swashbuckle Swagger
-
Organize code by concepts, not layers
That’s exactly what I meant. There’s about 0 maintenance required most of the time. Take a look at their official nuget GitHub page. This should work out of the box with ASP.NET core 3.0 and greater. For 5.0 onwards, the MVC template comes pre-configured with it.
What are some alternatives?
Motor Admin - Deploy a no-code admin panel for your application in less than a minute. Stop wasting time on custom internal tools and focus on the actual product. Motor Admin allows to launch a custom admin panel for any application.
swagger-core - Examples and server integrations for generating the Swagger API Specification, which enables easy access to your REST API
api-guidelines - Microsoft REST API Guidelines
ArnoldC - Arnold Schwarzenegger based programming language
SPA-Identity-Server-Authenticate-Sample - SPA Identity Server Authenticate Sample
fpcupdeluxe - A GUI based installer for FPC and Lazarus
swagger-petstore - swagger-codegen contains a template-driven engine to generate documentation, API clients and server stubs in different languages by parsing your OpenAPI / Swagger definition.
fetlang - Fetish-themed programming language
opentelemetry-specification - Specifications for OpenTelemetry
lowdefy - The config web stack for business apps - build internal tools, client portals, web apps, admin panels, dashboards, web sites, and CRUD apps with YAML or JSON.
cqrs-with-net-core-mediatr