* Add memoization level for the search aggregation fetch hook
* Fix search aggregation integration tests
* Reset data in case of error (fix mode availability for case when if aggregation gets an error)
* Make aggregation API fields required
* Refactor error UI state for aggregation components
* Fix styles for error message and error alert UI
* add feature flag
* pass feature flag through props
* disable aggregation if flag is set
* simplify aggregation mode check
* Remove disabled text
* updates from PR review
* hide expand button
* remove querystring param
* refactor to use new available layout
* undo changes to generateGraphQlOperations
* Polish aggregation UI and remove legacy proactive checks
* Remove gql generated types from search-ui
* Fix search-aggregation.test.ts
* Move aggregation chart to a separate chunk
* Fix problem with wrong rect background in bar chart
Co-authored-by: vovakulikov <vovakulikov@icloud.com>
* Fix styles for active bar segment for wildcard bar chart
* Support gql types generation for search-ui package
* Add aggregation data hook
* Connect GQL API to search aggregation UI
* Support new datum click api for the bar chart
* Connect aggregation chart with submit search logic
* Support missing groups count label
* Add BE calculated aggregation type support
* Add aggregation chart card UI
* Fix Pie chart prop interfaces
* Make limit required prop for aggregation hook
* Fix aggregation hook based on PR comments (adopt union type for result interface, simplify parse logic, update comments)
* Fix SearchAggregationResult.story.tsx (add query mocks)
* Fix search aggregation tests (add mocks)
* Fix bad storybook import
* Add integration test for aggregation drill down logic
* Fix search aggregation integration test (bar links transitions)
* JetBrains: Add GraphQL operation extraction for JetBrains
* JetBrains: Expose a way to query accessToken and endpointURL
* Implement telemetry endpoint and event batching
* JetBrains: Add a generic way to make GraphQL requests
* JetBrains: Log IDESearchSubmitted event and use the new telemetry interface
* JetBrains: Refactor blob fetching to use the proper GraphQL APIs
* Fix review input
* JetBrains: Simplify EventLogger
* Fix typos
* Remove FromJetBrains Suffix
* Format
* Refactor authz resolver to new pattern
* Prevent race when both graphql generators create files simultaneously
I don’t know why it never happened before, maybe with the multiple files the other generator got a little slower but essentially:
We have two type generators, and the one was in the process of writing it’s file when the other was picking up the file for checking it for graphql tags (for which it needs to parse the TS into an AST), and that could be an invalid file while it's still being written…
This PR adjusts all configs/generators/linters that we use to support multiple `.graphql` files to be stitched together for the final schema.
This should help a bit with the MASSIVE `schema.graphql` file that has grown to around 10k loc by now, by encapsulating different fields of concern into separate files. Using the `extend` keyword, there is nothing that cannot be expressed with separate files that could have been with a single file, so there are no drawbacks to this method, that I'm aware of.
In a follow-up PR, I will restructure the backend code for this a bit and make it so the enterprise schema is not used in OSS (which gives better introspection, because there is less noise from fields that aren't accessible because OSS) and doesn't require us to implement a `defaultXXResolver`.
* gulp: disable graphql-codegen's watch feature
Due to https://github.com/dotansimha/graphql-code-generator/issues/1796,
gulp is currently consuming a non-trivial amount of a CPU core watching
for updates that regenerate the GraphQL operations files. Let's use
Chokidar directly (via Gulp) and then we can be smarter about when we
actually trigger the several second generation process.
* Hush eslint.
* Simplify logic and ensure graphql types are generated before first run of webpack
Co-authored-by: Erik Seliger <erikseliger@me.com>
Works on the first milestone of #7998, getting syntax support done.
This currently has no effect, rather than passing validation for changeset specs and campaign specs sent from src-cli that use the new draft flag.
