Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A bag of small random fixes #339

Merged
merged 7 commits into from
Sep 9, 2024
Merged

Conversation

andlaus
Copy link
Collaborator

@andlaus andlaus commented Sep 9, 2024

This PR contains a set of fixes for a few random annoying issues which I've recently encountered. I decided that they are big enough to warrant a separate PR instead of doing them as "drive bys" for other pull requests.

Andreas Lauser <[email protected]>, on behalf of MBition GmbH.
Provider Information

Signed-off-by: Andreas Lauser <[email protected]>
Signed-off-by: Michael Hahn <[email protected]>
older versions of `mypy` complain about this, but interestingly enough
not newer ones...

Signed-off-by: Andreas Lauser <[email protected]>
Signed-off-by: Michael Hahn <[email protected]>
@andlaus andlaus requested a review from kayoub5 September 9, 2024 15:21
andlaus and others added 4 commits September 9, 2024 17:26
Since `COMPU-PHYS-TO-INTERNAL` and `COMPU-INTERNAL-TO-PHYS` are
conceptually inverse functions of each other, the set objects which
they are mapping to each other are swapped. i.e., the "source" type of
`COMPU-PHYS-TO-INTERNAL` is the physical type of the compu method
while `COMPU-INTERNAL-TO-PHYS` it is the opposite. Let's avoid this
confusion and use the proper mathematical terms 'domain' (for the set
of objects which a function maps from) and 'range' (for the set of
objects which a function maps to). Note that the domain and the range
are swapped for `COMPU-PHYS-TO-INTERNAL` and `COMPU-INTERNALTO-PHYS`.

Signed-off-by: Andreas Lauser <[email protected]>
Signed-off-by: Michael Hahn <[email protected]>
if a text identifier is specified, the jinja keeps a single space
before the `TI` attribute, i.e., the output data stays valid.

Signed-off-by: Andreas Lauser <[email protected]>
Signed-off-by: Michael Hahn <[email protected]>
Signed-off-by: Andreas Lauser <[email protected]>
Signed-off-by: Michael Hahn <[email protected]>
this is not too useful IMO, but the spec says `index.xml` (contained
by `.pdx` files) should contain a non-empty `SHORT-NAME` tag...

Signed-off-by: Andreas Lauser <[email protected]>
Signed-off-by: Michael Hahn <[email protected]>
internal_type: DataType
physical_type: DataType
domain_type: DataType
range_type: DataType
Copy link
Collaborator

Choose a reason for hiding this comment

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

document the properties, or their meaning gets lost in the commit message

Copy link
Collaborator

Choose a reason for hiding this comment

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

other than this, LGTM

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

good point. fixed, thanks: 1f39cf9

as usual, thanks [at]kayoub5!

Signed-off-by: Andreas Lauser <[email protected]>
Signed-off-by: Michael Hahn <[email protected]>
@andlaus andlaus merged commit b18d046 into mercedes-benz:main Sep 9, 2024
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants