sampathsris

{
  "name": "json-echo-server",
  "version": "0.1.0",
  "description": "Echos the request payload as JSON",
  "main": "server.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "author": "Sampath Sitinamaluwa",
  "license": "ISC"

sampathsris

Are you looking to make a quick prototype with React, but missing the alpha features like React Hooks?

Look no further. Check out my sandbox and fork it to do whatever you wish.

https://codesandbox.io/s/mm1o0klpv9

Happy coding!

/Sampath

sampathsris

using System;
using System.Linq;

namespace IntObjectTest
{
    public class Composer
    {
        static void Main()
        {
            Func<string, Func<string, string>> createAdder = s => x => x + s;

sampathsris

const express = require('express');
const session = require('express-session');
const passport = require('passport');
const ntlm = require('express-ntlm');
const ActiveDirectory = require('activedirectory');
const CustomStrategy = require('passport-custom');

const PORT = process.env.PORT || 8080;
const adconfig = {

sampathsris

/**
 * This is a crude hack to connect to an IFS Aurena endpoint using IFS Database
 * Identity Provider, and then query for projections from Node.js. Not sure the
 * purpose of this, but feeling it would come handy for something. You can do
 * the same in Postman, but I'm feeling the stateful client (read: with cookies)
 * will be helpful in chaining requests.
 *
 * Tested with:
 *  "dom-parser": "^0.1.5",
 *  "request": "^2.87.0",

sampathsris

@echo off

:: Harvest path is C:\Program Files (x86)\CA\SharedComponents\PEC\bin
:: Node.js path is C:\Program Files (x86)\nodejs
:: Let's replace Harvest's path with Node.js's path
set PATH=%PATH:C:\Program Files (x86)\CA\SharedComponents\PEC\bin;=%;C:\Program Files (x86)\nodejs;

:: Start a command prompt. But the environment variable change in previous
:: line will make sure that this new command prompt will run Node.js's node.exe
:: rather than Harvest SCM's node.exe.