mirror of
https://github.com/status-im/status-go.git
synced 2026-08-31 00:51:12 +00:00
Igor Sirotin
f3e4363808
Part of the Go project layout migration, item 27. Pure move plus import-path rewrite across 502 files. No API or behaviour change. `internal/` keeps the messaging application logic unimportable from outside the module, which is what the issue asks for -- status-go is consumed through the C-bindings in mobile/, not as a Go library. Things that had to follow the move, beyond the Go imports: - tools/generate-handlers/template.txt. messenger_handlers.go is generated, and the template hard-codes the imports it emits, so the generated file kept importing protocol/common and failed typecheck. - .gitignore. The ignore rule for that generated file was pinned to the old path; without moving it, a 1486-line generated file starts being tracked. - Makefile: the logosstorage and torrent test targets (both the archive packages and ./protocol itself), the archive README, migration-protocol. - scripts/run_unit_tests.sh, which names the protocol package explicitly to shard its tests. - scripts/cleanup_generated_files.sh and .golangci.yml. scripts/migration_check.sh also needed a fix that is not specific to this move: it validated every file the branch touched under a migration dir against the timestamp naming rule, and a directory rename makes every migration in it look newly added. It now excludes renames, so moving a migration is not mistaken for adding one. refs #7067
18 lines
878 B
Go
18 lines
878 B
Go
// This file is necessary because "github.com/status-im/migrate/v4"
|
|
// can't handle files starting with a prefix. At least that's the case
|
|
// for go-bindata.
|
|
// If go-bindata is called from the same directory, asset names
|
|
// have no prefix and "github.com/status-im/migrate/v4" works as expected.
|
|
|
|
// NOTE: The naming of the file needs to follow the unix timestamp convention
|
|
// unlike the two initial files.
|
|
// That's because currently the encryption migrations and protocol migrations
|
|
// share the same table, which means that the latest migration in terms of filename
|
|
// is from the encryption namespace files, which uses a unix timestamp.
|
|
// If we add 00003_... for example, this will be ignored in existing clients as
|
|
// older than the latest encryption migration.
|
|
|
|
package sqlite
|
|
|
|
//go:generate go tool go-bindata -modtime=1700000000 -pkg migrations -o ../migrations.go .
|