Closed brunomenezes closed 1 year ago
Folks (@nevendyulgerov , @dandheedge ),
I've been breaking the outdated
reports into smaller issues by context, but even these "bits" compress too much.
Today in our meeting, I want to discuss an approach I worked in the past and exchange ideas for this kind of issue that is a bit bigger in the sense of possible breaking changes—this one, for instance, touches multiple parts like storybook
, jest
, typescript
, ethers
etc. I am not just talking about making that an epic
combined with tracked tasklists but an approach on feature-branches and PRs. I am thinking for the sake of who is reviewing because it ended up a huge PR with multiple complex changes, and it becomes tedious work cognitively hard to grasp ending up on LGTM
😏.
So let's discuss this, and later I will refine this issue. I want to have this framework defined with you before creating one for the staking
because that is a monster 😄.
📄 Context
Update the dependencies defined in the
packages/ui
to avoid staying behind too much.Affected parts
📈 Subtasks