[PLA-1899] Expose qr and code for get beam

[enjinabner]

PR Type

enhancement

---

Description

• Removed the 'excludeFrom' attribute for the 'code' and 'qr' fields in the BeamType class to simplify the field definitions.
• This change ensures that the 'code' and 'qr' fields are now included in the 'GetBeam' and 'GetBeams' queries.

---

Changes walkthrough 📝

	Relevant files
Enhancement	BeamType.php Simplify BeamType fields by removing 'excludeFrom' attributes src/GraphQL/Types/BeamType.php Removed 'excludeFrom' attribute for 'code' and 'qr' fields in the BeamType class. Simplified the fields definition by excluding unnecessary attributes. +0/-2

---

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[github-actions]

PR Reviewer Guide 🔍

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ No key issues to review

[github-actions]

PR Code Suggestions ✨

Category	Suggestion	Score
Possible issue	Reintroduce the 'excludeFrom' key to restrict field exposure in specific queries Consider reintroducing the 'excludeFrom' key with values 'GetBeam' and 'GetBeams' for the 'code' field to ensure that it is not exposed in these queries if it was intentionally restricted previously. src/GraphQL/Types/BeamType.php [47-49] 'code' => [ 'type' => GraphQL::type('String!'), 'description' => __('enjin-platform-beam::mutation.claim_beam.args.code'), + 'excludeFrom' => ['GetBeam', 'GetBeams'], ], Suggestion importance[1-10]: 9 Why: The suggestion addresses a potential security or access control issue by ensuring that the 'code' field is not exposed in specific queries, which might have been an intentional restriction previously.	9
	Reintroduce the 'excludeFrom' key to maintain consistent access control Consider reintroducing the 'excludeFrom' key with values 'GetBeam' and 'GetBeams' for the 'probabilities' field to maintain consistent access control as previously configured. src/GraphQL/Types/BeamType.php [95-96] 'probabilities' => [ 'type' => GraphQL::type('Object'), + 'excludeFrom' => ['GetBeam', 'GetBeams'], ], Suggestion importance[1-10]: 9 Why: The suggestion ensures consistent access control for the 'probabilities' field, which aligns with the previous configuration and might be crucial for maintaining the intended security measures.	9