# Wanikani Open Framework \[developer thread\]

**URL:** <https://community.wanikani.com/t/wanikani-open-framework-developer-thread/22231>\
**Category:** API And Third-Party Apps\
**Created:** [November 21, 2017, 5:07pm UTC](https://community.wanikani.com/t/wanikani-open-framework-developer-thread/22231 "2017-11-21T17:07:07Z")\
**Posts on this page:** 1\
**Showing post:** 109

<div class="post-metadata">

**Author:** ![seanblue](https://sea1.discourse-cdn.com/wanikanicommunity/user_avatar/community.wanikani.com/seanblue/32/579844_2.png) [@seanblue](https://community.wanikani.com/u/seanblue)\
**Post date:** [March 15, 2018, 11:29pm UTC](https://community.wanikani.com/t/wanikani-open-framework-developer-thread/22231/109 "2018-03-15T23:29:35Z")

</div>

I’m not using that function, so I’m good on my end. And here is a link to my script’s forum post: [[Userscript] WaniKani Lesson Hover Details](https://community.wanikani.com/t/userscript-wanikani-lesson-hover-details/29312)

How are you planning to manage breaking changes in the long run? If your framework becomes even remotely popular, breaking changes could cause some real headaches for users. I think it’ll be especially problematic because users can only have one version of the framework and devs will respond to breaking changes at different rates, meaning it’s unlikely all of a user’s scripts will be compatible with the same version of the framework for a period of time.

---

_[View the full topic](https://community.wanikani.com/t/wanikani-open-framework-developer-thread/22231)._