7.1.x AutoTmestamp Enhancements + grails.importGrailsAnnotations GrailsExtension

[codeconsole]

Introduce @CreatedDate, @LastModifiedDate, @CreatedBy, and @LastModifiedBy similar to Spring Data

Introduce grails.importGrailsCommonAnnotations to automatically import common grails annotations and jakarta.validation.constraints.*

build.gradle

grails {
    importJavaTime = true
    importGrailsCommonAnnotations = true // kitchen sink
    starImports = ['java.util.concurrent', 'groovy.transform'] // fully customizable
}

allows the following with no imports

class User {
    String firstName
    String lastName
    String email
    @CreatedDate Instant created
    @LastModifiedDate Instant modified
}

class Car {
    String make
    String model
    @CreatedBy User owner
    @LastModifiedBy User driver
    @CreatedDate Instant purchased
    @LastModifiedDate Instant lastDriven
}

    @Bean
    AuditorAware<User> springSecurityAuditorAware() {
        return new AuditorAware< User >() {
            @Override
            Optional<String> getCurrentAuditor() {
                Optional.ofNullable(SecurityContextHolder.context)
                        .map { it.authentication }
                        .filter { it?.authenticated }
                        .map { (User) it.principal }
            }
        }
    }

@Scaffold(GormService<User>)
class UserService implements UserDetailsService {
    @Override
    UserDetails loadUserByUsername(String username) throws UsernameNotFoundException {
        return User.findByEmail(username)
    }
}

import grails.plugin.scaffolding.RestfulServiceController

@Scaffold(RestfulServiceController<User>)
class UserController {}

[jdaugherty]

Per the weekly meeting, we'll merge this into 7.1. The vote to create that branch is going now - once 72 hrs have passed, we'll create the branch.

[jdaugherty]

@codeconsole Can you update this PR now that you've made your mongo update date fixes?

[codeconsole]

@codeconsole Can you update this PR now that you've made your mongo update date fixes?

Done

[jdaugherty]

I've updated 7.1.x with the latest 7.0.x changes. Can you please merge 7.1.x into this PR so the changes are reflected?

[jdaugherty]

My largest problem is the breaking change with the isDevelopmentMode(). We need a better solution here. Can you give your reasoning for disabling the caching in development mode?

[jdaugherty]

Why can't constraints be added for the auditor type? It's perfectly reasonable if the auditor is a String, to set a max string (i.e. if you wanted a value greater than 255)

[matrei]

This is true, as auditor can be different types, and constraints influence the database schema.

[jdaugherty]

1. Can we pull this into it's own file?
2. Is "AutoTimestamp" really a good name for createdBy / updatedBy? Would Tracked or TrackedEntityType be a better name?

[codeconsole]

My largest problem is the breaking change with the isDevelopmentMode(). We need a better solution here. Can you give your reasoning for disabling the caching in development mode?

@jdaugherty You are looking at it from the wrong perspective. I am introducing caching when not in development mode. The current implementation has no caching. The performance benefit is so negligible that I suspect you wouldn't even notice.

[jdaugherty]

We should just always cache. We don't need the dependency that way.

[matrei]

This is true, as auditor can be different types, and constraints influence the database schema.

[matrei]

getInputProperties(PersistenProperty, List<String>, boolean) is not part of the DomainModelService interface.

[matrei]

This class is no longer implementing getInputProperties(PersistentEntity, List) from the DomainModelService interface.