Discussion
Loading...

#Tag

Log in
  • About
  • Code of conduct
  • Privacy
  • Users
  • Instances
  • About Bonfire
clacke: exhausted pixie dream boy πŸ‡ΈπŸ‡ͺπŸ‡­πŸ‡°πŸ’™πŸ’›
clacke: exhausted pixie dream boy πŸ‡ΈπŸ‡ͺπŸ‡­πŸ‡°πŸ’™πŸ’›
@clacke@libranet.de  Β·  activity timestamp 6 days ago

I gave the team a half-hour crash course in jq, some of the key features of its data and execution model, and how to do a handful of useful everyday things.

After, I had so many questions for myself that I spent over an hour learning more jq. I now have a greater understanding for how brilliant the language is, and I would do that crash course differently.

I think I owe @hpr an episode, if there isn't one.

I found many cheat sheets and liked none of them. A cheat sheet would be perfect to go in the show notes.

#jq

clacke: exhausted pixie dream boy πŸ‡ΈπŸ‡ͺπŸ‡­πŸ‡°πŸ’™πŸ’›
clacke: exhausted pixie dream boy πŸ‡ΈπŸ‡ͺπŸ‡­πŸ‡°πŸ’™πŸ’›
@clacke@libranet.de replied  Β·  activity timestamp 6 days ago

In Github Actions, jq comes pre-installed in the default worker. This can save you a lot of headache. Don't try to manipulate JSON with bash or Python, that's just clunky and error-prone when you can use jq instead.

I rewrote some of my own code from half a year ago. It's now shorter, more readable (if you know jq – hence the crash course), has zero quoting issues and provides better error messages.

#GithubActions

  • Copy link
  • Flag this comment
  • Block

bonfire.cafe

A space for Bonfire maintainers and contributors to communicate

bonfire.cafe: About Β· Code of conduct Β· Privacy Β· Users Β· Instances
Bonfire social Β· 1.0.1 no JS en
Automatic federation enabled
Log in
  • Explore
  • About
  • Members
  • Code of Conduct