I've been playing with Projects Beta using GitHub's GQL API but can't find a way to filter / search / query them.
For instance, I'd to get all issues in a project for which a field has a specific value.
How do I do so? Is it possible?
None of those objects as a filter attribute.
I've also looked at the search query but that doesn't seem to support Projects or Fields as query parmeters.
Thanks in advance!
I asked about this in the Projects Beta Feedback Discussion.
It seems that filtering hasn't been implemented (yet) and so it's necessary to do things the old fashioned way (like with the REST API) by using queries to get all the issues, then filtering after.
In many ways this is worse than things were with the REST API, as there's no way to get just the issues in a given column, you have to get every issue on the board, which quickly then gets you into needing pagination.
At least GraphQL queries are specifying which nodes/fields you want back, so you're not having to filter through all of everything, just some of everything.
Related
recently I have been working with symfony 4 in search of some solution for the creation of web services api-rest and I have found api-platform. After several days trying, because I do not have much knowledge of symfony, I managed to raise the API for an entity that I created by default. It turns out that now I have the doubt of how to add to the api methods other than those that are by default, say the put, the get and others that are already by default, I want to be able to add to my entity the methods that I estimate necessary and with the name that I want. Please I would appreciate your help with some form or some simple steps that allow me to add new methods to the api always keeping in mind that I do not have much knowledge in the matter.
try to avoid endpoint proliferation as much as possible, think REST
the recommended way to hook your own logic in API Platform is using the built-in events
if you really need to add custom endpoints, here is a dedicated documentation entry, but it should be your last resort (see 1/)
I am building a search component that allows users to filter by type of response. You can see all responses, just the PDFs, or just the webpages. I have the first two parts down, all responses is a basic search and you can filter for pdfs using &fileType=pdf in the query, but i'm not sure how to exclude the pdfs and only return web pages.
I can't find a similar "exclude" param such as -fileType which seems to be supported in other similar APIs. Maybe I just need to format the URL the right way... If anyone has insight into how to accomplish something like this I would appreciate it.
You can try with -inurl:pdf in your URL.
i'm searching for working search ui demo or tutorial for building search UI/Frontend. At best for php or js.
I never builded a elasticsearch application, but I already made projects with lucene, solr, epoq and google search.
Already searched on inet but most example are very simple and incomplete.
Examples:
github.com/scotchfield/elasticsearch-react-example/
github.com/spalger/elasticsearch-angular-example
There also API for PHP and JS
www.elastic.co/guide/en/elasticsearch/client/javascript-api/current/quick-start.html
www.elastic.co/guide/en/elasticsearch/client/php-api/2.0/_quickstart.html
What a example should contain (from my view)
* Basic Search Field
* Filter based on es fields index
* Resultview
* Filter interaction with results
* Paging
I was thinking something like this is already exits, but found no matching one. I think better ask, before invest time in creating.
Thanks in Advance
densanki
I found this live demo interesting:
http://demo.searchkit.co/imdb
If you already know ElasticSearch query syntax and some basic concepts like aggregations you may test all that on https://demo.elastic.co/app/kibana. But again, this would require some basic knowledge of Elastic stack.
Otherwise if you want just touch/try most common Elasticsearch features without going into implementations details then you may check these 3 demos for 3rd party SearchKit UI component.
There's also Elastic UI that you might be interested in: https://elastic.github.io/eui/#/
If you want something ready-made for the time-series use-case, you might want to check Sematext Cloud. There's a simpler UI than Kibana there, but there's API access, too, so you can develop your own.
Will a single GSA search request that specifies two site collections get loaded into the suggestions database for both sites?
For example consider the following query,
http://gsa/search?q=hello&site=site1|site2&client=myfrontend
If results are returned from both collections will the query "hello" get loaded into the suggestion database for both,
1. client=myfrontend&site=site1
2. client=myfrontend&site=site2
So far I have not seen the query get loaded into either suggest database, but perhaps I have not waited long enough, which makes me wonder is there any way to quickly reset/reload suggestions? In the past I have tried resetting them via admin console's suggestions page, and then enabling/disabling suggestions via the frontend, but it does not always regenerate them. Is there any other procedure people follow to reload suggestions?
Contacted Google support and, if multiple collections are defined in search request the suggestion gets logged to the default_collection.
They are working on a resolution :)
I'm developing a community extension for Magento, when a product search is detected, some JavaScript included with the extension needs to query the Magento API to get a larger number of results than are rendered on page.
I have the API configured, responding, and returning useful data, but I'm struggling to find a way to apply a query to the API call. I've tried adding ?q= or ?keyword= and similar, but it continues to return the same set of data without any filtering applied. Countless passes through Google, Magento StackExchange, and various Magento developer forums haven't made it clear one way or another if this is even possible.
Does the REST API support keyword / phrase searches, or will my extension need to include a block that adds this functionality to the REST API?
Did you take a look at Magento API Filtering .
You could also create you own Custom API or Extending the Core API