Skip to content

Refactor 24 trend new - #216

Open
gonzalezma wants to merge 1 commit into
refactor_24from
refactor_24_trend_new
Open

Refactor 24 trend new#216
gonzalezma wants to merge 1 commit into
refactor_24from
refactor_24_trend_new

Conversation

@gonzalezma

Copy link
Copy Markdown

New trend branch created directly from refactor_24. It contains the changes done in March to the original Trend class to allow defining an arbitrary number of axes in the Trend (populated either from the metadata or by giving a list of numerical values) and new tests, as well as some improvements to address the review comments in the previous refactor_24_trend branch.

@gonzalezma
gonzalezma requested a review from krzywon June 11, 2026 15:18
@krzywon
krzywon changed the base branch from master to refactor_24 June 11, 2026 15:55
@krzywon
krzywon changed the base branch from refactor_24 to master June 11, 2026 15:55
@krzywon
krzywon changed the base branch from master to refactor_24 June 11, 2026 15:55
@krzywon

krzywon commented Jun 11, 2026

Copy link
Copy Markdown
Collaborator

Yes, this is much easier to review. I'll close the other PR in favor of this one.

@krzywon krzywon mentioned this pull request Jun 11, 2026

@krzywon krzywon left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

This looks like it takes into multi-dimensional trends properly. Look at the one comment I made to be sure that doesn't affect functionality before merging.

Comment thread sasdata/metadata.py
if type(self.contents) is str:
children = f"\n{header} {self.contents}"
else:
match self.contents:

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

This match isn't completely equivalent to the previous if/else block. If self.contents == "", the new check will give children == f"\n{header} {self.contents}", but gave an empty string before.

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