put country setters in right places

[andrewbaxter439]

What

• closes develop branch in multirun setup doesn't create country before referencing it #224 by putting country setter in right places

[Copilot]

Pull Request Overview

This PR fixes country setter placement by moving the Country.getCountryFromNameString(countryString) assignment to occur before it's used in the database lookup, addressing issue #224.

• Moves country initialization to happen before the country variable is used in line 89
• Adds country initialization in the exception handler to ensure it's always set

[Copilot]

The country variable is used here but may still be null if an exception occurs during the Country.getCountryFromNameString() call on line 88, which would cause a NullPointerException.

Suggested change

	country = Country.getCountryFromNameString(countryString);
	String valueYear = lastDatabaseCountryAndYear.getValue(country.toString()).toString();
	startYear = Integer.parseInt(valueYear);
	} catch (NullPointerException e) {
	System.out.println("No last database country and year found.");
	countryString = "United Kingdom";
	country = Country.getCountryFromNameString(countryString);
	country = Country.getCountryFromNameString(countryString);
	if (country == null) {
	country = Country.UNITED_KINGDOM;
	}
	String valueYear = lastDatabaseCountryAndYear.getValue(country.toString()).toString();
	startYear = Integer.parseInt(valueYear);
	} catch (NullPointerException e) {
	System.out.println("No last database country and year found.");
	countryString = "United Kingdom";
	country = Country.getCountryFromNameString(countryString);
	if (country == null) {
	country = Country.UNITED_KINGDOM;
	}