It is set to true by default, based on assumption, that getting results will be your last action. $close is an expected boolean, that, if set to true, will close the cURL handle. To get results of parsers (listed below) you need to run ->getResult($close), which will return the array with the results. Additionally, achievements' test is purposefully ran with details set to true and Free Company members in All pages mode, because of this their benchmark results will be presented as list of timings. Note, that the last 2 tests are 'error tests', so their results are purposefully reversed for the report's consistency. ![]() Run it to get samples of output formatting and timings for each type of test in a table format. There is a \Simbiat\LodestoneTest class to test run all the available functions in some general scenarios. Default value for page is set to 1 to limit resources used. All pagesĪll parsers accepting page number support value of 0, which will return all pages (that is run the respective parser recursively). It is set to false by default, based on assumption, that you are using these only for some kind of validation. For list of all errors -getErrors($close). To get last error you can use ->getLastError($close). In essence, when an error occurs you will simply get an empty result for specific entity and it will not be added to output. In order not to break "linking" function, they are handled softly in the code itself and are reported to ->errors and ->lasterror arrays. In the new concept fatal errors generally can happen only during HTTP requests. It's possible to utilize Benchmarking to get parsing times for each iteration by ->setBenchmark(true) Error handling ![]() Accepted language values are na, eu, jp, fr, de It's also possible to change LodeStone language by ->setLanguage('na'). It's possible to set your own UserAgent used by CURL: simply use ->setUseragent('useragent') For example, you can get both Free Company and its members' details in same object. Ability to "link" different types of entities, requesting several pages in one object.Some filters even support actual "names" used on Lodestone (instead of just IDs). Return more potentially useful information where possible.It does not mean, that this will always be faster than using Symphony-based functions but will be true on average. Using regex instead of full HTML parsing for extra speed (and arrays instead of objects as result).This is what's different from original library from It has different code structure, that aims at reduction of rarely used or unnecessary functions and some standardization. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |