Skip to content
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: the release notes and other documentation changes on the website are outdated #559

Closed
nateshmbhat opened this issue Oct 19, 2022 · 17 comments

Comments

@nateshmbhat
Copy link
Contributor

No description provided.

@helenaford
Copy link
Member

thanks for opening this issue. Looks like the website hasn't updated but you can find release notes here (cc58d05) in the meantime

@helenaford helenaford changed the title Update release notes in notifee website : https://notifee.app/react-native/docs/release-notes docs: the release notes on the website are outdated Oct 19, 2022
@helenaford helenaford pinned this issue Oct 24, 2022
@github-actions
Copy link

github-actions bot commented Dec 6, 2022

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?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.

@helenaford helenaford changed the title docs: the release notes on the website are outdated docs: the release notes and other documentation changes on the website are outdated Dec 19, 2022
@github-actions
Copy link

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?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.

@helenaford
Copy link
Member

keep open.

@github-actions
Copy link

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?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 28, 2023
@helenaford helenaford reopened this Mar 1, 2023
@github-actions
Copy link

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?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 13, 2023
@rvasseur31
Copy link
Contributor

Hi @helenaford, do you have any update on this ?

@elibroftw
Copy link

elibroftw commented Aug 27, 2023

@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
image

be directed to github rather than the outdated page.

@VivienTournie
Copy link

Hi @helenaford , any update on this issue ?

@mikehardy
Copy link
Contributor

Definitely not stale!

mikehardy added a commit that referenced this issue Dec 13, 2023
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
Copy link

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?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 4, 2024
@mikehardy
Copy link
Contributor

The stale bot is still faster than I am but I make inevitable progress

@mikehardy mikehardy reopened this Jan 6, 2024
Copy link

github-actions bot commented Feb 3, 2024

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?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.

@liamjones
Copy link
Contributor

Not stale

@mikehardy
Copy link
Contributor

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...

Copy link

github-actions bot commented Mar 4, 2024

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?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 19, 2024
@johnf
Copy link

johnf commented Apr 29, 2024

not stale

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants