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

Roadmap until beta #7

Closed
solkimicreb opened this issue Sep 19, 2016 · 2 comments
Closed

Roadmap until beta #7

solkimicreb opened this issue Sep 19, 2016 · 2 comments

Comments

@solkimicreb
Copy link
Member

solkimicreb commented Sep 19, 2016

These are the changes I would like to happen before NX beta is released. In my opinion the beta should be as stable as possible to let us focus on bug fixes and documentation improvements. With a good pace the below changes should take around 2-3 months. What is your opinion? Would you like to see a stricter roadmap with rough deadlines?

Framework changes:

  • form validation middleware POSTPONED
  • transition/animation middleware DONE
  • change Custom Elements polyfill to a subset of the official v1 polyfill POSTPONED (native implementation of type extension is buggy)
  • Shadow DOM support (requires changes in core and the render middleware) DONE
  • Scoped styles support DONE
  • optimize the nx-compile and nx-observe helper libraries for speed DONE
  • determine a list of officially supported browsers with exact versions
  • get 100% test coverage with all supported browsers
  • setup a linter

Small fixes and refactors:

  • refactor core and all middlewares one by one: main goal is speed and readabilty DONE
  • fix all reported bugs (naturally)

Docs and utilities:

  • NX-CLI for project seed generation
  • complex example apps and walk throughs written in NX IN PROGRESS
  • home page cleanup and public release for contributors (the home page is an NX app)
  • documentation for contributors
  • separate, short API documentation instead of 'cheat sheets'

What comes after the beta:

  • unofficial API freeze, breaking changes will happen only if unavoidable
  • release a distributed version of NX, where every middleware is in its own repo (something similar to what Express is doing)
@NetOpWibby
Copy link

I like it! Looking forward to using this after the beta! It would be neat if there was a flag for when a site using NX is accessed by an unsupported browser so I could easily set up a message for those users.

@solkimicreb
Copy link
Member Author

solkimicreb commented Nov 24, 2016

Great idea, I will include it in the next release. Sorry for the (very) late response.

EDIT: Flag is available form alpha 6 and up. You can access it as nx.supported.

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