I get tons of rive files with no or very little documentation and then I bang my head on typos, missed state-machines, input, dynamic text names. How does one know for a given rive file, what are the state-machines, inputs (along with its type), listeners, events, and dynamic-text-runs using code.
Provide a Repro
A random persons send you a random Rive file and requests you to manipulate it (state-machines, dynamic-text, events and so on). You get the file import it in your IDE and now you have no clue on what is the code-interface coz you don't know the names or the names shred/documented had typos. It never works and you bang your head, because you mis-spelled something or you don't even know the name of that-something.
Source .riv/.rev file
<--
download any random rive file which has tons of inputs, dynamic texts etc.-->
Expected behavior
User should be able to at least "Print" / "Console.log" all the inputs, artboards, timelines, state-machines, events and so on.
Screenshots
N/A
Device & Versions (please complete the following information)
All
Additional context
In simple words users want to see what are the available node-names for code-interface for a given rive file.
Description
I get tons of rive files with no or very little documentation and then I bang my head on typos, missed state-machines, input, dynamic text names. How does one know for a given rive file, what are the state-machines, inputs (along with its type), listeners, events, and dynamic-text-runs using code.
Provide a Repro
A random persons send you a random Rive file and requests you to manipulate it (state-machines, dynamic-text, events and so on). You get the file import it in your IDE and now you have no clue on what is the code-interface coz you don't know the names or the names shred/documented had typos. It never works and you bang your head, because you mis-spelled something or you don't even know the name of that-something.
Source
.riv/.revfile<-- download any random rive file which has tons of inputs, dynamic texts etc.-->
Expected behavior
User should be able to at least "Print" / "Console.log" all the inputs, artboards, timelines, state-machines, events and so on.
Screenshots
N/A
Device & Versions (please complete the following information)
All
Additional context
In simple words users want to see what are the available node-names for code-interface for a given rive file.