view API/Objects/Requirement/Mock/AbstractFixedRequirement.cs @ 208:c323770e61c2

Re #379: Fix validation of requirements to check for unit * Rename classes in tests to match API changes * Alter tests to match new API (all classes require at least one UnitType that they're relevant to now)
author IBBoard <dev@ibboard.co.uk>
date Wed, 22 Feb 2012 20:48:40 +0000
parents 32b3e41bc8f0
children 5e03b68dd214
line wrap: on
line source

// This file (AbstractFixedRequirement.cs) is a part of the IBBoard.WarFoundry.API.Tests project and is copyright 2011 IBBoard
// 
// The file and the library/program it is in are licensed and distributed, without warranty, under the GNU Affero GPL license, either version 3 of the License or (at your option) any later version. Please see COPYING for more information and the full license.
using System;

namespace IBBoard.WarFoundry.API.Objects.Requirement.Mock
{
	public abstract class AbstractFixedRequirement : IRequirement
	{
		private Validation result;

		public string RequirementID
		{
			get { return GetType().Name; }
		}

		public AbstractFixedRequirement(Validation fixedResult)
		{
			result = fixedResult;
		}

		public Validation AllowsAdding(IWarFoundryObject wfObject, Army toArmy)
		{
			return result;
		}

		public Validation ValidatesArmy(Army army)
		{
			return result;
		}

		public string GetValidationMessage(Army army)
		{
			return (result.Equals(Validation.Failed)) ? "Validation failed" : "";
		}

		public string GetAllowsAddingMessage(IWarFoundryObject toAdd, Army toArmy)
		{
			return (result.Equals(Validation.Failed)) ? "Validation failed" : "";
		}
	}
}