Here's a quick review:
in .cleanData() you're using:
as.numeric(as.character(data[,x]))
to coerce factors to numeric. the issue with this is that if the column contains non-numeric values, it will (almost) silently convert these to missing values (NAs).
so you should use jmvcore::toNumeric() instead
after calling toNumeric() you can check that it is now numeric, and throw an error if it isn't.
https://dev.jamovi.org/tuts0202-handling-data.htmlyou also want to add .Rhistory and *.jmo to your .gitignore file (and not to your repo)
i'd encourage you to use camelCase for option names, and i'd encourage you to use the same column labels as we use in jamovi (just to be consistent). i.e.
SD for standard deviation
SE for standard error
p for p value
t for t statistic
we try and avoid dots in column headings
etc. we'll try and put together a style-guide for this stuff.
for your footnote, you have 'some computational error has occurred in lmerTest, summary from lme4 is returned' ... which is fine, but the user will be more interested in *why* and *how/if they can fix it* (and will be less interested in where it went wrong) ... but this error message might be appropriate if you're targeting a very technical audience.
finally, your indentation could do with some love, it's not always consistent.
cheers