Fix: Define kwargs properly for step validation

[obarahona10]

Following #1

[Copilot]

Pull request overview

Adjusts ManagementForm initialization so wizard step validation can pass steps via kwargs without conflicting with normal Form positional args (e.g., POST data), as a follow-up to #1’s current_step validation work.

Changes:

• Update ManagementForm.__init__ to accept *args, **kwargs and pull steps from kwargs.
• Ensure steps is stored on the instance before calling forms.Form.__init__.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

steps is now optional (kwargs.pop("steps", None)), but clean_current_step() assumes it’s iterable; omitting steps will raise a TypeError at validation time (value not in None). Consider making steps a required kw-only argument (e.g., def __init__(..., *, steps, **kwargs)) or raise a clear error in __init__ when steps is missing/None so failures are immediate and actionable.

Suggested change

	self.steps = kwargs.pop("steps", None)
	self.steps = kwargs.pop("steps", None)
	if self.steps is None:
	raise TypeError("ManagementForm requires a 'steps' keyword argument.")
	# Ensure that steps is iterable so membership checks in clean_current_step()
	# do not raise a TypeError at validation time.
	try:
	iter(self.steps)
	except TypeError as exc:
	raise TypeError("ManagementForm 'steps' must be an iterable of step names.") from exc