Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide Search GraphQL Interfaces #150

Merged
merged 7 commits into from
Nov 15, 2019
Merged

Provide Search GraphQL Interfaces #150

merged 7 commits into from
Nov 15, 2019

Conversation

lifedraft
Copy link
Contributor

No description provided.

search/interfaces/graphql/schema.graphql Outdated Show resolved Hide resolved
search/interfaces/graphql/schema.graphql Outdated Show resolved Hide resolved
Copy link
Contributor

@jeinfeldt jeinfeldt 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 contributing!

search/interfaces/graphql/dto/dto.go Outdated Show resolved Hide resolved
Copy link
Contributor

@thehl thehl 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 contributing

search/domain/service.go Outdated Show resolved Hide resolved
search/domain/service.go Outdated Show resolved Hide resolved
SelectedDesc bool
// Asc - DEPRECATED - used to give the "Field" that is used to trigger ascending search
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe document the deprecation like: https://github.com/golang/go/wiki/Deprecated

The field seems completely unused. Could this potentially lead to undesired behavior for library consumers since the value is ignored? (same for Desc)

Copy link
Contributor

Choose a reason for hiding this comment

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

I updated the deprecated fields. Which fields do you mean? Field or Asc/Desc? We left Asc/Desc there because we weren't sure if we introduce a breaking change if we remove them completely. In case of Field. We are using it for the graphql part and it is used in flamingo-om3 which is in the other merge request.

Copy link
Contributor

Choose a reason for hiding this comment

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

@danielpoe could both fields ( Asc, Desc) actually be deleted? this looks quite like dead code.

Copy link
Member

Choose a reason for hiding this comment

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

How do you know they are not used??
They are part of the public API - projects depend on it and its also filled in the Adapters currently
@panzerfahrer

Copy link
Contributor

Choose a reason for hiding this comment

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

The team decided to deprecate the field. If the fields are actually in use, we should probably add fallback behavior. Or do we need a rollback with another solution?

Copy link
Contributor

Choose a reason for hiding this comment

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

... @kalypso-byte could you please clarify, whether the deprecation was a valid move.

Copy link
Member

@danielpoe danielpoe Nov 18, 2019

Choose a reason for hiding this comment

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

The DEPRECATED is valid we did this together. - but because the intent of this property is wrong (it represents the fieldname for searchperience) we want to remove it in future

We just need time to adjust the current usage

Copy link
Member

Choose a reason for hiding this comment

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

So all is fine at the moment - just wanted to clarify

@brnhffmnn brnhffmnn merged commit 3f98fe8 into master Nov 15, 2019
SelectedDesc bool
// Asc - represents the field that is used to trigger ascending search.
// Deprecated: use "Field" and "SelectedAsc" instead to set which field should be sortable
Copy link
Member

Choose a reason for hiding this comment

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

The message is wrong
It should say: Use "Field" to know which Field to set in the SortFilter

@carstendietrich carstendietrich deleted the graphql-search branch December 20, 2019 16:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants