Page MenuHomePhabricator

Create Structured Contents Parser
Open, MediumPublic3 Estimated Story Points

Description

As a Engineer i want to break our current parser by functionality. I expect to have two parsers, current and structured contents one, where functionality will be bound to the use case itself and both can have their different lifecycles.

Acceptance Criteria

  • Repo created with the necessary code for Structured Contents

TODO

  • Review Structured Contents Main API code
  • Create a repository for the new code
  • Copy code and unit tests, without removing, from the parser to structured contents for:
    • Infobox
    • Sections

Do not delete the branches

Demo ticket

Event Timeline

JArguello-WMF set the point value for this task to 5.

The only feature we don't include in SC API is "GetTemplates". Should I remove it from the code?

We could use it in the future with some SC feature

@REsquito-WMF This ticket scope is to create the new Repo for "Structured-Contents-Parser"?

Should I extend this ticket to:

  1. Remove the duplicate code in the "Parser" module (remove the SC-specific logic)
  2. Refactor the Main API Proxy, so we replace the "Parser" submodule with this "SC Parser" submodule?
JArguello-WMF changed the point value for this task from 5 to 3.Wed, Apr 17, 1:12 PM