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
CIG can change the naming any way they want, which will unavoidably break parsing every now and then. How about adding an "unknown" category to gather all items that fail parsing? That way the user doesn't need to disable HangarXPLOR while waiting for an update.
The text was updated successfully, but these errors were encountered:
Have you got an example of an item that's breaking?
The plugin is meant to only enrich data it understands, and shouldn't choke on things it doesn't, so if you've got an item that breaks, please let me know
Peter Dolkens
On 2 Sep 2021, at 15:09, cintaracorp ***@***.***> wrote:
CIG can change the naming any way they want, which will unavoidably break parsing every now and then. How about adding an "unknown" category to gather all items that fail parsing? That way the user doesn't need to disable HangarXPLOR while waiting for an update.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
Not at the moment, however there have been a few earlier that didn't fit the mould. I didn't realise that the item would appear in "All Items", mainly because I rarely use it; the list is so unwieldy 😆! Anyway, in those cases, you have to notice that the item only exists in "All Items". If we had an "Unknown" category, it would be quicker to notice that an update to the filters is needed, and it would be easier to find items that fail categorisation.
CIG can change the naming any way they want, which will unavoidably break parsing every now and then. How about adding an "unknown" category to gather all items that fail parsing? That way the user doesn't need to disable HangarXPLOR while waiting for an update.
The text was updated successfully, but these errors were encountered: