mathstodon.xyz is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Mastodon instance for maths people. We have LaTeX rendering in the web interface!

Server stats:

2.8K
active users

#SwaggerUI

0 posts0 participants0 posts today
happyborg<p>Good progress on the <a href="https://fosstodon.org/tags/dweb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>dweb</span></a> REST APIs and improvements to the <a href="https://fosstodon.org/tags/OpenAPI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenAPI</span></a> docs today, all with the help of <a href="https://fosstodon.org/tags/actix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>actix</span></a> and <a href="https://fosstodon.org/tags/utoipa" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>utoipa</span></a> </p><p>BTW <a href="https://fosstodon.org/tags/SwaggerUI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SwaggerUI</span></a> is really cool </p><p>A few days ago I knew nothing about these but now I have a working API that is documented and can be tested live while reading those docs.</p><p>Someone asked if I might support <a href="https://fosstodon.org/tags/GraphQL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GraphQL</span></a> but I haven't looked into that. Convince me that I should!</p>
lachezar<p>I’ve updated a dependency producing <a href="https://mastodon.nu/tags/OpenAPI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenAPI</span></a> schema, which has also updated its OpenAPI spec version from 3.0 to 3.1 and <a href="https://mastodon.nu/tags/SwaggerUI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SwaggerUI</span></a> that has just recently announced support for 3.1. <br>Previous SwaggerUI rendering 3.1 spec does not show any of your tagged unions names - it just shows “object”.<br>So this was an unexpected event considering that it is a minor version change and SwaggerUI is probably the most famous viewer for a OpenAPI schema.</p><p><a href="https://swagger.io/blog/swagger-supports-openapi-3-1/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">swagger.io/blog/swagger-suppor</span><span class="invisible">ts-openapi-3-1/</span></a></p>
Marco Siccardi<p>Fellow <a href="https://mastodon.social/tags/dotNET" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>dotNET</span></a> developers, I have a repo that has already all <a href="https://mastodon.social/tags/DTO" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DTO</span></a> objects and a <a href="https://mastodon.social/tags/SwaggerUI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SwaggerUI</span></a> <a href="https://mastodon.social/tags/OpenAPI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenAPI</span></a> definition. Now I am about to write two clients—one will be an <a href="https://mastodon.social/tags/ASPNETCore" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ASPNETCore</span></a> website using that API, the other is a .NET <a href="https://mastodon.social/tags/MAUI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>MAUI</span></a> client. Which route would you go for a client SDK that connects the clients with the <a href="https://mastodon.social/tags/AzureFunctions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AzureFunctions</span></a> API?</p>
Marco Siccardi<p>Well, one of 6 endpoints have now <a href="https://mastodon.social/tags/OpenAPI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenAPI</span></a> <a href="https://mastodon.social/tags/docs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>docs</span></a>. I totally need to improve my <a href="https://mastodon.social/tags/documentation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>documentation</span></a> writing skills 😁 </p><p><a href="https://mastodon.social/tags/waytogo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>waytogo</span></a> <a href="https://mastodon.social/tags/devlife" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>devlife</span></a> <a href="https://mastodon.social/tags/Azure" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Azure</span></a> <a href="https://mastodon.social/tags/OpenWeb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenWeb</span></a> <a href="https://mastodon.social/tags/SwaggerUI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SwaggerUI</span></a> <a href="https://mastodon.social/tags/CASBAN6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CASBAN6</span></a></p>
jk<p>über die dip api des bundestages sind nun auch kürzlich geänderte einträge abrufbar. siehe kapitel 2.6: <a href="https://draftable.com/compare/zKXNmlxOnQcb" rel="nofollow noopener noreferrer" target="_blank"><span class="invisible">https://</span><span class="ellipsis">draftable.com/compare/zKXNmlxO</span><span class="invisible">nQcb</span></a></p><p>zudem sind ist die dokumentation neben der pdf-version auch in weiteren versionen verfügbar: </p><p>swagger-ui <br><a href="https://search.dip.bundestag.de/api/v1/swagger-ui/" rel="nofollow noopener noreferrer" target="_blank"><span class="invisible">https://</span><span class="ellipsis">search.dip.bundestag.de/api/v1</span><span class="invisible">/swagger-ui/</span></a></p><p>openapi yaml<br><a href="https://search.dip.bundestag.de/api/v1/openapi.yaml" rel="nofollow noopener noreferrer" target="_blank"><span class="invisible">https://</span><span class="ellipsis">search.dip.bundestag.de/api/v1</span><span class="invisible">/openapi.yaml</span></a></p><p><a href="https://chaos.social/tags/openbundestag" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>openbundestag</span></a> <a href="https://chaos.social/tags/opendata" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>opendata</span></a> <a href="https://chaos.social/tags/openparliaments" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>openparliaments</span></a> <a href="https://chaos.social/tags/openapi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>openapi</span></a> <a href="https://chaos.social/tags/swaggerui" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>swaggerui</span></a></p>
clacke: exhausted pixie dream boy 🇸🇪🇭🇰💙💛Is anyone aware of a UI constructor for OpenAPI-defined APIs that goes beyond Swagger UI?<br><br>Swagger UI is a great leap over just having API documentation and making your own HTTP requests, it literally generates a UI, if a barebones one, that not only knows the endpoints but even knows and helps you conform to the datatypes.<br><br>It would be awesome to have some low-code tool with very high whipuptitude that would allow you to create a working prototype of a more visual UI by just dragging some stuff around.<br><br><a href="https://libranet.de/search?tag=OpenAPI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenAPI</span></a> <a href="https://libranet.de/search?tag=swagger" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>swagger</span></a> <a href="https://libranet.de/search?tag=SwaggerUI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SwaggerUI</span></a>