Best Practice

About our bundler

About how to migrate to Nextjs app route

Practice about testing (unit/e2e)

About the interior rules

How we name our folders and components

About pipeline builder

About the pipeline recipe dirtiness

About the isNewPipeline state

Initially, we are using fetch pipeline result as a indicator about whether this is a new pipeline or not. But when we try to add the loading spin, the logic will make even user is creating the new pipeline they have to wait until the first fetch pipeline request is done. Which is not a good user experience.

Pipeline data coming from react-query as the single source of truth

We don’t store another Pipeline instance in the usePipelineBuilderStore

We only query pipeline with the id in the URL fragment