-
Notifications
You must be signed in to change notification settings - Fork 143
Overhaul trophy conditions #6391
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
base: 6.3-condition-notice
Are you sure you want to change the base?
Conversation
…ed via RebuildData.
…his prevents the form from immediately displaying an error message that the Conditions field has not been filled in.
…t (no added condition) returns `false` for this function either.
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.
Overall I don’t like how the runtime cache is being used. Littering the code with cache*IDs()
is not a solution but a hacky workaround.
Generally speaking, we usually know which trophies are being requested, so why not group them in a collection and fix this instead of making this an afterthought?
wcf\data\file\File