style: standardize on "service" for Beamable product capabilities (v5.1)#62
Open
allister-beamable wants to merge 1 commit intounity/v5.1from
Open
style: standardize on "service" for Beamable product capabilities (v5.1)#62allister-beamable wants to merge 1 commit intounity/v5.1from
allister-beamable wants to merge 1 commit intounity/v5.1from
Conversation
Replace "feature" with "service" as the noun for Beamable product capabilities across all beamable-services/ pages. Rationale: the nav section is already "Beamable Services"; "service" aligns with the engineering-oriented audience and the existing structural vocabulary. Preserved: "Feature Support" table headers, "feature prefab/Prefab" (Unity asset references), occurrences in code blocks, and any use of "feature" referring to non-Beamable concepts. Scope: docs/unity/user-reference/beamable-services/ only. Whatsnew/, portal/, and CLI guide pages are intentionally excluded. 71 substitutions across 29 files. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
allister-beamable
force-pushed
the
style/feature-to-service-v5.1
branch
from
3bf946b to
a58c48d
Compare
| ### Custom Purchaser | ||
|
|
||
| The Beamable **Custom Purchaser** feature allows game makers to implement custom purchasing solutions for in-app purchases, bypassing Unity's built-in IAP system for complete control over the payment flow. | ||
| The Beamable **Custom Purchaser** service allows game makers to implement custom purchasing solutions for in-app purchases, bypassing Unity's built-in IAP system for complete control over the payment flow. |
Contributor
Author
There was a problem hiding this comment.
Suggested change
| The Beamable **Custom Purchaser** service allows game makers to implement custom purchasing solutions for in-app purchases, bypassing Unity's built-in IAP system for complete control over the payment flow. | |
| The Beamable **Custom Purchaser** mechanism allows game makers to implement custom purchasing solutions for in-app purchases, bypassing Unity's built-in IAP system for complete control over the payment flow. |
|
|
||
| ### Custom Stores | ||
| The Beamable **CommerceService** feature allows game makers to create custom storefronts with flexible purchasing options. | ||
| The Beamable **CommerceService** service allows game makers to create custom storefronts with flexible purchasing options. |
Contributor
Author
There was a problem hiding this comment.
Suggested change
| The Beamable **CommerceService** service allows game makers to create custom storefronts with flexible purchasing options. | |
| The Beamable **Commerce** service allows game makers to create custom storefronts with flexible purchasing options. |
| {: style="height:auto;width:600px"} | ||
|
|
||
| Using the username and password feature is easy. There are just a few APIs you need to know about to be ready to go. Read more here to learn how to use `AddEmail` and `RecoverAccountWithEmail` methods of the `PlayerAccounts` SDK. | ||
| Using the username and password service is easy. There are just a few APIs you need to know about to be ready to go. Read more here to learn how to use `AddEmail` and `RecoverAccountWithEmail` methods of the `PlayerAccounts` SDK. |
Contributor
Author
There was a problem hiding this comment.
Suggested change
| Using the username and password service is easy. There are just a few APIs you need to know about to be ready to go. Read more here to learn how to use `AddEmail` and `RecoverAccountWithEmail` methods of the `PlayerAccounts` SDK. | |
| Using username and password for logins is easy. There are just a few APIs you need to know about to be ready to go. Read more here to learn how to use `AddEmail` and `RecoverAccountWithEmail` methods of the `PlayerAccounts` SDK. |
| # Content - Overview | ||
|
|
||
| The **Content** feature allows game maker to store project-specific data objects. It is embedded into many Beamable features, such as Inventory, Store, Leaderboards, and Tournaments. For simplicity, some Beamable data structures may be omitted from this diagram. | ||
| The **Content** service allows game maker to store project-specific data objects. It is embedded into many Beamable services, such as Inventory, Store, Leaderboards, and Tournaments. For simplicity, some Beamable data structures may be omitted from this diagram. |
Contributor
Author
There was a problem hiding this comment.
Suggested change
| The **Content** service allows game maker to store project-specific data objects. It is embedded into many Beamable services, such as Inventory, Store, Leaderboards, and Tournaments. For simplicity, some Beamable data structures may be omitted from this diagram. | |
| The **Content** service allows game maker to store project-specific data objects. It is embedded into many other Beamable services, such as Inventory, Store, Leaderboards, and Tournaments. For simplicity, some Beamable data structures may be omitted from this diagram. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
docs/unity/user-reference/beamable-services/pagesScope and exclusions
Changed:
docs/unity/user-reference/beamable-services/onlyIntentionally excluded:
whatsnew/— "new feature" is universal product/changelog vocabulary, leave itportal/— operator audience, less technical, leave itPreserved within scope:
Review notes
Please flag any substitution that reads awkwardly or that you feel should remain "feature" — this is a style policy discussion as much as an edit, and Eva/Chris/Balbio's input on the policy is the point of this PR.
The v5.0 counterpart is #61.
🤖 Generated with Claude Code