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
I think removing depreciated Functions and Macros would help users to use missionary.
You could do this for example on a major release where you clearly mark the breaking change.
I say this because you have a big missionary.core namespace .. and I find it hard to navigate the cljdocs. There are a lot of hard to digest concepts in missionary .. and finding the right function takes time.
I know you did keep the depreciated stuff for compatibility. But perhaps you want to consider moving them out in one breaking release.
In the minimum you should remove outdated
Functions/macros from cljdoc. This should be 100% safe because in cljdoc you can select the version.
Thanks!
The text was updated successfully, but these errors were encountered:
Hi @leonoel !
I think removing depreciated Functions and Macros would help users to use missionary.
You could do this for example on a major release where you clearly mark the breaking change.
I say this because you have a big missionary.core namespace .. and I find it hard to navigate the cljdocs. There are a lot of hard to digest concepts in missionary .. and finding the right function takes time.
I know you did keep the depreciated stuff for compatibility. But perhaps you want to consider moving them out in one breaking release.
In the minimum you should remove outdated
Functions/macros from cljdoc. This should be 100% safe because in cljdoc you can select the version.
Thanks!
The text was updated successfully, but these errors were encountered: