I don't see the point in this at all. The singular name style is to allow the use of the JModel Class. The plural names are for the legacy classes. I don't think we should be letting people use the legacy classes in the singular view name styles

This change not only for new MVC, if people want to use autoloading in legacy component, singular name can help this working well since table and form has already support singular name.
https://github.com/joomla/joomla-cms/blob/staging/libraries/legacy/model/legacy.php#L265

I think it will helpful when some component in a working process when they are changing to new style.

I tend to agree with @wilsonge. Mixing new and old MVC in the legacy classes doesn't sound like a good idea to me.
Table and form are different because they are not part of the MVC structure itself.

I agree with @asika32764's change.

You shoud notice that in the old MVC classes are already using singular names (which can be considered a bug in the whay that the legacy MVC works). If you want to have autoloading working out of the box in your component you can directly name models folder to model but for BC we have to keep models working.

That's why we need both working

I double checked it and if it's supposed to be autoloading it shouldn't be added manually like this PR does.

It should be enough with adding to your front controller. Example for content:

// Register component prefix
JLoader::registerPrefix('Content', __DIR__);

The real fix would be to replace the current createModel method with:

/**
 * Method to load and return a model object.
 *
 * @param   string  $name    The name of the model.
 * @param   string  $prefix  Optional model prefix.
 * @param   array   $config  Configuration array for the model. Optional.
 *
 * @return  mixed   Model object on success; otherwise null failure.
 *
 * @since   12.2
 * @note    Replaces _createModel.
 */
protected function createModel($name, $prefix = '', $config = array())
{
    // Clean the model name
    $modelName = preg_replace('/[^A-Z0-9_]/i', '', $name);
    $classPrefix = preg_replace('/[^A-Z0-9_]/i', '', $prefix);

    $className = ucfirst($classPrefix) . ucfirst(strtolower($modelName));

    if (class_exists($className))
    {
        return new $className($config);
    }

    $result = JModelLegacy::getInstance($modelName, $classPrefix, $config);

    return $result;
}

That will really make autoloading work.

@asika32764 can you double check if that fixes the issue and update your PR if you agree? Thanks!!

Thank you, I will check it when I have time.

I think we are discussing without a base position, me and @phproberto focus on autoloading, and we think autoloading is not equal to new MVC, so we trying to make legacy MVC work in autoloading with singular name.

So, this change depend on maintainer think autoloading & singular name is same as new MVC or not.

@asika32764 I would be fine with the approach of Roberto. Follow his lead

Thanks @phproberto , this code working well.

Actually I use this way at the beginning, but in this way, view have to build class name as ContentViewArticleHtml, I really don't want to mix new MVC's style in ControllerLegacy, so I choosing to use setPath() instead build this class name in the createView().

So, what everyone think about how to approach the view?

@asika32764 Can you please provide step-by-step test instructions so we know how to test your pull request? Thank you. If no test instructions are provided within 4 weeks, this PR will be closed. Thank you for your contribution.

Since no information has been provided I am going to close this issue. Feel free to re-open when you are ready and the issue still exists.