DUONG Phu-Hiep duongphuhiep

1. try/catch the right way

a) Don’t `try/catch` whenever you feel like it

[!info] 👍 Rule of thumb: Avoid try/catch as much as possible

try/catch is BAD. It hurts the application performance. Hence, all try/catch must to be justified.

You should put a comment to justify why would you have to try/catch here?

For example a BAD Code:

REST vs OpenAPI - Why REST is bad and We should return HTTP 200 in case error

Do you know that OpenAPI (formerly "Swagger") and REST are two different things?

A "pure" REST API should be self-descriptive (i.e., it doesn't require any documentation) by implementing the HATEOAS (Hypermedia as the Engine of Application State) principle. Clients interact with the API entirely through URLs provided by the server, without needing to know the structure of URLs in advance. This is similar to how browsers follow links.
Most REST APIs today are not "pure". Clients still need documentation to use the API's endpoints effectively.

OpenAPI helps describe (or document) "impure REST APIs." But please don't confuse the two! OpenAPI doesn't enforce as many conventions as REST. For example:

| REST (or impure REST)

How to Review PRs (or MRs) of unfamiliar C# codes base?

If you have to review a Pull Request (or Merge Request) in an unfamiliar C# codebase, what should you check? Here is my checklist for reviewing a C# codebase without fully knowing what it does:

Since we don’t know much about what the code is doing, the review should focus on best practices:

Are there tests that cover all the changes? If not, is there a justified reason why the changes are not unit-testable? (Yes, that can happen.)
Challenge any unjustified try/catch blocks.
Challenge the use of Generics or Reflection (often a sign of over-engineering).
Challenge the use of Inheritance (may indicate poor design or over-engineering).

Logging best practices

When generate a log message

Major branching points in your code
When errors or unexpected values are encountered
Any IO operations: calling database / stored proc or make http request
Significant domain events
Request failures and retries
Beginning and end of time-consuming operations

Problem

Your HTML page (the host page) has an Iframe. The Iframe source is on other domain, so you will have to use the window.postMessage() for cross-origin communication. But this communication is only in 1 direction (The Iframe can inform the Host or the Host can inform the Iframe)

This article shows you how to make the Request/Reply communication using postMessage() and MessageChannel combination.

The article did not show you how to add a timeout to the communication, so the Iframe might wait forever if the Host did not response.

I will resume the technique by some codes snippets and at the same time add the missing timeout implementation.

Technical Errors vs Business Errors

API's designer often categorize errors into "Technical" and "Functional" (or "Business") errors. However, this distinction may not make sense:

An API/micro-service should always return ONLY "Functional" (or "Business") errors.
The API/micro-service migh be crashed while processing a consumer's request and so the consumer will naturally get a technical error. But the API/micro-service should not deliberately return a "Technical" error for consumer. The simple fact that the App built a nice response called "Technical error", then gracefully return it, make it no longer a technical error, but a "fake" one.

We will explore the distinction between "real technical errors" and "fake technical errors". "Fake technical errors" are initially technical but later manifest as business errors, thus becoming "fake technical errors."

HTTP 404 Business error (or Fake technical error)

	/* Default value */
	:root {
	color-scheme: light;
	--rz-alert-message-margin: 0.125rem 0;
	--rz-alert-icon-margin: 0.125rem 0;
	--rz-base: #eeeeee;
	--rz-base-50: #fafafa;
	--rz-base-100: #f5f5f5;
	--rz-base-200: #eeeeee;
	--rz-base-300: #e0e0e0;

	using System.Security.Cryptography;
	using System.Text;

	namespace Lemonway.TransactionService.Application
	{
	public static class AesEncryptionHelper
	{
	public static string Encrypt(string payload, string secret)
	{
	byte[] iv = new byte[16];

	// Place your key bindings in this file to override the defaultsauto[]
	[
	{
	"key": "ctrl+t",
	"command": "workbench.action.togglePanel"
	},
	{
	"key": "ctrl+shift+f4",
	"command": "workbench.action.closeOtherEditors"
	},