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

Fix sample warnings and add samples to upm metadata #51

Conversation

johanhelsing
Copy link

@johanhelsing johanhelsing commented Aug 26, 2022

Pull request checklist

Please check if your PR fulfills the following requirements:

  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been reviewed and added / updated if needed (for bug fixes / features)
  • No compiler errors or warnings

Pull request type

Please check the type of change your PR introduces:

  • Bugfix
  • Feature
  • Code style update (formatting, renaming)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • Documentation content changes
  • Other (please describe):

Issue Number

Issue Number: #50

Previous attempt: modesttree#220

What is the current behavior?

Adding extenject or triggering re-import produces 54 warnings. Sample games do not show up in package manager.

What is the new behavior?

No warnings because of sample files being outside asmdefs remain.

Samples show up in the inspector

image

Does this introduce a breaking change?

  • Yes
  • No

Other information

On which Unity version has this been tested?

  • 2021.3 LTS
  • 2020.3 LTS
  • 2020.2
  • 2020.1
  • 2019.4 LTS
  • 2019.3
  • 2019.2
  • 2019.1
  • 2018.4 LTS

Scripting backend:

  • Mono
  • IL2CPP

Note: Every pull request is tested on the Continuous Integration (CI) system to confirm that it works in Unity.

Ideally, the pull request will pass ("be green"). This means that all tests pass and there are no errors. However, it is not uncommon for the CI infrastructure itself to fail on specific platforms or for so-called "flaky" tests to fail ("be red"). Each CI failure must be manually inspected to determine the cause.

CI starts automatically when you open a pull request, but only Releasers/Collaborators can restart a CI run. If you believe CI is giving a false negative, ask a Releaser to restart the tests.

@Mathijs-Bakker Mathijs-Bakker merged commit 6760e45 into Mathijs-Bakker:master Aug 30, 2022
@Mathijs-Bakker
Copy link
Owner

Merged.
Thank you Johan!

@Mathijs-Bakker
Copy link
Owner

Closes #50 #51

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

Successfully merging this pull request may close these issues.

2 participants