Skip to content
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

Write up documentation on posthog-dotnet #10589

Merged
merged 26 commits into from
Feb 10, 2025
Merged

Conversation

haacked
Copy link
Contributor

@haacked haacked commented Feb 6, 2025

Changes

This adds documentation for the posthog-dotnet library. Let me know if I missed anything.

Checklist

  • Words are spelled using American English
  • Titles are in sentence case
  • Feature names are in sentence case too
  • Use relative URLs for internal links
  • If I moved a page, I added a redirect in vercel.json
  • Remove this template if you're not going to fill it out!

Copy link

vercel bot commented Feb 6, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
posthog ✅ Ready (Inspect) Visit Preview Feb 10, 2025 3:34pm

@haacked
Copy link
Contributor Author

haacked commented Feb 6, 2025

  • C# code samples aren't syntax highlighted. Figured it out
  • When running locally, the feature flags section is loading python content. Clearing cache did the trick.

Scrolling horizontally is not nice.
I changed the method names in the .NET lib to more closely match the names in the other libraries.
Copy link
Contributor

@ivanagas ivanagas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is awesome, thank you! A bunch of minor corrections mostly.

Some other areas to add a few details:

  • /docs/product-analytics/capture-events
  • /docs/feature-flags/adding-feature-flag-code
  • /docs/experiments/installation
  • /docs/experiments/adding-experiment-code

I can also do this if you're busy.

After making the changes, I think we are good to go 🥳

contents/docs/libraries/dotnet/index.mdx Outdated Show resolved Hide resolved
contents/docs/libraries/dotnet/index.mdx Outdated Show resolved Hide resolved
contents/docs/libraries/dotnet/index.mdx Outdated Show resolved Hide resolved
contents/docs/libraries/dotnet/index.mdx Outdated Show resolved Hide resolved
contents/docs/libraries/dotnet/index.mdx Outdated Show resolved Hide resolved
contents/docs/integrate/_snippets/install-dotnet.mdx Outdated Show resolved Hide resolved
contents/docs/product-analytics/installation.mdx Outdated Show resolved Hide resolved
contents/docs/feature-flags/installation.mdx Outdated Show resolved Hide resolved
@haacked
Copy link
Contributor Author

haacked commented Feb 7, 2025

I can also do this if you're busy.

I’d like to do it. It’ll help me understand how the docs are laid out better. Thanks for the feedback!

@haacked haacked enabled auto-merge (squash) February 10, 2025 15:13
@haacked haacked merged commit 4fa912d into master Feb 10, 2025
3 checks passed
@haacked haacked deleted the haacked/dotnet-library branch February 10, 2025 15:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants