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

Separate Presention (Asp.Net Core) to consume API #44

Open
adanb007 opened this issue Jul 13, 2017 · 2 comments
Open

Separate Presention (Asp.Net Core) to consume API #44

adanb007 opened this issue Jul 13, 2017 · 2 comments
Assignees
@lucabriguglia
Labels
enhancement

Comments

@adanb007
Copy link
Contributor

We should refactor the Asp.net presentation to fully use the API. With this work, complete the API to ensure we can fully support any UI.
@adanb007
Copy link
Contributor Author

The additional intention is to have a complete API set. This will allow us to implement a UI using other UI frameworks (Angular 4, which I have started to work on, and others).

@lucabriguglia lucabriguglia self-assigned this Jul 16, 2017
@lucabriguglia
Copy link
Owner

This is a little bit tricky tough.
We should make sure that Weapsy can be used as a single application in case of deployment to a shared hosting for example.
But we should add the capability to have the api deployed on its own.
You can find some ideas in #34

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@lucabriguglia lucabriguglia

Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lucabriguglia @adanb007