Feedback: Confusing & Not intuitive API #64
Replies: 3 comments 2 replies
-
Hey @aaronclong, thanks for reaching out and trying out the package!
I totally, understand the need for a simpler interface while also keeping it functional, if there's any way we could do it, it could help make the library more accessible for many |
Beta Was this translation helpful? Give feedback.
-
Probably, a good starting point is to have more examples. Starting from something simple like the request above |
Beta Was this translation helpful? Give feedback.
-
I don't know what a better abstraction would be for this. I have been mulling that over myself. I'll share my failed attempt with this library. In general, I prefer functional programming with composition over OPP with inheritance so admitting my own bias. I was trying to parse out Google/Alphabet's 10Q
|
Beta Was this translation helpful? Give feedback.
-
I've been trying to follow your documentation (1, 2). However, I can't really make heads or tails of how to actually parse a document and its sections.
I can see the detail and care that when into designing the API, but I do think a simpler abstraction needs to be introduce. For instance, I've struggled for days to try and parse out a filing's sections and grab its text. While, I have gotten output it hasn't been usable, and I'm certain that text got truncated (all user error).
A big issue is just what method to call when since this works off inheritance. You have to do type checks all over the place. I think creating a higher level API or refactor might be needed to reduce the steep learning curve here.
I was kind of hoping this could just parse the tags automatically for me and put them into types.
Beta Was this translation helpful? Give feedback.
All reactions