AURELIA HTTP CLIENT EXAMPLE FULL
AURELIA HTTP CLIENT EXAMPLE CODE

You only have to use the DI decorators where you want to use them. ThatвЂ™s not the case with AureliaвЂ™s DI.ДЄurelia Services - such as components - are plain Typescript classes. Sometimes it can be difficult to use something universal in a specific framework or library, maybe you need additional decorators (therefore additional unnecessary layers) or sometimes this is even nearly impossible because of the incompatible principles. Injecting dependenciesДЄs I mentioned, we will use dependencies from our other library called sn-client-js. There are a lot of more complex possibilities however, like dynamic composition, value converters and computed properties. If you have a basic knowledge about HTML and Typescript you only have to learn how data binding works to create basic components. One of the cool things about Aurelia components is that you donвЂ™t need to dive deep in the framework.

AURELIA HTTP CLIENT EXAMPLE CODE

If you take a look at the example from the Aurelia hub you can notice that there is only a little piece of framework-specific code in the template and nothing (!) in the view-model. View templates are written in a standard-based HTML extended with a very simple binding language and the view-model can be written in ES2015 or Typescript. The view is separated from the view-model. In the first round, we have to develop these controls as Aurelia components.ДЄurelia has a clear concept of how a component should look like.

AURELIA HTTP CLIENT EXAMPLE FULL

Field controls represent a specific field type (letвЂ™s say a simple short text) while view controls represent a contentвЂ™s full view for a specific action (for example an Edit view of a user) and is built from FieldControl components based on the generated schema from sn-client-js. We have two major types of controls: Field controls and View controls. View- and Field Controls - The next layer of our building blocks They will contain Aurelia / React specific components and will use the core functionality from sn-client-js. We have just started to develop our component packages that depend on templating and data binding, thatвЂ™s where and why we have to create the two new packages - sn-controls-aurelia and sn-controls-react. Some features - like templating, data binding or routing - are implemented in each and every framework and they are based on different concepts. They work well in the core of our front-end library called sn-client-js. We have quite so much sensenet ECM specific client side features that can be made framework independent like user session management, content operations, querying. I will explain why weвЂ™ve chosen Aurelia besides React. At this point weвЂ™ve decided to build on two of them for SPA development. But when it comes to build our new UI components we really had to choose between the modern libraries and frameworks. Our concept with sensenet ECM 7+ is to support a wide range of front-end developers as far as possible with our sn-client-js package that can be integrated into almost every NPM development pipeline. In the end,we're still building an app so all the design patterns and SOLID stuff applies, but we're using Aurelia/TypeScript instead of WPF/C#.ItвЂ™s a quite challengeing task to choose a front-end toolset nowadays, especially for a development platform. While I'm still a novice when it comes to developing single page apps, I can't help but notice how often I can use the same approaches I'm using on the server side. But I recommend using this kind of abstraction primarily for developer friendliness as we don't need to change how we communicate with the server very often. Since I was using an abstraction like the above, I just needed to change the ApiClient implementation and nothing else.

For commands: baseUrl/, r=> success(r)) ДЄs a trivia fact, when I've started building my app, Aurelia's HttpClient was a wrapper over XMLHttpRequest, but now it implements the FetchApi.

On my server, I'm using the following conventions I want my app to take a Command/Query approach i.e when something needs to change I'll send a command request and when I just want some data but I don't want to change anything then I'll send a query request.

But this client is a bit to low level for my taste, I want my app to not be concerned with how a client communicates with the server. Every SPA needs a way to communicate with the server and Aurelia features a HttpClient that implements the Fetch API.

Aurelia http client example