LLM attribute calculation

[andhreljaKern]

This is the Main PR.

Related:

• LLM attribute calculation refinery-submodule-model#151
• LLM attribute calculation #287
• LLM attribute calculation refinery-ac-exec-env#70
• LLM attribute calculation submodule-javascript-functions#14
• LLM attribute calculation refinery-ui#61
• LLM attribute calculation refinery-tokenizer#83
• LLM attribute calculation submodule-react-components#37

[lumburovskalina]

Since this is a Note a suggest that we put into italic

• resolved
• ignored

[lumburovskalina]

If running id field is empty, the button 'Get by running_id' should be disabled

• resolved

[lumburovskalina]

In the LLM playground modal, I would suggest that the 'Use current values for attribute' should be disabled if the 'Test configuartion' is still running (since it takes some time)

• resolved
• ignored

[lumburovskalina]

If you try to change the Dropdown 'Load config template' it doesn't display the correct value

• resolved
• intended

[lumburovskalina]

Should we display this in <pre> tag?(to look more like code)

• resolved
• ignored

---

edit @JWittmeyer:
Added for view button display but not in the shorthand display

[lumburovskalina]

If i create an attribute from different type (ex. Category) and i change the datatype i don't see any of the configuration for the LLM response (only the provider and the api key), and the code is still the same.

We have some logic here that if it's the initial value, so nothing has changes since the creation, the user can still override it,
otherwise it's still possible/clickable but it doesn't make too much sense because the user will loose the data.

In this case we only need the config fields and the code change.

• resolved

---

Edit @JWittmeyer
Disabled the option to switch to LLM Type and vice versa since the attribute needs to be created with a different configuration

[lumburovskalina]

i think the modal can be a bit wider

• resolved
• ignored

[lumburovskalina]

Test configuration and 'Load config template' still possible for usable attributes, i think it should be disabled.

Edit Lina: I noticed that most of the fields are enabled, is that wanted?

• resolved
• ignored

---

Edit Jwittmeyer
Playground removed for useable attributes

[lumburovskalina]

Cursor pointer on disabled option in dropdown

• resolved

---

Edit JWittmeyer
Tooltip cursor overlays. imo best possibility to set to cursor-not-allowed => results in small overleap on edges

Alternative could be cursor default but then the disabled would also be default