Skip to content

case sensitivity issue on image extension. fixed. #4

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.

Sign up for GitHub

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

Merged
OpenTransitLab merged 2 commits into from
Nov 24, 2025
+2 −2
Merged

case sensitivity issue on image extension. fixed. #4

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
dd95e99
case sensitivity fix on image extension.
Nov 24, 2025
e6eaa64
Merge branch 'OpenTransitLab:develop' into develop
S-Nakib Nov 24, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion documentation/docs/patterns/commands-and-events/overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -84,7 +84,7 @@ When the `OrderProcessed` message is published to its Publish Endpoint, the brok

So let's see how the topology looks like from a Generic Broker's Perspective.

![ Commands and Events Topology ](/images/patterns/commands-and-events/generic-broker-topology.png)
![ Commands and Events Topology ](/images/patterns/commands-and-events/generic-broker-topology.PNG)

---

Expand Down
2 changes: 1 addition & 1 deletion documentation/docs/tutorials/basic-communication.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -126,7 +126,7 @@ Since this Configurations aren't RabbitMQ specific, and you may use any other br
In this project, we work with two message types: **SubmitOrder** and **ProcessOrder**.
Based on these message types, the topology is set up in the following way:

![ Generic Broker Topology](/images/tutorials/basic-communication/topology.png)
![ Generic Broker Topology](/images/tutorials/basic-communication/topology.PNG)

1. **Two Publish Endpoints and Two Receive Endpoints are created**, one pair for each message type.
2. Each `IConsumer<T>` is automatically subscribed to the **Receive Endpoint** for its message type **T**.
Expand Down