Patterns / Resuable Blocks and the technical debt

[talldan]

What problem does this address?

After the rename of Reusable Blocks to Patterns in the UI, there's now quite a bit of technical debt in the codebase.

Some newer features have adopted the 'Patterns' naming within code, while older features still use the 'Reusable Blocks' terminology.

This includes:

• A 'reusable blocks' package, which coexists alongside a 'patterns' package.
• Comments across the codebase referring to the feature as reusable blocks.
• Private and public APIs using the Reusable Blocks naming.

What is your proposed solution?

Private APIs can be renamed.

I think it's worth assessing on a case-by-case basis whether public APIs should be deprecated/renamed to patterns. Or alternatively there may be betters way to achieve what the API does.

In some cases, like the 'reusable blocks' package, it's continued existence might be confusing for developers. That package also seems to have some unused functionality (the redux store), and other than that it only exports one component, so it might be a good option to move functionality over to the patterns package and deprecate the package.