Skip to content

gatewayEdit Release 2.2.0
Compare
Choose a tag to compare
@elsylambert elsylambert released this 06 Dec 14:09
v2.2.0
3179311
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

v2.2.0 Release Notes

What’s New:

We are pleased to announce that gatewayEdit 2.2.0 is now officially released and is available online at https://gatewayedit.com with add and delete row feature for TSVs, Scripture alignment enhancements and bug fixes for highlighting and merge functionality.

Key Features:

  • Users can now add new rows to tNotes, TWLs and tQuestions. #483 #542 #543
  • Users would be able to add TWL when no items exists for a verse. #585
  • Delete row feature is available for tNotes, TWLs and tQuestions. #484
  • Alignment validation and migration check is available for scripture resources. #565
  • Users would be able to add front matter and align them if the Original text is available. #559
  • Shift+ Click Hotkeys can be used for selecting words for scripture alignment. #524
  • Clear/Reset button is available to clear the existing alignments. #569

Bug fixes:

  • Highlighting would work fine for Greek elision marks and occurrence numbers #535 #570
  • Improvement for merge feature #547, #551 #546

Note: After the upgrade if you find that your screen layout is distorted, please use the menu item Reset Resource Layout to fix the screen.

IMPORTANT NOTE FOR DEVELOPERS

Due to the main and develop branches being out of sync, the develop branch had to be rebased with the relevant changes from master.
This means that if you have done work off of develop, your commit history is most likely different from the new commit history! So, you will have to rebase whatever current work you have with the develop branch! See steps below:

  1. Create a copy of your branch as a backup in case something goes wrong 
    git branch backup-branch
  2. Make sure you are in your feature branch, and then run the rebase command to incorporate the changes from develop 
    git rebase origin/develop
  3. This may be a long process, but solve any merge conflicts for each commit and after resolving run 
    git rebase --continue
  4. Repeat this process until the rebase is finished. At the end, your branch should now contain the commit history contained in develop along with your changes (your changes should be after the develop commits)

For Further Info: Notes on Rebasing

Assets 2
Loading