in addition to being paired with a vector of values delimited by screen widths to support responsive layouts, attributes should also be able to accept a mapping of values that will change based on the predefined states of a component.
this may not be an ideal long-term solution: overloading vectors and maps for this purpose, while syntactically convenient, is arguably semantically abusive. it may be worth considering custom types instead.
in addition to being paired with a vector of values delimited by screen widths to support responsive layouts, attributes should also be able to accept a mapping of values that will change based on the predefined states of a component.
this may not be an ideal long-term solution: overloading vectors and maps for this purpose, while syntactically convenient, is arguably semantically abusive. it may be worth considering custom types instead.