| 21 Sep 2023 |
|  cponfick changed their display name from cponfick#0 to cponfick. | 06:09:02 |
|  keshav363 joined the room. | 07:05:33 |
 rodi | Hi, all. I am a novice in web development and still learning concepts related to DDD etc. IMHO, litestar's layered architecture(App, Router, Controller, Handler function), DI, DTO are literally astronishing and pleasure to follow that. However, the concept of Repository doesn't fit my brain yet although there is a good doc(tutorial, not a kind of concepts and ratoinale such as Usage part of DI, DTO etc. sadly) The question is that is it okay(sometimes recommended) not to use repository pattern (library built-in) to handle logic and persistence layer hadling? Thanks for reading a dumb question... | 11:48:09 |
|  stephenyau joined the room. | 13:57:29 |
 pedro.diaz | What we call here as "repository" is a design pattern that consists in abstracting the data layer of the application | 14:07:15 |
| pedro.diaz | Don't feel like you're attached or forced to use something you don't like to use, you're free to use whatever you feel like to, you're not limited to anything in Litestar | 14:09:29 |
| pedro.diaz | I do use the repository pattern, but I don't use its DTO for example | 14:09:57 |
| rodi | Redacted or Malformed Event | 14:18:41 |
| rodi | Yeah.. you're right! Thank you for sharing your thoughts. It's not related to this question. I see discussions in django community about service layer vs. fat models in context of django ORM(Active Record), and generic class based view vs. function view(one of maintainers call right way), many others. I think I just have to push myself to put product(webapp) in production and then make codebase better iteratively.. Thanks again for the reply. | 14:18:56 |
| pedro.diaz | Cheers | 14:19:54 |
|  stuzero joined the room. | 15:10:24 |
|  tumeboy_89081 joined the room. | 20:09:50 |
|  mythres joined the room. | 21:18:12 |
 __peter__ | I think I just have to push myself to put product(webapp) in production and then make codebase better iteratively | 22:46:54 |
| __peter__ | this is the way 🙂 | 22:46:58 |
| 22 Sep 2023 |
 alc.alc | then make codebase better iteratively.
famous last words | 07:46:25 |
|  moutafatin changed their display name from Moutafatin to moutafatin#0. | 14:54:30 |
| moutafatin changed their display name from moutafatin#0 to moutafatin. | 14:54:31 |
 Coffee | huh? | 17:00:18 |
 draconis1 | Just read the updated announcement | 17:01:56 |
| draconis1 | and drawing parallels haha | 17:02:03 |
 .litiam | Redacted or Malformed Event | 17:58:32 |
| .litiam | Redacted or Malformed Event | 17:58:47 |
|  naomirb joined the room. | 18:04:43 |
| 23 Sep 2023 |
|  selfhosted#0 joined the room. | 16:03:40 |
| selfhosted#0 | I was messing around with FastAPI/Vue to create a project, but found it a bit too bare bones. I had been following this since it was StarLite, and decided to give it a shot, but the lack of community resources has been the main blocker for me. Im curious if there are some good projects that not only show good form with the library, but also actually explain some things about the architecture/structure of the project?
Ive been reading through the litestar-fullstack app, and while I understand it at a high level, its questions about structure that Im having trouble understanding. The 'tutorial' just shows everything being built in one file, but the introduction of the domains/libs folders weren't really explained from what I was able to find | 16:03:41 |
| selfhosted#0 | I am coming at this as a first go at backend/full stack dev, so I know Ive got a lot to learn 😅
Most of my python work is for building internal libraries at my job combined with tooling for a specific team to utilize in the day to day | 16:04:36 |
 provinzkraut | Petition for cofin to release a course on litestar-fullstack 🙂 | 16:05:37 |
| alc.alc | from cofin as seen on #litestar-fullstack | 16:08:25 |
|  cemrehancavdar joined the room. | 21:23:19 |
