This roadmap is still WIP. Some issues are tagged for v2 but need to be ported to v3 as well (while kept tagged for v2).

#3230639: Support daterange
#3079012: Support for JSON Path + Pluggable Field Mappers
#3073025: A JSON:API storage client
#2998932: Config export is missing FieldConfig dependencies
#3018424: Mulitilingual support
#3176491: Missing entity cache tags in setPersistentCache
#3171505: Readme file missing
#3110209: Add event to transform raw data before mapping
#3005536: Automatically generate URL alias for new/updated external entities
#3395565: Fix the issues reported by phpcs
, #3421937: Fix HEAD tests for D10.2, currently only passes with D9.5 (duplicate)
#3108830: Mark annotation field as computed
#2999505: Improve date handling
#3374867: Define entity types programmatically
For some reasons, sometimes, an external entity field config is missing (or looses?) its dependency to its external entity type. This can be fixed by xnttmanager now (new "integrity" feature of commit 04284bae).
#3455362: Using multiple field mappers at once

v3 new features to include:

Add native support for Drupal "file" and "image" field types through a companion module. Motivation: being able to use those fields as they are and take profit of existing modules handling those, such as image styles (image cache), etc. as it is not possible with imagecache external.
Add native storage plugin for files (xnttfiles) and maybe something similar for databases (a more generic version of xnttdb) as common basis for future plugins.
Add native views support #2538706: Views integration as a companion module.
An example module providing a "hard-coded" external entity type (using extensions yaml files as xntt for instance) #3374867: Define entity types programmatically
Test coverage: additional automated tests to cover essential features.
- Test external entity type web interface (edition) using javascript: plugins selection, form validation
- Test query filters (source side only, Drupal side only, both sides, on different field types)
- Deeper xntt saving tests (all field types, non-mapped fields, arrays of values, complex mappings, concurrent edition scenari,...)
- Test File client
- Test multiple client features (groups, join fields, aggregation modes)

To consider:

Provide an XML response decoder as XML is/was quite common in (old?) web services and should be supported by the REST client
Provide a SPARQL client (as a derived Query Language client) as a native plugin (not a companion module like xnttsql)

Note: "wiki" (wikimedia) storage client will be removed from v3 and turned into a separate/independent plugin as it is not a generic plugin. However, JSON API storage client will remain there as it is related to Drupal core features.

For next v3 beta 1 (summer):

improve and test debug features (add field mapping debug info and logs for "transliterateDrupalFilters()")
#3374867: Define entity types programmatically
#3455362: Using multiple field mappers at once
Manual tests: under D9, on fresh install and on sites to upgrade

For v3 beta 2:

port of almost all existing external entities plugins to v3 (when relevant, using PR for modules I don't manage)
include views support as companion module
add new REST features: support for prev/next pager, support for dynamic entity count, support for requests from user browser side
add tests for xnttsql
add new examples for programmatically created xntt types

For v3 release candidate (before the end of 2024):

All the above
Wider (almost complete?) test coverage
Completed help, readme and online documentation
...

[META] Roadmap for v3.0

Comments & Activities