Altair: Create named collection of queries.

[imolorhe]

Each collection can have subfolders within it.

Each collection can be named, duplicated, exported.

Maybe lazy loaded.

• [x] Create new side menu
• [x] Move side menu to app level
• [x] Create collections component
• [x] Delete collection
• [x] Delete query from collection
• [x] Export collection #570
• [x] Edit collection

Store collection data in indexedDb.
http://dexie.org/

Parse markdown.
https://www.npmjs.com/package/ngx-md
https://www.npmjs.com/package/ngx-markdown

• Name of collection
• Description of collection
• Groups (folders) of queries
• Name of query
• Description of query
• Query (query, headers, variables, URL, subscription)

// collection
{
  title: '',
  description: '', // markdown support
  collections: [], // collection[]
  queries: [{ title: '', description: '', ...query }],
  created_at: null,
  updated_at: null
}

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[kurisutofu]

Hi, here are some thoughts.

• It would be nice to have 2 buttons (or one with dropdown) to have the option to "save" or "save as". "Save" would work the same was as now if the query is not in a collection but if in a collection already, it would overwrite it without prompt. "Save as" would always prompt. This way it could be used to copy the query to another collection.
• A way to delete a query from the collection would be welcomed.
• A way to delete a collection would be welcomed.
• Having the headers, variables and subscriptions scoped per collections would be a nice addition.

Thank you.

[imolorhe]

@kurisutofu How do you mean by "scoping headers, variables and subscriptions per collection"? Currently a query comprises of the actual query, headers, variables and URL attached to it, so when they are added to a collection, they are stored in the same way too.

[kurisutofu]

@imolorhe , I just noticed it was true ... I'll update the comment ;)

[kurisutofu]

Hi,

Another one.

• Saving a query with the same name in the same collection does not overwrite the existing query and creates duplicate. Added to the inability to remove a query, this means we need to have duplicates or write the full query from the get-go.

[imolorhe]

@kurisutofu I am not really sure I understand the last point. Are you asking if having a query in a collection would overwrite another query with the same name in that collection?

[kurisutofu]

@imolorhe , I'm not asking if it overwrites. According to my tests, it does not and this is a problem.

For example. you saved a query "test" in collection "set1". If you save again and choose the same name "test" and choose the collection "set1", you end up with 2 queries named "test" in collection "set1".

[ivan-kolmychek]

Thanks for the collections, they are pretty useful and nice.

I'm having same problems with them as @kurisutofu - without being able to update query that is already in collection or delete it from collection altogether, they quickly accumulate a lot of cruft. Which makes it harder to find the queries that you actually care about. :)

[imolorhe]

@ivan-kolmychek The delete tasks have been done. They would be available in the next version.

[carloditan24]

@imolorhe It would be nice to sort the names of the queries per collection. This would be useful for query collections that follow a certain workflow for their GraphQL application.

[imolorhe]

@carloditan24 Can you explain more? I am not sure I really understand what you are referring to.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[klawingco]

I'm almost done creating a Feature request for exporting collection but it seems already mentioned here.
It'll be a great help. Let me have a tactical dot here incase of updates :+1:

[imolorhe]

@klawingco I added that initially but no one mentioned it so I wasn't sure if anyone wanted it. Good to know someone is interested in it 😄