feat(coral): Suggestions to autocomplete keys and values when writing configurations
- Vorherrschende Sprache
- Java
- Sterne
- 195
- Forks
- 77
- Ø Merge
- 8 T. 9 Std.
- Gemergte PRs (30 T.)
- 1
Beschreibung
# What is currently missing?
When writing connector or advanced configuration we don't provide context to user on what is available.
# How could this be improved?
Offer suggestions to autocomplete keys, values, topic or connector class names (or anything else that is feasible) including documentation when writing configuration.

Worth noting here is that the fields change based on the connector.class. In this case, suggest keys supported by the connector.class
# Is this a feature you would work on yourself?
Sure, but need to figure out what information we can get. It would be best to get the available configuration through api from backend.
For example, for all keys, we would need to know all the supported fields per connector class and get the key/value/documentation information from api:
```
[
{
"connector.class": "class-1",
"options": [
{ "name": "tasks.max", type: "int", documentation: "", enum?: [""] },
....
],
},
...
]
```
topic names should be doable already.
* [ ] I plan to open a pull request for this feature
Beitragsleitfaden
Bewertung
Dieses Issue wurde noch nicht bewertet.