You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The EDTF syntax validation warning added in OpenHistoricalMap/iD#187 displays the full error message provided by EDTF.js, which in turn comes from Peggy, the parser generator library. This message can be helpful for diagnosing the error in this syntax, but sometimes the error gets way too long and complex to be useful. Moreover, Peggy considers it to be preformatted text, but we’re showing it as formatted text, so all the newlines and whitespace are getting collapsed. For example, this epic novel appears when typing a backslash instead of a slash for interval notation:
There are a couple things we could do here:
Collapse the detailed error message by default.
Format it as preformatted text, though this will cause it to take up even more screen real estate.
If EDTF.js provides the error in a more structured form, try to formulate our own error message, which would enable us to translate it too.
Just omit this detail. If the column number is difficult to act upon, the warning message could include the current malformed value with the offending character highlighted, sort of like how the validator warning about outdated tags shows an inline diff.
The EDTF syntax validation warning added in OpenHistoricalMap/iD#187 displays the full error message provided by EDTF.js, which in turn comes from Peggy, the parser generator library. This message can be helpful for diagnosing the error in this syntax, but sometimes the error gets way too long and complex to be useful. Moreover, Peggy considers it to be preformatted text, but we’re showing it as formatted text, so all the newlines and whitespace are getting collapsed. For example, this epic novel appears when typing a backslash instead of a slash for interval notation:
There are a couple things we could do here:
Originally reported by Hidoo in OSM World Discord.
The text was updated successfully, but these errors were encountered: