Thomas Boyer-Chammard

If the object is an `EventTemplate`/`ChTemplate` ([here](https://github.com/nasa/fprime-gds/blob/devel/src/fprime_gds/common/templates/ch_template.py#L19-L20)), they are not associated with a particular sample of telemetry, so there's no value to populate. If the object is an `EventData`/`ChData`, then...

--> provide another `get_typed_format_str()` or something that inserts the C-style format specifiers in the tokens

Closing in favor of #3923

Should the F Prime OSAL impose a specific behavior when calling `Os::File::open()` on a directory (has to error / succeed), or should that be up to the OS implementation ?...

Fixed (see above PRs)

@Kronos3 for the `fprime-examples` CI you likely need to merge the latest `fprime-examples@devel` in your `pr-xxxx` branch

Reminder: need to merge https://github.com/nasa/fprime-examples/pull/11 when (ideally right before) merging this PR here.

This is a good point. It would also remove the need to purge the build cache if generation hasn't been successful in some instances. What do we think would be...

Agreed! If anyone would like to contribute for this, changes likely should be around this function or wherever it gets invoked by `fprime-util generate` https://github.com/nasa/fprime-tools/blob/b72544568269010abf2197d9b0dec10bce40e71c/src/fprime/fbuild/builder.py#L371

It might be that this snippet can just be removed. But I don't know, there may be something else under. Here's how you can test it out yourself with a...