Tree:
7fcf648f36
2.9
3.0
3.1
3.2
3.3
4.0
4.1
4.2
4.3
4.4
4.4.1
4.4.2
4.4.3
5.0.0
5.0.0-rc.1
5.0.0-rc.2
5.1.1
5.1.3
5.1.4
5.2.0
5.2.1
5.2.2
6.0
6.0.0
6.0.0.1
aspire-integration
dependabot/npm_and_yarn/apps/vue/tests/server/follow-redirects-1.16.0
dependabot/npm_and_yarn/apps/vue/tests/server/lodash-4.18.1
dependabot/npm_and_yarn/apps/vue/tests/server/picomatch-2.3.2
dependabot/npm_and_yarn/apps/vue/tests/server/systeminformation-5.31.6
dependabot/npm_and_yarn/apps/vue/tests/server/vm2-3.11.5
dev
elsa-3.0
flutter
main
master
rel-10.0.2
rel-10.2.0
rel-10.4.0
rel-10.6.0
rel-10.7.0
rel-11.0
rel-11.0.0
rel-7.0.2
rel-7.0.3
rel-7.1.0
rel-7.1.1
rel-7.2.1
rel-7.3.2
rel-7.3.3
rel-7.4.0
rel-8.0.0
rel-8.0.3
rel-8.1.0
rel-8.1.1
rel-8.1.2
rel-8.1.3
rel-8.2.0
rel-8.2.1
rel-8.2.2
rel-8.3.0
rel-8.3.4
rel-9.1.1
rel-9.1.3
rel-9.2.0
rel-9.2.3
rel-9.3.1
rel-9.3.5
rel-9.3.6
upt-5.3.2
upt-5.3.4
upt-5.3.5
upt-6.0.1
upt-6.0.2
upt-7.0.0
upt-7.0.1
upt-7.2.1
upt-7.2.2
upt-7.4.0
upt-8.2.0
vben-5-7-0
10.0.2
10.2.0
10.4.0
10.6.0
10.7.0
3.2.1
3.2.2
3.2.3
3.3.0
3.3.1
3.3.2
4.0.0
4.4.0
4.4.3
5.0.0
5.0.0-rc.2
5.1.1
5.1.3
5.1.4
5.2.0
5.2.1
5.2.2
5.3.0
5.3.2
5.3.4
6.0.0
6.0.1
6.0.2
7.0.0
7.0.1
7.0.2
7.0.3
7.1.0
7.1.1
7.2.1
7.3.2
7.3.3
7.4.0
8.0.0
8.0.3
8.1.0
8.1.1
8.1.2
8.1.3
8.2.0
8.2.1
8.2.2
8.3.0
8.3.4
9.0.4
9.1.1
9.1.3
9.2.0
9.2.1
9.2.3
9.3.5
9.3.6
${ noResults }
2 Commits (7fcf648f36b8d7cbe810c062d060a26054d57504)
| Author | SHA1 | Message | Date |
|---|---|---|---|
|
|
8e93f8225c |
perf(notifications): Build the channel data property metadata without a global lock
`NotificationChannelDataPropertyCache.GetProperties` is read for every payload on the publish path (`NotificationChannelDataResolver` and `NotificationChannelDataSerializer`), but it guarded the whole lookup with one process wide lock, so every cache hit queued behind the lock and the first reflection plus `Expression.Compile()` for one payload type blocked all the others. Types that have nothing to do with each other were serialized on a single lock. - replace the `Dictionary` plus `SyncLock` pair with a `ConcurrentDictionary<Type, Lazy<NotificationChannelDataProperty[]>>`, so the hit path takes no lock and building one type no longer blocks reads of another - `Lazy<T>` keeps the build at most once: `GetOrAdd` may invoke its factory more than once under contention, but only one instance is stored and returned, and `LazyThreadSafetyMode.ExecutionAndPublication` makes the other threads wait for it - move the reflection and the expression compiling behind the `Lazy` factory so they never run while a lock is held - extract the population into `CreateProperties`; the selector, the attribute driven key resolution and the compiled getters/setters are unchanged, as is the returned array (callers only enumerate it) Tests: the cache had no concurrency coverage, which is the property this change rests on. Add `Should_Build_Property_Metadata_Once_Under_Concurrency`, which reads five payload types from 320 parallel calls and asserts every call observed the very same metadata instance, and `Should_Return_Same_Instance_On_Repeated_Calls`. |
1 month ago |
|
|
2064de2138 |
feat(notifications): Resolve channel specific payloads from the notification property bag
Every channel needs its own message shape (a WeChat Work template card, a webhook news article, a wx-pusher URL), but the only way to carry it was to stuff those types into `NotificationData`, which couples the producer to the channels and forces a schema change whenever a channel gains a field. Channels now declare their own payload types and the property bag carries them under per channel key prefixes, so one `ExtraProperties` column serves every channel and no notification table has to change. - add the channel data contract to `LINGYUN.Abp.Notifications.Core`: `NotificationChannelData` base type, `[NotificationChannelData]` / `[NotificationChannelProperty]` annotations, `NotificationChannelDataDescriptor`, `NotificationChannelDataFormat` and `NotificationChannelDataPresenceMode` - add the implementation to `LINGYUN.Abp.Notifications`: `INotificationChannelDataResolver` dispatching payloads in priority order, `INotificationChannelDataAccessor` reading and writing typed values in the property bag, `INotificationChannelDataSerializer` for the producer side, `INotificationChannelDataPresenceProvider`, `AbpNotificationChannelDataOptions` and `AbpNotificationChannelDataConfigurationException` for registration time validation - keys are namespaced per channel (`wx-work:`, `wx-work-hook:`, `wx-mp:`, `pusher:`, `plus:`) and matched case insensitively, so channels cannot collide in the shared property bag; complex payloads are stored as JSON strings and deserialized back with the configured `IJsonSerializer` - the WeChat Work channel gains 18 channel data types plus `WeChatWorkMessageFactory`, and the webhook channel 16 plus `WeChatWorkWebhookMessageFactory`, covering text, markdown, markdown_v2, image, news, file, voice, template card, mini program notice and mp news - PushPlus, WxPusher and the WeChat mini program channel adopt the same contract; the mini program keys are prefixed and the historical bare keys are kept as a read only fallback, marked `[Obsolete]` with the provider's `ApplyLegacyKeys` as the only sanctioned read site - delete the WxPusher `NotificationDataExtensions.SetUrl` in favour of the typed accessor - add `WebhookTemplateCardSystemTextJsonConverter` so the abstract webhook template card survives the property bag round trip, and make `WeChatWorkWebhookNewsMessage` public - test projects `LINGYUN.Abp.Notifications.ChannelData.Tests`, `...PushPlus.Tests`, `...WeChat.Work.Tests` and `...Webhook.WeChat.Work.Tests` (real ABP container, fake senders registered through `context.Services.Replace` so no real API is called), the mini program and wx-pusher tests now drive a fake sender, and each channel verifies payloads restored from a raw database JSON string as well as from memory |
1 month ago |