In this episode, the spotlight falls on Analog's recently introduced ng file format, alongside the Q&A segment moderated by Mark Thompson and Jeremy Elbourn.
.ng Files
Brandon Roberts introduced ng files, the newest addition to Analog, which is a framework built on top of Angular. This novel file format serves as the latest development. Analog then takes the contents of these files and converts them into a standard Angular component.
Essentially, the ng file is HTML at its core. Any logic, or TypeScript portion, which remains optional, is placed within the script tag.
While Analog generates these components with default settings, customization of the component's configuration is possible through defineMetadata. Interestingly, the selector for each component is determined based on the filename. For dependencies, merely importing the ng file in TypeScript suffices; there's no need to reference it within defineMetadata.
In the ng file architecture, emphasis shifts away from the TypeScript class and lands squarely on the template. Experimental and unique to Analog, these ng files serve a purpose—if they don't fit your current needs, consider them foundational work for prospective developments. Recall that the Angular core team is also investigating adjustments to its own authoring format.
Q&A with Mark and Jeremy
As usual, Mark and Jeremy, both from the Angular team, hosted their monthly Q&A session. If you catch the recording, you’ll see the future Signal Inputs in action. Jeremy walked through the API, demonstrated its usage, and covered some tricky scenarios.
Podcast Episodes
Should you require additional study resources, a number of podcast episodes have been released that could be of interest: