A major feature of Drupal as a CMS is the ability to extend all content entities, including comments, with fields that can collect and persist data with the entity. For example, a site builder can add a "rating" field to comments, which would then allow users to add a 1-5 star rating about the thing they are commenting on (as on amazon.com reviews). Or, a site builder can add a "flag" field to comments, which would provide no UI when initially adding a comment, but after the comment is saved, all users, including the original comment author, could toggle this flag, and see the total number of users who did so (as with Facebook's Like/Unlike or Amazon's Helpful/Unhelpful). The UI for these fields are currently all implemented in PHP code. So, what changes would be required of these fields to integrate with the JS-framework-driven UI? Until they make those changes, can they still function (even if suboptimally) within this new UI?
A major feature of Drupal as a CMS is the ability to extend all content entities, including comments, with fields that can collect and persist data with the entity. For example, a site builder can add a "rating" field to comments, which would then allow users to add a 1-5 star rating about the thing they are commenting on (as on amazon.com reviews). Or, a site builder can add a "flag" field to comments, which would provide no UI when initially adding a comment, but after the comment is saved, all users, including the original comment author, could toggle this flag, and see the total number of users who did so (as with Facebook's Like/Unlike or Amazon's Helpful/Unhelpful). The UI for these fields are currently all implemented in PHP code. So, what changes would be required of these fields to integrate with the JS-framework-driven UI? Until they make those changes, can they still function (even if suboptimally) within this new UI?
Dedicated Drupal thread https://github.com/acquia/js-exploration/issues/4