-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] Debug Logs #347
Comments
I don't think it's exactly what you're looking for, but there are logs you can enable that log to console certain events as things are happening. You can enable them via |
@dskuza Is there an update on this? Have you found a way to export the usable exports? I would love to be able to get a hold of exported text run names when having a .riv-file delivered so one can sanity check that the file has been set up correctly. |
@cerupcat @heyrodrigo There is something you can actually try to add to your workflow, but an important note that it's currently a work in progress. Feel free to check out a WIP CLI solution here: https://github.com/rive-app/rive-code-generator-wip/ Right now, there is JSON output support built-in, so you could perhaps do a cli -> json -> Swift flow, or add a custom template for Swift. We plan to work on a more finalized solution, but there are a few upcoming features we need to tackle first. |
That's great. We'll take a look!
ᐧ
…On Mon, Jan 13, 2025 at 9:51 AM David Skuza ***@***.***> wrote:
@cerupcat <https://github.com/cerupcat> @heyrodrigo
<https://github.com/heyrodrigo> There *is* something you can actually try
to add to your workflow, but an important note that it's currently a *work
in progress*. Feel free to check out a WIP CLI solution here:
https://github.com/rive-app/rive-code-generator-wip/
Right now, there is JSON output support built-in, so you could perhaps do
a cli -> json -> Swift flow, *or* add a custom template
<https://github.com/rive-app/rive-code-generator-wip/tree/main> for Swift.
We plan to work on a more finalized solution, but there are a few upcoming
features we need to tackle first.
—
Reply to this email directly, view it on GitHub
<#347 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABR254B5AM6OAFMQQYQWTL2KP4KZAVCNFSM6AAAAABRVF3G36VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOBXG44DQNRWGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@dskuza Wow! That seems super helpful. I will also have a look at it. Thanks for the update. |
I'd love to have a debug option that allows printing all artboard names (and subartboards), assets names, inputs, text runs and their paths, etc.
It's not always obvious what is available or if the riv file is configured correctly. Printing them in code will help ensure the right paths and options are used and help with debugging any issues with layers that may not be exported correctly.
The text was updated successfully, but these errors were encountered: