Comments (6)
I don't think having some print statements present is necessarily a bad thing. But if you have tons you could create a debug variable and set to false in the community app and change in production worst case if you don't want to just comment them out.
from community.
or (and I don't know if this is possible) - shunt that output during compile/test in the workflow so it doesn't flood the github logs.
from community.
So I'm sure it is possible, but even if it doesn't flood the github logs, I think it would still flood their logs on their servers?
I was simply giving you an alternative if you wanted at least a quicker temporary fix if this is possible to do. Not having to worry about commenting them out would be nice though, I don't disagree.
from community.
I don't typically leave them in code I submit - I use it for debugging & then delete them. But I see other folks still have them. was helping someone else out with a failed test & I had to weed through a bunch of another submitter's app debugging/print to find the error in the app we were working on. Just trying to streamline it as a general rule. we're on the same page.
from community.
Yeah, I'm with you if they are super useful and beyond just hit or miss on the api, usually they get commented out or just deleted.
But agreed, wading through those is a pita.
from community.
We're automatically closing this issue because it hasn't had any activity in 30 days. If that seems like a mistake, please feel free to re-open. Thanks!
from community.
Related Issues (20)
- How to pass config values when using `pixlet serve`? HOT 2
- Remove apps/deathvalleytemp/deathvalleytemp.go HOT 1
- Jacket app doesn't indicate how to get API keys HOT 7
- connection error HOT 2
- Spotify app doesn't update when song changes HOT 1
- Severe Thunderstorm Watch/Warning Display Issues HOT 1
- Production server .webp render not matching development pixlet renders. HOT 1
- Toggle and Dropdown Schema Randomly Change HOT 1
- Creator metrics/dashboard HOT 2
- app: shopify sales trends issue HOT 1
- Production server .webp render not matching development pixlet renders. (mk. II) HOT 2
- Schema.Location is buggy (and confusing) in local development HOT 1
- Baywheels GBFS feed changed HOT 2
- Allow passing a CSS selector to check if site is up HOT 1
- Allow passing a CSS selector to check if site is up
- MLB standings app displaying teams in the wrong order HOT 3
- make romaji text aqua instead of blue HOT 1
- WMATA buses app not reading schema settings correctly
- "Jacket" app doesn't update HOT 2
- Skordle Scores App Removal HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from community.