You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this issue #4896 kearfy mentions that meta:: will be re-introduced temporarily, however currently a function that contains "meta::" can not be browsed inside the functions tab because it says that the syntax is not valid (my guess is that since Surrealist 3.x auto-formats the functions, and that syntax is currently not allowed).
The problem with that is, if the functions in Surreal 1.x use meta::, and the schema is moved to Surreal 2.x by using surreal fix, the functions can not even be viewed in Surrealist.
Describe the solution
Either before or when Surreal 2.x re-introduces meta::, it would be good if those functions could be viewed in order to be updated.
Have you considered contributing this feature yourself?
Is your feature request related to a problem?
In this issue #4896 kearfy mentions that meta:: will be re-introduced temporarily, however currently a function that contains "meta::" can not be browsed inside the functions tab because it says that the syntax is not valid (my guess is that since Surrealist 3.x auto-formats the functions, and that syntax is currently not allowed).
The problem with that is, if the functions in Surreal 1.x use meta::, and the schema is moved to Surreal 2.x by using
surreal fix
, the functions can not even be viewed in Surrealist.Describe the solution
Either before or when Surreal 2.x re-introduces meta::, it would be good if those functions could be viewed in order to be updated.
Have you considered contributing this feature yourself?
No response
Surrealist Environment
Version: 3.0.3
Flags: feature_flags: false, query_view: true, explorer_view: true, graphql_view: true, designer_view: true, auth_view: true, functions_view: true, models_view: true, apidocs_view: true, cloud_view: true, themes: true, newsfeed: true, database_version_check: true, highlight_tool: false, legacy_serve: false, cloud_endpoints: production, cloud_access: false, cloud_killswitch: true, changelog: auto
Contact Details
No response
Is there an existing issue for this?
Code of Conduct
The text was updated successfully, but these errors were encountered: