Deprecated code cleanup

[Hans Van Akelyen <ha...@gmail.com>]

Hi All,

As one of the final stages towards 1.0 I will do a thorough cleanup of all
code that has been marked as deprecated. This will mean the API will start
with a clean slate moving forward. This will be a combination of removing
Methods or maybe even removing the Deprecated tag if it is unclear why it
was marked as deprecated.

If you are a plugin developer and still using a Deprecated Method with no
way to solve the issue, let us know so we will not block you in your
contributions to the project. This can be done via mail or by commenting on
ticket HOP-3221

When we move to 1.X we will continue our hunt and cleanup in the API, first
stage will be to mark as Deprecated with a later planned removal.

Cheers,
Hans

Re: Deprecated code cleanup

[Matt Casters <ma...@neo4j.com.INVALID>]

Great idea.  There really isn't a better time to do this than right now.
Same deal for a general code re-format of .java, .xml, .svg, .adoc and so
on.
It's really annoying if you can't see an accurate diff when reviewing a PR.

Cheers,
Matt

On Thu, Aug 26, 2021 at 9:54 AM Hans Van Akelyen <ha...@gmail.com>
wrote:

> Hi All,
>
> As one of the final stages towards 1.0 I will do a thorough cleanup of all
> code that has been marked as deprecated. This will mean the API will start
> with a clean slate moving forward. This will be a combination of removing
> Methods or maybe even removing the Deprecated tag if it is unclear why it
> was marked as deprecated.
>
> If you are a plugin developer and still using a Deprecated Method with no
> way to solve the issue, let us know so we will not block you in your
> contributions to the project. This can be done via mail or by commenting on
> ticket HOP-3221
>
> When we move to 1.X we will continue our hunt and cleanup in the API, first
> stage will be to mark as Deprecated with a later planned removal.
>
> Cheers,
> Hans
>


-- 
Neo4j Chief Solutions Architect
*✉   *matt.casters@neo4j.com