experiment/refactor-custom-fetch #892
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
marcel-bitfly
force-pushed
the
experiment/refactor-custom-fetch
branch
from
f455af6 to
604b730
Compare
marcel-bitfly
force-pushed
the
experiment/refactor-custom-fetch
branch
from
604b730 to
e62e743
Compare
marcel-bitfly
force-pushed
the
experiment/refactor-custom-fetch
branch
from
e62e743 to
e508d4d
Compare
marcel-bitfly
force-pushed
the
experiment/refactor-custom-fetch
branch
4 times, most recently
from
3b6c4d8 to
ec863f9
Compare
Deploying beaconchain with
|
| Latest commit: |
cacdc6e
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://9ed0f32b.beaconchain.pages.dev |
| Branch Preview URL: | https://experiment-refactor-custom-f.beaconchain.pages.dev |
marcel-bitfly
force-pushed
the
experiment/refactor-custom-fetch
branch
from
2841603 to
0cfa409
Compare
As it is rather a composable than a `store`.
Should probably be done by `NuxtScripts` feature
After an update of `nuxt` the `nuxt eslint module` did not work any more.
…1 app` This change is necessary, since `v1 app` and `v2 (this) app` are running on the same `url`. So the traffic originating from the browser to request a specific resource of this app has to be routed to the `v2 app instance` on the server. That's why we use a `generic prefix`(/assets-2usdf) for `publicly served assets`.This will prevent name collisions.
…th `v1 app` This change is necessary, since `v1 app` and `v2 (this) app` are running on the same `url`. So the traffic originating from the browser to request a specific route to be routed to the `v2 app instance` on the server. That's why we use `/api/bff`, as this will be routed to this app instance instead of `v1`.
For using a version that is optimized for nuxt for easier integration and maintainance.
marcel-bitfly
force-pushed
the
experiment/refactor-custom-fetch
branch
from
4784f21 to
286e543
Compare
marcel-bitfly
force-pushed
the
experiment/refactor-custom-fetch
branch
2 times, most recently
from
ba73b71 to
5d2149c
Compare
- add doptimistic response for adding, editing and deleting - remove client pagination
marcel-bitfly
force-pushed
the
experiment/refactor-custom-fetch
branch
from
5d2149c to
78abb5f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Get rid of
useCustomFetchs-complexity