feat: contacts import ocs#61277
Conversation
9e175b9 to
7553769
Compare
|
|
||
| use JsonSerializable; | ||
|
|
||
| interface ImportEvent extends JsonSerializable { |
There was a problem hiding this comment.
What value does this interface add of it has no methods?
There was a problem hiding this comment.
This is a common type for ImportCountEvent and ImportObjectEvent, its used to stream events all the way to the UI while processing.
There was a problem hiding this comment.
Got it. For simplicity, could you just use JsonSerializable in the few areas you use ImportEvent right now?
There was a problem hiding this comment.
Hmm, I think I would prefer the current way to make it more clear what's being expected from a readability standpoint 🤔
There was a problem hiding this comment.
This PR has to be backported. Can we keep it simple?
There was a problem hiding this comment.
You can add the YAGNI abstraction to master. But for the backportable bit let's skip it
There was a problem hiding this comment.
This PR has to be backported. Can we keep it simple?
Ahh, yeah, I didn't had that in mind. So, I'll agree with you 😄
There was a problem hiding this comment.
You can add the YAGNI abstraction to master. But for the backportable bit let's skip it
I agree with this. Lets do this.
| } | ||
| return match ($options->getFormat()) { | ||
| 'vcf' => $this->importProcess($source, $addressBook, $options, $this->importText(...)), | ||
| 'jcf' => $this->importProcess($source, $addressBook, $options, $this->importJson(...)), |
There was a problem hiding this comment.
Json and Xml aren't implemented (I've tested that, instant crash). So, maybe makes sense to remove for now?
There was a problem hiding this comment.
Ah! Forgot to remove those! Done
|
There are still some issues 🤔 The Call to undefined method OCA\\ContactsInteraction\\AddressBook::getResourceId()Memory exhaustedAnd the following warning is being thrown sometimes at the end of the import: Header already modified |
|
Hey David, Thanks for testing! Looks like some of these are not related to my PR.
|
c171464 to
90e83f0
Compare
d0e8053 to
4d7c277
Compare
90e83f0 to
60a348c
Compare
4d7c277 to
085f3d4
Compare
Signed-off-by: SebastianKrupinski <krupinskis05@gmail.com>
Signed-off-by: SebastianKrupinski <krupinskis05@gmail.com>
6de1791 to
3b8c00a
Compare
|
So I tracked down the memory exhaustion error and its not related to this PR, its happening at the request parsing level. Therefore unrelated and out of scope |
Signed-off-by: SebastianKrupinski <krupinskis05@gmail.com>
3b8c00a to
d7ed0f7
Compare
Summary
Checklist
3. to review, feature component)stable32)AI (if applicable)