I will add tests to the alias test function to make sure we cover these errors:
  -- giving the table name when the alias is required
  -- giving an undefined name when an alias is required.

I will also make sure that we have a test in a basic test function for:
  -- giving an undefined name when an alias is required gets an error.
  -- strange punctuation in the join order gets an error -- do you think it's OK that the join order parser takes anything other than a comma as part of the name? so it will claim "wrong number of elements when it expects "A,B" or "B,A" and you give it "A;B"?
  -- spaces around valid join order names should not matter.
  -- doubled comma like "A,,B" -- this case will claim that there are too many elements (counting "" as the second element and "B" as the third) -- do you think that's clear enough?

My preference would be to add these tests and merge the product code as it is. I can add a minor ticket to later make the parser smarter about detecting and describing the probable problem -- bad punctuation vs. bad names (and MAYBE even let them use the table name instead of the alias if it is unambiguous or at least recognize that they are trying to use the table name instead of the alias and suggest the exact correction.