Skip to content
This repository has been archived by the owner on Aug 30, 2023. It is now read-only.

[ENR-48] 🚀 Feature: Complete REST API to compliment our GraphQL API #95

Open
1 of 4 tasks
nirga opened this issue Jan 20, 2023 · 0 comments
Open
1 of 4 tasks
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@nirga
Copy link
Contributor

nirga commented Jan 20, 2023

🔖 Feature description

We started Enrolla with REST API only, but at some point decided to switch over to GraphQL as it makes lots of the queries in our management UI easier. We want to continue the REST API development to complement GraphQL.

🎤 Why is this feature needed ?

Using the REST API may be easier to some apps so we need to aim for complete feature parity between GraphQL and REST.

✌️ How do you aim to achieve this?

Following Nest.js conventions and the work already done in the Features module in the backend, we need to add controllers to the following modules / entities with CRUD support:

  • Customers
  • Packages
  • Organizations (read only)

🔄️ Additional Information

No response

👀 Have you spent some time to check if this feature request has been raised before?

  • I checked and didn't find similar issue

Are you willing to submit PR?

None

ENR-48

@nirga nirga changed the title 🚀 Feature: Complete REST API to compliment our GraphQL API [ENR-48] 🚀 Feature: Complete REST API to compliment our GraphQL API Jan 20, 2023
@nirga nirga added the good first issue Good for newcomers label Jan 20, 2023
@galkleinman galkleinman added the enhancement New feature or request label Jan 31, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants