Skip to content
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

Added property to dinamically get the GooglePlayGames root directory … #2120

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

mirkoaquaro
Copy link

…path

In the previous version of GPGSUtil.cs the GooglePlayGames directory path was hardcoded in all the fields requiring it, making it impossible to move the folder from "Assets" into a subfolder.

With this new version the issue is fixed and the GooglePlayGames directory can now be moved in any another project folder making it cleaner, tidier and less bloated.

…path

In the previous version of GPGSUtil.cs the GooglePlayGames directory path was hardcoded in all the fields requiring it, making it impossible to move the folder from "Assets" into a subfolder.

With this new version the issue is fixed and the GooglePlayGames directory can now be moved in any another project folder making it cleaner, tidier and less bloated.
@googlebot
Copy link

Thanks for your pull request. t looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.


What to do if you already signed the CLA

Individual signers
Corporate signers
  • Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the project maintainer to go/cla#troubleshoot.
  • The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
  • The email used to register you as an authorized contributor must also be attached to your GitHub account.

@mirkoaquaro
Copy link
Author

mirkoaquaro commented Feb 25, 2018 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants