#strcase fix
frigid stream
Having said that, maybe we can write an automation script to list all modules from our daggerverse list, and try calling their functions with new engine. Maybe we can identify some edge cases using that. what do you think?
@plucky birch so we have a script that can get the latest version of each module and perform a dagger develop on each. Having said that, IIUC that won't tell us if something breaks, right? We'd have to compare it with the current generated output of v0.12.4 correct?
plucky birch
hmm, yeah, i guess i'd want the graphql schema for each module
like the introspection results
and would want to compare between different versions
frigid stream
hmm, yeah, i guess i'd want the graphql schema for each module
yeah.. we can do that I guess. Let's get some time together tomorrow @regal rapids to check this out 🙏
frigid stream
@regal rapids @plucky birch, @crimson fjord added a draft test that can help us with this here https://github.com/dagger/dagger/pull/8122#issuecomment-2291596432
we'll add a compat mode so we can compare the generated APIs across different engines 🙏
plucky birch
yeah, sorry i saw this, thanks @crimson fjord
🎉
yeah, the comparison is important - if the module was broken, we don't care if it continues to be broken
the other part is that we need to see if the api has changed - not just if it loads and compiles - not quite sure how we can super neatly do this, we could do a graphql dagger query and load our introspection query for that module?
@frigid stream do you have cycles to help out on that?
frigid stream
the other part is that we need to see if the api has *changed* - not just if it ...
@crimson fjord will also help with this with the compat mode I was mentioning above
plucky birch
awesome awesome ❤️
frigid stream
we'll check that before merging the PR
crimson fjord