-
Notifications
You must be signed in to change notification settings - Fork 100
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
Spring Data Envers Documentation Only Contains General Spring Data Information #61
Comments
It has been three years, and the documentation is still non-existent. Why is this project still part of the spring framework? |
I am happy to help to improve the docs if needed. |
@scordio Help is always welcome. |
@schauder may I ask for some pointers about the documentation source files? https://github.com/spring-projects/spring-data-envers/tree/master/src/main/asciidoc seems to be empty so I'm wondering where they are actually stored. |
@scordio Sure. https://github.com/spring-projects/spring-data-envers/tree/master/src/main/asciidoc isn't empty, there is an We typically create a separate file for the main documentation which then gets included. The canonical name would be You might want to take a look in the corresponding source files in other projects, for example Spring Data JDBC https://github.com/spring-projects/spring-data-jdbc/tree/master/src/main/asciidoc |
Thanks and sorry, I thought I opened that file 🤦 |
Closes #61 See spring-projects/spring-data-examples#603 Original pull request: #279.
Closes #61 See spring-projects/spring-data-examples#603 Original pull request: #279.
The Spring Data Envers Documentation Link in the README file appears to be showing only the general Spring Data Commons information, and no specific details about working with spring-data-envers. The sections are all related to general CrudRepository usage, and 'Envers' only appears in the page header ('revision' doesn't appear anywhere in that document). This is also an issue for older versions of the documentation. I'm assuming that the links are just referring to the wrong documents somehow, so hopefully this is an easy fix. Apologies if this isn't the correct place to submit this feedback.
The text was updated successfully, but these errors were encountered: