Record the process of submitting code to openharmony once

Write it down once OpenHarmony The process of submitting code

author ： nuts

official account ："

Big front end tour

"

OpenHarmony Preacher ,InfoQ Signed on ,CSDN Blogger , Huawei cloud sharing expert , Alibaba cloud expert Blogger ,51CTO Chief experience officer of Blog ,

Open source project GVA One of the members

, Focus on the sharing of large front-end technology , Include Flutter, Hongmeng , Applet , Android ,VUE,JavaScript.

Last night there was a great deal of thunder , Cannot sleep! , So I got up and wrote , In the process of writing , Found some problems in the official documents , So I wanted to improve ,

I submitted pr Address ：

Next, let's talk about some steps in the process of submitting changes ！

One 、DCO signed

1.DCO Signing website

Developer original statement Developer Certificate of Origin

Developer original statement

2. signed DCO

3. matters needing attention

git config --global user.name " Xu Jianguo " 
git config --global user.email "[email protected]"
git config --global --list

Be careful

DCO signed Name  And git config --global user.name  The setting remains always DCO signed E-mail And git config --global user.email The setting remains always

Two 、 Submission code

1. Download code

1.1 Find the community code repository where you want to submit the code ,fork One to his own private warehouse ;

1.2 Copy your own private warehouse “ clone / download ” Medium HTTPS/SSH Link to download code

Create workspace locally , then

git clone https://gitee.com/jianguo888/docs.git

2. Submission code

2.1 Merge the modified code into the submission Repository ;

git add .
git commit -sm ' Modify the information ' //  The submitted information contains signoff mailbox
git push -f origin master 
​

2.2 If the same problem is modified

git commit --amend

Usually one by one is recommended commit Solve a problem

3、 ... and 、 Submit ISSUE

1. Enter the community main code to build Issue（ No fork Code warehouse of ）, At the same time, pay attention to Issue There are many types of options to choose from , Choose... According to the actual situation

2. If the creation is successful, a #XXXXX(I5E2H2) Of IssueID, Submit PR Can relate to , relation PR Integration ,Issue It will shut down automatically .

Four 、 Submit PR

1. Submit the code to your own private repository , Refresh , Click on “+ Pull Request” build PR Merge the code into the community main code warehouse ;

2. Get into PR Submit interface , Code warehouse branches can be selected , And correlation ISSUE ID, Briefly describe the combined PR Modification and other information ;

3.PR Build success , First, by default DCO Check , Check success , You need to manually enter a reply in the comment area ”start build” To access the code CI Static checking and compilation .

5、 ... and 、 contact committer

committer：

https://gitee.com/openharmony/community/blob/master/zh/committer.md

1. committer The corresponding committer Home page of the person in charge , Find a way to contact

I was in committer The person in charge of the discovery , Then wechat search , From the crowd .

My modified content , By the way, post it here

Modify the content

establish visual File support for low code development

• On the JS In Engineering , Select the of the module pages Folder , Right click , choice
  New > JS Visual
  .

• In the pop-up dialog , Input JS Visual Name, Click on
  Finish
  .

3. establish JS Visual after , The low code directory structure will be automatically generated in the project , As shown in the figure below .

• entry > src > main > js > MainAbility > pages > index > index.js
   ： Logical description file of low code page , Defines all the logical relationships used in the page , Like data 、 Events, etc. . Please refer to
  JS Syntax reference
  . If you create multiple low code pages , be pages Multiple page folders and corresponding folders will be generated under the directory js file .
• 
  

• explain ：
    When developing with low code pages , Its relevance js Files cannot have siblings hml and css page , For example, in the figure above  
  js > MainAbility > pages > index
    The directory cannot contain hml And css file , Otherwise, there will be compilation errors .

• entry > src > main > supervisual > MainAbility > pages > index > index.visual
   ：visual The file stores the data model of low code pages , Double click the file to open the low code page , Carry out visual development and design . If you create multiple low code pages , be pages Multiple page folders and corresponding folders will be generated under the directory visual file .

• open “page.visual” file , The visual layout design and development of the page can be carried out .

explain ：

• Using low code to develop the interface , If the interface needs to use other controls that do not support visual layout for the time being , After the low code interface is developed , Click on

• Button , Convert the low code interface to hml and css Code .
  Be careful
  , Transcoding will delete visual File and its parent directory , And it is an irreversible process , Cannot pass after code conversion hml/css File reverse generation visual file .

• Scenario of multi device development , You can click the device in the upper right corner of the interface canvas / Mode switch button

• , Perform device switching or mode switching .

Develop with low code OpenHarmony After application or service , If you need to use simulator or real machine equipment for debugging / function , Need to click

Button , take JS Visual The file is converted to hml and css Code before you can run .

These are some of the things I did in the middle of the night , Of course, for the first time , Maybe not perfect , I would like to thank all the teachers who replied to me in the middle of the night . well , expect PR Closing succeeded .