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

Remove deprecated flags and properties #21852

Merged
merged 4 commits into from Apr 3, 2023

Conversation

valentinpalkovic
Copy link
Contributor

@valentinpalkovic valentinpalkovic commented Mar 31, 2023

Closes N/A

What I did

Remove deprecated flags and properties.

Checklist

  • Make sure your changes are tested (stories and/or unit, integration, or end-to-end tests)
  • Make sure to add/update documentation regarding your changes
  • If you are deprecating/removing a feature, make sure to update
    MIGRATION.MD

Maintainers

  • If this PR should be tested against many or all sandboxes,
    make sure to add the ci:merged or ci:daily GH label to it.
  • Make sure this PR contains one of the labels below.

["cleanup", "BREAKING CHANGE", "feature request", "bug", "documentation", "maintenance", "dependencies", "other"]

@valentinpalkovic valentinpalkovic added maintenance User-facing maintenance tasks ci:daily Run the CI jobs that normally run in the daily job. labels Mar 31, 2023
@@ -243,19 +243,6 @@ function preparePartialAnnotations<TRenderer extends Renderer>(
initialArgsBeforeEnhancers
);

// Add some of our metadata into parameters as we used to do this in 6.x and users may be relying on it

if (!global.FEATURES?.breakingChangesV7) {
Copy link
Member

Choose a reason for hiding this comment

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

Should this be removed? I wonder if it's needed somehow in case storyStoreV7 is false

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Is breakingChangesV7 not always true in SB 7.0 (or must be)?

Copy link
Member

Choose a reason for hiding this comment

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

@yannbf I don't think it's necessarily to do with ssv7, just an old implementation detail that we used to store these things in parameters. We never told people to read them from there (AFAIK), but we were playing it safe in 6.x.

I think we can definitely drop this code in 7.0, but we may have missed the boat.

Not sure about breakingChangesV7 entirely. Certainly it makes sense to have gotten rid of it (I thought we already did, but it looks like @ndelangen just reversed the default). But other places it has an effect like this I am less sure of.

Copy link
Member

Choose a reason for hiding this comment

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

I'm pretty confident this is just good to merge. We haven't heard anyone at all about this feature flag. We should have removed it prior, but the name is pretty clear in it's intent.

@@ -243,19 +243,6 @@ function preparePartialAnnotations<TRenderer extends Renderer>(
initialArgsBeforeEnhancers
);

// Add some of our metadata into parameters as we used to do this in 6.x and users may be relying on it

if (!global.FEATURES?.breakingChangesV7) {
Copy link
Member

Choose a reason for hiding this comment

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

I'm pretty confident this is just good to merge. We haven't heard anyone at all about this feature flag. We should have removed it prior, but the name is pretty clear in it's intent.

@valentinpalkovic valentinpalkovic merged commit 6644043 into next Apr 3, 2023
18 checks passed
@valentinpalkovic valentinpalkovic deleted the valentin/remove-deprecated-apis branch April 3, 2023 09:17
title = name;
deprecate(
'`showName` is deprecated as `name` will stop having dual purposes in the future. Please specify a `title` in `globalTypes` instead.'
);
} else if (!showName && !icon && !title) {
} else if (!icon && !title) {
Copy link

Choose a reason for hiding this comment

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

This branch never gets executed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci:daily Run the CI jobs that normally run in the daily job. maintenance User-facing maintenance tasks
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants