Pretty print diagnostics

0xLucqs commented 1 month ago

Use this crate to prettily format diagnostics while it's not integrated yet in the compiler

Xavek commented 1 month ago

@0xLucqs I want to try this

0xLucqs commented 4 weeks ago

Hey @Xavek any news ?

Xavek commented 4 weeks ago

@0xLucqs I have unassigned myself. I caught up with other things and it looks like I would be occupied. Couldn't finish, next time

lauchaves commented 3 weeks ago

I am applying to this issue via OnlyDust platform.

My background and how it can be leveraged

Hey! @0xLucqs 👋 I'm Lau Chaves, and I would like to contribute to this issue! I have over 5 years of experience with JavaScript, React, TypeScript, and Ruby. I’m now enthusiastic about web3 and eager to learn more! I’m also a member of Dojo Coding Costa Rica. Feel free to check out my OnlyDust profile and my GitHub profile: lauchaves!

How I plan on tackling this issue

I'd follow this approach:

I'll add the new dependency annotate-snippets
Import and use the crate in the code
I'll create and format diagnostics would make a function called format_diagnostic for it
I’d find where diagnostics are currently output and replace that code with a call to format_diagnostic
I’d run the linter to ensure diagnostics are ok and the output is correctly formatted as well

0xLucqs commented 3 weeks ago

sounds good let's go

keep-starknet-strange / cairo-lint

Pretty print diagnostics #5

My background and how it can be leveraged

How I plan on tackling this issue