Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
3.4.1 release
3.4.1 release
copy-paste from requisition. Yea I changed all requisition to notification https://review.openlmis.org/static/ogdo0b/2static/images/wiki/icons/emoticons/wink.gif

copy-paste from requisition. Yea I changed all requisition to notification

OLMIS-5069: Generate ERD for notification service
OLMIS-5069: Generate ERD for notification service
Since we don't have the previously saved builds anymore, I'm creating branches for past releases. I added a simple Jenkinsfile which has two main stages - build and ERD generation. The links in doc...

Since we don't have the previously saved builds anymore, I'm creating branches for past releases. I added a simple Jenkinsfile which has two main stages - build and ERD generation.
The links in docs now point to the last successful builds on release branches, so that we wouldn't have to update links if we decided to rebuild our API docs later on. Does this make sense?
I also wonder if it's alright to modify versions on readthedocs.com to use branches instead of tags, but then the label would change (from v3.3.0 to rel-3.3.0). Otherwise, we would have to modify tags in each repo. What do you think?

OLMIS-4963: Bring back lost ERD and static docs for past releases
OLMIS-4963: Bring back lost ERD and static docs for past releases
LGTM

LGTM

OLMIS-4840, fix UI doc links
OLMIS-4840, fix UI doc links
Nvm, probably it was caused by redeploying on the server.

Nvm, probably it was caused by redeploying on the server.

Yes, I've got this error "Custom Security Schemes are not supported in Try It" and GET button change into Forse GET.

Yes, I've got this error "Custom Security Schemes are not supported in Try It" and GET button change into Forse GET.

Are you providing the Authorization string in the correct format? "Bearer <access token>"

Are you providing the Authorization string in the correct format? "Bearer <access token>"

It does not work when we provide only Authorization. It works properly for access_token or authorization + access_token.

It does not work when we provide only Authorization. It works properly for access_token or authorization + access_token.

I belive this should be "or", not "and". We can either use the access_token parameter or the Authorization header to provide the token and it should work either way.

I belive this should be "or", not "and". We can either use the access_token parameter or the Authorization header to provide the token and it should work either way.

OLMIS-3708: Updated docs about live documentation
OLMIS-3708: Updated docs about live documentation
Looks good, I think it's ready to close.

Looks good, I think it's ready to close.

Oh interesting — quick fix

Oh interesting — quick fix