I also agree with Galen's framing.
Standalone components will definitely make the simple generic
components easier to use, I think, but NgModules will still be useful
for encapsulation in some important cases.
Thanks, all!
--
Mike Rylander
Research and Development Manager
Equinox Open Library Initiative
1-877-OPEN-ILS (673-6457)
work: miker(a)equinoxOLI.org
personal: mrylander(a)gmail.com
https://equinoxOLI.org
On Thu, Feb 27, 2025 at 5:26 PM Jane Sandberg via Eg-newdevs
<eg-newdevs(a)list.evergreen-ils.org> wrote:
>
> +1 from me to Galen's formulation! Thanks for the discussion so far, Galen and Ruth!
>
> El jue, 27 feb 2025 a la(s) 1:02 p.m., Galen Charlton (gmc(a)equinoxoli.org) escribió:
>>
>> Hi,
>>
>> On Thu, Feb 27, 2025 at 9:10 AM Jane Sandberg via Eg-newdevs <eg-newdevs(a)list.evergreen-ils.org> wrote:
>> > But my proposal is that after a certain date TBD, if you create a new component, please make it standalone.
>>
>> I think this is too strong at present until we collectively get more experience with standalone components. While the standalone model does look useful - and of course, in the long run it does not pay for us to try to buck what's a very clear trend in Angular's evolution - we do have several sets of closely-linked components where keeping them bundled in an NgModule may still make sense (e.g., eg-grid). I fear that - for now - setting an absolute requirement that new components be standalone may reduce flexibility and create an implicit expectation that we _must_ perform (and pay for in various ways) what would be a large refactoring of the existing NgModule-based app.
>>
>> Consequently, I would propose a different formulation in two parts:
>>
>> * Writing new Angular components as standalone is both permitted and encouraged
>> * After more time has passed and we have more experience with wrestling with the management of dependencies for standalone components, we'll reevaluate whether a stricter mandate is warranted.
>>
>> By the way, I found this piece an interesting exploration of the opportunities and tradeoffs: https://borstch.com/blog/development/angulars-ngmodules-vs-standalone-compo…
>>
>> Regards,
>>
>> Galen
>> --
>> Galen Charlton
>> Implementation and IT Manager
>> Equinox Open Library Initiative
>> gmc(a)equinoxOLI.org
>> https://www.equinoxOLI.org
>> phone: 877-OPEN-ILS (673-6457)
>> direct: 770-709-5581
>
> _______________________________________________
> Eg-newdevs mailing list
> Eg-newdevs(a)list.evergreen-ils.org
> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/eg-newdevs
