feat: Feature Experimentation capabilities for Go SDK

Author: Abhi591

.github/workflows/main.yaml

@@ -0,0 +1,39 @@
+name: CI
+
+on:
+  push:
+    branches: [ master, github-action ]
+  pull_request:
+    branches: [ master ]
+
+jobs:
+  build:
+    if: "!contains(toJSON(github.event.commits.*.message), '[skip-ci]')"
+    name: Test on go ${{ matrix.go-version }} and ${{ matrix.os }}
+    runs-on: ${{ matrix.os }}
+    strategy:
+      matrix:
+        os:
+          - ubuntu-latest
+        go-version: [ 1.16, 1.17, 1.18, 1.19, 1.21, 1.22, 1.23]
+
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-go@v5
+        with:
+          go-version: ${{ matrix.go-version }}
+      - name: Run tests
+        run: go test ./test/... -v
+      - name: Upload coverage to Codecov
+        run: |
+          bash <(curl -s https://codecov.io/bash)
+      - name: Notification
+        if: always()
+        id: slack
+        uses: wingify/[email protected]
+        with:
+          channel-id: 'vwo-fs-fme-sdk-job-status'
+          slack-message: "<!here> Go FME SDK Test on *Go-${{ matrix.go-version }}* and *${{ matrix.os }}* got *${{job.status}}* ${{job.status == 'success' && ':heavy_check_mark:' || ':x:'}} \nCommit: `${{github.event.head_commit.message}}`. \nCheck the latest build: https://github.com/wingify/vwo-fme-go-sdk/actions"
+          color: "${{job.status == 'success' && '#00FF00' || '#FF0000'}}"
+        env:
+          SLACK_BOT_TOKEN: ${{ secrets.SLACK_NOTIFICATIONS_BOT_TOKEN }}

.gitignore

@@ -0,0 +1,80 @@
+# Binaries for programs and plugins
+*.exe
+*.exe~
+*.dll
+*.so
+*.dylib
+
+# Test binary, built with `go test -c`
+*.test
+
+# Output of the go coverage tool, specifically when used with LiteIDE
+*.out
+
+# Dependency directories (remove the comment below to include it)
+# vendor/
+
+# Go workspace file
+go.work
+
+# IDE files
+.vscode/
+.idea/
+*.swp
+*.swo
+*~
+
+# OS generated files
+.DS_Store
+.DS_Store?
+._*
+.Spotlight-V100
+.Trashes
+ehthumbs.db
+Thumbs.db
+
+# Logs
+*.log
+
+# Runtime data
+pids
+*.pid
+*.seed
+*.pid.lock
+
+# Coverage directory used by tools like istanbul
+coverage/
+
+# nyc test coverage
+.nyc_output
+
+# Grunt intermediate storage (https://gruntjs.com/creating-plugins#storing-task-files)
+.grunt
+
+# Bower dependency directory (https://bower.io/)
+bower_components
+
+# node_modules
+node_modules/
+
+# Optional npm cache directory
+.npm
+
+# Optional REPL history
+.node_repl_history
+
+# Output of 'npm pack'
+*.tgz
+
+# Yarn Integrity file
+.yarn-integrity
+
+# dotenv environment variables file
+.env
+
+# Build output
+dist/
+build/
+
+# Example directory
+example/

CHANGELOG.md

@@ -0,0 +1,72 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [1.3.0] - 2024-11-06
+
+### Added
+
+- First release of VWO Feature Management and Experimentation capabilities
+
+	```go
+	package main
+
+	import (
+		"fmt"
+		"log"
+
+		vwo "github.com/wingify/vwo-fme-go-sdk"
+	)
+
+	func main() {
+		// Initialize VWO SDK with your account details
+		options := map[string]interface{}{
+			"sdkKey":    "32-alpha-numeric-sdk-key", // Replace with your SDK key
+			"accountId": "123456",                   // Replace with your account ID
+		}
+
+		// Initialize VWO instance
+		vwoInstance, err := vwo.Init(options)
+		if err != nil {
+			log.Fatalf("Failed to initialize VWO client: %v", err)
+		}
+
+		// Create user context
+		context := map[string]interface{}{
+			"id": "unique_user_id", // Set a unique user identifier
+		}
+
+		// Check if a feature flag is enabled
+		getFlag, err := vwoInstance.GetFlag("feature_key", context)
+		if err != nil {
+			log.Printf("Error getting feature flag: %v", err)
+		} else {
+			isFeatureEnabled := getFlag.IsEnabled()
+			fmt.Println("Is feature enabled?", isFeatureEnabled)
+
+			// Get a variable value with a default fallback
+			variableValue := getFlag.GetVariable("feature_variable", "default_value")
+			fmt.Println("Variable value:", variableValue)
+		}
+
+		// Track a custom event
+		trackResponse, err := vwoInstance.TrackEvent("event_name", context)
+		if err != nil {
+			log.Printf("Error tracking event: %v", err)
+		} else {
+			fmt.Println("Event tracked:", trackResponse)
+		}
+
+		// Set multiple custom attributes
+		attributeMap := map[string]interface{}{
+			"attribute-name": "attribute-value",
+		}
+		err = vwoInstance.SetAttribute(attributeMap, context)
+		if err != nil {
+			log.Printf("Error setting attributes: %v", err)
+		}
+	}
+	```

CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+- The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at [email protected]. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

CONTRIBUTING.md

@@ -0,0 +1,42 @@
+## Contributing to VWO Feature Management and Experimentation SDK for Go
+
+We love your input! We want to make contributing to this project as easy and transparent as possible, whether it's:
+
+- Reporting a bug
+- Discussing the current state of the code
+- Submitting a fix
+- Proposing new features
+
+### We Use [Github Flow](https://guides.github.com/introduction/flow/index.html), So All Code Changes Happen Through Pull Requests
+
+Pull requests are the best way to propose changes to the codebase (we use [Github Flow](https://guides.github.com/introduction/flow/index.html)). We actively welcome your pull requests:
+
+1. Fork the repo and create your branch from `master`.
+2. If you've added code that should be tested, add tests.
+3. Ensure the test suite passes.
+4. Make sure your code lints.
+5. Open a pull request!
+
+### Any contributions you make will be under the Apache 2.0 Software License
+
+When you submit code changes, your submissions are understood to be under the same [Apache 2.0 License](http://www.apache.org/licenses/LICENSE-2.0) that covers the project. Feel free to contact the maintainers if that's a concern.
+
+### Report bugs using GitHub issues
+
+We use GitHub issues to track public bugs. Report a bug by [opening a new issue](https://github.com/wingify/vwo-fme-go-sdk/issues); it's that easy!
+
+**Note**: Write bug reports with detail, background, and sample code
+
+**Great Bug Reports** tend to have:
+
+- A quick summary and/or background
+- Steps to reproduce
+  - Be specific!
+  - Give sample code if you can.
+- What you expected would happen
+- What actually happens
+- Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)
+
+### License
+
+By contributing, you agree that your contributions will be licensed under its Apache 2.0 License.