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

Move the SG and weaver binaries to the Realm package #3319

Merged
merged 15 commits into from
May 12, 2023

Conversation

nirinchev
Copy link
Member

@nirinchev nirinchev commented May 10, 2023

Description

Removes the Realm.SourceGenerator package and moves the analyzer inside the regular Realm package. This should have no functional impact, but is a slight improvement in terms of maintainability as we have one fewer package to manage. It also makes it easier for users to understand what our dependencies are.

TODO

  • Changelog entry

@cla-bot cla-bot bot added the cla: yes label May 10, 2023
@coveralls
Copy link

coveralls commented May 10, 2023

Pull Request Test Coverage Report for Build 4947962804

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 81.92%

Totals Coverage Status
Change from base Build 4920425932: 0.0%
Covered Lines: 5908
Relevant Lines: 7085

💛 - Coveralls

@nirinchev nirinchev marked this pull request as ready for review May 10, 2023 15:35
@nirinchev nirinchev requested review from fealebenpae and papafe May 10, 2023 15:35
Copy link
Contributor

@papafe papafe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me! If the packaging works fine, it seems a really good idea

</ItemGroup>
<ItemGroup>
<ItemGroup Label="Package">
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this label used anywhere, or is it here just for readability?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, just for readability - if you collapse all nodes, you get several ItemGroup sections with no indication what is for what, so figured I'd add a label to clarify things a little.

@nirinchev nirinchev changed the title Move the SG binaries to the Realm package Move the SG and weaver binaries to the Realm package May 11, 2023
@nirinchev nirinchev merged commit a5a2584 into main May 12, 2023
@nirinchev nirinchev deleted the ni/move-sg-to-realm branch May 12, 2023 14:00
nirinchev added a commit that referenced this pull request Jun 12, 2023
* main: (29 commits)
  Add platform-specific helpers package (#3323)
  Allow geobox to be constructed from 4 coordinates (#3341)
  Add support for geospatial queries (#3300)
  Update UWP certificate, add instructions on how to do it (#3338)
  Don't throw an exception when setting an embedded property to the same value (#3337)
  Automatically handle object -> embedded object migrations (#3322)
  Add a check for the thread in Realm.IsInTransaction (#3336)
  Update to latest Core (#3334)
  Fix a few typos
  Move the SG and weaver binaries to the Realm package (#3319)
  Update ci-actions to latest commit (#3318)
  Fix a couple of warnings (#3317)
  Prepare for vNext (#3316)
  Prepare for 11.0.0 (#3315)
  Add support for arm on Linux (#3267)
  Update changelog
  Add tests for Set.PropertyChanged notifications (#3309)
  Change testing targets to net7.0 (#3305)
  Adjust codeql config (#3311)
  Allow publishing unity package on prerelease workflow (#3310)
  ...

# Conflicts:
#	Realm/Realm.UnityWeaver/UnityWeaver.cs
#	wrappers/realm-core
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 11, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants