this may not be the best place to do this validation

[github-actions]

homeserver/packages/federation-sdk/src/services/room.service.ts

Lines 1660 to 1665 in 015d352

	// TODO this may not be the best place to do this validation
	await this.federationValidationService.validateOutboundInvite(
	member,
	roomCreateEvent.roomId,
	);

---

This issue was generated by todo-issue based on a TODO comment in 015d352. It's been assigned to @sampaiodiego because they committed the code.

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Similar Issues

Possible Duplicates

• 320

Related Issues

• we should actually use the room state to validate the power levels #320
• is this just suppose to log things? #251
• check if all sendEventToAllServersInRoom should be followed by an emitter #304
• change this to call stagingAreaService directly (line above) #178

🔗 Related PRs

RocketChat/Rocket.Chat#37007 - fix: missing reactivity when creating a federated room [merged]
#281 - fix: can't add local users on remote rooms [merged]
#286 - fix: receive invite_room_state as invite param [merged]
RocketChat/Rocket.Chat#37824 - test(federation): validate empty room state [merged]
RocketChat/Rocket.Chat#37840 - fix(federation): update group DMs names [merged]

👤 Suggested Assignees

• sampaiodiego
• juliajforesti
• rodrigok

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord or schedule a call!