Mirjam Aulbach

# Layout  ## To clarify - we've a list of default environments and admins can create custom environments. It's unclear how to apply colour coding for that. - used...

feat(coral): Topic name with prefix/suffix in forms

4

# Descriptions When creating a topic, there can be rules for the topic name, e.g. to contain one of list of provided prefix / suffix or a combination of them....

# What happened? e.g. in connector or topic, we have now 3 complex components handling data loading, data setting and a form for creating, editing and promoting. These big component...

# What happened? We started adding a link to our new docs and we should see if there are more places where this is useful. One example is in our...

# What happened? Our focus styles are not working on a blue backround (since the focus outline IS blue) and it's also not very useful for a blue button (it...

# What happened? `preview` uses the remote-api mode, but that does not reflect the build 1:1 (for example, feature flags are true here) We probably want to have better options...

- add documentation about approach with custom setup/teardown in FE tests

💭 Rethink validation pattern for names

5

Issue was raised her in regards to team contact person: #577 # Description We've occurrences of the concept of a name (not "username"): - `KwTenantModel` `contactPerson` - `TeamModel` `contactPerson` The...

🪸 Check for additional eslint rules we want to use

1

During the last PRs we already noticed that there are some eslint rules we may want to add, e.g. [here](https://github.com/aiven/klaw/pull/205#discussion_r1021472885). The ticket is a reminder to revisit the topic and...

❓ specify more commit prefixes

2

## Background We're using [Conventional Commits](https://www.conventionalcommits.org/) and these prefixed commits can help us automatically generate changelogs. **Currently we're explicitly using:** - `fix` - `feat` - `docs` - `refactor` In the...