You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your change request related to a problem? Please describe.
As described in the documentation section of the Library Guidelines, Contributors libraries are expected to have mostly complete module documentation, preferably uploaded to Pursuit.
This library currently doesn't have sufficient module documentation -- many publicly-exported types and functions don't have any documentation comments.
Describe the solution you'd like
The library needs to have documentation comments on the majority (and preferably all) public types and functions. Once updated, we should tag a release and upload new module documentation to Pursuit so that folks can use it.
It's questionable whether we need to duplicate the official API docs for this wrapper library. Ideally, we could autogenerate our documentation by either scraping and/or linking to each function in the official API docs. Unfortunately, the official docs don't have anchor links, or at least they're broken, for example: https://ace.c9.io/#Editor.blockOutdent doesn't work.
Is your change request related to a problem? Please describe.
As described in the documentation section of the Library Guidelines, Contributors libraries are expected to have mostly complete module documentation, preferably uploaded to Pursuit.
This library currently doesn't have sufficient module documentation -- many publicly-exported types and functions don't have any documentation comments.
Describe the solution you'd like
The library needs to have documentation comments on the majority (and preferably all) public types and functions. Once updated, we should tag a release and upload new module documentation to Pursuit so that folks can use it.
It's questionable whether we need to duplicate the official API docs for this wrapper library. Ideally, we could autogenerate our documentation by either scraping and/or linking to each function in the official API docs. Unfortunately, the official docs don't have anchor links, or at least they're broken, for example: https://ace.c9.io/#Editor.blockOutdent doesn't work.
So maybe a good partial solution is to just link to docs per section (and not per function). For example, at the top of this section:
https://pursuit.purescript.org/packages/purescript-ace/docs/Ace.ScrollBar
link to:
https://ace.c9.io/#nav=api&api=scrollbar
Additional context
See the Governance repository for more information about requirements in the Contributors organization.
The text was updated successfully, but these errors were encountered: