![]() ![]() Our goal is to implement a backend that will work with the notes application from part 2. The newest version of Node supports a large majority of the latest features of JavaScript, so we can use the latest features without having to transpile our code. The situation with JavaScript running in the backend is different. Please make sure that your version of Node is at least as new as the version used in the material (you can check the version by running node -v in the command line).Īs mentioned in part 1, browsers don't yet support the newest features of JavaScript, and that is why the code running in the browser must be transpiled with e.g. This course material was written with version v18.13.0 of Node.js. We will be building our backend on top of NodeJS, which is a JavaScript runtime based on Google's Chrome V8 JavaScript engine. When I first filter/search for text in the console, and then perform a select-all/copy/paste, then only the filtered text (matching search criteria) is present in the document/application.In this part, our focus shifts towards the backend: that is, towards implementing functionality on the server side of the stack. cmd+A) and copy the text in the console, and then paste that copied text in another (external to Postman) document/application, then I can see that all the text from the Postman console is now present in the document/application. Please fix this issue before I decide to switch to another tool. The point is to increase value, not pain. The workarounds do not scale well and I don't want to become the guy who is debugging the workaround for everyone. Just imagine how many people are wasting valuable time trying to find a workaround - mucking with the CSS, doing stuff with newman, etc. ![]() It looks like there are tons of articles on the internet about ways to address the issue of being able to save Postman console output. However, being unable to copy this console output reliably in Postman means that I might need to consider using a different tool. Many of these use cases require them to be able to copy the console output to share with others via email, Slack, or other means. I've written small tools (employing the Tests portion) that help them be proactive in their role and diagnose/solve customer issues. I share my collections with TAMs and Customer Support because it's far easier for them to run a Postman collection than a python script. What you've created is a great tool - it makes it super easy build and share API collections with others. Ideally, I think we should have a button for Copy all, or a button to write the raw contents of the console to a file.Īpp information (please complete the following information):Īdd any other context about the problem here. Selecting all + copying grabs the entire contents of the console. Notice that what is pasted is only a small subset of the total Console logs.Click anywhere on the Console and select all (command + A, on MAC), then copy (command + C, on Mac).Populate the Console with more log messages than fit on the screen (i.e. ![]() Open Postman Console (command + option + C).This is problematic if a user needs to copy the content of the Postman Console, and paste it into (e.g.) a text editing app. If the console contains a lot of log messages, this mean a lot is missed. When selecting all (command + A) of the contents of the Postman Console and copying, only the contents visible in the window (plus a little extra) are copied. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |