Відео

Hmm, I couldn't make that work for some reason. I do use Neovim with LazyVim and the VSCode extra, but the Neovim plugin didn't work for me. Might give it another try!

Interesting! It took a minor amount of tweaking (Two settings and doing an apt install instead of snap) for windows + WSL. It worked immediately on my pure Linux install the last time tried. I would think it would be the same for macOS. Either way there is a few binds you have in here that aren’t covered by that and I will definitely be stealing them!!

Which terms are you referring to? I’d love to help you with that.

@@nikolovlazar like controllers, repositories, entities, infrastructure, and other names used in the repo and video, I don't quite get the responsibility of all of them, and that makes it hard to understand the architecture.

@@labdo_ooh right! Check out this video. It covers all the terms and their responsibilities - Implement Clean Architecture in Next.js ua-cam.com/video/jJVAla0dWJo/v-deo.html

By the book it is a library dependency, but we can make a conscious exception about it due to the fact that it doesn’t depend on a specific runtime or depends on a framework. In this case the chances of refactoring and replacing Zod with something else are much smaller than some of the bigger dependencies. If you want to be super safe, you could refactor the schemas into classes and wrap the validation method with a class method.

vim.mode != SearchInProgressMode works if anyone needs. :)

Nice! Thanks for sharing this!

Thanks! Yeah the initialize method gets executed when the getInjection gets called. For serverless node environment you’d want to initialize the container every time because it’s serverless. If you’re on a long-running node server you can conditionally initialize based on the container value.

@@nikolovlazar good point regarding difference between hosting options.. keep up the great work

Glad you like the content! Yep, the free Sentry account supports all SDK features, except the Insights modules (business+) and Dashboards (team+), but you'll be able to get alerts, capture exceptions, measure performance and use traces for debugging without issues on the free plan.

Fala Toshka!

Honestly me too, that's why I'm staying with Neovim 😁 VSCode does have keybindings for debugging actions like "step over" and "add breakpoint". You can extend this configuration with those keybindings if you want to cover debugging as well.

@@nikolovlazar Thanks for the response. I would love to switch to Neovim. But I do flutter too and there is a whole new areas with emulators and AVDs. I haven't tried it yet so having doubt about that too.

yeah that could be tricky. everything is a command and can be triggered via the command line, but in some cases IDEs put that command behind a button (eg. Play button in Xcode).

Sup!

Thanks! It started with me realizing I have more inspiration when I'm outside taking walks with my wife than when I'm in the rgb room 😁 so I thought I'll seize the opportunity and record some videos outside.

Is the calculator logic plain javascript that can be used both on the frontend and backend? If it's something that you don't expect to change a lot, it's fine if there are two implementations of it (comments should note that as well). If not, see if you can isolate it in a shared function and how that would look like. You need to maintain testability, so try to follow the operation flow (contoller > use case(s) / service(s) > repository(ies)). You can have a use case that invokes the shared calculate function and use its output. That should be perfectly fine.

Thank you! I do want to cover caching as well, but I'm not sure when that would be. Definitely stick around!

Thanks! I had to take a shortcut there. It's not CA-approved 😁 We should put that away in its own service and call the service instead.

It's definitely an overkill if testing or modularity is not important in your project. But it's not dependent only on testing. If the project's complexity extends to more than just 1 database or has a number of different data sources, or even different teams working on one project, then CA is a good discipline to keep things in order.

@@nikolovlazar I mostly agree, but I'd argue it's architecture in general, not necessarily CA

@@nwsome definitely! I'm not singling out CA as a superior architecture or anything like that.

It does look like it has a bit of learning curve, but I do think it's a really cool library!

It’s perfectly fine that the repository implements specific libraries. Nanoid could additionally be isolated in its own service, but I deemed it might be an overkill for this scenario.

Glad you liked it! Treat the controllers as part of your core app’s logic, and everything framework-related as a “consumer”. You want all crucial logic like input validation and auth checks to be in your core app logic, so all consumers will function the same. Instead of calling a server function inside of an api handler, just call the controller in both places and handle the errors accordingly. That would be the smartest way to go about this.

Thank you!

Thank you! Not sure if I’ve seen anything like that. Hop into creatures.sh and we can figure it out!

Thank you! And thank you for becoming a member! 💖

Good question! In my other project, I reuse the same Zod schema on the client-side to validate the form as well. Validating input is a *must* on the server-side, because it's easy to jump around the frontend and send data directly to the server without passing the validation mechanism. Validation on the frontend is good UX, validation on the backend is good security practice.

@@nikolovlazar Thank you for your time to response, I think I wasn't explicit enough with my question, the question was not 'to validate or not' but 'where to validate'. You validate your outgoing data inside your repository and sending back the validation error to the UI to handle it, most form libraries handle the validation in the context of the form and if the data is not valid it will never reach the repository ( repository call will never be reached in the onSubmit since the validation does not pass ). So my question is which one should be preferred as doing the latter feels good because of the proximity of the input to the form, the former makes sense in an 'architectural way' as the controller is the "gateguard" of the data 'correctness' of your application.

No I think I understood you. You should validate on both sides. As I mentioned, form validation is good UX, but you have to validate in the controller as well for security reasons. Validating in both places is a good practice. With Zod, you can even share the same validation schema. Here's how I do that in my other project: - Form: github.com/nikolovlazar/bife/blob/main/app/app/collections/create-collection.tsx#L38 - Controller: github.com/nikolovlazar/bife/blob/main/src/interface-adapters/controllers/create-collection.controller.ts#L6

@@nikolovlazar lookin at the code indeed you are double validating your outgoing data, thanks for sharing, but now then I have to ask isn't double validating redundant? ( or it is in this case but there might be a situation when something can actually happen between your action and the controller, the current example is very straightforward you pass the validated data directly into your controller, where you validate it again, i am interpreting correctly )

Double validation is not redundant. The backend and the frontend are two separate things that can live independently from each other, so each part handles validation for separate reasons. You could refactor it down the line and split it, or build a new client (ex. mobile app, AI client, whatever that uses the backend you already have) so you’ll have to refactor the server actions into api handlers. Even now, you can’t risk not validating the data on the backend, let alone in a scenario like that. Consider the backend and the frontend as two separate parts and validate data at both places. There won’t be any significant performance overheads as well.

It’s in regard to my Clean Architecture video. It’s not that it’s not possible, but the general consensus is that people prefer functions because they’re easier to work with. I do use classes for my services and repositories (because they’re injected with DI), but controllers and use cases don’t need to be, so it’s easier to write them as functions. There are no tradeoffs as well. Everything works the same, and controllers and use cases are still testable. There’s no reason to write them as classes.

@@nikolovlazar I have used boths in my life, but I think this is opinionated and there is any rule for it. You can easily use class or functions there is not difference. I consider that there are tradeoffs by using functions into indeviduals files, and that is that you increase the effor by adding and adding more files into your tree wich in medium and big projects this is really messy.

That's true, and a really good point about keeping individual functions in files. Classes are much tidier in that regard. There is no rule, just a preference. I did notice more JavaScript devs prefer functions over classes so I that's why I went with a functions-first approach. It's a good start and it can work for you for a long time, but if it starts to become painful you can always refactor into classes. Definitely a good idea to have that in mind when you start a new project.

@@nikolovlazar Yeap! Thanks for sharing your amazing knowladge niko!

@@pinocodexof course! Thanks for asking in the first place!

Glad you liked it! And that's a good question! I think the only thing forcing the libraries to push updates (once they achieved what they want to achieve) is the language itself. As TypeScript / JavaScript evolves and introduces breaking changes, they most likely would need to push an update. That doesn't happen as often, so that's why you don't see any activity on these repositories for an extended period of time. On the other hand, just like any other library dependency, there is always a risk of deprecation and refactoring.

I made some changes since then, but still check it out! 😁 Video on my latest setup: ua-cam.com/video/G7-qUMKSH_Y/v-deo.html Dotfiles: github.com/nikolovlazar/dotfiles

That would be an interesting topic. CA on the client side!

Yep, lazygit has given me a few headaches as well, but so far it's good. I also didn't know about tig, thanks for sharing it! I've gotten so used to lazygit it's fully a muscle memory at this point.

Hey! Depending on what your keybinding is set to. I open my autocomplete with Ctrl-Space, and pick the selected option with Ctrl-Y (for Yes). Auto-imports should show up as options in the autocomplete menu.

@@nikolovlazar thanks i am currently using your dotfile for nvim config and i love it

Thank you! This is not vscode, but neovim. Here’s my config video: ua-cam.com/video/G7-qUMKSH_Y/v-deo.htmlsi=kq2lTPyJaQqa9JTl

That’s Tmux!