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

What tools can be used? #29

Closed
BE-Webdesign opened this issue Feb 9, 2017 · 2 comments
Closed

What tools can be used? #29

BE-Webdesign opened this issue Feb 9, 2017 · 2 comments
Labels
[Type] Question Questions about the design or development of the editor.

Comments

@BE-Webdesign
Copy link
Contributor

BE-Webdesign commented Feb 9, 2017

Hi!

I was curious if there were any tooling limitations surrounding this project. I would like to be able to use es6 stuff, but wasn't sure if adding a build process, etc. was what this repository was all about. If a node.js build process, is not permitted, or if there is a future build process in mind, it would be nice to know what can be used or what potentially lies ahead. On top of build tools ( or lack thereof ), what unit testing stuff can be used?

No worries if this is not on the agenda at this time, but I would like to help out and having a bit of direction on what tools you like to use can help guide my contributions. For now I will do non es6, but it could get ugly 😄

Thank you!

@mtias
Copy link
Member

mtias commented Feb 9, 2017

Thanks for joining!

We had to revert a spread operator before due to browser support: 08fe7d5

We can bring some building process if we really feel constrained, though the main goal for the UI prototype is just to have an interactive mockup to serve as the basis for the real thing later on. So consider the code in blocks.js to be throwaway. We should start adding more technical prototypes soon and we should definitely polish that more as we move along.

@mtias mtias added the [Type] Question Questions about the design or development of the editor. label Feb 9, 2017
@mtias
Copy link
Member

mtias commented Feb 17, 2017

@BE-Webdesign as we put our attention on more technical prototypes we'll have build processes and the ability to use ES6, etc.

@mtias mtias closed this as completed Feb 17, 2017
omarreiss added a commit that referenced this issue Jun 26, 2018
chore: Add `package-lock.json` to domready package
hypest pushed a commit that referenced this issue Nov 2, 2018
ntwb added a commit that referenced this issue May 31, 2020
Update Travis and AppVeyor badges
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Type] Question Questions about the design or development of the editor.
Projects
None yet
Development

No branches or pull requests

2 participants