You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
currently, the deploy command requires a Solana.toml to exist.
while the toml file can make things easier for mucho to parse, developers should not be forced to create and use one
i consider this a bug.
The text was updated successfully, but these errors were encountered:
Tested that deploy command works without Solana.toml as well. However, it currently breaks if Solana.toml exists but doesn't have entries for the current program/cluster.
Suggestion: We could improve this further by making Solana.toml entirely optional, where:
If it exists, use it as a convenient way to specify program IDs and settings
If it doesn't exist or doesn't have entries for current program/cluster, fall back to auto-detection
This would give flexibility while maintaining the convenience of using toml when desired.
Would you like me to create a PR with these changes?
currently, the
deploy
command requires aSolana.toml
to exist.while the toml file can make things easier for mucho to parse, developers should not be forced to create and use one
i consider this a bug.
The text was updated successfully, but these errors were encountered: