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

Provide explicit spec to component API instead of implicit proxy over extend #23

Closed
nesterone opened this issue Aug 20, 2017 · 0 comments

Comments

@nesterone
Copy link
Owner

Yep, it's not obvious even from docs, it should be public utility function, so 'vue-vega-weppack' plugin would be using it to generate vue vega components directly from specs and/or js files

nesterone pushed a commit that referenced this issue Aug 25, 2017
- use default create options in view delegate
- exclude 'component as spec' example, because of #23
@nesterone nesterone moved this from Backlog to In Progress in Docs and initial features - Vega Lite Only Aug 25, 2017
nesterone pushed a commit that referenced this issue Sep 2, 2017
… extend #23

- copy spec props to component's props default
nesterone pushed a commit that referenced this issue Sep 2, 2017
… extend #23

- start using spec as json dependency for tests
nesterone pushed a commit that referenced this issue Sep 2, 2017
… extend #23

- use real specs to check props
- can't run example spec with `spec/vega-lite/index.js` (switch to `test/unit/specs/vegaLiteSpecSamples.js`)
nesterone pushed a commit that referenced this issue Sep 2, 2017
… extend #23

- provide some sort of integration test for component creation from the spec
nesterone pushed a commit that referenced this issue Sep 2, 2017
… extend #23

- update docs with link to webpack idea
@nesterone nesterone moved this from In Progress to Done in Docs and initial features - Vega Lite Only Sep 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant