Skip to content

Add for removal to previously deprecated methods and classes#15470

Draft
matrei wants to merge 20 commits into7.1.xfrom
deprecate-for-removal
Draft

Add for removal to previously deprecated methods and classes#15470
matrei wants to merge 20 commits into7.1.xfrom
deprecate-for-removal

Conversation

@matrei
Copy link
Contributor

@matrei matrei commented Feb 27, 2026

This will make it easier to remove these in 8 or later.

Add for removal and also to the adapter and the adapter bean.
Add for removal.
This is useful as it runs in the same context as setup()
but only runs once. This gives you access to objects
not yet initialized in setupSpec().
Update docs and usages to the preferred `updatable`
property name.

Cheap to keep backwards compatibility,
so no urgent need to remove.
Add for removal.
Copy link
Contributor

@jdaugherty jdaugherty left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems reasonable. It also reminded me of the GrailsDomainClass vs PersitentEntity change. Should we consider removing domainclass? I know it's a major change but in line with hibernate it may be worth it.

@matrei
Copy link
Contributor Author

matrei commented Feb 27, 2026

This seems reasonable. It also reminded me of the GrailsDomainClass vs PersitentEntity change. Should we consider removing domainclass? I know it's a major change but in line with hibernate it may be worth it.

I looked at GrailsDomainClass, but skipped on as it was not an easy removal like the rest of these. But we should definitely figure out the correct way to deal with that deprecation also. There is also JsonBuilder in grails-converters

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants