-
-
Notifications
You must be signed in to change notification settings - Fork 151
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(api): Updates API changlog #4745
base: main
Are you sure you want to change the base?
Conversation
1bf2a05
to
cb0280e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we can do a bit more here:
- Include links to the PRs and issues.
- Update the API pages to say v4.1 instead of v4.0.
- Link to the documentation for each feature from the release notes.
I think it's also worth separating the many enhancements into a bulleted list or something. It's a bit tricky to realize that the various sentences are orthogonal to each other.
@mlissner I've applied your suggestions, and here's the updated v4.1 section: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks close.
The ordering comment isn't quite right though. The order_by
parameter wasn't added, just additional fields to use with it:
A couple little tweaks too. It's important to get this right so that we can advertise all the little enhancements.
Thank you!
(<a href="https://github.com/freelawproject/courtlistener/issues/4061">Issue #4061</a>, <a | ||
href="https://github.com/freelawproject/courtlistener/pull/4700">PR #4700</a>). | ||
</li> | ||
<li><strong>Deeper Filtering for Parties and Attorneys:</strong> The <a href="{% url "pacer_api_help" %}#party-endpoint">parties</a> and <a href="{% url "pacer_api_help" %}#attorney-endpoint">attorneys</a> API endpoint has been upgraded with the filter_nested_results=True query parameter. This enables granular filtering of nested data, providing more control over the retrieved information. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
<li><strong>Deeper Filtering for Parties and Attorneys:</strong> The <a href="{% url "pacer_api_help" %}#party-endpoint">parties</a> and <a href="{% url "pacer_api_help" %}#attorney-endpoint">attorneys</a> API endpoint has been upgraded with the filter_nested_results=True query parameter. This enables granular filtering of nested data, providing more control over the retrieved information. | |
<li><strong>Deeper Filtering for Parties and Attorneys:</strong> The <a href="{% url "pacer_api_help" %}#party-endpoint">parties</a> and <a href="{% url "pacer_api_help" %}#attorney-endpoint">attorneys</a> API endpoint has been upgraded with the <code>filter_nested_results=True</code> query parameter. This enables granular filtering of nested data, providing more control over the retrieved information. |
@@ -24,7 +24,7 @@ <h4 class="v-offset-below-2"> | |||
{% include "includes/toc_sidebar.html" %} | |||
</div> | |||
<div class="col-xs-12 col-md-8 col-lg-6"> | |||
<h1 id="about">REST API – v4.0</h1> | |||
<h1 id="about">REST API – v4.1</h1> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's catch this in the HTML title too.
This PR closes #4678 by updating the REST API changelog template to reflect all changes made during the recent sprint cycle.
Note: This PR should be merged once all sub-issues related to #4678 are resolved.