Give unique colours to products/components

[bendl]

Currently hard-coded to grey/blue.

[smhussain110]

@bendl Maybe create an array of colors and randomly select a color for the product from the array

[smhussain110]

which file is this in? (Sorry but i am new to open source. If you can tell me the file, I can solve this thing)

[bendl]

app/scripts.babel/contentscript.js is the main file for this extension.

We need some kind of lookup table where you put in a the product/component and get a colour back.

I'm thinking if we have an array of colour hex codes, like var colours = ["#aaa", #"bbb", ...]

Then have an array of found products/components strings, like var products = ["tools", "other", ...] (added to like the board_sections are)

Then we look up the index of the current bugs' product/comp string in the products array, giving us an index to use for the colours array.

We then store the colour string at this index in the make_bug_item structure.

Then in board.html we do something like:

class="label" style="background-colour: {{ item.product_colour }}">{{ item.product }

[smhussain110]

@bendl Thanks. Also, when I am uploading the extension on chrome, I get the following error:

Any idea how to resolve this?

[bendl]

Good spot!

I've just added 2 commits (0bfddb6, 952b062) which fixes the bower dependencies!

Update to the latest, and do a bower install in the top directory.

I'll raise an issue about adding better install instructions to the README.md

[smhussain110]

@bendl Once the extension is installed in chrome, are there any test cases I can test?

[smhussain110]

And I was thinking, instead of maintaining 2 arrays, we can just maintain 1 data structure of a map with the key being the product/comp name and value being the color.

[bendl]

Nothing yet regarding proper tests, just looking at public Bugzilla servers like:

• https://sourceware.org/bugzilla/buglist.cgi?component=cli&product=gdb&resolution=---
• https://bugzilla.mozilla.org/buglist.cgi?product=Core&component=History%3A%20Global&resolution=---
• https://sourceware.org/bugzilla/buglist.cgi?component=ada&product=gdb&resolution=---
• https://bugs.llvm.org//buglist.cgi?chfieldfrom=24h
• https://bugzilla.gnome.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=Normal&product=gnome-terminal

[smhussain110]

@bendl I have solved this. Each unique product is given a unique color dynamically.

[smhussain110]

@bendl What about the color of components? Should it be the same as product's color or different?

[bendl]

Thanks @raza15!
I think if we just do products for now, then worry about components for later.
Could you raise a PR please?

[bendl]

PR #11 and #13 solve this issue.

Keeping this open as the current implementation uses randomly generated colours.
I would like to use a known colour array to keep consistency and the chance of getting bad colours from the random colour generator.

Something like bug_color = colours[product_index % num_colours]