/**
Copyright 2021 Forestry.io Holdings, Inc.
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
    http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
*/ export interface Store { glob ( pattern , hydrator ? ) : Promise < string [ ] > ; get < T extends object > ( filepath ) : Promise < T > ; clear ( ) : void ; param queryStrings param hydrator query ( queryStrings , hydrator ? ) : Promise < object [ ] > ; /**
     * In this context, seeding is the act of putting records and indexing data into an ephemeral
     * storage layer for use during the GraphQL runtime. What might seem suprising is that some stores
     * don't support seeding, this is because they're behaving more like a "bridge" (GithubStore and FilesystemStore).
     * Currently they're acting as a way to swap out true data-layer behavior with a backwards-compatible
     * "store". In the future, all stores should be able to query and seed data.
     *
     * At this time it seems that it would never make sense to be able to "query" without "seed"-ing, and
     * there'd be no value in "seeding" without "query"-ing.
     */ seed ( filepath , data , options ? ) : Promise < void > ; supportsSeeding ( ) : boolean ; /**
     * Whether this store supports the ability to index data.
     * Indexing data requires writing arbitrary keys/values to
     * the external service, so is not advisable to use for
     * something like Github, which would write commits to the
     * user's repo.
     */ supportsIndexing ( ) : boolean ; put ( filepath , data , options ? ) : Promise < void > ; }