best-practise | golang 各种组件的最佳实践，持续更新 | Awesome List library

In an app that's mainly a set of JTables and JTextFields, I tried to make it accessibility with keyboard as well as mouse. My thoughts are on the best way to help the user to navigate around between components using the VK_TAB key.

My first goal was to stop JTables "swallow" the VK_TAB key when the user tries to navigate to a neighbor JTextField. I tried to put together a minimal compilable and runnable example below. I asked about the focussed JTable reacting to VK_ENTER: after that, it would react to VK_TAB by giving focus to the next cell until ESC is pressed.

The runnable example below is the result of what I made of the answers I got. When the code is compiled, row selection mode is active and tab key hops between the text field and the table. When you press Enter, it switches to single editing mode and you can change cell using tab key until esc key is pressed.

The problem I still have is: when you edit a cell and press esc key, the single cell is still selected. Instead, the whole row should be selected. How can I reach that?

Thanks!

This is somewhat of both a best-practise question, and a technical one, and has a bit of context.

The TL-DR: I want to use a single-line-definition macro to create anonymous variable-sized arrays.

Note in my below question, I cannot use gcc extensions - I can only take vanilla C99 for granted.

In my project (a simulation software used by external users), there are several structs with 2D arrays

Whats is considered best-practise when creating topics for Apache Kafka?
Does everyone allow automatic creation of topics or how do you do it? Do you bundle the topic-creation-step with the starting of the kafka-instance?

I have a docker-based Kafka-installation which is gone be used by multiple applications. How can I keep the topic-creation for every application separate from the startup of the Kafka-container?. Looking at Confluents music-demo they create the topics by spinning up a new kafka-image, calling the "create-topic-script" and then leave the container to die. This feels abit "hacky" but maby its the only way?

Regards

I'm developing a VSTS-Extension which will be executable in the contextmenu of a workitem. I need to provide user-level configuration for the action that is performed by the extension (e.g. which external service should be notified, when performing an action). I'll store the data using the Data-Service provided by the API.

Is there a best-practise to make the configuration available to the user (comparable to the configuration of a dashboard-widget)?

I am looking for a best-practise / solution to render responses with different http-response codes than 422 - unprocessable entity.

I have a simple validator:

I want to create an expandable ListView, with a custom ViewCell containing two StackLayouts. The first one would be the header and the second layout would be a children of the first one and show additional details. The idea is that the details layout would be hidden by default, and its visibility would be toggled when its ViewCell container is tapped.

I am not sure how to properly achieve this in the Xamarin.Forms environment, and have not found any truly helpful resource. I can imagine one solution which would involve creating a custom sub-class of ViewCell; or another in which I would add a visibility attribute to each item of my ListView.itemsSource through a ViewModel.
What is consider best-practise in that case, and how to achieve this in Xamarin.Forms?

Below is a XAML outline of what I aim to create: