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 explict export to sample config #43

Closed
wants to merge 1 commit into from

Conversation

clach04
Copy link
Contributor

@clach04 clach04 commented Mar 9, 2016

Without this config fails to load.

Without this config fails to load.
@keegan-lillo
Copy link
Contributor

Unless the file is JSON. Would you like to create two examples? One for JSON and one for JS? Make sure to change the quotes to single and remove the quotes around the keys for the JS example. Honestly I'm tempted to get rid of the JSON examples so people don't need to fiddle with the wscript.

@Katharine what is your thoughts?

@Katharine
Copy link

As of SDK 3.10, the default wscript includes JSON files. I'd keep them.

@clach04
Copy link
Contributor Author

clach04 commented Mar 9, 2016

ahh, that explains issue #44 - so the (future) plan is that json files will be supported in CloudPebble? Any ETA on that? Having the current inconsistencies is painful. I'd certainly prefer to have pure json but right now I'm stuck with javascript with CloudPebble.

@Katharine
Copy link

CloudPebble will gain JSON file support in the relatively near future.

@keegan-lillo
Copy link
Contributor

Closed due to #44

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

Successfully merging this pull request may close these issues.

None yet

3 participants