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

Unify core.js and run.js conventions. #6

Open
sholladay opened this issue Sep 18, 2016 · 0 comments
Open

Unify core.js and run.js conventions. #6

sholladay opened this issue Sep 18, 2016 · 0 comments

Comments

@sholladay
Copy link
Member

sholladay commented Sep 18, 2016

Before the mini core can be brought online, it needs to know how to load the target app.

To do this reasonably, we should avoid any kind of lookup table for determining the main entry point of the app. That is a slippery slope and could cause headaches related to versioning if developers feel that it's okay to change the structure because we have a lookup table.

Instead, there should be a convention for all apps that core.js is the programmatic API and run.js has a side effect that initializes the app using that API.

A reference implementation can be found in sitecues-mobile run.js and core.js.

@sholladay sholladay changed the title Make core.js and run.js consistent conventions. Unify core.js and run.js conventions. Sep 18, 2016
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

No branches or pull requests

2 participants