You should use the dev tools in your browser to figure this out. In the sources tab of dev tools, turn on “break on caught error” and see if you can get to the line that looks like that one it printed out in that message. That’ll help you figure out what code is breaking.
Presumably it’s in the dynamic importer plugin, so you could just look in that plugin’s code on the site, and see where that is, and find out what’s gone wrong that way.
@perchance@lemmy.world Man, I wish the screenshots worked. “Here’s my completely empty tutorial page 👍👍🤓”
😂
Ah I see… I only used hash because that’s what the address changes to when you click a tab. You can now use history.replaceState() to change the params in the address bar, if you want to change things to use that instead, maybe?
@VioneT@lemmy.world I understand you maintain the hub?
Cool, thanks 👍
Okay, so you don’t need to put the code into the HTML as well; you can remove that.
The error box tells you there’s an error with [output]. Which you don’t need at all, so you can remove that from the HTML panel and that error will go away.
The wheelOptions object in the perchance panel ends immediately (with no items or properties or settings)… because the next line lineWidth=10 is not indented. So it just starts its own new list called lineWidth=10. That’s not what you want.
Indent it, and now that is a property of wheelOptions, and the rest of the items below it will be as well. So when wheelOptions is sent into that makeWheel() function it will use those settings to build the wheel.
What does that even do? I’ve never seen code like that in perchance documentation or anywhere else. Does that actually do anything?
Got a link to a generator that uses this code? It might stop the error but not actually do anything; if [input.Lighting] != "": would just be an item within the Line-Art style list. 🤷
If you could give me a link to the code I gave not working, I could look at the error and figure it out for you.
lol
Oh lol ;p
Hehe… Thanks.
Yeah I don’t know what should be at the “end.” There’s just no more to the plugin to explain. So 🤷
Does it need a Love you xoxo?
@perchance@lemmy.world Yeeeeeeeeeeah… so that wasn’t actually working. It does work when direct from a script. Doesn’t work when from an event, because it’s no longer processing the script tag itself. 🤦
I’ve resorted to requiring the plugin user to tell me if the HTML should be escaped or not. But obviously… that suuuuuucks.
Really hoping for some way of knowing if a code block is being processed or not. Or a way of setting my own “evaluateItem” so I can override the processing. Or a way of telling perchance not to forcibly evaluate an object.
This issue is driving me crazy every time I find a new edge case or some hacky workaround turns out not to be working after all.
Something’s definitely borked with the screenshoter. This doesn’t have a screenshot either 🤷
(Psst… by the way, your demo for that page errors for me.)
@perchance@lemmy.world I know you’ve parked the /api-plugin name. If you want to point it to my plugin, or change my plugin’s name to be that or whatever, you’re welcome to. Message me about it if you like.
You’re using the t2i framework, I’m guessing? I don’t use it myself, but having a look at it… Maybe this will work: [this.getParent.Environment._element.value]… something like that. That will find the actual select box in the page and and get its current value. Maybe.
Tip: If you put ``` before and after you code in a post/comment here, it will keep its line breaks etc. and look like the code you pasted in. You can use the preview button to preview if it’s working.
Some APIs have status: “success”, others use success: true. Which is… a thing. 😂
Might be a good idea to have both on all of them? Or pick on and make sure they all use it. Then people (meaning me) wouldn’t have to check for both or get confused about which is which.
@perchance@lemmy.world