The Price of Using Local Packages in Flutter

I hate over complicating solutions that doesn't need it, here is my take on packages.

Want to support me?

····················································································
You can find me on:
····················································································

[RobertBrunhage]

If you agree or disagree, let me know. I would love to be proven wrong here!

Hope you find the new format interesting, I am trying it out and with that can tackle a lot more interesting topics. If there is anything you want me to cover, let me know!

[krzysztofk.]

Talking about overengineering. 90% of the time these packages will be only used inside this particular app so generally they could be just inside `lib` directory and be part of the app.

[artofnessa]

I really LOVE the new set up you have🎉

[rydmike]

Nice to see you back Robert! There is a lot to be said for avoiding complexity, but sometimes it also needed. Right balance can be tricky. I'm guessing the news toolkit sample is also intended to demonstrate this technique, but went a bit overboard with it, for its particular use case. Cool studio 😀💙

[easazade]

I think in this project they made the right choice, implementing it like this. since this is a template project. and being easy to customize is the top priority. this way you have all the components of your app decoupled and hence customizing them is easier. but the trade-offs are the points you mentioned

[TechBuddy_]

wow the nvim setup looks cool, also the new video style is good I love it

[imamhatipoglu]

Yaay 🎉 New video. İt's cool setup, i like it. I'm using GNU Emacs for Python, but it's hard on flutter. Even I love Emacs, I don't think vim or emacs good enough for flutter.
About the packages you're right local packages is good for dictionary structure. İ have big project but i got long analyze times, even sometimes not response about the autocomplete, especially about the auto imports.

[samafaby]

La respuesta universal es, depende. Depende del proyecto, del tamaño, de la estructura que la compañía defina, son muchos los factores. En mi visión con proyectos grandes, la complejidad es menor al enfocar reglas de negocios específicas en módulos o paquetes que sólo cuiden ese objetivo. En proyectos pequeños esto no sería necesario y lo consideraría sobre-ingeniería. En mi experiencia con un proyecto empresarial muy grande, estamos tratando de modularizar para acortar los tiempos de desarrollo-producción ya que nuestro talón de aquiles son los tiempos de ejecución de pruebas. Cuando el primer requerimiento es tener 100% de coverage, las pruebas tomarán mucho de tu tiempo en el día a día.

[DevLife]

Excellent points I agree. Digging the nvim setup also but why do the line numbers seem out of sequence?

[thebitcoinranch]

I think that it's ok to use the local package approach when it's necessary. I do not justify creating a LOCAL package for a single or couple of repositories, but I'm in favor to use local packages to create domain boundaries and expose only the necessary for specific modules or features.

[leoingson]

I agree, overengineered. Being prepared for eventualities vs just solving the problem. Keep the trash coming!

[_undecided]

Not all understand reason of using packages. I can explain in short. You create package then if you can use it in another app that's reason for why packages is, but if package is created only for the one app then it called overengineerig.

[jeromestsauver]

I'm curious what some alternatives to packages might be for sharing code in flutter? I'm at a point that I would like to share a piece of functionality across 2 projects. I started down the packages path, but agree with the complexity of managing dependencies. Any thoughts about this?

[codegambit]

I enjoyed the video. Thank you. Please I can u share your vim config for flutter?

[dhanniekristanto]

It's been a while since you last upload something about flutter. I thought you switched to react 😄

[KeithDCommiskey]

After looking at the code, is having an `api` folder (or similar) as a sibling to `lib` and `packages` a common pattern? Feels weird having Dart files outside of `lib` or `packages`, but maybe I just haven't had the exposure to such.

[mohamedislambenoaie]

i can't join your discord !!!!
Why

[kuba-nb]

Random youtuber critizies very good ventures architecture 🤣🤣🤣 Anyway you just said words, but zero arguments, very bad video.

[chordfunc]

I have a topic for you:
Testing like in the news_repository_test.dart in the example app you referenced.
What are your thought of this type of testing... to me it seems completely bonkers.

when(apiClient.getCategories)
.thenAnswer((_) async => categoriesResponse);

expect(
newsRepository.getCategories(),
completion(equals(categoriesResponse)),
);