@cnakazawa tsc --build --watch w/ project references.
1. Each pkg defines a tsconfig w/ references
2. Root level tsconfig references all repo pkgs
Faster and more memory efficient than fanning out w/ turbo.
Would advise tooling to keep project references in sync.
@cnakazawa I wish fate wasn't coupled so tightly to tRPC, because I think the general concept of separating views from fetching implementation could be applicable with any API that provides a consistent interface for byId/list queries...
@cnakazawa I've been thinking about this riddle of how to colocate data requirements with components while having the simplicity of REST for years. I've used JSON:API, which enforces unique ids that allow normalization, but I've never had a good solution for fragments.
@lucy_guo@a_zatarain Lived in Miami for a couple years. Anytime I have the chance to travel back I go out of my way to stop at Blackbrick. Canβt go wrong with the Dan Dan Mian Noodles and the General Tsoβs Gator.
@tkulzer@ricreyna@maccaw Slight perspective shift, but I think there is benefit in engineers seeing functional tests as a tool rather than a burden. Example, to build X feature, begin by writing a functional test that drives app into X state.
@tkulzer@ricreyna@maccaw Agree on the need for multiple π, but could the same outcome not come from manual QA w/ feedback cycling back to feature engineer?
@ricreyna@maccaw If you donβt mind expanding... How did you determine that a dedicated role would be better than offloading to the engineers responsible for building the feature?
@rauchg@zeithq Perhaps I am fighting "against the stream" due to preconceptions of how I wanted the system to behave. I'll try to take a step back and look at it through a new lens.
I had heard so many good things about @zeithq. A little disappointed:
- Guides suggest GUI heavy workflows (Ex: "build settings"). I prefer to keep config in source control.
- High churn. Recently released APIs already appear to be deprecated (Ex: "builds").
@rauchg@zeithq I am having a difficult time identifying what config needs to live in the cloud vs `now.json`... and with the introduction of `.now/project.json`, I now have various configuration values split across three separate locations.
@rauchg@zeithq I think some of the friction stems from long-tail keyword searches surfacing deprecated solutions. Ex: searching for "zeit monorepo", I find https://t.co/Iiiy7A1zDc. During this process, I found myself continually asking, "Ok, but what is the best way to implement X now?"
@chibicode@zeithq Hi Shu. I'm looking for more context.
- Do I have to use the `now` command or can I manually add org/project ids?
- Why is a `.now` a directory being created?
- Why is it being ignored from source control and how does this affect working with multiple team members?