refactor: replace tag components across how-to and research #3367

[simontree]

PR Checklist

• - Commit messages are descriptive, it will be used in our Release Notes

PR Type

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Developer experience (improves developer workflows for contributing to the project)

Description

Refactoring of components using tagList as described in the issues ticket.

Git Issues

Closes #3357

What happens next?

Thanks for the contribution! We try to make sure all PRs are reviewed ahead of our monthly maintainers call (first Monday of the month)

If the PR is working as intended it'll be merged and included in the next platform release, if not changes will be requested and re-reviewed once updated.

If you need more immediate feedback you can try reaching out on Discord in the Community Platform development channel.

[benfurber]

@simontree - Nice work, thank you. I can see the unit tests are failing. From a quick look, it could well be because of the TagList component. A guard clause at the start of the component might do the trick e.g.:

export const TagList = ({ tags }: IProps) => {
  if (!tags) return 

  const { allTagsByKey } = useCommonStores().stores.tagsStore

[benfurber]

Hey @simontree. How are you getting on?

[simontree]

Hey @simontree. How are you getting on?

Hey @benfurber, I am working on my bachelor thesis right now - but from next week on I am done with that & try to finish both of my PRs