-
Notifications
You must be signed in to change notification settings - Fork 41
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
feat: automatically generated instanceId #226
Conversation
} | ||
}; | ||
``` | ||
The backup file name will follow this pattern: `{fileNameWithoutExtension}-{AppName}-{SdkVersion}.{extension}`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably worth mentioning that we took this out and why
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let me know if this is good enough or if you have a better idea: 00550c7
How does this play with this:
If I'm reading that right this is still spitting out an error onto the error events. I think it shouldn't do that anymore WDYT? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should change the error event but I don't think it's dangerous if you disagree so I'm gonna put an LGTM on it
Yep, addressed in 78cf8c2 |
https://linear.app/unleash/issue/2-2393/make-instance-id-autogenned-c
This drops the
InstanceTag
public property inUnleashSettings
in favor of an internal automatically generatedInstanceId
property. Any reference ofInstanceTag
is nowInstanceId
.File names no longer include
InstanceTag
and instead we're relying on gracefully handling file locks.