Skip to content
This repository has been archived by the owner on Jun 5, 2024. It is now read-only.

Dav response parser & possible usage of existing dav libraries #1036

Open
lookacat opened this issue Apr 5, 2022 · 0 comments
Open

Dav response parser & possible usage of existing dav libraries #1036

lookacat opened this issue Apr 5, 2022 · 0 comments

Comments

@lookacat
Copy link
Contributor

lookacat commented Apr 5, 2022

With the work on https://jira.owncloud.com/browse/WEB-1095 we have found some issues regarding our dav.js.

  1. Parsing of e.g. Propfind response does manipulate the keys und values of a prop significantly. This lead to information being thrown away. Only limited value types are supported and more complex values are either parsed wrong or are just cut off. It's also really time consuming to extend the parsing logic, and it's hard to understand existing code. E.g _parsePropNode in dav.js is not providing much value and is really hard to extend.

  2. We've discussed why we did write our own dav client if there are some promising libraries out there that are well maintained and would save us time and effort. Libraries we came across are:

  1. We should consider switching to an external library but we need to make sure they suit our needs and fit in with our code.

Issues that will be resolved by this:
#1032

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant