-
Notifications
You must be signed in to change notification settings - Fork 7
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
0.1 release roadmap #1
Comments
@basarat I would like to publish a 0.1alpha :
|
No. Publish as yourself. You can add others over time using e.g.
https://www.npmjs.com/package/tsps (typescript project services) pronounced |
@basarat I'm pretty much ready for initial release, could you give a look at the project (doc, code, package.json, etc...) before publishing ? |
Great stuff! love the docs! |
publish away ❤️ |
Ok now that the project is a little stable I would like to create a little roadmap.
Name
I quite hate the name that I have given to this project, if anybody has a better idea ... :D
Build system
Promise
Actually I have hidden the dependency over 'bluebird' (see : https://github.com/TypeStrong/typescript-project-services/blob/master/src/main/project.ts#L20-L21) to avoid forcing people consuming this project to have a bluebird declaration file, however in fact it would be better to let people inject the promise library they are comfortable with.
Documentation
The project need a read me a description and any kind of documentation helping to consume this project.
Feature
Actually the project expose 4 services, completion, definition, error, formatting. The project needs to expose pretty much all the possibilities given by the typescript language service.
Service interface
The project services interfaces are pretty much all the time consuming/emitting positions based on line/column (see: https://github.com/TypeStrong/typescript-project-services/blob/master/src/main/index.ts#L10-L13), it's pretty handy for brackets-typescript, since it's the format used for codemirror, however will it be the case for atom-typescript ?
Also I guess we should integrate the project with tsconfig instead of using a custom config format
Tests
Some parts of the project are somewhat well tested (like project/projectManager) but some others are not tested at all, since the project want to become a foundation for other project it needs to be well-tested and we need code-coverage
Contributing
Finally we need a contributing.md+ code guideline, also we need to add tslint, that will help anybody that want to contribute to respect our coding standard.
Feel free to comment to give me your point of view, I'll edit the issue if I missed something.
Task list
Edit: added tslint part and tsconfig part
Edit2: added the task list
*Edit3 : remove bullet point that won't be addressed
The text was updated successfully, but these errors were encountered: