mirror of https://github.com/d0zingcat/gocryptotrader.git synced 2026-05-22 07:26:50 +00:00

Files

Adrian Gallagher d64d56f77c build/ci: Update Go to v1.24, golangci-lint to v1.64.6 and fix issues (#1804 )

* build/ci: Update Go to v1.24, golangci-lint to v1.64.5 and fix issues

* Address shazbert's nitters

* linter/config: Fix new linter issue and use versionSize const

* Address gk's nitters and fix additional linter issue after rebase

* Address glorious nits

* staticcheck: Fix additional linter issues after upgrading to Go 1.24.1 and golangci-lint v1.64.6

Also addresses nits

* Improve testing, assertify usage and use common.ErrParsingWSField

* TestCreateNewStrategy: Replace must > should wording

2025-03-10 16:33:55 +11:00

main.go

build/ci: Update Go to v1.24, golangci-lint to v1.64.6 and fix issues (#1804 )

2025-03-10 16:33:55 +11:00

README.md

docs: Migrate development tracking from Trello to GitHub Projects (#1696 )

2024-11-08 10:10:49 +11:00

README.md

GoCryptoTrader Backtester: Strategyconfigbuilder package

This strategyconfigbuilder package is part of the GoCryptoTrader codebase.

This is still in active development

You can track ideas, planned features and what's in progress on our GoCryptoTrader Kanban board.

Join our slack to discuss all things related to GoCryptoTrader! GoCryptoTrader Slack

Strategyconfigbuilder package overview

What does the config builder do?

The config builder runs you through the process of creating a strategy config (.strat) file. Configs can also be generated via test code under config_test.go. Once the config is created, when running the backtester, you can reference it via go run . -configpath=(path-to-strat-file)

How do I run it?

go run .

Anything else?

The config builder will ask you all the necessary questions required to create a config file. If there is anything confusing, feel free to ask a question in our Slack group or open an issue!

Please click GoDocs chevron above to view current GoDoc information for this package

Contribution

Please feel free to submit any pull requests or suggest any desired features to be added.

When submitting a PR, please abide by our coding guidelines:

Code must adhere to the official Go formatting guidelines (i.e. uses gofmt).
Code must be documented adhering to the official Go commentary guidelines.
Code must adhere to our coding style.
Pull requests need to be based on and opened against the master branch.

Donations

If this framework helped you in any way, or you would like to support the developers working on it, please donate Bitcoin to:

bc1qk0jareu4jytc0cfrhr5wgshsq8282awpavfahc