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 use of non-existent WithRegistrySetup.features prop #9115

Closed
2 tasks done
techanvil opened this issue Aug 1, 2024 · 4 comments
Closed
2 tasks done

Remove use of non-existent WithRegistrySetup.features prop #9115

techanvil opened this issue Aug 1, 2024 · 4 comments
Labels
P2 Low priority Sp Wk 2 Issues to be completed in the second week of the assigned sprint Team M Issues for Squad 2 Type: Infrastructure Engineering infrastructure & tooling

Comments

@techanvil
Copy link
Collaborator

techanvil commented Aug 1, 2024

Feature Description

A number of stories have been implemented which pass the features prop to the WithRegistrySetup component. However, the component doesn't have this prop and it's ignored.

The stories are working as expected because the features prop is provided via parameters.

For example:

PaxConnected.parameters = {
features: [ 'adsPax' ],
};
PaxConnected.decorators = [
( Story, { parameters } ) => {
const setupRegistry = ( registry ) => {
// Unset the value set in the prrevious scenario.
registry.dispatch( MODULES_ADS ).setConversionID( null );
registry.dispatch( MODULES_ADS ).receiveGetSettings( {
paxConversionID: 'AW-54321',
extCustomerID: 'C-872756827HGFSD',
} );
};
return (
<WithRegistrySetup
func={ setupRegistry }
features={ parameters.features || [] }
>
<Story />
</WithRegistrySetup>
);
},
];

Note how WithRegistrySetup doesn't have the features prop:

function WithRegistrySetup( { func, children } ) {


Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

  • Stories using WithRegistrySetup should not attempt to pass the features prop to it.

Implementation Brief

Test Coverage

  • Confirm VRTs still pass and components which require feature flags still render in storybook. Feature flags should be passed on the main story definition.

QA Brief

Refer the storybook and ensure that following stories are rendering properly and as expected.

Changelog entry

  • Remove the use of the non-existent features prop in stories using the WithRegistrySetup component.
@techanvil techanvil added P2 Low priority Type: Infrastructure Engineering infrastructure & tooling labels Aug 1, 2024
@benbowler benbowler assigned benbowler and unassigned benbowler Sep 17, 2024
@eugene-manuilov eugene-manuilov self-assigned this Sep 18, 2024
@eugene-manuilov
Copy link
Collaborator

IB ✔️

@eugene-manuilov eugene-manuilov removed their assignment Sep 18, 2024
@ivonac4 ivonac4 added Team M Issues for Squad 2 Sp Wk 2 Issues to be completed in the second week of the assigned sprint labels Sep 24, 2024
@ankitrox ankitrox self-assigned this Sep 25, 2024
@ankitrox ankitrox removed their assignment Sep 26, 2024
@hussain-t hussain-t self-assigned this Sep 26, 2024
@hussain-t
Copy link
Collaborator

Hi @ankitrox, could you please provide the links to the stories to be verified in the QAB? Thanks!

@hussain-t hussain-t assigned ankitrox and unassigned hussain-t Sep 27, 2024
@ankitrox ankitrox removed their assignment Sep 30, 2024
@ankitrox
Copy link
Collaborator

Thanks @hussain-t

I have added links to those stories.

@mohitwp
Copy link
Collaborator

mohitwp commented Oct 1, 2024

QA Update ✅

@tofumatt tofumatt closed this as completed Oct 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 Low priority Sp Wk 2 Issues to be completed in the second week of the assigned sprint Team M Issues for Squad 2 Type: Infrastructure Engineering infrastructure & tooling
Projects
None yet
Development

No branches or pull requests

8 participants