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
I recently starting using vervet for the first time and ran into a bug where I had to manually recreate an embed.go placeholder file in order to successfully generate code again after encountering a yaml parsing error.
The steps that led to the bug:
use vervet to generate code/specs successfully
import the generated versions go package (which just contains embed.go) somewhere, e.g. in main.go
attempt to generate again but with a syntax error in one of your spec.yaml files
fix the syntax error, then attempt to generate again
The go compiler will complain about the import of the versions package, since that package is now empty.
This was confusing at first, since I had just bootstrapped the project from our go service template and wasn't very familiar with vervet or how everything was wired up. Luckily I eventually noticed the deletion of embed.go in a git diff, so I manually recreated it and was able to proceed.
A quick look at the code and it seems this is a result of vervet clearing the output directory at the beginning of the build step, so any errors that occur before embed.go is rewritten will lead to this same state.
The text was updated successfully, but these errors were encountered:
Hi,
I recently starting using vervet for the first time and ran into a bug where I had to manually recreate an
embed.go
placeholder file in order to successfully generate code again after encountering ayaml
parsing error.The steps that led to the bug:
versions
go package (which just containsembed.go
) somewhere, e.g. inmain.go
spec.yaml
filesThe go compiler will complain about the import of the
versions
package, since that package is now empty.This was confusing at first, since I had just bootstrapped the project from our go service template and wasn't very familiar with vervet or how everything was wired up. Luckily I eventually noticed the deletion of
embed.go
in agit diff
, so I manually recreated it and was able to proceed.A quick look at the code and it seems this is a result of vervet clearing the output directory at the beginning of the build step, so any errors that occur before
embed.go
is rewritten will lead to this same state.The text was updated successfully, but these errors were encountered: