Removing meta div from display and custom css

[ines (Ines Montani)]

At the moment no, sorry. The "card_css" is really just an object that is passed in as the container's "style" attribute. So you can think of it as:

<div style={card_css} />
<div style={{ color: 'red'}} />

So if you want fully custom and nested style overrides, the best solution for now would probably be to add a <style> tag to the index.html.

@alonisser

Also are the non human readable css classes generated for every prodigy version or consistent?

They're auto-generated, so we couldn't guarantee this. However, I'm open to adding more human-readable static class names to elements if you have a suggestion for what you (and potentially others) might want to customise. I also want to be adding more identifiers for recipes, views and a "global_css" setting for consistency. I wrote up some of the ideas in my comment here the other day:

Precision image annotation

That’s a good idea! We could do something like .prodigy-view-ner, .prodigy-view-choice etc. I do see the point for custom identifiers for custom recipes, though – but maybe we could expose the recipe name separately, like data-prodigy-recipe="ner.teach"? In addition, some more containers can get human-readable names, like .prodigy-buttons. And just like the "card_css" setting, we could then have a "global_css" setting that would let you add any other customisations you need. Okay, so what I …