yrosseel/lavaan

A minor issue with the documentation of `lavParseModelString()"

sfcheung opened this issue · 1 comments

I believe this issue may be fixed in the coming version but I open this issue anyway because it is in 0.6-17:

The current documentation of lavParseModelString() says that the default for parser is "new":

lavaan/man/model.syntax.Rd

Lines 170 to 171 in 9e1401d

\item{parser}{Character. If \code{"old"}, use the original/classic parser.
If \code{"new"}, use the new/ldw parser. The default is \code{"new"}.}

However, the default of parser in the function definition actually is "old":

lavaan/R/lav_syntax.R

Lines 5 to 7 in 9e1401d

lavParseModelString <- function(model.syntax = "", as.data.frame. = FALSE,
parser = "old",
warn = TRUE, debug = FALSE) {

I also casually searched calls to lavParseModelString() by lavaan function also relies on the default value of parser in lavParseModelString(). E.g.,

lavaan/R/lav_partable.R

Lines 66 to 68 in e63d492

flat <- lavParseModelString(
model.syntax = model, warn = warn,
debug = FALSE

Hope this helps.

Thanks. We temporarily changed the parser from "new" to "old" (for testing purposes only). As of today, it is back to "new" again. But we may change it back and forth a few times while testing in the next weeks. Eventually, it will stay "new".