test: improve coverage for init database

[joehan]

Description\nImplement unit tests for init database feature using nock.\n\n### Scenarios Tested\n- Defaults without project ID\n- Downloading rules with project ID\n- Actuate writing rules

[gemini-code-assist]

Code Review

This pull request introduces a new test suite for the database initialization feature, covering both the question-asking process and the actuation logic. The reviewer identified several instances where the 'any' type was used as an escape hatch in the test setup, which violates the repository's style guide regarding type safety. I recommend updating these test cases to use the proper 'Setup' interface as suggested.

[gemini-code-assist]

To avoid using any for the setup object in the tests below, you should import the Setup interface from the parent directory.

Suggested change

	import { askQuestions, actuate, DEFAULT_RULES } from "./database";
	import { askQuestions, actuate, DEFAULT_RULES } from "./database";
	import { Setup } from "..";

References

1. Never use any or unknown as an escape hatch. Define proper interfaces/types or use type guards. ^(link)

[gemini-code-assist]

Avoid using any as an escape hatch for types. Use the Setup interface (or a type assertion to Setup) to maintain type safety and adhere to the repository style guide.

Suggested change

	const setup: any = { config: {} };
	const setup = { config: {} } as Setup;

References

1. Never use any or unknown as an escape hatch. Define proper interfaces/types or use type guards. ^(link)

[gemini-code-assist]

Avoid using any as an escape hatch for types. Use the Setup interface to maintain type safety.

Suggested change

	const setup: any = { projectId: "my-project", config: {} };
	const setup = { projectId: "my-project", config: {} } as Setup;

References

1. Never use any or unknown as an escape hatch. Define proper interfaces/types or use type guards. ^(link)

[gemini-code-assist]

Avoid using any as an escape hatch for types. Use the Setup interface to maintain type safety.

Suggested change

	const setup: any = { projectId: "my-project", config: {} };
	const setup = { projectId: "my-project", config: {} } as Setup;

References

1. Never use any or unknown as an escape hatch. Define proper interfaces/types or use type guards. ^(link)

[gemini-code-assist]

Avoid using any as an escape hatch for types. Use the Setup interface to maintain type safety.

Suggested change

	const setup: any = {
	config: {},
	featureInfo: {
	database: {
	rulesFilename: "database.rules.json",
	rules: DEFAULT_RULES,
	writeRules: true,
	},
	},
	};
	const setup = {
	config: {},
	featureInfo: {
	database: {
	rulesFilename: "database.rules.json",
	rules: DEFAULT_RULES,
	writeRules: true,
	},
	},
	} as Setup;

References

1. Never use any or unknown as an escape hatch. Define proper interfaces/types or use type guards. ^(link)

[gemini-code-assist]

Avoid using any as an escape hatch for types. Use the Setup interface to maintain type safety.

Suggested change

	const setup: any = {
	config: {},
	featureInfo: {
	database: {
	rulesFilename: "database.rules.json",
	rules: DEFAULT_RULES,
	writeRules: false,
	},
	},
	};
	const setup = {
	config: {},
	featureInfo: {
	database: {
	rulesFilename: "database.rules.json",
	rules: DEFAULT_RULES,
	writeRules: false,
	},
	},
	} as Setup;

References

1. Never use any or unknown as an escape hatch. Define proper interfaces/types or use type guards. ^(link)