Conversation
|
Does anyone use the neo-gui project, Should we remove it? |
Won't hurt to keep it. At least this pr only focus on merging existing code. |
I agree with @Liaojinghui. Let's avoid changing the structure during the migration. |
|
@lock9 @shargon @roman-khimov @AnnaShaleva @superboyiii In case you feel it hard to verify the code, this script will help you to review that two folders (including all subdirs) of C# codes are exactly the same. If they are not, difference will be printed. Directory Comparison ScriptThis script is designed to compare C# files between two directories (referred to as the original and merge directories), including their subdirectories. It ensures that not only the contents of the C# files are identical, but also that the directory structures and the number of files are the same. Features
Usage
#!/bin/bash
# Check if two arguments are passed
if [ "$#" -ne 2 ]; then
echo "Usage: $0 <original_directory> <merge_directory>"
exit 1
fi
original_dir=$1
merge_dir=$2
# Function to compare two directories
compare_directories() {
local dir1=$1
local dir2=$2
# Get relative paths of all C# files in the first directory
local files_dir1=($(cd "$dir1" && find . -type f -name "*.cs"))
# Loop through each file in the first directory
for file1 in "${files_dir1[@]}"; do
local file2="${dir2}/${file1#./}"
if [ ! -f "$file2" ]; then
echo "File missing in $dir2: $file1"
continue
fi
# Compare the contents of the two files
if ! cmp -s "${dir1}/${file1}" "$file2"; then
echo "Difference found in file: $file1"
echo "----"
diff "${dir1}/${file1}" "$file2"
echo "----"
fi
done
}
# Compare original to merge
compare_directories "$original_dir" "$merge_dir"
# Compare merge to original (to catch any extra files in merge)
compare_directories "$merge_dir" "$original_dir"
|
|
We can also add it to the workflow to automatically check the code base. name: Compare Codebases
on:
pull_request:
branches: [ master ]
jobs:
compare:
runs-on: ubuntu-latest
steps:
- name: Checkout Repository
uses: actions/checkout@v2
- name: Checkout Target Repository
uses: actions/checkout@v2
with:
repository: 'https://github.com/neo-project/neo-node.git'
ref: 'https://github.com/neo-project/neo-node/commit/da786195cfb6d70236bb37611c37d7016bbc3aae'
path: 'neo-cli'
- name: Compare Directories
run: |
chmod +x ./compare_directories.sh
./compare_directories.sh ./ ${{ github.workspace }}/Neo.CLI > difference.log || true
- name: Upload differences if any
uses: actions/upload-artifact@v2
if: failure()
with:
name: differences
path: difference.log |
I think I trust |
As long as it can convince you to move monorepo faster. |
|
@lock9 could you update the code? |
|
Hi @shargon, |
|
The issues are ready to be transferred to this repository, the description and tag have been updated. |
…ct#905 (cschuchardt88) Added icon to applications neo-project#908 (cschuchardt88)
Added blockchain show block/transactions/contracts commands neo-project#905 (csc…
|
@lock9 we need to update the main README |
Ok. What are we going to do about the code coverage? Add the UT? |
What happened? I just updated the readme...? |
* master: (30 commits) Set project as nullable (neo-project#3042) Fix: fix equal (neo-project#3028) Added README to packages (neo-project#3026) Nuget MyGet Fix (neo-project#3031) Add: print out the stack (neo-project#3033) fixed myget (neo-project#3029) Fixed MyGet Workflow (neo-project#3027) Package icons - hotfix (neo-project#3022) Nuget Package Icon & Symbols (neo-project#3020) Fix warning (neo-project#3021) Neo-node Migration (neo-project#2990) Remove unnecessary default seedlist (neo-project#2980) Fix Neo VM target frameworks (neo-project#2989) Update Neo.VM location in README.md (neo-project#2988) Migrating Neo VM (neo-project#2970) 3.6.2 (neo-project#2962) fix ut (neo-project#2959) Validate serialization during Contract deploy and Update (neo-project#2948) code optimization (neo-project#2958) check null scriptcontainer (neo-project#2953) ...
Migrating neo-node project into the Neo repository.
Observations:
neoworkflow wasn't updated to distribute neo-cliQuestion:
Should I update the workflow to generate and test neo-cli?