Ticket #135 (closed defect: fixed)

Opened 2 years ago

Last modified 2 years ago

Strict mode check for both .xml and .xml.cfm files

Reported by: bboisvert@… Owned by: scorfield
Type: defect Priority: normal
Milestone: Fusebox 5.1 Component: Miscellaneous
Version: 5.0 Severity: normal
Keywords: strictMode Cc:

Description

When strictMode is enabled in fusebox.xml, the cores should error when both a .xml and a .xml.cfm version exists for a given file (fusebox.xml or circuit.xml). Ideally, it would only allow whatever fusebox.xml is (i.e. if you've got fusebox.xml, then any circuit.xml.cfm would cause an error, even if there isn't a corresponding circuit.xml).

Attachments

Change History

Changed 2 years ago by scorfield

  • owner changed from sean@corfield.org to scorfield
  • status changed from new to assigned
  • milestone set to Fusebox 5.1

Sounds reasonable.

Changed 2 years ago by scorfield

  • status changed from assigned to closed
  • resolution set to fixed

(In [280]) Fixes #135 by adding a check in strict mode that (a) only one of *.xml / *.xml.cfm exists
(for fusebox and circuit files) and (b) the file extensions are consistent (i.e., you can't
have fusebox.xml and then circuit.xml.cfm). The last may prove controversial.

Changed 2 years ago by scorfield

(In [281]) Addresses #135 by ensuring implicit circuit files are ignored for this check.

Changed 2 years ago by scorfield

Based on feedback in the forums, the file extension consistency check - (b) above - has been dropped as too draconian. That removal was quietly part of changeset [282].

Note: See TracTickets for help on using tickets.