-
Notifications
You must be signed in to change notification settings - Fork 234
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
ffjson failed to force regenerate, sometimes just re-run works #240
Comments
I think the problems you are have all come from the way ffjson works. ffjson doesn't inspect the Go code to find out which structs exist instead if compiles and runs a program with all the source and then uses reflect to find out information about all the structs. This results in issues when the program can't build for example because the old source still uses a field you removed. I always remove the old generated file before I generate a new one and this always works. I guess ffjson should do this automatically, but it doesn't. |
I do remove old file trick as well; so the
would you agree this project is no longer maintained? there are a couple of pending PRs for @pquerna to take care; I will see if last commit remains there in 2017 after this October will be more than 1 year no maintenance I will have to research some fork or alternatives. |
Looks like its no longer maintained no. Some of the pull requests and issues are easy to deal with and would have been if it was still maintained 😢 |
I have an api project uses ffjson to generate code handling json, use the
ffjson -force-regenerate $GOFILE
to always regenerate,Met two problems:
import ()
only, just re-run the same force-regenerate would fix and got a good generated file;Extra
from a data structure and re-generate, wonder why theforce-regenerate
need to look at the previously generated./admin_rest_ffjson.go
? Doesn't theforce-regenerate
mean to forget whatever existing code just force regenerate? The workaround is simple: just remove the./admin_rest_ffjson.go
beforego generate
Is this project Abandoned?
am checking many other open issues on this board seeing many ones have months no response at all; wonder is this project abandoned ? nobody is fixing any bugs ?
The text was updated successfully, but these errors were encountered: