You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to have predictable behaviour in implementations and when interacting with those scopes, we should clearly specify their lifecycles in the relevant Javadocs.
By now, we have numerous
Scope
types in our API. They all have a different lifecycle, and thus a different meaning of:Scope::creationTime
(see Add Scope.creationTime() and make it available through GeneratorContext.renderTime() #13471)Scope::data
In order to have predictable behaviour in implementations and when interacting with those scopes, we should clearly specify their lifecycles in the relevant Javadocs.
The list will be amended:
BindingScope
(see Add BindingScope, a common super type of the various BindingXYZContext types #13497)BindingSQLContext
BindingGetResultSetContext
BindingGetSQLInputContext
BindingGetStatementContext
BindingRegisterContext
BindingSetSQLOutputContext
BindingSetStatementContext
CacheContext
Context
BindContext
RenderContext
DSLContext
CloseableDSLContext
ExecuteContext
ExecuteScope
GeneratorContext
Meta
Migration
ParseContext
RecordContext
ResourceManagingScope
TransactionContext
VisitContext
The text was updated successfully, but these errors were encountered: