Migrate all scarb packages to support `edition = "2024_07"`

[kkawula]

Which components does the task require to be changed? (think hard pls)

snforge, sncast

Description

Migrate all scarb packages to support edition = "2024_07"

Sollution: for each

• change edition to "2024_07"
• run snforge test to check if the package compiles if not make proper changes

Related: https://github.com/foundry-rs/starknet-foundry/issues/2632

[enehizy]

Mind if I take this issue?

[OWK50GA]

Could I take on this issue?

[mexes20]

Hello, I’d like to be assigned to work on this.

ETA: 15 hours

[pheobeayo]

I'd love to give this a go.

[ShantelPeters]

Please can I be assigned to this issue

[PedroRosalba]

I am applying to this issue via OnlyDust platform.

My background and how it can be leveraged

How I plan on tackling this issue

[pheobeayo]

On it! thank you for the task.

[franciszekjob]

Hi @pheobeayo , just wanted to check out on your progress. Do you need any assistance 😄 ?

[pheobeayo]

@franciszekjob I am working on it, but how do I build successfully locally?

[franciszekjob]

but how do I build successfully locally?

Just run snforge test in the package.

[franciszekjob]

Hi @pheobeayo , how's the progress :) ?

[pheobeayo]

@franciszekjob still fixing the 507 bugs after changing the edition....

I have tried fixing some but still couldn't make the file public like this lib.cairo was initially like but I decided to make it public like this but still couldn't compile.....

Any clue to that

[franciszekjob]

@pheobeayo I see you're updating edition in snforge_std. I think we can address this specific package in other PR, as it may require more work. So let's limit the scope to update edition in all packages, apart of snforge_std, ok?

[pheobeayo]

okay

[pheobeayo]

@franciszekjob Kindly check out the PR I created yesterday, I updated the edition in all packages apart from the snforge_std