Microsoft/alguidelines
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

change nav 1-patterns formatting

Browse source
This commit is contained in:
christianbraeunlich 2021-12-05 19:02:27 +01:00
parent ba12637e35
commit 7e4e21d223
54 changed files with 211 additions and 250 deletions
Download patch file Download diff file Expand all files Collapse all files

4
content/NAVPatterns/1-patterns/discovery-event/index.md
View file

@ -2,7 +2,7 @@
title = "Discovery Event"
weight = 500
+++
by waldo
_by waldo_
# Abstract
@ -51,7 +51,7 @@ When you publish an event, it should obviously be raised somewhere in the code a
## Step 3: Create one or more global functions, so that your subscriber can call into your functionality to configure, set up, or do whatever it needs to do to make itself discoverable
The generic functionality that I want to call, should be part of the main class - in this case the**Module Discovery** class, or better, the table (**Module Status**). In this table, I create this global function, because I want to make it available for the subscribers:
The generic functionality that I want to call, should be part of the main class - in this case the **Module Discovery** class, or better, the table (**Module Status**). In this table, I create this global function, because I want to make it available for the subscribers:
[![ ][image3]][anchor3]
The business logic doesn't really matter for this pattern. This is obviously dependent on the functionality where you would like to implement the pattern.