Security News
Highlights from the 2024 Rails Community Survey
A record 2,709 developers participated in the 2024 Ruby on Rails Community Survey, revealing key tools, practices, and trends shaping the Rails ecosystem.
alphapolls
Advanced tools
A GraphQL API for managing and analyzing online surveys using ApolloServer and a MongoDB backend
npm install alphapolls
The instance of ApolloServer exposed by alphapolls must be plugged-in to an existing express app under a custom endpoint through the applyMiddleware method.
In order to setup the API server a function must be provided that takes an express request object and returns a GraphQL context object. The request object should have a user property and clearance property already set by an authentication middleware.
The clearance property of the context object must be set to one of 'admin', 'user' or 'public'. The user property of the context object, if the clearance property is set to 'user', must be set to the _id of the authenticated user as in the User model. If the clearance property is set to 'admin' or 'public', the user property may be set to anything.
const setContext = req => {
if (!req.session) {
throw new Error('a session must be set')
}
if (!req.session.clearance || !req.session.user) {
throw new Error('a valid session object must be provided')
}
return {
clearance: req.session.clearance,
user: req.session.user
}
}
Once a setContext function has been declared as above, we may proceed to apply the alphapolls server as a middleware to an express app.
const express = require('express')
const alphapolls = require('alphapolls')
const app = express()
const server = alphapolls.applyMiddleware(app, setContext, '/some-optional-custom-endpoint')
server.listen(3040)
All endpoints can be reached via a standard GraphQL request. The schema types are as follows:
type Question {
_id: String!
value: String!
input_type: String!
data_type: String!
input_minimum: Float
input_maximum: Float
choice: [String]
allow_arbitrary: Boolean!
date_created: String!
date_modified: String!
answer(value: String, date_created: String, date_modified: String, response: String): [Answer]
survey(name: String, date_created: String, date_modified: String, topic: [String], media: [String], survey_instance: [String]): [Survey]
}
type Answer {
_id: String!
question(_id: String, value: String, input_type: String, data_type: String, input_minimum: Float, input_maximum: Float, allow_arbitrary: Boolean, date_created: String, date_modified: String, choice: String, survey: [String]): [Question!]!
value: String!
date_created: String!
date_modified: String!
response(_id: String, survey_instance: String, date_created: String, date_modified: String): [Response]
}
type Source {
_id: String!
name: String!
website: String
date_created: String!
date_modified: String!
media(_id: String, uri: String, title: String, content: String, date_created: String, date_modified: String, survey: [String]): [Media]
}
type Media {
_id: String!
uri: String!
title: String!
content: String!
source(_id: String, name: String, website: String, date_created: String, date_modified: String): [Source!]!
date_created: String!
date_modified: String!
survey(_id: String, name: String, date_created: String, date_modified: String, topic: [String], question: [String], survey_instance: [String]): [Survey]
}
type Survey {
_id: String!
name: String!
topic: [String]
media(_id: String, uri: String, title: String, content: String, source: String, date_created: String, date_modified: String): [Media]
question(_id: String, value: String, input_type: String, data_type: String, input_minimum: Float, input_maximum: Float, allow_arbitrary: Boolean, date_created: String, date_modified: String, choice: String, answer: [String]): [Question!]!
date_created: String!
date_modified: String!
survey_instance(_id: String, start_date: String, end_date: String, date_created: String, date_modified: String, response: [String], user: [String]): [SurveyInstance]
}
type SurveyInstance {
_id: String!
survey(_id: String, name: String, date_created: String, date_modified: String, topic: [String], media: [String], question: [String]): [Survey!]!
start_date: String!
end_date: String!
date_created: String!
date_modified: String!
response(_id: String, date_created: String, date_modified: String, answer: [String]): [Response]
user(_id: String, auth_provider: String, auth_token: String, clearance: String): [User]
}
type Response {
_id: String!
survey_instance(_id: String, survey: String, start_date: String, end_date: String, date_created: String, date_modified: String, user: [String]): [SurveyInstance!]!
answer(_id: String, question: String, value: String, date_created: String, date_modified: String): [Answer!]!
date_created: String!
date_modified: String!
}
type User {
_id: String!
auth_provider: String!
auth_token: String!
clearance: String!
date_created: String!
date_modified: String!
survey_instance(_id: String, survey: String, start_date: String, end_date: String, date_created: String, date_modified: String): [SurveyInstance]
}
type Query {
user(_id: String, auth_provider: String, auth_token: String, clearance: String, survey_instance: [String]): [User]
response(_id: String, survey_instance: String, date_created: String, date_modified: String, answer: [String]): [Response]
survey_instance(_id: String, survey: String, start_date: String, end_date: String, date_created: String, date_modified: String, response: [String], user: [String]): [SurveyInstance]
survey(_id: String, name: String, date_created: String, date_modified: String, topic: [String], media: [String], question: [String], survey_instance: [String]): [Survey]
media(_id: String, uri: String, title: String, content: String, source: String, date_created: String, date_modified: String, survey: [String]): [Media]
source(_id: String, name: String, website: String, date_created: String, date_modified: String, media: [String]): [Source]
answer(_id: String, question: String, value: String, date_created: String, date_modified: String, response: String): [Answer]
question(_id: String, value: String, input_type: String, data_type: String, input_minimum: Float, input_maximum: Float, allow_arbitrary: Boolean, date_created: String, date_modified: String, choice: [String], answer: [String], survey: [String]): [Question]
}
type Mutation {
create_response(survey_instance: String!, answer: [String!]!): String!
create_survey_instance(survey: String!, start_date: String!, end_date: String!): String!
create_survey(name: String!, topic: [String], media: [String], question: [String!]!): String!
create_media(uri: String!, title: String!, content: String!, source: String!): String!
create_source(name: String!, website: String): String!
create_answer(question: String!, value: String!): String!
create_question(value: String!, input_type: String!, data_type: String!, input_minimum: Float, input_maximum: Float, allow_arbitrary: Boolean, choice: [String]): String!
update_response(_id: String!, survey_instance: String, answer: [String]): String!
update_survey_instance(_id: String!, survey: String, start_date: String, end_date: String): String!
update_survey(_id: String!, name: String, topic: [String], media: [String], question: [String]): String!
update_media(_id: String!, uri: String, title: String, content: String, source: String): String!
update_source(_id: String!, name: String, website: String): String!
update_answer(_id: String!, question: String, value: String): String!
update_question(_id: String!, value: String, input_type: String, data_type: String, input_minimum: Float, input_maximum: Float, allow_arbitrary: Boolean, choice: [String]): String!
}
FAQs
polling api
The npm package alphapolls receives a total of 1 weekly downloads. As such, alphapolls popularity was classified as not popular.
We found that alphapolls demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
A record 2,709 developers participated in the 2024 Ruby on Rails Community Survey, revealing key tools, practices, and trends shaping the Rails ecosystem.
Security News
In 2023, data breaches surged 78% from zero-day and supply chain attacks, but developers are still buried under alerts that are unable to prevent these threats.
Security News
Solo open source maintainers face burnout and security challenges, with 60% unpaid and 60% considering quitting.