kof / feature-driven-architecture

Defining boundaries for a large application.
https://codesandbox.io/s/github/kof/feature-driven-architecture/tree/master/demos/scoped-redux
38 stars 4 forks source link

Add linting of FDD #12

Open azinit opened 4 years ago

azinit commented 4 years ago

Hello, everyone!

I have idea to impl linting of Feature Driven Development rules, based on FDD principles:

If you have ideas / suggestions or if you can help in any way - you're welcome! =) https://github.com/feature-driven/eslint-plugin-feats

At the moment I've written base rules in project's README

azinit commented 4 years ago

Sorry, if its not relevant topic, but I don't know better place with FDD community in JS)

kof commented 4 years ago

I actually think that linting is a great idea!

kof commented 4 years ago

I would recommend starting with less options, more fixed settings, because I don't see much sense to have a linter if any convention can be broken by configuration. If someone presents a valid case - then consider adding a configuration for a particular behaviour.

azinit commented 4 years ago

@kof thanks for feedback!)

But I would be glad to discover more feature driven project examples, if you or anyone else can help with it

Because, I have some open questions about features cross-communication and data sharing

I asked for this in other issue too

UPD: It will help to impl real quality linter

azinit commented 4 years ago

Also I had idea to impl CRA template for FDD apps

For this and other FDD promotion projects I've created github organization

If you want to promote and develop FDD ideas - you're welcome =)

Write me to Telegram or to email (martis.azin@gmail.com) - I'll add you to org and GitHub team

image

Sorry if it's not such relevant topic, but I can't found place better for announce this

kof commented 4 years ago

I think creating an org is too premature at this point, I too created too many orgs too early.

kof commented 4 years ago

regarding cra template - yeah, I think it will be useful if the project matures and gets some users

kof commented 4 years ago

I think ultimately this methodology has most value for larger projects with long-term maintanance goals, cra is used mostly for smaller projects which are created more frequently. I still think it might be useful but I would focus on a linter, docs and examples first, make those useful and used by other people, then think about other integrations.