-
Notifications
You must be signed in to change notification settings - Fork 1
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
Venus/test1 #4
Venus/test1 #4
Conversation
✅ Deploy Preview for scu-virtual-tours ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
"x": -22.96102305361865, | ||
"y": 1.21997231224456693, | ||
"z":-9.258993120824082 | ||
"x": -23.5, |
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 like this position, looks much better and not in the way of the user's path.
version "7.16.7" | ||
resolved "https://registry.npmjs.org/@babel/code-frame/-/code-frame-7.16.7.tgz" | ||
integrity sha512-iAXqUn8IIeBTNd72xsFlgaXHkMBMt6y4HJp1tIaK465CWLT/fG1aqB7ykr95gHHmlBdGbFeWWfyB4NJJ0nmeIg== | ||
version "7.22.10" |
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'm not sure how the yarn.lock got changed because it is supposed to only update when there are dependency changes, meaning package.json was changed. I checked out your branch and ran from my side with yarn install, and didn't update the yarn.lock. So, I guess we don't need to worry about it now but keep an eye out if next time your yarn.lock still gets updated despite no dependency changes. We might be able to find a pattern.
Here is the link talking about yarn.lock: yarnpkg/yarn#4379
Adjusted the coordinates of one of the signs; still just mostly getting used to using git for collaboration again.