> For the complete documentation index, see [llms.txt](https://salvatos.gitbook.io/kanka-cookbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://salvatos.gitbook.io/kanka-cookbook/plugin-creators/javascript-in-character-sheets/exposing-properties-and-other-entry-information.md). # Exposing properties and other entry information ### entityData With Kanka 2.4, a partial JavaScript dump was added for properties and a handful of other information. As of 2.7, this object now includes most of the entry’s information relevant to a character sheet, with the notable exception of abilities. You can access it via the `entityData` object, which contains the following fields (further detailed on the [official Helper page](https://marketplace.kanka.io/helpers/template-html#javascript)): {% code title="console.log(entityData)" overflow="wrap" %} ```javascript { "name": "...", "is_private": true|false, "type": { ... }, "attributes": { ... }, "tags": [ ... ], "type_field": "...", "is_dead": true|false, // Characters and Creatures only "is_extinct": true|false, // Races and Creatures only "is_completed": true|false, // Quests only "is_defunct": true|false, // Organizations only "is_destroyed": true|false, // Locations only // The rest are only included for Character entries: "gender": "...", "pronouns": "...", "title": "...", "age": "...", "traits": [ ... ], // and appearances "races": [ ... ], "families": [ ... ], "location": { ... } } ``` {% endcode %} {% hint style="warning" %} Note that the property names used by `entityData` are "sluggified" and don’t match their Blade counterparts when it comes to capitalization, which can make interactions between the two languages difficult. On the other hand, it makes it possible to interact with properties whose name is invalid in Blade, for example those that contain special characters, as long as you know their corresponding slug. {% endhint %} ### Axios API Kanka 2.7 introduced tools to access the API via `axios` methods that interact with an entry’s properties **and** abilities. This allows us to generate a far more thorough property dump (including, for instance, property types and their pinned status) with names that match those used in Blade, as well as a detailed dump of ability information. However, because axios is only initialized after the page is fully loaded, unlike our character sheet scripts, `window.onload` is necessary to defer execution until axios is ready. Any processing that relies on the property/ability dumps must therefore also be deferred. Since you have to wait until the page finishes loading to make the API request, *then* wait for the data to be returned by the API, this introduces a significant delay to your data processing. If you try building an empty layout in Blade and filling it with content using axios-provided data in JavaScript, you will see that it can take more than a second before your layout gets populated, resulting in a poor user experience. Therefore, it is advisable to do any time-sensitive initial processing and content-building with `entityData` or Blade – though again, since property names differ between `entityData` and the API, you have to be vigilant about your references, and cross-references between the two are more or less impossible unless you are targeting specific properties for which you know the exact form of both slugs (forget running a `forEach` in one using properties passed by the other!). All of that said, here is some boilerplate that will fetch properties and abilities from the API, format the former to match Blade variable names, and either run any API-dependent code or log an error if something goes wrong. {% code overflow="wrap" lineNumbers="true" %} ```javascript function dumpAttributes (resp, dump = {}) { // Sanitize property names for PHP, removing [range] if applicable, to match Blade variables resp.forEach(obj => { dump[obj.name.replace(/\[range:.*\]|[^a-zA-Z0-9_\x80-\xff]/g, "")] = obj; }); return dump; } window.onload = (event) => { // Collect properties from the API axios.get(attributeApis.all.url).then(res => { window.attributes = dumpAttributes(res.data.data); console.table(attributes); // optional, useful for debugging /* Call any functions that require the dump here */ }).catch(err => { console.error("Failed to create attribute dump"); }); // Collect abilities from the API axios.get(abilityApis.all.url).then(res => { window.abilities = res.data.data; console.table(abilities); // optional, useful for debugging /* Call any functions that require the dump here */ }).catch(err => { console.error("Failed to create ability dump"); }); }; ``` {% endcode %} Each property value can then be accessed with a simple `attributes.slug.value`, where `slug` matches the property’s corresponding Blade variable: {% code overflow="wrap" %} ```javascript window.alert("Welcome to " + attributes.CharacterName.value + "’s character sheet!"); ``` {% endcode %} {% hint style="warning" %} Remember: `entityData` properties are all lower-case and can be accessed directly. API properties are case-sensitive and have several properties, so you need to specify `.value` to get the value. `entityData.attributes.charactername` = `attributes.CharacterName.value`. {% endhint %} Several other details are available via `attributes.slug`, beyond what is accessible in Blade; for example: {% code overflow="wrap" %} ```json { "id": 6640309, "name": "Multiclass Domain[range:Arcana,Blade,Bone,Codex,Grace,Midnight,Sage,Splendor,Valor]", // unparsed string "name_raw": "Multiclass Domain[range:Arcana,Blade,Bone,Codex,Grace,Midnight,Sage,Splendor,Valor]", // unparsed string (no difference as far as I can tell) "value": '3