asana.CreateProject (patch update) Color Palette not showing colors

[sayam-nasir]

Problem 1
The initial issue was that the color palette in the Asana Create Project component displayed Asana’s color names (e.g., "dark-pink") but these names were not valid CSS color values. This caused the color picker in the UI to not display colors correctly, as it could not interpret non-standard CSS values like "dark-pink".

Problem 2
some components have wrong description that can cause confusion between action and trigger

Fix:
Updated the color palette to use valid hex codes for the color options instead of Asana’s internal color names. The color names were still required by the Asana API, so I introduced a mapping between hex values and Asana color names. The UI now displays hex values, and when submitting the project, the hex value is mapped back to the corresponding Asana color name before being sent to the API. This ensures both proper color display in the UI and compatibility with Asana’s API.

Updated the verbs of the descriptions of action components

[vtalas]

the inspector is generated dynamically due to this color palette inputs, is that right?
is it really needed? it's only converting hard-coded asanaColorMap to another format (key: value -> value:key) why it's not in the {value: hex, content: "name"} directly in the component.json?

it could be reasonable if the asanaColorMap is somehow configurable.

BTW you don't need to make the whole inspector dynamic because of one input, you can generate inspector field separately, like it's here:

appmixer-connectors/src/appmixer/utils/forms/FormTrigger/component.json

Line 22 in 73c79f4

"data": { "properties": { "generateInspector": true } }

[sayam-nasir]

@vtalas youre right,
I will just take the input from the user, keep inspector in component.json. Create a mapper in CreateProject.js that will map user's input to asana specific color names and send to the API that will be cleaner simpler solution