Feature request

Recently, GitHub added nice blocks for emphasizing important information. WDYT about start using them?

https://github.com/orgs/community/discussions/16925

The documentation section Error-handling guidelines contains the sentences

Trying to reproduce this behaviour with Example project brings unexpected results. The way I had tried:

1. Setup database
2. Start the example server
3. Open http://127.0.0.1:8000 in the Chrome
4. Open DevTools with network and console tabs
5. Click on api WebSocket request and there on Messages tab. Check that auth/signin request was successful with the status logged.
6. Write in console await api.example.customException();
7. The result {message: "Custom ecxeption", code: 12345} despite documentation says that unknown error code will generate: "Internal Server Error" with "code":500.
8. Change error code in the file application/api/example/customException.js to 404. Save and check that update has been reloaded by server.
9. Call again in console await api.example.customException();
10. The result {message: "Custom ecxeption", code: 404} instead of automatic replacement of the message with "Not found" as being told at the documentation.
11. The same behaviour with public endpoint.

What is the desired latest behaviour: that mentioned in documentation OR that actually works in Example?

Scenario:

• Application serves WebSocket protocol
• Clients subscribe to the WebSockets room/channel via sending message to API using metacom message schema. The incoming request is handling by worker W1. The logic was taken from this example
• At some moment, domain logic initiates application.scheduler.add() that should invoke some task in 1 minute.
• The scheduler task execution is launching on worker W2 (default application behaviour). The task should broadcast WebSocket message to all subscribed clients connected to the application.
• Because the Room Map object is initiated in W1 worker (application logic by default), the W2 worker doesn't contain the Room Map object, and this is logical.
• How we can implement that internal communication between application workers? So we can broadcast some messages/events from all application workers to some master worker, and then broadcast messages to all connected WebSocket clients?

Thank you!

I propose pinning this repository, similar to the Contract repository.

https://github.com/metarhia/Docs/blob/main/ru/INTRO.md

metasql - утилиты для работы с pg, генератор структуры базы, миграций, простой построитель запросов, валида;

наверно имелся ввиду "валидатор" или "валидации" или что-то в этом роде