Add recipe for infrared.

[helehex]

No description provided.

[owenhilyard]

You're missing the CodeQL badge

[helehex]

Good catch, I tried it out and noticed it doesn't actually do anything for pure mojo code, so even if I add it, the badge doesn't show up right. I could still add it if necessary though.

If you want to see what I mean, I have a branch where I added the badge. (Also, CodeQL is enabled for the repo regardless of the badge)

[carolinefrasca]

Hey @helehex, good point on the pure Mojo part. Maybe we can just adjust this requirement to only be for packages that contain Python or other languages. The intention with the badge is just to provide a way for reviewers to tell that your repo has CodeQL enabled – is there another way to do that? I might've missed it.

[carolinefrasca]

@helehex looks like there is a little bit of trailing whitespace in your README - do you mind fixing so the pre-commit workflow won't complain?

[carolinefrasca]

Looking at this more, I think the fix is simple – line 15 of the recipe.yaml file just needs to be updated to: mojo package infrared -o ${{ PREFIX }}/lib/mojo/infrared.mojopkg

[yetalit]

@helehex if having the main folder of your package named as src but importing the library by the name of the package file (infrared) doesn't cause any problem, then the only issue is that the test env used max 24.6 for running the test: https://github.com/modular/modular-community/actions/runs/12321698072/job/34497056955?pr=31#step:4:308
(│ │ │ │ max ┆ 24.6.0 ┆ release ┆ max ┆ 9.62 KiB │)
You should limit the max version for your project.

[carolinefrasca]

A quick update for everyone with open PRs that will hopefully make this process a bit easier: it's actually not necessary to include your test file(s) in the PR if you'd like to keep them in your source repo instead, as long as you include the test invocation and SHA/ID for your GitHub in the recipe file (here's an example with @TilliFe's Endia). Please let me know if you have any questions!