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
To ensure that temporary or debug-specific code does not make it into production branches, this serves as a reminder to integrate the @doNotSubmit annotation from the meta package (1.14.0) once the Dart SDK constraints are updated to 3.4.0 or higher. The current lower SDK bounds prevent updating to Dart SDK 3.4.0, which supports meta version 1.14.0. This update would lock out a portion of the user base, hence the delay.
The @doNotSubmit annotation is designed to mark APIs that are intended for temporary or ephemeral use—such as those used during development or local testing—and should not be checked into the main branch. This annotation serves as a useful tool to flag certain code sections that need to be revisited or removed before final code submission, thus preventing potential issues in production.
An example of where this could be highly beneficial is with methods like takeScreenshot that are often used for debugging purposes but should not be available in the production environment.
The text was updated successfully, but these errors were encountered:
To ensure that temporary or debug-specific code does not make it into production branches, this serves as a reminder to integrate the
@doNotSubmit
annotation from the meta package (1.14.0
) once the Dart SDK constraints are updated to3.4.0
or higher. The current lower SDK bounds prevent updating to Dart SDK3.4.0
, which supports meta version1.14.0
. This update would lock out a portion of the user base, hence the delay.The
@doNotSubmit
annotation is designed to mark APIs that are intended for temporary or ephemeral use—such as those used during development or local testing—and should not be checked into the main branch. This annotation serves as a useful tool to flag certain code sections that need to be revisited or removed before final code submission, thus preventing potential issues in production.An example of where this could be highly beneficial is with methods like
takeScreenshot
that are often used for debugging purposes but should not be available in the production environment.The text was updated successfully, but these errors were encountered: