chore(repository): improve repository structure and naming #11
Conversation
I was also wondering if I should delete them or not, I guess we can keep them until we re-write the recommend specs |
|
Ah true the recommend is not in the |
| return url; | ||
| } | ||
|
|
||
| export function serializeQueryParameters(parameters: Readonly<Record<string, any>>): string { |
There was a problem hiding this comment.
not related to this PR: Is this function replacable with new UrlSearchParams?
There was a problem hiding this comment.
I think it is yes, some things are deprecated but I wanted to have the same behavior as the client at first.
There was a problem hiding this comment.
fair enough, we might want to investigate after we have some test in place
|
Can you rename |
I've removed the old |
Summary
Since we want to go for a monorepo I thought it was needed to improve its structure so we can iterate on our tooling/other API clients in parallel.
There should be no code changes, only some renaming/restructuring.
Test
See the proposed structure here: https://github.com/algolia/api-client-automation-experiment/tree/chore/repository or locally