The value is reset to "" when using setState about react-dadata-suggestions

[nobbynobbs]

Hi! I'm not sure, but probably I work wrong with context in callback functions in my component. I'll think about this issue.

[pavelkuligin]

I found workaround already :-)
<DadataSuggestions token={ token } placeholder="Иванов Иван Иванович" query={this.state.query} onChange={(query) => this.setState({query: query}) } service="fio" onSelect={ (suggestion) => { this.setState({person: suggestion} ) } } />

[nobbynobbs]

so can i close the issue?

[pavelkuligin]

I think yes

[SDKiller]

I thimk this should be reopened.

[nobbynobbs]

@SDKiller maybe. But could you explain why?

[SDKiller]

Foe example, I have a priviously stored user address and open form for edit. I cannot even initialize field (underlying text input) with value - component does allow to set it via value. The suggestion above with placeholder is tricky and actually is not suitable. вт, 19 мар. 2019 г., 9:21 Roman <[email protected]>:

…

@SDKiller <https://github.com/SDKiller> maybe. But could you explain why? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#12 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACDSBPn3tSVZkcDwL95FeeBrueCf92CHks5vYIHzgaJpZM4TPnPk> .

[SDKiller]

Hm, I think that issue with "value" is worth opening another issue. вт, 19 мар. 2019 г., 9:21 Roman <[email protected]>:

…

@SDKiller <https://github.com/SDKiller> maybe. But could you explain why? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#12 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACDSBPn3tSVZkcDwL95FeeBrueCf92CHks5vYIHzgaJpZM4TPnPk> .

[nobbynobbs]

@SDKiller

You could use query option to initialize query string, see Address example at https://codesandbox.io/s/p95804280q

I think it fits your case.

[SDKiller]

Thanks for example, if I initialize it via query - I got not editable field, I'll try to find what I'm doing wrong.

[SDKiller]

@nobbynobbs
Could you please suggest, how onSelect to send one more query with unrestricted_value and count 1?
The problem is that suggestions are returned with empty geo_lat and geo_lon.

According to today's answer of dadata support:

Подсказки возвращают координаты после того, как человек выбрал конкретный адрес из списка.

В API это запрос с параметром count = 1. При этом текст запроса должен быть результатом одного из предыдущих запросов (значением поля unrestricted_value). Например:

{ "query": "г Москва, ул Сухонская, д 11", "count": 1 }

[nobbynobbs]

@SDKiller I'm afraid react-dadata-suggestion can't do such query for you. You could make this query manually in onSelect callback with fetch-api or axios.

[SDKiller]

Thanks вт, 19 мар. 2019 г., 15:05 Roman <[email protected]>:

…

@SDKiller <https://github.com/SDKiller> I'm afraid react-dadata-suggestion can't do such query for you. You could make this query manually in onSelect callback with fetch-api or axios. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#12 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACDSBBjssoxFV-gRQ2DHto6amVtLgVFgks5vYNKXgaJpZM4TPnPk> .

[nobbynobbs]

Not at all