Skip to content

Conversation

facumenzella
Copy link
Contributor

Motivation

While going through the tuist set up once again, I noticed that testCustomEntitlementsComputation a project to test RevenueCat_CustomEntitlementComputation didn't have the settings.

Description

  • Extend appTarget to receive extra settingsDictionary
  • Tweak testCustomEntitlementsComputation to include it for the only target it has

Copy link

emerge-tools bot commented Aug 13, 2025

📸 Snapshot Test

1 modified, 704 unchanged

Name Added Removed Modified Renamed Unchanged Errored Approval
RevenueCat
com.revenuecat.PaywallsTester.mac-catalyst-optimized-for-mac
0 0 1 0 234 0 ⏳ Needs approval
RevenueCat
com.revenuecat.PaywallsTester
0 0 0 0 235 0 N/A
RevenueCat
com.revenuecat.PaywallsTester.mac-catalyst-scaled-to-match-ipad
0 0 0 0 235 0 N/A

🛸 Powered by Emerge Tools

Copy link
Member

@ajpallares ajpallares 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. Just one comment about the Examples/testCustomEntitlementsComputation/testCustomEntitlementsComputation.xcodeproj file

Copy link
Member

Choose a reason for hiding this comment

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

I'm curious. Is this file being used in CI at all? If not, perhaps we could remove it and/or always have tuist generate it?
Note that the .xcodeproj file is already gitignored

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think you're right. I can do that in another PR

@facumenzella facumenzella merged commit c735850 into main Sep 1, 2025
12 checks passed
@facumenzella facumenzella deleted the feat/add-ENABLE_CUSTOM_ENTITLEMENT_COMPUTATION-testproject branch September 1, 2025 15:41
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