mudlet-makers team mailing list archive

[Stephen Lyons <1473787@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

In https://bugs.launchpad.net/mudlet/+bug/1471406 several issues were
mentioned, this is one specific issue:

Although we specify a "version=1.0" attribute at the start of Mudlet XML
files WE HAVE COMMENTED OUT THE CHECK FOR THIS ON READING IN EXISTING
CODE - that needs to be reimplemented ASAP to minimise "current" code
getting broken when we do fix a few items in the future (e.g. the
command "seperater"/"separator" element cock-up) as the existing code in
the field will break or at least spew out "not understood element" debug
messages on future "new/improved/fixed" saved files.

** Affects: mudlet
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1473787

Title:
  No version checking in Mudlet XML files

Status in Mudlet:
  New

Bug description:
  In https://bugs.launchpad.net/mudlet/+bug/1471406 several issues were
  mentioned, this is one specific issue:

  Although we specify a "version=1.0" attribute at the start of Mudlet
  XML files WE HAVE COMMENTED OUT THE CHECK FOR THIS ON READING IN
  EXISTING CODE - that needs to be reimplemented ASAP to minimise
  "current" code getting broken when we do fix a few items in the future
  (e.g. the command "seperater"/"separator" element cock-up) as the
  existing code in the field will break or at least spew out "not
  understood element" debug messages on future "new/improved/fixed"
  saved files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mudlet/+bug/1473787/+subscriptions