Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a debugging guide #347

Open
chasenlehara opened this issue Aug 29, 2017 · 1 comment
Open

Add a debugging guide #347

chasenlehara opened this issue Aug 29, 2017 · 1 comment

Comments

@chasenlehara
Copy link
Member

chasenlehara commented Aug 29, 2017

@frank-dspeed commented on Mon Jul 24 2017

or if your using async values that are undefined at first like a promis always return the promis directly and use isResolved alternate method when your function uses resolve wrapp it with if

{{#if entitiesList}}
  {{#each entitiesList}}
  {{/each}}
{{/if}}

we could also add some wrong examples for canDefine and canConnect there this are the places where most trouble happens in canjs

I think it would be useful if we created a can-connect debugging guide. I think we should create a new “guides” section in the can-connect docs and add a Debugging page under that. I think it would make sense to start adding more “guide” content under that section, such as the existing Creating Behaviors docs.

@chasenlehara chasenlehara changed the title Proposal: create a FAQ Page on canjs.com Add a debugging guide Aug 29, 2017
@frank-dspeed
Copy link

@chasenlehara i am for adding npm module debug to all can libs like define on all places and then we can debug all stuff well i did that for can define direktspeed/can-define-debug@f390eb0

it helped me a lot https://www.npmjs.com/package/debug

i use it also backend side for all projects i did forks of every can package but don't published them and can this way debug them all

a commun method that i use then is i add to the init of my app that if env DEBUG exists in the node start line then i add directly in the init the settings to the localstorage in browser

because you need to filter out very verbose things like babel :) they all are using that module and if you do something like DEBUG=* you get with steal and babel a lot of fun :)

so DEBUG=,-babe is most importent if you debug whole projects if you debug only a single component turn on debug for babel is also cool

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants