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
Motivation / Use Case
Opened after checking with a user on some item issue.
Inability to create a custom weapon with the light property which looks to have been forgotten.
Expected Behavior
We want to have a way for item-builder with type weapon / subtype custom to have a checkbox for toggle of the Light property on the weapon.
Other Information
weapons.cljc -> already hardcodes the light? field for the base weapons, but the schema.clj for weapons doesn't have the boolean.
views.cljs -> Addition of the checkbox here. base-weapon-selector function is where it goes.
events.cljs -> should include the new reg-event-db, similar to the way we operate for the reach? boolean
subs.cljs -> should include the new reg-sub for event sub
magic-item.cljc -> the from-internal-item function should handle the field.
I don't have access to a dev environment for testing, but I'm pretty confident that should do the trick.
In an ideal world we'd have the properties displayed regardless of the selected type and we would have the ability to mock around with them. Which requires a quick rewrite of the views.cljs logic for display.
The text was updated successfully, but these errors were encountered:
Motivation / Use Case
Opened after checking with a user on some item issue.
Inability to create a custom weapon with the light property which looks to have been forgotten.
Expected Behavior
We want to have a way for item-builder with type weapon / subtype custom to have a checkbox for toggle of the Light property on the weapon.
Other Information
light?
field for the base weapons, but the schema.clj for weapons doesn't have the boolean.base-weapon-selector
function is where it goes.reach?
booleanfrom-internal-item
function should handle the field.I don't have access to a dev environment for testing, but I'm pretty confident that should do the trick.
In an ideal world we'd have the properties displayed regardless of the selected type and we would have the ability to mock around with them. Which requires a quick rewrite of the views.cljs logic for display.
The text was updated successfully, but these errors were encountered: