This repository was archived by the owner on Jul 1, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2
How parser work
Sweetlie edited this page Feb 26, 2018
·
9 revisions
- only one raid in a single pin
- The parser is not case sensitive
- Punctuation (or absence of punctuation) is important
- white space between word is not important
- position of the information in the document is not important, though if multiple part of the document match the information only the first one will be taken into account
- any text before and after the information is ignored
The following 3 part are describing information that are required in the template for it to be listed on the website
For the parser to be able to sort out these two informations they should always come in pair like "100 SLR"
- 100 SLR
- 100 Foxflower
- 100 fox
- 100 ff
- 100 Dreamleaf
- 100 DL
Date is supposed to be EST for us channels and CET for eu channels
- 2200 EST
- 22:00
- 10:00 PM
- Sunday, 25.02
- Sunday, 25/02
- Sunday 25/02
- Feb 25
- Feb 25th
- February 25
- February 25th
- 25/02/18 (eu channels)
- 25/02/2018 (eu channels)
- 25.02.2018 (eu channels)
- 02/25/18 (us channels)
- 02/25/2018 (us channels)
- 02.25.2018 (us channels)
- Organizer is always listed in the roster
- all other discord member mentioned in the post are added to the roster
- all members following a separator keyword like backup or standby are added in the second (standby) roster
- stand-by
- standby
- stand by
- backup
- backups
To avoid having a new bug report each time you make a new raid I added some keyword that will make the parser completely ignore the pin
- upcoming events
- upcoming raids
- scheduled raids
- scheduled events