Allow customizing which folders are recognized as segments

[jngmk]

According to the no-segmentless-slices README, the rule forbids slices without any segment folders. However, in practice, one of the ui, model, config, lib, or api folders must always be present. In our case, every feature requires a bridge, so we always want to keep a bridge folder as well. It would be great if the linter allowed us to configure additional folders to be recognized as valid segments through settings.

Related code

• https://github.com/feature-sliced/steiger/blob/master/packages/steiger-plugin-fsd/src/no-segmentless-slices/index.ts#L27
• https://github.com/feature-sliced/filesystem/blob/main/src/fsd-aware-traverse.ts#L210

[illright]

This is a good point. Could you share a bit more about your use case? What segment names do you use that don't intersect with standard names like api, model, ui?

[jngmk]

We generally don’t go beyond the conventional categories, but in our case we use an additional bridge segment due to legacy migration needs. We are gradually migrating a legacy project into a new repository, and because of this, every feature still needs to communicate with the legacy project. For that reason, we are intentionally placing the bridge functionality in a separate folder rather than inside the model or lib folders of a feature. Since the legacy codebase is very large and cannot be moved all at once, there are even some features that only need a bridge for now.

I assume there will be many different use cases depending on each team’s situation, and since the isSlice function already accepts additionalSegmentNames, I thought it would be nice if more exception cases could be supported.