Graph-comparator-service: Use appropriate and consistent naming

[plc-dev]

• Graph comparator / JSON comparator
• Error / Limitations
• ...

[RMickley]

What I renamed

Files (7)

Before	After
comparator_default.py	default_comparator.py
feedback_builder_default.py	default_feedback_builder.py
pipeline_default.py	default_pipeline.py
normalizer_cardinality.py	cardinality_normalizer.py
normalizer_flags.py	flags_normalizer.py
normalizer_labels.py	labels_normalizer.py
ops.py (erd/)	erd_operations.py

Code (5)

Before	After	Reason
JsonComparator	GraphComparator	Interface takes Graph objects, not JSON
DiffOp (type alias)	DiffOpType	Otherwise naming conflict with the DiffOperation class
get_comparator()	create_comparator()	get_ sounds like property access, create_ signals a factory
get_feedback_builder()	create_feedback_builder()	Same reason
build_final_feedback()	build_feedback()	final is meaningless

Strings / Config (3)

Before	After	Where
vergleicher	graph-comparator	docker-compose.yml (service name)
"JSON-Vergleicher"	"Graph Comparator"	main.py (FastAPI title)
getLogger("vergleicher")	getLogger("graph-comparator")	main.py

bc63953

[RMickley]

Renamed "limitations" to "warnings".

af9e807