-
-
Notifications
You must be signed in to change notification settings - Fork 493
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
export keys are not correct #273
Comments
I submitted a PR trying to fix this issue. I pass the field to the "async" func and let async call export with this parameter to avoid nested export key. |
Should we just put something in docs in the meantime? If this isn't being merged, then point out that file names are wrong, rather than that the filename is the first param to be passed in. |
Yes, this took me hours to figure out. Would be very helpful to flag it in the docs with a workaround. Here's what I used: const fixedKey = key.split(".").slice(-1)[0]; |
This is now fixed in v0.7.23 |
in current recur implementation of export, the result key is somehow got all connected with dot. so instead of "reg, cfg, map, ctx", now the exported keys are "reg, reg.cfg, reg.cfg.map, reg.cfg.map.ctx"
The text was updated successfully, but these errors were encountered: