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

WIP: Feature #3186/import alignment data with USFM import, and fix alignment export to USFM #3868

Closed

Conversation

PhotoNomad0
Copy link
Contributor

@PhotoNomad0 PhotoNomad0 commented Feb 17, 2018

Closed due to breaking changes in develop. Created new: #3895

Describe what your pull request addresses (Please include relevant issue numbers):

Please include detailed Test instructions for your pull request:

  • on USFM export, should see chapter and verse markers beginning on new lines.
  • on USFM export of project with unaligned chapters, should see data for all chapters, even the unaligned.
  • on USFM import of project with alignments, should see same alignment data in WA: unaligned words should show up in word bank and aligned words should show also.

Standard Test Instructions for PR Review Process:

  • Double check unit tests that have been written
  • Check for documentation for code changes
  • Check that there are not inadvertent commits to tC Apps when reviewing a tC Core PR
  • Checkout the branch locally and ensure that app runs as expected
    • Ensure tests pass
    • Open and watch the console for errors
    • Make sure all actions perform as expected
    • Import and Load a new Project
    • Load a tool and perform basic actions
    • Switch tools and perform basic actions
    • Switch project to an existing project
    • Load a tool and perform basic actions
    • Switch tools and perform basic actions
    • Next time reverse the order of importing after loading an existing project
  • Reviewer should double check the DoD in the ISSUE, including the “spirit” of the story
  • Ask Ben or Koz if you have any concerns about implementation (especially UI related)

This change is Reviewable

@codecov
Copy link

codecov bot commented Feb 17, 2018

Codecov Report

Merging #3868 into develop will increase coverage by 0.33%.
The diff coverage is 84.31%.

Impacted file tree graph

@@             Coverage Diff             @@
##           develop    #3868      +/-   ##
===========================================
+ Coverage    49.71%   50.05%   +0.33%     
===========================================
  Files          224      224              
  Lines         5652     5710      +58     
  Branches       905      922      +17     
===========================================
+ Hits          2810     2858      +48     
- Misses        2434     2440       +6     
- Partials       408      412       +4
Impacted Files Coverage Δ
src/js/actions/WordAlignmentActions.js 29.77% <ø> (ø) ⬆️
src/js/actions/WordAlignmentLoadActions.js 74.13% <100%> (ø) ⬆️
src/js/helpers/VerseObjectHelpers.js 95.58% <100%> (ø) ⬆️
src/js/helpers/ResourcesHelpers.js 77.89% <100%> (+1.29%) ⬆️
src/js/helpers/AlignmentHelpers.js 94.23% <60%> (-2.62%) ⬇️
src/js/helpers/WordAlignmentHelpers.js 91.83% <68.18%> (-5.64%) ⬇️
...FileConversionHelpers/UsfmFileConversionHelpers.js 87.5% <90%> (+0.26%) ⬆️
src/js/actions/ResourcesActions.js 68.67% <94.11%> (+3.67%) ⬆️
src/js/helpers/manifestHelpers.js 45.94% <0%> (-2.71%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update fd2ffe9...4486dbc. Read the comment docs.

@PhotoNomad0 PhotoNomad0 changed the title WIP: Feature #3186/import alignment data with USFM import Feature #3186/import alignment data with USFM import Feb 17, 2018
@PhotoNomad0 PhotoNomad0 self-assigned this Feb 19, 2018
…ationCore into feature-mcleanb-3186/importAlignmentDataWithUSFM.2
@klappy
Copy link
Contributor

klappy commented Feb 20, 2018

src/js/helpers/ResourcesHelpers.js, line 18 at r2 (raw file):

      const STATIC_RESOURCES_BIBLES_PATH = path.join(STATIC_RESOURCES_PATH, languagesId, 'bibles');
      const BIBLE_RESOURCES_PATH = path.join(USER_RESOURCES_PATH, languagesId, 'bibles');
      let bibleNames = fs.readdirSync(STATIC_RESOURCES_BIBLES_PATH).filter(folder => { // filter out .DS_Store

Was this added back on purpose? These were filtered out since they weren't doing anything. There aren't any folders .DS_Store just files and we don't need these in this file, it happens in a few blocks below as well.


Comments from Reviewable

@klappy
Copy link
Contributor

klappy commented Feb 20, 2018

Reviewed 8 of 11 files at r1, 2 of 2 files at r2.
Review status: 10 of 13 files reviewed at latest revision, 1 unresolved discussion, some commit checks failed.


Comments from Reviewable

@PhotoNomad0
Copy link
Contributor Author

Review status: 10 of 13 files reviewed at latest revision, 1 unresolved discussion, some commit checks failed.


src/js/helpers/ResourcesHelpers.js, line 18 at r2 (raw file):

Previously, klappy (Christopher Klapp) wrote…

Was this added back on purpose? These were filtered out since they weren't doing anything. There aren't any folders .DS_Store just files and we don't need these in this file, it happens in a few blocks below as well.

I don't know where it was added, but I don't see any check to make sure these are folders before copying.


Comments from Reviewable

…ationCore into feature-mcleanb-3186/importAlignmentDataWithUSFM.2

# Conflicts:
#	src/js/helpers/WordAlignmentHelpers.js
@PhotoNomad0
Copy link
Contributor Author

Review status: 6 of 11 files reviewed at latest revision, 1 unresolved discussion.


src/js/helpers/ResourcesHelpers.js, line 18 at r2 (raw file):

Previously, PhotoNomad0 (Bruce McLean) wrote…

I don't know where it was added, but I don't see any check to make sure these are folders before copying.

It looks like I hadn't merged with develop recently.


Comments from Reviewable

@PhotoNomad0
Copy link
Contributor Author

Review status: 6 of 11 files reviewed at latest revision, 1 unresolved discussion.


src/js/helpers/ResourcesHelpers.js, line 18 at r2 (raw file):

Previously, PhotoNomad0 (Bruce McLean) wrote…

It looks like I hadn't merged with develop recently.

Done.


Comments from Reviewable

@klappy
Copy link
Contributor

klappy commented Feb 20, 2018

Reviewed 1 of 11 files at r1, 1 of 4 files at r3.
Review status: 7 of 11 files reviewed at latest revision, all discussions resolved.


Comments from Reviewable

@klappy
Copy link
Contributor

klappy commented Feb 20, 2018

Reviewed 1 of 4 files at r3.
Review status: 8 of 11 files reviewed at latest revision, all discussions resolved.


Comments from Reviewable

@klappy
Copy link
Contributor

klappy commented Feb 20, 2018

Reviewed 1 of 11 files at r1.
Review status: 9 of 11 files reviewed at latest revision, all discussions resolved.


Comments from Reviewable

@klappy
Copy link
Contributor

klappy commented Feb 20, 2018

Reviewed 2 of 4 files at r3.
Review status: all files reviewed at latest revision, all discussions resolved.


Comments from Reviewable

@PhotoNomad0 PhotoNomad0 changed the title Feature #3186/import alignment data with USFM import Feature #3186/import alignment data with USFM import, and fix alignment export to USFM Feb 20, 2018
@PhotoNomad0 PhotoNomad0 changed the title Feature #3186/import alignment data with USFM import, and fix alignment export to USFM WIP: Feature #3186/import alignment data with USFM import, and fix alignment export to USFM Feb 21, 2018
@PhotoNomad0
Copy link
Contributor Author

Closed due to breaking changes in develop. Created new: #3895

@PhotoNomad0 PhotoNomad0 deleted the feature-mcleanb-3186/importAlignmentDataWithUSFM.2 branch March 5, 2018 13:32
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

Successfully merging this pull request may close these issues.

2 participants