Skip to content

RFC: 2.0.0 Roadmap #51

@davidyell

Description

@davidyell

I wanted to quickly make some notes about things which I think could be worked on for the next major release of the plugin. This is a quick list and by no means exhaustive. Any suggestions are welcome

  • CakePHP 3.5 support. Is it worth continuing work in the existing 3.4-test branch? Bump up to CakePHP 3.6
  • Where appropriate refactor mixed mode methods, such as Endpoint::endpoint() and Endpoint::alias() to getters and setters
  • Tidy up the api to remove confusing method names. Eg, Endpoint::endpoint and Endpoint::endpoint()
  • Upgrade to usage of setConfig() and getConfig()
  • Bump code sniffer version and fix any warnings
  • Implement the new setAlias() and getAlias() methods which are now part of the core RepositoryInterface into the Endpoints
  • Replace the useless {@inheritDoc} doc blocks with actual doc blocks
  • Move the AbstractDriver class into the Driver folder and update it's namespace
  • Typehint where appropriate such as Endpoint::webservice()
  • Add phpstan, with a script for basic support such as level 2
  • Bump phpunit to 7.x and update the test suite
  • Fix the FixtureListener in the phpunit.xml file as PHPUnit 7.x doesn't have the BaseListener class
  • If no results are found, the returned total should be zero Query::count() should always return integer. #44
  • Refactor Schema::options()
  • Refactor Schema::columnType()
  • Deprecate ControllerEndpointFilter since dispatch filters are deprecated in Cake 3.6 and add corresponding middleware instead. Deprecate the DispatchFilter #64
  • Deprecate the EndpointRegistry, as TableRegistry has been deprecated Deprecate the EndpointRegistry #69
  • Fix the Test boostraps use of deprecated DispatcherFactory Remove the use of deprecated dispatcher factory #67
  • Using Query::repository() as getter is deprecated. Use getRepository() instead. Seems mostly to be in the tests
  • Update the deprecated TypeMap() calls
  • Adding pagination support, ref How to get pagination data? #42 Preserve the pagination data in the result set #43 Moved to post 2.0.0 release.
  • Re-name some variables to better differentiate between strings and instances
  • Update the Readme to show the new api

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions