Skip to content
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

Open
cerupcat opened this issue Nov 12, 2024 · 5 comments
Open

[Feature Request] Debug Logs #347

cerupcat opened this issue Nov 12, 2024 · 5 comments

Comments

@cerupcat
Copy link

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.

@dskuza
Copy link
Collaborator

dskuza commented Nov 19, 2024

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 RiveLogger.isEnabled = true. We've been talking internally about the "best" way to export the usable exports from .riv files; there are a few options, so we're investigating a few to see what works well cross-platform.

@heyrodrigo
Copy link

@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.

@dskuza
Copy link
Collaborator

dskuza commented Jan 13, 2025

@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.

@cerupcat
Copy link
Author

cerupcat commented Jan 13, 2025 via email

@heyrodrigo
Copy link

@dskuza Wow! That seems super helpful. I will also have a look at it. Thanks for the update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants