Skip to content

Conversation

@yungcheng
Copy link
Contributor

No description provided.

@kevinv11n
Copy link

@apapko @Gr8Gatsby what's the branching strategy for this repo for features coming in the next major release? This PR is applicable only to the 228 / Winter 21 release.

@pmdartus
Copy link
Contributor

@yungcheng @kevinv11n We have not enabled this on the server for 228 and it won't also be enabled for 230. It should be fine merging this right now.

Is this PR still valid? I am preparing a new release of this package.

@yungcheng
Copy link
Contributor Author

yungcheng commented Nov 20, 2020

Is this PR still valid? I am preparing a new release of this package.

It is still valid and would be great if you can merge it

@kevinv11n
Copy link

kevinv11n commented Nov 20, 2020

We have not enabled this on the server for 228 and it won't also be enabled for 230. It should be fine merging this right now.

These eslint rules are provided to customers, right?

Assuming so this change should've gone out in 228 when getObjectInfos was released to customers.

@pmdartus pmdartus force-pushed the getObjectInfos branch 2 times, most recently from c2c83a1 to c6cac37 Compare November 23, 2020 09:17
@pmdartus pmdartus merged commit b94f28b into salesforce:master Nov 23, 2020
@pmdartus
Copy link
Contributor

It has been published with the V0.8.0 release.

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