When switching between Agent types in the in the new Agent form we need to clear the select fields values (targets,
receivers, control targets) when the current Agent does not support the respective method.
Added button to toggle visibility of disabled agents
* Moved index code to separate file
* Added cookie to allow toggling visibility of disabled agents
* Filter disabled agents based on cookie
* Removed js and use correct cookie name
* CR changes
* Agent to retweet all received tweet events
* Cache twitter rest client
* Update description, remove unused local
* Makes context strings more readable, style consistency
* to_h is not implemented in ruby 2.0
* In error case, include all agent_ids and event_ids
* Adds capability to favorite tweets
This restructures the Agent slightly to allow for retweeting and
favoriting. It is possible to do both at the same time.
- Renames the Agent from TwitterRetweetAgent
to TwitterActionAgent.
- Specs refactored
rm req json, not saving file, styled button a bit
skinny controller fat model
minor spacing mistake
build user credentials fixed mass assignment issue
undo mass assignment variables
spec in progress
spec
fixed exception issue
json fixtures
slight change to test
added test to assert credentials created for current user only
added tests to satisfy requirements
refined import method
added status 422
saving two lines of code
one more test
fixed small bug, words changed
minor change in test
styled file upload button
deleted unnecessary spec
switched to modal format
made modal more presentable
minor change to modal
fix indentation issue
ok nested correctly within form tag
quick rewording
changed glyphicon
skip failed jobs locked at and using update all
spec ready as well
rm without protection modify spec
rm unnecessary lines
work on delayed job feature
fixed render json
switched from ok to success
revert render json change for other methods
checking in work
test passed
reverting render and saving a line of code
add back sign in an user
run this on github
altered format.json
rm comment
prevent ajax error head no content
It is defaulted to `capitalized`, normalizing emitted headers by
capitalizing the names so downstream agents don't need to bother with
the letter cases.
Previously, the style of header names in an emitted event would vary
depending on the server and the backend HTTP library. Most notably, the
`net_http` backend downcases header names whereas other backends do not.
For backward compatibility, preexisting PostAgents are automatically
configured to have `event_headers_style` set to `raw` via migration.
- gives them a place to start from
- leverages existing code to import scenarios
- adds test coverage to seeds to ensure sees can run multiple times against the same db as is the case for Docker
- adds env variable to set if importing is turned on for new user
- adds env variable to point to a custom scenario for new users
When `content_type` contains a MIME type and `payload` is not a Hash the string in `payload` will be send as the HTTP
body and `content_type` is send as the `Content-Type` header.
#1361
