Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Documents to contribute #40

vallemar started this conversation in 1. Ideas & Discussions
Discussion options

I've recently wanted to contribute, and have, but developed in the @NativeScript folder under node_modules.
It has been impossible to build the core for me since I usually work on windows and for now (I know there is a PR to solve this) the core cannot be built on windows.

It is very uncomfortable to work on some of the core having to enter node_modules/@nativescript of my sample application and with each change I make I have to stop the app and start it. (I think it has to be more agile than I am doing)

Also, I have seen the interactive window and it seems good to me, but I think that for someone who just wants to test what they are doing in the core it is too much, at least without a documentation that says what each thing is for.

This RFC proposes:

  • Clear and concise documentation for new developers about the fastest way to develop (using the core) new functionality or fix.
  • Documentation on how to add unit test or integration.
  • Windows support.
You must be logged in to vote

Replies: 0 comments

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
1 participant

AltStyle によって変換されたページ (->オリジナル) /