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
Intellisense Documentation Links #3915
Comments
Addressed in elastic/elasticsearch#44487 |
Removing v6.8.1,v7.2.0 and adding v7.4.0, as the upstream fix will be applied to v7.4.0 |
@russcam Does this mean that the intelisense documenation will only be updated from version 7.4 forward? Is it possible to get the older versions updated also? I expect the older versions will be available for a long time so it will have a large impact. |
@Trisped I've asked the question on the upstream change. Typically, a change would be backported to a previous major only if there were to be a new release e.g. a new 6.x version. This change probably would not warrant a release of Elasticsearch, but is useful for the client libraries. Another approach that could be proposed is reinstating the redirects from |
@russcam New releases are preferable, but I understand not doing it since it will be a lot of work to re-release each version. The redirect would be a good work around as long as we are sure we did not miss any of the addresses changes. |
This commit replaces the remaining links to elasticsearch.org with their elastic.co counterparts. Closes #3915
I've opened #4220 to address the final bits in the 7.x client. |
This commit replaces the remaining links to elasticsearch.org with their elastic.co counterparts. Closes #3915
NEST/Elasticsearch.Net version: 6.7.0
Description of the problem including expected versus actual behavior:
I have run into a few places in the intelisense documenation (C#) where the links are broken. For example, the DeleteIndexAsync method on Nest.ElasticClient states:
The link will work if you replace http://www.elasticsearch.org with https://www.elastic.co.
Someone will need to make this change to all instances in the documentation.
The text was updated successfully, but these errors were encountered: