fix: improve fuels init directory detection

[petertonysmith94]

• Closes Improve fuels init directory detection #3614

Release notes

In this release, we:

• Improved directory detection for fuels init

Summary

When using fuels init, we now detect individual contracts, predicates and scripts by their respective Forc.toml files. This should account for more user error when using the command and alleviate some pain points.

Checklist

• All changes are covered by tests (or not applicable)
• All changes are documented (or not applicable)
• I reviewed the entire PR myself (preferably, on GH UI)
• I described all Breaking Changes (or there's none)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
fuels-template	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 5, 2025 1:17pm
ts-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 5, 2025 1:17pm
ts-docs-api	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 5, 2025 1:17pm

[Torres-ssf]

@petertonysmith94 Maybe I am missing something, but when running this locally while using the fuels from your branch, I have the following output for the project that I am using:

➜  pnpm fuels init --predicates sway-programs/predicate/* --output ./src/predicate_api
using deprecated parameters for the initialization function; pass a single object instead

✅ Your fuels version is up to date: 0.98.0

############### INIT CALLED

error: unable to detect program/s
- contract/s detected 0

The ############### INIT CALLED was added by me to serve as a confirmation that I was using the fuels from your branch

But when using the released version, everything seems to work:

➜  pnpm fuels init --predicates sway-programs/predicate/* --output ./src/predicate_api
using deprecated parameters for the initialization function; pass a single object instead

✅ Your fuels version is up to date: 0.98.0

Config file created at:

 /Users/torres-m3/Documents/personal/my-fuel-project/fuels.config.ts

[petertonysmith94]

@petertonysmith94 Maybe I am missing something, but when running this locally while using the fuels from your branch, I have the following output for the project that I am using:

It was me that was missing something - nice catch 🎣

Turns out the OS expands glob patterns before they hit the CLI. Therefore, our tests weren't picking these up. I've made the following changes 167c42a which should address this :)

[github-actions]

Coverage Report:

Lines	Branches	Functions	Statements
77.25%(+0.05%)	70.73%(-0.03%)	75.42%(+0.13%)	77.24%(+0.05%)

Changed Files:

Ok	File (✨=New File)	Lines	Branches	Functions	Statements
🔴	packages/fuels/src/cli/commands/init/index.ts	95.34% (-4.66%)	83.33% (-16.67%)	100% (+0%)	95.55% (-4.45%)
🔴	packages/fuels/src/cli/config/forcUtils.ts	94.28% (+0.84%)	75% (-5%)	100% (+0%)	94.59% (+0.75%)