Repository navigation
Disable collections - #2153
Draft
davidwaroquiers wants to merge 7 commits into
Draft
Disable collections#2153davidwaroquiers wants to merge 7 commits into
davidwaroquiers wants to merge 7 commits into
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2153 +/- ##
==========================================
+ Coverage 82.33% 82.37% +0.03%
==========================================
Files 90 90
Lines 8652 8681 +29
==========================================
+ Hits 7124 7151 +27
- Misses 1528 1530 +2
🚀 New features to boost your workflow:
|
This branch has not been deployed
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
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.
This is a draft pull request to disable collections in both the backend and frontend. It is based on #2113 and merely adds the disabling of backend routes/database etc ...
@ml-evs I let you decide which one you think is best. This one makes the disabling "complete" but at the same time I understand it is (slightly) more complex (not that much actually but obviously there are a few things in the backend ...)