Calling Developers!
We are reenergizing our code contribution process! Learn More

What are the Slack Archives?

It’s a history of our time together in the Slack Community! There’s a ton of knowledge in here, so feel free to search through the archives for a possible answer to your question.

Because this space is not active, you won’t be able to create a new post or comment here. If you have a question or want to start a discussion about something, head over to our categories and pick one to post in! You can always refer back to a post from Slack Archives if needed; just copy the link to use it as a reference..

Hey Spryks…! What’s the best way to log something out to the log files for when debugging the CLI?

Options
U02P7B6K2LC
U02P7B6K2LC Posts: 121 🧑🏻‍🚀 - Cadet

Hey Spryks…!

What’s the best way to log something out to the log files for when debugging the CLI? For instance… when running import commands and there are Writer exceptions etc.

Comments

  • Valerii Trots
    Valerii Trots SRE @ Spryker Sprykee Posts: 1,654 ✨ - Novice
    Options

    You can run default importers with -t option, that will print out actual exception.
    If this is something you are looking for.

  • U02P7B6K2LC
    U02P7B6K2LC Posts: 121 🧑🏻‍🚀 - Cadet
    Options

    That helps thank you!

    In general it’s difficult to see what’s contained in some of the data variables inside the importer and writer systems (since we aren’t in the browser so can’t do a “die dump” like you would in Laravel and see the contents).

    So I was thinking of using Symfony’s Logging system to print out some data and see what’s whappening.

    (in this case I managed to debug this without the need to do this but in future it would be handy)

  • U03KHD1RW6A
    U03KHD1RW6A Posts: 9 🧑🏻‍🚀 - Cadet
    Options

    docker/sdk console data:import: -t