-
Notifications
You must be signed in to change notification settings - Fork 132
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
Release 3.0.0 #267
Comments
We should make sure the latest code doesn't break Rails documentation pipeline, last time I checked there was some incompatibilities. |
@zzak Do you have any links to those incompatiblities? Are these visible when creating a PR in Rails with a new version? |
There are some more changes I would like to include in 3.0.0, so my vote would be to wait a few more weeks. But what is stopping us from pointing https://edgeapi.rubyonrails.org/ at sdoc |
@jonathanhefner Good idea. I've created: rails/rails#48904 |
Edge is now running |
Found this in the rails docs server logs:
|
I noticed that the Rails 7.1 API documentation was released using Personally, there are a few improvements I would like to make in the future, but I feel like we are at a good spot for a release. Though I would like to get some opinions on #325, and possibly include that. |
I would like to catch up with @AmandaPerino to make sure we're on the same page before cutting a major release, now that RailsWorld is over hopefully there will be more cycles to focus on this stuff. |
Sounds good. That being the case, I've updated the ref in Rails |
I was looking at docs and noticed some codeblocks are highlighted in a wrong way, specifically around erb. https://api.rubyonrails.org/v7.2.1.2/classes/ActionView/Helpers/FormHelper.html#method-i-form_with for example is interpreted as xml. Checking out the repo, I see this is already solved by switching to rogue and edgeguides look pretty good in that regard. It's much more colorful (ruby code has more highlighting), and seems to do a better job at choosing the right language. It would be nice to see this in released api docs some time 😉 |
Sorry, I don't want this issue to become a thread to discuss changes we want to see in the next iteration of the API docs, so going to close it. When the time and place is right, let's get feedback and ideas then. |
@zzak Can we release 3.0.0?
There are still some milestone issues but I think main has enough changes to warrant a new release.
This would also allow us to find possible issues on https://edgeapi.rubyonrails.org/
The text was updated successfully, but these errors were encountered: