Main menu

14 Sep 2018

Asset IDs are now optional in project settings

Loco's built-in unique identifiers are now optional. They are enabled by default on all new projects, but you can switch them off via the developer settings. This feature is aimed at developers whose platform does not use a language agnostic key in addition to the source language (e.g. Gettext). See Working without IDs.

With this option disabled you will no longer see any references to Asset IDs in any dashboard interfaces. Loco will also warn you if your assets are not unique by their source text. This makes working with Loco simpler when IDs are superfluous.

Working with individual assets via the API still requires a unique key, so with this options disabled you will see Asset objects returned have an id property which is simply a 24 byte hash. This is guaranteed to be unique, but you cannot modify it. If you require custom or readable identifiers then enable Asset IDs in your project.

Minor API changes

Version 1.0.20 of the API is released. See changelog.

Last updated by