When a smartdocs model is created in Developer portal, a Drupal views gets generated dynamically. Will this create any issue in long run?

[#1]

When a smartdocs model is created in Developer portal, a Drupal views gets generated dynamically based of "Smartdocs Method Listing" View.

Reference:

Smartdocs Method Listing Display: Block In code Type: Content

This is the base view for listing methods in a given model. Whenever you create a new model, a per-model view is generated based on this one.

Let's say the website has 100+ models & views, and if you want to make a change to the views, 100+ views need to overridden. Is this architecture maintainable & scalable?

[jaywanttopno-1]

HI Vignesh M

As per my knowledge, when an admin creates smartdocs by uploading swagger/yml file. an automated view/block get created for specific smartdocs API collection.

going forward if you want to make changes in n number of views/block, then it would be very difficult to apply changes. on the other side. it gives you an flexibility of managing multiple views blocks/pages.
i.e: imagine you want to add role based access or you wanna make display order change for particular smartdocs APIs.

Suggested solution: could be: on successful creation of smartdocs. create master block/page for smartdocs listing[Automated process/ not manual]. and keep rendering the data to the view page/block using contextual filter.