New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
domainSuffix ignored by views #10023
Comments
I believe that is all behaving as expected except for the fact that the scaffolding plugin doesn't take |
Yes, I think if dynamic scaffolding views respected the domainSuffix setting (as they do in 2.4) all would be good. |
This issue should probably be filed against the plugin. |
In JIRA, I (or an admin) would move this to the correct project, but I don't see a way to do that here. Can you do that? |
I don't think so. I will just close this issue. Feel free to create a similar one at https://github.com/grails3-plugins/scaffolding/issues if you like. |
Environment:
Windows 8.1
jdk1.8.0_92
Grails 3.1.7
I have upgraded an app from 2.4 to 3.1.7 and notice issues with scaffolding. In my 2.4 app, I had in Config.groovy:
grails.scaffolding.templates.domainSuffix = 'Instance'
And I'm pretty sure that was added by default, which means this will affect a lot of people.
In my controller's index method (rendered by default with the list scaffolding view), this line worked:
possibleDups is a list that corresponded with companyInstanceList, and the view rendered perfectly.
After upgrading to 3.1.7, both the main body (list) and pagination were empty. After testing, I discovered the following:
I tested by explicitly setting model variable names::
domainSuffix is also ignored in static scaffolding, as views generated with
look for companyList, not companyInstanceList, etc.
Right now, the workaround is to:
If this was intentional, the Upgrading and Scaffolding sections of the documentation should be updated to prevent confusion.
The text was updated successfully, but these errors were encountered: