All things Project Flogo... Report issues, chat with users & contributors. Join channel project-flogo/developers for project contribution & dev focused conversations.
JGrotex on gh-pages
Update index.html remove logo (compare)
JGrotex on gh-pages
Update index.html (compare)
JGrotex on gh-pages
Update index.html (compare)
JGrotex on gh-pages
Update index.html (compare)
JGrotex on gh-pages
Update index.html (compare)
JGrotex on master
Update _index.md (compare)
JGrotex on master
Update menu-footer.html (compare)
JGrotex on master
Update _index.md fix link (compare)
JGrotex on master
Update getting-started-webui.md (compare)
JGrotex on master
Update README.md (compare)
JGrotex on master
Create readme.md (compare)
JGrotex on master
Update timers.md Changed the n… Merge pull request #561 from dh… (compare)
JGrotex on master
Fix broken link to tibco labs Merge pull request #510 from ra… (compare)
C:\\Program Files (x86)\\Microsoft Visual Studio\\2017\\BuildTools\\MSBuild\\15.0\\Bin\\MSBuild.exe
failed with exit code: 1yarn install
? Or is it from another command? I’m seeing something similar (in Mac) during yarn install
when I use NodeJS v12 and NodeJS v14. However, it’s only a warning about an optional dependency and I can run the app. I can see in your logs that you’re using NodeJS v14.8.0, is there a chance you can downgrade to Node v10 and try?
handler.Handle(context.Background(), triggerData.ToMap())
to pass trigger-data to a flow. I noticed the following code that can directly pass trigger-data to the flow if nothing is mapped in the flow input. If I use this feature to make all trigger-data automatically available to the flow activities, would I still have to declare the data fields as trigger output in the descriptor.json? I guess that it is not necessary since I do not expect user to manually map these fields. However, it may be better to declare them in descriptor.json anyway to show user which fields are available. What would you think? It would be better if the Handler API allows me to specify some mappable fields and some auto-mapped fields as well.// https://github.com/project-flogo/core/blob/master/trigger/handler.go line 180
if act.actionInputMapper != nil {
inputMap, err = act.actionInputMapper.Apply(scope)
if err != nil {
return nil, err
}
} else {
inputMap = triggerValues
}
--cv
allows you to specify a core version, but I hope it allows me to specify a fork repo as well. I can work around it by editing the generated go.mod, although it is an extra-step that I have to script.