-
Notifications
You must be signed in to change notification settings - Fork 5
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
To dts #126
Conversation
Bumped to version 1.0.3
* Refactored __transform (flask_nemo.__init__) to _transform * Changed flask.ext.nemo to flask_nemo * Updated CHANGES.md and setup.py * Bumped to version 1.0.3
@PonteIneptique I don't need a review here yet. But the tests that are not passing now have to do with fetching annotations. And I am not sure precisely what has changed and where. I will keep researching, but if you have a tip where to look, I would appreciate it. |
Perhaps a bit more explanation here. The source of the difference is from https://github.com/Capitains/MyCapytain/blob/3ff0f27e514f5895d4f83dbe294d4035a9e4dc53/MyCapytain/resources/texts/local/capitains/cts.py#L235. This used to return an empty list but now it returns an error.
annotations is actually an empty list and thus annotation[0] throws an index error.
|
Matt, care to have a call this afternoon ? |
If @balmas is available as well, that would be great. |
Sure. I am available any time between 2pm and 5pm (so 7-10am eastern time). |
FYI, with MyCapytain 3.0.0, the dts-draft-1 branch of Nautlius, and the to_DTS branch of flask-nemo, all of my unit tests work on formulae-capitains-nemo and everything seems to work locally as well. |
I have solved the problem. The difference was that MyCapytain.resources.texts.local.capitains.cts.getValidReff returned simply a list of the passages before 3.0.0 (e.g., ['1.1', '1.2'...]) whereas now it returns a list of flask-capitains-nemo/flask_nemo/query/interface.py Lines 99 to 106 in 2e87aa2
ref_in_range.intersection(annotation.target.expanded) is never true (ref_in_range is made up of tuples and annotation.target.expanded of strings.I will push a (very small) change here and then you @PonteIneptique can decide whether this makes sense or not. |
I was actually having a look at it, and I am still not sure to understand why the first iteration on |
All tests now pass with MyCapytain 3.0.0 and Nautilus dts-draft-1
I think what you meant is getValidReff returns now CtsReferenceSet which are list of CtsReference which are tuple ? |
That is correct. That is what I meant. |
Have you tried to browse your current website using this version of nemo ? |
I have. And everything works. |
Ok, let me do some cosmetic change for one thing or two |
It is still testing 3.4.5? |
Yup and it should not. Let me do it ;) |
OK. |
Coverage goes down because the line that I left in query/interface.py for backward compatibility is not tested. flask-capitains-nemo/flask_nemo/query/interface.py Lines 136 to 137 in 65516ed
Perhaps it can be removed since I have put MyCapytain>=3.0.0 in the requirements.txt? |
Oh and maybe bump the Minor version :') |
Now you tell me. |
Should it be 1.1 instead of 1.0.4? |
Yup, 1.1.0 is what I meant with minor ;) |
I am not sure about the terminology there. |
The description of Nemo in setup.py is "Flask Extension to browse CTS Repository". Should I change this? Perhaps, "Flask Extension to browse a CapiTainS-compliant Repository"? |
Good catch. Yes :) |
1.0.4 Release (Keep nemo away from MyCapytain 3.0.0)
Looks good to me ! |
Should we PR to master as well and do a 2.0.0 release? |
Yes :')
Le ven. 25 oct. 2019 à 12:48 PM, Matthew Munson <notifications@github.com>
a écrit :
… Should we PR to master as well and do a 2.0.0 release?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#126?email_source=notifications&email_token=AAOXEZTDGB6D7ZOUZTDIERDQQLFGJA5CNFSM4JDM5F52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECH7FZI#issuecomment-546304741>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAOXEZQ3SIS3KPZDKZC77PDQQLFGJANCNFSM4JDM5F5Q>
.
|
No description provided.