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

ContextPath Prefixed - Multiple Occurrences - For Non Cloud #66

Merged

Conversation

friendlymahi
Copy link

- For multiple calls via $.ajax/.getJson & more
- Fixes Issue brightcove#64
@friendlymahi
Copy link
Author

@dcolvinbc - As advised, moved the changes using the new branch. Once these changes are merged to OnPrem/Non Cloud version, then I can make the changes in cloud version as well. Thanks !

@friendlymahi
Copy link
Author

@hngrylobster @dcolvinbc - Hope you are doing well. Any luck with the review and plan on when we can expect these in new version for use. Thanks!

@dcolvinbc
Copy link
Collaborator

@friendlymahi Sorry for the late response. I had a concern i had put on the other PR about not null checking CQ.shared.HTTP.getContextPath() before you put in a string. I think we should put in something that will check if is null or empty dont put in the string. I know that sounds like an odd request but I want to make sure we do not affect other customers as well. Something like this below would be good on those.

image

@friendlymahi
Copy link
Author

Sure np.. It's a fair ask. I will make the changes and send back 😊

@friendlymahi
Copy link
Author

@dcolvinbc - Looks like there were more occurences to this method CQ.shared.HTTP.getContextPath() than the ones I added. So added a common falsy check to all these occurrences by replacing them with an empty character '' when the expression is evaluated as falsy. Please review now and let me know if more changes are necessary.

Thanks !

@friendlymahi
Copy link
Author

Good morning. Any update on this request? Another question. I know it may not happen but will ask 😊. Do you intend to atleast keep the core bundle on nexus or an externally accessible public repository for us to add bright cove as a dependency on our code base?

Thanks!

@dcolvinbc dcolvinbc merged commit 43c5c14 into brightcove:release/6.0.5 Mar 8, 2024
3 checks passed
@friendlymahi
Copy link
Author

@dcolvinbc - Thank you so much for the support. Any update on my query regarding public access of the binary artifacts via nexus or maven central??

Thanks in advance!

@hngrylobster
Copy link
Collaborator

We will update our own Nexus with the compiled artifacts - yep. However, we do not provide any sort of SLA on its availability.

@friendlymahi
Copy link
Author

Np. When they are published please reply back here or update your docs. Additionally any time line on when this release will be published so we can download the artifact for our environment?

Thanks!

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.

3 participants