> Looks good.
>
> Any idea how to prevent people from changing the code and forgetting to update
> the qmltypes file? Could we think of a simple and fast test that verifies if
> they're up to date?
You'd need to be able to check that the API provided by the plug-in actually changed, outside of building the qmltypes file.
Maybe just add something to the review checklist and rely on that?
> Looks good.
>
> Any idea how to prevent people from changing the code and forgetting to update
> the qmltypes file? Could we think of a simple and fast test that verifies if
> they're up to date?
You'd need to be able to check that the API provided by the plug-in actually changed, outside of building the qmltypes file.
Maybe just add something to the review checklist and rely on that?