Docs - Note any custom helpers/extensions and link to javascript versions if applicable
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 59
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
I was about to write an iterate helper, but then noticed you had one in the source already (!)
I couldn't find any docs for it (aside from the source code) and I'm not sure what (if any) javascript implementations it is compatible with (there are several in the "issues" section of the active dust.js linkedin fork)
It would be great if this library's docs did 2 things:
- noted what helpers there are
- referenced any javascript implementations if available (since users often choose dust to work on client and server side)
see also - https://github.com/mahmoud/ashes/issues/22
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the source's existing helpers and the current documentation, then inspect the linked ashes issue #22 and the Dust.js implementations mentioned in the issue. Document the available helpers and link to compatible JavaScript implementations where applicable; done means both requested documentation sections are covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100