Timeline for fflib as Second Generation Managed Package (2GP)
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 29, 2021 at 19:41 | answer | added | ImJohnMDaniel | timeline score: 5 | |
| Dec 23, 2021 at 15:46 | answer | added | Vivek M. Chawla | timeline score: 7 | |
| Dec 21, 2021 at 9:33 | comment | added | lightxx | @cropredy thanks! | |
| Dec 21, 2021 at 5:28 | comment | added | cropredy | I'll cross-post this on Twitter to see if John Daniel has thoughts | |
| Dec 20, 2021 at 12:15 | comment | added | Phil W | That answer is predicated on 1GP managed packages, where "global" is a nightmare because it causes freezing of APIs and version-to-version compatibility issues. I don't believe namespace accessibility has the same constraints and should, therefore, be quite supportable in the code base. My only concern: what happens when you use this annotation outside a 2GP? I've not tried the latter. I would hope it is effectively ignored, but can't be sure. | |
| Dec 20, 2021 at 12:08 | comment | added | lightxx | @PhilW I thought so as well, but then I found this: github.com/apex-enterprise-patterns/fflib-apex-common/issues/85, and even though it's 6 years old Andrew makes it quite clear that he prefers to have fflib being embedded it in the package. So the question is how much chances a PR has getting merged. | |
| Dec 20, 2021 at 12:04 | comment | added | Phil W | Your suggestion makes sense (having this available in a separate 2GP). How about creating a PR against the fflib repo adding NamespaceAccessible annotations like you suggest? | |
| Dec 20, 2021 at 12:00 | history | tweeted | twitter.com/StackSalesforce/status/1472899606870691844 | ||
| Dec 20, 2021 at 9:32 | history | asked | lightxx | CC BY-SA 4.0 |