Open azinit opened 3 years ago
But there are still some open questions (which issues and articles - can't explain fully):
According to experience - no, but it wasn't clear and obviously at start
I found for my self:
on{Action}
format)But it isn't clear - what approach is recommended...
or is there exist some better methods
I read that it's recommend to share data on page level (it's logical) in format: feature1 => page => {other features}
But it isn't clear - how store and pass this data
features
and pages
slices
UPD: Other variation of question - How to share page context/state between (isolated) features?
(for example, auth data, entity mutation state - create/edit/view/delete
, and etc. - something meaningfull for page and that should impact to features)
If someone has opinion about some of questions above - please, share it here =)
At the moment I have little misunderstanding with Feature Driven Development, namely - with cross-features communication
@kof Does it exists example based on FDD, with multi-page logic and cross-feature communication and data sharing?
(example at repo - unfortunately, doesn't demonstrate this aspects enough)
Main questions:
I already doubt, that there is a perfect solution resolving all FDD principles enough
The main principle is that isolated features should not know about each other. There are multiple ways to achieve that:
Hi everyone! I have text version of kof's Berlin talk. https://www.notion.so/Summary-YouTube-Feature-Driven-Arhitecture-b8609fd4452b41f499703c841e56b8e9
Maybe, it'll be useful for someone 🤷♂️