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
Presently, copyright lines are stringly typed in the tool. The whole thing SPDX-FileCopyrightText: 2016, 2018--2020, 2023--present Carmen Bianca BAKKER <carmenbianca@fsfe.org> is one string.
I think it might make sense to write some kind of CopyrightLine class that can parse elements from such strings. For example, the above properties of the above example:
copyright_prefix - SPDX-FileCopyrightText
date_range - some DateRange object that can encode the concept of 2016, 2018--2020, and 2023--present. Or, if that all is too over-engineered, just the string 2016, 2018--2020, 2023--present
name - Carmen Bianca BAKKER
contact - carmenbianca@fsfe.org
If implemented well, this could heavily simplify date-range merging, which is currently spaghetti code.
The text was updated successfully, but these errors were encountered:
Presently, copyright lines are stringly typed in the tool. The whole thing
SPDX-FileCopyrightText: 2016, 2018--2020, 2023--present Carmen Bianca BAKKER <carmenbianca@fsfe.org>
is one string.I think it might make sense to write some kind of
CopyrightLine
class that can parse elements from such strings. For example, the above properties of the above example:SPDX-FileCopyrightText
2016
,2018--2020
, and2023--present
. Or, if that all is too over-engineered, just the string2016, 2018--2020, 2023--present
Carmen Bianca BAKKER
carmenbianca@fsfe.org
If implemented well, this could heavily simplify date-range merging, which is currently spaghetti code.
The text was updated successfully, but these errors were encountered: