Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / ejizba/func-nodejs-prototype issues and pull requests

#29 - Deployment steps via CI/CD example

Issue - State: open - Opened by sunil-bagde over 1 year ago

#28 - Functions are not working on Azure

Issue - State: closed - Opened by camila-akqa almost 2 years ago - 5 comments

#27 - Update Durable JS templates

Pull Request - State: closed - Opened by hossam-nasr almost 2 years ago

#26 - Update Durable TS Templates

Pull Request - State: closed - Opened by hossam-nasr almost 2 years ago

#25 - container +

Pull Request - State: closed - Opened by diberry almost 2 years ago

#24 - Extension bundle link in README

Issue - State: open - Opened by diberry almost 2 years ago - 1 comment

#23 - await `request.text()` (JS)

Pull Request - State: closed - Opened by hossam-nasr almost 2 years ago

#22 - await `request.text()`

Pull Request - State: closed - Opened by hossam-nasr almost 2 years ago

#21 - clean up and add readme

Pull Request - State: closed - Opened by hossam-nasr almost 2 years ago

#20 - Add extensions.csproj and update package.json to use public SDK

Pull Request - State: closed - Opened by hossam-nasr almost 2 years ago

#19 - is the new function model deployable to azure?

Issue - State: closed - Opened by jamiehaywood about 2 years ago - 1 comment

#18 - Delete `dist` folder as part of the build script

Issue - State: open - Opened by hossam-nasr about 2 years ago - 1 comment

#17 - Prettier

Pull Request - State: closed - Opened by hossam-nasr about 2 years ago

#16 - Some engineering updates

Pull Request - State: closed - Opened by hossam-nasr about 2 years ago

#15 - Add durable orchestration and entity samples using `app.generic`

Pull Request - State: open - Opened by hossam-nasr about 2 years ago - 1 comment

#14 - Add durable orchestration and entity examples

Pull Request - State: closed - Opened by hossam-nasr about 2 years ago - 2 comments

#13 - Add generic durable triggers

Pull Request - State: closed - Opened by hossam-nasr about 2 years ago - 1 comment

#12 - `eventGrid` does not exist on namespace `app`

Issue - State: closed - Opened by nturinski about 2 years ago - 1 comment

#11 - Option C: Provide an option to register more than one output binding at once?

Issue - State: closed - Opened by hossam-nasr over 2 years ago - 1 comment

#10 - Remove name property from trigger binding options

Issue - State: closed - Opened by hossam-nasr over 2 years ago - 1 comment

#9 - How should we register functions?

Issue - State: closed - Opened by hossam-nasr over 2 years ago - 1 comment

#8 - Should we use the word "Binding"

Issue - State: closed - Opened by ejizba over 2 years ago - 1 comment

#7 - How should we name timer triggers?

Issue - State: closed - Opened by hossam-nasr over 2 years ago - 1 comment

#6 - How should we name adding HTTP triggers?

Issue - State: closed - Opened by hossam-nasr over 2 years ago - 1 comment

#5 - How to set output value

Issue - State: closed - Opened by ejizba over 2 years ago - 1 comment

#4 - What should we name registering a function

Issue - State: closed - Opened by ejizba over 2 years ago - 2 comments

#3 - Use an `app` root object for all function registrations

Issue - State: closed - Opened by ejizba over 2 years ago - 1 comment

#2 - Additional design approach

Pull Request - State: closed - Opened by aaronpowell over 2 years ago - 1 comment

#1 - OptionC: adding registerUserFunction

Issue - State: closed - Opened by YunchuWang over 2 years ago - 1 comment