--- Comment #1 from Thiemo M├Ąttig <> ---
When choosing a property there is a single, pretty simple "wbgetentities" API
call triggered. At the moment I don't see a reason why this should cause a
"substantial" delay other than what an API call usually causes.

The previous autocomplete call ("wbsearchentities") doesn't include the
required information. Example response:
I don't think it's a good idea to change this.

A possible solution would be to use the fetchedEntities local store to avoid
these API calls if the property is already in the store. Currently the API is
always requested and the store is never used (but the API calls result is put
in the store). Not sure if this is a good idea. When will an outdated property
in the store be invalidated?

You are receiving this mail because:
You are on the CC list for the bug.
Wikibugs-l mailing list

Reply via email to