Skip to content

Conversation

@JoelBergstrand
Copy link
Contributor

Added examples for three new deprecations

@JoelBergstrand JoelBergstrand added the dev The default branch. label Oct 21, 2025
@renetapopova renetapopova added 2025.11 and removed dev The default branch. labels Oct 21, 2025
+
[source,cypher]
----
RETURN coll.flatten() AS result
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, this one, never heard of it.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

coll.flatten is in the pipeline to be implemented. Hopefully in 2025.11 as well. This notification shows when a used defined function shadows a builtin function that is in a deprecated namespace.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, I see. Then, we should make sure that this PR is merged after coll.flatten is implemented.

RETURN coll.flatten() AS result
----
Description of the returned code::
The namespace of the invoked user-defined function is deprecated and the function is shadowing an internal function. (coll.flatten)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is also a table 15 further up with all possible descriptions for 01N00 where you could add these as well.

@renetapopova renetapopova force-pushed the 2025.x-namespace-deprecations branch from 54066db to 6b2e73c Compare October 27, 2025 12:55
@neo4j-docops-agent
Copy link
Collaborator

This PR includes documentation updates
View the updated docs at https://neo4j-docs-status-codes-394.surge.sh

Updated pages:

----
Description of the returned code::
The namespace of the invoked function is deprecated. (point.function)
The namespace of the invoked user-defined function is deprecated. (point.function)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are we allowed to change the neo4j codes' descriptions? As far as I know, this would be a breaking change.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The descriptions should match the codebase. If we change them here, we need to change them there as well.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes in this case it is fine because the description is brand new for this feature so it is not breaking for anyone yet to change it

Copy link
Collaborator

@renetapopova renetapopova left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for committing my suggestions, @JoelBergstrand. However, we can only change the Status descriptions, and those changes should be reflected in the codebase as well. The docs should show what the user will see.

----
Description of the returned code::
The namespace of the invoked function is deprecated. (point.function)
The namespace of the invoked user-defined function is deprecated. (point.function)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The descriptions should match the codebase. If we change them here, we need to change them there as well.

@renetapopova renetapopova mentioned this pull request Oct 27, 2025
@JoelBergstrand
Copy link
Contributor Author

JoelBergstrand commented Oct 28, 2025

@renetapopova, my mistake - I was sure I made the corresponding update in the code base as well. Will do it right away. PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants