2023-12-10 18:22:43 +03:00
|
|
|
# Logs
|
|
|
|
|
logs
|
|
|
|
|
*.log
|
|
|
|
|
npm-debug.log*
|
|
|
|
|
yarn-debug.log*
|
|
|
|
|
yarn-error.log*
|
|
|
|
|
pnpm-debug.log*
|
|
|
|
|
lerna-debug.log*
|
2022-12-01 17:58:08 +03:00
|
|
|
|
|
|
|
|
# dependencies
|
|
|
|
|
/node_modules
|
2023-12-10 18:22:43 +03:00
|
|
|
/coverage*
|
2022-12-01 17:58:08 +03:00
|
|
|
/.pnp
|
|
|
|
|
.pnp.js
|
|
|
|
|
|
|
|
|
|
# testing
|
|
|
|
|
/coverage
|
2023-05-31 17:33:11 +03:00
|
|
|
storybook-static
|
2023-06-01 12:20:05 +03:00
|
|
|
build-storybook.log
|
2022-12-01 17:58:08 +03:00
|
|
|
|
|
|
|
|
# production
|
|
|
|
|
/build
|
2023-12-10 18:22:43 +03:00
|
|
|
dist
|
|
|
|
|
dist-ssr
|
2022-12-01 17:58:08 +03:00
|
|
|
|
2023-12-10 18:22:43 +03:00
|
|
|
# env
|
2022-12-01 17:58:08 +03:00
|
|
|
.env.local
|
|
|
|
|
.env.development.local
|
|
|
|
|
.env.test.local
|
|
|
|
|
.env.production.local
|
|
|
|
|
|
2023-12-10 18:22:43 +03:00
|
|
|
# Editor directories and files
|
|
|
|
|
.vscode/*
|
|
|
|
|
!.vscode/extensions.json
|
|
|
|
|
.idea
|
|
|
|
|
.DS_Store
|
|
|
|
|
*.suo
|
|
|
|
|
*.ntvs*
|
|
|
|
|
*.njsproj
|
|
|
|
|
*.sln
|
|
|
|
|
*.sw?
|
2023-12-11 13:13:03 +03:00
|
|
|
|
Feat/put target object identifier on use activities (#4682)
When writing to the normalized cache (record), it's crucial to use _refs
for relationships to avoid many problems. Essentially, we only deal with
level 0 and generate all fields to be comfortable with their defaults.
When writing in queries (which should be very rare, the only cases are
prefetch and the case of activities due to the nested query; I've
reduced this to a single file for activities
usePrepareFindManyActivitiesQuery 🙂), it's important to use queryFields
to avoid bugs. I've implemented them on the side of query generation and
record generation.
When doing an updateOne / createOne, etc., it's necessary to distinguish
between optimistic writing (which we actually want to do with _refs) and
the server response without refs. This allows for a clean write in the
optimistic cache without worrying about nesting (as the first point).
To simplify the whole activities part, write to the normalized cache
first. Then, base queries on it in an idempotent manner. This way,
there's no need to worry about the current page or action. The
normalized cache is up-to-date, so I update the queries. Same idea as
for optimisticEffects, actually.
Finally, I've triggered optimisticEffects rather than the manual update
of many queries.
---------
Co-authored-by: Lucas Bordeau <bordeau.lucas@gmail.com>
2024-04-01 14:12:37 +03:00
|
|
|
.vite/
|
2024-10-28 14:06:58 +03:00
|
|
|
.nyc_output/
|
|
|
|
|
|
|
|
|
|
# eslint-plugin-project-structure
|
|
|
|
|
projectStructure.cache.json
|
