-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feat/remove ccjs #1991
Merged
Merged
Feat/remove ccjs #1991
Conversation
This file contains 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
Contributor
Crash--
commented
Aug 21, 2023
•
edited
Loading
edited
Crash--
force-pushed
the
feat/removeCCJS
branch
from
August 21, 2023 14:14
34f69af
to
c3add38
Compare
Crash--
force-pushed
the
feat/removeCCJS
branch
from
September 25, 2023 08:06
dac644a
to
dd3f6a9
Compare
Crash--
force-pushed
the
feat/removeCCJS
branch
2 times, most recently
from
October 19, 2023 09:46
d418b8b
to
8d99203
Compare
cballevre
reviewed
Oct 19, 2023
Crash--
force-pushed
the
feat/removeCCJS
branch
from
November 14, 2023 14:45
63331fd
to
8dd23f3
Compare
BundleMonFiles updated (6)
Unchanged files (7)
Total files change -34.77KB -1.16% Final result: ✅ View report in BundleMon website ➡️ |
cballevre
force-pushed
the
feat/removeCCJS
branch
from
November 27, 2023 09:59
1f09d1d
to
d1373bd
Compare
We had a few issues with the data persistence within the flagship app. This is mostly due to the fact that we have a lot of way to manage data for the Home application. Here, I remove the `fetchTriggers` to use query(Q('io.cozy.triggers')) everywhere within the app. I also changed the konnectorTile to use data from the cozy-client store instead of the one from the Home.
Stack returns twice the app when served by --serve option in dev mode resulting in a lot of warning in the console. Made a quick dedup
feat: Upgrade CC to fix tests
Instead of having our own implementation
This intent should be called with closable=false since Harvest will handle by itself how to cancel.
- Move the file close to its component - make it dynamic for the konnector name - Split describe in order to have UI and no UI stuff
Need to check why I've removed it recently.
It was previoulsy done by KonnectorsErrors, but since we've removed it, it was not there anymore.
Let's the Intent Service tell the IntentModal that the cross should be hidden Depends on: cozy/cozy-ui#2520 cozy/cozy-libs#2323
The idea is to be able to display an account from every where. This intent is not directly used in production, but it's useful to test the end (aka the display of harvest) of the intent create io.cozy.accounts. I used it to debug the "open in Drive" feature, since the link was not working.
Because Harvest is based on `cozySubdomainType` and we didn't have it in this template, it didn't work in the intents. So I added the same attributes as the browser ones.
cballevre
force-pushed
the
feat/removeCCJS
branch
from
December 20, 2023 14:53
d1373bd
to
d6bb2e4
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.