To have a more dynamic approach for setting choice field values and update these in the site generation process, it would be nice to have support for ID and Title.
{"title":"Multi-select with ID","name":"choiceId","type":"choice","choices":[{"id":1,"title":"Choice 1"},{"id":"2","title":"Choice 2"},{"id":"3","title":"Choice 3"}],"multiSelect":true}
The user can choose if they want to use a string or { id: string; title: string} object.
To have a more dynamic approach for setting choice field values and update these in the site generation process, it would be nice to have support for ID and Title.
```json
{
"title": "Multi-select with ID",
"name": "choiceId",
"type": "choice",
"choices": [
{ "id": 1, "title": "Choice 1" },
{ "id": "2", "title": "Choice 2" },
{ "id": "3", "title": "Choice 3" }
],
"multiSelect": true
}
```
The user can choose if they want to use a `string` or `{ id: string; title: string}` object.
<!-- github-sync-id:1011822761 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
To have a more dynamic approach for setting choice field values and update these in the site generation process, it would be nice to have support for ID and Title.
The user can choose if they want to use a
stringor{ id: string; title: string}object.