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
However, the difference would be, that instead of providing an organisation name, as ESLint allows to do so, like:
{
"extend": "@org-name"
}
Which is a Node.js package uploaded to registry (either public - npmjs.com, or other).
Possible solution
In the case of Rust ecosystem, I believe the most convenient way would be providing a whole URL link to the .rustfmt.toml file hosted on any repository hosting service like GitHub.
The only concern I have for now, what if the repository is private?
I guess, we could do similarly to what Cargo.toml does with using ssh://[email protected]/....
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I am wondering if anyone else feel the need an ability of having a shared configuration for several repositories?
Inspiration
Similarly to what ESLint (from the JavaScript ecosystem) has: https://eslint.org/docs/latest/extend/ways-to-extend#shareable-configs
However, the difference would be, that instead of providing an organisation name, as ESLint allows to do so, like:
Which is a Node.js package uploaded to registry (either public - npmjs.com, or other).
Possible solution
In the case of Rust ecosystem, I believe the most convenient way would be providing a whole URL link to the
.rustfmt.toml
file hosted on any repository hosting service like GitHub.Example:
What about private/secured access?
The only concern I have for now, what if the repository is private?
I guess, we could do similarly to what
Cargo.toml
does with usingssh://[email protected]/...
.Beta Was this translation helpful? Give feedback.
All reactions