Issue 26170 show more than 20 items for bundles #27569
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* #26227 adding js engine + js script actionlet + js resource + js servlet. Still missing the graal real work, but most of the dot-boilerplate is kinda done * #26227 adding js engine + js script actionlet + js resource + js servlet. Still missing the graal real work, but most of the dot-boilerplate is kinda done * #26227 adding js engine + js script actionlet + js resource + js servlet. Still missing the graal real work, but most of the dot-boilerplate is kinda done * #26227 adding js engine + js script actionlet + js resource + js servlet. Still missing the graal real work, but most of the dot-boilerplate is kinda done * #26227 now at least compiles ok * #26227 wiring to the dotcms stack * #26227 seems now is kinda working * #26227 minor fix * #26227 adding the ability to print a template or payload return * #26227 now support a bit the request need to more a lot more to make it ok * #26227 moving to the dot-mozilla request * #26227 adding the js request and js context * #26227 adding the js request and js context * #26227 adding more elements to the context * #26227 some more enhacements for response * #26227 adding changes to handle diff results on the graaljs * #26277 adding view tools * #26227 working on proxies and js view tools * #26227 more proxy * #26277 the dotcontent js view tool may be done * #26227 adding the story block map proxy and other fixes * #26227 more changes to support worfklow on js view tools * #26227 now the fireEdit is kinda ready to test * #26227 adding archive * #26227 addding feedback * #26227 adding support for all system actions * #26227 fixes to support wf * #26227 adding the tags view tool; * #26227 adding the Tags and template js view tools * #26227 adding the latest js view tools * #26227 now the dotcache is working on js * #26227 adding the fetch * #26227 adding fetch functionality * #26227 compiling errors fixed * #26227 now the sources are being read from the file system and cache the contents in advance * #26227 now modules are kinda working * #26227 now user modules are working * finally cross site modules can be imported * #26227 adding some fixes * #26227 adding the last proxies by now * #26227 adding the content type api * #26227 adding more changes * $26227 adding error sintax handling * #26227 improving the error msg handling * #26227 adding more error handling * #26227 now the JSContent is being rendered properly * #26227 doc and minor improvements * #26227 adding unit test * #26227 adding unit test * #26227 testing the js engine * #26227 adding test * #26227 fixing dependencies * #26227 fixing dependencies * #26227 fixing unit test * #26227 fixing test * #26277 adding feedback * #26227 sonar feedback * #26277 sonarq feedback * #26277 sonarq feedback * #26277 sonarq feedback * #26277 sonarq feedback * #26227 removing temporaly the postman * #26227 fixing the postman test * #26227 Adding a change on the postman * #26227 now if can not read the modules nor functions, just avoid the loading * #26227 merging with master * #26227 refactoring the IT * #26227 feedback done * #26227 adding sonar feedback * #26227 sonarq fixes * #26227 sonarq fixes * #26227 sonarq fixes
The `json.web.token.allowhttp` property had its default changed from `true` to `false` about a year ago, but the comment above it was not updated to match; it still seemed to imply a default of `true`, and encouraged users to change it in a production environment. This could lead to confusion, or worse! Co-authored-by: erickgonzalez <erick.gonzalez@dotcms.com>
…ders not loading (#27470)
* Update ApiToken_Resource.postman_collection.json * Update ApiToken_Resource.postman_collection.json * Update ApiToken_Resource.postman_collection.json
* #26633 Refactor SitePushHandler and add SiteTestHelper The SitePushHandler class has been refactored to improve readability and maintainability. Helper methods have been introduced to decide whether a site should be published, archived or unpublished. The push handler now utilizes ScheduledExecutorService to handle potential delays in site status changes. Furthermore, SiteTestHelper has been introduced providing common utility functions for site related tests. * #26633 Refactor site testing and enhance site copying command Adjusted SiteCommandIT to ensure a site is created before invoking the copy command. The SiteCopy class's output now includes a note that the copy operation happens in the background. * #26633 Refactor finding site by name into a separate method * #26633 Handle received exceptions when getting site response The commit modifies the logic to handle the processing of responses when invoking the verifyAndReturnSiteAfterCompletion method for site pushing. It now makes use of Java's CompletableFuture.exceptionally method, which allows us to handle exceptions that occur in the previous stages of the pipeline. This change also included a minor adjustment to clarify the calculation for ending time in the Runnable task. * #26633 Disable intermittently failing tests in CLI module The commit marks a substantial number of tests as disabled due to intermittent failures. These tests span multiple files within the CLI module, across different functionalities such as pulling, pushing, and tree traversal. This temporary measure is taken to enable smoother CI runs, while these intermittent issues are being investigated and resolved. * #26633 Applying feedback removing Thread.sleep from code
…the content types (#27477) * feat(edit content) #27289 : Add a button to the Content Type screen to enable the new edit mode * progress * fix conflicts of cherry picks * fix tests and add scenarios * clean up 1 * traductions * labels fix * fix conflicts of cherry picks --------- Co-authored-by: Humberto Morera <humberto.morera@dotcms.com> Co-authored-by: Freddy Montes <751424+fmontes@users.noreply.github.com>
…ata file doesn't have it yet #27393 (#27398) * fix(Edit Content) #27393 : Expose the `editableAsText` attribute even if the metadata file doesn't have it yet * Fixing Integration Test * Fixing `GraphQLTests.json` Postman Test --------- Co-authored-by: Freddy Montes <751424+fmontes@users.noreply.github.com>
* Updating some deprecated action versions. Co-authored-by: Daniel Colina <daniel.colina@dotcms.com>
…ield (#27388) * feat(edit-content) add to binary-field and json-field use custom FieldVariable of Monaco Editor * feat(edit-content) type fixes * Update core-web/libs/edit-content/src/lib/fields/dot-edit-content-binary-field/components/dot-binary-field-editor/dot-binary-field-editor.component.ts Make signal private. Co-authored-by: Rafael Velazco <rjvelazco21@gmail.com> * fix(edit-content) fix comments * fix(edit-content) add properties to sonarqube config --------- Co-authored-by: Rafael Velazco <rjvelazco21@gmail.com>
* Clean-up runner * test * test * test
…om prod and fixing postman Ref:s#25736 (#27480) * #25736 the postman is set to create the CT taking into account the announcementDate as publish date * #25736 megre latest from master * #25736 allowing time for publishing to take effect * #25736 debugging postman failure * #25736 correcting announcements remote query * #25736 code clean up * #25736 updating postman test * #25736 url query fix * #25736 adjusting test * #25736 imrproved IT * #25736 log should be debug
* Update Permission_Resource.postman_collection.json * Update Permission_Resource.postman_collection.json
* Update Scripting_Resource.postman_collection.json * Update Scripting_Resource.postman_collection.json * Update Scripting_Resource.postman_collection.json * Update Scripting_Resource.postman_collection.json --------- Co-authored-by: Mehdi <10160868+mbiuki@users.noreply.github.com>
* Update BringBack.postman_collection.json * Update BringBack.postman_collection.json * Update BringBack.postman_collection.json * Update BringBack.postman_collection.json --------- Co-authored-by: Mehdi <10160868+mbiuki@users.noreply.github.com>
spbolton
approved these changes
Feb 12, 2024
jdotcms
approved these changes
Feb 12, 2024
erickgonzalez
approved these changes
Feb 13, 2024
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
|
erickgonzalez
deleted the
issue-26170-show-more-than-20-items-for-bundles
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed Changes
getPublishQueueElements()method onBundleResourceresource class to list items for all the saved bundles (bundles uploaded or created by the user)Checklist