Skip to content

feat: Redoc v3.0.0#2735

Open
AlexVarchuk wants to merge 4 commits intomainfrom
v3.0.0
Open

feat: Redoc v3.0.0#2735
AlexVarchuk wants to merge 4 commits intomainfrom
v3.0.0

Conversation

@AlexVarchuk
Copy link
Collaborator

@AlexVarchuk AlexVarchuk commented Oct 23, 2025

What/Why/How?

Redoc v3.0.0 release:

  • Modern UI
  • New Search Functionality
  • Native Dark Theme Support
  • Deep CSS Variable Customisation

Reference

Tests

Screenshots (optional)

Screenshot 2025-10-23 at 14 42 10 Screenshot 2025-10-23 at 14 42 02 ## Check yourself
  • Code is linted
  • Tested
  • All new/updated code is covered with tests

@AlexVarchuk AlexVarchuk requested review from a team as code owners October 23, 2025 12:42
@AlexVarchuk AlexVarchuk force-pushed the v3.0.0 branch 8 times, most recently from 5eacf46 to c01c687 Compare October 24, 2025 15:40
Co-authored-by: Roman Hotsiy <gotsijroman@gmail.com>
Co-authored-by: Alex Varchuk <olexandr.varchuk@gmail.com>
Co-authored-by: Oprysk Vyacheslav <vyacheslav@redocly.com>
Co-authored-by: Ivan Kropyvnytskyi <130547411+ivankropyvnytskyi@users.noreply.github.com>
Co-authored-by: Yevhen Pylyp <yevhen.pylyp@redocly.com>
Co-authored-by: Vladyslav Makarenko <vladyslav.makarenko@redocly.com>
Co-authored-by: Yevhenii Medviediev <yevhenii.medviediev@redocly.com>
Co-authored-by: Oleksii Horbachevskyi <oleksii.horbachevskyi@redocly.com>
Co-authored-by: volodymyr-rutskyi <rutskyi.v@gmail.com>
Co-authored-by: Adam Altman <adam@redoc.ly>
Co-authored-by: Andrew Tatomyr <andrew.tatomyr@redocly.com>
Co-authored-by: Anastasiia Derymarko <anastasiia@redocly.com>
Co-authored-by: Roman Marshevskyy <roman.marshevskyy@redoc.ly>
Co-authored-by: Lorna Mitchell <lorna.mitchell@redocly.com>
Co-authored-by: Taylor Krusen <taylor.krusen@redocly.com>
@Poltuu
Copy link

Poltuu commented Dec 18, 2025

out of curiosity, will this support OpenAPI 3.2 ? #2746

@coddingtonbear
Copy link

coddingtonbear commented Jan 10, 2026

out of curiosity, will this support OpenAPI 3.2 ? #2746

Looking at the branch, it looks like it will:

additionalOperations?: Record<string, OpenAPIOperation>;

@Postremus
Copy link

@AlexVarchuk is routingBasePath expected to work with 3.0.0.rc0? Redocly does not load, when I set it to a value other than /.

@AlexVarchuk
Copy link
Collaborator Author

AlexVarchuk commented Jan 29, 2026

out of curiosity, will this support OpenAPI 3.2 ? #2746

@Poltuu not full support yet, we are still working on it. We are planning add it until the major release.

@AlexVarchuk
Copy link
Collaborator Author

@AlexVarchuk is routingBasePath expected to work with 3.0.0.rc0? Redocly does not load, when I set it to a value other than

@Postremus, Hey, it's not working now.
But it should works without this options in different path.
If you have a problem, as a temporary solution,n use router: hash.
You can describe your use case here, and we will try to fix it until the next major release.

<redoc router="hash" spec-url="https://raw.githubusercontent.com/Redocly/redoc/refs/heads/main/demo/museum.yaml"></redoc>

@Postremus
Copy link

@AlexVarchuk Thanks for the response.

My initial problem was, that redocly mostly works correctly when I just host it in a path other than /.
E.g. I have in directory /redoc my index.html, where I define redocly and its config options.

For most of the links in the side bar - this works. I.e. If I click on an operation, I stay in /redoc/ - and the operation is just appended to the path (with a #).

However, this does not work for schema-definitions-tag-name="Schemas". If I click on the Schemas section in the sidebar and on of the schemas inside, my browser url is then changed to /. I.e. it does not contain the /redoc path anymore after I click on the schema-definitions-tag-name section.

After I found this issue, my hope was that routingBasePath would solve my problems, but just caused others :D

I can prepare a small reproducer if that helps?

@AlexVarchuk
Copy link
Collaborator Author

@Postremus, I see the issue. Try to use router="hash", I know the route is ugly, but it works in my case. We'll fix it until the major release.

@Postremus
Copy link

Thanks! will do :)

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants