Replies: 3 comments 4 replies
-
Thanks for raising this.
So for me, I am OK with option 2 and option 4 :)) From my side, I was thinking 🤔 |
Beta Was this translation helpful? Give feedback.
-
I think options 2 and 4 are the most appropriate. For option 2 (duplicating the tool/service on the radar for each relevant dimension) we preserve the full JSON representation and provide a more complete view of each tool. However, we should add a visual style or a “multi-dimensional” label to clearly indicate that these are duplicates of the same tool (to see if that’s feasible on the current radar setup ?). For option 4 (splitting tools/services into submodules) it maximizes visibility and provides more detailed information on the radar. However, it does require additional consideration, especially for tools where submodules are not clearly defined (expl: if a submodule could also enhance more than one dimension, how should that be handled?) |
Beta Was this translation helpful? Give feedback.
-
Thank you for your comments.
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
The technical developments that allow us to use the quality dimensions as segments of the TechRadar have raised a question for which I’d like your opinion.
Our JSON schema allows tools and services to have multiple
qualityDimension
. However, this isn’t possible in the markdown representation used by the Radar for graphical display.Please let me know your thoughts on this.
0 votes ·
Beta Was this translation helpful? Give feedback.
All reactions