Skip to content

Conversation

@arturobernalg
Copy link
Contributor

Impact

  • Bug fix (non-breaking change which fixes expected existing functionality)
  • [X ] Enhancement/New feature (adds functionality without impacting existing logic)
  • Breaking change (fix or feature that would cause existing functionality to change)

Description

@nvoxland
Copy link
Contributor

nvoxland commented Mar 8, 2023

Initial/Pre-Review Thoughts

I didn't actually read through the javadoc changes, so if there's questions during the main review feel free to ask.

Questions I have:

  • None

Potential risks:

  • None

What could make the full review difficult:

  • Nothing

@nvoxland nvoxland assigned nvoxland and unassigned nvoxland Mar 8, 2023
@arturobernalg
Copy link
Contributor Author

Initial/Pre-Review Thoughts

I didn't actually read through the javadoc changes, so if there's questions during the main review feel free to ask.

Questions I have:

  • None

Potential risks:

  • None

What could make the full review difficult:

  • Nothing

I did. Just improvement and add new one.

@MalloD12 MalloD12 self-assigned this Apr 11, 2023
@MalloD12 MalloD12 self-requested a review April 11, 2023 12:52
Copy link
Collaborator

@MalloD12 MalloD12 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved.

Review and testing results:

This looks ok to me. I have only made a very few minor tweaks to some javadocs. Thanks @arturobernalg.

Things to be aware of:

  • None

Things to worry about:

  • None

@MalloD12 MalloD12 changed the base branch from master to 3.3.x May 16, 2023 15:25
@MalloD12 MalloD12 changed the base branch from 3.3.x to master May 16, 2023 15:25
*
* @param contexts The contexts to filter for.
* @param labelExpression The labels to filter for.
* @param collectAllReasons A flag to control whether all skip reasons are accumulated.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do not see the collectAllReasons parameter in the method definition. Additionally, the @return list is not complete (missing ShouldRunChangeSetFilter, ContextChangeSetFilter, LabelChangeSetFilter, DbmsChangeSetFilter and IgnoreChangesetFilter).

The "vbnet copy code" words seem random??? Perhaps a mistake?

CC @MalloD12 , @arturobernalg

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey Erz, I'm going to update this as I saw it collectAllReasons wasn't there previously:

/**
     *
     * Return a ChangeLogIterator constructed with standard filters
     *
     * @param   contexts                           Contexts to filter for
     * @param   labelExpression                    Labels to filter for
     * @param   changeLog                          The changelog to process
     *
     * @return  ChangeLogIterator
     * @throws DatabaseException
     *
     */
    protected ChangeLogIterator getStandardChangelogIterator(Contexts contexts, LabelExpression labelExpression,
                                                             DatabaseChangeLog changeLog) throws DatabaseException {
        return new ChangeLogIterator(changeLog,
                new ShouldRunChangeSetFilter(database),
                new ContextChangeSetFilter(contexts),
                new LabelChangeSetFilter(labelExpression),
                new DbmsChangeSetFilter(database),
                new IgnoreChangeSetFilter());
    }

When talk about the missing filters in the @return do you mean we should be adding them in the javadoc? It specifies a ChangelogIterator instance is returned and that's what the method is returning.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you, @MalloD12 ! I misread the code for @return. I appreciate you removing collectAllReasons @param.

* @throws DatabaseException
* Executes the prepared statement created by the given factory.
*
* @param factory a factory for creating a <code>PreparedStatement</code> object.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should <code>PreparedStatement</code> be `{@code PreparedStatement}'?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If I'm not wrong they both have the same purpose, even {@code} (coming from Java5) is older than which I think will format better indentations and line breaks.

Copy link
Contributor

@XDelphiGrl XDelphiGrl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've left a few comments for (potential) requested changes.

I also validated that we're not making any changes to serialization in JavaDoc annotations to prevent regressions like https://github.com/liquibase/liquibase/pull/4161/files.

MalloD12 added 2 commits May 16, 2023 15:08
…ure/improve-javadoc

# Conflicts:
#	liquibase-standard/src/main/java/liquibase/hub/core/StandardHubService.java
@MalloD12
Copy link
Collaborator

@XDelphiGrl I have made a few updates based on your comments. Can you please re-review them? And please let me know if you think there are more requested changes.

Thanks,
Daniel.

@XDelphiGrl
Copy link
Contributor

Thanks for the code changes, @MalloD12. I'm going to wait for the functional tests to run (since there is a lot of change due to the Hub refactoring work). When those pass, I'll do the final review/approval.

@XDelphiGrl
Copy link
Contributor

XDelphiGrl commented May 16, 2023

For whatever reason, the test harness is lingering in the "pending" state. I've kicked off a manual build here: https://github.com/liquibase/liquibase-test-harness/actions/runs/4996652294. PASSED

I excluded the HSQL and Firebird databases as they are failing due to Titan errors.

Copy link
Contributor

@XDelphiGrl XDelphiGrl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a JavaDoc cleanup PR that improves @param and @return documentation for many methods.

  • No serializable annotations are modified in this PR (which is good!)
  • Functional tests and test harness executions are passing.
  • No additional testing required.

APPROVED

@filipelautert filipelautert added this to the 1NEXT milestone May 17, 2023
@filipelautert filipelautert merged commit d281104 into liquibase:master May 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

7 participants