Overriding FPrime components

[zimri-leisher]

One thing I have had to do several times now is copy an Fprime component into a local repo so we can change a very small part of the component's behavior (printout, event args, assert args, etc). This means we cause merge conflicts when we try to pull in updates from a new FPrime version.
This would be mitigated if there were a way of overriding the behavior of an FPrime component in a separate file. Any suggestions for how to do this?

[LeStarch]

The current recommended practice is to use interfaces (.fppi containing ports) and implement the interface. It isn't great for making small adjustments to the components. F´ would need to add interfaces for any component following this approach.

The other option is to do a PR back to F´  with your suggestions and work with us to get it merged. Not great for small changes that are inherently tied to a project without wider utility.

I don't think there are other clean approaches, that don't have serious trade-offs.

[zimri-leisher]

I wonder if one possibility would be for us to write a component that included the original FPP file (even though it's not an fppi file). Maybe we could even #include the cpp

[kevin-f-ortega]

It would be cool to do/allow some sort of component inheritance