Next Steps for Next Release
ajitid opened this issue · comments
To Do
[None remaining]
Done
Dynamically generating items in normalized map
Covered in #40
We want to do this to reduce bundle size.
Few ideas:
- Reduce number of items in the map by using krisk/Fuse#415 (comment). If we choose this, we'll need to see its browser support as I'm quite sure that it cannot be polyfilled.
- Use a map
{ 'A': [rune1, rune2], 'E': [rune3], ... }
Improve docs versioning
Links to example for <=v0.3 will still break due to the nature of project structure but code links are now hardcoded to a commit.
Right now only docs.mdx
is pulled for versioning. This results in broken links to codebase. What might rather be preferred is to target a specific commit in dev
branch so they remain stable. Another issue is that examples might break too. So versioning both lib and docs would be preferred. Corrections would be required in v0.3.1 too.
Writing docs
Doc length is fairly small-medium so we are not doing this for now.
I'm slightly worried that now with so many features added, a single page doc might not suffice. And with that, a full-text search solution might be needed.
Attaching license in bundled files
Covered in #61
License file is retained while building an npm package though I'm not sure if one needs to write an author doc in bundled files too. If that's the case, then this Rollup config would be useful.