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
As the user of Stalker I want the Version class to have anoter major version counter called revision_number which precedes version_number attribute so that I can iterate with major and minor version numbers.
Acceptance Criteria
This should be done after #78 and #120 (the Version.variant_name being removed). This is basically replacing the variant_name with a numeric attribute.
Update Version class:
Add a new mapped int attribute called revision_number.
The revision_number should start from 1.
version_number attribute should be grouped with the revision_number so that incrementing revision_number by 1 should reset the version_number to 1.
Update Version.latest_version so that it returns the highest version_number with the current revision_number of the Version instance.
Update Version.maximum_version_number so that it returns the highest version_number with the current revision_number of that particular Version instance.
Add Version.maximum_revision_number that returns the maximum revision_number in the database.
Update Version.is_latest_published_version to check with the current revision_number of the Version instance.
Update Version.latest_published_version it should return the latest published version with the same revision_number.
Update Version.__eq__() tests to also check the functionality with different revision_number attribute values.
Update the defaults.filename_template to:
filename_template='{% for naming_parent in version.naming_parents%}{{naming_parent.nice_name}}_{%endfor%}r{{"%02d"|format(version.revision_number)}}_v{{"%03d"|format(version.version_number)}}'
Add alembic revision.
The text was updated successfully, but these errors were encountered:
Because the Review class now has the version attribute and the Version has the reviews attribute (8de3bf1), the Version.review_number is giving the impresion that it is related to the Review.review_number attribute, we might use the DNEG's approach by naming them as major and minor versions... I'm not sure, maybe we should come up with a different name.
We might keep the name revision_number but we might do it together with the removal of variant_name in #120 as the revision_number attribute is kind of replacing the variant_name attribute.
User Story
As the user of Stalker I want the Version class to have anoter major version counter called
revision_number
which precedesversion_number
attribute so that I can iterate with major and minor version numbers.Acceptance Criteria
This should be done after #78 and #120 (the
Version.variant_name
being removed). This is basically replacing thevariant_name
with a numeric attribute.Update
Version
class:int
attribute calledrevision_number
.revision_number
should start from 1.version_number
attribute should be grouped with therevision_number
so that incrementingrevision_number
by 1 should reset theversion_number
to 1.Version.latest_version
so that it returns the highestversion_number
with the currentrevision_number
of theVersion
instance.Version.maximum_version_number
so that it returns the highestversion_number
with the currentrevision_number
of that particularVersion
instance.Version.maximum_revision_number
that returns the maximumrevision_number
in the database.Version.is_latest_published_version
to check with the currentrevision_number
of theVersion
instance.Version.latest_published_version
it should return the latest published version with the samerevision_number
.Version.__eq__()
tests to also check the functionality with differentrevision_number
attribute values.Update the
defaults.filename_template
to:Add alembic revision.
The text was updated successfully, but these errors were encountered: