Skip to content

Conversation

@anoto-moniz
Copy link
Collaborator

Only product and hierarchical design spaces are allowed as the top-level design space type. Any top-level formulation or data source design spaces that remain on the platform can no longer be read by the SDK. Additionally, support for enumerated design spaces has been dropped entirely. All such design spaces will eventually be removed from the platform.

PR Type:

  • Breaking change (fix or feature that would cause existing functionality to change)
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Maintenance (non-breaking change to assist developers)

Adherence to team decisions

  • I have added tests for 100% coverage
  • I have written Numpy-style docstrings for every method and class.
  • I have communicated the downstream consequences of the PR to others.
  • I have bumped the version in __version__.py

Only product and hierarchical design spaces are allowed as the
top-level design space type. Any top-level formulation or data source
design spaces that remain on the platform can no longer be read by the
SDK. Additionally, support for enumerated design spaces has been dropped
entirely. All such design spaces will eventually be removed from the
platform.
@anoto-moniz anoto-moniz changed the title Restrict top-level design space types. [v4.0] Restrict top-level design space types. Jan 27, 2026
@anoto-moniz anoto-moniz marked this pull request as ready for review January 28, 2026 17:13
@anoto-moniz anoto-moniz requested a review from a team as a code owner January 28, 2026 17:13
Copy link
Collaborator

@kroenlein kroenlein left a comment

Choose a reason for hiding this comment

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

Generally looks good. Only wondering if we've got the proper deprecations in place for retiring the namespaces.

from citrine._serialization import properties
from citrine.informatics.data_sources import DataSource
from citrine.informatics.design_spaces.design_space import DesignSpace
from citrine.informatics.design_spaces.subspace import DesignSubspace
Copy link
Collaborator

Choose a reason for hiding this comment

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

Is this technically a migration? It doesn't look like running

from citrine.informatics.design_spaces.design_space import DesignSpace

currently issues a deprecation warning. Am I missing something?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

The deprecation warning is only issued if the user attempts to read or write any of the deprecated types.

Copy link
Collaborator

@kroenlein kroenlein left a comment

Choose a reason for hiding this comment

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

Seems to cover the bases.

@anoto-moniz anoto-moniz merged commit 47f060e into release/v4.0 Jan 28, 2026
41 checks passed
@anoto-moniz anoto-moniz deleted the feature/restrict-top-level-design-spaces branch January 28, 2026 18:15
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.

3 participants