visual-editor VS Nest

A few words about Visual Editor. This editor is built around the powerful Quilljs Delta document format originally developed by QuillJs. Delta documents can be easily converted to JSON, the encoding is easy to read and modify and offers many extensibility options.

There's a fork of flutter_quill called visual-editor. It switches to the next widget in the focus sequence, which is one way to properly handle the key.

Flutter also isn't great for text editors, but there are a few implementations like visual-editor for formatted text that's acceptable. Also, the xterm package is pretty amazing from its capabilities (even runs full vim!).

There's visual-editor, but that one has a different focus than a programming editor.

Two months ago I decided to fork the Quill rich text editor because the architecture is extremely difficult to follow. Since I desperately need for my own project, a strong rich text editor that can be easily extended with more features I took the decision to byte the bullet and refactor Quill from the ground up. There are numerous extremely good features in Quill yet the overall architecture was a total train wreck. In this article I'll be explaining in detail what were the issues and how I attempted to improve them. You can find the source code at Visual Editor Github. I've documented the entire process and I'll be releasing deep dive Flutter architecture episodes at Visual Coding YouTube. Enough shameless plugs, let's get going.

You are right, we have programmed the app with Flutter and are very happy with the framework. Two years ago, when we started, many libraries were still missing in the community, especially the text editors were problematic. That's why I contributed a lot to the community to improve the status. At the moment I am very excited about the libraries SuperEditor and VisualEditor. Otherwise, the tooling with Flutter is excellent and it's a lot of fun to program with it. We programmed the server with NestJS, use a PostgreSQL database and GraphQL as the query language.

Visual Editor Gihub Repo - Freshly forked, already many changes, to be published in pub dev.

When using the NestJS framework, sometimes you may need to change some default timeout. You can define them just like you'd do in a plain Node.js HTTP server like so:

Back: a graphQL server built with Nestjs

NestJS - opinionated more scalable, but harder to learn docs

Pragmatically, we can apply this to a Nest application by creating an Interface for our services, separating the Presenter layer (Controller) from the Use Case (Services):

It’s a text document that contains all the commands a user could call to assemble an image. Let’s check an example of a Dockerfile for a nodejs app in this case it will be a NestJS app and then explain each part.

describe('Create bookmarks', () => { const dto: CreateBookmarkDto = { title: 'NestJS', link: 'https://nestjs.com/', }; it('should create bookmark', () => { return pactum .spec() .post('/bookmarks') .withHeaders({ Authorization: 'Bearer $S{userAt}', }) .withBody(dto) .expectStatus(201) .stores('bookmarkId', 'id')//store the bookmark id in the variable bookmarkId .expectBodyContains(dto.title) .expectBodyContains(dto.link) }); });

In my usual NodeJS tech stack, which includes GraphQL, NestJS, SQL (predominantly PostgreSQL with MikroORM), I encountered these limitations. To overcome them, I've developed a new stack utilizing Rust, which still offers some ease of development:

The purpose of this article is to provide a step-by-step guide for implementing authentication system in a NestJS project using the Passport middleware module.

That's exactly where I am. My manager gave me these links, that cover a lot of those words the backend uses, so I can identify what they mean and how to use them. 1. For inspiration and concepts: https://github.com/Sairyss/domain-driven-hexagon 2. Suggested to read the documentation for nest.js. They apply such concepts I don't understand: https://nestjs.com/