Skip to content

Bring the docs up to date with review text, review search and the new MCP features - #21

Merged
stphnwlsh merged 4 commits into
mainfrom
fix/docs-for-review-text
Nov 7, 2026
Merged

Bring the docs up to date with review text, review search and the new MCP features#21
stphnwlsh merged 4 commits into
mainfrom
fix/docs-for-review-text

Conversation

@stphnwlsh

@stphnwlsh stphnwlsh commented Nov 6, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Summary

The template PRs merged on 6 November changed things the docs show, so the pages caught up:

  • Recognisable sample titles. Every example now uses the new seed: query=space finds Deep Space Gardeners and three more. The ids, counts and averages come from the five templates running on main. The getting-started jokes moved on from the buzzword titles.
  • Review text and search. Reviews have optional text (up to 1000 characters) when you create, update and read them. Listing reviews takes query (matches the text) and minStars. The Minimal API, Web API, GraphQL and Lambda references show both, and the REST pages have a search example.
  • MCP.
    • Two new prompts, summarise_movie_reviews and summarise_author_reviews.
    • The movies://top-rated resource.
    • Ids complete in prompts and resource templates.
    • Tool results carry resource_link blocks.
    • Tools, prompts and resources have icons.
    • Missing values are written as null with anyOf schemas.
    • reviews_write takes text.
    • The version resource is named server_version.
    • The optional Open WebUI chat demo has its own section in Run it locally.
  • Ports. dotnet run has listened on 8080/8081 since the launch settings change on 2 November, and it redirects HTTP to HTTPS. Minimal API, MCP and GraphQL still said 5032/7032. The dotnet run examples now use https://localhost:8081 and say to run dotnet dev-certs https --trust once. Docker Compose only listens on HTTP, so its examples keep http://localhost:8080. MCP clients are pointed at the Compose address, because they may not trust the development certificate.
  • Auth wording. The reference intros said every endpoint requires authorization. They now say that applies to a solution created with --include-auth.

MCP's review search (CleanModelContextProtocol#57) is still open, so reviews_list doesn't show query or minStars yet. The matching RUN.md fix is in CleanMinimalApi#81, CleanModelContextProtocol#61, CleanGraphQLApi#61 and CleanWebApi#55.

@stphnwlsh
Bring the docs up to date with review text, review search and the new…
4a55bda 
… MCP features

The sample movies have recognisable titles now, so every example shows the
new ids and numbers. Reviews have text and can be searched by it and by a
minimum star rating. MCP has two more prompts, a top rated resource, id
completions, resource links, icons, null fields and an optional chat demo.
dotnet run listens on port 8080 now, not 5032.
@stphnwlsh stphnwlsh self-assigned this Nov 6, 2026
@stphnwlsh
Use the HTTPS address in the dotnet run examples
c6af68d 
dotnet run redirects http://localhost:8080 to https://localhost:8081, so a
curl against the HTTP address got an empty 307. The examples use the HTTPS
address and say to trust the development certificate once. Docker Compose
only listens on HTTP, so its examples keep http://localhost:8080.
@stphnwlsh
Name both dotnet run ports in the Stuck tips
5a6d00c
This was referenced Nov 6, 2026
Merged
Merged
Merged
Merged
Merged
stphnwlsh added a commit to LeanMeanCleanApps/CleanMinimalApi that referenced this pull request Nov 7, 2026
@stphnwlsh
Say that dotnet run redirects HTTP to HTTPS (#81)
498c88c 
## Summary

RUN.md said the app only redirects HTTP to HTTPS outside `local` and
`Development`. Only HSTS is off there; `UseHttpsRedirection` always
runs, so under `dotnet run` <http://localhost:8080> redirects to
<https://localhost:8081>, and a plain `curl` gets an empty 307. RUN.md
now says what `dotnet run` listens on, that HTTP redirects, and how to
trust the development certificate. The behaviour stays as it is.

The same change in the other templates:
[MCP](LeanMeanCleanApps/CleanModelContextProtocol#61),
[GraphQL](LeanMeanCleanApps/CleanGraphQLApi#61),
[Web API](LeanMeanCleanApps/CleanWebApi#55). The
docs site follows in LeanMeanCleanApps/leanmeancleanapps.github.io#21.

## Related issues

None.

## Type of change

- [ ] Bug fix
- [ ] New feature
- [ ] Breaking change (the generated solution or template parameters
change in a way existing users will notice)
- [ ] Refactoring or clean-up
- [x] Documentation
- [ ] Build, pipeline or dependency update

## Shared layers

- [x] This only touches the Presentation layer of this template.
- [ ] This touches the Application or Infrastructure layers, tests,
pipeline or repository setup, so it needs to be carried across all five
templates.

## Checklist

- [ ] `dotnet build` and `dotnet test` pass locally with no warnings.
- [ ] I added or updated tests, and line coverage stays at or above 95%.
- [x] I updated the README or docs where behaviour changed.
- [ ] If this changes how we do something, I updated the matching skill
in `.agents/skills`.
- [ ] I checked the template still installs and creates a working
solution (see CONTRIBUTING.md).
stphnwlsh added a commit to LeanMeanCleanApps/CleanWebApi that referenced this pull request Nov 7, 2026
@stphnwlsh
Say that dotnet run redirects HTTP to HTTPS (#55)
dc0bef2 
## Summary

RUN.md said the app only redirects HTTP to HTTPS outside `local` and
`Development`. Only HSTS is off there; `UseHttpsRedirection` always
runs, so under `dotnet run` <http://localhost:8080> redirects to
<https://localhost:8081>, and a plain `curl` gets an empty 307. RUN.md
now says what `dotnet run` listens on, that HTTP redirects, and how to
trust the development certificate. The behaviour stays as it is.

The same change in the other templates: [Minimal
API](LeanMeanCleanApps/CleanMinimalApi#81),
[MCP](LeanMeanCleanApps/CleanModelContextProtocol#61),
[GraphQL](LeanMeanCleanApps/CleanGraphQLApi#61).
The docs site follows in
LeanMeanCleanApps/leanmeancleanapps.github.io#21.

## Related issues

None.

## Type of change

- [ ] Bug fix
- [ ] New feature
- [ ] Breaking change (the generated solution or template parameters
change in a way existing users will notice)
- [ ] Refactoring or clean-up
- [x] Documentation
- [ ] Build, pipeline or dependency update

## Shared layers

- [x] This only touches the Presentation layer of this template.
- [ ] This touches the Application or Infrastructure layers, tests,
pipeline or repository setup, so it needs to be carried across all five
templates.

## Checklist

- [ ] `dotnet build` and `dotnet test` pass locally with no warnings.
- [ ] I added or updated tests, and line coverage stays at or above 95%.
- [x] I updated the README or docs where behaviour changed.
- [ ] If this changes how we do something, I updated the matching skill
in `.agents/skills`.
- [ ] I checked the template still installs and creates a working
solution (see CONTRIBUTING.md).
stphnwlsh added a commit to LeanMeanCleanApps/CleanGraphQLApi that referenced this pull request Nov 7, 2026
@stphnwlsh
Say that dotnet run redirects HTTP to HTTPS (#61)
664f366 
## Summary

RUN.md said the app only redirects HTTP to HTTPS outside `local` and
`Development`. Only HSTS is off there; `UseHttpsRedirection` always
runs, so under `dotnet run` <http://localhost:8080> redirects to
<https://localhost:8081>, and a plain `curl` gets an empty 307. RUN.md
now says what `dotnet run` listens on, that HTTP redirects, and how to
trust the development certificate. The behaviour stays as it is.

The same change in the other templates: [Minimal
API](LeanMeanCleanApps/CleanMinimalApi#81),
[MCP](LeanMeanCleanApps/CleanModelContextProtocol#61),
[Web API](LeanMeanCleanApps/CleanWebApi#55). The
docs site follows in LeanMeanCleanApps/leanmeancleanapps.github.io#21.

## Related issues

None.

## Type of change

- [ ] Bug fix
- [ ] New feature
- [ ] Breaking change (the generated solution or template parameters
change in a way existing users will notice)
- [ ] Refactoring or clean-up
- [x] Documentation
- [ ] Build, pipeline or dependency update

## Shared layers

- [x] This only touches the Presentation layer of this template.
- [ ] This touches the Application or Infrastructure layers, tests,
pipeline or repository setup, so it needs to be carried across all five
templates.

## Checklist

- [ ] `dotnet build` and `dotnet test` pass locally with no warnings.
- [ ] I added or updated tests, and line coverage stays at or above 95%.
- [x] I updated the README or docs where behaviour changed.
- [ ] If this changes how we do something, I updated the matching skill
in `.agents/skills`.
- [ ] I checked the template still installs and creates a working
solution (see CONTRIBUTING.md).
stphnwlsh added a commit to LeanMeanCleanApps/CleanModelContextProtocol that referenced this pull request Nov 7, 2026
@stphnwlsh
Say that dotnet run redirects HTTP to HTTPS (#61)
d7062ff 
## Summary

RUN.md said the app only redirects HTTP to HTTPS outside `local` and
`Development`. Only HSTS is off there; `UseHttpsRedirection` always
runs, so under `dotnet run` <http://localhost:8080> redirects to
<https://localhost:8081>, and a plain `curl` gets an empty 307. RUN.md
now says what `dotnet run` listens on, that HTTP redirects, and how to
trust the development certificate. The behaviour stays as it is.

The same change in the other templates: [Minimal
API](LeanMeanCleanApps/CleanMinimalApi#81),
[GraphQL](LeanMeanCleanApps/CleanGraphQLApi#61),
[Web API](LeanMeanCleanApps/CleanWebApi#55). The
docs site follows in LeanMeanCleanApps/leanmeancleanapps.github.io#21.

## Related issues

None.

## Type of change

- [ ] Bug fix
- [ ] New feature
- [ ] Breaking change (the generated solution or template parameters
change in a way existing users will notice)
- [ ] Refactoring or clean-up
- [x] Documentation
- [ ] Build, pipeline or dependency update

## Shared layers

- [x] This only touches the Presentation layer of this template.
- [ ] This touches the Application or Infrastructure layers, tests,
pipeline or repository setup, so it needs to be carried across all five
templates.

## Checklist

- [ ] `dotnet build` and `dotnet test` pass locally with no warnings.
- [ ] I added or updated tests, and line coverage stays at or above 95%.
- [x] I updated the README or docs where behaviour changed.
- [ ] If this changes how we do something, I updated the matching skill
in `.agents/skills`.
- [ ] I checked the template still installs and creates a working
solution (see CONTRIBUTING.md).
@stphnwlsh
stphnwlsh merged commit 9a1b782 into main Nov 7, 2026
5 checks passed
@stphnwlsh
stphnwlsh deleted the fix/docs-for-review-text branch November 7, 2026 02:55
This was referenced Nov 7, 2026
Closed
Closed
Closed
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

@stphnwlsh stphnwlsh

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@stphnwlsh