You are here

README.txt in Feeds extensible parsers 7.2

Same filename and directory in other branches
  1. 7 README.txt
Feeds extensible parsers
========================

A set of extensible parsers for Feeds.
http://drupal.org/project/feeds_ex

Provided parsers
================
- XPath XML & HTML
- QueryPath XML & HTML (requires the QueryPath module)
- JSONPath JSON & JSON lines parser (requires JSONPath)
- JMESPath JSON & JSON linesparser (requires JMESPath and PHP 5.4)

Requirements
============

- Feeds
  http://drupal.org/project/feeds

Installation
============

- Download and enable just like a normal module.

QueryPath
=========
To use the QueryPath parsers, download and enable the QueryPath module.
http://drupal.org/project/querypath

JSONPath
========
To use the JSONPath parser, download
https://jsonpath.googlecode.com/svn/trunk/src/php/jsonpath.php
into sites/all/libraries/jsonpath and clear the cache.
Note: The JMESPath parser is preferred if you can meet the requirements.

JMESPath
========
To use the JMESPath parsers, you'll need Composer, and PHP >= 5.4.
In sites/all/libraries:

$ git clone https://github.com/mtdowling/jmespath.php.git
$ cd jmespath.php
$ composer install
$ drush cc all # Or just clear the cache however you normally would.

Development
===========
To run tests locally, the TUnit module is required.
http://drupal.org/project/tunit
One of the goals of this module is to allow other developers to easily create
certain types of parsers. For example, it should be trivial to create a parser
for a specific XML format.
Documention to come.

History
=======
This is the new home for:
- Feeds XPath Parser
- Feeds JSONPath Parser
- Feeds QueryPath Parser
The above modules are all in various states of maintenance. This project is
meant to combine them so that they can benefit from each other's development and
simplify maintenance. There are also some major architectural changes.

There is no upgrade path for the old modules. It remains on the table, but those
modules are still maintained and should continue to work.

File

README.txt
View source
  1. Feeds extensible parsers
  2. ========================
  3. A set of extensible parsers for Feeds.
  4. http://drupal.org/project/feeds_ex
  5. Provided parsers
  6. ================
  7. - XPath XML & HTML
  8. - QueryPath XML & HTML (requires the QueryPath module)
  9. - JSONPath JSON & JSON lines parser (requires JSONPath)
  10. - JMESPath JSON & JSON linesparser (requires JMESPath and PHP 5.4)
  11. Requirements
  12. ============
  13. - Feeds
  14. http://drupal.org/project/feeds
  15. Installation
  16. ============
  17. - Download and enable just like a normal module.
  18. QueryPath
  19. =========
  20. To use the QueryPath parsers, download and enable the QueryPath module.
  21. http://drupal.org/project/querypath
  22. JSONPath
  23. ========
  24. To use the JSONPath parser, download
  25. https://jsonpath.googlecode.com/svn/trunk/src/php/jsonpath.php
  26. into sites/all/libraries/jsonpath and clear the cache.
  27. Note: The JMESPath parser is preferred if you can meet the requirements.
  28. JMESPath
  29. ========
  30. To use the JMESPath parsers, you'll need Composer, and PHP >= 5.4.
  31. In sites/all/libraries:
  32. $ git clone https://github.com/mtdowling/jmespath.php.git
  33. $ cd jmespath.php
  34. $ composer install
  35. $ drush cc all # Or just clear the cache however you normally would.
  36. Development
  37. ===========
  38. To run tests locally, the TUnit module is required.
  39. http://drupal.org/project/tunit
  40. One of the goals of this module is to allow other developers to easily create
  41. certain types of parsers. For example, it should be trivial to create a parser
  42. for a specific XML format.
  43. Documention to come.
  44. History
  45. =======
  46. This is the new home for:
  47. - Feeds XPath Parser
  48. - Feeds JSONPath Parser
  49. - Feeds QueryPath Parser
  50. The above modules are all in various states of maintenance. This project is
  51. meant to combine them so that they can benefit from each other's development and
  52. simplify maintenance. There are also some major architectural changes.
  53. There is no upgrade path for the old modules. It remains on the table, but those
  54. modules are still maintained and should continue to work.