<div dir="ltr">+1 from me to Galen's formulation! Thanks for the discussion so far, Galen and Ruth!</div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">El jue, 27 feb 2025 a la(s) 1:02 p.m., Galen Charlton (<a href="mailto:gmc@equinoxoli.org">gmc@equinoxoli.org</a>) escribió:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hi,<br><br>On Thu, Feb 27, 2025 at 9:10 AM Jane Sandberg via Eg-newdevs <<a href="mailto:eg-newdevs@list.evergreen-ils.org" target="_blank">eg-newdevs@list.evergreen-ils.org</a>> wrote:<br><div>> But my proposal is that after a certain date TBD, if you create a new component, please make it standalone.</div><div><br></div><div>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.</div><div><br></div><div>Consequently, I would propose a different formulation in two parts:</div><div><br></div><div>* Writing new Angular components as standalone is both permitted and encouraged</div></div><div>* 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.</div><div><br></div><div>By the way, I found this piece an interesting exploration of the opportunities and tradeoffs: <a href="https://borstch.com/blog/development/angulars-ngmodules-vs-standalone-components-pros-and-cons" target="_blank">https://borstch.com/blog/development/angulars-ngmodules-vs-standalone-components-pros-and-cons</a></div><div><br></div><div>Regards,</div><div><br></div><div>Galen</div><div>--<br>Galen Charlton<br>Implementation and IT Manager<br>Equinox Open Library Initiative<br>gmc@equinoxOLI.org<br><a href="https://www.equinoxOLI.org" target="_blank">https://www.equinoxOLI.org</a><br>phone: 877-OPEN-ILS (673-6457)<br>direct: 770-709-5581</div></div>
</blockquote></div>