Skip to content

As a tenant Admin I want the legacy flat service switches retired once every resource carries a services config. #1595

Description

@nopivnick

Follow-up to #1594.

The request form renders services two ways: the schema-driven per-room service sections, and a legacy fallback of tenant-level flat switches (setup, equipment, staffing, catering, cleaning, security) used when no selected room carries a services config. #1594 moves both paths to the Services step unchanged.

This issue retires the fallback:

  • Confirm every tenant's resources carry a services config (or migrate them)
  • Remove the flat-switch rendering and its effects (catering→cleaning, 75+ security) from the legacy path, keeping the schema-driven equivalents
  • Treat rooms without a services config as offering no services
  • Remove form.services tenant flags that only the fallback consumed, per the direction in As an MC Admin I want to refactor the request form. #1408

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions