Dephney

Aspiring full stack developer, C# enthusiast, Wannabe javascript baddie

[Dephney @dephneyCodes_]

@khabubu_phathu No you didn't 🤣🤣🤣👀

[Dephney @dephneyCodes_]

@mogau_im I eat my food and some of his...a girl has two stomachs... "I'm full" is trying too hard 😏

[Dephney @dephneyCodes_]

@mogau_im Building (ehm, learning) WASM app. Thinking of rewriting the frontend of some app at work using WASM, my last ambitious idea of the year

[Dephney @dephneyCodes_]

@czioutas @mirzaleka huh...interesting 🤔

[Dephney @dephneyCodes_]

@GirlCode_za Morning, What's on the agenda for this workshop?

[Dephney @dephneyCodes_]

@Cl4s1k @npm_run_serve Ohk.. Got it.. Thanks

[Dephney @dephneyCodes_]

@Cl4s1k @npm_run_serve Contracts? What's in there

[Dephney @dephneyCodes_]

@TreciaKS Yesssssss...I'm very interested, a good read already 😊

[Dephney @dephneyCodes_]

@Madisonkanna You should've said "yes..tomorrow is my last day"

[Dephney @dephneyCodes_]

@mwaseemzakir 8

[Dephney @dephneyCodes_]

@The_GreatBonnie We'll never know😅... Congratulations!

[Mukesh Murugan @iammukeshm]

Follow this guide to level up your .NET Career! A well-structured roadmap on what you need to know to become a Star .NET Developer in 2024 and beyond!

To read more practical articles, subscribe to my newsletter, where I have started a .NET 8 Zero to Hero Series: https://t.co/BZNvyzpTgd

#dotnet #developer #roadmap #dev #microsoft

[Dephney @dephneyCodes_]

@iammukeshm A golden thread..can't believe I read if for free. Thanks you so much for sharing🙏

[Milan Jovanović @mjovanovictech]

How do you design a good API?

Here are 5 tips for designing a quality API.

API design is deciding how your API will expose data and functionality to consumers. A good API design describes the API endpoints and resources in some standard format.

There are 4 key stages of API design:

1 - Determine what the API should do
2 - Define the API contracts (OpenAPI)
3 - Validate your assumptions with tests
4 - Document the API (endpoints, error codes, etc.)

Here are 5 more tips for designing a good API.

1) 𝗣𝗿𝗶𝗼𝗿𝗶𝘁𝗶𝘇𝗲 𝗖𝗼𝗻𝘀𝗶𝘀𝘁𝗲𝗻𝗰𝘆 𝗮𝗻𝗱 𝗦𝗶𝗺𝗽𝗹𝗶𝗰𝗶𝘁𝘆

Your API should have consistent naming conventions, response formats, and an error-handling strategy. Simplicity in API design makes it easier for developers to understand and integrate with your API.

2) 𝗘𝗺𝗯𝗿𝗮𝗰𝗲 𝗥𝗘𝗦𝗧𝗳𝘂𝗹 𝗣𝗿𝗶𝗻𝗰𝗶𝗽𝗹𝗲𝘀

You should design your API according to RESTful principles, emphasizing statelessness, a client-server architecture, and a uniform interface. REST APIs are the standard in most .NET applications.

3) 𝗨𝘀𝗲 𝘁𝗵𝗲 𝗰𝗼𝗿𝗿𝗲𝗰𝘁 𝗛𝗧𝗧𝗣 𝗦𝘁𝗮𝘁𝘂𝘀 𝗖𝗼𝗱𝗲𝘀

You should use the correct HTTP status codes to communicate the outcome of API requests. This includes successful operations (2xx), client errors (4xx), and server errors (5xx). It helps consumers of your API understand what went wrong and how to rectify it.

4) 𝗜𝗺𝗽𝗹𝗲𝗺𝗲𝗻𝘁 𝗔𝗣𝗜 𝗩𝗲𝗿𝘀𝗶𝗼𝗻𝗶𝗻𝗴

Plan for future changes by implementing versioning in your API. This allows you to make improvements and changes without breaking existing client integrations. The most common approach is URL versioning.

5) 𝗔𝘂𝘁𝗵𝗡 𝗮𝗻𝗱 𝗔𝘂𝘁𝗵𝗭

Implement authentication, authorization, and data encryption where necessary. Protecting sensitive data and ensuring that only authorized users can access specific API endpoints is crucial for maintaining the trust and integrity of your API.

If you liked this, consider joining 48,000+ engineers in The .NET Weekly.

✅ One practical tip every Saturday
✅ .NET best practices and actionable advice
✅ Software Architecture deep dives and fresh ideas

Subscribe here → https://t.co/IAdIqoDe37

What is something you do to design a good API?

[Dephney @dephneyCodes_]

@mwaseemzakir This was so helpful I gave my phone a hug🤗... Thank you so much

[ASP.NET Core News @aspnetcore_news]

EP 54 : Publish an ASP .NET Core app to IIS by @mwaseemzakir https://t.co/NM0vfRaSEx #aspnetcore

[Milan Jovanović @mjovanovictech]

The easiest way to send HTTP requests in .NET is using an HttpClient.

But there's an even simpler alternative.

The problem with HttpClient?

If used incorrectly, you could run into port exhaustion and DNS issues.

You also need to take care of serialization and deserialization manually.

Thankfully, there's an excellent library that solves this.

It's called Refit.

It's an automatic, type-safe REST API client for .NET.

In this video, I'll show you how to use Refit to easily integrate with an HTTP API.

Watch it here: https://t.co/vhWMGESVPU

[Dr Milan Milanović @milan_milanovic]

𝗪𝗵𝗮𝘁 𝗶𝘀 𝗖𝗿𝗼𝘀𝘀-𝗢𝗿𝗶𝗴𝗶𝗻 𝗥𝗲𝘀𝗼𝘂𝗿𝗰𝗲 𝗦𝗵𝗮𝗿𝗶𝗻𝗴 (𝗖𝗢𝗥𝗦)?

Browsers use CORS to prevent websites from requesting data from different URLs. A browser request includes an origin header in the request message. The browser allows the request if it gets to the server of the exact origin; if not, it blocks it.

We can deal with CORS issues on the backend. Cross-origin requests require that the values for origin and 𝗔𝗰𝗰𝗲𝘀𝘀-𝗖𝗼𝗻𝘁𝗿𝗼𝗹-𝗔𝗹𝗹𝗼𝘄-𝗢𝗿𝗶𝗴𝗶𝗻 in the response headers match and the server sets it. When you add an origin to the backend code, the CORS middleware only permits this URL to communicate with other origins and be utilized for cross-origin resource requests.

There are two ways to fix CORS issues:

𝟭. 𝗖𝗼𝗻𝗳𝗶𝗴𝘂𝗿𝗲 𝘁𝗵𝗲 𝗕𝗮𝗰𝗸𝗲𝗻𝗱 𝘁�� 𝗔𝗹𝗹𝗼𝘄 𝗖𝗢𝗥𝗦

The server can let all domains with 𝗔𝗰𝗰𝗲𝘀𝘀-𝗖𝗼𝗻𝘁𝗿𝗼𝗹-𝗔𝗹𝗹𝗼𝘄-𝗢𝗿𝗶𝗴𝗶𝗻: *. This turns off the same-origin policy, which is not recommended. Another option would be only to allow a particular domain, which is a better option, e.g., 𝗔𝗰𝗰𝗲𝘀𝘀-𝗖𝗼𝗻𝘁𝗿𝗼𝗹-𝗔𝗹𝗹𝗼𝘄-𝗢𝗿𝗶𝗴𝗶𝗻: 𝗵𝘁𝘁𝗽𝘀://𝘀𝗼𝗺𝗲𝗱𝗼𝗺𝗮𝗶𝗻.𝗰𝗼𝗺.

𝟮. 𝗨𝘀𝗲 𝗮 𝗣𝗿𝗼𝘅𝘆 𝗦𝗲𝗿𝘃𝗲𝗿

We can use a proxy server to call external API. It acts as a middleware between the client and the server. If the server doesn't return proper headers defined by CORS, we can add them to the proxy.

Image credits: Rapid API.

#api

[Dephney @dephneyCodes_]

@virender7k @CodeToCreation Hey.. Really interested.. Squeeze me in

[Dephney @dephneyCodes_]

@_sdvh I would marinate in the compliments