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

LPS-115816 change InfoFormValues to InfoItemFieldValues on names used #306

Conversation

AliciaGarciaGarcia
Copy link
Collaborator

No description provided.

brianchandotcom and others added 30 commits June 23, 2020 21:34
Why?
1) In reality this is not tied to a form, that's just one use case. So just referring to it as "Field Values" is more accurate
2) Since it provides a way to keep a reference to the InfoItem where the values come from, it should not just be InfoFieldValues but InfoItemFieldValues
…to the InfoItem the values are from

It was already assumed in some client code that the reference would exist, but the API was not enforcing it, which could have led to NullPointerException errors at one point. Not anymore :)
…a given item object

This provider will allow simplifying InfoItemFormProvider by removing the methods related to retrieving values
…es with usages of the new InfoItemFieldValuesProvider
…o an implementation of InfoItemFieldValuesProvider

Extract field definitions into the new JournalArticleInfoItemFields interface to avoid duplication
… implementation of InfoItemFieldValuesProvider

Extract field definitions into the new BlogsEntryInfoItemFields interface to avoid duplication
… implementation of InfoItemFieldValuesProvider

Extract field definitions into the new AssetEntryInfoItemFields interface to avoid duplication
…o register the instances as InfoItemFieldValuesProvider services
…ount into a supplier to avoid a db query if it's not used later

Note: this has nothing to do with this ticket, but it's a super small fix so I decided to just do it now
…ave been accidentally reordered while source formatting)
@AliciaGarciaGarcia
Copy link
Collaborator Author

ci:forward

@liferay-continuous-integration
Copy link
Collaborator

CI is automatically triggering the following test suites:

  •     ci:test:relevant
  •     ci:test:sf

The pull request will automatically be forwarded to the user brianchandotcom if the following test suites pass:

  •     ci:test:relevant
  •     ci:test:sf
  •     ci:test:stable

@liferay-continuous-integration
Copy link
Collaborator

✔️ ci:test:sf - 1 out of 1 jobs passed in 4 minutes

Click here for more details.

Base Branch:

Branch Name: master
Branch GIT ID: 0df14b8ed544d2c0286c4cc200703e3005e673ad

Sender Branch:

Branch Name: LPS-115816.5
Branch GIT ID: 4c0fda38eae64030073aac814e30f9272cd45c22

1 out of 1jobs PASSED
1 Successful Jobs:
For more details click here.

@liferay-continuous-integration
Copy link
Collaborator

✔️ ci:test:stable - 20 out of 20 jobs passed

✔️ ci:test:relevant - 48 out of 48 jobs passed in 1 hour 56 minutes

Click here for more details.

Base Branch:

Branch Name: master
Branch GIT ID: 9b16898f5c46d1e57b05a17ea68f5d1e6233ba45

Copied in Private Modules Branch:

Branch Name: master-private
Branch GIT ID: 132b6a6de2529323e7ade179ae4e1386e97be5cb

ci:test:stable - 20 out of 20 jobs PASSED
20 Successful Jobs:
ci:test:relevant - 48 out of 48 jobs PASSED
48 Successful Jobs:
For more details click here.

@liferay-continuous-integration
Copy link
Collaborator

All required test suite(s) passed.
Forwarding pullrequest to brianchandotcom.

@liferay-continuous-integration
Copy link
Collaborator

Pull request has been successfully forwarded to brianchandotcom#90609

@liferay-continuous-integration
Copy link
Collaborator

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.