You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Given that iD loads the most recent version of the tagging presets and that strings/translations are fetched separately from the presets data. This is in general a good think. But when a new version is released, it could be the case that a browser (or a CDN) has some of these files still cached (at the state of an older version) and fetches the remaining file freshly (at the state of the new version). This can lead to a situation where the files don't match properly, leading to symptoms like missing labels of new presets and fields.
In order to avoid this, iD should fetch the exact version of the id-tagging-schema first, and then fetch all data files with the exact full version. This will ensure that the versions of the files always are identical.
The text was updated successfully, but these errors were encountered:
Noticed this bug. name-suggestion-index etc. is being fetched from a hardcoded url from cdn.jsdelivr.net like https://cdn.jsdelivr.net/npm/name-suggestion-index@${vMinor}/dist/nsi.min.json. name-suggestion-index is constantly being updated and any new tagging presets won't be reflected in iD until you clear the cache or the cache expires.
Given that iD loads the most recent version of the tagging presets and that strings/translations are fetched separately from the presets data. This is in general a good think. But when a new version is released, it could be the case that a browser (or a CDN) has some of these files still cached (at the state of an older version) and fetches the remaining file freshly (at the state of the new version). This can lead to a situation where the files don't match properly, leading to symptoms like missing labels of new presets and fields.
In order to avoid this, iD should fetch the exact version of the id-tagging-schema first, and then fetch all data files with the exact full version. This will ensure that the versions of the files always are identical.
The text was updated successfully, but these errors were encountered: