7 Commits (3a1719e4e10b121d5e1cbbd46a69bfbf01dbb4c1)

Author	SHA1	Message	Date
Siew Kam Onn	dfa49faa79	Fix isExplicitEmptyOverride for empty maps handling ... Enhanced the isExplicitEmptyOverride function to correctly identify empty maps and placeholders created by --set key={}, preventing unintentional reintroduction of chart defaults. Added regression tests to ensure proper treatment of empty map placeholders and validated that CLI values maintain empty maps after coalescing. Signed-off-by: Siew Kam Onn <kosiew@gmail.com>	3 months ago
Siew Kam Onn	b099506632	Refactor coalesce functions to handle empty maps ... Reordered coalesceValues and coalesceTablesFullKey to convert explicit empty overrides into empty maps before merging. This prevents default map entries from resurfacing, even for nested tables. Additionally, the regression suite is expanded to cover nested empty overrides, ensuring empty maps are preserved across different override shapes. Signed-off-by: Siew Kam Onn <kosiew@gmail.com>	3 months ago
Siew Kam Onn	2f2a54a0aa	Refactor tests in coalesce_test.go to use require and assert for better error handling and readability ... Signed-off-by: Siew Kam Onn <kosiew@gmail.com>	3 months ago
Siew Kam Onn	cf8ebe8e5c	Clarify behavior for empty destination tables in coalesceTablesFullKey function ... Signed-off-by: Siew Kam Onn <kosiew@gmail.com>	3 months ago
Siew Kam Onn	7a54bdca44	Add test for CoalesceTables with empty destination table ... Signed-off-by: Siew Kam Onn <kosiew@gmail.com>	3 months ago
Siew Kam Onn	58aaf2f263	Add test for coalescing values with empty map overrides ... Signed-off-by: Siew Kam Onn <kosiew@gmail.com>	3 months ago
Matt Farina	9dcc49cbd5	Move lint pkg to be part of each chart version ... Linting is specific to the chart versions. A v2 and v3 chart will lint differently. To accomplish this, packages like engine need to be able to handle different chart versions. This was accomplished by some changes: 1. The introduction of a Charter interface for charts 2. The ChartAccessor which is able to accept a chart and then provide access to its data via an interface. There is an interface, factory, and implementation for each version of chart. 3. Common packages were moved to a common and util packages. Due to some package loops, there are 2 packages which may get some consolidation in the future. The new interfaces provide the foundation to move the actions and cmd packages to be able to handle multiple apiVersions of charts. Signed-off-by: Matt Farina <matt.farina@suse.com>	5 months ago