Skip to content
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

Update extension properties API docs #635

Open
AndreiKingsley opened this issue Mar 21, 2024 · 2 comments · May be fixed by #651
Open

Update extension properties API docs #635

AndreiKingsley opened this issue Mar 21, 2024 · 2 comments · May be fixed by #651
Assignees
Labels
documentation Improvements or additions to documentation (not KDocs)
Milestone

Comments

@AndreiKingsley
Copy link
Collaborator

I think there needs to be more explanation and examples here, topic looks seriously incomplete:
https://kotlin.github.io/dataframe/extensionpropertiesapi.html

@AndreiKingsley AndreiKingsley added the documentation Improvements or additions to documentation (not KDocs) label Mar 21, 2024
@Jolanrensen Jolanrensen added this to the Docs infrastructure milestone Mar 21, 2024
@Jolanrensen
Copy link
Collaborator

What else would you want to be there? Some example of what is generated perhaps?
There is already more at:
https://kotlin.github.io/dataframe/schemasgradle.html#execute-the-assemble-task-to-generate-type-safe-accessors-for-schemas

@AndreiKingsley
Copy link
Collaborator Author

No, I don't want implementation details or other deep stuff. I'd like users, unfamiliar with DataFrame, to have a clearer understanding. For example, to say that "in this cell a dataframe appeared, it has these columns, and we can use them further like that".
So, in my personal opinion, there seems to be a lack of clarity regarding what happened between the lines of code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation (not KDocs)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants