A starter kit for working with the Aurelia TypeScript type definitions
cmichaelgraham on update-for-perf-testing
updated bundles for perf testing (compare)
cmichaelgraham on master
Update README.md (compare)
cmichaelgraham on master
Update README.md (compare)
cmichaelgraham on master
yahoooooooooo !! beta (compare)
cmichaelgraham on 1.0.0-beta.1.0.2
cmichaelgraham on get-started-and-beta-update
updated todo-require-vs-ts (compare)
cmichaelgraham on get-started-and-beta-update
updated skel-nav-require-websto… (compare)
cmichaelgraham on get-started-and-beta-update
updated skel-nav-esri-vs-ts (compare)
cmichaelgraham on get-started-and-beta-update
updated skel-nav-esri-gulp (compare)
cmichaelgraham on get-started-and-beta-update
updated skel-nav-esri-atom (compare)
cmichaelgraham on get-started-and-beta-update
updated pwkad-aurelia-samples (compare)
cmichaelgraham on get-started-and-beta-update
updated nwind-breeze-bootstrap (compare)
attached(params, routeConfig, navigationInstruction) {
}
What are the backing types for these params?
activate
and not attached? https://aurelia.io/docs/api/router/interface/RoutableComponentActivate/method/activate
TS2556: Expected 15 arguments, but got 0 or more.
super(...args);
constructor(
protected rollbar,
protected ablyService,
protected dataStore,
protected db,
protected eventAggregator,
protected eventService,
protected notificationService,
protected router,
protected cache,
protected taskQueue,
protected templatingEngine,
protected http,
protected utils,
protected environment,
protected signaler) { }
class Child extends Super {
constructor(...rest) {
super(...rest);
}
...
constructor( protected rollbar, protected ablyService, protected dataStore, protected db, protected eventAggregator, protected eventService, protected notificationService, protected router, protected cache, protected taskQueue, protected templatingEngine, protected http, protected utils, protected environment, protected signaler) { }
TS2556: Expected 15 arguments, but got 0 or more.
I am very much impressed with typescript and angular for developing apps.
but to develop REST API i faced problems with javascript (no typing ..) and express redundant code.
So I have created a framework dinoloop which is powered by typescript heavily influenced by C# WebAPI and MVC.
Dinoloop focuses on OOPS and SOLID principles.
try dinoloop in developing small part of your REST API. You can then either gradually expand its presence,
or keep it contained to a few routes. You can develop your entire REST API in dinoloop or you can develop part of it.
project wiki: https://github.com/ParallelTask/dinoloop
Dinoloop has been designed from the start for gradual adoption, and you can use as little or as much dinoloop as you need. Perhaps you only want to develop some "REST APIs" using dinoloop and other REST APIs can be developed using expressjs. In this section, we will show how to create dinoloop REST API to an existing express app.
Step 1: Add HomeController (file: home.controller.ts)
import { ApiController, Controller, HttpGet } from 'dinoloop';
@Controller('/home')
export class HomeController extends ApiController {
@HttpGet('/get')
get(): string {
return 'Hello World!';
}
}
Step 2: Mount dinoloop and bind to express instance (file: app.ts)
const app = express();
app.use(bodyParser.json());
// Dino requires express instance and base-uri to which dino will be mounted
const dino = new Dino(app, '/api');
// Dino requires express router too
dino.useRouter(() => express.Router());
// Register controller
dino.registerController(HomeController);
// Bind dino to express
dino.bind();
// These are your normal express endpoints
app.get('/home', (req, res, next) => {
res.status(200).json('Hello World!');
});
app.get('/about', (req, res, next) => {
res.status(200).json('Hello World!');
});
// Start your express app
app.listen(8088, () => console.log('Server started on port 8088'));
Dinoloop is mounted on /api and all of its controller routes/endpoints which are registered with dinoloop are also mounted on /api. Dinoloop will handle those requests which are mounted on /api i.e. /api/home/get, the other end points /home and /about which are created by expressjs are not handled by dinoloop, this way you can slowly migrate your existing express app to dinoloop or you can start writing your new REST APIs using dinoloop.
please find the reference: https://github.com/ParallelTask/dinoloop
let result = this.filteredArray.map(a => a.time);
result.filter((data) =>{
let newDate = new Date(data *1000);
let timeResult = newDate.toTimeString();
return timeResult;
});
console.log(result);
<h3 class="card-header bg-primary lighten-1 white-text py-3">{{ data.tags[0].replace(/([a-z])([A-Z])/g, '$1 $2') }}<i class="fa fa-hdd-o float-right"></i></h3>