Gujiawei-Edinburgh commented on issue #236: URL: https://github.com/apache/bifromq/issues/236#issuecomment-4131221665
> Yeah, we do observe some users from the local community finding the explicit *FQN config a bit cumbersome, especially during local dev/test. Maybe we can make a tradeoff here: > > * Make *FQN config optional > * If it’s explicitly set, then we treat it as a hard requirement: > > * the plugin must exist at runtime > * otherwise BifroMQ just fails fast on startup > * If it’s not set, we can follow the behavior suggested by [@liaodn](https://github.com/liaodn) > This way dev stays simple, but prod still has a clear and strict contract. Does this sound reasonable? This tradeoff sounds reasonable. We should also make sure this behavior is clearly documented so expectations are explicit. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
