Please provide better documentation

[PhilippRoessner]

Hi,
Is there a chance to get better documentation? I am having trouble to get the "get" function working which I need to chain to the "skip" or "top" function. Or is there a different method to subscribe to these functions?

Thx!

[diegomvh]

Hi @PhilippRoessner

Basically, the library works with abstractions of the odata endpoints called resources.
There are different types of resources (entity-set, entity, property, etc) and they are obtained from services.
Each resource according to its type has different ways of interacting with it using the http get post put delete methods.
For these http primitives the library only takes the data and the associated metadata and makes it available to the caller
Then with these primitives higher order functions such as fetch, fetchAll or call are built, depending on the need

Documentation is a big missing and a "skinny" part of the project.
Regarding the use, there is an example project.

https://github.com/diegomvh/AngularODataEntity/blob/1ce092b9421e0033ca761ead4efd47df3d3fc195/src/app/app.component.ts#L74

The demo does not cover all the functionality but it does cover the basics.
My intention is to continue adding and working on the features. Although eventually documenting will be necessary.

Regards

[AliAlmutawakel]

Documentation is really necessary for this library. It's great, thorough, and extremely powerful but it's too bad nobody knows how to use it. Even minimum documentation would be super helpful. Nothing fancy is necessary, just a minimal function or property /** documentation */ can go a long way to say what it does. At least then more people would use it, issues can be found, library stabilizes & matures quicker, and opens doors for people to contribute to it. I hope you would change your mind about the priority of the documentation or at least cover all the functionality in the example project.

[Coder7777]

Documentation is really necessary for this library. It's great, thorough, and extremely powerful but it's too bad nobody knows how to use it. Even minimum documentation would be super helpful. Nothing fancy is necessary, just a minimal function or property /** documentation */ can go a long way to say what it does. At least then more people would use it, issues can be found, library stabilizes & matures quicker, and opens doors for people to contribute to it. I hope you would change your mind about the priority of the documentation or at least cover all the functionality in the example project.

I can not agree with you more.

[krstev1994]

Hi Diego,
Can you provide some examples of using create, update and destroy methods?
Get and fetch options are awesome!
Tnx and BR,
Vasil.