Perspective Component Style

I would like to give the possibility to customize a component using the style property.

"style":{ "$ref":"urn:ignition-schema:schemas/style-properties.schema.json" }

What is the best way to use this style object in the front-end ? (in tsx)

Those styles will be added through the emit(). in the upper level of your component. Which you already should be using for positoning ect.

1 Like

Thanks a lot @victordcq !
I didn’t think the style tag would be enough, I probably still lack knowledge in react.

It seems that I have to add “psc-” in front of all the classes defined in the project styles in order for them to be taken into account.

Yes if you dont use the emit you will have to parse it yourself.
Its not necessarily related to react, but more to how igntion passes along the properties^^

You will have to use the emit() somewhere though (best in the top level div), else your component will not be positioned correctly in the view.

this is what it says in the example

I feel like I need to parse the class list in any case.

{…this.props.emit({classes: ans[“style”][“classes”]})} // Doesn’t work

“classes” expects an array while the classes coming from the props of the component ans[“style”][“classes”] are a String.

Your upper div should contain {...this.props.emit()}, because the position data is in there.
The classesNames defined in the will also automatically be provided through there.

i believe this will also work for the other styles

it proabbly should look like this

or maybe

<div {...this.props.emit()}>
    //annotions map ...
    <div  {...ans.emit()}>

I just test with {…this.props.emit()} on the main div and now I completely understand the concept you just explained.
But as you have understood, I am in a particular case where we have a list of items (so a list of style too).

I just tested {…ans.emit()} and {…} but it does not work.
It raises the following error: TypeError: is not a function / TypeError: ans.emit is not a function


can you show me how you defined the

for the annotations?

Please post code in a code block, not as a screen shot. Especially with a black background (hard on the eyes of anyone older than 40 or so).

1 Like

I thought found solution but it was a mistake…
This is what my property structure looks like :

Would be neat if there was a plugin for discourse to allow for screenshots to automatically be converted into formatted text snippets, with the ability to either see the automatically generated text or the provided screenshot.

I’d rather the editor just detect screenshots of text and put a suggestion on the preview pane. Something like “This image appears to be mostly text. You should post the text instead, in a code block if necessary, to avoid being called out by irate interlocutors.”


Heh it seems the props are turned into objects the moment you go deeper into them. causing them to loose the emit function…
And it turns out you dont really want to use the emit anyways since there the position props are in it too, which is not what you want for a list.

So instead you could do something like this, but i guess your methode is just as fine (aslong as you have the base emit in the upper level)

<div {...this.props.emit()}>
      const styleProps =
              .readStyle("configuration[" + cnfId+ "].annotations[" + ansId + "].style")
      return <div  className={styleProps.className + " annotation-markers"} style={}>{ans["value"]} </div>
1 Like

I think you are absolutely right and your proposal works very well !
I finally decided to use this solution to use the emitter.

<div {...emit()}>
	{/* tslint:disable-next-line:jsx-no-multiline-js */}
	{ => {
		return cnf["annotations"].map((ans: Object) => {
			const styleProps = PropertyTree.parseStyle(ans["style"])

			// tslint:disable-next-line:jsx-key
			return <div id={ans["id"]} {...emit(styleProps.toEmitProps())}>{ans["value"]}</div>;

Thanks again @victordcq for all the time you took to help me !

1 Like

heh thats a good one, better than my answer^^