-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
proper use filter in getTags function #14427
Conversation
Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s). |
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.
LGTM, let see what @deltakosh thinks and I hope it was a bug and not intended :-)
Snapshot stored with reference name: Test environment: To test a playground add it to the URL, for example: https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14427/merge/index.html#WGZLGJ#4600 Links to test babylon tools with this snapshot: https://playground.babylonjs.com/?snapshot=refs/pull/14427/merge To test the snapshot in the playground with a playground ID add it after the snapshot query string: https://playground.babylonjs.com/?snapshot=refs/pull/14427/merge#BCU1XR#0 |
I did not write that code but I remember it :) |
Since we're adding as a breaking change anyway, I'm renaming forEach to filter to make its function clearer 🙂 |
Changing the name of a variable is not a really breaking change. it doesn't change a thing when calling the function. |
Do I understand correctly, the migration of the breaking change is simply the following? |
Sorry for the misunderstanding here. Yes to have same behavior you could do |
Fix #14424