-
Notifications
You must be signed in to change notification settings - Fork 222
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: website is outdated! Use source: https://github.com/invertase/notifee/tree/main/docs-react-native/react-native/docs #559
Comments
Hello 👋, to help manage issues we automatically close stale issues. This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?
Thank you for your contributions. |
Hello 👋, to help manage issues we automatically close stale issues. This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?
Thank you for your contributions. |
keep open. |
Hello 👋, to help manage issues we automatically close stale issues. This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?
Thank you for your contributions. |
Hello 👋, to help manage issues we automatically close stale issues. This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?
Thank you for your contributions. |
Hi @helenaford, do you have any update on this ? |
@helenaford , the website links to outdated release notes. If notifee does not want to keep this page synced with the release notes through an automatied script, then I suggest this page be deleted and that the release note link on the sidebar be directed to github rather than the outdated page. |
Hi @helenaford , any update on this issue ? |
Definitely not stale! |
previously the doc was pointing at the published docs site but we can't use that since the docs site does not actually publish, pending resolution of #559
Hello 👋, to help manage issues we automatically close stale issues. This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?
Thank you for your contributions. |
The stale bot is still faster than I am but I make inevitable progress |
Hello 👋, to help manage issues we automatically close stale issues. This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?
Thank you for your contributions. |
Not stale |
This is an issue common to all the invertase react-native repos at the moment. react-native-firebase is undergoing a documentation refresh at the moment and the sticking point for us always "the docs we manually write" vs "the API reference". In the past we made great efforts to have the API reference match the manual docs exactly so things looked coherent but unfortunately the auto-generation of the manual docs is something that CDNs and web frameworks can't really handle dynamically, and if we generate the API docs statically then they aren't themed correctly like the manual docs. This may not seem important but it's one of those little visual things we were trying to get 100% correct and it just wasn't happening. We've decided last week at a high level that auto-generation of API docs is the only way to make those maintainable + keep them up to date (obviously) but importantly we've decided to relax our success criteria for visual fidelity of API vs manual docs which unblocks this whole thing at a design level so we can just get on with implementation Hoping to have docs published and up to date then, as that is kind of a critical matter... |
Hello 👋, to help manage issues we automatically close stale issues. This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?
Thank you for your contributions. |
not stale |
We've got some progress at long last! https://docs.page/invertase/notifee~docs-page built from branch here https://github.com/invertase/notifee/tree/docs-page And I have a "yes" / approval as an answer to this question which should finally resolve the "okay, but how do we publish the reference API with the types built from source, huh?"
|
No description provided.
The text was updated successfully, but these errors were encountered: