📎 Support extensible config via "extends" property

[marcalexiei]

Description

Support extends key inside configuration file in order to provide the ability to re-use configuration among different repositories.

References:

• ☂️ One config format, in one place #1596 (comment)
• Extendable config #4036

[ematipico]

Bumping this. After the 12.1.0 release, I think we could start implementing it.

We have good diagnostics and a great awareness of the configuration file now. Of course, the extends will be limited only to physical paths:

Yes ✅

{
	"extends": ["./formatter.json"],
}

No ❌

{
	"extends": ["@somelibrary/hey"],
}

cc @rome/core-contributors if you're interested of if there's someone interested

[Nikola-Milovic]

No x
{
"extends": ["@somelibrary/hey"],
}

@ematipico does this mean we still can't have a shared package with rome config in monorepos and use it to extend? Especially in larger monorepos I'd love to have shared rome config across all projects. I currently use this approach for tsconfigs for example

[ematipico]

We're clearly aware of the limitation, but Rome can't resolve dependencies yet. Hopefully soon we will be able to implement it.