IPFS Things 2023 - Workshop Feedbacks

[laurentsenta]

Build

• docker build time is too slow
• window support!

String Formatting:

• Provide a non-formatted option for string comparison (Equal vs Equalf) to help with testing URL-escaped strings
• golang's verb collides with URL-escaping a lot: Provide a simpler templating system where you could create a string with something like /ipfs/{{CID}}/%c4%85/%c4%99 and not have to deal with escaping strings

Usage:

• Avoid magic - We should NOT default to "follow redirects"; make sure this is an explicit option #62
• Better description of fixtures

Fixtures:

• better description of fixtures, what it contains, and what's inside
• Make sure fixtures (CAR) can be recreated, maybe generate them on the fly
• provide a way to inspect these CARs

Debugging

• verbose mode: print content of fixtures, make them inspectable

Documentation

• document what are CAR files and why we use them

[laurentsenta]

One open question we'll have to tackle: one of the feedback was "Make sure fixtures (CAR) can be recreated, maybe generate them on the fly".

Another of our goal is to have specs come with fixtures directly (like the _redirect fixtures).

We'll have to think about:

• do we really want to generate fixtures on the fly? (one of our task was to NOT generate them on the fly in Kubo)
• what should the spec recipe, used to recreate it, look like? In kubo they look like this