Skip to content

Document @DirtiesContext semantics when declared at the class level and method level #30623

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

Closed
manueljordan opened this issue Jun 8, 2023 · 2 comments
Assignees
Labels
in: test Issues in the test module type: documentation A documentation task
Milestone

Comments

@manueljordan
Copy link

About the current javadoc for the DirtiesContext annotation there is no an indication about what happens if the annotation is annotated twice, it in a class level and method level.

So would be nice indicate if exists an overriding of the method over the class or a simply a merge of both.

Thanks for your understanding.

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged or decided on label Jun 8, 2023
@sbrannen sbrannen changed the title Improve @DirtiesContext javadoc about what happens when is declared twice - class and method level Document @DirtiesContext semantics when declared at the class level and method level Jun 9, 2023
@sbrannen sbrannen self-assigned this Jun 9, 2023
@sbrannen sbrannen added in: test Issues in the test module type: documentation A documentation task and removed status: waiting-for-triage An issue we've not yet triaged or decided on labels Jun 9, 2023
@sbrannen sbrannen added this to the 6.0.10 milestone Jun 9, 2023
@sbrannen
Copy link
Member

sbrannen commented Jun 9, 2023

This has been addressed in 6.0.x and `main.

@manueljordan
Copy link
Author

As usual, thanks for your polite support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: test Issues in the test module type: documentation A documentation task
Projects
None yet
Development

No branches or pull requests

3 participants