Skip to content
This repository has been archived by the owner on Sep 2, 2024. It is now read-only.

Merge DBCParser into Mapper #138

Merged
merged 1 commit into from
Sep 14, 2023

Conversation

sophokles73
Copy link
Contributor

The readers require a Mapper as well as information provided by the DBCParser. The Mapper itself also requires information from the parser.

The Mapper has therefore been changed to use the DBCParser class as a mixin. The readers and the Feeder have been adapted accordingly.

@sophokles73 sophokles73 force-pushed the merge_parser_into_mapper branch 3 times, most recently from 6ef3a0b to ce85994 Compare September 8, 2023 08:08
@sophokles73 sophokles73 marked this pull request as draft September 11, 2023 06:19
@@ -1,7 +1,7 @@
#!/usr/bin/python3

########################################################################
# Copyright (c) 2020 Robert Bosch GmbH
# Copyright (c) 2020,2023 Robert Bosch GmbH
Copy link
Contributor

@erikbosch erikbosch Sep 11, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@SebastianSchildt - do we somewhere have any guidelines on how to handle "years" in copyright? As of today we have for dbcfeeder two types of license statements, one (like here) stating Bosch copyright, others have a more generic "Contributors to the Eclipse Foundation". Then for year, when shall we add a new year like here. Always?

Edit: I noticed that in https://www.eclipse.org/projects/handbook/#ip-copyright-headers they say

"Do I need to update the year in the copyright statement when I make changes to the file?"

"No. The year in the copyright header should be the year that the content was created."

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The same section also states for the newer copyright header's 1st line:

The year is expressed as a single year or a range spanning the year of the very initial assertion and that of the most recent change.

:-)

@sophokles73 sophokles73 force-pushed the merge_parser_into_mapper branch 3 times, most recently from cad7a50 to e51a570 Compare September 12, 2023 09:44
@sophokles73 sophokles73 marked this pull request as ready for review September 12, 2023 09:47
@sophokles73 sophokles73 marked this pull request as draft September 12, 2023 09:48
The readers require a Mapper as well as information provided by the
DBCParser. The Mapper itself also requires information from the parser.

The Mapper has therefore been changed to use the DBCParser class as a
mixin. The readers and the Feeder have been adapted accordingly.
@sophokles73 sophokles73 marked this pull request as ready for review September 12, 2023 11:50
#!/usr/bin/python3

########################################################################
# Copyright (c) 2023 Contributors to the Eclipse Foundation
Copy link
Contributor

@erikbosch erikbosch Sep 12, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Intentional to remove this file? - it was just added, right?

Or no longer needed as functionality integrated into test_readers folder?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's the latter :-)

@erikbosch erikbosch merged commit 9d718b9 into eclipse-kuksa:main Sep 14, 2023
5 checks passed
@erikbosch erikbosch deleted the merge_parser_into_mapper branch October 31, 2024 13:17
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants