You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Workshop.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ Before starting, make sure you have:
9
9
10
10
- Completed the setup instructions in the [README](README.md)
11
11
- The application running via .NET Aspire
12
-
- Access to the Aspire Dashboard at https://localhost:15888
12
+
- Access to the Aspire Dashboard at <https://localhost:15888>
13
13
- Make sure the Docker containers are running
14
14
15
15
## Workshop Flow
@@ -92,7 +92,7 @@ You should see the statistics header toggle on and off based on your feature fla
92
92
3. Implement a Custom Provider
93
93
94
94
- Create a new class `CustomFeatureProvider` in `src/Garage.ServiceDefaults/Providers`
95
-
-Use the `FeatureProvider` base class. Tip: You can implement a dictionary with the same flag keys and default values as used in the environment variables
95
+
-Look at the `FeatureProvider` base class. Tip: You can try access the environment variables directly in the `CustomFeatureProvider` class
96
96
- Add the provider to the OpenFeature configuration in `Extensions.cs`
97
97
98
98
4. Replace the IFeatureFlags dependency injection
@@ -203,7 +203,7 @@ reflected in real-time without restarting the application.
203
203
204
204
- Consider how you might change this value without redeploying
205
205
- Think about gradual rollout scenarios (e.g., 10% of users get faster performance)
206
-
- Look into https://flagd.dev/playground/ for the fractional rollout feature example
206
+
- Look into <https://flagd.dev/playground/> for the fractional rollout feature example
207
207
208
208
### Expected Outcome
209
209
@@ -319,7 +319,7 @@ You will have implemented a basic A/B test using feature flags, allowing you to
319
319
320
320
2. Visualize Flag Usage
321
321
322
-
- Open the Aspire dashboard at https://localhost:15888
322
+
- Open the Aspire dashboard at <https://localhost:15888>
323
323
- Visit the `Traces` section
324
324
- Look for traces related to feature flag evaluations
325
325
- Check the `Metrics` section for flag usage statistics
@@ -344,11 +344,11 @@ You will have integrated telemetry for feature flags, allowing you to monitor th
344
344
## Extra Exercises: Custom Hooks
345
345
346
346
- Implement custom hooks for feature flag evaluations
347
-
- Use hooks to log flag evaluation behavior (see https://openfeature.dev/docs/reference/concepts/hooks/)
347
+
- Use hooks to log flag evaluation behavior (see <https://openfeature.dev/docs/reference/concepts/hooks/>)
348
348
349
349
## Extra Exercises: Event Handlers
350
350
351
-
- Add an event handler to listen to flag changes (see https://openfeature.dev/specification/sections/events)
351
+
- Add an event handler to listen to flag changes (see <https://openfeature.dev/specification/sections/events>)
352
352
353
353
---
354
354
@@ -395,7 +395,7 @@ Congratulations! You've completed the OpenFeature .NET workshop. You should now
395
395
396
396
### Next Steps
397
397
398
-
- Explore other OpenFeature providers (https://openfeature.dev/ecosystem)
398
+
- Explore other OpenFeature providers (<https://openfeature.dev/ecosystem>)
399
399
- Implement feature flags in your own applications
0 commit comments