Skip to content

Presentation class inherits directly from Base #3543

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

Merged
merged 2 commits into from
Oct 26, 2024

Conversation

amolenaar
Copy link
Member

@amolenaar amolenaar commented Oct 19, 2024

This PR builds on #3541.

PR Type

What kind of change does this PR introduce?

  • Bug fix
  • Feature
  • Chore (refactoring, formatting, local variables, other cleanup)
  • Documentation content changes

What is the current behavior?

Presentation inherited from Element, which provided it with features it would never need, such as a name, ownership.

Issue Number: N/A

What is the new behavior?

Presentation is now derived directly from Base. This makes it clear that this kind of element is different from the modeling language base type Element.

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

  • Documentation improvements

Presentations have no name of their own.
@github-actions github-actions bot added the python Pull requests that update Python code label Oct 19, 2024
@amolenaar amolenaar requested a review from danyeaw October 19, 2024 14:59
Base automatically changed from revert-types-to-core to save-model-namespace October 26, 2024 19:24
Copy link
Member

@danyeaw danyeaw left a comment

Choose a reason for hiding this comment

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

Thanks @amolenaar!

@danyeaw danyeaw added chore Maintenance related PR and removed python Pull requests that update Python code documentation labels Oct 26, 2024
@danyeaw danyeaw merged commit 1cd7680 into save-model-namespace Oct 26, 2024
5 checks passed
@danyeaw danyeaw deleted the presentation-base branch October 26, 2024 19:36
@amolenaar
Copy link
Member Author

@danyeaw I still have to adress your comments in #3531.

@danyeaw
Copy link
Member

danyeaw commented Oct 26, 2024

@amolenaar Whoops, did I merge these out of order?

@amolenaar
Copy link
Member Author

No, they're now part of that pr. I addressed your comments and fixed the merge conflict. It should be good to go, now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore Maintenance related PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants