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
My believes is we should keep this flag, but extent it to room all tested records as we are moving forward to use several thin-clients against a Central DataBase (CDB).
We would then need this flag to control whether a string is for a complete retest of a file (IE: Dev new code for runners) or use some defaults depending on the categorized contents which is being tested.
The next thing could be a new flag for !ACTIVE retest.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Initial thread goes here: #142
My believes is we should keep this flag, but extent it to room all tested records as we are moving forward to use several thin-clients against a Central DataBase (CDB).
We would then need this flag to control whether a string is for a complete retest of a file (IE: Dev new code for runners) or use some defaults depending on the categorized contents which is being tested.
The next thing could be a new flag for
!ACTIVEretest.Initial thought 💭 🤔
Beta Was this translation helpful? Give feedback.
All reactions