The magic of the parse() function

[stchris]

When I started untangle I thought it would be very clever to have one single entry point which "magically" reacts to the input given. Hence untangle has this one function which can take either a file path, an XML content string or an URL. As I gained experience and untangle got more popular than I ever thought, I realized that this is a bad idea for multiple reasons. I tend to shy away from anything "magic" nowadays, so here's my proposal:

• split parse() into
  • parse_from_path()
  • parse_from_string()
  • parse_url()
• potentially introduce these changes without breaking the API and deprecate parse()

[stchris]

The corresponding issue for this is #87